Radio resource control state control method and apparatus, and communication device

Abstract

The application discloses a wireless resource control state control method and device and communication equipment, and belongs to the communication technical field. The wireless resource control state control method of the application embodiment comprises the following steps: in a first time period, a communication device controls the RRC state of a terminal according to first information and an RRC state change principle. The first time period is a time period associated with a multicast service interested by the terminal. The first information is used for determining the RRC state of the terminal receiving the multicast service interested.

Description

TECHNICAL FIELD

[0001] The present application belongs to the technical field of communication, and particularly relates to a radio resource control (RRC) state control method and device and a communication device. BACKGROUND

[0002] At present, the RRC state of a terminal can be changed due to occurrence of certain events. For example, when a terminal in an RRC-inactive state cannot execute part or all of the configurations in an RRC resume message, the terminal will enter an RRC-idle state from the RRC-inactive state. For another example, when a terminal in an RRC-connected state receives indication information that a timer of a lower layer expires, the terminal will enter an RRC-idle state from the RRC-connected state.

[0003] Generally, a terminal needs to receive multicast services in a specific RRC state. If the above event of changing the RRC state of the terminal occurs in the process of receiving the multicast services, the RRC state of the terminal can be changed to an RRC state that does not conform to the RRC state of receiving the multicast services. SUMMARY

[0004] Embodiments of the present application provide a radio resource control state control method and device and a communication device, which can solve the problem that a terminal cannot accurately control an RRC state in the case of occurrence of an event of changing the RRC state of the terminal.

[0005] In a first aspect, a radio resource control state control method is provided. The method comprises: in a first time period, controlling, by a communication device, an RRC state of a terminal according to first information and an RRC state change principle. The first time period is a time period associated with multicast services of interest to the terminal. The first information is used to determine an RRC state in which the terminal receives the multicast services of interest.

[0006] In a second aspect, a radio resource control state control device is provided. The device is applied to a communication device, and comprises a control module. The control module is configured to, in a first time period, control an RRC state of a terminal according to first information and an RRC state change principle. The first time period is a time period associated with multicast services of interest to the terminal. The first information is used to determine an RRC state in which the terminal receives the multicast services of interest.

[0007] In a third aspect, a terminal is provided. The terminal comprises a processor and a memory. The memory stores a program or instructions executable on and run on the processor, and the program or instructions are executed by the processor to implement the steps of the method of the first aspect.

[0008] In a fourth aspect, a terminal is provided, including a processor and a communication interface. The processor is configured to control a RRC state of the terminal according to first information and a RRC state change principle in a first time period.

[0009] In a fifth aspect, a readable storage medium is provided, and the readable storage medium stores a program or instructions. The program or instructions are executed by a processor to implement the steps of the method in the first aspect.

[0010] In a sixth aspect, a chip is provided, and the chip includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is configured to run a program or instructions to implement the method in the first aspect.

[0011] In a seventh aspect, a computer program / program product is provided, and the computer program / program product is stored in a storage medium. The program / program product is executed by at least one processor to implement the steps of the RRC state control method in the first aspect.

[0012] In the embodiments of the present application, in the first time period, the communication device can control the RRC state of the terminal according to the first information and the RRC state change principle. According to the scheme, since the communication device can determine the RRC state in which the terminal should be in to receive the multicast service of interest according to the first information, and can determine how the RRC state of the terminal changes under different circumstances according to the RRC state change principle, therefore in the first time period associated with the multicast service of interest of the terminal, when the terminal has the multicast service of interest, if an event of changing the RRC state of the terminal occurs, the communication device can accurately control the RRC state of the terminal according to the first information and the RRC state change principle. BRIEF DESCRIPTION OF DRAWINGS

[0013] Figure 1 is a structural schematic diagram of a wireless communication system provided by the embodiments of the present application;

[0014] Figure 2 is a flowchart of a RRC state control method provided by the embodiments of the present application;

[0015] Figure 3 is a schematic diagram of a starting time of the first time period provided by the embodiments of the present application;

[0016] Figure 4 is a structural schematic diagram of a RRC state control device provided by the embodiments of the present application;

[0017] Figure 5 is a structural schematic diagram of a RRC state control device provided by the embodiments of the present application;

[0018] Figure 6 Fig. 3 is a structural schematic diagram of a wireless resource control state control device according to an embodiment of the present application;

[0019] Figure 7 Fig. 4 is a structural schematic diagram of a communication device according to an embodiment of the present application;

[0020] Figure 8 Fig. 5 is a structural schematic diagram of a terminal according to an embodiment of the present application;

[0021] Figure 9 Fig. 6 is a structural schematic diagram of a network side device according to an embodiment of the present application. DETAILED DESCRIPTION

[0022] The technical solutions in the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all of them. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art belong to the scope of protection of the present application.

[0023] The terms "first", "second", and the like in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchanged under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than that illustrated or described herein, and the objects distinguished by "first", "second" are generally of a kind, and are not limited to the number of objects, for example, the first object can be one or more. In addition, "and / or" in the specification and claims means at least one of the connected objects, and the character " / " generally represents an "or" relationship between the front and rear associated objects.

[0024] It is worth noting that the technology described in the embodiments of the present application is not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used in the above-mentioned systems and radio technologies, as well as in other systems and radio technologies. The following description describes a New Radio (NR) system for example purposes, and NR terminology is used in most of the following description, but these technologies can also be applied outside the NR system application, such as in a 6th Generation (6G) communication system. th

[0025] Figure 1 ​A block diagram of a wireless communication system to which embodiments of the present application can be applied is shown. The wireless communication system includes a terminal 11 and a network side device 12. The terminal 11 can be a terminal side device such as a mobile phone, a tablet personal computer, a laptop computer, a personal digital assistant (PDA), a palm computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile Internet device (MID), an augmented reality (AR) / virtual reality (VR) device, a robot, a wearable device, a vehicle-mounted device (VUE), a pedestrian terminal (PUE), a smart home (a home device with a wireless communication function such as a refrigerator, a television, a washing machine, or furniture), a game console, a personal computer (PC), a kiosk, or a self-service machine. The wearable device includes a smart watch, a smart bracelet, a smart earphone, smart glasses, smart jewelry (a smart bracelet, a smart necklace, a smart ring, a smart necklace, a smart anklet, a smart necklace, etc.), a smart wristband, and smart clothing. It should be noted that the specific type of the terminal 11 is not limited in the embodiments of the present application. The network side device 12 can include an access network device or a core network device. The access network device 12 can also be referred to as a radio access network device, a radio access network (RAN), a radio access network function, or a radio access network unit. The access network device 12 can include a base station, a WLAN access point, or a WiFi node. The base station can be referred to as a node B, an evolved node B (eNB), 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 home node B, a home evolved node B, a transmitting receiving point (TRP), or some other appropriate terminology in the art, as long as the same technical effects are achieved. The base station is not limited to a specific technical term, and it should be noted that only a base station in an NR system is taken as an example for description in the embodiments of the present application, and the specific type of the base station is not limited.The core network device can include, but is not limited to, at least one of the following: a core network node, a core network function, a mobility management entity (MME), an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a policy control function (PCF), a policy and charging rules function (PCRF), an edge application server discovery function (EASDF), a unified data management (UDM), a unified data repository (UDR), a home subscriber server (HSS), a centralized network configuration (CNC), a network repository function (NRF), a network exposure function (NEF), a local NEF (L-NEF), a binding support function (BSF), an application function (AF), and the like. It should be noted that only the core network device in the NR system is taken as an example for introduction in the embodiments of the present application, and the specific type of the core network device is not limited.

[0026] The wireless resource control state control method provided by the embodiments of the present application will be described in detail in combination with the accompanying drawings and some embodiments and application scenarios. It should be noted that the method can be applied to Figure 1 the terminal 11 in the wireless communication system shown in FIG. 1, and can also be applied to Figure 1 the network side device 12 in the wireless communication system shown in FIG. 1. For the sake of simplicity, the terminal and the network side device are collectively referred to as a communication device in the embodiments of the present application.

[0027] In addition, the names of messages between various network elements in the following embodiments of the present application or the names of parameters in the messages are only examples, and other names can also be used in actual implementation, and the embodiments of the present application do not limit this.

[0028] Figure 2 A wireless resource control state control method provided by the embodiments of the present application is shown, and the method can include S201 described below.

[0029] S201, in a first time period, a communication device controls an RRC state of a terminal according to first information and an RRC state change principle.

[0030] The first time period is associated with a multicast service in which the terminal is interested. The first information can be used to determine the RRC state of the terminal receiving the multicast service in which the terminal is interested.

[0031] It can be understood that, in the case that the communication device is a network side device, the network side device can accurately control the RRC state of the terminal according to the first information and the RRC state change principle. For example, the network side device discovers that the terminal in the RRC connected state cannot be released to the RRC idle state according to the RRC state change principle, and then the network side device does not send an RRC release message to the terminal. In the case that the communication device is a terminal device, the terminal can control its own RRC state according to the first information and the RRC state change principle. For example, when the terminal in the RRC connected state receives indication information that a timer sent by an underlying layer has timed out, if the terminal discovers that it cannot change to the RRC idle state according to the RRC state change principle, the terminal can remain in the RRC connected state.

[0032] It should be noted that, in the embodiments of the present application, the RRC state change principle can be predefined by a protocol, configured or indicated to the terminal by a network; and the first information can be configured or indicated to the terminal by the network, and the embodiments of the present application do not limit this.

[0033] In addition, in the embodiments of the present application, the multicast service in which the terminal is interested can be a multicast service that the terminal intends to receive. It can be understood that the multicast service in which the terminal is interested can be one multicast service, or can include multiple multicast services. For example, one multicast service can also be one program.

[0034] In some embodiments, in the case that the communication device is a terminal, the terminal can determine the multicast service of interest according to the relevant information of the multicast service, such as the identifier (ID) of the multicast service, the service start time, the service end time, the frequency of receiving the multicast service, the cell list for receiving the multicast service, and the like. If the terminal is interested in a certain multicast service, the terminal can report the multicast service of interest to the network side device, for example, by joining the multicast session group corresponding to the multicast service of interest, the terminal can report the multicast service of interest to the network side device.

[0035] In some other embodiments, in the case that the communication device is a network side device, the network side device can determine the multicast service of interest of the terminal according to the multicast service of interest reported by the terminal, for example, according to the multicast session group joined by the terminal.

[0036] In the embodiments of the present application, the communication device can determine the first time period according to a start time and an end time. The start time and the end time can have various implementation forms.

[0037] Optionally, the start time of the first time period can include at least one of the following:

[0038] (1) the time when the terminal is interested in the multicast service of interest;

[0039] (2) the session start time of the multicast service of interest of the terminal;

[0040] (3) in the case that the communication device is a network side device, the start time is the time when the network side device starts to send the data of the multicast service of interest of the terminal; or in the case that the communication device is a terminal, the start time is the time when the terminal starts to receive the data of the multicast service of interest of the terminal;

[0041] (4) the time when the multicast service of interest of the terminal becomes going to active state;

[0042] (5) if the session start time of the multicast service of interest of the terminal is earlier than the first time, the start time of the first time period is the first time, and the first time is the time when the terminal is interested in the multicast service of interest.

[0043] In some embodiments, in the case that the multicast service of interest to the terminal is one multicast service (such as multicast service A), the starting moment of the first time period can be a moment related to the multicast service A. For example, taking the (1) above as an example, the starting moment of the first time period can be the moment at which the terminal is interested in the multicast service A. For another example, taking the (4) above as an example, the starting moment of the first time period can be the moment at which the multicast service A becomes active.

[0044] It should be noted that the moment at which the terminal is interested in a certain multicast service can be the moment at which the terminal joins a multicast session group corresponding to the multicast service, or can be the moment at which the terminal determines to want to receive the multicast service. Of course, in actual implementation, it can also be other possible moments, and the embodiments of the present application do not limit this.

[0045] In addition, if a certain multicast service becomes active, it means that there is currently data that needs to be sent to the terminal that joins the multicast session group. That is, if the terminal has joined the multicast session group, the terminal can receive the data of the multicast service when the multicast service is in the active state.

[0046] In some other embodiments, in the case that the multicast service of interest to the terminal includes multiple multicast services (i.e., at least two multicast services), the starting moment of the first time period can be a moment related to a certain multicast service of the at least two multicast services.

[0047] The following will be described in detail in combination with some examples:

[0048] (A) In the (1) above, the moment at which the terminal is interested in the multicast service of interest is the moment at which the terminal is interested in the third multicast service, and the third multicast service can be the multicast service that the terminal is interested in earliest among the at least two multicast services. In other words, the moment at which the terminal is interested in the multicast service of interest is the earliest moment at which the terminal is interested in the multicast service among the at least two multicast services.

[0049] In one example, it is assumed that the multicast service of interest to the terminal includes three multicast services, namely multicast service A, multicast service B, and multicast service C. Among them, the moment at which the terminal is interested in the multicast service A is 8 o'clock in the morning, the moment at which the terminal is interested in the multicast service B is 9 o'clock in the morning, and the moment at which the terminal is interested in the multicast service C is 11 o'clock in the morning. In this case, the terminal is interested in the multicast service A earliest, and the multicast service A is the third multicast service described above, so the starting moment of the first time period can be the moment at which the terminal is interested in the multicast service A. That is, the starting moment of the first time period can be 8 o'clock in the morning.

[0050] (B) In the above (2), the session start time of the multicast service of interest to the terminal is the session start time of the multicast service that starts earliest among the at least two multicast services.

[0051] In one example, the multicast services of interest to the terminal are still the above three multicast services. Among them, the session start time of the multicast service A is 3 pm, the session start time of the multicast service B is 10 am, and the session start time of the multicast service C is 11 am. In this case, the multicast service B is the multicast service that starts earliest among the three multicast services, and thus the start time of the first time period can be the session start time of the multicast service B.

[0052] (C) In the above (3), the time at which the network-side device starts to send the data of the multicast service of interest to the terminal is the start time at which the network-side device starts to send the data of the fourth multicast service, the fourth multicast service being the multicast service that is sent earliest by the network-side device among the at least two multicast services; and the time at which the terminal starts to receive the data of the multicast service of interest to the terminal is the start time at which the terminal starts to receive the data of the fifth multicast service, the fifth multicast service being the multicast service that is received earliest by the terminal among the at least two multicast services.

[0053] In one example, it is assumed that the multicast services of interest to the terminal include two multicast services, namely, the multicast service A and the multicast service B. Among them, the time at which the terminal starts to receive the data of the multicast service A is 4 pm, and the time at which the terminal starts to receive the data of the multicast service B is 6 pm. In this case, the multicast service A is the multicast service that is received earliest by the terminal, i.e., the fifth multicast service, and thus the start time of the first time period can be the time at which the terminal starts to receive the data of the multicast service A, i.e., 6 pm.

[0054] (D) In the above (4), the time at which the multicast service of interest to the terminal becomes active is the time at which the multicast service that becomes active earliest among the at least two multicast services becomes active.

[0055] In one example, it is assumed that the multicast services of interest to the terminal include three multicast services, namely, the multicast service A, the multicast service B, and the multicast service C. Among them, the time at which the multicast service A becomes active is 11 am, the time at which the multicast service B becomes active is 3 pm, and the time at which the multicast service C becomes active is 5 pm. In this case, the multicast service A is the multicast service that becomes active earliest among the three multicast services, and thus the start time of the first time period can be the time at which the multicast service A becomes active.

[0056] (E) In the above (5), the first moment (i.e. the moment when the terminal is interested in the multicast service of interest) is the moment when the terminal is interested in the third multicast service, wherein the third multicast service is the multicast service that the terminal is interested in earliest among at least two multicast services.

[0057] In one example, suppose the multicast services that the terminal is interested in include three multicast services: multicast service A, multicast service B, and multicast service C. For example... Figure 3 As shown, the session start time of multicast service A is time K1, and the terminal becomes interested in multicast service A at time K2, with time K1 earlier than time K2; the session start time of multicast service B is time K4, and the terminal becomes interested in multicast service B at time K3, with time K4 later than time K3; the session start time of multicast service C is time K5, and the terminal becomes interested in multicast service C at time K6, with time K5 earlier than time K6. In this case, the terminal becomes interested in multicast service A the earliest, meaning the third multicast service is multicast service A. Therefore, the start time of the first time period is the time when the terminal becomes interested in multicast service A (i.e., time K2).

[0058] It should be noted that, in this embodiment of the application, when the multicast service of interest to the terminal is multiple multicast services, the times related to each multicast service can be of the same type (e.g., the times when all multicast services become active), and the start time of the first time period is the earliest of these times. Alternatively, the times related to each multicast service can also be of different types, and the start time of the first time period can be the earliest of these times. For example, taking the multicast services of interest to the terminal as including three multicast services (multicast service A, multicast service B, and multicast service C), the time related to multicast service A can be, for example, the time when the terminal becomes interested in multicast service A; the time related to multicast service B can be, for example, the session start time of multicast service B; and the time related to multicast service C can be, for example, the time when multicast service C becomes active. Then, the start time of the first time period can be the earliest of the above three times.

[0059] Optionally, in this embodiment of the application, the end time of the first time period may include at least one of the following:

[0060] (1) The moment when the terminal is no longer interested in the multicast service it was interested in;

[0061] (2) The end time of the multicast service that the terminal is interested in;

[0062] (3) The moment when the multicast service that the terminal is interested in becomes inactive.

[0063] In some embodiments, in the case that the multicast service of interest to the terminal is one multicast service (such as multicast service A), the ending moment of the first time period can be a moment related to the multicast service A. For example, taking the (1) above as an example, the ending moment of the first time period can be the moment at which the terminal is no longer interested in the multicast service A. For another example, taking the (3) above as an example, the ending moment of the first time period can be the moment at which the multicast service A becomes inactive.

[0064] It should be noted that the moment at which the terminal is no longer interested in a certain multicast service can be the moment at which the terminal leaves the session group of the multicast service; or can be the moment at which the terminal determines that it no longer wants to receive the multicast service. Of course, in actual implementation, the moment at which the terminal is no longer interested in a certain multicast service can also be other possible moments, and the embodiments of the present application do not limit this.

[0065] In addition, if a certain multicast service becomes inactive, it means that there is currently no data that needs to be sent to the terminal that joins the multicast session group. That is, if the terminal joins the multicast session group, the terminal cannot receive the data of the multicast service when the multicast service is in the inactive state.

[0066] In other embodiments, in the case that the multicast service of interest to the terminal is multiple multicast services (i.e., at least two multicast services), the ending moment of the first time period can be a moment related to a certain multicast service of the at least two multicast services.

[0067] The following will be described in detail in combination with some examples:

[0068] (a) In the (1) above, the moment at which the terminal is no longer interested in the multicast service of interest to the terminal is the moment at which the terminal is no longer interested in the sixth multicast service, which is the multicast service that the terminal is no longer interested in the latest among the at least two multicast services. In other words, the moment at which the terminal is no longer interested in the multicast service of interest to the terminal is the latest moment at which the terminal is no longer interested in the multicast service among the at least two multicast services.

[0069] In one example, it is assumed that the multicast service of interest to the terminal includes 3 multicast services, which are multicast service A, multicast service B, and multicast service C. Among them, the moment at which the terminal is no longer interested in the multicast service A is T1 moment, the moment at which the terminal is no longer interested in the multicast service B is T2 moment, and the moment at which the terminal is no longer interested in the multicast service C is T3 moment, and T1 moment is earlier than T2 moment, and T2 moment is earlier than T3 moment. In this case, the terminal is no longer interested in the multicast service C the latest, and the multicast service C is the sixth multicast service in the above, so that the ending moment of the first time period can be the moment at which the terminal is no longer interested in the multicast service C. That is, the ending moment of the first time period can be T3 moment.

[0070] (b) In the above (2), the ending time of the multicast service of interest to the terminal is the ending time of the multicast service that ends latest among the at least two multicast services.

[0071] In an example, the multicast services of interest to the terminal are still the above-mentioned three multicast services. Among them, the ending time of the multicast service A is 3 pm every day, the ending time of the multicast service B is 10 am every day, and the ending time of the multicast service C is 11 am every day. In this case, the multicast service A is the multicast service that ends latest among the three multicast services, and then the ending time of the first time period can be the ending time of the multicast service A.

[0072] (c) In the above (3), the time when the multicast service of interest to the terminal becomes inactive is the time when the multicast service that becomes inactive latest among the at least two multicast services becomes inactive.

[0073] In an example, the multicast services of interest to the terminal are still the above-mentioned three multicast services. Among them, the time when the multicast service A becomes inactive is 11 am every day, the time when the multicast service B becomes inactive is 3 pm every day, and the time when the multicast service C becomes inactive is 5 pm every day. In this case, the multicast service C is the multicast service that becomes inactive latest among the three multicast services, and then the ending time of the first time period can be the time when the multicast service C becomes inactive.

[0074] Optionally, the above-mentioned first information can include at least one of the following:

[0075] receiving the multicast service of interest only in the RRC connected state;

[0076] receiving the multicast service of interest in the RRC inactive state.

[0077] Among them, receiving the multicast service of interest only in the RRC connected state can include at least one of the following:

[0078] only acquiring the configuration information of the multicast service of interest in the RRC connected state;

[0079] receiving the multicast service of interest only in the RRC connected state.

[0080] Among them, receiving the multicast service of interest in the RRC inactive state can include at least one of the following:

[0081] receiving the multicast service of interest only in the RRC inactive state;

[0082] receiving the multicast service of interest in both the RRC inactive state and the RRC connected state;

[0083] not receiving the multicast service of interest in the RRC idle state.

[0084] Exemplarily, the receiving the multicast service of interest in the RRC inactive state can comprise: receiving configuration information of the multicast service of interest in the RRC inactive state. For example, in the case that the multicast service of interest is broadcasted, the terminal can receive the configuration information of the multicast service of interest in the RRC inactive state.

[0085] In some embodiments, the above-mentioned principles of RRC state change can comprise at least one of the following:

[0086] (I) If the multicast service of interest of the terminal comprises at least one first multicast service, the RRC state of the terminal is the RRC connected state, and the first multicast service is a multicast service that can only be received in the RRC connected state;

[0087] (II) If all the multicast services of interest of the terminal are multicast services that can be received in the RRC inactive state, the RRC state of the terminal is the RRC inactive state or the RRC connected state;

[0088] (III) If an event of changing the RRC state of the terminal occurs, and the multicast services of interest of the terminal comprise at least one second multicast service, the RRC state of the terminal is the RRC state corresponding to the first object, and the first object is the object with higher priority between the event and the at least one second multicast service; wherein the second multicast service is a multicast service that cannot be received in the RRC state corresponding to the event;

[0089] (IV) If an event of changing the RRC state of the terminal occurs, and the multicast services of interest of the terminal comprise at least one second multicast service, the RRC state of the terminal is determined according to the control information sent by the network side device;

[0090] (V) In the case that the terminal is in the RRC inactive state or the RRC connected state, if an event of changing the RRC state of the terminal occurs, and the multicast services of interest of the terminal do not support being received in the RRC state corresponding to the event, the RRC state of the terminal is consistent with the RRC state corresponding to the event.

[0091] It should be noted that the above-mentioned (I), (II), (III) and (V) correspond to four principles that can be applicable to the network side device and the terminal device, and the above-mentioned (IV) corresponds to a principle that can be applicable to the terminal device. In addition, in the principle corresponding to (III), the priority of the multicast service and the priority of the event of changing the RRC state of the terminal can be configured or indicated to the terminal by the network side device.

[0092] Exemplarily, the principle corresponding to (V) can comprise at least one of the following:

[0093] (V A) In case that the terminal is in the RRC connected state, if at least one of the multicast services interested by the terminal includes a multicast service supported to be received in the RRC connected state, and an event occurs to make the terminal change from the RRC connected state to the RRC idle state or the RRC inactive state, the RRC state of the terminal is consistent with the RRC state corresponding to the event;

[0094] (V B) In case that the terminal is in the RRC connected state, if all the multicast services interested by the terminal are multicast services received in the RRC inactive state, and an event occurs to make the terminal change from the RRC connected state to the RRC idle state, the RRC state of the terminal is the RRC idle state;

[0095] (V C) In case that the terminal is in the RRC inactive state, if none of the multicast services interested by the terminal includes a multicast service received in the RRC idle state, and an event occurs to make the terminal change from the RRC inactive state to the RRC idle state, the RRC state of the terminal is the RRC idle state.

[0096] Wherein, the RRC state corresponding to the event of changing the RRC state of the terminal can be the RRC state after the change according to the event. For example, the event of changing the RRC state of the terminal can be "when the terminal in the RRC connected state receives the indication information that the timer of the underlying transmission expires, the terminal enters the RRC idle state from the RRC connected state", and the RRC state corresponding to the event can be the RRC idle state.

[0097] In the embodiments of the present application, the event of making the RRC state of the terminal change from the RRC connected state to the RRC idle state can include the following events:

[0098] ① Synchronization reconfiguration

[0099] The terminal should perform the following operations to perform the synchronization reconfiguration:

[0100] If the access stratum (AS) security is not activated, the operation of entering the RRC idle state is performed, and the release reason is "other".

[0101] ② The terminal receives the RRC reestablishment message

[0102] If the integrity protection check of the RRC reestablishment message fails, the terminal performs the operation of entering the RRC idle state, and the release reason is "RRC connection failure".

[0103] ③ Timer T311 expires

[0104] If the timer T311 is triggered by radio link failure or handover failure, the terminal sets the value of noSuitableCellFound in VarRLF-Report to "true" once the timer T311 expires;

[0105] The terminal performs the operation of entering the RRC idle state and releases the cause "RRC connection failure".

[0106] In the embodiments of the present application, the event of changing the RRC state of the terminal from the RRC inactive state to the RRC idle state can include the following events:

[0107] ① Failure to comply with the RRC resume message

[0108] If the terminal fails to perform part or all of the configuration in the RRC resume message, the terminal performs the operation of entering the RRC idle state and releases the cause "RRC resume failure".

[0109] ② RAN-based Notification Area (RNA) update

[0110] If the terminal in the RRC inactive state fails to find a suitable cell and resides on an acceptable cell in order to obtain limited services, the terminal performs the operation of entering the RRC idle state and releases the cause "other".

[0111] ③ inter-RAT cell reselection

[0112] When reselecting to an inter-RAT cell, the terminal performs the operation of entering the RRC idle state and releases the cause "other".

[0113] Of course, the events listed in the above embodiments are only some examples, and there are many other events that change the RRC state of the terminal in specific implementations, which are not described in detail in the embodiments of the present application.

[0114] In some embodiments, when the communication device is a terminal, the RRC state change principle can include: if the multicast service of interest of the terminal includes at least one multicast service that is only received in the RRC connected state, the RRC state of the terminal is the RRC connected state, that is, the principle corresponding to the above (I).

[0115] In the above case, controlling the RRC state of the terminal can include at least one of the following:

[0116] In the case where the terminal is in the RRC connected state, the triggering condition of the first event is disabled, and the first event is an event of changing the RRC state of the terminal to the non-RRC connected state;

[0117] ignoring the first event when the terminal is in the RRC connected state;

[0118] not performing the operation of changing the RRC state of the terminal to the non-RRC connected state after the first event occurs when the terminal is in the RRC connected state;

[0119] deactivating the trigger condition of the second event when the terminal is in the RRC inactive state, the second event being an event of changing the RRC state of the terminal to the RRC idle state;

[0120] ignoring the second event when the terminal is in the RRC inactive state;

[0121] not performing the operation of changing the RRC state of the terminal to the RRC idle state after the second event occurs when the terminal is in the RRC inactive state;

[0122] controlling the terminal to change from the RRC inactive state to the RRC connected state when the terminal is in the RRC inactive state.

[0123] In the prior art, when a terminal in the RRC connected state receives an indication that a data inactivity timer has expired, the terminal performs an operation of entering the RRC idle state. In the embodiments of the present application, when the terminal receives the indication that the timer has expired, if the terminal has a multicast service of interest and at least one multicast service of interest of the terminal includes a multicast service that can only be received in the RRC connected state according to the first information, the terminal can control the RRC state of the terminal based on the RRC state change principle before the multicast service of interest ends. Based on this, the operation of the terminal to control the RRC state can include at least one of the following:

[0124] deactivating the data inactivity timer;

[0125] stopping or starting the data inactivity timer;

[0126] not performing the operation of entering the RRC idle state and remaining in the RRC connected state.

[0127] In the prior art, if a terminal in the RRC inactive state cannot perform part or all of the configuration in the RRC resume message, the terminal performs an operation of entering the RRC idle state. In the embodiments of the present application, when the event occurs, if the terminal has a multicast service of interest and at least one multicast service of interest of the terminal includes a multicast service that can only be received in the RRC connected state, the terminal can control the RRC state of the terminal based on the RRC state change principle before the multicast service of interest ends. Based on this, the operation of the terminal to control the RRC state can include at least one of the following:

[0128] whether the terminal is capable of performing part of the configuration or all of the configuration in the RRC resume message is not determined;

[0129] the event that the terminal is incapable of performing part of the configuration or all of the configuration in the RRC resume message is ignored;

[0130] the operation of entering the RRC idle state is not performed;

[0131] the RRC state of the terminal is changed from the RRC inactive state to the RRC connected state.

[0132] In some embodiments, when the communication device is the terminal, the RRC state change principle can include: if all the multicast services of interest to the terminal are multicast services received in the RRC inactive state, the RRC state of the terminal is the RRC inactive state or the RRC connected state, i.e., the principle corresponding to (II) above.

[0133] Based on this, controlling the RRC state of the terminal can include at least one of the following:

[0134] In the case where the terminal is in the RRC connected state, the triggering condition of a third event is disabled, the third event being an event of changing the RRC state of the terminal to the RRC idle state;

[0135] In the case where the terminal is in the RRC connected state, the third event is ignored;

[0136] In the case where the terminal is in the RRC connected state, after the third event occurs, the operation of changing the RRC state of the terminal to the RRC idle state is not performed;

[0137] In the case where the terminal is in the RRC connected state, the terminal is controlled to remain in the RRC connected state or to change to the RRC inactive state;

[0138] In the case where the terminal is in the RRC inactive state, the triggering condition of a fourth event is disabled, the fourth event being an event of changing the RRC state of the terminal to the RRC idle state;

[0139] In the case where the terminal is in the RRC inactive state, the fourth event is ignored;

[0140] In the case where the terminal is in the RRC inactive state, after the fourth event occurs, the operation of changing the RRC state of the terminal to the RRC idle state is not performed;

[0141] In the case where the terminal is in the RRC inactive state, the terminal is controlled to remain in the RRC inactive state or to change to the RRC connected state.

[0142] Exemplarily, in the prior art, when a terminal in an RRC connected state receives an indication that a data inactivity timer has expired, the terminal should perform an operation of entering an RRC idle state. In embodiments of the present application, when the terminal receives the indication that the timer has expired, if the terminal has interested multicast services and can determine, according to the first information, that all the multicast services of interest to the terminal are multicast services received in an RRC inactive state, the terminal can control its RRC state based on the above RRC state change principle before the multicast services of interest end. Based on this, the operation of the terminal to control the RRC state can include at least one of the following:

[0143] disabling the data inactivity timer;

[0144] stopping or starting the data inactivity timer;

[0145] not performing the operation of entering the RRC idle state;

[0146] remaining in the RRC connected state or becoming in the RRC inactive state.

[0147] Exemplarily, in the prior art, if a terminal in an RRC inactive state cannot perform part or all of the configurations in an RRC resume message, the terminal performs an operation of entering an RRC idle state. In embodiments of the present application, when the above event occurs, if the terminal has interested multicast services and all the multicast services of interest to the terminal are multicast services received in an RRC inactive state, the terminal can control its RRC state based on the above RRC state change principle before the multicast services of interest end. Based on this, the operation of the terminal to control the RRC state can include at least one of the following:

[0148] not judging whether the terminal can perform part or all of the configurations in the RRC resume message;

[0149] ignoring the event that the terminal cannot perform part or all of the configurations in the RRC resume message;

[0150] not performing the operation of entering the RRC idle state;

[0151] remaining in the RRC inactive state or becoming in the RRC connected state.

[0152] In some embodiments, when the communication device is a terminal, the RRC state change principle can include: if an event of changing the RRC state of the terminal occurs, and at least one second multicast service (i.e., a multicast service that does not support being received in an RRC state corresponding to the event) is included in the multicast services of interest to the terminal, the RRC state of the terminal is an RRC state corresponding to a first object, i.e., the principle corresponding to (III) above.

[0153] In the above case, the controlling of the RRC state of the terminal can include at least one of:

[0154] In the case where the terminal is in the RRC connected state, if the priority of the at least one second multicast service is higher, an operation of changing the RRC state of the terminal to the RRC state corresponding to the event changing the RRC state of the terminal is not performed;

[0155] In the case where the terminal is in the RRC connected state and the at least one second multicast service includes a second multicast service received only in the RRC connected state, if the priority of the second multicast service received only in the RRC connected state is higher, the terminal is controlled to remain in the RRC connected state;

[0156] In the case where the terminal is in the RRC connected state and the at least one second multicast service is all multicast services received in the RRC inactive state, if the priority of the at least one second multicast service is higher, the terminal is controlled to remain in the RRC connected state or to change to the RRC inactive state;

[0157] In the case where the terminal is in the RRC connected state, if the priority of the event changing the RRC state of the terminal is higher, the RRC state of the terminal is controlled to change to the RRC state corresponding to the event;

[0158] In the case where the terminal is in the RRC inactive state, if the priority of the at least one second multicast service is higher, an operation of changing the RRC state of the terminal to the RRC idle state is not performed;

[0159] In the case where the terminal is in the RRC inactive state and the at least one second multicast service includes a second multicast service received only in the RRC connected state, if the priority of the second multicast service received only in the RRC connected state is higher, the terminal is controlled to change from the RRC inactive state to the RRC connected state;

[0160] In the case where the terminal is in the RRC inactive state and the at least one multicast service is all multicast services received in the RRC inactive state, if the priority of the at least one multicast service is higher, the terminal is controlled to remain in the RRC inactive state or to change to the RRC connected state;

[0161] In the case where the terminal is in the RRC inactive state, if the priority of the event changing the RRC state of the terminal is higher, the RRC state of the terminal is controlled to change to the RRC state corresponding to the event.

[0162] It should be noted that in the above embodiments, the "at least one second multicast service with higher priority" can be one or more second multicast services in the at least one second multicast service with a priority higher than the event of changing the RRC state of the terminal. The priority of the at least one second multicast service can be different, or partially the same, or all the same, which is not limited in the embodiments of the present application. It can be easily understood that in the case where the priorities of the second multicast services are all the same, when determining whether the priority of the at least one second multicast service is higher, the terminal can only determine whether the priority of any one of the second multicast services is higher than the event of changing the RRC state of the terminal.

[0163] In addition, the second multicast service received only in the RRC connected state can be one second multicast service or multiple second multicast services. In the case where the second multicast service received only in the RRC connected state is multiple second multicast services, if at least one second multicast service with higher priority is included, the terminal in the RRC connected state can remain in the RRC connected state, and the terminal in the RRC inactive state can become the RRC connected state.

[0164] For example, in the prior art, when the terminal in the RRC connected state receives an indication that the data inactivity timer from the underlying layer is overdue, the terminal should perform the operation of entering the RRC idle state. In the embodiments of the present application, when the terminal receives the indication that the timer is overdue, if the terminal has multicast services of interest, and according to the first information, it can be determined that at least one second multicast service (which does not support reception in the RRC idle state) is included in the multicast services of interest of the terminal, the terminal can control the RRC state of the terminal based on the RRC state change principle before all the multicast services of interest end. Based on this, the operation of the terminal to control the RRC state can include at least one of the following:

[0165] If the priority of the at least one second multicast service is higher, the terminal does not perform the operation of entering the RRC idle state;

[0166] In the case where the at least one second multicast service includes one second multicast service received only in the RRC connected state, if the priority of the second multicast service is higher, the terminal remains in the RRC connected state;

[0167] In the case where the at least one second multicast service is all multicast services received in the RRC inactive state, if the priority of the at least one second multicast service is higher, the terminal remains in the RRC connected state or becomes the RRC inactive state;

[0168] If the priority of the event (i.e., receiving an indication that the data inactivity timer from the underlying layer is overdue) is higher, the RRC state of the terminal becomes the RRC idle state.

[0169] In the prior art, if the terminal in the RRC inactive state cannot perform part or all of the configuration in the RRC resume message, the terminal performs the operation of entering the RRC idle state. In the embodiments of the present application, when the above event occurs, if the terminal has interested multicast services and the interested multicast services of the terminal include at least one second multicast service (which does not support reception in the RRC inactive state), the terminal can control its RRC state based on the above RRC state change principle before the interested multicast services end. In the above example, the operation of the terminal to control the RRC state can include at least one of the following:

[0170] If the priority of the at least one second multicast service is higher, the terminal does not perform the operation of entering the RRC idle state;

[0171] In the case where the at least one second multicast service includes one second multicast service that is only received in the RRC connected state, if the priority of the second multicast service is higher, the terminal becomes the RRC connected state;

[0172] In the case where the at least one second multicast service is all multicast services received in the RRC inactive state, if the priority of the at least one second multicast service is higher, the terminal remains in the RRC inactive state or becomes the RRC connected state;

[0173] If the priority of the above event (i.e., the terminal in the RRC inactive state cannot perform part or all of the configuration in the RRC resume message) is higher, the RRC state of the terminal becomes the RRC idle state.

[0174] In some embodiments, in the case where the communication device is a terminal, the wireless resource control state control method provided by the embodiments of the present application can further include the following S202.

[0175] S202, the terminal acquires first information and / or an RRC state change principle.

[0176] In the embodiments of the present application, the terminal acquiring the first information and / or the RRC state change principle can be that the terminal reads the preconfigured first information and / or the RRC state change principle, or the terminal receives the first information and / or the RRC state change principle sent by the network side. The specific determination can be made according to actual use requirements, and the embodiments of the present application are not limited.

[0177] In the embodiments of the present application, the terminal can acquire the first information in at least one of two ways (first implementation and second implementation).

[0178] The first implementation method: The terminal obtains service information of the multicast service that it is interested in. This multicast service information may include the first piece of information.

[0179] For example, the aforementioned service information may include the multicast service ID, service start time, service end time, frequency of receiving multicast services, and list of cells receiving multicast services.

[0180] It should be noted that, in this embodiment of the application, after the terminal obtains the service information of the multicast service, the terminal can receive the multicast service according to the service information of the multicast service.

[0181] The second implementation method is as follows: During the process of the terminal reporting the multicast service it is interested in to the network-side device, such as when the terminal joins the multicast session group corresponding to the multicast service it is interested in, the terminal receives the first information sent by the network-side device.

[0182] It should be noted that, in this embodiment of the application, when the terminal obtains the first information through the second implementation method described above, the service information of the multicast service may not include the first information.

[0183] In this embodiment of the application, since the communication device can determine the RRC state that the terminal should be in when receiving the multicast service of interest based on the first information, and can determine how the RRC state of the terminal changes under different circumstances based on the RRC state change principle, during the first time period associated with the multicast service of interest to the terminal, if an event that changes the RRC state of the terminal occurs when the terminal has the multicast service of interest, the communication device can accurately control the RRC state of the terminal based on the first information and the RRC state change principle.

[0184] It should be noted that the execution entity of the above-described wireless resource control state control method provided in this application embodiment can be a wireless resource control state control device, or a control module in the wireless resource control state control device for executing the above-described wireless resource control state control method. This application embodiment uses the execution of the above-described wireless resource control state control method by a wireless resource control state control device as an example to illustrate the wireless resource control state control device provided in this application embodiment.

[0185] like Figure 4 The diagram illustrates a Radio Resource Control (RRC) state control device 400 provided in this application embodiment. This device can be applied to communication equipment and includes a control module 401. The control module 401 is used to control the RRC state of a terminal within a first time period, based on first information and RRC state change principles. The first time period is a time period associated with the multicast service of interest to the terminal. The first information is used to determine the RRC state of the terminal receiving the multicast service of interest.

[0186] In some embodiments, the first information can comprise at least one of:

[0187] the multicast service of interest is received only in the RRC connected state;

[0188] the multicast service of interest is received in the RRC inactive state.

[0189] In some embodiments, the RRC state change principle comprises at least one of:

[0190] if the multicast service of interest comprises at least one first multicast service, the RRC state of the terminal is the RRC connected state, and the first multicast service is a multicast service received only in the RRC connected state;

[0191] if all the multicast service of interest is a multicast service received in the RRC inactive state, the RRC state of the terminal is the RRC inactive state or the RRC connected state;

[0192] if an event occurs to change the RRC state of the terminal, and the multicast service of interest comprises at least one second multicast service, the RRC state of the terminal is the RRC state corresponding to the first object, the first object is the object with higher priority in the event and the at least one second multicast service, and the second multicast service is a multicast service not supported to be received in the RRC state corresponding to the event;

[0193] if an event occurs to change the RRC state of the terminal, and the multicast service of interest comprises at least one second multicast service, the RRC state of the terminal is determined according to the control information sent by the network side device.

[0194] In some embodiments, the starting time of the first time period can comprise at least one of:

[0195] the time when the terminal is interested in the multicast service of interest;

[0196] the session start time of the multicast service of interest;

[0197] the time when the network side device starts to send data of the multicast service of interest; or, the time when the terminal starts to receive data of the multicast service of interest;

[0198] the time when the multicast service of interest becomes active;

[0199] if the session time of the multicast service of interest is earlier than the first time, the starting time of the first time period is the first time. Wherein, the first time is the time when the terminal is interested in the multicast service of interest.

[0200] In the embodiments of the present application, the multicast service of interest of the terminal can include at least two multicast services. In this case, the time when the terminal is interested in the multicast service of interest can be the time when the terminal is interested in the third multicast service, the third multicast service being the multicast service of the at least two multicast services that the terminal is interested in earliest.

[0201] In the embodiments of the present application, the multicast service of interest of the terminal can include at least two multicast services. In this case, the session start time of the multicast service of interest can be the session start time of the multicast service of the at least two multicast services that starts earliest.

[0202] In the embodiments of the present application, the multicast service of interest of the terminal can include at least two multicast services. In this case, the time when the network side device starts to send the data of the multicast service of interest can be the start time when the network side device sends the data of the fourth multicast service, the fourth multicast service being the multicast service of the at least two multicast services that the network side device sends earliest. The time when the terminal starts to receive the data of the multicast service of interest can be the start time when the terminal receives the data of the fifth multicast service, the fifth multicast service being the multicast service of the at least two multicast services that the terminal receives earliest.

[0203] In the embodiments of the present application, the multicast service of interest of the terminal can include at least two multicast services. In this case, the time when the multicast service of interest of the terminal becomes active can be the time when the multicast service of the at least two multicast services that becomes active earliest becomes active.

[0204] In the embodiments of the present application, the end time of the first time period can include at least one of the following:

[0205] The time when the terminal is no longer interested in the multicast service of interest;

[0206] The end time of the multicast service of interest;

[0207] The time when the multicast service of interest becomes inactive.

[0208] In the embodiments of the present application, the multicast service of interest of the terminal can include at least two multicast services. In this case, the time when the terminal is no longer interested in the multicast service of interest can be the time when the terminal is no longer interested in the sixth multicast service, the sixth multicast service being the multicast service of the at least two multicast services that the terminal is no longer interested in latest.

[0209] In the embodiments of the present application, the multicast service of interest of the terminal can include at least two multicast services. In this case, the end time of the multicast service of interest can be the end time of the multicast service of the at least two multicast services that ends latest.

[0210] In the embodiments of the present application, the multicast service of interest of the terminal can include at least two multicast services. In this case, the time when the multicast service of interest becomes the inactive state is the time when the multicast service that becomes the inactive state latest among the at least two multicast services becomes the inactive state.

[0211] In the embodiments of the present application, the principle of RRC state change can include: if the multicast service of interest includes at least one first multicast service, the RRC state of the terminal is the RRC connected state.

[0212] In the above case, if the communication device is a terminal, the control of the RRC state of the terminal can include at least one of the following:

[0213] In the case where the terminal is in the RRC connected state, the triggering condition of the first event is disabled, the first event being an event of changing the RRC state of the terminal to the non-RRC connected state;

[0214] In the case where the terminal is in the RRC connected state, the first event is ignored;

[0215] In the case where the terminal is in the RRC connected state, after the first event occurs, an operation of changing the RRC state of the terminal to the non-RRC connected state is not performed;

[0216] In the case where the terminal is in the RRC inactive state, the triggering condition of the second event is disabled, the second event being an event of changing the RRC state of the terminal to the RRC idle state;

[0217] In the case where the terminal is in the RRC inactive state, the second event is ignored;

[0218] In the case where the terminal is in the RRC inactive state, after the second event occurs, an operation of changing the RRC state of the terminal to the RRC idle state is not performed;

[0219] In the case where the terminal is in the RRC inactive state, the terminal is controlled to change from the RRC inactive state to the RRC connected state.

[0220] In the embodiments of the present application, the principle of RRC state change can include: if all the multicast services of interest are multicast services received in the RRC inactive state, the RRC state of the terminal is the RRC inactive state or the RRC connected state.

[0221] In the above case, if the communication device is a terminal, the control of the RRC state of the terminal can include at least one of the following:

[0222] In the case where the terminal is in the RRC connected state, the triggering condition of the third event is disabled, the third event being an event of changing the RRC state of the terminal to the RRC idle state;

[0223] The third event is ignored when the terminal is in the RRC connected state;

[0224] The operation of changing the RRC state of the terminal to the RRC idle state is not performed after the third event occurs when the terminal is in the RRC connected state;

[0225] The terminal is controlled to remain in the RRC connected state or change to the RRC inactive state when the terminal is in the RRC connected state;

[0226] The triggering condition of the fourth event is disabled when the terminal is in the RRC inactive state, the fourth event being an event of changing the RRC state of the terminal to the RRC idle state;

[0227] The fourth event is ignored when the terminal is in the RRC inactive state;

[0228] The operation of changing the RRC state of the terminal to the RRC idle state is not performed after the fourth event occurs when the terminal is in the RRC inactive state;

[0229] The terminal is controlled to remain in the RRC inactive state or change to the RRC connected state when the terminal is in the RRC inactive state.

[0230] In the embodiments of the present application, the RRC state change principle can include: if an event of changing the RRC state of the terminal occurs, and the interested multicast service includes at least one second multicast service, the RRC state of the terminal is the RRC state corresponding to the first object.

[0231] In the above case, if the communication device is a terminal, the RRC state of the terminal can be controlled as follows:

[0232] If the priority of the at least one second multicast service is higher, the operation of changing the RRC state of the terminal to the RRC state corresponding to the event is not performed when the terminal is in the RRC connected state;

[0233] If the priority of the only RRC connected state received second multicast service is higher, the terminal is controlled to remain in the RRC connected state when the terminal is in the RRC connected state and the at least one second multicast service includes an only RRC connected state received second multicast service;

[0234] If the priority of the at least one second multicast service is higher, the terminal is controlled to remain in the RRC connected state or change to the RRC inactive state when the terminal is in the RRC connected state and the at least one second multicast service is all multicast services received in the RRC inactive state;

[0235] In the case that the terminal is in the RRC connected state, if the priority of the event for changing the RRC state of the terminal is higher, the RRC state of the terminal is controlled to be changed to the RRC state corresponding to the event;

[0236] In the case that the terminal is in the RRC inactive state, if the priority of at least one second multicast service is higher, the operation of changing the RRC state of the terminal to the RRC idle state is not performed;

[0237] In the case that the terminal is in the RRC inactive state, and at least one second multicast service includes a second multicast service received only in the RRC connected state, if the priority of the second multicast service received only in the RRC connected state is higher, the terminal is controlled to be changed from the RRC inactive state to the RRC connected state;

[0238] In the case that the terminal is in the RRC inactive state, and all the at least one second multicast service is a multicast service received in the RRC inactive state, if the priority of at least one second multicast service is higher, the terminal is controlled to remain in the RRC inactive state or be changed to the RRC connected state;

[0239] In the case that the terminal is in the RRC inactive state, if the priority of the event for changing the RRC state of the terminal is higher, the RRC state of the terminal is controlled to be changed to the RRC state corresponding to the event.

[0240] Optionally, as shown in Figure 5 In the case that the communication device is a terminal, the wireless resource control state control apparatus 400 provided by the embodiment of the present application can further include an obtaining module 402. The obtaining module 402 is configured to obtain the first information and / or the RRC state change principle.

[0241] Optionally, as shown in Figure 6 The obtaining module 402 can include an obtaining unit 4021 and / or a receiving unit 4022. The obtaining unit is configured to obtain the service information of the multicast service of interest, and the service information includes the first information. The receiving unit is configured to receive the first information sent by the network side device in the process that the terminal reports the multicast service of interest to the network side device.

[0242] In the embodiment of the present application, the wireless resource control state control apparatus can determine the RRC state in which the terminal should be in for receiving the multicast service of interest according to the first information, and determine how the RRC state of the terminal changes under different conditions according to the RRC state change principle. Therefore, in the first time period associated with the multicast service of interest of the terminal, when the terminal has the multicast service of interest, if an event for changing the RRC state of the terminal occurs, the wireless resource control state control apparatus can accurately control the RRC state of the terminal according to the first information and the RRC state change principle.

[0243] The wireless resource control state control apparatus in the embodiments of the present application can be an electronic device, for example, an electronic device with an operating system, or a component in an electronic device, for example, an integrated circuit or a chip. The electronic device can be a terminal or other device than a terminal. Exemplarily, the terminal can include, but is not limited to, the types of the terminal 11 listed above, and the other device can be a server, a network attached storage (NAS), etc., which are not limited in the embodiments of the present application.

[0244] The wireless resource control state control apparatus provided in the embodiments of the present application can achieve Figure 1 The method embodiments shown achieve various processes and achieve the same technical effects, and to avoid repetition, details are not described herein.

[0245] Optionally, as Figure 7 The communication device 700 is a terminal, the program or instructions stored in the memory 702 and executable by the processor 701 implement each step of the wireless resource control state control method embodiments described above and achieve the same technical effects when executed by the processor 701. The communication device 700 is a network side device, the program or instructions stored in the memory 702 and executable by the processor 701 also implement each step of the wireless resource control state control method embodiments described above and achieve the same technical effects when executed by the processor 701. To avoid repetition, details are not described herein.

[0246] The embodiments of the present application also provide a terminal including a processor and a communication interface. The processor is configured to control a RRC state of the terminal according to first information and a RRC state change principle in a first time period. The communication interface is configured to communicate with other communication devices (such as network side devices). The terminal embodiment corresponds to the wireless resource control state control method embodiments described above, and each implementation process and implementation manner of the method embodiments described above can be applied to the terminal embodiment and achieve the same technical effects. Specifically, Figure 8 To implement a hardware structure of a terminal according to an embodiment of the present application.

[0247] The terminal 800 includes, but is not limited to, at least part of the following components: a radio frequency unit 801, a network module 802, an audio output unit 803, an input unit 804, a sensor 805, a display unit 806, a user input unit 807, an interface unit 808, a memory 809, and a processor 810, etc.

[0248] Those skilled in the art can understand that the terminal 800 can also include a power supply (such as a battery) for supplying power to each component, and the power supply can be logically connected to the processor 810 through a power management system, so that the power management system can realize the functions of managing charging, discharging, and power consumption management. Figure 8 The terminal structure shown in the figure does not constitute a limitation on the terminal, and the terminal can include more or fewer components than the figure, or combine certain components, or different component arrangements, which are not described here.

[0249] It should be understood that in the embodiments of the present application, the input unit 804 can include a graphics processing unit (GPU) 8041 and a microphone 8042. The graphics processor 8041 processes image data of a still picture or a video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 806 can include a display panel 8061, which can be configured in the form of a liquid crystal display, an organic light-emitting diode, etc. The user input unit 807 includes at least one of a touch panel 8071 and other input devices 8072. The touch panel 8071 is also called a touch screen. The touch panel 8071 can include two parts of a touch detection device and a touch controller. The other input devices 8072 can include, but are not limited to, a physical keyboard, function keys (such as volume control keys, on-off keys, etc.), trackballs, mice, joysticks, which are not described here.

[0250] In the embodiments of the present application, after the radio frequency unit 801 receives the downlink data from the network side device, it can be transmitted to the processor 810 for processing. In addition, the radio frequency unit 801 can send uplink data to the network side device. Generally, the radio frequency unit 801 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0251] The memory 809 can be used to store software programs or instructions and various data. The memory 809 can mainly include a first storage area storing programs or instructions and a second storage area storing data, wherein the first storage area can store an operating system, application programs or instructions required by at least one function (such as a sound playing function, an image playing function, etc.), and the like. In addition, the memory 809 can include a volatile memory or a non-volatile memory, or the memory 809 can include both volatile and non-volatile memories. The non-volatile memory can be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically EPROM (EEPROM), or a flash memory. The volatile memory can be a Random Access Memory (RAM), a Static RAM (SRAM), a Dynamic RAM (DRAM), a Synchronous DRAM (SDRAM), a Double Data Rate SDRAM (DDR SDRAM), an Enhanced SDRAM (ESDRAM), a Synch link DRAM (SLDRAM), and a Direct Rambus RAM (DRRAM). The memory 809 in the embodiments of the present application includes but is not limited to these and any other suitable types of memories.

[0252] The processor 810 can include one or more processing units; optionally, the processor 810 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and an application program, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It can be understood that the above-mentioned modem processor can also not be integrated into the processor 810.

[0253] The processor 810 is configured to control the RRC state of the terminal according to the first information and the RRC state change principle in the first time period.

[0254] Through the scheme, since the terminal can determine the RRC state in which the terminal should be in to receive the multicast service of interest according to the first information, and can determine how the RRC state of the terminal changes in different cases according to the RRC state change principle, therefore, in the first time period associated with the multicast service of interest of the terminal, when the terminal has the multicast service of interest, if an event of changing the RRC state of the terminal occurs, the terminal can accurately control the RRC state of the terminal according to the first information and the RRC state change principle.

[0255] Optionally, the radio frequency unit 801 can be configured to acquire the first information and / or the RRC state change principle.

[0256] Based on the above scheme, the terminal can acquire the first information and / or the RRC state change principle.

[0257] Optionally, the radio frequency unit 801 can be configured to perform at least one of the following:

[0258] Acquire service information of the multicast service of interest, and the service information includes the first information;

[0259] In a process in which the terminal reports the multicast service of interest to the network side device, receive the first information sent by the network side device.

[0260] The embodiment of the application further provides a network side device, including a processor and a communication interface, the processor is used for controlling the RRC state of the terminal according to the first information and the RRC state change principle in the first time period. The communication interface is used for communicating with other communication devices (such as the terminal). The network side device embodiment corresponds to the network side device method embodiment described above, and each implementation process and implementation manner of the method embodiment can be applied to the network side device embodiment, and the same technical effects can be achieved.

[0261] Specifically, the embodiment of the application further provides a network side device. As shown in the Figure 9 network side device 900 includes an antenna 91, a radio frequency device 92, a baseband device 93, a processor 94 and a memory 95. The antenna 91 is connected with the radio frequency device 92. In the uplink direction, the radio frequency device 92 receives information through the antenna 91, and sends the received information to the baseband device 93 for processing. In the downlink direction, the baseband device 93 processes the information to be sent and sends it to the radio frequency device 92, and the radio frequency device 92 processes the received information and sends it out through the antenna 91.

[0262] The method performed by the network side device in the above embodiment can be implemented in the baseband device 93, and the baseband device 93 includes a baseband processor.

[0263] Baseband device 93 may include, for example, at least one baseband board on which multiple chips are disposed, such as Figure 9 As shown, one of the chips is, for example, a baseband processor, which is connected to the memory 95 via a bus interface to call the program in the memory 95 and execute the network-side device operations shown in the above method embodiment.

[0264] The network-side device may also include a network interface 96, such as a common public radio interface (CPRI).

[0265] Specifically, the network-side device 900 of this embodiment further includes: instructions or programs stored in a memory 95 and executable on a processor 94, wherein the processor 94 calls the instructions or programs in the memory 95 to execute. Figures 4 to 6 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0266] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described wireless resource control state control method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0267] The processor is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0268] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described wireless resource control state control method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0269] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0270] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described wireless resource control state control method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0271] It should be noted that, in the present document, the terms "comprises", "comprising", or any other variations 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 can include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by "comprises... a" does not, without more constraints, exclude the presence of additional identical elements in the process, method, article, or apparatus that comprises the element. Furthermore, it is to be understood that the method and apparatus of the present application can be carried out by more than one process, method, article, or apparatus either simultaneously, concurrently, or with intervening action that are carried out at the same time, in any order, or in an overlapping manner. For example, the described method can be performed in a different order or simultaneously, and the various steps can be combined or omitted, or additional steps can be added, without departing from the scope of the described method. Also, features described with respect to certain examples can be combined in other examples.

[0272] From the above description of the embodiments, it is apparent that the above-described method can be implemented by software and necessary universal hardware platform, of course, it can also be implemented by hardware, but in many cases, the former is a better implementation. Based on such understanding, the technical solutions of the present application can be embodied in the form of computer software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a plurality of instructions for making a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) execute the method described in various embodiments of the present application.

[0273] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-described specific embodiments, which are merely illustrative rather than restrictive, and those of ordinary skill in the art can make many forms under the inspiration of the present application without departing from the scope of the present application and the scope protected by the claims.

Claims

1. A radio resource control state control method, characterized by, The method comprises: controlling, by a communication device, a radio resource control (RRC) state of a terminal according to first information and an RRC state change principle during a first time period; wherein the first time period is a time period associated with multicast services of interest to the terminal; and the first information is used to determine an RRC state of the terminal for receiving the multicast services of interest; the RRC state change principle comprises at least one of the following: if the multicast services of interest include at least one first multicast service, the RRC state of the terminal is an RRC connected state, and the first multicast service is a multicast service that can only be received in the RRC connected state; if all the multicast services of interest are multicast services that can be received in an RRC inactive state, the RRC state of the terminal is the RRC inactive state or the RRC connected state; if an event occurs to change the RRC state of the terminal, and the multicast services of interest include at least one second multicast service, the RRC state of the terminal is an RRC state corresponding to a first object, the first object being an object with a higher priority between the event and the at least one second multicast service, and the second multicast service being a multicast service that cannot be received in an RRC state corresponding to the event; if an event occurs to change the RRC state of the terminal, and the multicast services of interest include at least one second multicast service, the RRC state of the terminal is determined according to control information sent by a network side device.

2. The method of claim 1, wherein, The first information comprises at least one of the following: the multicast services of interest can only be received in the RRC connected state; the multicast services of interest can be received in the RRC inactive state.

3. The method of claim 1, wherein, The start time of the first time period comprises at least one of the following: a time when the terminal is interested in the multicast services of interest; a session start time of the multicast services of interest; a time when a network side device starts to send data of the multicast services of interest; or a time when the terminal starts to receive data of the multicast services of interest; a time when the multicast services of interest become active; if the session start time of the multicast services of interest is earlier than a first time, the start time is the first time, and the first time is the time when the terminal is interested in the multicast services of interest.

4. The method of claim 3, wherein, The multicast services of interest comprise at least two multicast services; the time when the terminal is interested in the multicast services of interest is a time when the terminal is interested in a third multicast service, the third multicast service being a multicast service that the terminal is most interested in among the at least two multicast services.

5. The method of claim 3, wherein, The multicast services of interest comprise at least two multicast services; the session start time of the multicast services of interest is a session start time of a multicast service whose session starts earliest among the at least two multicast services.

6. The method of claim 3, wherein, The multicast services of interest comprise at least two multicast services; The time when the network-side device starts to send the data of the multicast service of interest is the starting time when the network-side device sends the data of a fourth multicast service, the fourth multicast service being a multicast service that is sent earliest by the network-side device among the at least two multicast services; The time when the terminal starts to receive the data of the multicast service of interest is the starting time when the terminal receives the data of a fifth multicast service, the fifth multicast service being a multicast service that is received earliest by the terminal among the at least two multicast services.

7. The method of claim 3, wherein, The multicast service of interest includes at least two multicast services; The time when the multicast service of interest of the terminal becomes active is the time when a multicast service that becomes active earliest among the at least two multicast services becomes active.

8. The method of claim 1, wherein, The ending time of the first time period includes at least one of the following: The time when the terminal is no longer interested in the multicast service of interest; The ending time of the multicast service of interest; The time when the multicast service of interest becomes inactive.

9. The method of claim 8, wherein, The multicast service of interest includes at least two multicast services; The time when the terminal is no longer interested in the multicast service of interest is the time when the terminal is no longer interested in a sixth multicast service, the sixth multicast service being a multicast service that is no longer interested in latest by the terminal among the at least two multicast services.

10. The method of claim 8, wherein, The multicast service of interest includes at least two multicast services; The ending time of the multicast service of interest is the ending time of a multicast service that ends latest among the at least two multicast services.

11. The method of claim 8, wherein, The multicast service of interest includes at least two multicast services; The time when the multicast service of interest becomes inactive is the time when a multicast service that becomes inactive latest among the at least two multicast services becomes inactive.

12. The method of claim 1, wherein, The RRC state change principle includes: if the multicast service of interest includes at least one first multicast service, the RRC state of the terminal is an RRC connected state; In the case that the communication device is the terminal, the control of the RRC state of the terminal includes at least one of the following: In the case that the terminal is in an RRC connected state, a triggering condition of a first event is disabled, the first event being an event of changing the RRC state of the terminal to an RRC non-connected state; In the case that the terminal is in an RRC connected state, the first event is ignored; In the case that the terminal is in an RRC connected state, after the first event occurs, an operation of changing the RRC state of the terminal to an RRC non-connected state is not performed; In the case that the terminal is in an RRC non-connected state, a triggering condition of a second event is disabled, the second event being an event of changing the RRC state of the terminal to an RRC idle state; In the case that the terminal is in an RRC non-connected state, the second event is ignored; In the case that the terminal is in an RRC non-connected state, after the second event occurs, an operation of changing the RRC state of the terminal to an RRC idle state is not performed; In a case where the terminal is in the RRC inactive state, controlling the terminal to change from the RRC inactive state to the RRC connected state.

13. The method of claim 1, wherein, The RRC state change principle includes: if all the multicast services of interest are multicast services received in the RRC inactive state, the RRC state of the terminal is the RRC inactive state or the RRC connected state; In a case where the communication device is the terminal, the controlling of the RRC state of the terminal includes at least one of: In a case where the terminal is in the RRC connected state, disabling a triggering condition of a third event, the third event being an event of changing the RRC state of the terminal to the RRC idle state; In a case where the terminal is in the RRC connected state, ignoring the third event; In a case where the terminal is in the RRC connected state, after the third event occurs, not performing an operation of changing the RRC state of the terminal to the RRC idle state; In a case where the terminal is in the RRC connected state, controlling the terminal to remain in the RRC connected state or change to the RRC inactive state; In a case where the terminal is in the RRC inactive state, disabling a triggering condition of a fourth event, the fourth event being an event of changing the RRC state of the terminal to the RRC idle state; In a case where the terminal is in the RRC inactive state, ignoring the fourth event; In a case where the terminal is in the RRC inactive state, after the fourth event occurs, not performing an operation of changing the RRC state of the terminal to the RRC idle state; In a case where the terminal is in the RRC inactive state, controlling the terminal to remain in the RRC inactive state or change to the RRC connected state.

14. The method of claim 1, wherein, The RRC state change principle includes: if an event of changing the RRC state of the terminal occurs, and at least one second multicast service is included in the multicast services of interest, the RRC state of the terminal is the RRC state corresponding to the first object; In a case where the communication device is the terminal, the controlling of the RRC state of the terminal includes at least one of: In a case where the terminal is in the RRC connected state, if the priority of the at least one second multicast service is higher, not performing an operation of changing the RRC state of the terminal to the RRC state corresponding to the event; In a case where the terminal is in the RRC connected state, and the at least one second multicast service includes a second multicast service received only in the RRC connected state, if the priority of the second multicast service received only in the RRC connected state is higher, controlling the terminal to remain in the RRC connected state; In a case where the terminal is in the RRC connected state, and the at least one second multicast service is all multicast services received in the RRC inactive state, if the priority of the at least one second multicast service is higher, controlling the terminal to remain in the RRC connected state or change to the RRC inactive state; In a case where the terminal is in the RRC connected state, if the priority of the event of changing the RRC state of the terminal is higher, controlling the RRC state of the terminal to change to the RRC state corresponding to the event; In a case where the terminal is in the RRC inactive state, if the priority of the at least one second multicast service is higher, an operation of changing the RRC state of the terminal to the RRC idle state is not performed; In a case where the terminal is in the RRC inactive state and the at least one second multicast service includes a second multicast service that is received only in the RRC connected state, if the priority of the second multicast service that is received only in the RRC connected state is higher, the terminal is controlled to change from the RRC inactive state to the RRC connected state; In a case where the terminal is in the RRC inactive state and the at least one second multicast service is all multicast services that are received in the RRC inactive state, if the priority of the at least one second multicast service is higher, the terminal is controlled to remain in the RRC inactive state or change to the RRC connected state; In a case where the terminal is in the RRC inactive state, if the priority of an event of changing the RRC state of the terminal is higher, the RRC state of the terminal is controlled to change to an RRC state corresponding to the event.

15. The method of claim 1, wherein, In a case where the communication device is the terminal, the method further includes: The terminal acquires the first information and / or the RRC state change principle.

16. The method of claim 15, wherein, The terminal acquires the first information includes at least one of: The terminal acquires service information of the multicast service of interest, and the first information is included in the service information; In a process in which the terminal reports the multicast service of interest to a network side device, the terminal receives the first information sent by the network side device.

17. A wireless resource control status control device, characterized in that, The apparatus is applied to a communication device, and the apparatus includes a control module; The control module is configured to control the RRC state of a terminal according to first information and an RRC state change principle in a first time period. The first time period is a time period associated with a multicast service of interest of the terminal, and the first information is used to determine an RRC state in which the terminal receives the multicast service of interest. The RRC state change principle includes at least one of: If the multicast service of interest includes at least one first multicast service, the RRC state of the terminal is the RRC connected state, and the first multicast service is a multicast service that is received only in the RRC connected state; If the multicast service of interest is all multicast services that are received in the RRC inactive state, the RRC state of the terminal is the RRC inactive state or the RRC connected state; If an event of changing the RRC state of the terminal occurs and the multicast service of interest includes at least one second multicast service, the RRC state of the terminal is an RRC state corresponding to a first object, the first object is an object with a higher priority between the event and the at least one second multicast service, and the second multicast service is a multicast service that is not supported to be received in the RRC state corresponding to the event; If an event of changing the RRC state of the terminal occurs and the multicast service of interest includes at least one second multicast service, the RRC state of the terminal is determined according to control information sent by a network side device.

18. The apparatus of claim 17, wherein, The first information comprises at least one of: receiving the multicast service of interest only in the RRC connected state; receiving the multicast service of interest in the RRC inactive state.

19. The apparatus of claim 17, wherein, The starting moment of the first time period comprises at least one of: a moment when the terminal is interested in the multicast service of interest; a session starting moment of the multicast service of interest; a moment when the network side device starts to send data of the multicast service of interest, or a moment when the terminal starts to receive data of the multicast service of interest; a moment when the multicast service of interest becomes active; if the session starting moment of the multicast service of interest is earlier than a first moment, the starting moment is the first moment, and the first moment is a moment when the terminal is interested in the multicast service of interest.

20. The apparatus of claim 19, wherein, The multicast service of interest comprises at least two multicast services; the moment when the terminal is interested in the multicast service of interest is a moment when the terminal is interested in a third multicast service, and the third multicast service is a multicast service that the terminal is most interested in among the at least two multicast services.

21. The apparatus of claim 19, wherein, The multicast service of interest comprises at least two multicast services; the session starting moment of the multicast service of interest is a session starting moment of a multicast service whose session starts earliest among the at least two multicast services.

22. The apparatus of claim 19, wherein, The multicast service of interest comprises at least two multicast services; the moment when the network side device starts to send data of the multicast service of interest is a starting moment of sending data of a fourth multicast service, and the fourth multicast service is a multicast service that the network side device sends earliest among the at least two multicast services; the moment when the terminal starts to receive data of the multicast service of interest is a starting moment of receiving data of a fifth multicast service, and the fifth multicast service is a multicast service that the terminal receives earliest among the at least two multicast services.

23. The apparatus of claim 19, wherein, The multicast service of interest comprises at least two multicast services; the moment when the multicast service of interest that the terminal is interested in becomes active is a moment when a multicast service that becomes active earliest among the at least two multicast services becomes active.

24. The apparatus of claim 17, wherein, The ending moment of the first time period comprises at least one of: a moment when the terminal is no longer interested in the multicast service of interest; an ending moment of the multicast service of interest; a moment when the multicast service of interest becomes inactive.

25. The apparatus of claim 24, wherein, The multicast service of interest comprises at least two multicast services; the moment when the terminal is no longer interested in the multicast service of interest is a moment when the terminal is no longer interested in a sixth multicast service, and the sixth multicast service is a multicast service that the terminal is no longer interested in latest among the at least two multicast services.

26. The apparatus of claim 24, wherein, The multicast service of interest comprises at least two multicast services; the ending moment of the multicast service of interest is an ending moment of a multicast service that ends latest among the at least two multicast services.

27. The apparatus of claim 24, wherein, The multicast service of interest comprises at least two multicast services; The moment when the multicast service of interest becomes inactive is the moment when the multicast service of the at least two multicast services that becomes inactive is the latest.

28. The apparatus of claim 18, wherein, The RRC state change principle includes: if the multicast service of interest includes at least one first multicast service, the RRC state of the terminal is the RRC connected state. In the case that the terminal is in the RRC connected state, the triggering condition of a first event is disabled, the first event being an event of changing the RRC state of the terminal to the non-RRC connected state. In the case that the terminal is in the RRC connected state, the first event is ignored. In the case that the terminal is in the RRC connected state, after the first event occurs, an operation of changing the RRC state of the terminal to the non-RRC connected state is not performed. In the case that the terminal is in the RRC inactive state, the triggering condition of a second event is disabled, the second event being an event of changing the RRC state of the terminal to the RRC idle state. In the case that the terminal is in the RRC inactive state, the second event is ignored. In the case that the terminal is in the RRC inactive state, after the second event occurs, an operation of changing the RRC state of the terminal to the RRC idle state is not performed. In the case that the terminal is in the RRC inactive state, the terminal is controlled to change from the RRC inactive state to the RRC connected state. The RRC state change principle includes: if all the multicast service of interest is a multicast service received in the RRC inactive state, the RRC state of the terminal is the RRC inactive state or the RRC connected state.

29. The apparatus of claim 18, wherein, In the case that the terminal is in the RRC connected state, the triggering condition of a third event is disabled, the third event being an event of changing the RRC state of the terminal to the RRC idle state. In the case that the terminal is in the RRC connected state, the third event is ignored. In the case that the terminal is in the RRC connected state, after the third event occurs, an operation of changing the RRC state of the terminal to the RRC idle state is not performed. In the case that the terminal is in the RRC connected state, the terminal is controlled to remain in the RRC connected state or change to the RRC inactive state. In the case that the terminal is in the RRC inactive state, the triggering condition of a fourth event is disabled, the fourth event being an event of changing the RRC state of the terminal to the RRC idle state. In the case that the terminal is in the RRC inactive state, the fourth event is ignored. In the case that the terminal is in the RRC inactive state, after the fourth event occurs, an operation of changing the RRC state of the terminal to the RRC idle state is not performed. In the case that the terminal is in the RRC inactive state, the terminal is controlled to remain in the RRC inactive state or change to the RRC connected state. ​ ​ 30. The apparatus of claim 18, wherein, The RRC state change principle includes: if an event of changing the RRC state of the terminal occurs, and at least one second multicast service is included in the multicast service of interest, the RRC state of the terminal is the RRC state corresponding to the first object; In the case where the communication device is the terminal, the control of the RRC state of the terminal includes at least one of the following: In the case where the terminal is in the RRC connected state, if the priority of the at least one second multicast service is higher, the operation of changing the RRC state of the terminal to the RRC state corresponding to the event is not performed; In the case where the terminal is in the RRC connected state, and the at least one second multicast service includes a second multicast service received only in the RRC connected state, if the priority of the second multicast service received only in the RRC connected state is higher, the terminal is controlled to remain in the RRC connected state; In the case where the terminal is in the RRC connected state, and the at least one second multicast service is all multicast service received in the RRC inactive state, if the priority of the at least one second multicast service is higher, the terminal is controlled to remain in the RRC connected state or change to the RRC inactive state; In the case where the terminal is in the RRC connected state, if the priority of the event of changing the RRC state of the terminal is higher, the RRC state of the terminal is controlled to change to the RRC state corresponding to the event; In the case where the terminal is in the RRC inactive state, if the priority of the at least one second multicast service is higher, the operation of changing the RRC state of the terminal to the RRC idle state is not performed; In the case where the terminal is in the RRC inactive state, and the at least one second multicast service includes a second multicast service received only in the RRC connected state, if the priority of the second multicast service received only in the RRC connected state is higher, the terminal is controlled to change from the RRC inactive state to the RRC connected state; In the case where the terminal is in the RRC inactive state, and the at least one second multicast service is all multicast service received in the RRC inactive state, if the priority of the at least one second multicast service is higher, the terminal is controlled to remain in the RRC inactive state or change to the RRC connected state; In the case where the terminal is in the RRC inactive state, if the priority of the event of changing the RRC state of the terminal is higher, the RRC state of the terminal is controlled to change to the RRC state corresponding to the event.

31. The apparatus of claim 17, wherein, In the case where the communication device is the terminal, the apparatus further includes an acquisition module; The acquisition module is configured to acquire the first information and / or the RRC state change principle.

32. The apparatus of claim 31, wherein, The acquisition module includes an acquisition unit and / or a receiving unit; The acquisition unit is configured to acquire service information of the multicast service of interest, and the service information includes the first information; The receiving unit is configured to receive the first information sent by a network side device in a process in which the terminal reports the multicast service of interest to the network side device.

33. A communications device, characterized by A computer program product including a computer readable storage medium having stored thereon a program or instructions which can be executed by a processor to implement the steps of the radio resource control state control method according to any one of claims 1 to 16.

34. A readable storage medium characterized by, A program or instructions stored on a computer readable storage medium which, when executed by a processor, implement the steps of the radio resource control state control method according to any one of claims 1 to 16.

Images