MBS service transmission progress control method and device, and communication equipment
Patent Information
- Application Number
- CN202080105067.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-09-18
- Publication Date
- 2025-02-25
- Estimated Expiration
- 2040-09-18
AI Technical Summary
In the field of mobile communication technology, due to different scheduling progress differences between different base stations of the same multimedia multicast service (MBS) service, MBS service data may be lost during the movement of terminal devices.
The MBS transmission progress request message is sent to at least two base stations through the core network element, and the MBS transmission progress report of each base station is obtained, and the progress of MBS service data sent to each base station is adjusted based on these reports to reduce the transmission between base stations. Progress difference.
It effectively reduces the loss of MBS service data due to differences in transmission progress between base stations, and ensures the continuity of data during terminal equipment movement.
Smart Images

Figure CN116114375B_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present application relate to the field of mobile communication technology, and specifically to a method and device for controlling the transmission progress of a Multimedia Broadcast Service (MBS) service, and a communication device. Background Art
[0002] For the same MBS service, the core network will send MBS service data to multiple base stations at the same time. However, the progress of scheduling MBS service data by different base stations will be different, which will result in different progress of MBS service data transmitted by different base stations. When a terminal device moves from a cell covered by one base station to a cell covered by another base station, it needs to continue to receive MBS service data. If the progress of MBS transmission data in the two cells is significantly different, there will be a problem of MBS service data loss. Summary of the invention
[0003] The embodiments of the present application provide a method and apparatus for controlling MBS service transmission progress, and a communication device.
[0004] The method for controlling MBS service transmission progress provided in the embodiment of the present application includes:
[0005] The core network element sends an MBS transmission progress request message to at least two base stations, where the MBS transmission progress request message is used to request reporting of an MBS transmission progress report;
[0006] The core network element receives the MBS transmission progress reports sent by the at least two base stations, and adjusts the progress of sending the MBS service data to the at least two base stations based on the MBS transmission progress reports sent by the at least two base stations.
[0007] The method for controlling MBS service transmission progress provided in the embodiment of the present application includes:
[0008] The first base station sends an MBS transmission progress request message to at least one second base station, where the MBS transmission progress request message is used to request reporting of an MBS transmission progress report;
[0009] The first base station receives the MBS transmission progress report sent by the at least one second base station, and adjusts the progress of the MBS service data scheduled on the air interface based on the MBS transmission progress report sent by the at least one second base station.
[0010] The MBS service transmission progress control device provided in the embodiment of the present application is applied to a core network element, and the device includes:
[0011] A sending unit, configured to send an MBS transmission progress request message to at least two base stations, wherein the MBS transmission progress request message is used to request reporting of an MBS transmission progress report;
[0012] A receiving unit, configured to receive the MBS transmission progress reports sent by the at least two base stations;
[0013] An adjusting unit is used to adjust the progress of MBS service data sent to the at least two base stations based on the MBS transmission progress reports sent by the at least two base stations.
[0014] The MBS service transmission progress control device provided in the embodiment of the present application is applied to a first base station, and the device includes:
[0015] a sending unit, configured to send an MBS transmission progress request message to at least one second base station, wherein the MBS transmission progress request message is used to request reporting of an MBS transmission progress report;
[0016] A receiving unit, configured to receive an MBS transmission progress report sent by the at least one second base station;
[0017] An adjusting unit is used to adjust the progress of MBS service data scheduled on the air interface based on the MBS transmission progress report sent by the at least one second base station.
[0018] The communication device provided in the embodiment of the present application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the above-mentioned method for controlling the transmission progress of the MBS service.
[0019] The chip provided in the embodiment of the present application is used to implement the above-mentioned method for controlling the transmission progress of the MBS service.
[0020] Specifically, the chip includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes the above-mentioned method for controlling the transmission progress of the MBS service.
[0021] The computer-readable storage medium provided in the embodiment of the present application is used to store a computer program, and the computer program enables a computer to execute the above-mentioned method for controlling the transmission progress of MBS services.
[0022] The computer program product provided in the embodiment of the present application includes computer program instructions, and the computer program instructions enable a computer to execute the above-mentioned method for controlling the transmission progress of MBS services.
[0023] The computer program provided in the embodiment of the present application, when executed on a computer, enables the computer to execute the above-mentioned method for controlling the transmission progress of the MBS service.
[0024] The technical solution of the embodiment of the present application is that, on the one hand, the core network element obtains the MBS transmission progress report of at least two base stations, and then controls the MBS transmission progress according to the MBS transmission progress report of at least two base stations, so that the difference in MBS transmission progress between base stations is reduced, and the degree of MBS service data loss caused by the terminal device moving between base stations is reduced. On the other hand, the base stations exchange MBS transmission progress reports, and the base stations can adjust their own MBS service transmission progress according to the MBS service transmission progress of other base stations, so that the difference in MBS transmission progress between base stations is reduced, and the degree of MBS service data loss caused by the terminal device moving between base stations is reduced. Through the above technical solution, the MBS service transmission progress is coordinated between base stations, so that the MBS service transmission progress between each base station is synchronized as much as possible, avoiding data loss of terminal devices during mobility. BRIEF DESCRIPTION OF THE DRAWINGS
[0025] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:
[0026] Figure 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application;
[0027] Figure 2 This is a transmission network architecture diagram of the MBS service provided in the embodiment of the present application;
[0028] Figure 3 This is a flow chart of a method for controlling MBS service transmission progress provided in an embodiment of the present application. Figure 1 ;
[0029] Figure 4 It is a schematic diagram of interaction between a core network element and a base station provided in an embodiment of the present application;
[0030] Figure 5 This is a flow chart of a method for controlling MBS service transmission progress provided in an embodiment of the present application. Figure 2 ;
[0031] Figure 6 is a schematic diagram of interaction between base stations provided in an embodiment of the present application;
[0032] Figure 7 The structure of the control device for MBS service transmission progress provided by the embodiment of the present application is shown in FIG. Figure 1 ;
[0033] Figure 8The structure of the control device for MBS service transmission progress provided by the embodiment of the present application is shown in FIG. Figure 2 ;
[0034] Fig. 9 is a schematic structural diagram of a communication device provided in an embodiment of the present application;
[0035] Fig.10 It is a schematic structural diagram of the chip of an embodiment of the present application. DETAILED DESCRIPTION
[0036] The following will describe the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0037] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, 5G communication system or future communication system, etc.
[0038] For example, the communication system 100 used in the embodiment of the present application is as follows: Figure 1 As shown. The communication system 100 may include a network device 110, which may be a device that communicates with a terminal 120 (or referred to as a communication terminal, terminal). The network device 110 may provide communication coverage for a specific geographical area, and may communicate with terminals located within the coverage area. Optionally, the network device 110 may be an evolved base station (eNB or eNodeB) in an LTE system, or a wireless controller in a cloud radio access network (CRAN), or the network device may be a mobile switching center, a relay station, an access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a network-side device in a 5G network, or a network device in a future communication system, etc.
[0039] The communication system 100 also includes at least one terminal 120 located within the coverage of the network device 110. As used herein, "terminal" includes but is not limited to connecting via a wired line, such as via a Public Switched Telephone Networks (PSTN), a Digital Subscriber Line (DSL), a digital cable, a direct cable connection; and / or another data connection / network; and / or via a wireless interface, such as, for a cellular network, a Wireless Local Area Network (WLAN), a digital television network such as a DVB-H network, a satellite network, an AM-FM broadcast transmitter; and / or another terminal configured to receive / send communication signals; and / or an Internet of Things (IoT) device. A terminal configured to communicate via a wireless interface may be referred to as a "wireless communication terminal", "wireless terminal" or "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular telephones; Personal Communications System (PCS) terminals that may combine cellular radiotelephones with data processing, fax, and data communications capabilities; PDAs that may include radiotelephones, pagers, Internet / Intranet access, Web browsers, notepads, calendars, and / or Global Positioning System (GPS) receivers; and conventional laptop and / or palmtop receivers or other electronic devices that include radiotelephone transceivers. A terminal may refer to an access terminal, User Equipment (UE), a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device. The access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal in a 5G network, or a terminal in a future evolved PLMN, etc.
[0040] Optionally, the terminals 120 may perform device-to-device (D2D) communication.
[0041] Optionally, the 5G communication system or 5G network may also be referred to as a New Radio (NR) system or NR network.
[0042] Figure 1 One network device and two terminals are shown exemplarily. Optionally, the communication system 100 may include multiple network devices and each network device may include another number of terminals within its coverage area, which is not limited in the embodiments of the present application.
[0043] Optionally, the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiments of the present application.
[0044] It should be understood that the device with communication function in the network / system in the embodiment of the present application can be referred to as a communication device. Figure 1 Taking the communication system 100 shown as an example, the communication equipment may include a network device 110 and a terminal 120 with communication functions. The network device 110 and the terminal 120 may be the specific devices described above and will not be repeated here. The communication equipment may also include other devices in the communication system 100, such as a network controller, a mobile management entity and other network entities, which is not limited in the embodiments of the present application.
[0045] It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is only a description of the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.
[0046] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions related to the embodiments of the present application are described below.
[0047] With the pursuit of speed, latency, high-speed mobility, energy efficiency and the diversity and complexity of services in future life, the Third Generation Partnership Project (3GPP) rd The 3rd Generation Partnership Project (3GPP) international standard organization has begun to develop 5G. The main application scenarios of 5G are: enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC).
[0048] On the one hand, eMBB still aims at users to obtain multimedia content, services and data, and its demand is growing rapidly. On the other hand, since eMBB may be deployed in different scenarios, such as indoors, in urban areas, and in rural areas, its capabilities and requirements vary greatly, so it cannot be generalized and must be analyzed in detail in combination with specific deployment scenarios. Typical applications of URLLC include: industrial automation, power automation, remote medical operations (surgery), traffic safety, etc. Typical features of mMTC include: high connection density, small data volume, latency-insensitive services, low cost and long service life of modules, etc.
[0049] In the early days of NR deployment, complete NR coverage was difficult to obtain, so the typical network coverage was wide-area LTE coverage and NR island coverage. In addition, a large number of LTEs are deployed below 6GHz, and there is little spectrum below 6GHz available for 5G. Therefore, NR must study spectrum applications above 6GHz, but high-frequency bands have limited coverage and fast signal fading. At the same time, in order to protect mobile operators' early investments in LTE, a tight interworking working mode between LTE and NR was proposed.
[0050] RRC Status
[0051] In order to reduce air interface signaling and quickly restore wireless connections and data services, 5G defines a new Radio Resource Control (RRC) state, namely the RRC inactive (RRC_INACTIVE) state. This state is different from the RRC idle (RRC_IDLE) state and the RRC active (RRC_ACTIVE) state.
[0052] in,
[0053] 1) RRC_IDLE state (abbreviated as idle state): Mobility is based on UE cell selection and reselection, paging is initiated by the core network (CN), and the paging area is configured by the CN. There is no UE context on the base station side and no RRC connection.
[0054] 2) RRC_CONNECTED state (referred to as connected state): There is an RRC connection, and UE context exists on the base station side and the UE side. The network side knows the location of the UE at the specific cell level. Mobility is mobility controlled by the network side. Unicast data can be transmitted between the UE and the base station.
[0055] 3) RRC_INACTIVE state (abbreviated as inactive state): Mobility is based on UE cell selection and reselection, there is a connection between CN and NR, the UE context exists on a certain base station, paging is triggered by RAN, and the RAN-based paging area is managed by RAN. The network side knows the UE location based on the RAN paging area level.
[0056] MBMS
[0057] MBMS is a technology that transmits data from one data source to multiple terminal devices by sharing network resources. While providing multimedia services, this technology can effectively utilize network resources and achieve broadcast and multicast of multimedia services at a higher rate (such as 256kbps).
[0058] Since MBMS spectrum efficiency is low, it is not enough to effectively carry and support the operation of mobile TV services. Therefore, in LTE, 3GPP explicitly proposed to enhance the support capability for downlink high-speed MBMS services and determined the design requirements for the physical layer and air interface.
[0059] 3GPP R9 introduced evolved MBMS (eMBMS) into LTE. eMBMS proposed the concept of Single Frequency Network (SFN), namely Multimedia Broadcast multicast service Single Frequency Network (MBSFN). MBSFN uses a unified frequency to send service data in all cells at the same time, but synchronization between cells must be guaranteed. This method can greatly improve the overall signal-to-noise ratio distribution of the cell, and the spectrum efficiency will also be greatly improved accordingly. eMBMS implements broadcast and multicast of services based on the IP multicast protocol.
[0060] In LTE or enhanced LTE (LTE-Advanced, LTE-A), MBMS has only a broadcast bearer mode, but no multicast bearer mode. In addition, the reception of MBMS services is applicable to terminal devices in an idle state or a connected state.
[0061] 3GPP R13 introduced the concept of Single Cell Point To Multipoint (SC-PTM), which is based on the MBMS network architecture.
[0062] MBMS introduces new logical channels, including Single Cell-Multicast Control Channel (SC-MCCH) and Single Cell-Multicast Transport Channel (SC-MTCH). SC-MCCH and SC-MTCH are mapped to Downlink Shared Channel (DL-SCH), and further, DL-SCH is mapped to Physical Downlink Shared Channel (PDSCH), where SC-MCCH and SC-MTCH are logical channels, DL-SCH is a transport channel, and PDSCH is a physical channel. SC-MCCH and SC-MTCH do not support Hybrid Automatic Repeat reQuest (HARQ) operation.
[0063] MBMS introduces a new type of System Information Block (SIB), namely SIB20. Specifically, the configuration information of SC-MCCH is transmitted through SIB20, and there is only one SC-MCCH in a cell. The configuration information of SC-MCCH includes: the modification period of SC-MCCH, the repetition period of SC-MCCH, and the radio frame and subframe for scheduling SC-MCCH. Further, 1) The boundary of the modification period of SC-MCCH satisfies SFN mod m = 0, where SFN represents the system frame number of the boundary, and m is the modification period of SC-MCCH configured in SIB20 (i.e., sc-mcch-ModificationPeriod). 2) The radio frame for scheduling SC-MCCH satisfies: SFN mod mcch-RepetitionPeriod = mcch-Offset, where SFN represents the system frame number of the radio frame, mcch-RepetitionPeriod represents the repetition period of SC-MCCH, and mcch-Offset represents the offset of SC-MCCH. 3) The subframe for scheduling SC-MCCH is indicated by sc-mcch-Subframe.
[0064] SC-MCCH is scheduled through the Physical Downlink Control Channel (PDCCH). On the one hand, a new Radio Network Temporary Identity (RNTI), namely the Single Cell RNTI (SC-RNTI), is introduced to identify the PDCCH (such as SC-MCCHPDCCH) used to schedule SC-MCCH. Optionally, the SC-RNTI is fixed to FFFC. On the other hand, a new RNTI, namely the Single Cell Notification RNTI (SC-N-RNTI), is introduced to identify the PDCCH (such as the notification PDCCH) used to indicate the change notification of SC-MCCH. Optionally, the SC-N-RNTI is fixed to FFFB; further, one of the 8 bits of DCI 1C can be used to indicate the change notification. In LTE, the configuration information of SC-PTM is based on the SC-MCCH configured by SIB20, and then the SC-MCCH configures the SC-MTCH, which is used to transmit service data.
[0065] Specifically, SC-MCCH only transmits one message (i.e., SCPTMConfiguration), which is used to configure the configuration information of SC-PTM. The configuration information of SC-PTM includes: Temporary Mobile Group Identity (TMGI), session id, group RNTI (G-RNTI), discontinuous reception (DRX) configuration information, and SC-PTM service information of neighboring cells. It should be noted that SC-PTM in R13 does not support the robust header compression (ROHC) function.
[0066] The downlink discontinuous reception of SC-PTM is controlled by the following parameters: onDurationTimerSCPTM, drx-InactivityTimerSCPTM, SC-MTCH-SchedulingCycle, and SC-MTCH-SchedulingOffset.
[0067] When [(SFN*10)+subframe number]modulo(SC-MTCH-SchedulingCycle)=SC-MTCH-SchedulingOffset is satisfied, the timer onDurationTimerSCPTM is started;
[0068] When receiving downlink PDCCH scheduling, start the timer drx-InactivityTimerSCPTM;
[0069] Downlink SC-PTM services are received only when the timer onDurationTimerSCPTM or drx-InactivityTimerSCPTM is running.
[0070] SC-PTM service continuity adopts the MBMS service continuity concept based on SIB15, namely the "SIB15+MBMSInterestIndication" mode. The service continuity of idle terminal devices is based on the concept of frequency priority.
[0071] In the technical solution of the embodiment of the present application, a new SIB (called the first SIB) is defined. The first SIB includes configuration information of the first MCCH. Here, the first MCCH is the control channel of the MBMS service. In other words, the first SIB is used to configure the configuration information of the control channel of NRMBMS. Optionally, the control channel of NR MBMS can also be called NR MCCH (i.e., the first MCCH).
[0072] Further, the first MCCH is used to carry the first signaling. The embodiment of the present application does not limit the name of the first signaling. For example, the first signaling is signaling A. The first signaling includes configuration information of at least one first MTCH. Here, the first MTCH is a service channel (also called a data channel or a transmission channel) of the MBMS service. The first MTCH is used to transmit MBMS service data (such as service data of NR MBMS). In other words, the first MCCH is used to configure the configuration information of the service channel of NR MBMS. Optionally, the service channel of NR MBMS can also be called NR MTCH (i.e., the first MTCH).
[0073] Specifically, the first signaling is used to configure the service channel of NR MBMS, the service information corresponding to the service channel, and the scheduling information corresponding to the service channel. Further, optionally, the service information corresponding to the service channel, such as identification information of the service such as TMGI and session id. The scheduling information corresponding to the service channel, such as the RNTI used when the MBMS service data corresponding to the service channel is scheduled, such as G-RNTI, DRX configuration information, etc.
[0074] It should be noted that the transmission of the first MCCH and the first MTCH are both based on PDCCH scheduling. The RNTI used by the PDCCH for scheduling the first MCCH uses a network-wide unique identifier, that is, a fixed value. The RNTI used by the PDCCH for scheduling the first MTCH is configured through the first MCCH.
[0075] It should be noted that the embodiments of the present application do not limit the naming of the first SIB, the first MCCH and the first MTCH. For ease of description, the first SIB may also be referred to as SIB, the first MCCH may also be referred to as MCCH, and the first MTCH may also be referred to as MTCH. The PDCCH for scheduling MCCH (i.e., MCCHPDCCH) and notifying PDCCH are configured through SIB, wherein the DCI carried by MCCH PDCCH is scheduled for transmitting the PDSCH for MCCH (i.e., MCCH PDSCH). Further, M PDCCHs for scheduling MTCH (i.e., MTCH 1PDCCH, MTCH2PDCCH, ..., MTCH M PDCCH) are configured through MCCH, wherein the DCI carried by MTCH n PDCCH is scheduled for transmitting the PDSCH for MTCH n (i.e., MTCH n PDSCH), and n is an integer greater than or equal to 1 and less than or equal to M. MCCH and MTCH are mapped to DL-SCH, and further, DL-SCH is mapped to PDSCH, wherein MCCH and MTCH belong to logical channels, DL-SCH belongs to a transport channel, and PDSCH belongs to a physical channel.
[0076] It should be noted that the MBMS service in the above solution includes but is not limited to multicast service and groupcast service. The embodiment of the present application takes the MBS service as an example for explanation, and the description of "MBS service" can also be replaced by "multicast service" or "groupcast service" or "MBMS service".
[0077] In NR MBS, the transmission network architecture of MBS services is as follows: Figure 2 As shown, the 5G core network transmits the MBS service flow to the 5G access network (such as gNB) through a shared GTP tunnel. The 5G access network can determine whether to transmit the MBS service flow to the terminal device through a point-to-point (PTP) mode or a point-to-multipoint (PTM) mode. Here, the PTP mode is also a unicast mode, and the PTM mode is also a multicast mode.
[0078] For the same MBS service, the core network will send MBS service data to multiple base stations at the same time. For example, the core network sends MBS service data to multiple base stations at the same time through a shared GTP tunnel or a GTP tunnel for the terminal device (i.e., per UE). When the terminal device moves from a cell covered by one base station to a cell covered by another base station, it needs to continue to receive MBS service data. If the MBS transmission progress of the two cells is different, for example, one cell transmits faster and the other cell transmits slower, there will be a problem of MBS service data loss. In order to ensure that the MBS service data is not lost during the movement process, data forwarding is required during the switching process. However, for MBS services that do not require data not to be lost, there may be no data forwarding, which will cause the MBS service data to be lost due to the difference in the transmission progress of the two base stations. To this end, the following technical solution of the embodiment of the present application is proposed. The technical solution of the embodiment of the present application ensures that the MBS service transmission progress between the two base stations is as similar as possible, so as to minimize the loss of MBS service data caused by the different MBS service transmission progress of the two base stations.
[0079] Figure 3 This is a flow chart of a method for controlling MBS service transmission progress provided in an embodiment of the present application. Figure 1 ,like Figure 3 As shown, the method for controlling the MBS service transmission progress includes the following steps:
[0080] Step 301: a core network element sends an MBS transmission progress request message to at least two base stations, where the MBS transmission progress request message is used to request reporting of an MBS transmission progress report.
[0081] In an optional manner, the core network network element includes at least one of the following: a session management function network element (Session Management Function, SMF), an access and mobility management function network element (Access and Mobility Management Function, AMF), and a core network user plane function network element (User Plane Function, UPF).
[0082] In an optional embodiment, the base station is a gNB.
[0083] In the embodiment of the present application, a GTP tunnel is established between a core network element and at least two base stations for a certain MBS service. The core network element transmits MBS service data to at least two base stations through the GTP tunnel. Here, the GTP tunnel can be a shared GTP tunnel or a per UE GTP tunnel.
[0084] For example, the core network element transmits MBS service data of a certain MBS service to base station 1 and base station 2 at the same time.
[0085] In the embodiment of the present application, the core network element centrally controls the MBS transmission progress of each base station. To this end, the core network element sends an MBS transmission progress request message to at least two base stations, wherein the MBS transmission progress request message is used to request to report an MBS transmission progress report.
[0086] For example: Refer to Figure 4 , the core network element sends an MBS transmission progress request message to base station 1, and sends an MBS transmission progress request message to base station 2.
[0087] Here, the MBS transmission progress request message is also used to configure the base station to send the MBS service data transmission information of the base station.
[0088] In the embodiment of the present application, the MBS transmission progress request message includes at least one of the following: a service identifier of the MBS service, and a reporting method of the MBS transmission progress report of the MBS service.
[0089] In the above solution, optionally, the service identifier of the MBS service includes at least one of the following: TMGI, G-RNTI, and MBS session identifier.
[0090] In the above solution, optionally, the reporting method of the MBS transmission progress report of the MBS service is a periodic reporting method, a one-time reporting method, or an event-triggered reporting method.
[0091] A) When the reporting mode of the MBS transmission progress report of the MBS service is the periodic reporting mode, the MBS transmission progress request message further includes: a reporting period of the periodic reporting mode.
[0092] B) When the reporting mode of the MBS transmission progress report of the MBS service is the event-triggered reporting mode, the MBS transmission progress request message further includes: an event type and / or a condition satisfied by the event.
[0093] In an optional manner, the event type is the number of MBS service data to be transmitted stored in the base station.
[0094] In an optional manner, the condition for the event to be satisfied is that the number of MBS service data to be transmitted stored in the base station is greater than or greater than or equal to a first threshold; or, the condition for the event to be satisfied is that the number of MBS service data to be transmitted stored in the base station is less than or less than or equal to a second threshold.
[0095] In an example, the reporting method of the MBS transmission progress report of the MBS service is the periodic reporting method, and the base station periodically sends the MBS transmission progress report to the core network element according to the reporting period.
[0096] In an example, the reporting method of the MBS transmission progress report of the MBS service is the one-time reporting method. After receiving the MBS transmission progress request message, the base station directly sends the MBS transmission progress report to the core network element.
[0097] In one example, the reporting method of the MBS transmission progress report of the MBS service is the event-triggered reporting method, and the event type is the number of MBS data to be transmitted stored in the base station, such as the number of PDCP SDUs; the condition satisfied by the event is that the number of MBS data to be transmitted stored in the base station is greater than or equal to N1, N1 is a positive integer, and if the number of PDCP SDUs to be transmitted stored in the base station is greater than or equal to N1, the base station is triggered to send an MBS transmission progress report to a core network element. The condition satisfied by the event may also be that the number of MBS data to be transmitted stored in the base station is less than or less than equal to N2, N2 is a positive integer, and if the number of PDCP SDUs to be transmitted stored in the base station is less than or less than equal to N2, the base station is triggered to send an MBS transmission progress report to a core network element. Optionally, N2 is less than N1.
[0098] Step 302: The core network element receives the MBS transmission progress reports sent by the at least two base stations, and adjusts the progress of sending MBS service data to the at least two base stations based on the MBS transmission progress reports sent by the at least two base stations.
[0099] In the embodiment of the present application, each of the at least two base stations sends an MBS transmission progress report to a core network element based on the MBS transmission progress request message.
[0100] For example: Refer to Figure 4 , base station 1 sends an MBS transmission progress report to the core network element, and base station 2 sends an MBS transmission progress report to the core network element.
[0101] In the embodiment of the present application, the content of the MBS transmission progress report sent by each of the at least two base stations may refer to the following description.
[0102] The MBS transmission progress report includes at least one of the following:
[0103] 1) Service identification of MBS service.
[0104] Here, the service identifier of the MBS service includes at least one of the following: TMGI, G-RNTI, MBS session identifier. The service identifier of the MBS service is used to indicate for which MBS service the MBS transmission progress report is for.
[0105] 2) The cell identifier of the cell where the MBS service is located.
[0106] 3) The number of MBS service data to be transmitted stored in the base station.
[0107] Here, the number of MBS service data to be transmitted stored in the base station is, for example, the number of PDCP SDUs to be transmitted stored in the base station.
[0108] 4) The sequence number (Series Number, SN) of the next MBS service data to be transmitted by the base station.
[0109] 5) The SN of the last MBS service data transmitted by the base station.
[0110] Corresponding to the above 4) and 5), optionally, the SN is a PDCP SN; or, the SN is an SN added by a core network element (such as AMF / UPF).
[0111] Further, optionally, when the reporting mode of the MBS transmission progress report is an event-triggered reporting mode, the MBS transmission progress report further includes at least one of the following: an event type triggering the MBS transmission progress report and a condition satisfied by the event.
[0112] In the above solution of the embodiment of the present application, the event type can be represented by an identifier (ID) of the event type, and the MBS transmission progress report only needs to carry the identifier of the event type.
[0113] In the embodiment of the present application, after the core network element receives the MBS transmission progress report sent by at least two base stations, it determines the number of MBS services to be transmitted stored in at least two base stations based on the MBS transmission progress reports of the at least two base stations. Taking two base stations as an example, if the number of MBS services to be transmitted stored in base station 1 is greater than the number of MBS services to be transmitted stored in base station 2 or the difference between the number of MBS services to be transmitted stored in base station 1 and the number of MBS services to be transmitted stored in base station 2 exceeds a certain threshold, the core network element temporarily does not transmit the MBS service data to the two base stations. In this way, the number of MBS services to be transmitted stored in base station 1 will gradually decrease, thereby shortening the gap between the number of MBS services to be transmitted stored in base station 2. If the difference between the number of MBS services to be transmitted stored in base station 1 and the number of MBS services to be transmitted stored in base station 2 is less than a certain threshold, the core network element continues to transmit the MBS service data to the two base stations.
[0114] For example: the number of MBS services to be transmitted stored in base station 1 is 10, and the number of MBS services to be transmitted stored in base station 2 is 3, which means that the MBS service transmission progress of base station 2 is faster than that of base station 1. The core network element temporarily does not transmit MBS service data to these two base stations. Base station 2 and base station 1 continue to schedule their own MBS service data. After scheduling, base station 1 waits for scheduling by base station 2. When the number of MBS services to be transmitted stored in base station 1 is 3 and the number of MBS services to be transmitted stored in base station 2 is 0, the core network element continues to transmit MBS service data to these two base stations.
[0115] In the above scheme of the embodiment of the present application, the MBS transmission progress request message is sent through the first NGAP signaling, and the MBS transmission progress report is sent through the second NGAP signaling; or, the MBS transmission progress request message is sent through the first GTP-C signaling, and the MBS transmission progress report is sent through the second GTP-C signaling.
[0116] The technical solution of the embodiment of the present application coordinates the MBS transmission progress between the core network element and the base station. The core network element controls and coordinates the MBS service transmission progress to be basically consistent between each base station, so as to minimize the loss of MBS service data caused by the different MBS service transmission progress of the two base stations.
[0117] Figure 5 This is a flow chart of a method for controlling MBS service transmission progress provided in an embodiment of the present application. Figure 2 ,like Figure 5 As shown, the method for controlling the MBS service transmission progress includes the following steps:
[0118] Step 501: a first base station sends an MBS transmission progress request message to at least one second base station, where the MBS transmission progress request message is used to request reporting of an MBS transmission progress report.
[0119] In an optional embodiment, the type of the first base station and the second base station is gNB.
[0120] In the embodiment of the present application, a GTP tunnel is established between a core network element and at least two base stations (including a first base station and at least one second base station) for a certain MBS service. The core network element transmits MBS service data to at least two base stations through the GTP tunnel. Here, the GTP tunnel can be a shared GTP tunnel or a per UE GTP tunnel.
[0121] In the embodiment of the present application, the distributed control of the MBS transmission progress of each base station is achieved by exchanging MBS transmission progress reports between base stations.
[0122] For example: Refer to Figure 6 , one of base stations 1, base station 2, and base station 3 (referred to as the first base station) sends an MBS transmission progress request message to the other two base stations (referred to as the second base stations).
[0123] Here, the MBS transmission progress request message is also used to configure the second base station to send the information about the MBS service data transmission of the base station.
[0124] In the embodiment of the present application, the MBS transmission progress request message includes at least one of the following: a service identifier of the MBS service, and a reporting method of the MBS transmission progress report of the MBS service.
[0125] In the above solution, optionally, the service identifier of the MBS service includes at least one of the following: TMGI, G-RNTI, and MBS session identifier.
[0126] In the above solution, optionally, the reporting method of the MBS transmission progress report of the MBS service is a periodic reporting method, a one-time reporting method, or an event-triggered reporting method.
[0127] A) When the reporting mode of the MBS transmission progress report of the MBS service is the periodic reporting mode, the MBS transmission progress request message further includes: a reporting period of the periodic reporting mode.
[0128] B) When the reporting mode of the MBS transmission progress report of the MBS service is the event-triggered reporting mode, the MBS transmission progress request message further includes: an event type and / or a condition satisfied by the event.
[0129] In an optional manner, the event type is the number of MBS service data to be transmitted stored in the base station.
[0130] In an optional manner, the condition for the event to be satisfied is that the number of MBS service data to be transmitted stored in the base station is greater than or greater than or equal to a first threshold; or, the condition for the event to be satisfied is that the number of MBS service data to be transmitted stored in the base station is less than or less than or equal to a second threshold.
[0131] In an example, the reporting method of the MBS transmission progress report of the MBS service is the periodic reporting method, and the second base station periodically sends the MBS transmission progress report to the first base station according to the reporting period.
[0132] In an example, the reporting method of the MBS transmission progress report of the MBS service is the one-time reporting method. After receiving the MBS transmission progress request message, the second base station directly sends the MBS transmission progress report to the first base station.
[0133] In one example, the reporting method of the MBS transmission progress report of the MBS service is the event-triggered reporting method, and the event type is the number of MBS data to be transmitted stored in the base station, such as the number of PDCP SDUs; the condition satisfied by the event is that the number of MBS data to be transmitted stored in the base station is greater than or equal to N1, N1 is a positive integer, and if the number of PDCP SDUs to be transmitted stored in the second base station is greater than or equal to N1, the second base station is triggered to send the MBS transmission progress report to the first base station. The condition satisfied by the event can also be that the number of MBS data to be transmitted stored in the base station is less than or less than equal to N2, N2 is a positive integer, and if the number of PDCP SDUs to be transmitted stored in the second base station is less than or less than equal to N2, the second base station is triggered to send the MBS transmission progress report to the first base station. Optionally, N2 is less than N1.
[0134] Step 502: The first base station receives the MBS transmission progress report sent by the at least one second base station, and adjusts the progress of the MBS service data scheduled on the air interface based on the MBS transmission progress report sent by the at least one second base station.
[0135] In the embodiment of the present application, each of the at least one second base station sends an MBS transmission progress report to the first base station based on the MBS transmission progress request message.
[0136] For example: Refer to Figure 6, base station 2 and base station 3 send MBS transmission progress reports to base station 1 (base station 1 is the first base station). Similarly, base station 1 and base station 3 send MBS transmission progress reports to base station 2 (base station 2 is the first base station). Base station 1 and base station 2 send MBS transmission progress reports to base station 3 (base station 3 is the first base station).
[0137] In the embodiment of the present application, the content of the MBS transmission progress report sent by each base station in the at least one second base station may refer to the following description.
[0138] 1) Service identification of MBS service.
[0139] Here, the service identifier of the MBS service includes at least one of the following: TMGI, G-RNTI, MBS session identifier. The service identifier of the MBS service is used to indicate for which MBS service the MBS transmission progress report is for.
[0140] 2) The cell identifier of the cell where the MBS service is located.
[0141] 3) The number of MBS service data to be transmitted stored in the base station.
[0142] Here, the number of MBS service data to be transmitted stored in the base station is, for example, the number of PDCP SDUs to be transmitted stored in the base station.
[0143] 4) The sequence number (Series Number, SN) of the next MBS service data to be transmitted by the base station.
[0144] 5) The SN of the last MBS service data transmitted by the base station.
[0145] Corresponding to the above 4) and 5), optionally, the SN is a PDCP SN; or, the SN is an SN added by a core network element (such as AMF / UPF).
[0146] Further, optionally, when the reporting mode of the MBS transmission progress report is an event-triggered reporting mode, the MBS transmission progress report further includes at least one of the following: an event type triggering the MBS transmission progress report and a condition satisfied by the event.
[0147] In the above solution of the embodiment of the present application, the event type can be represented by an identifier (ID) of the event type, and the MBS transmission progress report only needs to carry the identifier of the event type.
[0148] In the embodiment of the present application, after receiving the MBS transmission progress report sent by at least one second base station, the first base station adjusts the progress of the MBS service data scheduled on the air interface based on the MBS transmission progress report sent by the at least one second base station.
[0149] In an optional manner, the first base station determines the number of MBS service data to be transmitted stored in the at least one second base station based on the MBS transmission progress report sent by the at least one second base station, and determines a first reference value based on the number of MBS service data to be transmitted stored in the at least one second base station; if the number of MBS service data to be transmitted stored in the first base station is greater than the first reference value, the progress of the MBS service data scheduled on the air interface is accelerated; if the number of MBS service data to be transmitted stored in the first base station is less than the first reference value, the progress of the MBS service data scheduled on the air interface is slowed down. Optionally, the first reference value is the average value of the number of MBS service data to be transmitted stored in the at least one second base station.
[0150] For example: the number of MBS service data to be transmitted stored in base station 1 is 14, the number of MBS service data to be transmitted stored in base station 2 is 7, and the number of MBS service data to be transmitted stored in base station 3 is 9. The first reference value is (7+9) / 2=8. Then, the MBS service transmission progress of base station 1 is slow, and base station 1 speeds up the progress of MBS service data scheduled on the air interface.
[0151] For example: the number of MBS service data to be transmitted stored in base station 1 is 5, the number of MBS service data to be transmitted stored in base station 2 is 7, and the number of MBS service data to be transmitted stored in base station 3 is 9. The first reference value is (7+9) / 2=8. Then, the MBS service transmission progress of base station 1 is faster, and base station 1 slows down the progress of MBS service data scheduled on the air interface.
[0152] In an optional manner, the first base station determines the number of MBS service data to be transmitted stored in the at least one second base station based on the MBS transmission progress report sent by the at least one second base station, and determines the second reference value based on the number of MBS service data to be transmitted stored in the first base station and the number of MBS service data to be transmitted stored in the at least one second base station; if the second reference value is greater than a third threshold, the progress of the MBS service data scheduled on the air interface is accelerated; if the second reference value is less than the third threshold, the progress of the MBS service data scheduled on the air interface is slowed down. Further, the second reference value is the difference between the number of MBS service data to be transmitted stored in the first base station and the first reference value, and the first reference value is determined based on the number of MBS service data to be transmitted stored in the at least one second base station. Optionally, the first reference value is the average value of the number of MBS service data to be transmitted stored in the at least one second base station.
[0153] For example: the number of MBS service data to be transmitted stored in base station 1 is 14, the number of MBS service data to be transmitted stored in base station 2 is 7, the number of MBS service data to be transmitted stored in base station 3 is 9, the first reference value is (7+9) / 2=8, the second reference value is 14-8=6, and the third threshold is 0 or 1. Then, if the second reference value is greater than the third threshold, the MBS service transmission progress of base station 1 is slow, and base station 1 speeds up the progress of MBS service data scheduled on the air interface.
[0154] For example: the number of MBS service data to be transmitted stored in base station 1 is 5, the number of MBS service data to be transmitted stored in base station 2 is 7, the number of MBS service data to be transmitted stored in base station 3 is 9, the first reference value is (7+9) / 2=8, the second reference value is 5-8=-3, and the third threshold is 0 or 1. Then, if the second reference value is less than the third threshold, the MBS service transmission progress of base station 1 is faster, and base station 1 slows down the progress of MBS service data scheduled on the air interface.
[0155] In the above solution of the embodiment of the present application, the MBS transmission progress request message is sent through the first XnAP signaling, and the MBS transmission progress report is sent through the second XnAP signaling.
[0156] The technical solution of the embodiment of the present application coordinates the MBS transmission progress between base stations to decide whether to speed up or slow down the MBS transmission progress of the base station, so that the MBS transmission progress between the base stations is as synchronized as possible, thereby minimizing the loss of MBS service data caused by the different MBS service transmission progress of the two base stations.
[0157] Figure 7The structure of the control device for MBS service transmission progress provided by the embodiment of the present application is shown in FIG. Figure 1 , applied to core network elements, such as Figure 7 As shown, the MBS service transmission progress control device includes:
[0158] A sending unit 701 is configured to send an MBS transmission progress request message to at least two base stations, where the MBS transmission progress request message is used to request reporting of an MBS transmission progress report;
[0159] The receiving unit 702 is configured to receive the MBS transmission progress reports sent by the at least two base stations;
[0160] The adjusting unit 703 is configured to adjust the progress of sending the MBS service data to the at least two base stations based on the MBS transmission progress reports sent by the at least two base stations.
[0161] In an optional manner, the MBS transmission progress request message includes at least one of the following: a service identifier of the MBS service, and a reporting method of an MBS transmission progress report of the MBS service.
[0162] In an optional manner, the reporting method of the MBS transmission progress report of the MBS service is a periodic reporting method, a one-time reporting method, or an event-triggered reporting method.
[0163] In an optional manner, when the reporting method of the MBS transmission progress report of the MBS service is the periodic reporting method,
[0164] The MBS transmission progress request message further includes: a reporting period of the periodic reporting method.
[0165] In an optional manner, when the reporting method of the MBS transmission progress report of the MBS service is the event-triggered reporting method,
[0166] The MBS transmission progress request message further includes: an event type and / or a condition satisfied by the event.
[0167] In an optional manner, the event type is the number of MBS service data to be transmitted stored in the base station.
[0168] In an optional manner, the condition satisfied by the event is that the number of MBS service data to be transmitted stored in the base station is greater than or equal to a first threshold; or,
[0169] The condition satisfied by the event is that the number of MBS service data to be transmitted stored in the base station is less than or equal to a second threshold.
[0170] In an optional manner, the MBS transmission progress report includes at least one of the following: a service identifier of the MBS service, a cell identifier of the cell where the MBS service is located, the number of MBS service data to be transmitted stored in the base station, the SN of the next MBS service data to be transmitted by the base station, and the SN of the last MBS service data transmitted by the base station.
[0171] In an optional manner, when the reporting mode of the MBS transmission progress report is an event-triggered reporting mode, the MBS transmission progress report further includes at least one of the following: the event type triggering the MBS transmission progress report and the condition satisfied by the event.
[0172] In an optional manner, the SN is a PDCP SN; or,
[0173] The SN is the SN added by the core network element.
[0174] In an optional manner, the MBS transmission progress request message is sent via a first NGAP signaling, and the MBS transmission progress report is sent via a second NGAP signaling; or,
[0175] The MBS transmission progress request message is sent via a first GTP-C signaling, and the MBS transmission progress report is sent via a second GTP-C signaling.
[0176] Those skilled in the art should understand that the relevant description of the above-mentioned MBS service transmission progress control device in the embodiment of the present application can be understood by referring to the relevant description of the MBS service transmission progress control method in the embodiment of the present application.
[0177] Figure 8 The structure of the control device for MBS service transmission progress provided by the embodiment of the present application is shown in FIG. Figure 2 , applied to the first base station, such as Figure 8 As shown, the MBS service transmission progress control device includes:
[0178] A sending unit 801 is configured to send an MBS transmission progress request message to at least one second base station, where the MBS transmission progress request message is used to request reporting of an MBS transmission progress report;
[0179] The receiving unit 802 is configured to receive an MBS transmission progress report sent by the at least one second base station;
[0180] The adjusting unit 803 is configured to adjust the progress of the MBS service data scheduled on the air interface based on the MBS transmission progress report sent by the at least one second base station.
[0181] In an optional manner, the MBS transmission progress request message includes at least one of the following: a service identifier of the MBS service, and a reporting method of an MBS transmission progress report of the MBS service.
[0182] In an optional manner, the reporting method of the MBS transmission progress report of the MBS service is a periodic reporting method, a one-time reporting method, or an event-triggered reporting method.
[0183] In an optional manner, when the reporting method of the MBS transmission progress report of the MBS service is the periodic reporting method,
[0184] The MBS transmission progress request message further includes: a reporting period of the periodic reporting method.
[0185] In an optional manner, when the reporting method of the MBS transmission progress report of the MBS service is the event-triggered reporting method,
[0186] The MBS transmission progress request message further includes: an event type and / or a condition satisfied by the event.
[0187] In an optional manner, the event type is the number of MBS service data to be transmitted stored in the base station.
[0188] In an optional manner, the condition satisfied by the event is that the number of MBS service data to be transmitted stored in the base station is greater than or equal to a first threshold; or,
[0189] The condition satisfied by the event is that the number of MBS service data to be transmitted stored in the base station is less than or equal to a second threshold.
[0190] In an optional manner, the MBS transmission progress report includes at least one of the following: a service identifier of the MBS service, a cell identifier of the cell where the MBS service is located, the number of MBS service data to be transmitted stored in the base station, the SN of the next MBS service data to be transmitted by the base station, and the SN of the last MBS service data transmitted by the base station.
[0191] In an optional manner, when the reporting mode of the MBS transmission progress report is an event-triggered reporting mode, the MBS transmission progress report further includes at least one of the following: the event type triggering the MBS transmission progress report and the condition satisfied by the event.
[0192] In an optional manner, the SN is a PDCP SN; or,
[0193] The SN is the SN added by the core network element.
[0194] In an optional manner, the adjustment unit 803 is used to determine the number of MBS service data to be transmitted stored in the at least one second base station based on the MBS transmission progress report sent by the at least one second base station, and determine a first reference value based on the number of MBS service data to be transmitted stored in the at least one second base station; if the number of MBS service data to be transmitted stored in the first base station is greater than the first reference value, the progress of the MBS service data scheduled on the air interface is accelerated; if the number of MBS service data to be transmitted stored in the first base station is less than the first reference value, the progress of the MBS service data scheduled on the air interface is slowed down.
[0195] In an optional manner, the adjustment unit 803 is used to determine the number of MBS service data to be transmitted stored in the at least one second base station based on the MBS transmission progress report sent by the at least one second base station, and determine a second reference value based on the number of MBS service data to be transmitted stored in the first base station and the number of MBS service data to be transmitted stored in the at least one second base station; if the second reference value is greater than a third threshold, the progress of the MBS service data scheduled on the air interface is accelerated; if the second reference value is less than the third threshold, the progress of the MBS service data scheduled on the air interface is slowed down.
[0196] In an optional manner, the second reference value is the difference between the number of MBS service data to be transmitted stored in the first base station and the first reference value, and the first reference value is determined based on the number of MBS service data to be transmitted stored in the at least one second base station.
[0197] In an optional manner, the first reference value is an average value of the number of MBS service data to be transmitted stored in the at least one second base station.
[0198] In an optional manner, the MBS transmission progress request message is sent via a first XnAP signaling, and the MBS transmission progress report is sent via a second XnAP signaling.
[0199] Those skilled in the art should understand that the relevant description of the above-mentioned MBS service transmission progress control device in the embodiment of the present application can be understood by referring to the relevant description of the MBS service transmission progress control method in the embodiment of the present application.
[0200] Fig. 9 900 is a schematic structural diagram of a communication device provided in an embodiment of the present application. The communication device may be a base station or a core network element. Fig. 9 The communication device 900 shown includes a processor 910, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.
[0201] Alternatively, if Fig. 9 As shown, the communication device 900 may further include a memory 920. The processor 910 may call and run a computer program from the memory 920 to implement the method in the embodiment of the present application.
[0202] The memory 920 may be a separate device independent of the processor 910 , or may be integrated into the processor 910 .
[0203] Alternatively, if Fig. 9 As shown, the communication device 900 may further include a transceiver 930, and the processor 910 may control the transceiver 930 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.
[0204] The transceiver 930 may include a transmitter and a receiver. The transceiver 930 may further include an antenna, and the number of antennas may be one or more.
[0205] Optionally, the communication device 900 may specifically be the first base station of the embodiment of the present application, and the communication device 900 may implement the corresponding processes implemented by the first base station in each method of the embodiment of the present application, which will not be described again for the sake of brevity.
[0206] Optionally, the communication device 900 may specifically be a core network element of an embodiment of the present application, and the communication device 900 may implement the corresponding processes implemented by the core network element in each method of the embodiment of the present application, which will not be described again for the sake of brevity.
[0207] Fig.10 It is a schematic structural diagram of the chip of an embodiment of the present application. Fig.10 The chip 1000 shown includes a processor 1010, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.
[0208] Alternatively, if Fig.10 As shown, the chip 1000 may further include a memory 1020. The processor 1010 may call and run a computer program from the memory 1020 to implement the method in the embodiment of the present application.
[0209] The memory 1020 may be a separate device independent of the processor 1010 , or may be integrated into the processor 1010 .
[0210] Optionally, the chip 1000 may further include an input interface 1030. The processor 1010 may control the input interface 1030 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.
[0211] Optionally, the chip 1000 may further include an output interface 1040. The processor 1010 may control the output interface 1040 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.
[0212] Optionally, the chip can be applied to the first base station in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the first base station in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.
[0213] Optionally, the chip can be applied to the core network network element in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the core network network element in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.
[0214] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.
[0215] It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by the hardware integrated logic circuit or software instructions in the processor. The above processor can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor are combined and performed. The software module can be located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, and other mature storage media in the art. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
[0216] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.
[0217] It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiments of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.
[0218] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.
[0219] Optionally, the computer-readable storage medium can be applied to the first base station in the embodiment of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the first base station in the various methods of the embodiment of the present application. For the sake of brevity, they are not repeated here.
[0220] Optionally, the computer-readable storage medium can be applied to the core network network elements in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the core network network elements in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.
[0221] An embodiment of the present application also provides a computer program product, including computer program instructions.
[0222] Optionally, the computer program product can be applied to the first base station in the embodiment of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the first base station in the various methods of the embodiment of the present application. For the sake of brevity, they are not repeated here.
[0223] Optionally, the computer program product can be applied to the core network network elements in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the core network network elements in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.
[0224] The embodiment of the present application also provides a computer program.
[0225] Optionally, the computer program can be applied to the first base station in the embodiment of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the first base station in the various methods in the embodiment of the present application. For the sake of brevity, they are not repeated here.
[0226] Optionally, the computer program can be applied to the core network network elements in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the core network network elements in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.
[0227] 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.
[0228] 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.
[0229] In the several embodiments provided in the present application, it should be understood that 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 the units is only a logical function division. There may be other division methods in actual implementation, such as 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.
[0230] 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.
[0231] 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.
[0232] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution 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 described in 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 read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
[0233] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.
Claims
1. A method for controlling the transmission progress of a multimedia multicast service (MBS) service, the method comprising: The core network element sends an MBS transmission progress request message to at least two base stations, where the MBS transmission progress request message is used to request reporting of an MBS transmission progress report; The core network element receives the MBS transmission progress reports sent by the at least two base stations, and adjusts the progress of sending the MBS service data to the at least two base stations based on the MBS transmission progress reports sent by the at least two base stations.
2. The method according to claim 1, wherein: The MBS transmission progress request message includes at least one of the following: a service identifier of the MBS service, and a reporting method of an MBS transmission progress report of the MBS service.
3. The method according to claim 2, wherein: The reporting method of the MBS transmission progress report of the MBS service is a periodic reporting method, a one-time reporting method, or an event-triggered reporting method.
4. The method according to claim 3, wherein: When the reporting method of the MBS transmission progress report of the MBS service is the periodic reporting method, The MBS transmission progress request message further includes: a reporting period of the periodic reporting method.
5. The method according to claim 3, wherein: When the reporting method of the MBS transmission progress report of the MBS service is the event-triggered reporting method, The MBS transmission progress request message further includes: an event type and / or a condition satisfied by the event.
6. The method according to claim 5, wherein: The event type is the number of MBS service data to be transmitted stored in the base station.
7. The method according to claim 5 or 6, wherein: The condition satisfied by the event is that the number of MBS service data to be transmitted stored in the base station is greater than or equal to a first threshold; or, The condition satisfied by the event is that the number of MBS service data to be transmitted stored in the base station is less than or equal to a second threshold.
8. The method according to any one of claims 1 to 6, wherein: The MBS transmission progress report includes at least one of the following: the service identifier of the MBS service, the cell identifier of the cell where the MBS service is located, the number of MBS service data to be transmitted stored in the base station, the sequence number SN of the next MBS service data to be transmitted by the base station, and the SN of the last MBS service data transmitted by the base station.
9. The method according to claim 8, wherein: When the reporting mode of the MBS transmission progress report is an event-triggered reporting mode, the MBS transmission progress report further includes at least one of the following: an event type triggering the MBS transmission progress report and a condition satisfied by the event.
10. The method according to claim 8, wherein: The SN is a Packet Data Convergence Protocol (PDCP) SN; or, The SN is the SN added by the core network element.
11. The method according to any one of claims 1 to 6, 9 and 10, wherein: The MBS transmission progress request message is sent via a first NGAP signaling, and the MBS transmission progress report is sent via a second NGAP signaling; or, The MBS transmission progress request message is sent via a first GTP-C signaling, and the MBS transmission progress report is sent via a second GTP-C signaling.
12. A method for controlling MBS service transmission progress, the method comprising: The first base station sends an MBS transmission progress request message to at least one second base station, where the MBS transmission progress request message is used to request reporting of an MBS transmission progress report; The first base station receives the MBS transmission progress report sent by the at least one second base station, and adjusts the progress of the MBS service data scheduled on the air interface based on the MBS transmission progress report sent by the at least one second base station.
13. The method according to claim 12, wherein: The MBS transmission progress request message includes at least one of the following: a service identifier of the MBS service, and a reporting method of an MBS transmission progress report of the MBS service.
14. The method according to claim 13, wherein: The reporting method of the MBS transmission progress report of the MBS service is a periodic reporting method, a one-time reporting method, or an event-triggered reporting method.
15. The method according to claim 14, wherein: When the reporting method of the MBS transmission progress report of the MBS service is the periodic reporting method, The MBS transmission progress request message further includes: a reporting period of the periodic reporting method.
16. The method according to claim 14, wherein: When the reporting method of the MBS transmission progress report of the MBS service is the event-triggered reporting method, The MBS transmission progress request message further includes: an event type and / or a condition satisfied by the event.
17. The method according to claim 16, wherein: The event type is the number of MBS service data to be transmitted stored in the base station.
18. The method according to claim 16 or 17, wherein: The condition satisfied by the event is that the number of MBS service data to be transmitted stored in the base station is greater than or equal to a first threshold; or, The condition satisfied by the event is that the number of MBS service data to be transmitted stored in the base station is less than or equal to a second threshold.
19. The method according to any one of claims 12 to 17, wherein: The MBS transmission progress report includes at least one of the following: the service identifier of the MBS service, the cell identifier of the cell where the MBS service is located, the number of MBS service data to be transmitted stored in the base station, the SN of the next MBS service data to be transmitted by the base station, and the SN of the last MBS service data transmitted by the base station.
20. The method according to claim 19, wherein: When the reporting mode of the MBS transmission progress report is an event-triggered reporting mode, the MBS transmission progress report further includes at least one of the following: an event type triggering the MBS transmission progress report and a condition satisfied by the event.
21. The method according to claim 20, wherein: The SN is a PDCP SN; or, The SN is the SN added by the core network element.
22. The method according to any one of claims 12 to 17, 20 and 21, wherein: The adjusting the progress of the MBS service data scheduled on the air interface based on the MBS transmission progress report sent by the at least one second base station includes: The first base station determines, based on the MBS transmission progress report sent by the at least one second base station, the number of MBS service data to be transmitted stored in the at least one second base station, and determines a first reference value based on the number of MBS service data to be transmitted stored in the at least one second base station; If the number of MBS service data to be transmitted stored in the first base station is greater than the first reference value, the progress of the MBS service data scheduled on the air interface is accelerated; if the number of MBS service data to be transmitted stored in the first base station is less than the first reference value, the progress of the MBS service data scheduled on the air interface is slowed down.
23. The method according to any one of claims 12 to 17, 20, and 21, wherein: The adjusting the progress of the MBS service data scheduled on the air interface based on the MBS transmission progress report sent by the at least one second base station includes: The first base station determines, based on the MBS transmission progress report sent by the at least one second base station, the number of MBS service data to be transmitted stored in the at least one second base station, and determines a second reference value based on the number of MBS service data to be transmitted stored in the first base station and the number of MBS service data to be transmitted stored in the at least one second base station; If the second reference value is greater than the third threshold, the progress of the MBS service data scheduled on the air interface is accelerated; if the second reference value is less than the third threshold, the progress of the MBS service data scheduled on the air interface is slowed down.
24. The method according to claim 23, wherein: The second reference value is a difference between the number of MBS service data to be transmitted stored in the first base station and a first reference value, and the first reference value is determined based on the number of MBS service data to be transmitted stored in the at least one second base station.
25. The method according to claim 24, wherein: The first reference value is an average value of the number of MBS service data to be transmitted and stored in the at least one second base station.
26. The method according to any one of claims 12 to 17, 20, 21, 24, 25, wherein: The MBS transmission progress request message is sent via a first XnAP signaling, and the MBS transmission progress report is sent via a second XnAP signaling.
27. A device for controlling MBS service transmission progress, applied to a core network element, the device comprising: A sending unit, configured to send an MBS transmission progress request message to at least two base stations, wherein the MBS transmission progress request message is used to request reporting of an MBS transmission progress report; A receiving unit, configured to receive the MBS transmission progress reports sent by the at least two base stations; An adjusting unit is used to adjust the progress of MBS service data sent to the at least two base stations based on the MBS transmission progress reports sent by the at least two base stations.
28. The device according to claim 27, wherein The MBS transmission progress request message includes at least one of the following: a service identifier of the MBS service, and a reporting method of an MBS transmission progress report of the MBS service.
29. The device according to claim 28, wherein The reporting method of the MBS transmission progress report of the MBS service is a periodic reporting method, a one-time reporting method, or an event-triggered reporting method.
30. The device according to claim 29, wherein: When the reporting method of the MBS transmission progress report of the MBS service is the periodic reporting method, The MBS transmission progress request message further includes: a reporting period of the periodic reporting method.
31. The device according to claim 29, wherein: When the reporting method of the MBS transmission progress report of the MBS service is the event-triggered reporting method, The MBS transmission progress request message further includes: an event type and / or a condition satisfied by the event.
32. The device according to claim 31, wherein The event type is the number of MBS service data to be transmitted stored in the base station.
33. The device according to claim 31 or 32, wherein: The condition satisfied by the event is that the number of MBS service data to be transmitted stored in the base station is greater than or equal to a first threshold; or, The condition satisfied by the event is that the number of MBS service data to be transmitted stored in the base station is less than or equal to a second threshold.
34. The device according to any one of claims 27 to 32, wherein: The MBS transmission progress report includes at least one of the following: the service identifier of the MBS service, the cell identifier of the cell where the MBS service is located, the number of MBS service data to be transmitted stored in the base station, the SN of the next MBS service data to be transmitted by the base station, and the SN of the last MBS service data transmitted by the base station.
35. The device according to claim 34, wherein When the reporting mode of the MBS transmission progress report is an event-triggered reporting mode, the MBS transmission progress report further includes at least one of the following: an event type triggering the MBS transmission progress report and a condition satisfied by the event.
36. The device according to claim 34, wherein The SN is a PDCP SN; or, The SN is the SN added by the core network element.
37. The device according to any one of claims 27 to 32, 35 and 36, wherein: The MBS transmission progress request message is sent via a first NGAP signaling, and the MBS transmission progress report is sent via a second NGAP signaling; or, The MBS transmission progress request message is sent via a first GTP-C signaling, and the MBS transmission progress report is sent via a second GTP-C signaling.
38. A device for controlling MBS service transmission progress, applied to a first base station, the device comprising: a sending unit, configured to send an MBS transmission progress request message to at least one second base station, wherein the MBS transmission progress request message is used to request reporting of an MBS transmission progress report; A receiving unit, configured to receive an MBS transmission progress report sent by the at least one second base station; An adjusting unit is used to adjust the progress of MBS service data scheduled on the air interface based on the MBS transmission progress report sent by the at least one second base station.
39. The device according to claim 38, wherein The MBS transmission progress request message includes at least one of the following: a service identifier of the MBS service, and a reporting method of an MBS transmission progress report of the MBS service.
40. The device according to claim 39, wherein The reporting method of the MBS transmission progress report of the MBS service is a periodic reporting method, a one-time reporting method, or an event-triggered reporting method.
41. The device according to claim 40, wherein When the reporting method of the MBS transmission progress report of the MBS service is the periodic reporting method, The MBS transmission progress request message further includes: a reporting period of the periodic reporting method.
42. The device according to claim 40, wherein: When the reporting method of the MBS transmission progress report of the MBS service is the event-triggered reporting method, The MBS transmission progress request message further includes: an event type and / or a condition satisfied by the event.
43. The device according to claim 42, wherein: The event type is the number of MBS service data to be transmitted stored in the base station.
44. The device according to claim 42 or 43, wherein: The condition satisfied by the event is that the number of MBS service data to be transmitted stored in the base station is greater than or equal to a first threshold; or, The condition satisfied by the event is that the number of MBS service data to be transmitted stored in the base station is less than or equal to a second threshold.
45. The device according to any one of claims 38 to 43, wherein: The MBS transmission progress report includes at least one of the following: the service identifier of the MBS service, the cell identifier of the cell where the MBS service is located, the number of MBS service data to be transmitted stored in the base station, the SN of the next MBS service data to be transmitted by the base station, and the SN of the last MBS service data transmitted by the base station.
46. The device according to claim 45, wherein When the reporting mode of the MBS transmission progress report is an event-triggered reporting mode, the MBS transmission progress report further includes at least one of the following: an event type triggering the MBS transmission progress report and a condition satisfied by the event.
47. The device according to claim 46, wherein The SN is a PDCP SN; or, The SN is the SN added by the core network element.
48. The device according to any one of claims 38 to 43, 46 and 47, wherein: The adjusting unit is configured to determine the number of MBS service data to be transmitted stored in the at least one second base station based on the MBS transmission progress report sent by the at least one second base station, and determine the first reference value based on the number of MBS service data to be transmitted stored in the at least one second base station; If the number of MBS service data to be transmitted stored in the first base station is greater than the first reference value, the progress of the MBS service data scheduled on the air interface is accelerated; if the number of MBS service data to be transmitted stored in the first base station is less than the first reference value, the progress of the MBS service data scheduled on the air interface is slowed down.
49. The device according to any one of claims 38 to 43, 46 and 47, wherein: The adjusting unit is configured to determine the number of MBS service data to be transmitted stored in the at least one second base station based on the MBS transmission progress report sent by the at least one second base station, and determine the second reference value based on the number of MBS service data to be transmitted stored in the first base station and the number of MBS service data to be transmitted stored in the at least one second base station; If the second reference value is greater than the third threshold, the progress of the MBS service data scheduled on the air interface is accelerated; if the second reference value is less than the third threshold, the progress of the MBS service data scheduled on the air interface is slowed down.
50. The apparatus of claim 49, wherein: The second reference value is a difference between the number of MBS service data to be transmitted stored in the first base station and a first reference value, and the first reference value is determined based on the number of MBS service data to be transmitted stored in the at least one second base station.
51. The apparatus of claim 50, wherein: The first reference value is an average value of the number of MBS service data to be transmitted and stored in the at least one second base station.
52. The device according to any one of claims 38 to 43, 46, 47, 50, 51, wherein: The MBS transmission progress request message is sent via a first XnAP signaling, and the MBS transmission progress report is sent via a second XnAP signaling.
53. A communication device comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method as claimed in any one of claims 1 to 11, or the method as claimed in any one of claims 12 to 26.
54. A chip, comprising: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 11, or a method as claimed in any one of claims 12 to 26.
55. A computer-readable storage medium for storing a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 11, or the method according to any one of claims 12 to 26.
Citation Information
Patent Citations
Method, system and equipment for realizing synchronization of multicast / broadcast service (MBS) of multi-hop system
CN101742409A
Apparatus for and method of multicast and broadcast service (MBS) macro-diversity based information processing
US20090219849A1