CN114339616B

CN114339616B - Congestion control method, device and equipment for broadcast multicast service

Info

Publication number: CN114339616B
Application number: CN202011063156.6A
Authority: CN
Inventors: 钟婷婷; 吴昱民; 刘佳敏
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2020-09-30
Filing date: 2020-09-30
Publication date: 2023-03-10
Anticipated expiration: 2040-09-30
Also published as: CN114339616A; WO2022068679A1

Abstract

The application discloses a congestion control method, a congestion control device and congestion control equipment for broadcast multicast services, and belongs to the field of communication. Wherein the method comprises the following steps: performing congestion control on the broadcast multicast service in a first process; wherein the first process comprises: a second procedure and a random access procedure of a media access control, MAC, layer, the second procedure comprising at least one of a radio resource control, RRC, connection establishment procedure and an RRC connection recovery procedure. By adopting the embodiment of the application, the congestion control process of the broadcast multicast service is added in one or more of the RRC connection establishment process, the RRC connection recovery process and the random access process of the MAC layer, so that the probability of congestion generated in the random access process due to the large number of terminal equipment which is in a non-RRC connection state and has a demand on the broadcast multicast service can be reduced, and the system performance is improved.

Description

Congestion control method, device and equipment for broadcast multicast service

Technical Field

The present application relates to the field of communications, and in particular, to a congestion control method, apparatus and device for a broadcast multicast service.

Background

Currently, in a New Radio (NR) system, for a broadcast Multicast service, such as an MBS (Multicast/broadcast service) service, a User Equipment (UE, which may also be referred to as a terminal device, a User terminal, a mobile terminal, etc.) interested in a Non-Radio Resource control connected (Non-Radio Resource controlled connected) User Equipment needs to enter an RRC connected state to execute an MBS session join (session join) process; and when the MBS service uses a dedicated RRC signaling (dedicatedly signaling) to send control information of the MBS or when data of the MBS service needs to be sent in a Point-to-Point (PTP) manner on a Radio Access Network (RAN) side, the UE also needs to enter an RRC connection state to obtain the control information of the MBS or receive the data of the MBS.

However, when the number of UEs in the non-RRC connected state is large and there is a demand for the broadcast multicast service, congestion is easily caused in the random access procedure, thereby seriously affecting the performance of the system.

Disclosure of Invention

The embodiment of the application provides a congestion control method, a congestion control device and congestion control equipment for broadcast multicast services, so that the problem that congestion is easily caused in a random access process when the number of UEs which are in a non-RRC (radio resource control) connection state and have requirements on the broadcast multicast services is large can be solved.

In a first aspect, a congestion control method for broadcast multicast service is provided, which is applied to a terminal device, and the method includes:

performing congestion control on the broadcast multicast service in a first process; wherein the first process comprises: a second procedure and a random access procedure of a media access control, MAC, layer, the second procedure comprising at least one of a radio resource control, RRC, connection establishment procedure and an RRC connection recovery procedure.

In a second aspect, a congestion control apparatus for broadcast multicast service is provided, which is applied to a terminal device, and the apparatus includes:

the control module is used for executing congestion control on the broadcast multicast service in a first process; wherein the first process comprises: a second procedure and a random access procedure of a media access control, MAC, layer, the second procedure comprising at least one of a radio resource control, RRC, connection establishment procedure and an RRC connection recovery procedure.

In a third aspect, a terminal device is provided, which includes: memory, processor and program or instructions stored on the memory and executable on the processor, which when executed by the processor, implement the steps of the method of congestion control of broadcast multicast traffic as described in the first aspect.

In a fourth aspect, a congestion control method for a broadcast multicast service is provided, which is applied to a network side device, and the method includes:

receiving a request corresponding to a first process sent by a terminal device, wherein the first process is used for the terminal device to execute congestion control on a broadcast multicast service; wherein the first process comprises: a second procedure and a random access procedure of a media access control, MAC, layer, the second procedure comprising at least one of a radio resource control, RRC, connection establishment procedure and an RRC connection recovery procedure.

In a fifth aspect, a congestion control apparatus for broadcast multicast service is provided, which is applied to a network side device, and includes:

a receiving module, configured to 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 comprises: a second procedure and a random access procedure of a media access control, MAC, layer, the second procedure comprising at least one of a radio resource control, RRC, connection establishment procedure and an RRC connection recovery procedure.

A sixth aspect provides a network side device, comprising: a memory, a processor and a program or instructions stored on the memory and executable on the processor, which when executed by the processor, implement the steps of the congestion control method for broadcast multicast service according to the fourth aspect.

In a seventh aspect, a readable storage medium is provided, on which a program or instructions are stored, which when executed by a processor implement the steps of the congestion control method for broadcast multicast service according to the first aspect, or which when executed by a processor implement the steps of the congestion control method for broadcast multicast service according to the fourth aspect.

In an eighth aspect, a computer program product is provided, which comprises a processor, a memory, and a program or instructions stored on the memory and executable on the processor, the program or instructions when executed by the processor implementing the steps of the congestion control method for broadcast multicast service according to the first aspect, or the program or instructions when executed by the processor implementing the steps of the congestion control method for broadcast multicast service according to the fourth aspect.

In a ninth aspect, a chip is provided, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a terminal device or a network-side device program or instruction, implement the steps of the congestion control method for broadcast and multicast services according to the first aspect, or implement the steps of the congestion control method for broadcast and multicast services according to the fourth aspect.

In the embodiment of the present application, the congestion control for the broadcast multicast service may be implemented at least in one of a second procedure and a random access procedure of a medium access control MAC layer, wherein the second procedure includes at least one of a radio resource control RRC connection establishment procedure and an RRC connection recovery procedure. In this way, by adding the congestion control process 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, the probability of congestion occurring in the random access process due to a large number of terminal devices that are in a non-RRC connected state and are in need of the broadcast multicast service can be reduced, thereby improving system performance.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

FIG. 1 illustrates a block diagram of a wireless communication system to which embodiments of the present application are applicable;

fig. 2 is a flowchart illustrating a congestion control method for broadcast multicast service in an embodiment of the present application;

fig. 3 is a schematic flowchart of another congestion control method for broadcast multicast service in an embodiment of the present application;

fig. 4 is a schematic structural diagram of a congestion control apparatus for broadcast multicast service in an embodiment of the present application;

fig. 5 is a schematic structural diagram of another congestion control apparatus for 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 device in this embodiment.

Detailed Description

The technical solutions in the embodiments of the present application will be described clearly below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application are within the scope of protection of the present application.

The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It should be understood that the data so used are interchangeable under appropriate circumstances such that embodiments of the application can be practiced in sequences other than those illustrated or described herein, and the terms "first" and "second" used herein generally do not denote any order, nor do they denote any order, for example, the first object may be one or more. In addition, "and/or" in the specification and claims means at least one of connected objects, and a character "/" generally means that the former and latter related objects are in an "or" relationship.

It is noted that the techniques described in the embodiments of the present application are not limited to Long Term Evolution (LTE)/LTE-Advanced (LTE-a) systems, but may also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), time Division Multiple Access (TDMA), frequency Division Multiple Access (Frequency Division Multiple Access), and the likeion Multiple Access, FDMA), orthogonal Frequency Division Multiple Access (OFDMA), single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described techniques can be used for both the above-mentioned systems and radio technologies, as well as for other systems and radio technologies. However, the following description describes a New Radio (NR) system for purposes of example, and NR terminology is used in much of the description below, and the techniques may also be applied to applications other than NR system applications, such as 6 th generation (6 th generation) NR systems ^th Generation, 6G) communication system.

Fig. 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable. The wireless communication system includes a terminal 11 and a network-side device 12. Wherein, the terminal 11 may also be called a terminal Device or a User Equipment (UE), the terminal 11 may be a Mobile phone, a Tablet Personal Computer (Tablet Personal Computer), a Laptop Computer (Laptop Computer) or a notebook Computer, a Personal Digital Assistant (PDA), a palmtop Computer, a netbook, an ultra-Mobile Personal Computer (UMPC), a Mobile Internet Device (MID), a Wearable Device (Wearable Device) or a Vehicle-mounted Device (vehicular UE, VUE), a Pedestrian terminal (Wearable UE, PUE), and other terminal side devices, and the terminal Device includes: bracelets, earphones, glasses and the like. It should be noted that the embodiment of the present application does not limit the specific type of the terminal 11. The network-side device 12 may be a Base Station or a core network, where 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 (BSS), an Extended Service Set (ESS), a node B, an evolved node B (eNB), a home node B, a home evolved node B, a WLAN access point, a WiFi node, a Transmit Receive 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, and it should be noted that, in the embodiment of the present application, only the Base Station in the NR system is taken as an example, but a specific type of the Base Station is not limited.

The congestion control method for broadcast multicast service provided by the embodiments of the present application is described in detail below with reference to the accompanying drawings by using some embodiments and application scenarios thereof.

Referring to fig. 2, an embodiment of the present application provides a congestion control method for a broadcast multicast service, which is executed by a terminal device, and the method includes the following steps:

step 201: performing congestion control on the broadcast multicast service in a first process; wherein the first process comprises: a second procedure and a random Access procedure of a Medium Access Control (MAC) layer, the second procedure including at least one of a radio resource Control RRC connection establishment procedure and an RRC connection recovery procedure.

In the embodiment of the present application, the congestion control for the broadcast multicast service may be implemented at least in one of a second procedure and a random access procedure of a medium access control MAC layer, wherein the second procedure includes at least one of a radio resource control RRC connection establishment procedure and an RRC connection recovery procedure. In this way, by adding the congestion control process for the broadcast multicast service 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, the probability of congestion occurring in the random access process due to a large number of terminal devices that are in a non-RRC connected state and are in need of the broadcast multicast service can be reduced, thereby improving system performance.

Optionally, when the first process is an RRC connection establishment (RRC connection initialization) process, the terminal device is correspondingly in an IDLE state (IDLE), and the terminal device may be referred to as an IDLE UE; when the first procedure is an RRC connection resume (RRC connection resume) procedure, the terminal device is correspondingly in an Inactive state (Inactive), and the terminal device may be referred to as an Inactive UE.

Optionally, in the congestion control method for a broadcast multicast service according to the embodiment of the present application, in the second process, a condition that the terminal device initiates the second process includes at least one of the following:

(1) The terminal device executes a first condition when a broadcast multicast service session join process (such as an MBS join procedure) is executed.

Optionally, the first condition includes at least one of:

a) The terminal equipment receives broadcast multicast service information; for example, USD (user service description) in LTE.

b) And the terminal equipment is interested in at least one broadcast multicast service corresponding to the broadcast multicast service information.

c) Upper layers (upperlayers) request establishment of an RRC connection; the method is mainly suitable for the terminal equipment in an idle state.

d) The upper layer requests the recovery of the RRC connection; the method is mainly suitable for the terminal equipment in the non-activated state.

e) The terminal equipment has the broadcast multicast service capability.

f) The network side equipment supports broadcast multicast service; such as support for including in system messages an indication that it supports broadcast multicast services.

g) The terminal equipment receives a session start notification sent by network side equipment; for example, session Start command, group Paging with Group Paging Identity (TMGI), paging message, etc.

h) The terminal equipment receives control information of the broadcast multicast service sent by the network side equipment; such as the System Information Block (SIB 15) of LTE, SIB20, and the like.

(2) And the terminal equipment executes a second condition when receiving the broadcast multicast service data after the session joining process of the broadcast multicast service is finished. When the broadcast multicast service data is received after the session joining process of the broadcast multicast service is completed, for example, the scheduling information of the MBS, the configuration information of the MBS (e.g., sctmcmon configuration similar to LTE), the information related to the MBS service continuity (e.g., content in SIB15 SIB20 similar to LTE), and the MBS data are acquired.

Optionally, the second condition comprises at least one of:

a) The terminal equipment receives a session starting notification sent by network side equipment; such as Session Start command, group Paging with Group Paging Identity (TMGI), paging messages, etc.

b) The terminal equipment has the broadcast multicast service capability.

c) The network side equipment supports broadcast multicast service; such as SIB15, SIB20, etc. for LTE.

Optionally, in the congestion Control method for a broadcast multicast service according to the embodiment of the present application, after the second process is initiated, the method may be applied to one of the following specific embodiments with respect to a definition of a Unified Access Control (UAC) part:

detailed description of the preferred embodiment

In the first embodiment, in the second procedure, the UAC procedure is not executed.

Detailed description of the preferred embodiment

In the second specific embodiment, the UAC process is executed in the second process.

Optionally, in the second specific embodiment, that is, in the case of executing the UAC procedure, the congestion control method for broadcast multicast service according to the embodiment of the present application may further include at least one of the following contents:

(1) When the terminal device executes a session join (session join) process, a Non-access stratum (NAS) layer or an RRC layer of the terminal device determines an access type corresponding to access control.

(2) When the terminal equipment receives MBS data after the session joining process of the broadcast multicast service is completed, the RRC layer of the terminal equipment determines and sets the access type corresponding to the access control.

Optionally, in the second specific embodiment, that is, in the case of executing the UAC procedure, the value of the parameter corresponding to the access control includes at least one of:

(1) A first value; the first value may be understood as the value of a parameter that is already present and that may be used for access control of the broadcast multicast service.

Wherein the value of the parameter corresponding to the Access control includes at least one of a value of an Access category (Access category) and a value of an Access identity (Access identity)

In one example, the first value may include: the value of Access identity is set to 0 and the value of Access category is set to 7 (i.e., transmission Data mo-Data).

(2) A second value different from the first value; the second value may be understood as a value of a parameter corresponding to a new access control for the broadcast multicast service that is different from the existing first value.

Wherein the second value is at least one of:

a) A value applicable to all broadcast multicast services. That is, the second value does not distinguish between specific broadcast multicast services, different broadcast multicast services have the same Access category and/or Access identification value, in one example, access identity is set to 0 and Access category is set to 13 (mt-MBSaccess); in another example, the Access identity is set to 16, the Access category is set to 7 (mo-Data); in yet another example, the Access identity is set to 16 and the Access category is set to 13 (mt-MBSaccess).

b) A value set individually on a per broadcast multicast service basis. That is, the second value distinguishes between specific broadcast multicast services, different broadcast multicast services having different access categories and/or access identification values. In one example, for a broadcast multicast service such as public safety (public safety), the Access identity is set to 16, the Access category is set to 15 (mo-public safety data); in another example, for a broadcast multicast service such as an interactive network television IPTV, the Access identity is set to 17, the Access category is set to 17 (mo-iptata); in yet another example, for MBS session ID = x, TMGI (or IP multicast address or any method of identifying broadcast multicast service such as application server address + IP multicast address) = y this broadcast multicast service, access identity is set to 16 and Access category is set to 15.

c) A value set individually on a per broadcast multicast service group basis. Wherein each broadcast multicast service group comprises one or more broadcast multicast services); that is, the second value distinguishes between specific broadcast multicast service groups, with different broadcast multicast service groups having different access categories and/or access identification values. In one example, for a broadcast multicast service group ID = x, the service group includes session ID = z, TMGI (or IP multicast address or any method of identifying a broadcast multicast service such as application server address + IP multicast address) = m, and session ID = n, TMGI (or IP multicast address or any method of identifying a broadcast multicast service such as application server address + IP multicast address) = o two broadcast multicast services, access identity is set to 16 and Access category is set to 15.

Optionally, in the congestion control method for a broadcast multicast service according to the embodiment of the present application, in the second process, the method may further include the following steps:

and executing access control on the broadcast multicast service.

In one example, after the second procedure is initiated and before the RRCSetupRequest message applicable to IDLE UEs or the rrcoresumrequest or rrcoresumrequest 1 message applicable to Inactive UEs is transmitted, access control for the broadcast and multicast service is performed.

Further optionally, the UAC and the access control for the broadcast multicast service may have a certain association relationship, including at least one of:

(1) When the terminal device does not perform the UAC procedure, it can immediately perform access control for the broadcast-multicast service. (2) When the terminal equipment executes the UAC process, if the access attempt of the UAC process is forbidden, the access control of the broadcast multicast service is not executed any more; and if the UAC procedure access attempt is allowed, immediately performing access control for the broadcast-multicast service.

Further optionally, in the second process, in a case of performing access control on the broadcast multicast service, the congestion control method for the broadcast multicast service according to the embodiment of the present application may further include the following contents:

selecting a value of a first random number, wherein the value of the first random number is used for the terminal equipment to execute access control on the broadcast multicast service; in case the value of the first random number is below a first threshold value, the access attempt is considered barred, otherwise the access attempt is considered allowed.

Optionally, the name of the first random number is at least one of:

a) Name applicable to all broadcast multicast services. That is, the name of the first random number does not distinguish specific broadcast multicast services, and different broadcast multicast services have the same name of the random number, such as rand1.

b) Based on the name set separately for each broadcast multicast service. That is, the name of the first random number distinguishes specific broadcast multicast services, and different broadcast multicast services have different names of random numbers. In one example, for a broadcast multicast service such as IPTV, the name of the random number is rand1; in another example, for a broadcast multicast service such as public safety, the name of the random number is rand2; in yet another example, for MBS session ID = x, TMGI (or IP multicast address or any method of identifying a broadcast multicast service such as application server address + IP multicast address) = y this broadcast multicast service, the name of random number is rand3.

c) Based on the name set separately for each broadcast multicast service group. Each broadcast multicast service group comprises 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 different names of random numbers. In one example, for MBS service group ID = x, the service group includes session ID = z, TMGI (or IP multicast address or any method of identifying broadcast multicast service such as app server address + IP multicast address) = m, and session ID = n, TMGI (or IP multicast address or any method of identifying broadcast multicast service such as app server address + IP multicast address) = o two broadcast multicast services, and the name of random number is rand4.

Optionally, in the congestion control method for a broadcast multicast service in the embodiment of the present application, the first threshold may be configured by a network side device, that is, the method may further include the following steps:

and receiving the first threshold value configured by the network side equipment.

Further optionally, the first threshold is at least one of:

a) Threshold value suitable for all broadcast multicast services. That is, the first threshold does not distinguish specific broadcast multicast services, and different broadcast multicast services have the same threshold, such as MBSac-BarringFactor.

b) A threshold value set individually based on each broadcast multicast service. That is, the first threshold value distinguishes specific broadcast multicast services, and different broadcast multicast services have different threshold values. In one example, for a broadcast multicast service such as IPTV, the threshold value is IPTVac-BarringFactor; in another example, for a Public safety such as a broadcast multicast service, the threshold value is Public safety-BarringFactor; in yet another example, for MBS session ID = x, TMGI (or IP multicast address or any method of identifying broadcast multicast service such as application server address + IP multicast address) = y this broadcast multicast service, the threshold value is BarringFactor1.

c) A threshold value set individually based on each broadcast multicast service group. Each broadcast multicast service group comprises 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 values. In one example, for MBS service group ID = x, the service group includes session ID = z, TMGI (or IP multicast address or any method of identifying broadcast multicast service such as app server address + IP multicast address) = m, and session ID = n, TMGI (or IP multicast address or any method of identifying broadcast multicast service such as app server address + IP multicast address) = o two broadcast multicast services, and the threshold value is BarringFactor2.

Further optionally, in the congestion control method for a broadcast multicast service according to the embodiment of the present application, when the value of the first random number is lower than a first threshold value, that is, when it is considered that an access attempt is prohibited, the method may further include the following steps:

selecting the value of the random number again (optional), and starting a first access control timer; after the first access control timer expires, access barring of access attempts is considered mitigated.

Optionally, in the congestion control method for a broadcast multicast service according to the embodiment of the present application, the first access control timer may be configured by a network side device, that is, the method may further include the following steps:

and receiving the first access control timer configured by the network side equipment.

Further optionally, the name of the first access control timer is at least one of:

a) Name applicable to all broadcast multicast services. That is, the name of the first access control timer does not distinguish specific broadcast multicast services, and different broadcast multicast services have the same name of the timer, such as T390a.

b) Based on the name set separately for each broadcast multicast service. That is, the name of the first access control timer distinguishes between specific broadcast multicast services, and different broadcast multicast services have different names of timers. In one example, for a broadcast multicast service such as IPTV, the name of the timer is T390a; in another example, for a broadcast multicast service such as public safety, the name of the timer is T390b; in yet another example, for MBS session ID = x, TMGI (or IP multicast address or any method of identifying a broadcast multicast service such as application server address + IP multicast address) = y this broadcast multicast service, the name of the timer is T390c.

c) Based on the name set separately for each broadcast multicast service group. Each broadcast multicast service group comprises one or more broadcast multicast service settings; that is, the name of the first access control timer distinguishes a specific broadcast-multicast service group, and different broadcast-multicast service groups have different names of timers. In one example, for MBS service group ID = x, the service group includes session ID = z, TMGI (or IP multicast address or any method of identifying broadcast multicast service such as app server address + IP multicast address) = m, and session ID = n, TMGI (or IP multicast address or any method of identifying broadcast multicast service such as app server address + IP multicast address) = o two broadcast multicast services, and the name of the timer is T390d.

Further optionally, the timing duration calculation formula corresponding to the first access control timer is related to at least one of the following:

a value of the first random number; and the back-off time value configured by the network side equipment.

In one example, when a 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 random number). Wherein, if the UE makes multiple selections of the random number value, the latest random number value is used in the formula.

In another example, when a timing duration calculation formula corresponding to the first access control timer is related to a value of the first random number and a value of the backoff time, the calculation formula may be expressed as: (value of 0.7+0.6 + random number) value of backoff time.

Wherein the timing duration calculation formula is at least one of the following:

a) The formula is suitable for all broadcast multicast services. That is, the timing duration calculation formula does not distinguish specific broadcast multicast services, and different broadcast multicast services have the same calculation formula.

b) A formula set separately based on each broadcast multicast service. That is, the timing duration calculation formula distinguishes specific broadcast multicast services, and different broadcast multicast services have different calculation formulas. In one example, for a broadcast multicast service such as IPTV, the calculation formula is formula 1; in another example, for a broadcast multicast service such as public safety, the calculation formula is formula 2; in yet another example, for MBS session ID = x, TMGI (or IP multicast address or any method of identifying a broadcast multicast service such as application server address + IP multicast address) = y this broadcast multicast service, the calculation formula is formula 3.

c) A formula set separately based on each broadcast multicast service group. Each broadcast multicast service group comprises 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 formulas. In one example, for MBS service group ID = x, the service group includes session ID = z, TMGI (or IP multicast address or any method of identifying a broadcast-multicast service such as application server address + IP multicast address) = m, and session ID = n, TMGI (or IP multicast address or any method of identifying a broadcast-multicast service such as application server address + IP multicast address) = o two broadcast-multicast services, and the calculation formula is formula 4.

Optionally, in the congestion control method for a broadcast multicast service according to the embodiment of the present application, the value of the back-off time may be configured by a network side device, that is, the method may further include the following steps:

and receiving the value of the back-off time configured by the network side.

Further optionally, the value of the backoff time is at least one of:

a) A value applicable to all broadcast multicast services. That is, the value of the backoff time does not distinguish specific broadcast multicast services, and different broadcast multicast services have the same backoff time, such as MBSac-BarringTime.

b) A value set individually on a per broadcast multicast service basis. That is, the value of the back-off time distinguishes between specific broadcast multicast services, and different broadcast multicast services have different back-off times. In one example, for a broadcast multicast service such as IPTV, the backoff time is IPTVac-BarringTime; in another example, for broadcast multicast traffic such as Public safety, the back-off time is Public safety ac-BarringTime; in yet another example, for MBS session ID = x, TMGI (or IP multicast address or any method of identifying a broadcast multicast service such as application server address + IP multicast address) = y this broadcast multicast service, the backoff time is BarringTime1.

c) A value set individually on a per broadcast multicast service group basis. Each broadcast multicast service group comprises one or more broadcast multicast service settings; that is, the value of the back-off time distinguishes a specific broadcast-multicast service group, and different broadcast-multicast service groups have different back-off times. In one example, for MBS service group ID = x, the service group includes session ID = z, TMGI (or IP multicast address or any method of identifying a broadcast-multicast service such as application server address + IP multicast address) = m, and session ID = n, TMGI (or IP multicast address or any method of identifying a broadcast-multicast service such as application server address + IP multicast address) = o two broadcast-multicast services, and the backoff time is BarringTime2.

Optionally, in the congestion control method for a broadcast multicast service according to the embodiment of the present application, in a case that the UAC process is executed, the method further includes: under the condition that the UAC process access attempt is forbidden, the access control of the broadcast multicast service is not executed any more; in case the UAC procedure access attempt is allowed, immediately performing access control for broadcast multicast traffic. Specific embodiments of access control for broadcast multicast services associated with UAC procedures include, but are not limited to, the following:

in specific embodiment I, the terminal device performs congestion control on the broadcast multicast service in the first process, and performs a UAC process; further, in the case that the UAC procedure access attempt is prohibited, no access control for the broadcast multicast service is performed any more; in case the UAC procedure access attempt is allowed, immediately performing access control for broadcast multicast traffic.

In a specific embodiment II, the terminal device performs congestion control on the broadcast multicast service and performs a UAC procedure in the second procedure, and further, does not perform access control on the broadcast multicast service any more when the UAC procedure access attempt is prohibited; in case the UAC procedure access attempt is allowed, immediately performing access control for the broadcast multicast service.

In specific embodiment III, the terminal device performs congestion control on the broadcast multicast service in the first procedure described above, and performs access control on the broadcast multicast service in the second procedure. Further, in the step of performing access control on the broadcast multicast service, in the case of performing the UAC procedure, if the UAC procedure access attempt is prohibited, the access control on the broadcast multicast service is no longer performed, and if the UAC procedure access attempt is permitted, the access control on the broadcast multicast service is immediately performed.

Optionally, in the congestion control method for a broadcast multicast service according to the embodiment of the present application, the cause of initiation of the second process includes at least one of:

(1) A first event; this first event may be understood as the value of the cause of the second procedure already existing and may be used for broadcast multicast traffic, e.g. set to mt-Access or mo-Signalling.

(2) A second event different from the first event; the second event may be understood as a new event that is different from the existing first event as the initiation cause of the second process.

Wherein the second event is at least one of:

a) The method is applicable to all events of the broadcast multicast service. That is, 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 mbsconfiguration, MBS-data, MBS-signaling, MBSmt-Access.

b) Events individually set on a per broadcast multicast service basis. That is, the second event distinguishes a specific broadcast-multicast service, and different broadcast-multicast services have different values. In one example, for a broadcast multicast service such as IPTV, the second event is IPTVConfiguration, IPTV-data, IPTVmt-Access; in another example, for a broadcast-multicast service such as Public safety, the second event is Public safety Configuration, public safety-data; in yet another example, for MBS session ID = x, TMGI (or IP multicast address or any method of identifying broadcast multicast service such as application server address + IP multicast address) = y this broadcast multicast service, and the second event is MBS1Configuration, MBS1-data, MBS 1-signaling, MBS1mt-Access.

c) Events individually set on a per broadcast multicast service group basis. Each broadcast multicast service group comprises one or more broadcast multicast service settings; that is, the second event distinguishes a specific broadcast-multicast service group, with different broadcast-multicast service groups having different values. In one example, for MBS service group ID = x, the service group includes session ID = z, TMGI (or any method of identifying broadcast-multicast service such as IP multicast address or application server address + IP multicast address) = m, and session ID = n, TMGI (or any method of identifying broadcast-multicast service such as IP multicast address or application server address + IP multicast address) = o two broadcast-multicast services, and the second event is MBS2Configuration, MBS2-data, or MBS2 mo-signaling.

Wherein the initiation is due to at least one of: a recovery cause resumecuse and an establishment cause estabilishment cause.

Optionally, in the method for controlling congestion of a broadcast multicast service according to the embodiment of the present application, when congestion control is performed on the broadcast multicast service in a Random Access Channel (RACH) process of a MAC layer, a MAC Protocol Data Unit (PDU) with an RRCSetupRequest message applicable to IDLE UE or an MAC PDU with an rrcresumererequest or RRCResumeRequest1 message applicable to Inactive UE is submitted to a physical layer and sent to a network side in the Random Access process of the MAC layer.

Optionally, in the congestion control method for a broadcast multicast service according to the embodiment of the present application, the trigger event of the random access procedure in the MAC layer includes at least one of the following events:

(1) A third event; the third event may be understood as a trigger event of an existing random access procedure of the MAC layer and may be used for a broadcast multicast service, such as Initial access from RRC _ IDLE, transition from RRC _ INACTIVE, and the like.

(2) A fourth event different from the third event. The fourth event may be understood as a trigger event of a random access procedure of a new MAC layer different from the existing third event.

Wherein the fourth event is at least one of:

a) The method is applicable to all events of the broadcast multicast service. That is, the fourth event does not distinguish specific broadcast multicast services, and different broadcast multicast services have the same value, for example, the fourth event is gain MBS configuration, receive MBS data, MBS-signaling, and the like.

b) Events individually set on a per broadcast multicast service basis. That is, the fourth event distinguishes a specific broadcast-multicast service, and different broadcast-multicast services have different values. In one example, for the broadcast multicast service such as IPTV, the fourth event is gain IPTV Configuration, receive IPTV data, IPTV-signaling; in another example, for a broadcast-multicast service, which is Public security, the second event is gain Public security Configuration, receive Public security data, and Public security-signaling; in yet another example, for MBS session ID = x, TMGI (or IP multicast address or any method of identifying broadcast multicast service such as application server address + IP multicast address) = y this broadcast multicast service, and the fourth event is gain MBS1Configuration, receive MBS1data, MBS 1-signaling.

c) Events individually set on a per broadcast multicast service group basis. Each broadcast multicast service group comprises one or more broadcast multicast service settings; that is, the fourth event distinguishes a specific broadcast-multicast service group, and different broadcast-multicast service groups have different values. In one example, for MBS service group ID = x, the service group includes session ID = z, TMGI (or any method of identifying broadcast-multicast service such as IP multicast address or application server address + IP multicast address) = m, and session ID = n, TMGI (or any method of identifying broadcast-multicast service such as IP multicast address or application server address + IP multicast address) = o two broadcast-multicast services, and the fourth event is gain MBS2Configuration, receive 2data, MBS2 mo-signaling.

Optionally, in the congestion control method for a broadcast multicast service according to the embodiment of the present application, when congestion control is performed on the broadcast multicast service in a random access procedure of a MAC layer, a network device may provide relevant parameters for the congestion control, that is, the method may further include the following steps:

receiving parameters related to the broadcast multicast service configured for the random access process of the MAC layer by the network side equipment; wherein the broadcast multicast service related parameters include at least one of: a power increase step (powerRampingStep), a backoff parameter BI scaling factor (scalingfactorb), and a random access preamble maximum number of transmissions (preambleTransMax).

Further optionally, in the congestion control method for a broadcast multicast service according to the embodiment of the present application, the powerRampingStep parameter is at least one of:

a) The method is applicable to all the parameters of the broadcast multicast service. That is, the powerRampingStep parameter does not distinguish between specific broadcast-multicast services, and different broadcast-multicast services have the same parameter, such as powerRampingStepLowPriority-MBS, powerRampingStep-MBS.

b) Parameters that are set individually on a per broadcast multicast service basis. That is, the powerRampingStep parameter distinguishes between specific broadcast multicast services, and different broadcast multicast services have different parameters. In one example, for a broadcast multicast service such as IPTV, the powerRampingStep parameter includes powerRampingStep-IPTV, powerRampingStep lowpriority-IPTV; in another example, for a broadcast-multicast service of public safety, the powerRampingStep parameter is powerRampingStep-public safety, powerRampingStep lowpriority-public safety; in yet another example, for MBS session ID = x, TMGI (or IP multicast address or any method of identifying a broadcast-multicast service such as application server address + IP multicast address) = y this broadcast-multicast service, and the powerRampingStep parameter is powerRampingStepLowPriority-MBS1.

c) Parameters that are set individually on a per broadcast multicast service group basis. Each broadcast multicast service group comprises one or more broadcast multicast service settings; that is, the powerRampingStep parameter distinguishes a specific broadcast-multicast service group, and different broadcast-multicast service groups have different parameters. In one example, for MBS service group ID = x, the service group includes session ID = z, TMGI (or IP multicast address or any method of identifying a broadcast-multicast service such as application server address + IP multicast address) = m, and session ID = n, TMGI (or IP multicast address or any method of identifying a broadcast-multicast service such as application server address + IP multicast address) = o two broadcast-multicast services, and the powerRampingStep parameter is powerRampingStepLowPriority-MBS2.

the parameters of all random access types corresponding to the random access process of the MAC layer are suitable for; and the parameters are independently set based on each random access type corresponding to the random access process of the MAC layer.

The random access types corresponding to the random access procedure of the MAC layer include a 4-step random access type (i.e., 4-step RACH) and a 2-step random access type (i.e., 2-step RACH).

Further optionally, in the congestion control method for a broadcast multicast service according to the embodiment of the present application, the scalingfactory bi parameter is at least one of:

a) The method is applicable to all parameters of the broadcast multicast service. That is, the scalingFactorBI parameter does not distinguish between specific broadcast-multicast services, and different broadcast-multicast services have the same parameter, such as scalingFactorBI-MBS.

b) Parameters that are set individually on a per broadcast multicast service basis. That is, the scalingfactory bi parameter distinguishes between specific broadcast multicast services, with different parameters for different broadcast multicast services. In one example, for a broadcast multicast service such as IPTV, the scalingfactory bi parameter comprises scalingfactory bi-IPTV; in another example, for a broadcast multicast service such as public safety, the scalingfactory bi parameter is scalingfactory bi-public safety; in yet another example, for MBS session ID = x, TMGI (or IP multicast address or any method of identifying broadcast multicast service such as application server address + IP multicast address) = y this broadcast multicast service, the scalingfacerbi parameter is scalingfacerbi-1.

c) Parameters that are set individually on a per broadcast multicast service group basis. Each broadcast multicast service group comprises one or more broadcast multicast service settings; that is, the scalingFactorBI parameter distinguishes between specific broadcast multicast service groups, with different broadcast multicast service groups having different parameters. In one example, for MBS service group ID = x, the service group includes session ID = z, TMGI (or IP multicast address or any method of identifying broadcast multicast service such as app server address + IP multicast address) = m, and session ID = n, TMGI (or IP multicast address or any method of identifying broadcast multicast service such as app server address + IP multicast address) = o two broadcast multicast services, and the scaling factor bi parameter is scaling factor bi-2.

The random access type corresponding to the random access procedure of the MAC layer includes 4-step RACH and 2-step RACH.

Further optionally, in the congestion control method for a broadcast multicast service according to the embodiment of the present application, the preambleTransMax parameter is at least one of the following parameters:

a) The method is applicable to all parameters of the broadcast multicast service. That is, the preambleTransMax parameter does not distinguish specific broadcast multicast services, and different broadcast multicast services have the same parameter, such as preambleTransMax-MBS.

b) Parameters that are set individually on a per broadcast multicast service basis. That is, the preambleTransMax parameter distinguishes specific broadcast multicast services, and different broadcast multicast services have different parameters. In one example, for a broadcast multicast service such as IPTV, the preambleTransMax parameter comprises preambleTransMax-IPTV; in another example, for a broadcast multicast service such as public safety, the preambleTransMax parameter is preambleTransMax-public safety; in yet another example, for MBS session ID = x, TMGI (or IP multicast address or any method of identifying a broadcast multicast service such as application server address + IP multicast address) = y this broadcast multicast service, the preambleTransMax parameter is preambleTransMax-1.

c) Parameters that are set individually on a per broadcast multicast service group basis. Each broadcast multicast service group comprises one or more broadcast multicast service settings; that is, the preambleTransMax parameter distinguishes between specific broadcast multicast service groups, and different broadcast multicast service groups have different parameters. In one example, for MBS service group ID = x, the service group includes session ID = z, TMGI (or any method of identifying a broadcast-multicast service such as IP multicast address or application server address + IP multicast address) = m, and session ID = n, TMGI (or any method of identifying a broadcast-multicast service such as IP multicast address or application server address + IP multicast address) = o two broadcast-multicast services, and the preambleTransMax parameter is preambleTransMax-2.

Optionally, in the congestion control method for a broadcast multicast service according to the embodiment of the present application, when congestion control for the broadcast multicast service is performed in a random access process of a MAC layer, the method may further include the following steps:

setting values of the broadcast multicast service related parameters according to at least one of: a random access type; a trigger event of a random access procedure of the MAC layer; and whether the network side equipment configures parameters related to the broadcast multicast service for the random access process of the MAC layer or not.

In this embodiment, when the MAC layer of the terminal device performs initialization of variables (i.e. parameters related to broadcast multicast service) of each random access type, the MAC layer may set values of RACH parameters, such as values of PREAMBLE _ POWER _ random _ STEP, scan _ FACTOR _ BI and PREAMBLE transmax, according to at least the selected RACH type (2-STEP RACH or 4-STEP RACH), a trigger event of the RACH, and the parameters configured by the RRC layer for the random access procedure, including but not limited to the following specific examples:

in example one, if RA _ TYPE is set to 2-stepRA, and if the random access procedure is triggered because of an existing triggering event (e.g., initial access from RRC _ IDLE, transition from RRC _ INACTIVE), PREAMBLE _ POWER _ RAMPING _ STEP to msgA-PREAMBLePowerRampingStep, SCALING _ FACTOR _ BI is set to 1, and PREAMBLETRANMax contained in RACH-ConfigGenericTwosTwopRA is used.

In example two, if RA _ TYPE is set to 2-stepRA, and if the random access procedure is triggered because a triggering event applicable to all broadcast-multicast services is triggered (e.g., gain MBS configuration), and if the RRC configuration (e.g., RACH-configcommon twosra) has RACH parameters applicable to all broadcast-multicast services (e.g., powerRampingStepLowPriority-MBS, SCALING FACTOR BI-MBS, SCALING transmax-MBS), preable _ POWER _ ramp _ STEP to powerRampingStepLowPriority-MBS, SCALING _ FACTOR _ BI is set to SCALING FACTOR BI-MBS, and SCALING transmax-MBS is employed.

In example three, if RA _ TYPE is set to 4-stepRA, and if the RA _ TYPE is due to a trigger event of per broadcast-multicast service (such as gain IPTV MBS configuration), and if the RRC configures (such as RACH-ConfigCommon) RACH parameters of per broadcast-multicast service (such as powerRampingStepLowPriority-IPTV, scalingsectorbi-IPTV, preambletracemax-IPTV), preamplambable _ POWER _ rampingsteprapringsteprateploriority-IPTV is set, scalingfattor _ BI is set to scalefactorbbi-IPTV, preamblemax-IPTV is applied.

As can be seen from the above, in the congestion control method for a broadcast multicast service in the embodiment of the present application, it is considered that when Non-RRCConnected UE enters RRCConnected state, it is mainly necessary to perform RRCconnection estimation procedure (for IDLE UE) or RRC connection resume procedure (for Inactive UE) in the RRC layer, and a random access procedure in the MAC layer, which are two procedures. Then, various mutually independent sub-schemes can be added in the two procedures to realize congestion control of the MBS service, that is, in an RRC connection assignment procedure (for IDLE UE) or an RRC connection resume procedure (for Inactive UE) of the RRC layer, access control for the broadcast multicast service is performed, a random access procedure of the MAC layer sets at least three RACH parameters, namely powerRampingStep, scalingfactory bi, and prembletransmax, for the broadcast multicast service, and all the settings are divided into three cases applicable to all the broadcast multicast services, per broadcast multicast service, and per broadcast multicast service group. Therefore, when the number of Non-RRC Connected UEs which have requirements on the broadcast multicast service is large, the probability of congestion generated in the random access process can be reduced, and the performance of the system is seriously influenced.

Referring to fig. 3, an embodiment of the present application provides a congestion control method for a broadcast multicast service, where the method is executed by a network side device, and the method includes the following steps:

step 301: receiving a request corresponding to a first process sent by a terminal device, wherein the first process is used for the terminal device to execute congestion control on a broadcast multicast service; wherein the first process comprises: a second procedure and a random access procedure of a media access control, MAC, layer, the second procedure comprising at least one of a radio resource control, RRC, connection establishment procedure and an RRC connection recovery procedure.

In the embodiment of the application, congestion control on the broadcast multicast service is realized at least in one or more of the RRC connection establishment process, the RRC connection recovery process and the random access process of the MAC layer, so that the probability of congestion in the random access process due to a large number of terminal devices which are in a non-RRC connected state and have a demand for the broadcast multicast service can be reduced, and system performance is improved.

Optionally, in the congestion control method for a broadcast multicast service according to the embodiment of the present application, before step 301, the method may further include the following steps:

configuring a first threshold value; and sending the first threshold value to the terminal equipment, wherein the first threshold value is used for comparing with a first random number value selected by the terminal equipment, and the first random number value is used for the terminal equipment to execute access control on the broadcast multicast service.

Optionally, the name of the first random number is at least one of: the name suitable for all the broadcast multicast services, the name set independently based on each broadcast multicast service and the name set independently based on each broadcast multicast service group.

Optionally, the first threshold is at least one of: a threshold value suitable for all broadcast multicast services, a threshold value individually set based on each broadcast multicast service, and a threshold value individually set based on each broadcast multicast service group.

configuring a first access control timer; sending the first access control timer to the terminal device, the first access control timer being used for the terminal device to determine whether access barring of the access attempt is mitigated.

Optionally, the name of the first access control timer is at least one of: the name suitable for all the broadcast multicast services, the name set independently based on each broadcast multicast service and the name set independently based on each broadcast multicast service group.

Optionally, the timing duration calculation formula corresponding to the first access control timer is related to at least one of the following:

a value of the first random number; a value of a backoff time; wherein the timing duration calculation formula is at least one of the following: a formula suitable for all broadcast multicast services, a formula set individually based on each broadcast multicast service, and a formula set individually based on each broadcast multicast service group.

Further optionally, in the congestion control method for broadcast multicast service according to the embodiment of the present application, the following contents may also be included:

configuring a value of the backoff time; sending the value of the back-off time to the terminal equipment; wherein the value of the back-off time is at least one of: a value applicable to all broadcast multicast services, a value set individually based on each broadcast multicast service, and a value set individually based on each broadcast multicast service group.

configuring parameters related to the broadcast multicast service corresponding to the random access process of the MAC layer; sending the parameters related to the broadcast multicast service to the terminal equipment; wherein the broadcast multicast service related parameters include at least one of: a power increase step size, a backoff parameter BI scaling factor, and a random access preamble maximum transmission number.

Optionally, the broadcast multicast service-related parameter is at least one of: parameters suitable for all broadcast multicast services, parameters individually set based on each broadcast multicast service, and parameters individually set based on each broadcast multicast service group.

Optionally, the broadcast multicast service related parameter is at least one of the following: the parameters of all random access types corresponding to the random access process of the MAC layer are suitable for; and the parameters are independently set based on each random access type corresponding to the random access process of the MAC layer.

It should be noted that, in the congestion control method for a broadcast and multicast service according to the embodiment of the present application, the same or similar contents as those in the congestion control method for a broadcast and multicast service executed by the terminal device side may refer to corresponding contents in the embodiment of fig. 2 corresponding to the congestion control method for a broadcast and multicast service executed by the terminal device, and are not described herein again.

It should be noted that, in the congestion control method for a broadcast and multicast service executed by a terminal device according to the embodiment of the present application, the execution subject may be a congestion control device for a broadcast and multicast service, or a control module in the congestion control device for a broadcast and multicast service, which is used for executing the congestion control method for a broadcast and multicast service. In the embodiment of the present application, a congestion control method for a congestion control device of a broadcast multicast service to execute the broadcast multicast service is taken as an example, to describe the congestion control device of the broadcast multicast service provided in the embodiment of the present application.

Referring to fig. 4, an embodiment of the present application provides a congestion control apparatus 400 for a broadcast multicast service, which is applied to a terminal device, where the congestion control apparatus 400 for a broadcast multicast service includes:

a control module 401, configured to perform congestion control on a broadcast multicast service in a first process; wherein the first process comprises: a second procedure and a random access procedure of a media access control, MAC, layer, the second procedure comprising at least one of a radio resource control, RRC, connection establishment procedure and an RRC connection recovery procedure.

Optionally, in the congestion control apparatus 400 for broadcast multicast service according to the embodiment of the present application, in the second procedure, a condition that the terminal device initiates the second procedure includes at least one of:

the terminal equipment executes a first condition when a broadcast multicast service session joins the process; and the terminal equipment executes a second condition when the broadcast multicast service data is received after the session joining process of the broadcast multicast service is completed.

Optionally, in the congestion control apparatus 400 for broadcast multicast service according to the embodiment of the present application, the first condition includes at least one of:

the terminal equipment receives broadcast multicast service information; the terminal equipment is interested in at least one broadcast multicast service corresponding to the broadcast multicast service information; the upper layer requests the establishment of RRC connection; the upper layer requests the recovery of the RRC connection; the terminal equipment has the broadcast multicast service capability; the network side equipment supports broadcast multicast service; the terminal equipment receives a session starting notification sent by network side equipment; and the terminal equipment receives the control information of the broadcast multicast service sent by the network side equipment.

Optionally, in the congestion control apparatus 400 for broadcast multicast service according to the embodiment of the present application, the second condition includes at least one of:

the terminal equipment receives a session start notification sent by network side equipment; the terminal equipment has the broadcast multicast service capability; the network side equipment supports the broadcast multicast service.

Optionally, in the congestion control apparatus 400 for a broadcast multicast service according to the embodiment of the present application, the control module 401 may be further configured to, in the second process, perform one of the following operations:

the unified access control UAC process is not executed; and executing the UAC process.

Optionally, in the congestion control apparatus 400 for broadcast multicast service according to the embodiment of the present application, the control module 401, when executing the UAC procedure, may be further configured to perform one of the following operations:

when the terminal equipment executes a session joining process of the broadcast multicast service, determining an access type corresponding to access control through a non-access stratum (NAS) layer or an RRC layer of the terminal equipment; and when the terminal equipment receives the MBS data after the session joining process of the broadcast multicast service is completed, determining and setting an access type corresponding to access control through an RRC layer of the terminal equipment.

Optionally, in the congestion control apparatus 400 for broadcast multicast service according to the embodiment of the present application, in a case that the UAC procedure is executed, a value of a parameter corresponding to access control includes at least one of:

a first value; a second value different from the first value; wherein the value of the parameter corresponding to the access control comprises at least one of a value of an access category and a value of an access identification; the second value is at least one of: a value applicable to all broadcast multicast services, a value set individually based on each broadcast multicast service, and a value set individually based on each broadcast multicast service group.

Optionally, in the congestion control apparatus 400 for a broadcast multicast service according to the embodiment of the present application, the control module 401 may be further configured to perform access control on the broadcast multicast service in the second process.

Optionally, the congestion control apparatus 400 for broadcast multicast service according to this embodiment of the present application may further include a processing module, where the processing module is configured to:

Optionally, the congestion control apparatus 400 for broadcast multicast service according to the embodiment of the present application may further include:

and the receiving module is used for receiving the first threshold value configured by the network side equipment.

Optionally, in the congestion control apparatus 400 for broadcast multicast service according to the embodiment of the present application, the name of the first random number is at least one of: the name suitable for all the broadcast multicast services, the name set independently based on each broadcast multicast service and the name set independently based on each broadcast multicast service group.

Optionally, in the congestion control apparatus 400 for broadcast multicast service according to the embodiment of the present application, the first threshold is at least one of: a threshold value suitable for all broadcast multicast services, a threshold value individually set based on each broadcast multicast service, and a threshold value individually set based on each broadcast multicast service group.

Optionally, in the congestion control apparatus 400 for a broadcast multicast service according to the embodiment of the present application, the processing module may be further configured to:

starting a first access control timer under the condition that the access attempt is considered to be forbidden; after the first access control timer expires, access barring of access attempts is considered mitigated.

Optionally, in the congestion control apparatus 400 for a broadcast multicast service according to the embodiment of the present application, the receiving module may be further configured to:

Optionally, in the congestion control apparatus 400 for broadcast multicast service according to the embodiment of the present application, the name of the first access control timer is at least one of: the name suitable for all the broadcast multicast services, the name set independently based on each broadcast multicast service and the name set independently based on each broadcast multicast service group.

Optionally, in the congestion control apparatus 400 for broadcast multicast service according to the embodiment of the present application, a timing duration calculation formula corresponding to the first access control timer is related to at least one of the following:

a value of the first random number; the value of the back-off time configured by the network side equipment; wherein the timing duration calculation formula is at least one of the following: a formula suitable for all broadcast multicast services, a formula set individually based on each broadcast multicast service, and a formula set individually based on each broadcast multicast service group.

and receiving the value of the back-off time configured by the network side.

Optionally, in the congestion control apparatus 400 for broadcast multicast service according to the embodiment of the present application, the value of the back-off time is at least one of: a value applicable to all broadcast multicast services, a value set individually based on each broadcast multicast service, and a value set individually based on each broadcast multicast service group.

Optionally, in the congestion control apparatus 400 for broadcast multicast service according to the embodiment of the present application, the control module 401 may be further configured to, in a case that the UAC process is executed, execute the following operations:

under the condition that the UAC process access attempt is forbidden, the access control of the broadcast multicast service is not executed any more; in case the UAC procedure access attempt is allowed, immediately performing access control for broadcast multicast traffic.

Optionally, in the congestion control apparatus 400 for broadcast multicast service according to the embodiment of the present application, the cause of initiating the second procedure 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 event setting method comprises the following steps of applying to all events of broadcast multicast services, events individually set based on each broadcast multicast service and events individually set based on each broadcast multicast service group; wherein the initiation is due to at least one of: a recovery cause resumecuse and an establishment cause estabilishment cause.

Optionally, in the congestion control apparatus 400 for broadcast multicast service according to the embodiment of the present application, the trigger event of the random access procedure of the MAC layer includes at least one of: a third event; a fourth event different from the third event; wherein the fourth event is at least one of: the method is suitable for events of all broadcast multicast services, events individually set based on each broadcast multicast service and events individually set based on each broadcast multicast service group.

receiving parameters related to the broadcast multicast service configured for the random access process of the MAC layer by the network side equipment; wherein the broadcast multicast service related parameters include at least one of: a power increase step size, a backoff parameter BI scaling factor, and a random access preamble maximum transmission number.

Optionally, in the congestion control apparatus 400 for a broadcast multicast service according to the embodiment of the present application, the parameter related to the broadcast multicast service is at least one of: the parameters suitable for all the broadcast multicast services, the parameters individually set based on each broadcast multicast service and the parameters individually set based on each broadcast multicast service group.

Optionally, in the congestion control apparatus 400 for a broadcast multicast service according to the embodiment of the present application, the parameter related to the broadcast multicast service is at least one of the following:

the parameters of all random access types corresponding to the random access process of the MAC layer are suitable for; and the parameter is independently set based on each random access type corresponding to the random access process of the MAC layer.

Optionally, in the congestion control apparatus 400 for broadcast multicast service according to the embodiment of the present application, the processing module may be further configured to:

In the embodiment of the application, the congestion control for the broadcast multicast service can be implemented at least in one of a second procedure and a random access procedure of a media access control MAC layer, wherein the second procedure comprises at least one of a radio resource control RRC connection establishment procedure and an RRC connection recovery procedure. In this way, by adding the congestion control process for the broadcast multicast service 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, the probability of congestion occurring in the random access process due to a large number of terminal devices that are in a non-RRC connected state and are in need of the broadcast multicast service can be reduced, thereby improving system performance.

The congestion control device for the broadcast multicast service in the embodiment of the present application may be a device, or may be a component, an integrated circuit, or a chip in a terminal device. The device can be a mobile terminal or a non-mobile terminal. For example, the mobile terminal may include, but is not limited to, the type of the terminal 11 listed above, and the non-mobile terminal may be a server, a Network Attached Storage (NAS), a Personal Computer (PC), a television (television), a teller machine (teller machine), a self-service machine (kiosk), or the like, and the embodiments of the present application are not limited in particular.

The congestion control device for the broadcast multicast service in the embodiment of the present application may be a device having an operating system. The operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, and embodiments of the present application are not limited specifically.

The congestion control device for broadcast multicast service provided in the embodiment of the present application can implement each process implemented in the method embodiment of fig. 2, and achieve the same technical effect, and is not described here again to avoid repetition.

It should be noted that, in the congestion control method for a broadcast and multicast service executed by a network side device according to the embodiment of the present application, the execution subject may be a congestion control device for a broadcast and multicast service, or a control module in the congestion control device for a broadcast and multicast service, which is used for executing the congestion control method for a broadcast and multicast service. In the embodiment of the present application, a congestion control method for a congestion control device of a broadcast multicast service to execute the broadcast multicast service is taken as an example, to describe the congestion control device of the broadcast multicast service provided in the embodiment of the present application.

Referring to fig. 5, 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, where the congestion control apparatus 500 for a broadcast multicast service includes:

a receiving module 501, configured to 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 comprises: a second procedure and a random access procedure of a media access control, MAC, layer, the second procedure comprising at least one of a radio resource control, RRC, connection establishment procedure and an RRC connection recovery procedure.

Optionally, the congestion control apparatus 500 for broadcast multicast service according to the embodiment of the present application may further include:

the first processing module is used for configuring a first threshold value before the request corresponding to the first process sent by the receiving terminal equipment is received; and the first sending module is used for sending the first threshold value to the terminal equipment, wherein the first threshold value is used for comparing with a first random number value selected by the terminal equipment, and the first random number value is used for the terminal equipment to execute access control on the broadcast multicast service.

Optionally, in the congestion control apparatus 500 for broadcast multicast service according to the embodiment of the present application, the name of the first random number is at least one of: the name suitable for all the broadcast multicast services, the name set independently based on each broadcast multicast service and the name set independently based on each broadcast multicast service group.

Optionally, in the congestion control apparatus 500 for broadcast multicast service according to the embodiment of the present application, the first threshold is at least one of: a threshold value suitable for all broadcast multicast services, a threshold value individually set based on each broadcast multicast service, and a threshold value individually set based on each broadcast multicast service group.

a second processing module, configured to configure a first access control timer before receiving a request corresponding to a first process sent by a terminal device; a second sending module, configured to send the first access control timer to the terminal device, where the first access control timer is used for the terminal device to determine whether access barring of an access attempt is mitigated.

Optionally, in the congestion control apparatus 500 for broadcast multicast service according to the embodiment of the present application, the name of the first access control timer is at least one of: the name suitable for all the broadcast multicast services, the name set independently based on each broadcast multicast service and the name set independently based on each broadcast multicast service group.

Optionally, in the congestion control apparatus 500 for broadcast multicast service according to the embodiment of the present application, a timing duration calculation formula corresponding to the first access control timer is related to at least one of the following:

a value of the first random number; a value of a 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 individually based on each broadcast multicast service, and a formula set individually based on each broadcast multicast service group.

Optionally, in the congestion control apparatus 500 for a broadcast multicast service according to the embodiment of the present application, the second processing module is further configured to configure a value of the backoff time; the second sending module is further configured to send the value of the backoff time to the terminal device; wherein the value of the back-off time is at least one of: a value applicable to all broadcast multicast services, a value set individually based on each broadcast multicast service, and a value set individually based on each broadcast multicast service group.

a third processing module, configured to configure parameters related to a broadcast multicast service corresponding to a random access procedure of the MAC layer before receiving a request corresponding to a first procedure sent by the terminal device; a third sending module, configured to send the parameters related to the broadcast multicast service to the terminal device; wherein the broadcast multicast service related parameters include at least one of: a power increase step size, a backoff parameter BI scaling factor, and a random access preamble maximum transmission number.

Optionally, in the congestion control apparatus 500 for a broadcast multicast service according to the embodiment of the present application, the parameter related to the broadcast multicast service is at least one of the following: the parameters suitable for all the broadcast multicast services, the parameters individually set based on each broadcast multicast service and the parameters individually set based on each broadcast multicast service group.

Optionally, in the congestion control apparatus 500 for a broadcast multicast service according to the embodiment of the present application, the parameter related to the broadcast multicast service is at least one of the following:

The congestion control device for the broadcast multicast service in the embodiment of the present application may be a device, or may be a component, an integrated circuit, or a chip in a network side device. The apparatus may be a network side device. Illustratively, the network-side device may include, but is not limited to, the types of network-side device 12 listed above.

The congestion control device for a broadcast multicast service according to the embodiment of the present application can implement each process implemented by the method embodiment of fig. 3, and achieve the same technical effect, and is not described herein again to avoid repetition.

Optionally, as shown in fig. 6, an embodiment of the present application further provides a communication device 600, which includes a processor 601, a memory 602, and a program or an instruction stored in the memory 602 and executable on the processor 601, for example, when the communication device 600 is a terminal, the program or the instruction is executed by the processor 601 to implement each process of the foregoing congestion control method embodiment of the broadcast multicast service corresponding to fig. 2, and can achieve the same technical effect. When the communication device 600 is a network-side device, the program or the instruction is executed by the processor 601 to implement the processes of the foregoing congestion control method embodiment of the broadcast multicast service corresponding to fig. 3, and the same technical effect can be achieved, and details are not described here to avoid repetition.

Fig. 7 is a schematic diagram of a hardware structure of a terminal for implementing the 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, and a processor 710.

Those skilled in the art will appreciate that the terminal 700 may further include a power supply (e.g., a battery) for supplying power to various components, which may be logically connected to the processor 710 via a power management system, so as to manage charging, discharging, and power consumption management functions via the power management system. The terminal structure shown in fig. 7 does not constitute a limitation of the terminal, and the terminal may include more or less components than those shown, or combine some components, or have a different arrangement of components, and will not be described again here.

It should be understood that, in the embodiment of the present application, the input Unit 704 may include a Graphics Processing Unit (GPU) 7041 and a microphone 7042, and the Graphics processor 7041 processes image data of a still picture or a video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The display unit 706 may include a display panel 7061, and the display panel 7061 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 referred to as a touch screen. The touch panel 7071 may include two portions, a touch detection device and a touch controller. Other input devices 7072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be described in further detail herein.

In this embodiment, the radio frequency unit 701 receives downlink data from a network side device and then processes the downlink data to the processor 710; in addition, the uplink data is sent to the network side equipment. In general, 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.

The 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 (such as a sound playing function, an image playing function, etc.) required by at least one function, and the like. In addition, the memory 709 may include a high-speed random access memory and a nonvolatile memory, where the nonvolatile memory may be a Read-only memory (ROM), a programmable Read-only memory (PROM), an erasable programmable Read-only memory (EPROM), an electrically erasable programmable Read-only memory (EEPROM), or a flash memory. Such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.

Processor 710 may include one or more processing units; alternatively, processor 710 may integrate an application processor that handles primarily the operating system, user interface, and application programs or instructions, etc. and a modem processor that handles primarily wireless communications, such as a baseband processor. It will be appreciated that the modem processor described above may not be integrated into processor 710.

Wherein, the processor 710 is configured to perform congestion control on a broadcast multicast service in a first procedure; wherein the first process comprises: a second procedure and a random access procedure of a media access control, MAC, layer, the second procedure comprising at least one of a radio resource control, RRC, connection establishment procedure and an RRC connection recovery procedure.

The embodiment of the application also provides network side equipment. As shown in fig. 8, the network side device 800 includes: antenna 801, radio frequency device 802, baseband device 803. The antenna 801 is connected to a radio frequency device 802. In the uplink direction, the rf device 802 receives information through the antenna 801 and sends the received information to the baseband device 803 for processing. In the downlink direction, the baseband device 803 processes information to be transmitted and transmits the information to the radio frequency device 802, and the radio frequency device 802 processes the received information and transmits the processed information through the antenna 801.

The above band processing means may be located in the baseband means 803, and the method performed by the network side device in the above embodiment may be implemented in the baseband means 803, where the baseband means 803 includes a processor 804 and a memory 805.

The baseband apparatus 803 may include, for example, at least one baseband board, on which a plurality of chips are disposed, as shown in fig. 8, where one of the chips, for example, the processor 804, is connected to the memory 805 to call up the program in the memory 805 to perform the network side device operation shown in the above method embodiment.

The baseband device 803 may further include a network interface 806, such as a common public radio interface (CPRI for short), for exchanging information with the radio frequency device 802.

Specifically, the network side device of the embodiment of the present invention further includes: the instructions or programs stored in the memory 805 and capable of being executed on the processor 804, and the processor 804 calls the instructions or programs in the memory 805 to execute the methods executed by the modules shown in fig. 5, and achieve the same technical effects, which are not described herein for avoiding repetition.

The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of any one of the foregoing embodiments of the congestion control method for a broadcast multicast service, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

The processor is the processor in the terminal or the network side device in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and so on.

An embodiment of the present application further provides a computer program product, where the computer program product includes a processor, a memory, and a program or an instruction stored in the memory and capable of running on the processor, and when the program or the instruction is executed by the processor, the processes of any one of the foregoing embodiments of congestion control method for broadcast and multicast services are implemented, and the same technical effect can be achieved, and in order to avoid repetition, details are not repeated here.

The 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 configured to run a terminal device or a network-side device program or an instruction, to implement each process of the foregoing corresponding congestion control method for a broadcast multicast service, and the same technical effect can be achieved, and is not described here again to avoid repetition.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip or a system-on-chip.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrases "comprising a component of' 8230; \8230;" does not exclude the presence of another like element in a process, method, article, or apparatus that comprises the element. Further, it should be noted that the scope of the methods and apparatuses in the embodiments of the present application is not limited to performing the functions in the order illustrated or discussed, but may include performing the functions in a substantially simultaneous manner or in a reverse order based on the functions recited, e.g., the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network-side device) to execute the method according to the embodiments of the present application.

While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. A congestion control method for broadcast multicast service is applied to a terminal device, and is characterized in that the method comprises the following steps:

performing congestion control on the broadcast multicast service in a first process; wherein the first process comprises: a second process and a random access process of a Media Access Control (MAC) layer, wherein the second process comprises at least one of a Radio Resource Control (RRC) connection establishment process and an RRC connection recovery process;

in the second procedure, in the case of performing a unified access control UAC procedure, the value of the parameter corresponding to access control includes at least one of: a first value; a second value different from the first value; wherein the value of the parameter corresponding to the access control comprises at least one of a value of an access category and a value of an access identification; the second value is at least one of: values applicable to all broadcast multicast services, values individually set based on each broadcast multicast service, and values individually set based on each broadcast multicast service group; alternatively, the first and second liquid crystal display panels may be,

in the second process, the method further comprises: performing access control on the broadcast multicast service; selecting a value of a first random number, wherein the value of the first random number is used for the terminal equipment to execute access control on the broadcast multicast service; considering the access attempt to be forbidden if the value of the first random number is lower than a first threshold value, and considering the access attempt to be allowed if the value of the first random number is not lower than the first threshold value;

in a random access procedure of the MAC layer, the method further includes: receiving parameters related to the broadcast multicast service configured for the random access process of the MAC layer by the network side equipment; wherein the broadcast multicast service related parameters include at least one of: a power increase step size, a backoff parameter BI scaling factor, and a random access preamble maximum transmission number.

2. The method according to claim 1, wherein in the second procedure, the condition for the terminal device to initiate the second procedure comprises at least one of:

the terminal equipment executes a first condition when a broadcast multicast service session joins the process;

and the terminal equipment executes a second condition when receiving the broadcast multicast service data after the session joining process of the broadcast multicast service is finished.

3. The method of claim 2, wherein the first condition comprises at least one of:

the terminal equipment receives broadcast multicast service information;

the terminal equipment is interested in at least one broadcast multicast service corresponding to the broadcast multicast service information;

the upper layer requests the establishment of RRC connection;

the upper layer requests the recovery of the RRC connection;

the terminal equipment has the broadcast multicast service capability;

the network side equipment supports the broadcast multicast service;

the terminal equipment receives a session starting notification sent by network side equipment;

and the terminal equipment receives the control information of the broadcast multicast service sent by the network side equipment.

4. The method of claim 2, wherein the second condition comprises at least one of:

the terminal equipment has the broadcast multicast service capability;

the network side equipment supports the broadcast multicast service.

5. The method of claim 1, wherein in the second process, the method further comprises one of:

the UAC process is not executed;

and executing the UAC process.

6. The method according to claim 5, wherein in case of performing the UAC procedure, the method further comprises at least one of:

when the terminal equipment executes a session joining process of the broadcast multicast service, determining an access type corresponding to access control by a non-access stratum (NAS) layer or a Radio Resource Control (RRC) layer of the terminal equipment;

when the terminal equipment receives MBS data after the session joining process of the broadcast multicast service is completed, the RRC layer of the terminal equipment determines and sets the access type corresponding to the access control.

7. The method of claim 1, further comprising:

8. The method of claim 1, wherein the first random number is named at least one of: the name suitable for all the broadcast multicast services, the name set independently based on each broadcast multicast service and the name set independently based on each broadcast multicast service group.

9. The method of claim 1, wherein the first threshold value is at least one of: a threshold value suitable for all broadcast multicast services, a threshold value individually set based on each broadcast multicast service, and a threshold value individually set based on each broadcast multicast service group.

10. The method of claim 1, further comprising:

starting a first access control timer under the condition that the access attempt is considered to be forbidden;

after the first access control timer expires, access barring of access attempts is considered mitigated.

11. The method of claim 10, further comprising:

12. The method of claim 10, wherein the first access control timer is named at least one of: the name suitable for all the broadcast multicast services, the name set independently based on each broadcast multicast service and the name set independently based on each broadcast multicast service group.

13. The method of claim 10, wherein the timing duration calculation formula corresponding to the first access control timer is related to at least one of the following:

a value of the first random number;

the value of the back-off time configured by the network side equipment;

wherein the timing duration calculation formula is at least one of the following: a formula suitable for all broadcast multicast services, a formula set individually based on each broadcast multicast service, and a formula set individually based on each broadcast multicast service group.

14. The method of claim 13, further comprising:

and receiving the value of the back-off time configured by the network side.

15. The method of claim 13, wherein the back-off time has a value of at least one of:

a value applicable to all broadcast multicast services, a value set individually based on each broadcast multicast service, and a value set individually based on each broadcast multicast service group.

16. The method according to claim 1 or 5, characterized in that in case of performing the UAC procedure, the method further comprises:

under the condition that the UAC process access attempt is forbidden, the access control of the broadcast multicast service is not executed any more;

in case the UAC procedure access attempt is allowed, immediately performing access control for broadcast multicast traffic.

17. The method of claim 1, wherein the cause of initiation of the second procedure comprises at least one of:

a first event;

a second event different from the first event; wherein the second event is at least one of: the event setting method comprises the following steps of applying to all events of broadcast multicast services, events individually set based on each broadcast multicast service and events individually set based on each broadcast multicast service group;

18. The method of claim 1, wherein the triggering event of the random access procedure of the MAC layer comprises at least one of:

a third event;

a fourth event different from the third event; wherein the fourth event is at least one of: the method is applicable to events of all broadcast multicast services, events individually set based on each broadcast multicast service and events individually set based on each broadcast multicast service group.

19. The method of claim 1, wherein the broadcast-multicast service related parameter is at least one of:

parameters suitable for all broadcast multicast services, parameters individually set based on each broadcast multicast service, and parameters individually set based on each broadcast multicast service group.

20. The method of claim 1, wherein the broadcast-multicast service related parameter is at least one of:

the parameters of all random access types corresponding to the random access process of the MAC layer are suitable for;

and the parameters are independently set based on each random access type corresponding to the random access process of the MAC layer.

21. The method according to any one of claims 18-20, further comprising:

setting values of the broadcast multicast service related parameters according to at least one of:

a random access type;

a trigger event of a random access procedure of the MAC layer;

and whether the network side equipment configures parameters related to the broadcast multicast service for the random access process of the MAC layer or not.

22. A congestion control method for broadcast multicast service is applied to network side equipment, and is characterized in that the method comprises the following steps:

receiving a request corresponding to a first process sent by a terminal device, wherein the first process is used for the terminal device to execute congestion control on a broadcast multicast service;

wherein the first process comprises: a second process and a random access process of a Media Access Control (MAC) layer, wherein the second process comprises at least one of a Radio Resource Control (RRC) connection establishment process and an RRC connection recovery process;

before the step of receiving the request corresponding to the first process sent by the terminal device, the method further includes: configuring a first threshold value; sending the first threshold value to the terminal device, where the first threshold value is used to compare with a first random number value selected by the terminal device, and the first random number value is used for the terminal device to perform access control on a broadcast multicast service;

before the step of receiving the request corresponding to the first process sent by the terminal device, the method further includes: configuring parameters related to the broadcast multicast service corresponding to the random access process of the MAC layer; sending the parameters related to the broadcast multicast service to the terminal equipment; wherein the broadcast multicast service related parameters include at least one of: a power increase step size, a backoff parameter BI scaling factor, and a random access preamble maximum transmission number.

23. The method of claim 22, wherein the first random number is named at least one of:

the name suitable for all the broadcast multicast services, the name set independently based on each broadcast multicast service and the name set independently based on each broadcast multicast service group.

24. The method of claim 22, wherein the first threshold is at least one of:

the threshold value suitable for all the broadcast multicast services, the threshold value set independently based on each broadcast multicast service and the threshold value set independently based on each broadcast multicast service group.

25. The method according to claim 22, wherein before the step of receiving the request corresponding to the first procedure sent by the terminal device, the method further comprises:

configuring a first access control timer;

sending the first access control timer to the terminal device, the first access control timer being used for the terminal device to determine whether access barring of the access attempt is mitigated.

26. The method of claim 25, wherein the first access control timer is named at least one of:

27. The method of claim 25, wherein the timing duration calculation formula corresponding to the first access control timer is related to at least one of the following:

a value of the first random number;

a value of a backoff time;

28. The method of claim 27, further comprising:

configuring a value of the back-off time;

sending the value of the back-off time to the terminal equipment;

wherein the value of the back-off time is at least one of: a value applicable to all broadcast multicast services, a value set individually based on each broadcast multicast service, and a value set individually based on each broadcast multicast service group.

29. The method of claim 22, wherein the broadcast-multicast service related parameter is at least one of:

30. The method of claim 22, wherein the broadcast-multicast service related parameter is at least one of:

and the parameter is independently set based on each random access type corresponding to the random access process of the MAC layer.

31. A congestion control device for broadcast multicast service, applied to a terminal device, the device comprising:

the control module is used for executing congestion control on the broadcast multicast service in a first process; wherein the first process comprises: a second process and a random access process of a Media Access Control (MAC) layer, wherein the second process comprises at least one of a Radio Resource Control (RRC) connection establishment process and an RRC connection recovery process;

in the second procedure, in the case of performing a UAC procedure, the value of the parameter corresponding to access control includes at least one of: a first value; a second value different from the first value; wherein the value of the parameter corresponding to the access control comprises at least one of a value of an access category and a value of an access identification; the second value is at least one of: values applicable to all broadcast multicast services, values set individually based on each broadcast multicast service, and values set individually based on each broadcast multicast service group; alternatively, the first and second electrodes may be,

the control module is further configured to perform access control on a broadcast multicast service in the second process; selecting a value of a first random number, wherein the value of the first random number is used for the terminal equipment to execute access control on the broadcast multicast service; considering the access attempt to be forbidden if the value of the first random number is lower than a first threshold value, and considering the access attempt to be allowed if the value of the first random number is not lower than the first threshold value;

the device further comprises: a receiving module, configured to receive, in the random access process of the MAC layer, a parameter related to a broadcast multicast service configured by a network side device for the random access process of the MAC layer; wherein the broadcast multicast service related parameters include at least one of: a power increase step size, a backoff parameter BI scaling factor, and a random access preamble maximum transmission number.

32. The apparatus of claim 31, wherein the control module is further configured to, during the second procedure, perform one of:

the unified access control UAC process is not executed;

and executing the UAC process.

33. The apparatus according to any of the claims 31-32, wherein said control module, if performing said UAC procedure, is further configured to:

in case the UAC procedure access attempt is allowed, immediately performing access control for the broadcast multicast service.

34. A congestion control device for broadcast multicast service, applied to a network side device, is characterized in that the device comprises:

a receiving module, configured to 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;

the device further comprises: the first processing module is used for configuring a first threshold value before the request corresponding to the first process sent by the receiving terminal equipment is received; a first sending module, configured to send the first threshold to the terminal device, where the first threshold is used to compare with a first random number value selected by the terminal device, and the first random number value is used for the terminal device to perform access control on a broadcast multicast service;

the device further comprises: a third processing module, configured to configure parameters related to a broadcast multicast service corresponding to a random access procedure of the MAC layer before receiving a request corresponding to a first procedure sent by the terminal device; a third sending module, configured to send the parameters related to the broadcast multicast service to the terminal device; wherein the broadcast multicast service related parameters include at least one of: a power increase step size, a backoff parameter BI scaling factor, and a random access preamble maximum transmission number.

35. The apparatus of claim 34, further comprising:

a second processing module, configured to configure a first access control timer before receiving a request corresponding to a first process sent by a terminal device;

a second sending module, configured to send the first access control timer to the terminal device, where the first access control timer is used for the terminal device to determine whether access barring of an access attempt is mitigated.

36. A terminal device, comprising: memory, processor and program or instructions stored on the memory and executable on the processor, which when executed by the processor implement the steps of the method of congestion control of broadcast multicast traffic according to any of claims 1 to 21.

37. A network-side device, comprising: memory, processor and program or instructions stored on the memory and executable on the processor, which when executed by the processor implement the steps of the congestion control method of broadcast multicast service according to any of the claims 22 to 30.

38. A readable storage medium, on which a program or instructions are stored, which when executed by a processor implement the steps of the program or instructions of any one of claims 1 to 21 when executed by a processor implement the method for congestion control of broadcast multicast service, or which when executed by a processor implement the steps of the method for congestion control of broadcast multicast service, of any one of claims 22 to 30.