WO2022068679A1 - 广播多播业务的拥塞控制方法、装置和设备 - Google Patents

广播多播业务的拥塞控制方法、装置和设备 Download PDF

Info

Publication number
WO2022068679A1
WO2022068679A1 PCT/CN2021/120143 CN2021120143W WO2022068679A1 WO 2022068679 A1 WO2022068679 A1 WO 2022068679A1 CN 2021120143 W CN2021120143 W CN 2021120143W WO 2022068679 A1 WO2022068679 A1 WO 2022068679A1
Authority
WO
WIPO (PCT)
Prior art keywords
broadcast multicast
multicast service
terminal device
broadcast
access
Prior art date
Application number
PCT/CN2021/120143
Other languages
English (en)
French (fr)
Inventor
钟婷婷
吴昱民
刘佳敏
Original Assignee
维沃移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Publication of WO2022068679A1 publication Critical patent/WO2022068679A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast

Definitions

  • the present application relates to the field of communications, and in particular, to a method, apparatus and device for congestion control of broadcast multicast services.
  • UE User Equipment
  • RRC dedicated signaling dedicated signaling
  • PTP point-to-point
  • RAN Radio Access Network
  • Embodiments of the present application provide a method, device, and device for congestion control of broadcast multicast services, so as to solve the problem that random access procedures are easily caused when the number of UEs in a non-RRC connection state that requires broadcast multicast services is large. cause congestion problems.
  • a method for congestion control of a broadcast multicast service is provided, which is applied to a terminal device.
  • the method includes: performing congestion control on the broadcast multicast service in a first process; wherein the first process includes: : a second process and a random access process at the MAC layer of the medium access control, the second process includes at least one of a radio resource control RRC connection establishment process and an RRC connection recovery process.
  • a device for congestion control of broadcast multicast service which is applied to terminal equipment, the device includes: a control module configured to perform congestion control on broadcast multicast service in a first process;
  • the first process includes: a second process and a random access process of the medium access control MAC layer, the second process includes at least one of a radio resource control RRC connection establishment process and an RRC connection recovery process.
  • a terminal device including: a memory, a processor, and a program or instruction stored on the memory and executable on the processor, when the program or instruction is executed by the processor.
  • a method for controlling congestion of broadcast multicast services is provided, which is applied to a network side device.
  • the method includes: receiving a request corresponding to a first process sent by a terminal device, where the first process is used for the The terminal device performs congestion control on the broadcast multicast service; wherein, the first process includes: a second process and a random access process at the MAC layer of medium access control, and the second process includes a radio resource control RRC connection establishment process and at least one of the RRC connection recovery procedures.
  • a fifth aspect provides a congestion control apparatus for a broadcast multicast service, which is applied to a network side device, the apparatus includes: a receiving module, configured to receive a request corresponding to a first process sent by a terminal device, the first process It is used for the terminal device to perform congestion control on broadcast multicast services; wherein the first process includes: a second process and a random access process at the MAC layer of medium access control, and the second process includes radio resources At least one of the RRC connection establishment procedure and the RRC connection recovery procedure is controlled.
  • a sixth aspect provides a network side device, including: a memory, a processor, and a program or instruction stored on the memory and executable on the processor, when the program or instruction is executed by the processor.
  • a readable storage medium is provided, and a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the congestion control of the broadcast multicast service according to the first aspect is implemented
  • a computer program product is provided, the computer program product is stored in a non-volatile readable storage medium, and when the computer program product is executed by a processor, the broadcast multicast service according to the first aspect is implemented The steps of the congestion control method, or the steps of implementing the congestion control method of the broadcast multicast service according to the fourth aspect when the program or instruction is executed by the processor.
  • a chip in a ninth aspect, includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a terminal device or a network side device program or instruction, to achieve the The steps of the method for congestion control of the broadcast multicast service described in one aspect, or the steps of implementing the method for congestion control of the broadcast multicast service described in the fourth aspect.
  • the congestion control of the broadcast multicast service may be implemented in at least one of the second process and the random access process of the MAC layer of the medium access control, where the second process includes the radio resource control RRC connection At least one of the establishment procedure and the RRC connection recovery procedure.
  • the congestion control process for the broadcast multicast service may be added to at least one or more of the RRC connection establishment process, the RRC connection recovery process and the random access process of the MAC layer, it is possible to reduce the demand for the broadcast multicast service.
  • the number of terminal devices in the non-RRC connection state is relatively large, which leads to the probability of congestion in the random access process, thereby improving the system performance.
  • FIG. 1 shows a block diagram of a wireless communication system to which an embodiment of the present application can be applied
  • FIG. 2 is a schematic flowchart of a method for congestion control of a broadcast multicast service in an embodiment of the present application
  • FIG. 3 is a schematic flowchart of another congestion control method for a broadcast multicast service in an embodiment of the present application
  • FIG. 4 is a schematic structural diagram of a congestion control device for a broadcast multicast service in an embodiment of the present application
  • FIG. 5 is a schematic structural diagram of another congestion control apparatus for a broadcast multicast service in an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a communication device in an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a terminal device in an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a network side device in an embodiment of the present application.
  • first, second and the like in the description and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It is to be understood that the data so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in sequences other than those illustrated or described herein, and "first”, “second” distinguishes Usually it is a class, and the number of objects is not limited.
  • the first object may be one or multiple.
  • “and/or” in the description and claims indicates at least one of the connected objects, and the character “/" generally indicates that the associated objects are in an "or” relationship.
  • LTE Long Term Evolution
  • LTE-Advanced LTE-Advanced
  • LTE-A Long Term Evolution-Advanced
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency-Division Multiple Access
  • system and “network” in the embodiments of the present application are often used interchangeably, and the described technology can be used not only for the above-mentioned systems and radio technologies, but also for other systems and radio technologies.
  • NR New Radio
  • the following description describes a New Radio (NR) system for example purposes, and uses NR terminology in most of the following description, these techniques can also be applied to applications other than NR system applications, such as the 6th generation (6th generation ). Generation, 6G) communication system.
  • 6th generation 6th generation
  • FIG. 1 shows a block diagram of a wireless communication system to which the embodiments of the present application can be applied.
  • the wireless communication system includes a terminal 11 and a network-side device 12 .
  • the terminal 11 may also be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital computer Assistant (Personal Digital Assistant, PDA), handheld computer, netbook, ultra-mobile personal computer (ultra-mobile personal computer, UMPC), mobile Internet device (Mobile Internet Device, MID), wearable device (Wearable Device) or vehicle-mounted device (Vehicle UE, VUE), pedestrian terminal (Pedestrian UE, PUE) and other terminal-side devices, wearable devices include: bracelets, headphones, glasses, etc.
  • the network side device 12 may be a base station or a core network, wherein the base station may be referred to as a Node B, an evolved Node B, an access point, a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a basic service Set (Basic Service Set, BSS), Extended Service Set (Extended Service Set, ESS), Node B, Evolved Node B (eNB), Home Node B, Home Evolved Node B, WLAN Access Point, WiFi Node, Send Transmitting Receiving Point (TRP) or some other suitable term in the field, as long as the same technical effect is achieved, the base station is not limited to a specific technical vocabulary. It should be noted that in the embodiment of this application, only the NR system is used. The base station in the example is taken as an example, but the specific type of the base station is not limited.
  • an embodiment of the present application provides a method for controlling congestion of a broadcast multicast service, which is executed by a terminal device, and the method includes the following process steps:
  • Step 201 Perform congestion control on the broadcast multicast service in the first process; wherein, the first process includes: the second process and the random access process of the medium access control (Medium Access Control, MAC) layer, so The second process includes at least one of a radio resource control RRC connection establishment process and an RRC connection recovery process.
  • the first process includes: the second process and the random access process of the medium access control (Medium Access Control, MAC) layer, so The second process includes at least one of a radio resource control RRC connection establishment process and an RRC connection recovery process.
  • the first process includes: the second process and the random access process of the medium access control (Medium Access Control, MAC) layer
  • the second process includes at least one of a radio resource control RRC connection establishment process and an RRC connection recovery process.
  • the congestion control of the broadcast multicast service may be implemented in at least one of the second process and the random access process of the MAC layer of the medium access control, where the second process includes the radio resource control RRC connection At least one of the establishment procedure and the RRC connection recovery procedure.
  • the congestion control process for the broadcast multicast service may be added to at least one or more of the RRC connection establishment process, the RRC connection recovery process and the random access process of the MAC layer, it is possible to reduce the demand for the broadcast multicast service.
  • the number of terminal devices in the non-RRC connection state is relatively large, which leads to the probability of congestion in the random access process, thereby improving the system performance.
  • the terminal device when the first process is an RRC connection establishment (RRC connection establishment) process, the terminal device corresponds to an idle state (idle), and the terminal device may be called an IDLE UE; when the first process is RRC connection recovery ( During the RRC connection resume) process, the terminal device is correspondingly in an inactive state (Inactive), and the terminal device may be called an Inactive UE.
  • RRC connection establishment RRC connection establishment
  • IDLE UE idle state
  • the terminal device when the first process is RRC connection recovery ( During the RRC connection resume) process, the terminal device is correspondingly in an inactive state (Inactive), and the terminal device may be called an Inactive UE.
  • a condition for the terminal device to initiate the second process includes at least one of the following:
  • the first condition when the terminal device performs a broadcast multicast service session join procedure (such as MBS join procedure).
  • the first condition includes at least one of the following.
  • the terminal device receives broadcast multicast service information; for example, USD (user service description) in LTE.
  • USD user service description
  • the terminal device is interested in at least one broadcast multicast service corresponding to the broadcast multicast service information.
  • the upper layers request the establishment of an RRC connection; it is mainly applicable to terminal equipment in an idle state.
  • the upper layer requests the recovery of the RRC connection; it is mainly applicable to the terminal equipment in the inactive state.
  • the terminal device has broadcast multicast service capability.
  • the network side equipment supports broadcast multicast services; for example, supports including an indication that it supports broadcast multicast services in system messages.
  • the terminal device receives a session start notification sent by the network side device; for example, Session Start command, group paging (group paging), paging message with Group Paging Identity (TMGI), etc.
  • a session start notification sent by the network side device; for example, Session Start command, group paging (group paging), paging message with Group Paging Identity (TMGI), etc.
  • the terminal device receives the control information of the broadcast multicast service sent by the network side device; for example, the LTE system information block (System Information Block, SIB15), SIB20, etc.
  • the LTE system information block System Information Block, SIB15
  • SIB20 SIB20
  • the second condition when the terminal device performs the reception of the broadcast multicast service data after the broadcast multicast service session joining process is completed.
  • the broadcast multicast service data when received after the broadcast multicast service session joining process is completed, it refers to, for example, acquiring MBS scheduling information, MBS configuration information (such as scptmConfiguration similar to LTE), and MBS service continuity related information.
  • information such as the content in SIB15 SIB20 similar to LTE
  • the second condition includes at least one of the following.
  • the terminal device receives the session start notification sent by the network side device; for example, Session Start command, group paging, paging message with Group Paging Identity (TMGI), etc.
  • Session Start command for example, Session Start command, group paging, paging message with Group Paging Identity (TMGI), etc.
  • TMGI Group Paging Identity
  • the terminal equipment has the capability of broadcast multicast service.
  • the network side equipment supports broadcast multicast services; for example, SIB15 and SIB20 of LTE.
  • the limitation for the unified access control (Unified Access Control, UAC) part can be applied to the following specific implementation. one of the examples.
  • the unified access control UAC process is not performed.
  • the congestion control method for the broadcast multicast service in this embodiment of the present application may further include at least one of the following contents.
  • the non-access stratum (Non-access stratum, NAS) layer or the RRC layer of the terminal device determines the corresponding access control Type of access.
  • the RRC layer of the terminal device determines and sets the access type corresponding to the access control.
  • the value of the parameter corresponding to the access control includes at least one of the following.
  • a first value can be understood as an existing value of a parameter corresponding to the access control of the broadcast multicast service.
  • the value of the parameter corresponding to the access control includes at least one of the value of the access category (Access category) and the value of the access identification (Access identity)
  • the first value may include: the value of Access identity is set to 0, and the value of Access category is set to 7 (ie, the data mo-Data is sent).
  • a second value different from the first value can be understood as a new value of a parameter corresponding to the access control of the broadcast multicast service, which is different from the existing first value.
  • the second value is at least one of the following.
  • Different broadcast multicast services have the same access type and/or access identification value.
  • Access identity is set to 0, and Access identity is set to 0.
  • category is set to 13 (mt-MBSaccess); in another example, Access identity is set to 16, and Access category is set to 7 (mo-Data); in yet another example, Access identity is set to 16, and Access category is set to 13 (mt-MBSaccess).
  • the second value distinguishes specific broadcast multicast services, and different broadcast multicast services have different access types and/or access identification values.
  • each broadcast multicast service group contains one or more broadcast multicast services); that is, the second value distinguishes specific broadcast multicast service groups, and different broadcast multicast service groups have different The value of access category and/or access identification.
  • the method may further include the following content: performing access control for the broadcast multicast service.
  • the access control to the broadcast multicast service is performed.
  • the access control of the broadcast multicast service and the UAC may have a certain relationship, including at least one of the following.
  • the terminal device When the terminal device does not perform the UAC procedure, it can immediately perform access control to the broadcast multicast service. (2) When the terminal device performs the UAC procedure, if the UAC procedure access attempt is prohibited, the access control to the broadcast multicast service is no longer performed; and if the UAC procedure access attempt is allowed, the broadcast multicast service is immediately executed. access control for broadcast services.
  • the method for congestion control of the broadcast multicast service may further include the following content.
  • the value of the first random number is used for the terminal device to perform access control to the broadcast multicast service; when the value of the first random number is lower than the first threshold value In the case of , the access attempt is considered to be prohibited, otherwise, the access attempt is considered to be allowed.
  • the name of the first random number is at least one of the following.
  • the name of the first random number distinguishes specific broadcast multicast services, and different broadcast multicast services have different names of random numbers.
  • TMGI or IP multicast address or application server address+IP multicast address and other methods for identifying broadcast multicast services
  • each broadcast multicast service group contains one or more broadcast multicast service settings; that is, the name of the first random number distinguishes a specific broadcast multicast service group, and different broadcast multicast service groups have The name of a different random number.
  • the above-mentioned first threshold value can be configured by the network side device, that is, the method can also include the following content:
  • the first threshold value configured by the network side device is received.
  • the above-mentioned first threshold value is at least one of the following.
  • Threshold value applicable to all broadcast multicast services That is to say, the first threshold value does not distinguish specific broadcast multicast services, and different broadcast multicast services have the same threshold value, such as MBSac-BarringFactor.
  • Threshold value set individually based on each broadcast multicast service. That is to say, the first threshold value distinguishes specific broadcast multicast services, and different broadcast multicast services have different threshold values.
  • the threshold value is IPTVac-BarringFactor; in another example, for the broadcast multicast service of public safety, the threshold value is Public safety-BarringFactor; in another example
  • TMGI or IP multicast address or application server address+IP multicast address and other methods for identifying broadcast multicast services
  • each broadcast multicast service group includes one or more broadcast multicast service settings; that is, the first threshold value distinguishes specific broadcast multicast service groups, and different broadcast multicast service groups have different threshold value.
  • the congestion control method of the broadcast multicast service when the value of the first random number is lower than the first threshold value, that is, it is considered that the access attempt is prohibited, the The method may also include the following.
  • the value of the random number is selected again (optional), and the first access control timer is started; after the first access control timer expires, it is considered that the access barring of the access attempt is relieved.
  • the above-mentioned first access control timer may be configured by a network-side device, that is, the method may further include the following content: receiving The first access control timer configured by the network side device.
  • the name of the above-mentioned first access control timer is at least one of the following.
  • the name of the first access control timer distinguishes specific broadcast multicast services, and different broadcast multicast services have different timer names.
  • This broadcast multicast service the name of the timer is T390c.
  • each broadcast multicast service group contains one or more broadcast multicast service settings; that is, the name of the first access control timer distinguishes a specific broadcast multicast service group from different broadcast multicast service groups.
  • Service groups have different timer names.
  • the timing duration calculation formula corresponding to the first access control timer is related to at least one of the following: the value of the first random number; and the value of the backoff time configured by the network side device.
  • the calculation formula when the timing duration calculation formula corresponding to the first access control timer is related to the value of the first random number, the calculation formula may be expressed as: (0.7+0.6*value of the random number). Wherein, if the UE performs multiple selections of random numbers, the latest value of the random number is used in the formula.
  • the timing duration calculation formula corresponding to the first access control timer is related to the value of the first random number and the value of the backoff time
  • the calculation formula can be expressed as: (0.7+0.6*random number value) * the value of the fallback time.
  • the formula for calculating the timing duration is at least one of the following.
  • the timing duration calculation formula distinguishes specific broadcast multicast services, and different broadcast multicast services have different calculation formulas.
  • This broadcast multicast service the calculation formula 3.
  • each broadcast multicast service group contains one or more broadcast multicast service settings; that is, the timing duration calculation formula distinguishes specific broadcast multicast service groups, and different broadcast multicast service groups have different calculation formula.
  • the calculation formula is formula 4.
  • the value of the above-mentioned backoff time may be configured by a network side device, that is, the method may further include the following content: receiving the network side The value of the configured fallback time.
  • the value of the aforementioned fallback time is at least one of the following.
  • each broadcast multicast service group contains one or more broadcast multicast service settings; that is to say, the value of the backoff time distinguishes specific broadcast multicast service groups, and different broadcast multicast service groups have different fallback time.
  • the method further includes: in the case that the UAC process access attempt is prohibited, The access control to the broadcast multicast service is no longer performed; in the case that the UAC procedure access attempt is allowed, the access control to the broadcast multicast service is performed immediately.
  • Specific embodiments of the access control to the broadcast multicast service associated with the UAC process include but are not limited to the following embodiments:
  • the terminal device performs congestion control on the broadcast multicast service in the above-mentioned first process, and performs the UAC process; further, in the case that the access attempt of the UAC process is prohibited, it is no longer performed. Access control to the broadcast multicast service; when the UAC procedure access attempt is allowed, the access control to the broadcast multicast service is performed immediately.
  • the terminal device performs congestion control on the broadcast multicast service in the above-mentioned second process, and performs the UAC process, and further, in the case that the access attempt of the UAC process is prohibited, it is no longer performed. Access control to the broadcast multicast service; when the UAC procedure access attempt is allowed, the access control to the broadcast multicast service is performed immediately.
  • the terminal device performs congestion control for the broadcast multicast service in the above-mentioned first process, and performs access control for the broadcast multicast service in the second process. Further, in the step of executing the access control to the broadcast multicast service, in the case of executing the UAC process, if the UAC process access attempt is prohibited, the access control to the broadcast multicast service is no longer executed. If the process access attempt is allowed, the access control to the broadcast multicast service is performed immediately.
  • the reason for initiating the second process includes at least one of the following.
  • the first event can be understood as the value of the existing cause of initiation of the second process and can be used for broadcast multicast services, for example, set to mt-Access or mo-Signalling.
  • a second event that is different from the first event can be understood as a new event that is different from the existing first event and is the cause of the initiation of the second process.
  • the second event is at least one of the following.
  • the second event does not distinguish specific broadcast multicast services, and different broadcast multicast services have the same value, for example, the second event is MBSConfiguartion, MBS-data, mbs-signalling, and MBSmt-Access.
  • the second event distinguishes specific broadcast multicast services, and different broadcast multicast services have different values.
  • the second event is IPTVConfiguration, IPTV-data, IPTVmt-Access
  • the second event is Public safety Configuration, Public safety-data
  • the second event is MBS1Configuration, MBS1-data, mbs1-signalling, and mbs1mt-Access.
  • each broadcast multicast service group contains one or more broadcast multicast service settings; that is, the second event distinguishes specific broadcast multicast service groups, and different broadcast multicast service groups have different values. .
  • the initiation cause is at least one of the following: resumeCause and establishmentCause.
  • the MAC layer is subjected to congestion control.
  • the MAC protocol data unit Provides the RRCSetupRequest message for IDLE UE, or the MAC PDU for the RRCResumeRequest or RRCResumeRequest1 message for Inactive UE, is submitted to the physical layer and sent to network side.
  • the triggering event of the random access procedure of the MAC layer includes at least one of the following.
  • the third event can be understood as the trigger event of the random access process of the existing MAC layer and can be used for broadcast multicast services, such as Initial access from RRC_IDLE, Transition from RRC_INACTIVE, etc.
  • the fourth event can be understood as a triggering event of the random access procedure of the new MAC layer which is different from the existing third event.
  • the fourth event is at least one of the following.
  • the fourth event does not distinguish specific broadcast multicast services, and different broadcast multicast services have the same value.
  • the fourth event is gain MBS Configuration, receive MBS data, and MBS-signalling.
  • the fourth event distinguishes specific broadcast multicast services, and different broadcast multicast services have different values.
  • each broadcast multicast service group contains one or more broadcast multicast service settings; that is, the fourth event distinguishes specific broadcast multicast service groups, and different broadcast multicast service groups have different values. .
  • the network side device may provide relevant information for the broadcast multicast service.
  • the method can also include the following:
  • the parameters related to the broadcast multicast service include at least one of the following: power ramping step (powerRampingStep), return Scaling factor BI (scalingFactorBI) and the maximum number of random access preamble transmissions (preambleTransMax).
  • the powerRampingStep parameter is at least one of the following:
  • the powerRampingStep parameter does not distinguish specific broadcast multicast services, and different broadcast multicast services have the same parameters, such as powerRampingStepLowPriority-MBS, powerRampingStep-MBS.
  • the powerRampingStep parameter distinguishes specific broadcast multicast services, and different broadcast multicast services have different parameters.
  • the powerRampingStep parameter is powerRampingStepLowPriority-mbs1.
  • each broadcast multicast service group contains one or more broadcast multicast service settings; that is, the powerRampingStep parameter distinguishes specific broadcast multicast service groups, and different broadcast multicast service groups have different parameters.
  • the powerRampingStep parameter is at least one of the following:
  • Parameters applicable to all random access types corresponding to the random access process of the MAC layer based on parameters set separately for each random access type corresponding to the random access process of the MAC layer.
  • the random access type corresponding to the random access process of the MAC layer includes a 4-step random access type (that is, a 4-step RACH) and a 2-step random access type (that is, a 2-step RACH).
  • the scalingFactorBI parameter is at least one of the following.
  • scalingFactorBI parameter does not distinguish specific broadcast multicast services, and different broadcast multicast services have the same parameters, such as scalingFactorBI-MBS.
  • the scalingFactorBI parameter distinguishes specific broadcast multicast services, and different broadcast multicast services have different parameters.
  • the scalingFactorBI parameter includes scalingFactorBI-IPTV; in another example, for a broadcast multicast service such as public safety, the scalingFactorBI parameter is scalingFactorBI-public safety; in another example
  • TMGI or IP multicast address or application server address+IP multicast address and other methods for identifying broadcast multicast services
  • each broadcast multicast service group contains one or more broadcast multicast service settings; that is, the scalingFactorBI parameter distinguishes specific broadcast multicast service groups, and different broadcast multicast service groups have different parameters.
  • the scalingFactorBI parameter is scalingFactorBI-2.
  • the scalingFactorBI parameter is at least one of the following.
  • Parameters applicable to all random access types corresponding to the random access process of the MAC layer based on parameters set separately for each random access type corresponding to the random access process of the MAC layer.
  • the random access types corresponding to the random access process of the MAC layer include 4-step RACH and 2-step RACH.
  • the preambleTransMax parameter is at least one of the following.
  • preambleTransMax parameter does not distinguish specific broadcast multicast services, and different broadcast multicast services have the same parameters, such as preambleTransMax-MBS.
  • the preambleTransMax parameter distinguishes specific broadcast multicast services, and different broadcast multicast services have different parameters.
  • the preambleTransMax parameter includes preambleTransMax-IPTV; in another example, for a broadcast multicast service such as public safety, the preambleTransMax parameter is preambleTransMax-public safety; in another example
  • TMGI or any method for identifying broadcast multicast services such as IP multicast address or application server address+IP multicast address
  • each broadcast multicast service group contains one or more broadcast multicast service settings; that is, the preambleTransMax parameter distinguishes specific broadcast multicast service groups, and different broadcast multicast service groups have different parameters.
  • the preambleTransMax parameter is preambleTransMax-2.
  • the preambleTransMax parameter is at least one of the following:
  • Parameters applicable to all random access types corresponding to the random access process of the MAC layer based on parameters set separately for each random access type corresponding to the random access process of the MAC layer.
  • the random access types corresponding to the random access process of the MAC layer include 4-step RACH and 2-step RACH.
  • the method when the congestion control of the broadcast multicast service is performed in the random access process of the MAC layer, the method may further include the following content.
  • the procedure configures parameters related to the broadcast multicast service.
  • the MAC layer of the terminal device when the MAC layer of the terminal device performs initialization of the variables of each random access type (that is, parameters related to the broadcast multicast service), the MAC layer can at least select the above RACH type (2-step RACH or 4-step RACH) Step RACH), the trigger event of the above-mentioned RACH and the above-mentioned parameters that the RRC layer configures for the random access process, to set the value of the RACH parameter, such as setting the value of PREAMBLE_POWER_RAMPING_STEP, SCALING_FACTOR_BI and preambleTransMax, including but not limited to the following specific examples.
  • the RACH parameter such as setting the value of PREAMBLE_POWER_RAMPING_STEP, SCALING_FACTOR_BI and preambleTransMax, including but not limited to the following specific examples.
  • RA_TYPE is set to 2-stepRA
  • PREAMBLE_POWER_RAMPING_STEP to msgA-PreamblePowerRampingStep
  • SCALING_FACTOR_BI is 1, using preambleTransMax contained in RACH-ConfigGenericTwoStepRA.
  • RA_TYPE is set to 2-stepRA
  • RRC is configured (such as RACH-ConfigCommonTwoStepRA ) when RACH parameters applicable to all broadcast multicast services (such as powerRampingStepLowPriority-MBS, scalingFactorBI-MBS, preambleTransMax-MBS), set PREAMBLE_POWER_RAMPING_STEP to powerRampingStepLowPriority-MBS, set SCALING_FACTOR_BI to scalingFactorBI-MBS, and use preambleTransMax-MBS.
  • RACH parameters applicable to all broadcast multicast services such as powerRampingStepLowPriority-MBS, scalingFactorBI-MBS, preambleTransMax-MBS
  • PREAMBLE_POWER_RAMPING_STEP to powerRampingStepLowPriority-MBS
  • SCALING_FACTOR_BI scalingFactorBI-MBS
  • preambleTransMax-MBS use preambleTransMax
  • RA_TYPE is set to 4-stepRA
  • RRC is configured (such as RACH-ConfigCommon)
  • RACH parameters of per broadcast multicast service such as powerRampingStepLowPriority-IPTV, scalingFactorBI-IPTV, preambleTransMax-IPTV
  • PREAMBLE_POWER_RAMPING_STEP to powerRampingStepLowPriority-IPTV
  • SCALING_FACTOR_BI to scalingFactorBI-IPTV
  • preambleTransMax-IPTV use preambleTransMax-IPTV.
  • the congestion control method of the broadcast multicast service considering that the Non-RRCConnected UE enters the RRCConnected state, it is mainly necessary to perform the RRC connection establishment process (for IDLE UE) or the RRC connection resume process of the RRC layer. (For Inactive UE), the random access process of the MAC layer, these two processes. Then, the congestion control of the MBS service can be realized by adding various independent sub-schemes in the two processes, that is, the RRC connection establishment process (for IDLE UE) or the RRC connection resume process of the RRC layer.
  • the access control for the broadcast multicast service is performed, and the random access process of the MAC layer sets at least three RACH parameters of powerRampingStep, scalingFactorBI, and preambleTransMax for the broadcast multicast service, and all settings, It is divided into three cases applicable to all broadcast multicast services, per broadcast multicast services, and per broadcast multicast service groups. In this way, when the number of Non-RRC Connected UEs that need broadcast multicast services is large, the probability of congestion in the random access process can be reduced, thereby improving the performance of the system which is seriously affected.
  • an embodiment of the present application provides a method for controlling congestion of a broadcast multicast service, which is performed by a device on a network side, and the method includes the following process steps.
  • Step 301 Receive a request corresponding to a first process sent by a terminal device, where the first process is used for the terminal device to perform congestion control on a broadcast multicast service; wherein the first process includes: the second process and The random access process of the MAC layer of the medium access control, the second process includes at least one of a radio resource control RRC connection establishment process and an RRC connection recovery process.
  • the congestion control for the broadcast multicast service in at least one or more of the RRC connection establishment process, the RRC connection recovery process, and the random access process of the MAC layer, it is possible to reduce the number of broadcast multicast services caused by The number of terminal devices in the non-RRC connection state requiring broadcast services is large, which leads to the probability of congestion in the random access process, thereby improving system performance.
  • the method may further include the following content.
  • Configuring a first threshold value ; sending the first threshold value to the terminal device, where the first threshold value is used for comparison with the value of the first random number selected by the terminal device, and the first threshold value is used for comparison with the value of the first random number selected by the terminal device.
  • the value of a random number is used for the terminal device to perform access control to the broadcast multicast service.
  • the name of the first random number is at least one of the following: a name applicable to all broadcast and multicast services, a name that is set independently based on each broadcast and multicast service, and a name that is set independently based on each broadcast and multicast service group. The name.
  • the first threshold value is at least one of the following: a threshold value applicable to all broadcast multicast services, a threshold value independently set based on each broadcast multicast service, and a threshold value based on each broadcast multicast service. Threshold values set individually for groups.
  • the method may further include the following content:
  • Configuring a first access control timer sending the first access control timer to the terminal device, where the first access control timer is used for the terminal device to determine whether the access attempt is barred or not be relieved.
  • the name of the first access control timer is at least one of the following: a name applicable to all broadcast multicast services, a name set separately based on each broadcast multicast service, and a name based on each broadcast multicast service.
  • the timing duration calculation formula corresponding to the first access control timer is related to at least one of the following.
  • the value of the first random number; the value of the fallback time; wherein, the formula for calculating the timing duration is at least one of the following: a formula applicable to all broadcast and multicast services, a formula set separately based on each broadcast and multicast service and formulas set individually based on each broadcast-multicast service group.
  • the following contents may be further included.
  • the value of the backoff time is at least one of the following: a value applicable to all broadcast multicast services, based on The value set individually for each broadcast multicast service and the value set individually based on each broadcast multicast service group.
  • the method may further include the following content.
  • the parameters related to the broadcast multicast service include the following At least one item: power increase step size, back-off parameter BI scaling factor, and maximum number of random access preamble transmissions.
  • the parameters related to the broadcast multicast service are at least one of the following: parameters applicable to all broadcast multicast services, parameters independently set based on each broadcast multicast service, and parameters based on each broadcast multicast service group independently. set parameters.
  • the parameters related to the broadcast multicast service are at least one of the following: parameters applicable to all random access types corresponding to the random access process of the MAC layer; random access process based on the MAC layer The corresponding parameters for each random access type are set separately.
  • the execution subject may be the congestion control device of the broadcast multicast service, or, in the congestion control device of the broadcast multicast service
  • the control module for executing the congestion control method of broadcast multicast service is described by taking the congestion control method of the broadcast multicast service performed by the congestion control device of the broadcast multicast service as an example.
  • an embodiment of the present application provides a congestion control apparatus 400 for a broadcast multicast service, which is applied to a terminal device.
  • the congestion control apparatus 400 for a broadcast multicast service includes: a control module 401 for performing a first process in a Execute congestion control on broadcast multicast services in the network; wherein, the first process includes: a second process and a random access process of the MAC layer of the medium access control, the second process includes the radio resource control RRC connection establishment process and At least one of the RRC connection recovery procedures.
  • a condition for the terminal device to initiate the second process includes at least one of the following: the terminal device The first condition when the device executes the broadcast multicast service session joining process; the second condition when the terminal device executes the broadcast multicast service data reception after the broadcast multicast service session joining process is completed.
  • the first condition includes at least one of the following: the terminal device receives the broadcast multicast service information; At least one broadcast multicast service corresponding to the broadcast multicast service information is interested in; the upper layer requests the establishment of the RRC connection; the upper layer requests the restoration of the RRC connection; the terminal equipment has the broadcast multicast service capability; the network side equipment supports the broadcast multicast service ; the terminal device receives the session start notification sent by the network side device; the terminal device receives the control information of the broadcast multicast service sent by the network side device.
  • the second condition includes at least one of the following: the terminal device receives a session start notification sent by a network side device; the terminal device The equipment has the capability of broadcast and multicast services; the equipment on the network side supports broadcast and multicast services.
  • control module 401 may also be configured to perform one of the following operations in the second process: not performing unified access Control the UAC procedure; execute the UAC procedure.
  • the control module 401 when the UAC process is performed, may also be configured to perform one of the following operations: when the UAC process is performed When the terminal device performs the process of joining the broadcast multicast service session, the access type corresponding to the access control is determined by the non-access layer NAS layer or the RRC layer of the terminal device; when the terminal device joins the broadcast multicast service session When the receiving of the MBS data is performed after the process is completed, the access type corresponding to the access control is determined and set through the RRC layer of the terminal device.
  • the value of the parameter corresponding to the access control includes at least one of the following: a first value; and a second value different from the first value; wherein the value of the parameter corresponding to the access control includes at least one of a value of an access type and a value of an access identification; the second value is at least one of the following Items: Values that apply to all broadcast-multicast services, values that are set individually on a per-broadcast-multicast-service basis, and values that are set individually on a per-broadcast-multicast service group.
  • control module 401 may be further configured to perform access control for the broadcast multicast service in the second process.
  • the apparatus 400 for congestion control of a broadcast multicast service in this embodiment of the present application may further include a processing module, where the processing module is configured to: select a value of a first random number, and the value of the first random number is used for For the terminal device to perform access control to the broadcast multicast service; if the value of the first random number is lower than the first threshold value, it is considered that the access attempt is prohibited, otherwise, the access attempt is considered to be allowed .
  • the apparatus 400 for congestion control of a broadcast multicast service in this embodiment of the present application may further include: a receiving module configured to receive the first threshold value configured by the network side device.
  • the name of the first random number is at least one of the following: a name applicable to all broadcast multicast services, a name based on each broadcast multicast service Names that are set individually for the broadcast service and names that are set individually for each broadcast-multicast service group.
  • the first threshold value is at least one of the following: a threshold value applicable to all broadcast multicast services, a threshold value based on each broadcast Thresholds set individually for multicast services and thresholds set individually for each broadcast-multicast service group.
  • the processing module may be further configured to: start the first access control timer when it is considered that the access attempt is prohibited ; After the first access control timer expires, the access barring of the access attempt is considered to be relieved.
  • the receiving module may be further configured to: receive the first access control timer configured by the network side device.
  • the name of the first access control timer is at least one of the following: a name applicable to all broadcast multicast services, a name based on each The name set individually for each broadcast multicast service and the name set individually based on each broadcast multicast service group.
  • the timing duration calculation formula corresponding to the first access control timer is related to at least one of the following: value; the value of the fallback time configured by the network side device; wherein, the formula for calculating the timing duration is at least one of the following: a formula applicable to all broadcast multicast services, a formula based on a separate setting for each broadcast multicast service, and a formula based on The formula set individually for each broadcast multicast service group.
  • the receiving module may further be configured to: receive the value of the backoff time configured by the network side.
  • the value of the backoff time is at least one of the following: a value applicable to all broadcast multicast services, based on each broadcast multicast service The value set individually for the service and the value set individually based on each broadcast multicast service group.
  • control module 401 may also be configured to perform the following operations when the UAC process is performed: in the UAC process When the access attempt is prohibited, the access control to the broadcast multicast service is no longer performed; when the access attempt in the UAC procedure is allowed, the access control to the broadcast multicast service is immediately performed.
  • a cause for initiating the second process includes at least one of the following: a first event; a second event different from the first event ; wherein, the second event is at least one of the following: an event applicable to all broadcast and multicast services, an event based on each broadcast and multicast service individually set and an event based on each broadcast and multicast service group independently set; wherein , the initiation cause is at least one of the following: resumeCause and establishmentCause.
  • the triggering event of the random access process at the MAC layer includes at least one of the following: a third event; different from the third event The fourth event; wherein, the fourth event is at least one of the following: an event applicable to all broadcast and multicast services, an event that is individually set based on each broadcast and multicast service, and an event that is independently set based on each broadcast and multicast service group event.
  • the receiving module may also be configured to: receive a broadcast multicast service related to the broadcast multicast service configured by the network side device for the random access process of the MAC layer.
  • the parameters related to the broadcast multicast service include at least one of the following: a power increase step size, a backoff parameter BI scaling factor, and a maximum number of random access pilot transmissions.
  • the parameter related to the broadcast multicast service is at least one of the following: a parameter applicable to all broadcast multicast services, a parameter based on each broadcast Parameters that are set individually for multicast services and parameters that are set individually for each broadcast-multicast service group.
  • the parameter related to the broadcast multicast service is at least one of the following: applicable to all the random access procedures corresponding to the MAC layer. Parameters of random access types; parameters set independently for each random access type corresponding to the random access process of the MAC layer.
  • the processing module may further be configured to: set the value of a parameter related to the broadcast multicast service according to at least one of the following: The random access type; the trigger event of the random access process of the MAC layer; whether the network side device configures the parameters related to the broadcast multicast service for the random access process of the MAC layer.
  • the congestion control of the broadcast multicast service may be implemented in at least one of the second process and the random access process of the MAC layer of the medium access control, where the second process includes the radio resource control RRC connection At least one of the establishment procedure and the RRC connection recovery procedure.
  • the congestion control process for the broadcast multicast service may be added to at least one or more of the RRC connection establishment process, the RRC connection recovery process and the random access process of the MAC layer, it is possible to reduce the demand for the broadcast multicast service.
  • the number of terminal devices in the non-RRC connection state is relatively large, which leads to the probability of congestion in the random access process, thereby improving the system performance.
  • the congestion control apparatus for the broadcast multicast service in the embodiment of the present application may be an apparatus, or may be a component, an integrated circuit, or a chip in a terminal device.
  • the device may be a mobile terminal or a non-mobile terminal.
  • the mobile terminal may include, but is not limited to, the types of terminals 11 listed above, and the non-mobile terminal may be a server, a network attached storage (NAS), a personal computer (personal computer, PC), a television ( television, TV), teller machine, or self-service machine, etc., which are not specifically limited in the embodiments of the present application.
  • the congestion control device for the broadcast multicast service in the embodiment of the present application may be a device with an operating system.
  • the operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, which are not specifically limited in the embodiments of the present application.
  • the apparatus for congestion control of the broadcast multicast service provided by the embodiment of the present application can implement each process implemented by the method embodiment in FIG. 2 and achieve the same technical effect. To avoid repetition, details are not described here.
  • the execution subject may be the congestion control device of the broadcast multicast service, or the congestion control device of the broadcast multicast service.
  • a control module for implementing a congestion control method for broadcast multicast services is described by taking the method for performing the congestion control of the broadcast multicast service by the congestion control device of the broadcast multicast service as an example.
  • an embodiment of the present application provides a congestion control apparatus 500 for a broadcast multicast service, which is applied to a network side device.
  • the congestion control apparatus 500 for a broadcast multicast service includes: a receiving module 501 for receiving terminal equipment A request corresponding to the sent first process, where the first process is used for the terminal device to perform congestion control on the broadcast multicast service; wherein the first process includes: the second process and the medium access control MAC layer the random access process, the second process includes at least one of a radio resource control RRC connection establishment process and an RRC connection recovery process.
  • the apparatus 500 for congestion control of a broadcast multicast service in this embodiment of the present application may further include: a first processing module, configured to configure a first gate before receiving a request corresponding to the first process sent by the terminal device a limit value; a first sending module, configured to send the first threshold value to the terminal device, where the first threshold value is used to compare with the value of the first random number selected by the terminal device, The value of the first random number is used for the terminal device to perform access control to the broadcast multicast service.
  • a first processing module configured to configure a first gate before receiving a request corresponding to the first process sent by the terminal device a limit value
  • a first sending module configured to send the first threshold value to the terminal device, where the first threshold value is used to compare with the value of the first random number selected by the terminal device, The value of the first random number is used for the terminal device to perform access control to the broadcast multicast service.
  • the name of the first random number is at least one of the following: a name applicable to all broadcast multicast services, a name based on each broadcast multicast service Names that are set individually for the broadcast service and names that are set individually for each broadcast-multicast service group.
  • the first threshold value is at least one of the following: a threshold value applicable to all broadcast multicast services, a threshold value based on each broadcast Thresholds set individually for multicast services and thresholds set individually for each broadcast-multicast service group.
  • the apparatus 500 for congestion control of a broadcast multicast service in this embodiment of the present application may further include: a second processing module, configured to configure a first connection before receiving a request corresponding to the first process sent by the terminal device. an access control timer; a second sending module, configured to send the first access control timer to the terminal equipment, where the first access control timer is used for the terminal equipment to determine the connection of an access attempt Whether the entry ban has been alleviated.
  • the name of the first access control timer is at least one of the following: a name applicable to all broadcast multicast services, a name based on each The name set individually for each broadcast multicast service and the name set individually based on each broadcast multicast service group.
  • the timing duration calculation formula corresponding to the first access control timer is related to at least one of the following: value; the value of the backoff time; wherein, the timing duration calculation formula is at least one of the following: a formula applicable to all broadcast multicast services, a formula set separately based on each broadcast multicast service, and a formula based on each broadcast multicast service Formulas set individually by business groups.
  • the second processing module is further configured to configure the value of the backoff time; the second sending module is further configured to Sending the value of the backoff time to the terminal device; wherein the value of the backoff time is at least one of the following: a value applicable to all broadcast multicast services, a value set separately based on each broadcast multicast service values and values that are set individually based on each broadcast multicast service group.
  • the apparatus 500 for congestion control of a broadcast multicast service in this embodiment of the present application may further include: a third processing module, configured to configure the MAC address before receiving the request corresponding to the first process sent by the terminal device
  • the parameters related to the broadcast multicast service corresponding to the random access process of the layer are used for sending the parameters related to the broadcast multicast service to the terminal device;
  • the parameters include at least one of the following: a power increase step size, a back-off parameter BI scaling factor, and a maximum number of random access preamble transmissions.
  • the parameters related to the broadcast multicast service are at least one of the following: a parameter applicable to all broadcast multicast services, a parameter based on each broadcast Parameters that are set individually for multicast services and parameters that are set individually for each broadcast-multicast service group.
  • the parameter related to the broadcast multicast service is at least one of the following: applicable to all the random access procedures corresponding to the MAC layer. Parameters of random access types; parameters set independently for each random access type corresponding to the random access process of the MAC layer.
  • the congestion control for the broadcast multicast service in at least one or more of the RRC connection establishment process, the RRC connection recovery process, and the random access process of the MAC layer, it is possible to reduce the number of broadcast multicast services caused by The number of terminal devices in the non-RRC connection state requiring broadcast services is large, which leads to the probability of congestion in the random access process, thereby improving system performance.
  • the congestion control apparatus for the broadcast multicast service in the embodiment of the present application may be an apparatus, or may be a component, an integrated circuit, or a chip in a network-side device.
  • the apparatus may be a network side device.
  • the network-side device may include, but is not limited to, the types of the network-side device 12 listed above.
  • the congestion control device for the broadcast multicast service in the embodiment of the present application may be a device with an operating system.
  • the operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, which are not specifically limited in the embodiments of the present application.
  • the apparatus for controlling the congestion of broadcast multicast services can implement each process implemented by the method embodiment in FIG. 3 and achieve the same technical effect. To avoid repetition, details are not described here.
  • an embodiment of the present application further provides a communication device 600, including a processor 601, a memory 602, a program or instruction stored in the memory 602 and executable on the processor 601,
  • a communication device 600 including a processor 601, a memory 602, a program or instruction stored in the memory 602 and executable on the processor 601
  • the communication device 600 is a terminal
  • the program or instruction is executed by the processor 601
  • each process of the above-mentioned embodiment of the congestion control method for broadcast multicast service corresponding to FIG. 2 can be realized, and the same technical effect can be achieved.
  • the communication device 600 is a network-side device, when the program or instruction is executed by the processor 601, each process of the above-mentioned embodiment of the congestion control method for broadcast multicast service corresponding to FIG. 3 can be realized, and the same technical effect can be achieved. In order to avoid Repeat, and will not repeat them here.
  • FIG. 7 is a schematic diagram of a hardware structure of a terminal implementing an embodiment of the present application.
  • the terminal 700 includes but is not limited to: a radio frequency unit 701, a network module 702, an audio output unit 703, an input unit 704, a sensor 705, a display unit 706, a user input unit 707, an interface unit 708, a memory 709, a processor 710 and other components .
  • the terminal 700 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 710 through a power management system, so as to manage charging, discharging, and power consumption through the power management system management and other functions.
  • a power source such as a battery
  • the terminal structure shown in FIG. 7 does not constitute a limitation on the terminal, and the terminal may include more or less components than shown, or combine some components, or arrange different components, which will not be repeated here.
  • the input unit 704 may include a graphics processor (Graphics Processing Unit, GPU) 7041 and a microphone 7042. Such as camera) to obtain still pictures or video image data for processing.
  • the display unit 706 may include a display panel 7061, which may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like.
  • the user input unit 707 includes a touch panel 7071 and other input devices 7072 .
  • the touch panel 7071 is also called a touch screen.
  • the touch panel 7071 may include two parts, a touch detection device and a touch controller.
  • Other input devices 7072 may include, but are not limited to, physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which will not be repeated here.
  • the radio frequency unit 701 receives the downlink data from the network side device, and then processes it to the processor 710; in addition, sends the uplink data to the network side device.
  • the radio frequency unit 701 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
  • Memory 709 may be used to store software programs or instructions as well as various data.
  • the memory 709 may mainly include a storage program or instruction area and a storage data area, wherein the storage program or instruction area may store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.) and the like.
  • the memory 709 may include a high-speed random access memory, and may also include a non-volatile memory, wherein the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM) ), erasable programmable read-only memory (ErasablePROM, EPROM), electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • ROM Read-Only Memory
  • PROM programmable read-only memory
  • ErasablePROM ErasablePROM
  • EPROM electrically erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • flash memory for example at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.
  • the processor 710 may include one or more processing units; optionally, the processor 710 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, application programs or instructions, etc., Modem processors mainly deal with wireless communications, such as baseband processors. It can be understood that, the above-mentioned modulation and demodulation processor may not be integrated into the processor 710.
  • the processor 710 is configured to perform congestion control on broadcast multicast services in a first process; wherein the first process includes: a second process and a random access process at the MAC layer of medium access control, the The second procedure includes at least one of a radio resource control RRC connection establishment procedure and an RRC connection recovery procedure.
  • the congestion control of the broadcast multicast service may be implemented in at least one of the second process and the random access process of the MAC layer of the medium access control, where the second process includes the radio resource control RRC connection At least one of the establishment procedure and the RRC connection recovery procedure.
  • the congestion control process for the broadcast multicast service may be added to at least one or more of the RRC connection establishment process, the RRC connection recovery process and the random access process of the MAC layer, it is possible to reduce the demand for the broadcast multicast service.
  • the number of terminal devices in the non-RRC connection state is relatively large, which leads to the probability of congestion in the random access process, thereby improving the system performance.
  • the network side device 800 includes: an antenna 801 , a radio frequency device 802 , and a baseband device 803 .
  • the antenna 801 is connected to the radio frequency device 802 .
  • the radio frequency device 802 receives information through the antenna 801, and sends the received information to the baseband device 803 for processing.
  • the baseband device 803 processes the information to be sent and sends it to the radio frequency device 802
  • the radio frequency device 802 processes the received information and sends it out through the antenna 801 .
  • the above-mentioned frequency band processing apparatus may be located in the baseband apparatus 803 , and the method performed by the network side device in the above embodiments may be implemented in the baseband apparatus 803 .
  • the baseband apparatus 803 includes a processor 804 and a memory 805 .
  • the baseband device 803 may include, for example, at least one baseband board on which multiple chips are arranged. As shown in FIG. 8 , one of the chips is, for example, the processor 804 , which is connected to the memory 805 to call the program in the memory 805 to execute The network-side device shown in the above method embodiments operates.
  • the baseband device 803 may further include a network interface 806 for exchanging information with the radio frequency device 802, and the interface is, for example, a common public radio interface (CPRI for short).
  • CPRI common public radio interface
  • the network-side device in the embodiment of the present invention further includes: instructions or programs stored in the memory 805 and executable on the processor 804, and the processor 804 invokes the instructions or programs in the memory 805 to execute the modules shown in FIG. 5 .
  • Embodiments of the present application further provide a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, any one of the above-mentioned embodiments of the congestion control method for a broadcast multicast service is implemented.
  • a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, any one of the above-mentioned embodiments of the congestion control method for a broadcast multicast service is implemented.
  • Each process can achieve the same technical effect. In order to avoid repetition, it will not be repeated here.
  • the processor is the processor in the terminal or the network side device described in the foregoing embodiment.
  • the readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.
  • An embodiment of the present application further provides a computer program product, the computer program product is stored in a non-volatile readable storage medium, and when the computer program product is executed by the processor, implements any one of the above broadcast multicasting
  • the various processes of the embodiments of the method for congestion control of services can achieve the same technical effect, and are not repeated here to avoid repetition.
  • An embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a terminal device or a network-side device program or instruction to implement the above
  • the chip includes a processor and a communication interface
  • the communication interface is coupled to the processor
  • the processor is used to run a terminal device or a network-side device program or instruction to implement the above
  • the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-chip, or a system-on-a-chip, or the like.
  • the method of the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is better implementation.
  • the technical solution of the present application can be embodied in the form of a software product in essence or in a part that contributes to the prior art, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, CD-ROM), including several instructions to make a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network side device, etc.) execute the methods described in the various embodiments of this application.
  • a storage medium such as ROM/RAM, magnetic disk, CD-ROM

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种广播多播业务的拥塞控制方法、装置和设备，属于通信领域。其中，所述方法包括：在第一过程中执行对广播多播业务的拥塞控制；其中，所述第一过程包括：第二过程和媒体接入控制MAC层的随机接入过程，所述第二过程包括无线资源控制RRC连接建立过程和RRC连接恢复过程中的至少一项。

Description

广播多播业务的拥塞控制方法、装置和设备
交叉引用
本发明要求在2020年09月30日提交中国专利局、申请号为202011063156.6、发明名称为“广播多播业务的拥塞控制方法、装置和设备”的中国专利申请的优先权，该申请的全部内容通过引用结合在本发明中。
技术领域
本申请涉及通信领域，尤其涉及一种广播多播业务的拥塞控制方法、装置和设备。
背景技术
目前，在新空口(New Radio，NR)系统中，对广播多播业务，比如MBS(Multicast/BroadcastService)业务，感兴趣且处于非无线资源控制连接态(Non-Radio Resource ControlConnected)的用户设备(User Equipment，UE，也可称为终端设备、用户终端、移动终端等)需要进入RRC连接态来执行MBS会话加入(session join)过程；以及当MBS业务采用RRC专用信令(dedicatedsignalling)发送MBS的控制信息或当MBS业务的数据在无线接入网络(Radio Access Network，RAN)侧需要采用点对点(Point-to-Point，PTP)的方式发送时，UE也需要进入RRC连接态来获得MBS的控制信息或接收MBS的数据。
但是，当对广播多播业务有需求且处于非RRC连接态的UE的数量较大时，容易导致随机接入过程产生拥塞，从而严重影响系统的性能。
发明内容
本申请实施例提供一种广播多播业务的拥塞控制方法、装置和设备，以能够解决当对广播多播业务有需求且处于非RRC连接态的UE的数量较大时 易导致随机接入过程产生拥塞的问题。
第一方面，提供了一种广播多播业务的拥塞控制方法，应用于终端设备，所述方法包括：在第一过程中执行对广播多播业务的拥塞控制；其中，所述第一过程包括：第二过程和媒体接入控制MAC层的随机接入过程，所述第二过程包括无线资源控制RRC连接建立过程和RRC连接恢复过程中的至少一项。
第二方面，提供了一种广播多播业务的拥塞控制装置，应用于终端设备，所述装置包括：控制模块，用于在第一过程中执行对广播多播业务的拥塞控制；其中，所述第一过程包括：第二过程和媒体接入控制MAC层的随机接入过程，所述第二过程包括无线资源控制RRC连接建立过程和RRC连接恢复过程中的至少一项。
第三方面，提供了一种终端设备，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的广播多播业务的拥塞控制方法的步骤。
第四方面，提供了一种广播多播业务的拥塞控制方法，应用于网络侧设备，所述方法包括：接收终端设备发送的第一过程对应的请求，所述第一过程用于供所述终端设备执行对广播多播业务的拥塞控制；其中，所述第一过程包括：第二过程和媒体接入控制MAC层的随机接入过程，所述第二过程包括无线资源控制RRC连接建立过程和RRC连接恢复过程中的至少一项。
第五方面，提供了一种广播多播业务的拥塞控制装置，应用于网络侧设备，所述装置包括：接收模块，用于接收终端设备发送的第一过程对应的请求，所述第一过程用于供所述终端设备执行对广播多播业务的拥塞控制；其中，所述第一过程包括：第二过程和媒体接入控制MAC层的随机接入过程，所述第二过程包括无线资源控制RRC连接建立过程和RRC连接恢复过程中的至少一项。
第六方面提供了一种网络侧设备，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处 理器执行时实现如第四方面所述的广播多播业务的拥塞控制方法的步骤。
第七方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面所述的广播多播业务的拥塞控制方法的步骤，或者所述程序或指令被处理器执行时实现如第四方面所述的广播多播业务的拥塞控制方法的步骤。
第八方面，提供了一种计算机程序产品，该计算机程序产品存储在非易失性的可读存储介质，所述计算机程序产品被处理器执行时实现如第一方面所述的广播多播业务的拥塞控制方法的步骤，或者所述程序或指令被处理器执行时实现如第四方面所述的广播多播业务的拥塞控制方法的步骤。
第九方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行终端设备或网络侧设备程序或指令，实现如第一方面所述的广播多播业务的拥塞控制方法的步骤，或者实现如第四方面所述的广播多播业务的拥塞控制方法的步骤。
在本申请实施例中，可以至少在第二过程和媒体接入控制MAC层的随机接入过程中的一个实现对广播多播业务的拥塞控制，其中，该第二过程包括无线资源控制RRC连接建立过程和RRC连接恢复过程中的至少一项。如此，通过至少在RRC连接建立过程、RRC连接恢复过程和MAC层的随机接入过程中的一个或多个中加入对广播多播业务的拥塞控制过程，可以降低由于对广播多播业务有需求的且处于非RRC连接态的终端设备的数量较大，导致随机接入过程产生拥塞的概率，从而提高系统性能。
附图说明
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1示出本申请实施例可应用的一种无线通信系统的框图；
图2是本申请实施例中一种广播多播业务的拥塞控制方法的流程示意图；
图3是本申请实施例中另一种广播多播业务的拥塞控制方法的流程示意图；
图4是本申请实施例中一种广播多播业务的拥塞控制装置的结构示意图；
图5是本申请实施例中另一种广播多播业务的拥塞控制装置的结构示意图；
图6是本申请实施例中一种通信设备的结构示意图；
图7是本申请实施例中一种终端设备的结构示意图；
图8是本申请实施例中一种网络侧设备的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员所获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，说明书以及权利要求中“和/或”表示所连接对象的至少其中之一，字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码分多址(Code Division Multiple Access，CDMA)、时分多址(Time Division Multiple Access，TDMA)、频分多址(Frequency Division Multiple Access，FDMA)、正交频分多址(Orthogonal Frequency Division Multiple Access，OFDMA)、单载波频分多址(Single-carrier  Frequency-Division Multiple Access，SC-FDMA)和其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。然而，以下描述出于示例目的描述了新空口(NewRadio，NR)系统，并且在以下大部分描述中使用NR术语，这些技术也可应用于NR系统应用以外的应用，如第6代(6 thGeneration，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端11和网络侧设备12。其中，终端11也可以称作终端设备或者用户终端(User Equipment，UE)，终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(ultra-mobile personal computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、可穿戴式设备(Wearable Device)或车载设备(Vehicle UE，VUE)、行人终端(Pedestrian UE，PUE)等终端侧设备，可穿戴式设备包括：手环、耳机、眼镜等。需要说明的是，在本申请实施例并不限定终端11的具体类型。网络侧设备12可以是基站或核心网，其中，基站可被称为节点B、演进节点B、接入点、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、B节点、演进型B节点(eNB)、家用B节点、家用演进型B节点、WLAN接入点、WiFi节点、发送接收点(TransmittingReceivingPoint，TRP)或所述领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例，但是并不限定基站的具体类型。
下面结合附图，通过一些实施例及其应用场景对本申请实施例提供的广播多播业务的拥塞控制方法进行详细地说明。
参见图2所示，本申请实施例提供一种广播多播业务的拥塞控制方法，由终端设备执行，该方法包括以下流程步骤：
步骤201：在第一过程中执行对广播多播业务的拥塞控制；其中，所述第一过程包括：第二过程和媒体接入控制(Medium Access Control，MAC)层的随机接入过程，所述第二过程包括无线资源控制RRC连接建立过程和RRC连接恢复过程中的至少一项。
在本申请实施例中，可以至少在第二过程和媒体接入控制MAC层的随机接入过程中的一个实现对广播多播业务的拥塞控制，其中，该第二过程包括无线资源控制RRC连接建立过程和RRC连接恢复过程中的至少一项。如此，通过至少在RRC连接建立过程、RRC连接恢复过程和MAC层的随机接入过程中的一个或多个中加入对广播多播业务的拥塞控制过程，可以降低由于对广播多播业务有需求的且处于非RRC连接态的终端设备的数量较大，导致随机接入过程产生拥塞的概率，从而提高系统性能。
可选的，当第一过程为RRC连接建立(RRC connection establishment)过程时，终端设备对应的处于空闲态(idle)，该终端设备可以称之为IDLE UE；当第一过程为RRC连接恢复(RRC connection resume)过程时，终端设备对应的处于非激活态(Inactive)，该终端设备可以称之为Inactive UE。
可选的，在本申请实施例的广播多播业务的拥塞控制方法中，在上述第二过程中，所述终端设备发起所述第二过程的条件包括以下至少一项：
(1)所述终端设备执行广播多播业务会话加入过程(比如MBS join procedure)时的第一条件。
可选的，所述第一条件包括以下至少一项。
a)所述终端设备接收到广播多播业务信息；比如，LTE中的USD(user service description)。
b)所述终端设备对所述广播多播业务信息对应的至少一个广播多播业务感兴趣。
c)上层(upper layers)请求RRC连接的建立；主要适用于处于空闲态的终端设备。
d)上层请求RRC连接的恢复；主要适用于处于非激活态的终端设备。
e)所述终端设备具有广播多播业务能力。
f)网络侧设备支持广播多播业务；比如支持在系统消息中包含其支持广播多播业务的指示。
g)所述终端设备接收到网络侧设备发送的会话开始(session start)通知；比如，Session Start command、带有Group Paging Identity(TMGI)的组寻呼(group paging)、paging消息等。
h)所述终端设备接收到网络侧设备发送的广播多播业务的控制信息；比如LTE的系统信息块(System Information Block，SIB15)、SIB20等。
(2)所述终端设备在广播多播业务会话加入过程完成后执行广播多播业务数据的接收时的第二条件。其中，在广播多播业务会话加入过程完成后执行广播多播业务数据的接收时，是指，比如获取MBS的调度信息、MBS的配置信息(比如类似于LTE的scptmConfiguration)、MBS业务连续性相关的信息(比如类似于LTE的SIB15 SIB20中的内容)、接收MBS数据。
可选的，所述第二条件包括以下至少一项。
a)所述终端设备接收到网络侧设备发送的会话开始通知；比如，Session Start command、带有Group Paging Identity(TMGI)的group paging、paging消息等。
b)所述终端设备具有广播多播业务能力。
c)网络侧设备支持广播多播业务；比如LTE的SIB15、SIB20等。
可选的，在本申请实施例的广播多播业务的拥塞控制方法中，在上述第二过程发起后，针对统一接入控制(Unified Access Control，UAC)部分的限定，可以适用于以下具体实施例之一。
具体实施例一
在该具体实施例一中，在上述第二过程中，不执行统一接入控制UAC过程。
具体实施例二
在该具体实施例二中，在上述第二过程中，执行所述UAC过程。
可选的，在该具体实施例二中，即在执行所述UAC过程的情况下，本申请实施例的广播多播业务的拥塞控制方法，还可以包括内容中的以下至少之一。
(1)当所述终端设备执行广播多播业务会话加入(session join)过程时，由所述终端设备的非接入层(Non-access stratum，NAS)层或者RRC层决定接入控制对应的接入种类。
(2)当所述终端设备是在广播多播业务会话加入过程完成后执行MBS数据的接收时，由所述终端设备的RRC层决定和设置接入控制对应的接入种类。
可选的，在该具体实施例二中，即在执行所述UAC过程的情况下，接入控制对应的参数的值包括以下至少之一。
(1)第一值；该第一值可以理解为已有的且可以用于广播多播业务的接入控制对应的参数的值。
其中，所述接入控制对应的参数的值包括接入种类(Access category)的值和接入识别(Access identity)的值中的至少一项
在一个示例中，该第一值可以包括：Access identity的值设置为0，Access category的值设置为7(即发送数据mo-Data)。
(2)与所述第一值不同的第二值；该第二值可以理解为与已有的第一值不同的新的用于广播多播业务的接入控制对应的参数的值。
其中，所述第二值为以下至少一项。
a)适用于所有广播多播业务的值。也就是说，该第二值不区分具体的广播多播业务，不同的广播多播业务有相同的接入种类和/或接入识别的值，在一个示例中，Access identity设置为0，Access category设置为13(mt-MBSaccess)；在另一个示例中，Access identity设置为16，Access category设置为7(mo-Data)；在又一个示例中，Access identity设置为16，Access category设置为13(mt-MBSaccess)。
b)基于每个广播多播业务单独设置的值。也就是说，该第二值区分具体 的广播多播业务，不同的广播多播业务有不同的接入种类和/或接入识别的值。在一个示例中，针对公共安全(public safety)这种广播多播业务，Access identity设置为16，Access category设置为15(mo-PublicSafetydata)；在另一个示例中，针对交互式网络电视IPTV这种广播多播业务，Access identity设置为17，Access category设置为17(mo-IPTVdata)；在又一个示例中，针对MBS session ID＝x，TMGI(或者IP multicast address或者应用服务器地址+IP multicast address等任何标识广播多播业务的方法)＝y这个广播多播业务，Access identity设置为16，Access category设置为15。
c)基于每个广播多播业务组单独设置的值。其中，每个广播多播业务组包含一个或者多个的广播多播业务)设置的；也就是说，该第二值区分具体的广播多播业务组，不同的广播多播业务组有不同的接入种类和/或接入识别的值。在一个示例中，针对广播多播业务组id＝x,该业务组包括session ID＝z，TMGI(或者IP multicast address或者应用服务器地址+IP multicast address等任何标识广播多播业务的方法)＝m，以及session ID＝n，TMGI(或者IP multicast address或者应用服务器地址+IP multicast address等任何标识广播多播业务的方法)＝o两个广播多播业务，Access identity设置为16，Access category设置为15。
可选的，在本申请实施例的广播多播业务的拥塞控制方法中，在上述第二过程中，该方法还可以包括以下内容：执行对广播多播业务的接入控制。
在一个示例中，在上述第二过程发起后且在传输适用于IDLE UE的RRCSetupRequest消息，或者适用于Inactive UE的RRCResumeRequest或RRCResumeRequest1消息之前，执行对广播多播业务的接入控制。
进一步可选的，对广播多播业务的接入控制和UAC可以具有一定的关联关系，包括以下至少一项。
(1)在终端设备不执行UAC过程时，其可以立即执行对广播多播业务的接入控制。(2)在终端设备执行UAC过程时，如果UAC过程接入尝试被禁止，则不再执行对广播多播业务的接入控制；而如果UAC过程接入尝试 被允许，则立即执行对广播多播业务的接入控制。
进一步可选的，在上述第二过程中，执行对广播多播业务的接入控制的情况下，本申请实施例的广播多播业务的拥塞控制方法，还可以包括以下内容。
选择第一随机数的值，所述第一随机数的值用于供所述终端设备执行对广播多播业务的接入控制；在所述第一随机数的值低于第一门限值的情况下，认为接入尝试被禁止，否则认为接入尝试被允许。
可选的，上述第一随机数的名称为以下至少一项。
a)适用于所有广播多播业务的名称。也就是说，该第一随机数的名称不区分具体的广播多播业务，不同的广播多播业务有相同的随机数的名称，比如rand1。
b)基于每个广播多播业务单独设置的名称。也就是说，该第一随机数的名称区分具体的广播多播业务，不同的广播多播业务有不同的随机数的名称。在一个示例中，针对IPTV这种广播多播业务，随机数的名称为rand1；在另一个示例中，针对public safety这种广播多播业务，随机数的名称为rand2；在又一个示例中，针对MBS session ID＝x，TMGI(或者IP multicast address或者应用服务器地址+IP multicast address等任何标识广播多播业务的方法)＝y这个广播多播业务，随机数的名称为rand3。
c)基于每个广播多播业务组单独设置的名称。其中，每个广播多播业务组包含一个或者多个的广播多播业务设置的；也就是说，该第一随机数的名称区分具体的广播多播业务组，不同的广播多播业务组有不同的随机数的名称。在一个示例中，针对MBS业务组id＝x，该业务组包括session ID＝z，TMGI(或者IP multicast address或者应用服务器地址+IP multicast address等任何标识广播多播业务的方法)＝m，以及session ID＝n，TMGI(或者IP multicast address或者应用服务器地址+IP multicast address等任何标识广播多播业务的方法)＝o两个广播多播业务，随机数的名称为rand4。
可选的，在本申请实施例的广播多播业务的拥塞控制方法中，上述第一 门限值可以是由网络侧设备配置的，也就是说，该方法还可以包括以下内容：
接收网络侧设备配置的所述第一门限值。
进一步可选的，上述第一门限值为以下至少一项。
a)适用于所有广播多播业务的门限值。也就是说，该第一门限值不区分具体的广播多播业务，不同的广播多播业务有相同的门限值，比如MBSac-BarringFactor。
b)基于每个广播多播业务单独设置的门限值。也就是说，该第一门限值区分具体的广播多播业务，不同的广播多播业务有不同的门限值。在一个示例中，针对IPTV这种广播多播业务，门限值为IPTVac-BarringFactor；在另一个示例中，针对public safety这种广播多播业务，门限值为Public safety-BarringFactor；在又一个示例中，针对MBS session ID＝x，TMGI(或者IP multicast address或者应用服务器地址+IP multicast address等任何标识广播多播业务的方法)＝y这个广播多播业务，门限值为BarringFactor1。
c)基于每个广播多播业务组单独设置的门限值。其中，每个广播多播业务组包含一个或者多个的广播多播业务设置的；也就是说，该第一门限值区分具体的广播多播业务组，不同的广播多播业务组有不同的门限值。在一个示例中，针对MBS业务组id＝x，该业务组包括session ID＝z，TMGI(或者IP multicast address或者应用服务器地址+IP multicast address等任何标识广播多播业务的方法)＝m，以及session ID＝n，TMGI(或者IP multicast address或者应用服务器地址+IP multicast address等任何标识广播多播业务的方法)＝o两个广播多播业务，门限值为BarringFactor2。
进一步可选的，在本申请实施例的广播多播业务的拥塞控制方法中，在所述第一随机数的值低于第一门限值，即认为接入尝试被禁止的情况下，该方法还可以包括以下内容。
再次选择随机数的值(可选的)，开启第一接入控制定时器；在所述第一接入控制定时器超时后，认为接入尝试的接入禁止被减轻。
可选的，在本申请实施例的广播多播业务的拥塞控制方法中，上述第一 接入控制定时器可以是由网络侧设备配置的，也就是说，该方法还可以包括以下内容：接收网络侧设备配置的所述第一接入控制定时器。
进一步可选的，上述第一接入控制定时器的名称为以下至少一项。
a)适用于所有广播多播业务的名称。也就是说，该第一接入控制定时器的名称不区分具体的广播多播业务，不同的广播多播业务有相同的定时器的名称，比如T390a。
b)基于每个广播多播业务单独设置的名称。也就是说，该第一接入控制定时器的名称区分具体的广播多播业务，不同的广播多播业务有不同的定时器的名称。在一个示例中，针对IPTV这种广播多播业务，定时器额名称为T390a；在另一个示例中，针对public safety这种广播多播业务，定时器的名称为T390b；在又一个示例中，针对MBS session ID＝x，TMGI(或者IP multicast address或者应用服务器地址+IP multicast address等任何标识广播多播业务的方法)＝y这个广播多播业务，定时器的名称为T390c。
c)基于每个广播多播业务组单独设置的名称。其中，每个广播多播业务组包含一个或者多个的广播多播业务设置的；也就是说，该第一接入控制定时器的名称区分具体的广播多播业务组，不同的广播多播业务组有不同的定时器的名称。在一个示例中，针对MBS业务组id＝x，该业务组包括session ID＝z，TMGI(或者IP multicast address或者应用服务器地址+IP multicast address等任何标识广播多播业务的方法)＝m，以及session ID＝n，TMGI(或者IP multicast address或者应用服务器地址+IP multicast address等任何标识广播多播业务的方法)＝o两个广播多播业务，定时器的名称为T390d。
进一步可选的，上述第一接入控制定时器对应的定时时长计算公式与以下至少之一有关：所述第一随机数的值；网络侧设备配置的回退时间的值。
在一个示例中，当第一接入控制定时器对应的定时时长计算公式与第一随机数的值有关时，该计算公式可以表示为：(0.7+0.6*随机数的值)。其中，如果UE进行了随机数值的多次选择，则公式中使用的是随机数最新的那个值。
在另一个示例中，当第一接入控制定时器对应的定时时长计算公式与第一随机数的值有关和回退时间的值时，该计算公式可以表示为：(0.7+0.6*随机数的值)*回退时间的值。
其中，所述定时时长计算公式为以下至少一项。
a)适用于所有广播多播业务的公式。也就是说，该定时时长计算公式不区分具体的广播多播业务，不同的广播多播业务有相同的计算公式。
b)基于每个广播多播业务单独设置的公式。也就是说，该定时时长计算公式区分具体的广播多播业务，不同的广播多播业务有不同的计算公式。在一个示例中，针对IPTV这种广播多播业务，计算公式为公式1；在另一个示例中，针对public safety这种广播多播业务，计算公式为公式2；在又一个示例中，针对MBS session ID＝x，TMGI(或者IP multicast address或者应用服务器地址+IP multicast address等任何标识广播多播业务的方法)＝y这个广播多播业务，计算公式为公式3。
c)基于每个广播多播业务组单独设置的公式。其中，每个广播多播业务组包含一个或者多个的广播多播业务设置的；也就是说，该定时时长计算公式区分具体的广播多播业务组，不同的广播多播业务组有不同的计算公式。在一个示例中，针对MBS业务组id＝x，该业务组包括session ID＝z，TMGI(或者IP multicast address或者应用服务器地址+IP multicast address等任何标识广播多播业务的方法)＝m，以及session ID＝n，TMGI(或者IP multicast address或者应用服务器地址+IP multicast address等任何标识广播多播业务的方法)＝o两个广播多播业务，计算公式为公式4。
可选的，在本申请实施例的广播多播业务的拥塞控制方法中，上述回退时间的值可以是由网络侧设备配置的，也就是说，该方法还可以包括以下内容：接收网络侧配置的所述回退时间的值。
进一步可选的，上述所述回退时间的值为以下至少一项。
a)适用于所有广播多播业务的值。也就是说，该回退时间的值不区分具体的广播多播业务，不同的广播多播业务有相同的回退时间，比如 MBSac-BarringTime。
b)基于每个广播多播业务单独设置的值。也就是说，该回退时间的值区分具体的广播多播业务，不同的广播多播业务有不同的回退时间。在一个示例中，针对IPTV这种广播多播业务，回退时间为IPTVac-BarringTime；在另一个示例中，针对public safety这种广播多播业务，回退时间为Public safetyac-BarringTime；在又一个示例中，针对MBS session ID＝x，TMGI(或者IP multicast address或者应用服务器地址+IP multicast address等任何标识广播多播业务的方法)＝y这个广播多播业务，回退时间为BarringTime1。
c)基于每个广播多播业务组单独设置的值。其中，每个广播多播业务组包含一个或者多个的广播多播业务设置的；也就是说，该回退时间的值区分具体的广播多播业务组，不同的广播多播业务组有不同的回退时间。在一个示例中，针对MBS业务组id＝x，该业务组包括session ID＝z，TMGI(或者IP multicast address或者应用服务器地址+IP multicast address等任何标识广播多播业务的方法)＝m，以及session ID＝n，TMGI(或者IP multicast address或者应用服务器地址+IP multicast address等任何标识广播多播业务的方法)＝o两个广播多播业务，回退时间为BarringTime2。
可选的，在本申请实施例的广播多播业务的拥塞控制方法中，在执行所述UAC过程的情况下，所述方法还包括：在所述UAC过程接入尝试被禁止的情况下，不再执行对广播多播业务的接入控制；在所述UAC过程接入尝试被允许的情况下，立即执行对广播多播业务的接入控制。与UAC过程关联的对广播多播业务的接入控制的具体实施例包括但不限于以下几个实施例：
在具体实施例I中，终端设备在上述第一过程中执行对广播多播业务的拥塞控制，以及执行UAC过程；进一步地，在所述UAC过程接入尝试被禁止的情况下，不再执行对广播多播业务的接入控制；在所述UAC过程接入尝试被允许的情况下，立即执行对广播多播业务的接入控制。
在具体实施例II中，终端设备在上述第二过程中执行对广播多播业务的拥塞控制，以及执行UAC过程，进一步地，在所述UAC过程接入尝试被禁 止的情况下，不再执行对广播多播业务的接入控制；在所述UAC过程接入尝试被允许的情况下，立即执行对广播多播业务的接入控制。
在具体实施例III中，终端设备在上述第一过程中执行对广播多播业务的拥塞控制，以及在第二过程中，执行对广播多播业务的接入控制。进一步地，该执行对广播多播业务的接入控制的步骤，在执行UAC过程的情况下，若UAC过程接入尝试被禁止，则不再执行对广播多播业务的接入控制，若UAC过程接入尝试被允许，则立即执行对广播多播业务的接入控制。
可选的，在本申请实施例的广播多播业务的拥塞控制方法中，所述第二过程的发起原因包括以下至少一项。
(1)第一事件；该第一事件可以理解为已有的第二过程的发起原因的值且可用于广播多播业务，比如设置为mt-Access或者mo-Signalling。
(2)与所述第一事件不同的第二事件；该第二事件可以理解为与已有的第一事件不同的新的作为第二过程的发起原因的事件。
其中，所述第二事件为以下至少一项。
a)适用于所有广播多播业务的事件。也就是说，该第二事件不区分具体的广播多播业务，不同的广播多播业务有相同的值，比如该第二事件为MBSConfiguartion，MBS-data，mbs-signalling，MBSmt-Access。
b)基于每个广播多播业务单独设置的事件。也就是说，该第二事件区分具体的广播多播业务，不同的广播多播业务有不同的值。在一个示例中，针对IPTV这种广播多播业务，该第二事件为IPTVConfiguration，IPTV-data，IPTVmt-Access；在另一个示例中，针对public safety这种广播多播业务，该第二事件为Public safety Configuration，Public safety-data；在又一个示例中，针对MBS session ID＝x，TMGI(或者IP multicast address或者应用服务器地址+IP multicast address等任何标识广播多播业务的方法)＝y这个广播多播业务，该第二事件为MBS1Configuration，MBS1-data，mbs1-signalling，mbs1mt-Access。
c)基于每个广播多播业务组单独设置的事件。其中，每个广播多播业务 组包含一个或者多个的广播多播业务设置的；也就是说，该第二事件区分具体的广播多播业务组，不同的广播多播业务组有不同的值。在一个示例中，针对MBS业务组id＝x，该业务组包括session ID＝z，TMGI(或者IP multicast address或者应用服务器地址+IP multicast address等任何标识广播多播业务的方法)＝m，以及session ID＝n，TMGI(或者IP multicast address或者应用服务器地址+IP multicast address等任何标识广播多播业务的方法)＝o两个广播多播业务，该第二事件为MBS2Configuration，MBS2-data，MBS2mo-signalling。
其中，所述发起原因为以下至少一项：恢复原因resumeCause和建立原因establishmentCause。
可选的，在本申请实施例的广播多播业务的拥塞控制方法中，当在MAC层的随机接入(Random Access Channel，RACH)过程中对广播多播业务进行拥塞控制时，对MAC层的随机接入过程，将带有适用于IDLE UE的RRCSetupRequest消息的MAC协议数据单元(Protocol Data Unit，PDU)，或者适用于Inactive UE的RRCResumeRequest或RRCResumeRequest1消息的MAC PDU，提交给物理层并发送至网络侧。
可选的，在本申请实施例的广播多播业务的拥塞控制方法中，所述MAC层的随机接入过程的触发事件包括以下至少一项。
(1)第三事件；该第三事件可以理解为已有的MAC层的随机接入过程的触发事件且可用于广播多播业务，比如Initial access from RRC_IDLE，Transition from RRC_INACTIVE等。
(2)与所述第三事件不同的第四事件。该第四事件可以理解为与已有的第三事件不同的新的MAC层的随机接入过程的触发事件。
其中，所述第四事件为以下至少一项。
a)适用于所有广播多播业务的事件。也就是说，该第四事件不区分具体的广播多播业务，不同的广播多播业务有相同的值，比如该第四事件为gain MBS Configuartion，receive MBS data，MBS-signalling等。
b)基于每个广播多播业务单独设置的事件。也就是说，该第四事件区分具体的广播多播业务，不同的广播多播业务有不同的值。在一个示例中，针对IPTV这种广播多播业务，该第四事件为gain IPTV Configuration，receive IPTV data，IPTV-signalling；在另一个示例中，针对public safety这种广播多播业务，该第二事件为gain Public safety Configuration,receive Public safety data,Public safety-signalling；在又一个示例中，针对MBS session ID＝x，TMGI(或者IP multicast address或者应用服务器地址+IP multicast address等任何标识广播多播业务的方法)＝y这个广播多播业务，该第四事件为gain MBS1Configuration，receive MBS1data，mbs1-signalling。
c)基于每个广播多播业务组单独设置的事件。其中，每个广播多播业务组包含一个或者多个的广播多播业务设置的；也就是说，该第四事件区分具体的广播多播业务组，不同的广播多播业务组有不同的值。在一个示例中，针对MBS业务组id＝x，该业务组包括session ID＝z，TMGI(或者IP multicast address或者应用服务器地址+IP multicast address等任何标识广播多播业务的方法)＝m，以及session ID＝n，TMGI(或者IP multicast address或者应用服务器地址+IP multicast address等任何标识广播多播业务的方法)＝o两个广播多播业务，该第四事件为gain MBS2Configuration，receive MBS2data，MBS2mo-signalling。
可选的，在本申请实施例的广播多播业务的拥塞控制方法中，当在MAC层的随机接入过程中执行对广播多播业务的拥塞控制时，可以由网络侧设备为其提供相关的参数，也就是说，该方法还可以包括以下内容：
接收网络侧设备为所述MAC层的随机接入过程配置的广播多播业务相关的参数；其中，所述广播多播业务相关的参数包括以下至少一项：功率增长步长(powerRampingStep)、回退参数BI缩放因子(scalingFactorBI)和随机接入导码最大传输次数(preambleTransMax)。
进一步可选的，在本申请实施例的广播多播业务的拥塞控制方法中，所述powerRampingStep参数为以下至少一项：
a)适用于所有广播多播业务的参数。也就是说，该powerRampingStep参数不区分具体的广播多播业务，不同的广播多播业务有相同的参数，比如powerRampingStepLowPriority-MBS，powerRampingStep-MBS。
b)基于每个广播多播业务单独设置的参数。也就是说，该powerRampingStep参数区分具体的广播多播业务，不同的广播多播业务有不同的参数。在一个示例中，针对IPTV这种广播多播业务，该powerRampingStep参数包括powerRampingStep-IPTV、powerRampingStepLowPriority-IPTV；在另一个示例中，针对public safety这种广播多播业务，该powerRampingStep参数为powerRampingStep-public safety、powerRampingStepLowPriority-public safety；在又一个示例中，针对MBS session ID＝x，TMGI(或者IP multicast address或者应用服务器地址+IP multicast address等任何标识广播多播业务的方法)＝y这个广播多播业务，该powerRampingStep参数为powerRampingStepLowPriority-mbs1。
c)基于每个广播多播业务组单独设置的参数。其中，每个广播多播业务组包含一个或者多个的广播多播业务设置的；也就是说，该powerRampingStep参数区分具体的广播多播业务组，不同的广播多播业务组有不同的参数。在一个示例中，针对MBS业务组id＝x，该业务组包括session ID＝z，TMGI(或者IP multicast address或者应用服务器地址+IP multicast address等任何标识广播多播业务的方法)＝m，以及session ID＝n，TMGI(或者IP multicast address或者应用服务器地址+IP multicast address等任何标识广播多播业务的方法)＝o两个广播多播业务，该powerRampingStep参数为powerRampingStepLowPriority-mbs2。
进一步可选的，在本申请实施例的广播多播业务的拥塞控制方法中，所述powerRampingStep参数为以下至少一项：
适用于所述MAC层的随机接入过程对应的所有随机接入类型的参数；基于所述MAC层的随机接入过程对应的每种随机接入类型单独设置的参数。
其中，MAC层的随机接入过程对应的随机接入类型包括4步随机接入类 型(即4步RACH)和2步随机接入类型(即2步RACH)。
进一步可选的，在本申请实施例的广播多播业务的拥塞控制方法中，所述scalingFactorBI参数为以下至少一项。
a)适用于所有广播多播业务的参数。也就是说，该scalingFactorBI参数不区分具体的广播多播业务，不同的广播多播业务有相同的参数，比如scalingFactorBI-MBS。
b)基于每个广播多播业务单独设置的参数。也就是说，该scalingFactorBI参数区分具体的广播多播业务，不同的广播多播业务有不同的参数。在一个示例中，针对IPTV这种广播多播业务，该scalingFactorBI参数包括scalingFactorBI–IPTV；在另一个示例中，针对public safety这种广播多播业务，该scalingFactorBI参数为scalingFactorBI-public safety；在又一个示例中，针对MBS session ID＝x，TMGI(或者IP multicast address或者应用服务器地址+IP multicast address等任何标识广播多播业务的方法)＝y这个广播多播业务，该scalingFactorBI参数为scalingFactorBI-1。
c)基于每个广播多播业务组单独设置的参数。其中，每个广播多播业务组包含一个或者多个的广播多播业务设置的；也就是说，该scalingFactorBI参数区分具体的广播多播业务组，不同的广播多播业务组有不同的参数。在一个示例中，针对MBS业务组id＝x，该业务组包括session ID＝z，TMGI(或者IP multicast address或者应用服务器地址+IP multicast address等任何标识广播多播业务的方法)＝m，以及session ID＝n，TMGI(或者IP multicast address或者应用服务器地址+IP multicast address等任何标识广播多播业务的方法)＝o两个广播多播业务，该scalingFactorBI参数为scalingFactorBI-2。
进一步可选的，在本申请实施例的广播多播业务的拥塞控制方法中，所述scalingFactorBI参数为以下至少一项。
适用于所述MAC层的随机接入过程对应的所有随机接入类型的参数；基于所述MAC层的随机接入过程对应的每种随机接入类型单独设置的参数。
其中，MAC层的随机接入过程对应的随机接入类型包括4步RACH和2 步RACH。
进一步可选的，在本申请实施例的广播多播业务的拥塞控制方法中，所述preambleTransMax参数为以下至少一项。
a)适用于所有广播多播业务的参数。也就是说，该preambleTransMax参数不区分具体的广播多播业务，不同的广播多播业务有相同的参数，比如preambleTransMax–MBS。
b)基于每个广播多播业务单独设置的参数。也就是说，该preambleTransMax参数区分具体的广播多播业务，不同的广播多播业务有不同的参数。在一个示例中，针对IPTV这种广播多播业务，该preambleTransMax参数包括preambleTransMax–IPTV；在另一个示例中，针对public safety这种广播多播业务，该preambleTransMax参数为preambleTransMax-public safety；在又一个示例中，针对MBS session ID＝x，TMGI(或者IP multicast address或者应用服务器地址+IP multicast address等任何标识广播多播业务的方法)＝y这个广播多播业务，该preambleTransMax参数为preambleTransMax-1。
c)基于每个广播多播业务组单独设置的参数。其中，每个广播多播业务组包含一个或者多个的广播多播业务设置的；也就是说，该preambleTransMax参数区分具体的广播多播业务组，不同的广播多播业务组有不同的参数。在一个示例中，针对MBS业务组id＝x，该业务组包括session ID＝z，TMGI(或者IP multicast address或者应用服务器地址+IP multicast address等任何标识广播多播业务的方法)＝m，以及session ID＝n，TMGI(或者IP multicast address或者应用服务器地址+IP multicast address等任何标识广播多播业务的方法)＝o两个广播多播业务，该preambleTransMax参数为preambleTransMax-2。
进一步可选的，在本申请实施例的广播多播业务的拥塞控制方法中，所述preambleTransMax参数为以下至少一项：
适用于所述MAC层的随机接入过程对应的所有随机接入类型的参数；基于所述MAC层的随机接入过程对应的每种随机接入类型单独设置的参数。
其中，MAC层的随机接入过程对应的随机接入类型包括4步RACH和2步RACH。
可选的，在本申请实施例的广播多播业务的拥塞控制方法中，当在MAC层的随机接入过程中执行对广播多播业务的拥塞控制时，该方法还可以包括以下内容。
根据以下至少一项，设置所述广播多播业务相关的参数的值：随机接入类型；所述MAC层的随机接入过程的触发事件；网络侧设备是否为所述MAC层的随机接入过程配置广播多播业务相关的参数。
在该实施例中，终端设备的MAC层执行每种随机接入类型的变量(即广播多播业务相关的参数)的初始化时，MAC层至少可以根据选择的上述RACH类型(2步RACH或者4步RACH)，上述RACH的触发事件以及RRC层为随机接入过程配置的上述参数，来设置RACH参数的值，比如设置PREAMBLE_POWER_RAMPING_STEP，SCALING_FACTOR_BI和preambleTransMax的值，包括但不限于以下具体示例。
在示例一中，如果RA_TYPE被设置为2-stepRA，且如果随机接入过程是因为已有的触发事件(比如Initial access from RRC_IDLE，Transition from RRC_INACTIVE)被触发时，设置PREAMBLE_POWER_RAMPING_STEP to msgA-PreamblePowerRampingStep，设置SCALING_FACTOR_BI为1，运用RACH-ConfigGenericTwoStepRA中包含的preambleTransMax。
在示例二中，如果RA_TYPE被设置为2-stepRA，且如果随机接入过程是因为适用于所有广播多播业务的触发事件被触发(比如gain MBS Configuartion)，且如果RRC配置(比如RACH-ConfigCommonTwoStepRA)了适用于所有广播多播业务的RACH参数(比如powerRampingStepLowPriority-MBS，scalingFactorBI-MBS，preambleTransMax-MBS)时，设置PREAMBLE_POWER_RAMPING_STEP to powerRampingStepLowPriority-MBS，设置SCALING_FACTOR_BI为scalingFactorBI-MBS，运用preambleTransMax–MBS.
在示例三中，如果RA_TYPE被设置为4-stepRA，且如果随机接入过程是因为per广播多播业务的触发事件被触发(比如gain IPTV MBS Configuartion)，且如果RRC配置(比如RACH-ConfigCommon)了per广播多播业务的RACH参数(比如powerRampingStepLowPriority-IPTV，scalingFactorBI-IPTV，preambleTransMax-IPTV)时，设置PREAMBLE_POWER_RAMPING_STEP to powerRampingStepLowPriority-IPTV，设置SCALING_FACTOR_BI为scalingFactorBI-IPTV，运用preambleTransMax–IPTV。
由上可知，在本申请实施例的广播多播业务的拥塞控制方法中，考虑到Non-RRCConnected UE进入RRCConnected态主要需要执行RRC层的RRCconnection establishment过程(对于IDLE UE而言)或者RRC connection resume过程(对于Inactive UE而言)，MAC层的随机接入过程，这两个过程。那么，则可以通过在这两个过程中加入各种相互独立的子方案来实现MBS业务的拥塞控制，也就是说，RRC层的RRC connection establishment过程(对于IDLE UE而言)或者RRC connection resume过程(对于Inactive UE而言)中，执行针对广播多播业务的接入控制，MAC层的随机接入过程至少设置针对广播多播业务的powerRampingStep、scalingFactorBI、preambleTransMax三个RACH参数，以及所有的设置，分为适用于所有的广播多播业务，per广播多播业务，per广播多播业务组三种情况。如此，当对广播多播业务有需求的Non-RRC Connected UE的数量很大时，可以降低随机接入过程产生拥塞的概率，从而提高严重影响系统的性能。
参见图3所示，本申请实施例提供一种广播多播业务的拥塞控制方法，由通网络侧设备执行，该方法包括以下流程步骤。
步骤301：接收终端设备发送的第一过程对应的请求，所述第一过程用于供所述终端设备执行对广播多播业务的拥塞控制；其中，所述第一过程包括：第二过程和媒体接入控制MAC层的随机接入过程，所述第二过程包括无线资源控制RRC连接建立过程和RRC连接恢复过程中的至少一项。
在本申请实施例中，通过至少在RRC连接建立过程、RRC连接恢复过程和MAC层的随机接入过程中的一个或多个中实现对广播多播业务的拥塞控制，可以降低由于对广播多播业务有需求的且处于非RRC连接态的终端设备的数量较大，导致随机接入过程产生拥塞的概率，从而提高系统性能。
可选的，在本申请实施例的广播多播业务的拥塞控制方法中，在上述步骤301之前，该方法还可以包括以下内容。
配置第一门限值；将所述第一门限值发送至所述终端设备，所述第一门限值用于与所述终端设备选择的第一随机数的值进行比较，所述第一随机数的值用于供所述终端设备执行对广播多播业务的接入控制。
可选的，所述第一随机数的名称为以下至少一项：适用于所有广播多播业务的名称、基于每个广播多播业务单独设置的名称和基于每个广播多播业务组单独设置的名称。
可选的，所述第一门限值为以下至少一项：适用于所有广播多播业务的门限值、基于每个广播多播业务单独设置的门限值和基于每个广播多播业务组单独设置的门限值。
可选的，在本申请实施例的广播多播业务的拥塞控制方法中，在上述步骤301之前，该方法还可以包括以下内容：
配置第一接入控制定时器；将所述第一接入控制定时器发送至所述终端设备，所述第一接入控制定时器用于供所述终端设备确定接入尝试的接入禁止是否被减轻。
可选的，所述第一接入控制定时器的名称为以下至少一项：适用于所有广播多播业务的名称、基于每个广播多播业务单独设置的名称和基于每个广播多播业务组单独设置的名称。
可选的，所述第一接入控制定时器对应的定时时长计算公式与以下至少之一有关。
所述第一随机数的值；回退时间的值；其中，所述定时时长计算公式为以下至少一项：适用于所有广播多播业务的公式、基于每个广播多播业务单 独设置的公式和基于每个广播多播业务组单独设置的公式。
进一步可选的，在本申请实施例的广播多播业务的拥塞控制方法中，还可以包括以下内容。
配置所述回退时间的值；将所述回退时间的值发送至所述终端设备；其中，所述回退时间的值为以下至少一项：适用于所有广播多播业务的值、基于每个广播多播业务单独设置的值和基于每个广播多播业务组单独设置的值。
可选的，在本申请实施例的广播多播业务的拥塞控制方法中，在上述步骤301之前，该方法还可以包括以下内容。
配置所述MAC层的随机接入过程对应的广播多播业务相关的参数；将所述广播多播业务相关的参数发送至所述终端设备；其中，所述广播多播业务相关的参数包括以下至少一项：功率增长步长、回退参数BI缩放因子和随机接入导码最大传输次数。
可选的，所述广播多播业务相关的参数为以下至少一项：适用于所有广播多播业务的参数、基于每个广播多播业务单独设置的参数和基于每个广播多播业务组单独设置的参数。
可选的，所述广播多播业务相关的参数为以下至少一项：适用于所述MAC层的随机接入过程对应的所有随机接入类型的参数；基于所述MAC层的随机接入过程对应的每种随机接入类型单独设置的参数。
需要说明的是，本申请实施例的广播多播业务的拥塞控制方法中与上述终端设备侧执行的广播多播业务的拥塞控制方法中相同或类似的内容，可以参照上述图2对应由终端设备执行的广播多播业务的拥塞方法的实施例中的相应内容，在此不再赘述。
需要说明的是，本申请实施例提供的由终端设备执行的广播多播业务的拥塞控制方法，执行主体可以为广播多播业务的拥塞控制装置，或者，该广播多播业务的拥塞控制装置中的用于执行广播多播业务的拥塞控制方法的控制模块。本申请实施例中以广播多播业务的拥塞控制装置执行广播多播业务的拥塞控制方法为例，说明本申请实施例提供的广播多播业务的拥塞控制装 置。
参见图4所示，本申请实施例提供一种广播多播业务的拥塞控制装置400，应用于终端设备，该广播多播业务的拥塞控制装置400包括：控制模块401，用于在第一过程中执行对广播多播业务的拥塞控制；其中，所述第一过程包括：第二过程和媒体接入控制MAC层的随机接入过程，所述第二过程包括无线资源控制RRC连接建立过程和RRC连接恢复过程中的至少一项。
可选的，在本申请实施例的广播多播业务的拥塞控制装置400中，在所述第二过程中，所述终端设备发起所述第二过程的条件包括以下至少一项：所述终端设备执行广播多播业务会话加入过程时的第一条件；所述终端设备在广播多播业务会话加入过程完成后执行广播多播业务数据的接收时的第二条件。
可选的，在本申请实施例的广播多播业务的拥塞控制装置400中，所述第一条件包括以下至少一项：所述终端设备接收到广播多播业务信息；所述终端设备对所述广播多播业务信息对应的至少一个广播多播业务感兴趣；上层请求RRC连接的建立；上层请求RRC连接的恢复；所述终端设备具有广播多播业务能力；网络侧设备支持广播多播业务；所述终端设备接收到网络侧设备发送的会话开始通知；所述终端设备接收到网络侧设备发送的广播多播业务的控制信息。
可选的，在本申请实施例的广播多播业务的拥塞控制装置400中，所述第二条件包括以下至少一项：所述终端设备接收到网络侧设备发送的会话开始通知；所述终端设备具有广播多播业务能力；网络侧设备支持广播多播业务。
可选的，在本申请实施例的广播多播业务的拥塞控制装置400中，所述控制模块401，还可以用于在所述第二过程中，执行以下操作之一：不执行统一接入控制UAC过程；执行所述UAC过程。
可选的，在本申请实施例的广播多播业务的拥塞控制装置400中，所述控制模块401，在执行所述UAC过程的情况下，还可以用于执行以下操作之 一：当所述终端设备执行广播多播业务会话加入过程时，通过所述终端设备的非接入层NAS层或者RRC层决定接入控制对应的接入种类；当所述终端设备是在广播多播业务会话加入过程完成后执行MBS数据的接收时，通过所述终端设备的RRC层决定和设置接入控制对应的接入种类。
可选的，在本申请实施例的广播多播业务的拥塞控制装置400中，在执行所述UAC过程的情况下，接入控制对应的参数的值包括以下至少之一：第一值；与所述第一值不同的第二值；其中，所述接入控制对应的参数的值包括接入种类的值和接入识别的值中的至少一项；所述第二值为以下至少一项：适用于所有广播多播业务的值、基于每个广播多播业务单独设置的值和基于每个广播多播业务组单独设置的值。
可选的，在本申请实施例的广播多播业务的拥塞控制装置400中，所述控制模块401，还可以用于在所述第二过程中，执行对广播多播业务的接入控制。
可选的，本申请实施例的广播多播业务的拥塞控制装置400，还可以包括处理模块，所述处理模块用于：选择第一随机数的值，所述第一随机数的值用于供所述终端设备执行对广播多播业务的接入控制；在所述第一随机数的值低于第一门限值的情况下，认为接入尝试被禁止，否则认为接入尝试被允许。
可选的，本申请实施例的广播多播业务的拥塞控制装置400，还可以包括：接收模块，用于接收网络侧设备配置的所述第一门限值。
可选的，在本申请实施例的广播多播业务的拥塞控制装置400中，所述第一随机数的名称为以下至少一项：适用于所有广播多播业务的名称、基于每个广播多播业务单独设置的名称和基于每个广播多播业务组单独设置的名称。
可选的，在本申请实施例的广播多播业务的拥塞控制装置400中，所述第一门限值为以下至少一项：适用于所有广播多播业务的门限值、基于每个广播多播业务单独设置的门限值和基于每个广播多播业务组单独设置的门限 值。
可选的，在本申请实施例的广播多播业务的拥塞控制装置400中，所述处理模块，还可以用于：在认为接入尝试被禁止的情况下，开启第一接入控制定时器；在所述第一接入控制定时器超时后，认为接入尝试的接入禁止被减轻。
可选的，在本申请实施例的广播多播业务的拥塞控制装置400中，所述接收模块，还可以用于：接收网络侧设备配置的所述第一接入控制定时器。
可选的，在本申请实施例的广播多播业务的拥塞控制装置400中，所述第一接入控制定时器的名称为以下至少一项：适用于所有广播多播业务的名称、基于每个广播多播业务单独设置的名称和基于每个广播多播业务组单独设置的名称。
可选的，在本申请实施例的广播多播业务的拥塞控制装置400中，所述第一接入控制定时器对应的定时时长计算公式与以下至少之一有关：所述第一随机数的值；网络侧设备配置的回退时间的值；其中，所述定时时长计算公式为以下至少一项：适用于所有广播多播业务的公式、基于每个广播多播业务单独设置的公式和基于每个广播多播业务组单独设置的公式。
可选的，在本申请实施例的广播多播业务的拥塞控制装置400中，所述接收模块，还可以用于：接收网络侧配置的所述回退时间的值。
可选的，在本申请实施例的广播多播业务的拥塞控制装置400中，所述回退时间的值为以下至少一项：适用于所有广播多播业务的值、基于每个广播多播业务单独设置的值和基于每个广播多播业务组单独设置的值。
可选的，在本申请实施例的广播多播业务的拥塞控制装置400中，所述控制模块401，还可以用于在执行所述UAC过程的情况下，执行以下操作：在所述UAC过程接入尝试被禁止的情况下，不再执行对广播多播业务的接入控制；在所述UAC过程接入尝试被允许的情况下，立即执行对广播多播业务的接入控制。
可选的，在本申请实施例的广播多播业务的拥塞控制装置400中，所述 第二过程的发起原因包括以下至少一项：第一事件；与所述第一事件不同的第二事件；其中，所述第二事件为以下至少一项：适用于所有广播多播业务的事件、基于每个广播多播业务单独设置的事件和基于每个广播多播业务组单独设置的事件；其中，所述发起原因为以下至少一项：恢复原因resumeCause和建立原因establishmentCause。
可选的，在本申请实施例的广播多播业务的拥塞控制装置400中，所述MAC层的随机接入过程的触发事件包括以下至少一项：第三事件；与所述第三事件不同的第四事件；其中，所述第四事件为以下至少一项：适用于所有广播多播业务的事件、基于每个广播多播业务单独设置的事件和基于每个广播多播业务组单独设置的事件。
可选的，本申请实施例的广播多播业务的拥塞控制装置400，所述接收模块，还可以用于：接收网络侧设备为所述MAC层的随机接入过程配置的广播多播业务相关的参数；其中，所述广播多播业务相关的参数包括以下至少一项：功率增长步长、回退参数BI缩放因子和随机接入导码最大传输次数。
可选的，在本申请实施例的广播多播业务的拥塞控制装置400中，所述广播多播业务相关的参数为以下至少一项：适用于所有广播多播业务的参数、基于每个广播多播业务单独设置的参数和基于每个广播多播业务组单独设置的参数。
可选的，在本申请实施例的广播多播业务的拥塞控制装置400中，所述广播多播业务相关的参数为以下至少一项：适用于所述MAC层的随机接入过程对应的所有随机接入类型的参数；基于所述MAC层的随机接入过程对应的每种随机接入类型单独设置的参数。
可选的，在本申请实施例的广播多播业务的拥塞控制装置400中，所述处理模块，还可以用于：根据以下至少一项，设置所述广播多播业务相关的参数的值：随机接入类型；所述MAC层的随机接入过程的触发事件；网络侧设备是否为所述MAC层的随机接入过程配置广播多播业务相关的参数。
在本申请实施例中，可以至少在第二过程和媒体接入控制MAC层的随 机接入过程中的一个实现对广播多播业务的拥塞控制，其中，该第二过程包括无线资源控制RRC连接建立过程和RRC连接恢复过程中的至少一项。如此，通过至少在RRC连接建立过程、RRC连接恢复过程和MAC层的随机接入过程中的一个或多个中加入对广播多播业务的拥塞控制过程，可以降低由于对广播多播业务有需求的且处于非RRC连接态的终端设备的数量较大，导致随机接入过程产生拥塞的概率，从而提高系统性能。
本申请实施例中的广播多播业务的拥塞控制装置可以是装置，也可以是终端设备中的部件、集成电路、或芯片。该装置可以是移动终端，也可以为非移动终端。示例性的，移动终端可以包括但不限于上述所列举的终端11的类型，非移动终端可以为服务器、网络附属存储器(Network Attached Storage，NAS)、个人计算机(personal computer，PC)、电视机(television，TV)、柜员机或者自助机等，本申请实施例不作具体限定。
本申请实施例中的广播多播业务的拥塞控制装置可以为具有操作系统的装置。该操作系统可以为安卓(Android)操作系统，可以为ios操作系统，还可以为其他可能的操作系统，本申请实施例不作具体限定。
本申请实施例提供的广播多播业务的拥塞控制装置能够实现图2的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
需要说明的是，本申请实施例提供的由网络侧设备执行的广播多播业务的拥塞控制方法，执行主体可以为广播多播业务的拥塞控制装置，或者，该广播多播业务的拥塞控制装置中的用于执行广播多播业务的拥塞控制方法的控制模块。本申请实施例中以广播多播业务的拥塞控制装置执行广播多播业务的拥塞控制方法为例，说明本申请实施例提供的广播多播业务的拥塞控制装置。
参见图5所示，本申请实施例提供一种广播多播业务的拥塞控制装置500，应用于网络侧设备，该广播多播业务的拥塞控制装置500包括：接收模块501，用于接收终端设备发送的第一过程对应的请求，所述第一过程用于供所述终 端设备执行对广播多播业务的拥塞控制；其中，所述第一过程包括：第二过程和媒体接入控制MAC层的随机接入过程，所述第二过程包括无线资源控制RRC连接建立过程和RRC连接恢复过程中的至少一项。
可选的，本申请实施例的广播多播业务的拥塞控制装置500，还可以包括：第一处理模块，用于在所述接收终端设备发送的第一过程对应的请求之前，配置第一门限值；第一发送模块，用于将所述第一门限值发送至所述终端设备，所述第一门限值用于与所述终端设备选择的第一随机数的值进行比较，所述第一随机数的值用于供所述终端设备执行对广播多播业务的接入控制。
可选的，在本申请实施例的广播多播业务的拥塞控制装置500中，所述第一随机数的名称为以下至少一项：适用于所有广播多播业务的名称、基于每个广播多播业务单独设置的名称和基于每个广播多播业务组单独设置的名称。
可选的，在本申请实施例的广播多播业务的拥塞控制装置500中，所述第一门限值为以下至少一项：适用于所有广播多播业务的门限值、基于每个广播多播业务单独设置的门限值和基于每个广播多播业务组单独设置的门限值。
可选的，本申请实施例的广播多播业务的拥塞控制装置500，还可以包括：第二处理模块，用于在所述接收终端设备发送的第一过程对应的请求之前，配置第一接入控制定时器；第二发送模块，用于将所述第一接入控制定时器发送至所述终端设备，所述第一接入控制定时器用于供所述终端设备确定接入尝试的接入禁止是否被减轻。
可选的，在本申请实施例的广播多播业务的拥塞控制装置500中，所述第一接入控制定时器的名称为以下至少一项：适用于所有广播多播业务的名称、基于每个广播多播业务单独设置的名称和基于每个广播多播业务组单独设置的名称。
可选的，在本申请实施例的广播多播业务的拥塞控制装置500中，所述 第一接入控制定时器对应的定时时长计算公式与以下至少之一有关：所述第一随机数的值；回退时间的值；其中，所述定时时长计算公式为以下至少一项：适用于所有广播多播业务的公式、基于每个广播多播业务单独设置的公式和基于每个广播多播业务组单独设置的公式。
可选的，在本申请实施例的广播多播业务的拥塞控制装置500中，所述第二处理模块，还用于配置所述回退时间的值；所述第二发送模块，还用于将所述回退时间的值发送至所述终端设备；其中，所述回退时间的值为以下至少一项：适用于所有广播多播业务的值、基于每个广播多播业务单独设置的值和基于每个广播多播业务组单独设置的值。
可选的，本申请实施例的广播多播业务的拥塞控制装置500，还可以包括：第三处理模块，用于在所述接收终端设备发送的第一过程对应的请求之前，配置所述MAC层的随机接入过程对应的广播多播业务相关的参数；第三发送模块，用于将所述广播多播业务相关的参数发送至所述终端设备；其中，所述广播多播业务相关的参数包括以下至少一项：功率增长步长、回退参数BI缩放因子和随机接入导码最大传输次数。
可选的，在本申请实施例的广播多播业务的拥塞控制装置500中，所述广播多播业务相关的参数为以下至少一项：适用于所有广播多播业务的参数、基于每个广播多播业务单独设置的参数和基于每个广播多播业务组单独设置的参数。
可选的，在本申请实施例的广播多播业务的拥塞控制装置500中，所述广播多播业务相关的参数为以下至少一项：适用于所述MAC层的随机接入过程对应的所有随机接入类型的参数；基于所述MAC层的随机接入过程对应的每种随机接入类型单独设置的参数。
在本申请实施例中，通过至少在RRC连接建立过程、RRC连接恢复过程和MAC层的随机接入过程中的一个或多个中实现对广播多播业务的拥塞控制，可以降低由于对广播多播业务有需求的且处于非RRC连接态的终端设备的数量较大，导致随机接入过程产生拥塞的概率，从而提高系统性能。
本申请实施例中的广播多播业务的拥塞控制装置可以是装置，也可以是网络侧设备中的部件、集成电路、或芯片。该装置可以是网络侧设备。示例性的，网络侧设备可以包括但不限于上述所列举的网络侧设备12的类型。
本申请实施例中的广播多播业务的拥塞控制装置可以为具有操作系统的装置。该操作系统可以为安卓(Android)操作系统，可以为ios操作系统，还可以为其他可能的操作系统，本申请实施例不作具体限定。
本申请实施例提供的广播多播业务的拥塞控制装置能够实现图3的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
可选的，如图6所示，本申请实施例还提供一种通信设备600，包括处理器601，存储器602，存储在存储器602上并可在所述处理器601上运行的程序或指令，例如，该通信设备600为终端时，该程序或指令被处理器601执行时实现上述图2对应的广播多播业务的拥塞控制方法实施例的各个过程，且能达到相同的技术效果。该通信设备600为网络侧设备时，该程序或指令被处理器601执行时实现上述图3对应的广播多播业务的拥塞控制方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
图7为实现本申请实施例的一种终端的硬件结构示意图。
该终端700包括但不限于：射频单元701、网络模块702、音频输出单元703、输入单元704、传感器705、显示单元706、用户输入单元707、接口单元708、存储器709、以及处理器710等部件。
本领域技术人员可以理解，终端700还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器710逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。图7中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元704可以包括图形处理器(Graphics Processing Unit，GPU)7041和麦克风7042，图形处理器7041对 在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元706可包括显示面板7061，可以采用液晶显示器、有机发光二极管等形式来配置显示面板7061。用户输入单元707包括触控面板7071以及其他输入设备7072。触控面板7071，也称为触摸屏。触控面板7071可包括触摸检测装置和触摸控制器两个部分。其他输入设备7072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元701将来自网络侧设备的下行数据接收后，给处理器710处理；另外，将上行的数据发送给网络侧设备。通常，射频单元701包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器709可用于存储软件程序或指令以及各种数据。存储器709可主要包括存储程序或指令区和存储数据区，其中，存储程序或指令区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器709可以包括高速随机存取存储器，还可以包括非易失性存储器，其中，非易失性存储器可以是只读存储器(Read-OnlyMemory，ROM)、可编程只读存储器(ProgrammableROM，PROM)、可擦除可编程只读存储器(ErasablePROM，EPROM)、电可擦除可编程只读存储器(ElectricallyEPROM，EEPROM)或闪存。例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。
处理器710可包括一个或多个处理单元；可选的，处理器710可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界面和应用程序或指令等，调制解调处理器主要处理无线通信，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器710中。
其中，处理器710，用于在第一过程中执行对广播多播业务的拥塞控制；其中，所述第一过程包括：第二过程和媒体接入控制MAC层的随机接入过程，所述第二过程包括无线资源控制RRC连接建立过程和RRC连接恢复过 程中的至少一项。
在本申请实施例中，可以至少在第二过程和媒体接入控制MAC层的随机接入过程中的一个实现对广播多播业务的拥塞控制，其中，该第二过程包括无线资源控制RRC连接建立过程和RRC连接恢复过程中的至少一项。如此，通过至少在RRC连接建立过程、RRC连接恢复过程和MAC层的随机接入过程中的一个或多个中加入对广播多播业务的拥塞控制过程，可以降低由于对广播多播业务有需求的且处于非RRC连接态的终端设备的数量较大，导致随机接入过程产生拥塞的概率，从而提高系统性能。
本申请实施例还提供了一种网络侧设备。如图8所示，该网络侧设备800包括：天线801、射频装置802、基带装置803。天线801与射频装置802连接。在上行方向上，射频装置802通过天线801接收信息，将接收的信息发送给基带装置803进行处理。在下行方向上，基带装置803对要发送的信息进行处理，并发送给射频装置802，射频装置802对收到的信息进行处理后经过天线801发送出去。
上述频带处理装置可以位于基带装置803中，以上实施例中网络侧设备执行的方法可以在基带装置803中实现，该基带装置803包括处理器804和存储器805。
基带装置803例如可以包括至少一个基带板，该基带板上设置有多个芯片，如图8所示，其中一个芯片例如为处理器804，与存储器805连接，以调用存储器805中的程序，执行以上方法实施例中所示的网络侧设备操作。
该基带装置803还可以包括网络接口806，用于与射频装置802交互信息，该接口例如为通用公共无线接口(common public radio interface，简称CPRI)。
具体地，本发明实施例的网络侧设备还包括：存储在存储器805上并可在处理器804上运行的指令或程序，处理器804调用存储器805中的指令或程序执行图5所示各模块执行的方法，并达到相同的技术效果，为避免重复，故不在此赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述任一广播多播业务的拥塞控制方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，所述处理器为上述实施例中所述的终端或网络侧设备中的处理器。所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等。
本申请实施例另提供了一种计算机程序产品，所述计算机程序产品存储在非易失性的可读存储介质，所述计算机程序产品被所述处理器执行时，实现上述任一广播多播业务的拥塞控制方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行终端设备或网络侧设备程序或指令，实现上述各对应的广播多播业务的拥塞控制方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省 去、或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络侧设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (51)

  1. 一种广播多播业务的拥塞控制方法，应用于终端设备，所述方法包括：
    在第一过程中执行对广播多播业务的拥塞控制；其中，所述第一过程包括：第二过程和媒体接入控制MAC层的随机接入过程，所述第二过程包括无线资源控制RRC连接建立过程和RRC连接恢复过程中的至少一项。
  2. 根据权利要求1所述的方法，其中，在所述第二过程中，所述终端设备发起所述第二过程的条件包括以下至少一项：
    所述终端设备执行广播多播业务会话加入过程时的第一条件；
    所述终端设备在广播多播业务会话加入过程完成后执行广播多播业务数据的接收时的第二条件。
  3. 根据权利要求2所述的方法，其中，所述第一条件包括以下至少一项：
    所述终端设备接收到广播多播业务信息；
    所述终端设备对所述广播多播业务信息对应的至少一个广播多播业务感兴趣；
    上层请求RRC连接的建立；
    上层请求RRC连接的恢复；
    所述终端设备具有广播多播业务能力；
    网络侧设备支持广播多播业务；
    所述终端设备接收到网络侧设备发送的会话开始通知；
    所述终端设备接收到网络侧设备发送的广播多播业务的控制信息。
  4. 根据权利要求2所述的方法，其中，所述第二条件包括以下至少一项：
    所述终端设备接收到网络侧设备发送的会话开始通知；
    所述终端设备具有广播多播业务能力；
    网络侧设备支持广播多播业务。
  5. 根据权利要求1所述的方法，其中，在所述第二过程中，所述方法还包括以下之一：
    不执行统一接入控制UAC过程；
    执行所述UAC过程。
  6. 根据权利要求5所述的方法，其中，在执行所述UAC过程的情况下，所述方法还包括以下至少之一：
    当所述终端设备执行广播多播业务会话加入过程时，由所述终端设备的非接入层NAS层或者RRC层决定接入控制对应的接入种类；
    当所述终端设备是在广播多播业务会话加入过程完成后执行MBS数据的接收时，由所述终端设备的RRC层决定和设置接入控制对应的接入种类。
  7. 根据权利要求5所述的方法，其中，在执行所述UAC过程的情况下，接入控制对应的参数的值包括以下至少之一：
    第一值；
    与所述第一值不同的第二值；
    其中，所述接入控制对应的参数的值包括接入种类的值和接入识别的值中的至少一项；所述第二值为以下至少一项：适用于所有广播多播业务的值、基于每个广播多播业务单独设置的值和基于每个广播多播业务组单独设置的值。
  8. 根据权利要求1所述的方法，其中，在所述第二过程中，所述方法还包括：
    执行对广播多播业务的接入控制。
  9. 根据权利要求8所述的方法，其中，所述方法还包括：
    选择第一随机数的值，所述第一随机数的值用于供所述终端设备执行对广播多播业务的接入控制；
    在所述第一随机数的值低于第一门限值的情况下，认为接入尝试被禁止，否则认为接入尝试被允许。
  10. 根据权利要求9所述的方法，其中，所述方法还包括：
    接收网络侧设备配置的所述第一门限值。
  11. 根据权利要求9所述的方法，其中，所述第一随机数的名称为以下至少一项：适用于所有广播多播业务的名称、基于每个广播多播业务单独设 置的名称和基于每个广播多播业务组单独设置的名称。
  12. 根据权利要求9所述的方法，其中，所述第一门限值为以下至少一项：适用于所有广播多播业务的门限值、基于每个广播多播业务单独设置的门限值和基于每个广播多播业务组单独设置的门限值。
  13. 根据权利要求9所述的方法，其中，所述方法还包括：
    在认为接入尝试被禁止的情况下，开启第一接入控制定时器；
    在所述第一接入控制定时器超时后，认为接入尝试的接入禁止被减轻。
  14. 根据权利要求13所述的方法，其中，所述方法还包括：
    接收网络侧设备配置的所述第一接入控制定时器。
  15. 根据权利要求13所述的方法，其中，所述第一接入控制定时器的名称为以下至少一项：适用于所有广播多播业务的名称、基于每个广播多播业务单独设置的名称和基于每个广播多播业务组单独设置的名称。
  16. 根据权利要求13所述的方法，其中，所述第一接入控制定时器对应的定时时长计算公式与以下至少之一有关：
    所述第一随机数的值；
    网络侧设备配置的回退时间的值；
    其中，所述定时时长计算公式为以下至少一项：适用于所有广播多播业务的公式、基于每个广播多播业务单独设置的公式和基于每个广播多播业务组单独设置的公式。
  17. 根据权利要求16所述的方法，其中，所述方法还包括：
    接收网络侧配置的所述回退时间的值。
  18. 根据权利要求16所述的方法，其中，所述回退时间的值为以下至少一项：
    适用于所有广播多播业务的值、基于每个广播多播业务单独设置的值和基于每个广播多播业务组单独设置的值。
  19. 根据权利要求1、5或8所述的方法，其中，在执行所述UAC过程的情况下，所述方法还包括：
    在所述UAC过程接入尝试被禁止的情况下，不再执行对广播多播业务的接入控制；
    在所述UAC过程接入尝试被允许的情况下，立即执行对广播多播业务的接入控制。
  20. 根据权利要求1所述的方法，其中，所述第二过程的发起原因包括以下至少一项：
    第一事件；
    与所述第一事件不同的第二事件；其中，所述第二事件为以下至少一项：适用于所有广播多播业务的事件、基于每个广播多播业务单独设置的事件和基于每个广播多播业务组单独设置的事件；
    其中，所述发起原因为以下至少一项：恢复原因resumeCause和建立原因establishmentCause。
  21. 根据权利要求1所述的方法，其中，所述MAC层的随机接入过程的触发事件包括以下至少一项：
    第三事件；
    与所述第三事件不同的第四事件；其中，所述第四事件为以下至少一项：适用于所有广播多播业务的事件、基于每个广播多播业务单独设置的事件和基于每个广播多播业务组单独设置的事件。
  22. 根据权利要求1所述的方法，其中，所述方法还包括：
    接收网络侧设备为所述MAC层的随机接入过程配置的广播多播业务相关的参数；
    其中，所述广播多播业务相关的参数包括以下至少一项：功率增长步长、回退参数BI缩放因子和随机接入导码最大传输次数。
  23. 根据权利要求22所述的方法，其中，所述广播多播业务相关的参数为以下至少一项：
    适用于所有广播多播业务的参数、基于每个广播多播业务单独设置的参数和基于每个广播多播业务组单独设置的参数。
  24. 根据权利要求22所述的方法，其中，所述广播多播业务相关的参数为以下至少一项：
    适用于所述MAC层的随机接入过程对应的所有随机接入类型的参数；
    基于所述MAC层的随机接入过程对应的每种随机接入类型单独设置的参数。
  25. 根据权利要求21-24中任一项所述的方法，其中，所述方法还包括：
    根据以下至少一项，设置所述广播多播业务相关的参数的值：
    随机接入类型；
    所述MAC层的随机接入过程的触发事件；
    网络侧设备是否为所述MAC层的随机接入过程配置广播多播业务相关的参数。
  26. 一种广播多播业务的拥塞控制方法，应用于网络侧设备，所述方法包括：
    接收终端设备发送的第一过程对应的请求，所述第一过程用于供所述终端设备执行对广播多播业务的拥塞控制；
    其中，所述第一过程包括：第二过程和媒体接入控制MAC层的随机接入过程，所述第二过程包括无线资源控制RRC连接建立过程和RRC连接恢复过程中的至少一项。
  27. 根据权利要求26所述的方法，其中，在所述接收终端设备发送的第一过程对应的请求的步骤之前，所述方法还包括：
    配置第一门限值；
    将所述第一门限值发送至所述终端设备，所述第一门限值用于与所述终端设备选择的第一随机数的值进行比较，所述第一随机数的值用于供所述终端设备执行对广播多播业务的接入控制。
  28. 根据权利要求27所述的方法，其中，所述第一随机数的名称为以下至少一项：
    适用于所有广播多播业务的名称、基于每个广播多播业务单独设置的名 称和基于每个广播多播业务组单独设置的名称。
  29. 根据权利要求27所述的方法，其中，所述第一门限值为以下至少一项：
    适用于所有广播多播业务的门限值、基于每个广播多播业务单独设置的门限值和基于每个广播多播业务组单独设置的门限值。
  30. 根据权利要求26所述的方法，其中，在所述接收终端设备发送的第一过程对应的请求的步骤之前，所述方法还包括：
    配置第一接入控制定时器；
    将所述第一接入控制定时器发送至所述终端设备，所述第一接入控制定时器用于供所述终端设备确定接入尝试的接入禁止是否被减轻。
  31. 根据权利要求30所述的方法，其中，所述第一接入控制定时器的名称为以下至少一项：
    适用于所有广播多播业务的名称、基于每个广播多播业务单独设置的名称和基于每个广播多播业务组单独设置的名称。
  32. 根据权利要求30所述的方法，其中，所述第一接入控制定时器对应的定时时长计算公式与以下至少之一有关：
    第一随机数的值；
    回退时间的值；
    其中，所述定时时长计算公式为以下至少一项：适用于所有广播多播业务的公式、基于每个广播多播业务单独设置的公式和基于每个广播多播业务组单独设置的公式。
  33. 根据权利要求32所述的方法，其中，所述方法还包括：
    配置所述回退时间的值；
    将所述回退时间的值发送至所述终端设备；
    其中，所述回退时间的值为以下至少一项：适用于所有广播多播业务的值、基于每个广播多播业务单独设置的值和基于每个广播多播业务组单独设置的值。
  34. 根据权利要求26所述的方法，其中，在所述接收终端设备发送的第一过程对应的请求的步骤之前，所述方法还包括：
    配置所述MAC层的随机接入过程对应的广播多播业务相关的参数；
    将所述广播多播业务相关的参数发送至所述终端设备；
    其中，所述广播多播业务相关的参数包括以下至少一项：功率增长步长、回退参数BI缩放因子和随机接入导码最大传输次数。
  35. 根据权利要求34所述的方法，其中，所述广播多播业务相关的参数为以下至少一项：
    适用于所有广播多播业务的参数、基于每个广播多播业务单独设置的参数和基于每个广播多播业务组单独设置的参数。
  36. 根据权利要求34所述的方法，其中，所述广播多播业务相关的参数为以下至少一项：
    适用于所述MAC层的随机接入过程对应的所有随机接入类型的参数；
    基于所述MAC层的随机接入过程对应的每种随机接入类型单独设置的参数。
  37. 一种广播多播业务的拥塞控制装置，应用于终端设备，所述装置包括：
    控制模块，用于在第一过程中执行对广播多播业务的拥塞控制；其中，所述第一过程包括：第二过程和媒体接入控制MAC层的随机接入过程，所述第二过程包括无线资源控制RRC连接建立过程和RRC连接恢复过程中的至少一项。
  38. 根据权利要求37所述的装置，其中，所述控制模块，还用于在所述第二过程中，执行以下操作之一：
    不执行统一接入控制UAC过程；
    执行所述UAC过程。
  39. 根据权利要求37所述的装置，其中，所述控制模块，还用于在所述第二过程中，执行对广播多播业务的接入控制。
  40. 根据权利要求37-39中任一项所述的装置，其中，所述控制模块，还用于在执行所述UAC过程的情况下，执行以下操作：
    在所述UAC过程接入尝试被禁止的情况下，不再执行对广播多播业务的接入控制；
    在所述UAC过程接入尝试被允许的情况下，立即执行对广播多播业务的接入控制。
  41. 根据权利要求37所述的装置，其中，所述装置还包括：
    接收模块，用于接收网络侧设备为所述MAC层的随机接入过程配置的广播多播业务相关的参数；
    其中，所述广播多播业务相关的参数包括以下至少一项：功率增长步长、回退参数BI缩放因子和随机接入导码最大传输次数。
  42. 一种广播多播业务的拥塞控制装置，应用于网络侧设备，所述装置包括：
    接收模块，用于接收终端设备发送的第一过程对应的请求，所述第一过程用于供所述终端设备执行对广播多播业务的拥塞控制；
    其中，所述第一过程包括：第二过程和媒体接入控制MAC层的随机接入过程，所述第二过程包括无线资源控制RRC连接建立过程和RRC连接恢复过程中的至少一项。
  43. 根据权利要求42所述的装置，其中，所述装置还包括：
    第一处理模块，用于在所述接收终端设备发送的第一过程对应的请求之前，配置第一门限值；
    第一发送模块，用于将所述第一门限值发送至所述终端设备，所述第一门限值用于与所述终端设备选择的第一随机数的值进行比较，所述第一随机数的值用于供所述终端设备执行对广播多播业务的接入控制。
  44. 根据权利要求42所述的装置，其中，所述装置还包括：
    第二处理模块，用于在所述接收终端设备发送的第一过程对应的请求之前，配置第一接入控制定时器；
    第二发送模块，用于将所述第一接入控制定时器发送至所述终端设备，所述第一接入控制定时器用于供所述终端设备确定接入尝试的接入禁止是否被减轻。
  45. 根据权利要求42所述的装置，其中，所述装置还包括：
    第三处理模块，用于在所述接收终端设备发送的第一过程对应的请求之前，配置所述MAC层的随机接入过程对应的广播多播业务相关的参数；
    第三发送模块，用于将所述广播多播业务相关的参数发送至所述终端设备；
    其中，所述广播多播业务相关的参数包括以下至少一项：功率增长步长、回退参数BI缩放因子和随机接入导码最大传输次数。
  46. 一种终端设备，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被处理器执行时实现如权利要求1至25中任一项所述的广播多播业务的拥塞控制方法的步骤。
  47. 一种网络侧设备，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求26至36中任一项所述的广播多播业务的拥塞控制方法的步骤。
  48. 一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如权利要求所述程序或指令被处理器执行时实现如权利要求1至25中任一项所述的广播多播业务的拥塞控制方法的步骤，或者所述程序或指令被处理器执行时实现如权利要求26至36中任一项所述的广播多播业务的拥塞控制方法的步骤。
  49. 一种计算机程序产品，所述计算机程序产品存储在非易失性的可读存储介质，所述计算机程序产品被所述处理器执行时，实现如权利要求1至25中任一项所述的广播多播业务的拥塞控制方法的步骤，或者所述程序或指令被处理器执行时实现如权利要求26至36中任一项所述的广播多播业务的拥塞控制方法的步骤。
  50. 一种终端设备，其特征在于，所述终端设备被配置成用于执行如权利要求1至25中任一项所述的广播多播业务的拥塞控制方法的步骤。
  51. 一种网络侧设备，其特征在于，所述网络侧设备被配置成用于执行如权利要求26至36中任一项所述的广播多播业务的拥塞控制方法的步骤。
PCT/CN2021/120143 2020-09-30 2021-09-24 广播多播业务的拥塞控制方法、装置和设备 WO2022068679A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011063156.6 2020-09-30
CN202011063156.6A CN114339616B (zh) 2020-09-30 2020-09-30 广播多播业务的拥塞控制方法、装置和设备

Publications (1)

Publication Number Publication Date
WO2022068679A1 true WO2022068679A1 (zh) 2022-04-07

Family

ID=80949605

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/120143 WO2022068679A1 (zh) 2020-09-30 2021-09-24 广播多播业务的拥塞控制方法、装置和设备

Country Status (2)

Country Link
CN (1) CN114339616B (zh)
WO (1) WO2022068679A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024021007A1 (zh) * 2022-07-29 2024-02-01 Oppo广东移动通信有限公司 通信方法及通信装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1819697A (zh) * 2005-02-07 2006-08-16 上海贝尔阿尔卡特股份有限公司 多媒体广播和组播业务中小区拥塞和重同步的处理
CN108093433A (zh) * 2016-11-21 2018-05-29 中国移动通信有限公司研究院 无线网络拥塞处理方法及装置
US20200178162A1 (en) * 2017-06-16 2020-06-04 Telefonaktiebolaget Lm Ericsson (Publ) Method for Access Barring

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050243721A1 (en) * 2004-04-29 2005-11-03 Zhijun Cai Method and apparatus for controlling access to a multimedia broadcast/multicast service
CN101064864A (zh) * 2006-04-28 2007-10-31 大唐移动通信设备有限公司 一种mbms业务中计数及其接入控制方法
CN101925151A (zh) * 2009-06-12 2010-12-22 华为技术有限公司 接入控制方法、设备及系统
CN102291780B (zh) * 2010-06-21 2015-09-16 中兴通讯股份有限公司 小区公共信息的配置方法及系统
CN102378112B (zh) * 2010-08-12 2016-06-15 中兴通讯股份有限公司 多媒体广播多播业务中统计用户设备信息的方法和系统
CN102378111A (zh) * 2010-08-12 2012-03-14 中兴通讯股份有限公司 多媒体广播多播业务中统计用户设备信息的方法和系统
WO2015065053A1 (en) * 2013-10-31 2015-05-07 Lg Electronics Inc. Method of receiving mbms service in wireless communication system and apparatus thereof
CN104936149A (zh) * 2014-03-19 2015-09-23 中兴通讯股份有限公司 一种实现mbms最小化路测配置的方法、系统及设备
JP2018537874A (ja) * 2015-09-30 2018-12-20 グァンドン オッポ モバイル テレコミュニケーションズ コーポレーション リミテッド サービスベアリング輻輳制御方法及び装置
CN108271213B (zh) * 2017-01-04 2021-06-22 华为技术有限公司 通信控制方法、非授权传输方法及装置
WO2019243976A1 (en) * 2018-06-21 2019-12-26 Telefonaktiebolaget Lm Ericsson (Publ) Stop of barring timers

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1819697A (zh) * 2005-02-07 2006-08-16 上海贝尔阿尔卡特股份有限公司 多媒体广播和组播业务中小区拥塞和重同步的处理
CN108093433A (zh) * 2016-11-21 2018-05-29 中国移动通信有限公司研究院 无线网络拥塞处理方法及装置
US20200178162A1 (en) * 2017-06-16 2020-06-04 Telefonaktiebolaget Lm Ericsson (Publ) Method for Access Barring

Also Published As

Publication number Publication date
CN114339616A (zh) 2022-04-12
CN114339616B (zh) 2023-03-10

Similar Documents

Publication Publication Date Title
WO2022042752A1 (zh) 物理下行控制信道的监听方法、装置和设备
WO2022033531A1 (zh) 传输系统消息的方法、终端设备和网络设备
WO2022152275A1 (zh) Msg3传输方法、装置、设备及存储介质
WO2022017359A1 (zh) 直接通信启动控制方法及相关设备
WO2022028539A1 (zh) 信息传输方法、装置、终端及网络侧设备
WO2022022636A1 (zh) 初始接入方法及装置、终端及网络侧设备
WO2022068679A1 (zh) 广播多播业务的拥塞控制方法、装置和设备
WO2022022488A1 (zh) 传输辅助信息的方法、终端设备和网络设备
WO2022017360A1 (zh) 直接通信启动控制方法及相关设备
US20230328789A1 (en) Busy indication transmission method and apparatus
US20230262654A1 (en) Paging message receiving method, paging configuration method, terminal, and network side device
US20230180303A1 (en) Uplink timing advance value processing method, apparatus, and terminal
WO2022213982A1 (zh) 配置方法、装置及设备
WO2022148431A1 (zh) 非连续接收drx配置切换的方法、装置及终端
WO2022068813A1 (zh) 拥塞控制方法、装置、终端及网络侧设备
WO2022017481A1 (zh) 业务传输资源的更新方法、终端及网络侧设备
WO2022022685A1 (zh) 接入控制方法、终端及网络侧设备
CN113905452A (zh) 消息发送方法、接收方法、装置及通信设备
WO2022007785A1 (zh) 消息发送方法、接收方法、装置及通信设备
WO2022267948A1 (zh) 数据传输方法、装置及终端
US20230156550A1 (en) Connection establishment method and device
WO2022127693A1 (zh) 无线资源控制连接方法、装置及终端
WO2023066129A1 (zh) 信息上报方法、设备及可读存储介质
WO2022143975A1 (zh) 搜索空间组切换方法和设备
WO2022017506A1 (zh) 业务的处理方法、装置及相关设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21874340

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21874340

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 21874340

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 06/11/2023)