Mps management method and related apparatus

Abstract

Embodiments of the present application disclose a method and device for managing MPS. The method comprises: receiving, by a terminal device, an RRC release message including an MPS priority indication and a redirected frequency; attempting to camp on a suitable cell on the redirected frequency or a specified RAT; and sending, by the terminal device, an RRC setup request message or an RRC resume request message including a first cause value to the first cell when successfully camping on a first cell and detecting that a first condition is met, wherein the first condition is related to at least one of the MPS priority indication or the redirected frequency. Thus, the effectiveness of the MPS priority is managed, and the communication impact on other terminal devices accessing the network caused by the terminal device incorrectly accessing the network according to the MPS priority is avoided.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of wireless communications, and in particular to an MPS management method and related devices. Background Art

[0002] In the field of communications technology, network equipment often considers redirecting terminal devices (such as user equipment (UE)) to other frequencies to achieve load balancing. Network equipment can redirect UEs to other frequencies within the same RAT (Radio Access Technology) or to other RATs. For example, if a UE is operating on an NR (New Radio) network, the network can instruct the UE to redirect to an LTE (Long Term Evolution) network. With the rapid development of wireless network communication technologies, mobile users' expectations for mobile network service quality are constantly increasing. Priority services are becoming an effective means for more and more operators to improve mobile user satisfaction. Multimedia Priority Service (MPS) allows specific subscribers or other authorized persons to have priority access to network resources, especially in times of network congestion or emergencies, enabling timely assistance, dispatch management, and other tasks. When a mobile user requests priority services, network equipment identifies the priority services and provides them with priority treatment over standard services. In the case of network congestion or insufficient resources, priority services sent by mobile users with high priority service levels can be processed with high priority by network equipment, thereby meeting the needs of high priority mobile users.

[0003] In order to enable terminal devices that have not signed up for MPS or have not yet implemented MPS to enjoy MPS priority processing in high-priority services, existing technologies can support network devices to instruct terminal devices to use MPS priority for subsequent access during redirection.

[0004] However, the terminal device may not necessarily be redirected to the specified frequency or RAT as required by the network device, and the redirection may even fail. In the above case, it is unclear whether the terminal device can still use the priority access of MPS. Summary of the Invention

[0005] The embodiments of the present application provide an MPS management method and related apparatus for managing the validity of an MPS priority indication during a redirection process.

[0006] In a first aspect, an embodiment of the present application provides an MPS management method, which can be executed by a terminal device in a wireless network or by a component of the terminal device (such as a processor, chip, or chip system). The method includes:

[0007] After the terminal device receives the radio resource control RRC release message sent by the network device, it releases or suspends the connection and attempts to reside on the cell, wherein the RRC release message includes the multimedia priority service MPS priority indication and the redirected frequency. Subsequently, the terminal device sends an RRC establishment request message or an RRC recovery request message to the first cell where it successfully resides, wherein the RRC establishment request message is used to request to establish a connection to the first cell, and the RRC establishment request message includes an establishment reason. The RRC recovery request message is used to request to restore the connection to the first cell, and the RRC recovery request message includes a recovery reason. When the first condition is met, the establishment reason or the recovery reason is a first reason value, otherwise, the establishment reason or the recovery reason is a second reason value, and the first condition is related to at least one of the MPS priority indication or the redirected frequency.

[0008] During the redirection process, the terminal device will try to reside on the redirected frequency or a suitable cell on the specified RAT according to the redirection information in the RRC release message. If the residency on the redirected frequency or specified RAT is successful, access will be performed according to the MPS priority indication. However, in the actual communication process, the terminal device may not be redirected to the specified frequency or specified RAT as expected by the network device, and redirection may even fail. If the terminal device fails to reside on the specified frequency or specified RAT, it will continue to try to search for and reside on cells on other frequencies or RATs. If the residency on a cell on another frequency or RAT is successful, an RRC connection request or RRC connection recovery is initiated. At this time, it is unclear whether the MPS priority is still used to access the frequency or RAT. It is understandable that the network device redirects the terminal device to the specified frequency or specified RAT because the load of the specified frequency or specified RAT or the network conditions support the processing of the MPS priority of the terminal device. If a terminal device chooses to access a cell on another frequency or RAT, it is unclear whether the load or network conditions of the cell on that frequency or RAT can support the terminal device's MPS priority service. If the frequency or RAT cannot support the use of MPS priority, and the terminal device continues to use MPS priority access, it may affect other terminal devices accessing the network.

[0009] Therefore, by using the method provided in the application, after receiving the RRC release message sent by the network device, the terminal device attempts to camp on a suitable cell on the redirected frequency point or the cell on the specified RAT according to the redirection information in the RRC release message. If the terminal device cannot find a suitable cell on the redirected frequency point, the terminal device attempts to camp on a cell on the specified RAT (i.e., the redirected RAT), and if the terminal device cannot select a suitable cell on the specified RAT, the terminal device performs a cell selection process to select a suitable cell according to the actual network situation or the information stored by the terminal device. If the terminal device successfully camps on the first cell, when the terminal device has a service transmission requirement, for example, the terminal device can send an RRC setup request message or an RRC resume request message to the network device to which the first cell belongs. At this time, the terminal device can determine the setup cause or the resume cause carried in the setup request message or the resume request message according to whether the first condition is met, wherein the first condition is related to at least one of the MPS priority indication or the redirected frequency point. The terminal device can only set the setup cause or the resume cause to the first cause value in the case where the first condition is met. By setting the first cause value, the terminal device accesses according to the priority of the MPS in the connection setup or resume process after redirection, thereby guaranteeing the priority of the service and the service continuity. Therefore, the effectiveness of the MPS priority can be further managed, and the communication impact on other terminal devices accessing the network caused by the terminal device incorrectly accessing according to the MPS priority can be avoided.

[0010] In a possible implementation manner, in the case where the terminal device detects that the first condition is met, the terminal device sends an RRC setup request message or an RRC resume request message to the first cell, and the first condition is used to control the terminal device to use the MPS priority, and includes at least one of the following:

[0011] Condition 1: the first cell belongs to the redirected frequency point; or,

[0012] Condition 2: the first cell and the redirected frequency point correspond to the same RAT; or,

[0013] Condition 3: the RRC setup request message or the RRC resume request message is the first RRC setup request message or RRC resume request message sent after receiving the RRC release message; or,

[0014] Condition 4: a timer is not expired, and the timer is used to indicate the validity duration of the MPS priority indication; or,

[0015] Condition 5: the first cell belongs to a first area, and the first area is a home area or a service area of the terminal device.

[0016] In the possible implementation, by explicitly indicating the effective use range, effective use scenario, and effective time length of the MPS priority, the communication of other terminal devices accessing the network is avoided from being affected by the terminal device accessing the network according to the MPS priority by mistake. The first condition is mainly considered as follows:

[0017] I. The first and second conditions are mainly considered as follows: different factors such as the load or network situation of different frequency points or RATs may be different. The network device redirects the terminal device to a specified frequency point or a specified RAT, which may be due to the load or network situation of the frequency point or the RAT supporting the terminal device to perform the MPS priority service. If the terminal device selects to access other frequency points or RATs, and the cell on the frequency point or the RAT does not support the terminal device to perform the MPS priority service, the terminal device may affect the network performance of the accessed cell, and further affect the communication quality of the terminal device and other terminal devices.

[0018] II. The third condition is that the terminal device initiates the RRC connection establishment or connection recovery on the specified frequency point or RAT for the first time after receiving the RRC release message carrying the MPS priority indication, and the terminal device can access using the MPS priority. By setting the above conditions, the terminal device can adjust whether to access using the MPS priority service according to the network policy. If the network device rejects the connection establishment or recovery of the MPS priority requested by the terminal device, the terminal device should not use the MPS priority access in the subsequent connection establishment or recovery process, thereby improving the probability of successful access of the terminal device.

[0019] III. The fourth condition is mainly considered as follows: in the process of redirection of the terminal device, if the terminal device fails to camp on the cell on the specified frequency point or the specified RAT, and successfully camps on a cell after a long time of cell search, whether the terminal device still accesses the cell according to the MPS priority needs to be limited and explained. By explicitly indicating the effective time length of the MPS priority indication, the timeliness and effectiveness of the MPS priority service are guaranteed.

[0020] IV. The fifth condition is mainly considered as follows: the access identification or access level related to the MPS priority issued by the non-access layer is only valid in the home country, and therefore the MPS priority indication allocated by the network can also be limited to be valid in the home country or the home public land mobile network (HPLMN). In addition, if the terminal device receives the RRC release message in the current service PLMN or service country, and is given the MPS priority, it does not mean that the terminal device can use the MPS priority in other PLMNs or other countries, and in this case, the limitation and explanation are needed.

[0021] In a possible implementation, the first cause value is an MPS priority access cause value. When the cell that the terminal device attempts to camp on is an NR cell, the first cause value sent by the terminal device is the MPS priority access.

[0022] In a possible implementation, the first cause value is a high priority access cause value. When the cell that the terminal device attempts to camp on is an LTE or evolved universal terrestrial radio access (E-UTRA) cell, the first cause value sent by the terminal device is the high priority access.

[0023] In a possible implementation, the second cause value is a cause value received from a non-access stratum.

[0024] In the three possible implementations described above, after receiving the RRC release message containing the redirection information, the terminal device initiates an RRC connection establishment procedure or a connection resume procedure, and can carry a connection establishment cause or a connection resume cause in the connection establishment request or the connection resume request message to inform the network device of the cause of the connection establishment or the connection resume. The cause values of the MPS priority access and the high priority access are respectively associated with the MPS priority service in different RATs. When the first condition is met, the terminal device sets the first cause value to indicate that the cause of the connection establishment or the connection resume is related to the MPS priority service, so that the network can process the service according to the MPS priority, thereby increasing the possibility of successful connection establishment or connection resume, and reducing the establishment delay of the service connection or the transmission delay of the service data. If the first condition is not met, the terminal device accesses according to the cause value indicated by the non-access stratum, and the network device does not process the connection establishment or the connection resume as the MPS priority service, thereby avoiding the impact on other terminal devices caused by the terminal device incorrectly accessing according to the MPS priority.

[0025] In a possible implementation, when the first condition is not met, the MPS priority indication is invalid.

[0026] In this possible implementation, if the first condition is not met, the MPS priority indication is considered invalid, and the terminal device accesses according to the cause value indicated by the non-access stratum, thereby avoiding the impact on other terminal devices caused by the terminal device incorrectly accessing according to the MPS priority. In the subsequent connection establishment or connection resume procedure, the terminal device also does not access according to the MPS priority because the MPS priority indication is invalid.

[0027] In a possible implementation, before sending the RRC establishment request message or the RRC resume request message, the terminal device receives first indication information, and the first indication information is used to indicate that the first access identity or the first access class allows access.

[0028] When the first condition is met, it is considered that access is allowed.

[0029] In the possible implementation, the terminal device needs to perform unified access control before sending the RRC setup request message or the RRC resume request message. The terminal device receives first indication information sent by the network device, and the first indication information can be used to indicate whether the network device allows access attempts corresponding to the first access identity or the first access class. In a case where the first indication information indicates that the access attempts corresponding to the first access identity or the first access class are allowed, the terminal device determines whether a first condition is met. If the first condition is met, it is considered or regarded that the access attempt is allowed, and the RRC connection setup request or the connection resume request is sent.

[0030] By the implementation, the terminal device determines whether the access attempt is allowed by using the MPS priority indication only in a case where the first condition is met, thereby avoiding access attempt failure caused by the terminal mistakenly considering that the access attempt is allowed.

[0031] In a possible implementation, the terminal device determines the first condition according to second indication information sent by the network device.

[0032] In a possible implementation, the RRC release message further includes the second indication information.

[0033] After the terminal device receives the radio resource control (RRC) release message, the terminal device determines the first condition according to second indication information sent by the network device.

[0034] In the above two possible implementations, the first condition can be obtained from the network device, thereby more flexibly configuring the validity of the MPS priority indication.

[0035] The second aspect of the embodiments of the present application provides a method for managing MPS, which can be executed by a network device or a component (for example, a processor, a chip or a chip system, etc.) of the network device. The method comprises the following steps.

[0036] The first network device sends a radio resource control (RRC) release message to a terminal device, wherein the RRC release message includes multimedia priority service (MPS) priority indication and a redirected frequency point.

[0037] The second network device receives an RRC setup request message or an RRC resume request message, wherein the RRC setup request message is used to request to establish a connection to a first cell, the RRC setup request message includes a setup cause, the RRC resume request message is used to request to resume a connection to the first cell, and the RRC resume request message includes a resume cause, wherein the setup cause or the resume cause is a first reason value or a second reason value, the first reason value or the second reason value is related to a first condition, and the first condition is related to at least one of the MPS priority indication or the redirected frequency point.

[0038] In this embodiment, the first network device will send an RRC release message to the terminal device based on load balancing considerations, so that the terminal device attempts to reside on the redirected frequency or a suitable cell on the designated RAT according to the redirection information in the RRC release message. If the residency on the designated frequency or designated RAT is successful, access is performed according to the MPS priority indication. If the second network device receives an RRC establishment request message or an RRC recovery request message, the RRC establishment request message or the RRC recovery request message includes a first cause value, and the first cause value is related to the first condition, and the first condition is related to at least one of the MPS priority indication or the redirected frequency, it means that the terminal device accesses the second network device using the MPS priority. Therefore, by clarifying the conditions for the terminal device to use the MPS priority, the validity of the MPS priority is managed, and the communication impact caused by the terminal device erroneously accessing according to the MPS priority on other terminal devices accessing the network is avoided.

[0039] In one possible implementation, the first condition includes at least one of the following:

[0040] The first cell belongs to the redirected frequency; or, the first cell and the redirected frequency correspond to the same RAT; or, the RRC establishment request message or the RRC recovery request message is the first RRC establishment request message or RRC recovery request message sent after receiving the RRC release message; or, the timer has not timed out, and the timer is used to indicate the valid duration of the MPS priority indication; or, the first cell belongs to the first area, and the first area is the home area or service area of ​​the terminal device.

[0041] In this possible implementation, by clarifying the effective use scope, effective use scenarios, and effective duration of the MPS priority, the communication impact on other terminal devices accessing the network caused by the terminal device mistakenly accessing according to the MPS priority is avoided.

[0042] In a possible implementation, the first cause value is an MPS priority access cause value.

[0043] In a possible implementation, the first cause value is a high-priority access cause value.

[0044] In a possible implementation, the second cause value is a cause value received from the non-access stratum.

[0045] In the three possible implementations mentioned above, the cause values ​​of MPS priority access and high priority access are respectively associated with MPS priority services under different RATs. When the first condition is met, the terminal device indicates that the reason for establishing or restoring the connection is related to the MPS priority service by setting the first cause value, so that the network can process the service according to the MPS priority, increase the possibility of successful connection establishment or restoration, and reduce the establishment delay of the service connection or the transmission delay of the service data. If the first condition is not met, the terminal device accesses according to the cause value indicated by the non-access layer, and the network device will not process the connection establishment or connection restoration according to the MPS priority service, thereby avoiding the impact on other terminal devices caused by the terminal erroneously accessing according to the MPS priority.

[0046] Optionally, in a possible implementation of the second aspect, before the network device receives an RRC establishment request message or an RRC recovery request message, indication information is sent to the terminal device, where the indication information is used to indicate that the first access identifier or the first access level allows access.

[0047] In this possible implementation, the terminal device needs to perform unified access control before sending an RRC establishment request message or an RRC recovery request message. The terminal device receives first indication information sent by a network device, where the first indication information is used to indicate whether the network device allows an access attempt corresponding to a first access identifier or a first access level. When the first indication information indicates that the access attempt corresponding to the first access identifier or the first access level is allowed, the terminal device determines whether the first condition is met. If the first condition is met, it is considered or deemed that the access attempt is allowed, and an RRC connection establishment request or a connection recovery request is sent.

[0048] Through this implementation, the terminal device uses the MPS priority indication to determine whether the access attempt is allowed only when the first condition is met, thereby avoiding access attempt failure caused by the terminal mistakenly believing that the access attempt is allowed.

[0049] In one possible implementation, the terminal device determines the first condition based on second indication information sent by the network device.

[0050] In a possible implementation manner, the RRC release message also includes second indication information.

[0051] In the two possible implementations described above, the first condition can be obtained from the network device, thereby more flexibly configuring the validity of the MPS priority indication.

[0052] According to a third aspect, a communications device is provided. The beneficial effects can be found in the description of the first aspect and are not further elaborated here. The communications device has the function of implementing the actions in the method example of the first aspect. The functions can be implemented by hardware or by hardware executing corresponding software implementations. The hardware or software includes one or more modules corresponding to the functions. In one possible design, the communications device includes: a receiving unit configured to receive a radio resource control (RRC) release message, wherein the RRC release message includes a multimedia priority service (MPS) priority indicator and a redirected frequency; and a sending unit configured to send an RRC establishment request message or an RRC recovery request message, wherein the RRC establishment request message is used to request establishment of a connection with a first cell and includes an establishment cause; and the RRC recovery request message is used to request restoration of a connection with the first cell and includes a restoration cause. If a first condition is met, the establishment cause or restoration cause is a first cause value; otherwise, the establishment cause or restoration cause is a second cause value, and the first condition is related to at least one of the MPS priority indicator and the redirected frequency. These units can perform the corresponding functions in the method example of the first aspect. For details, refer to the detailed description of the method example and are not further elaborated here.

[0053] In a fourth aspect, a communication device is provided. The beneficial effects can be found in the description of the second aspect and are not further described here. The communication device has the function of implementing the behavior in the method example of the second aspect. The function can be implemented by hardware, or by hardware executing corresponding software implementation. The hardware or software includes one or more modules corresponding to the above-mentioned functions. In one possible design, the communication device includes: a sending unit, configured to send a radio resource control (RRC) release message to a terminal device, wherein the RRC release message includes a multimedia priority service (MPS) priority indicator and a redirected frequency; and a receiving unit, configured to receive an RRC establishment request message or an RRC recovery request message, wherein the RRC establishment request message is used to request establishment of a connection with a first cell, the RRC establishment request message includes an establishment cause, and the RRC recovery request message is used to request restoration of a connection with the first cell, the RRC recovery request message includes a restoration cause, the establishment cause or the restoration cause being a first cause value or a second cause value, the first cause value or the second cause value being related to a first condition, and the first condition being related to at least one of the MPS priority indicator or the redirected frequency. These units can perform the corresponding functions in the above-mentioned method example of the second aspect. Please refer to the detailed description in the method example for details, which will not be repeated here.

[0054] The fifth aspect of the embodiments of the present application provides a communication device, comprising a processor and an interface circuit, the interface circuit is used for receiving signals from other communication devices and transmitting the signals to the processor or sending signals from the processor to other communication devices, and the processor is used for implementing the method in the first aspect or any possible implementation manner of the first aspect by means of a logic circuit or executing code instructions.

[0055] The sixth aspect of the embodiments of the present application provides a communication device, comprising a processor and an interface circuit, the interface circuit is used for receiving signals from other communication devices and transmitting the signals to the processor or sending signals from the processor to other communication devices, and the processor is used for implementing the method in the second aspect or any possible implementation manner of the second aspect by means of a logic circuit or executing code instructions.

[0056] The seventh aspect of the embodiments of the present application provides a communication system, comprising the communication device in the fifth aspect and / or the communication device in the sixth aspect.

[0057] The eighth aspect of the embodiments of the present application provides a computer program product, when the computer program product is executed by a computer, the method in the first aspect or any possible implementation manner of the first aspect or the method in the second aspect or any possible implementation manner of the second aspect is implemented.

[0058] The ninth aspect of the embodiments of the present application provides a computer readable storage medium, the computer program or instructions are stored in the storage medium, when the computer program or instructions are executed by a communication device, the method in the first aspect or any possible implementation manner of the first aspect or the method in the second aspect or any possible implementation manner of the second aspect is implemented.

[0059] The technical effects brought by the third, fifth, seventh, eighth, ninth aspects or any possible implementation manner thereof can be referred to the technical effects brought by the first aspect or different possible implementation manners of the first aspect, and details are not described herein.

[0060] The technical effects brought by the fourth, sixth, seventh, eighth, ninth aspects or any possible implementation manner thereof can be referred to the technical effects brought by the second aspect or different possible implementation manners of the second aspect, and details are not described herein.

[0061] In the tenth aspect, the present application provides a communication method, including: a network device sends a radio resource control (RRC) release message to a terminal device, wherein the RRC release message includes a multimedia priority service (MPS) priority indication and a redirected frequency, and the terminal device receives the radio resource control (RRC) release message; the terminal device sends an RRC establishment request message or an RRC recovery request message, wherein the RRC establishment request message is used to request to establish a connection to a first cell, the RRC establishment request message includes an establishment cause, and the RRC recovery request message is used to request to restore the connection to the first cell, and the RRC recovery request message includes a recovery cause; wherein, if a first condition is met, the establishment cause or the recovery cause is a first cause value, otherwise, the establishment cause or the recovery cause is a second cause value, and the first condition is related to at least one of the MPS priority indication or the redirected frequency. The network device receives the RRC establishment request message or the RRC recovery request message.

[0062] In an eleventh aspect, the present application provides a communication system comprising a terminal device for executing the method of the first aspect and a network device for executing the method of the second aspect.

[0063] In a twelfth aspect, the present application provides a chip system comprising a processor for implementing the functions of the terminal device in the methods of the above aspects. In one possible design, the chip system further comprises a memory for storing program instructions and / or data. The chip system may be composed of a chip alone or may include a chip and other discrete components.

[0064] In a thirteenth aspect, the present application provides a chip system comprising a processor for implementing the network device functions described in the aforementioned methods. In one possible design, the chip system further comprises a memory for storing program instructions and / or data. The chip system may be comprised solely of a chip or may include a chip and other discrete components. BRIEF DESCRIPTION OF THE DRAWINGS

[0065] Figure 1 This is a schematic diagram of the architecture of a communication system used in an embodiment of the present application;

[0066] Figure 2a A schematic diagram of a flow chart of an RRC connection establishment process provided in an embodiment of the present application;

[0067] Figure 2b A schematic diagram of another RRC connection establishment process provided in an embodiment of the present application;

[0068] Figure 3a A schematic diagram of a flow chart of an RRC connection recovery process provided in an embodiment of the present application;

[0069] Figure 3b A flowchart of another RRC connection recovery procedure provided for an embodiment of the present application is shown in FIG. 14B.

[0070] Figure 4 A flowchart of a unified access control procedure provided for an embodiment of the present application is shown in FIG. 15B.

[0071] Figure 5 A flowchart of a MPS management method provided for an embodiment of the present application is shown in FIG. 16B.

[0072] Figure 6 A flowchart of another MPS management method provided for an embodiment of the present application is shown in FIG. 17B.

[0073] Figure 7 A structure diagram of a communication apparatus provided for an embodiment of the present application is shown in FIG. 18B.

[0074] Figure 8 A structure diagram of another communication apparatus provided for an embodiment of the present application is shown in FIG. 19B.

[0075] Figure 9 A structure diagram of another communication apparatus provided for an embodiment of the present application is shown in FIG. 20B.

[0076] Figure 10 A structure diagram of another communication apparatus provided for an embodiment of the present application is shown in FIG. 21B.

[0077] Figure 11 A structure diagram of another communication apparatus provided for an embodiment of the present application is shown in FIG. 22B. DETAILED DESCRIPTION

[0078] The embodiments of the present application will be described below in conjunction with the accompanying drawings. It is obvious that the described embodiments are only a part of the embodiments of the present application, but not all the embodiments of the present application. It is obvious for those skilled in the art that, with the development of technology and the appearance of new scenes, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

[0079] The terms "first", "second", etc. in the specification and claims of this application and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate so that the embodiments described herein can be implemented in a sequence other than that illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or modules is not necessarily limited to those steps or modules clearly listed, but may include other steps or modules that are not clearly listed or that are inherent to these processes, methods, products or devices. The naming or numbering of steps in this application does not mean that the steps in the method flow must be executed in the time / logical sequence indicated by the naming or numbering. The process steps that have been named or numbered can be changed in the execution order according to the technical purpose to be achieved, as long as the same or similar technical effects can be achieved. The division of units in this application is a logical division. In actual application, there may be other division methods. For example, multiple units can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between each other shown or discussed can be through some interfaces, and the indirect coupling or communication connection between units can be electrical or other similar forms, which are not limited in this application. Moreover, the units or sub-units described as separate components may or may not be physically separated, may or may not be physical units, or may be distributed into multiple circuit units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this application.

[0080] It will be understood that the “embodiment” mentioned throughout the specification means that the specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, the various embodiments in the entire specification do not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It will be understood that in the various embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application. The same or similar parts between the various embodiments in the present application can refer to each other.

[0081] In the various embodiments of this application, and the various implementation methods / implementation methods / implementation methods in each embodiment, unless otherwise specified or logically conflicting, the terms and / or descriptions between different embodiments and the various implementation methods / implementation methods / implementation methods in each embodiment are consistent and can be referenced to each other. The technical features in different embodiments and the various implementation methods / implementation methods / implementation methods in each embodiment can be combined to form new embodiments, implementation methods, implementation methods, or implementation methods according to their inherent logical relationships. The above-described implementation methods of this application do not constitute a limitation on the scope of protection of this application.

[0082] It can be understood that in this application, "when", "if" and "if" all mean that the device will perform corresponding processing under certain objective circumstances, and do not limit the time. It does not require that the device must perform a judgment action when it is implemented, nor does it mean that there are other limitations.

[0083] In this application, unless otherwise specified, “at least one” is intended to mean “one or more” and “more than one” is intended to mean “two or more”.

[0084] Additionally, the terms "system" and "network" are often used interchangeably. The term "and / or" is simply a description of an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can mean: A exists alone, A and B exist simultaneously, or B exists alone. A can be singular or plural, and B can be singular or plural. The character " / " generally indicates an "or" relationship between the related objects.

[0085] The word “exemplary” is used exclusively herein to mean “serving as an example, example, or illustration.” Any embodiment described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments.

[0086] The present application can be applied to the protocol framework of various wireless communication systems, and the wireless communication systems may include but are not limited to LTE systems, NR systems, future evolved communication systems, etc., and future evolved communication systems such as future networks or sixth generation communication systems.

[0087] The following describes the application scenarios of the MPS management method provided in the embodiments of the present application.

[0088] See also Figure 1 , Figure 1 It is a schematic diagram of the architecture of the communication system 1000 used in the embodiment of the present application.

[0089] like Figure 1As shown, the communication system includes a wireless access network 100 and a core network 200. Optionally, the communication system 1000 may also include the Internet 300. The wireless access network 100 may include at least one network device (such as Figure 1 110a and 110b), and may further include at least one terminal device (such as Figure 1 120a-120j in FIG. 120b). Terminal devices are wirelessly connected to network devices, and network devices are wirelessly or wiredly connected to the core network. The core network device and the network device can be independent, distinct physical devices, or the core network device's functions and the network device's logical functions can be integrated into the same physical device. Alternatively, a single physical device can integrate some of the core network device's functions and some of the network device's functions. Terminal devices and network devices can be interconnected via wired or wireless connections. Figure 1 This is just a schematic diagram. The communication system may also include other network devices, such as wireless relay devices and wireless backhaul devices. Figure 1 Not drawn in the middle.

[0090] A network device is an access device that allows a terminal device to wirelessly access a communication system. A network device can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation NodeB (gNB) in a fifth-generation (5G) mobile communication system, a next-generation base station in a sixth-generation (6G) mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system. It can also be a module or unit that performs some of the functions of a base station, such as a centralized unit (CU) or a distributed unit (DU). The CU here completes the functions of the radio resource control protocol and packet data convergence protocol (PDCP) of the base station, and can also complete the function of the service data adaptation protocol (SDAP); the DU completes the functions of the radio link control layer and medium access control (MAC) layer of the base station, and can also complete the functions of part or all of the physical layer. For detailed descriptions of the above-mentioned protocol layers, please refer to the relevant technical specifications of the 3rd Generation Partnership Project (3GPP). The network device can be a macro base station (such as Figure 1 110a), or a micro base station or an indoor station (such as Figure 1 110b), may also be a relay node or a donor node, etc. The embodiments of the present application do not limit the specific technology and specific device form adopted by the network device.

[0091] A terminal device is a device with wireless transceiving function, which can send signals to a network device or receive signals from a network device. A terminal device can also be referred to as a user equipment (UE), a mobile station, a mobile terminal, etc. A terminal device can be widely applied to various scenarios, such as device-to-device (D2D), vehicle to everything (V2X) communication, machine-type communication (MTC), internet of things (IOT), virtual reality, augmented reality, industrial control, automatic driving, remote medical treatment, smart power grid, smart furniture, smart office, smart wear, smart transportation, smart city, etc. A terminal device can be a mobile phone, a tablet computer, a computer with wireless transceiving function, a wearable device, a vehicle, an airplane, a ship, a robot, a mechanical arm, a smart home device, etc. Embodiments of the present application do not limit the specific technology and specific device form of a terminal device.

[0092] A network device and a terminal device can be fixed in position or movable. A network device and a terminal device can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can be deployed on water surface; can also be deployed on an airplane, a balloon and a man-made satellite. Embodiments of the present application do not limit the application scenarios of a network device and a terminal device.

[0093] The roles of a network device and a terminal device can be relative, for example, Figure 1 A helicopter or a drone 120i in FIG. 1 can be configured as a mobile network device. For a terminal device 120j that accesses a wireless access network 100 through 120i, 120i is a network device; but for a network device 110a, 120i is a terminal device, i.e., 110a and 120i communicate with each other through a wireless air interface protocol. Of course, 110a and 120i can also communicate with each other through an interface protocol between network devices, in which case, 120i is also a network device relative to 110a. Therefore, a network device and a terminal device can be collectively referred to as a communication apparatus, Figure 1 110a and 110b in FIG. 1 can be referred to as a communication apparatus with network device function, Figure 2a 120a-120j in FIG. 1 can be referred to as a communication apparatus with terminal function.

[0094] The network device and the terminal device, the network device and the network device, and the terminal device and the terminal device can communicate through an authorized frequency spectrum, or through an unlicensed frequency spectrum, or through both the authorized frequency spectrum and the unlicensed frequency spectrum; can communicate through a frequency spectrum below 6 gigahertz (GHz), or through a frequency spectrum above 6 GHz, or through both the frequency spectrum below 6 GHz and the frequency spectrum above 6 GHz. Embodiments of the present application do not limit the frequency spectrum used for wireless communication.

[0095] In embodiments of the present application, the functions of the network device can also be performed by a module (such as a chip) in the network device, or by a control subsystem containing network device functions. The control subsystem containing network device functions herein can be a control center in the above-mentioned application scenarios such as smart grid, industrial control, intelligent transportation, and smart city. The functions of the terminal device can also be performed by a module (such as a chip or modem) in the terminal device, or by a device containing terminal functions.

[0096] The above introduces the scenario to which the MPS management method provided by the embodiments of the present application is applied. The specific implementation process of the MPS management method provided by the embodiments of the present application will be described in detail below.

[0097] First, the professional terms in the embodiments of the present application are introduced.

[0098] (1) Redirection

[0099] The redirection process is that the network device instructs the terminal device to attempt to camp on a cell on a specified frequency point through redirection information (Redirected Carrier Info). The redirection information can be contained in an RRC (Radio Resource Control) release message, and the redirection information can include a redirected frequency point. The redirection information can also indicate a redirected radio access technology (RAT), for example, the redirection information includes carrier information (Carrier Info) of NR, which indicates that the terminal device attempts to camp on an NR cell. Or, for example, the redirection information includes redirected carrier information (Redirected Carrier Info-EUTRA) of E-UTRA, which indicates that the terminal device attempts to camp on an E-UTRA cell.

[0100] When the RRC release message includes redirection information, the terminal device should attempt to reside in a suitable cell (suitable cell) on the redirected frequency indicated by the redirection information. If the terminal device cannot find a suitable cell to reside in on the redirected frequency, the terminal device can try to reside in a suitable cell on the specified RAT. If the terminal device does not find a suitable cell on the specified RAT, the terminal device can use its stored information to perform a cell selection process to find a suitable cell to reside in. At this time, the terminal device may select and reside in a cell on a non-redirected frequency or non-redirected RAT.

[0101] (2)RRC connection establishment process

[0102] The RRC connection establishment process is used to establish an RRC connection. When starting the RRC connection establishment process, the terminal device should perform unified access control (UAC) to determine whether the access attempt is allowed.

[0103] If this access attempt is allowed, Figure 2b As shown, it is a flow chart of an RRC connection establishment process provided in an embodiment of the present application. The RRC connection establishment process is as follows:

[0104] In step 201a, the terminal device sends an RRC Setup Request message to the network device, wherein the request message includes an establishment cause.

[0105] Step 202a: If the network device allows the terminal device to establish a connection, an RRC connection establishment (RRC Setup) message is sent to the terminal device. The RRC connection establishment message includes the configuration required for the terminal device to establish a connection.

[0106] Step 203a: After completing the configuration, the terminal device sends an RRC Setup Complete message to the network device, and the RRC connection establishment process ends.

[0107] If the network device does not allow the terminal device to establish a connection, such as Figure 3a As shown, it is a flow chart of another RRC connection establishment process provided in an embodiment of the present application. The RRC connection establishment process is as follows:

[0108] Step 201b: The terminal device sends an RRC Setup Request message to the network device.

[0109] Step 202b, the network device replies to the terminal device with an RRC reject message. After receiving the RRC reject message, the terminal device reports the connection establishment failure to the non-access layer, and the RRC connection establishment process ends.

[0110] (3) RRC connection resumption process

[0111] The RRC connection resumption process is used to resume the suspended RRC connection. When starting the RRC connection resumption process, the terminal device should perform unified access control to determine whether the current access attempt is allowed.

[0112] In the case where the current access attempt is allowed, as shown in Figure 3a , a flowchart of the RRC connection resumption process provided by an embodiment of the present application is shown, and the RRC connection resumption process is as follows: Figure 3b

[0113] Step 301a, the terminal device sends an RRC resume request (RRC Resume Request or RRCResume Request1) message to the network device. The request message includes a resume cause.

[0114] Step 302a, if the network device allows the terminal device to resume the connection, the network device sends an RRC connection resumption (RRC Resume) message to the terminal device, and the RRC connection resumption message includes the configuration required by the terminal device to resume the connection.

[0115] Step 303a, after completing the configuration, the terminal device sends an RRC resume complete (RRC Resume Complete) message to the network device, and the RRC connection resumption process ends.

[0116] If the network device does not allow the terminal device to resume the connection, as shown in Figure 3b , another flowchart of the RRC connection resumption process provided by an embodiment of the present application is shown, and the RRC connection resumption process is as follows: Figure 4

[0117] Step 301b, the terminal device sends an RRC resume request (RRC Resume Request or RRCResume Request1) message to the network device. The request message includes a resume cause.

[0118] Step 302b, the network device replies to the terminal device with an RRC reject message.

[0119] After receiving the RRC reject message, the terminal device reports the connection resumption failure to the non-access layer and discards the related configuration, and the RRC connection resumption process ends.​​

[0120] (4) Unified access control

[0121] To prevent excessive access to a network device, which could lead to network overload and congestion, the network device can implement access control for the terminal devices using unified access control technology. The unified access control process is used to perform access barring checks on a particular access attempt. Access attempts can include RRC connection establishment attempts and RRC connection recovery attempts. Figure 5 , is a flow chart of a unified access control process provided in an embodiment of the present application. The unified access control process is as follows:

[0122] Step 401: The network device sends unified access control parameters to the terminal device.

[0123] In step 402, the terminal device performs an access barring check based on the unified access control parameters broadcast by the network device (e.g., uac-BarringForAccessIdentity or ac-BarringForSpecialAC), the access category (Access Category) issued by the non-access layer, and the access identity (Access Identity) or access class (Access Class) issued by the non-access layer or generated by the access layer.

[0124] Exemplarily, access control is implemented based on an access identifier or an access class. The bit value corresponding to the access identifier or access class determines whether the corresponding access attempt is allowed. If the bit value corresponding to the access identifier or access class is 0, it indicates that the corresponding access attempt is allowed. If the bit value corresponding to the access identifier or access class is 1, it indicates that the corresponding access attempt is not allowed. For MPS, the access identifier in the NR system can be Access Identity 1, and the access class in the LTE system can be Access Class 12, 13, or 14. Access Identity 1 or Access Class 12, 13, or 14 is only valid in the home country.

[0125] (5)MPS priority indication

[0126] When the RRC release message includes redirection information, the network device may also include an MPS priority indication in the RRC release message. The MPS priority indication is used to indicate that the terminal device can access according to the MPS priority indication in subsequent access. For example, it may include one or more of the following:

[0127] 1. When the terminal device sends an RRC establishment request, if the RRC connection establishment is the result of a release including an MPS priority indication and redirection, the terminal device sets the establishment cause to MPS priority access (mps-PriorityAccess), for example, when the cell establishing the RRC connection is an NR cell; or the terminal device sets the establishment cause to high priority access (high Priority Access), for example, when the cell establishing the RRC connection is an E-UTRA cell.

[0128] 2. When the terminal device sends an RRC recovery request, if the RRC connection recovery occurs after the release including the MPS priority indication and redirection, the terminal device sets the recovery cause to MPS priority access, for example, when the cell in which the RRC connection is restored is an NR cell; or, the terminal device sets the recovery cause to high priority access, for example, when the cell in which the RRC connection is restored is an E-UTRA cell.

[0129] 3. When the terminal device is performing an access bar check, for example, when the terminal device attempts to access an NR cell, if the access attempt is the result of a release including an MPS priority indication and redirection, and access identifier 1 in the unified access control parameters broadcast by the NR cell indicates that access is allowed, the terminal device regards the access attempt as allowed. Alternatively, for example, when the terminal device attempts to access an E-UTRA cell, if the access attempt is the result of a release including an MPS priority indication and redirection, and any one of access levels 12, 13, or 14 in the unified access control parameters broadcast by the E-UTRA cell indicates that access is allowed, the terminal device regards the access attempt as allowed.

[0130] The above introduces the professional terms provided in the embodiments of the present application. The following will introduce in detail the specific implementation process of the MPS management method provided in the embodiments of the present application.

[0131] See also Figure 5 , Figure 5 This is a flow chart of an MPS management method provided in an embodiment of the present application. Figure 1 The MPS management approach shown in Figure 5 The terminal equipment and network equipment shown in . Figure 6 As shown, the MPS management method includes the following steps 501-502.

[0132] Step 501: A first network device sends a radio resource control (RRC) release message to a terminal device, wherein the RRC release message includes a multimedia priority service (MPS) priority indication (MPS Priority Indication) and a redirected frequency. The terminal device receives the RRC release message.

[0133] In this embodiment, the first network device carries the MPS priority indication and the redirected frequency in the RRC release message, instructing the terminal device to attempt to reside in the cell on the specified frequency. In the connection establishment process, connection recovery process or unified access control process after redirection, the terminal device accesses according to the MPS priority indication, thereby ensuring the priority and continuity of the service.

[0134] Exemplarily, the first network device may determine whether to include an MPS priority indication in the RRC release message based on the service quality of service (QoS) characteristics or the allocation and retention priority (ARP) of the terminal device. The MPS priority indication is used to indicate that the terminal device can accept MPS processing. For example, the terminal device can set the establishment cause to mps-Priority Access when redirecting to the NR cell.

[0135] For example, the first network device may include redirection information (Redirected Carrier Info) in the RRC release message based on factors such as load or network capability. The redirection information includes a redirected frequency point, and redirects the terminal device to the specified frequency point.

[0136] Exemplarily, the redirection information also includes the redirected RAT, that is, the RRC release message includes the MPS priority indication, the redirected frequency and the redirected RAT. For example, the redirection information includes the carrier information (Carrier InfoNR) of NR, and the redirected RAT is NR. The carrier information of NR includes the redirected frequency, thereby indicating that the terminal device attempts to reside in the cell on the specified frequency of NR. For another example, the redirection information includes the redirected carrier information (Redirected CarrierInfo-EUTRA) of E-UTRA, and the redirected RAT is E-UTRA. The redirected carrier information of E-UTRA includes the redirected frequency, thereby indicating that the terminal device attempts to reside in the cell on the specified frequency of EUTRA. The redirected RAT can be understood as the RAT corresponding to the redirected frequency.

[0137] Further, after receiving the RRC release message, the terminal device releases (release) or suspends (suspends) the RRC connection, and performs the following operations according to the redirection information included in the RRC release message:

[0138] (1) First, the terminal device attempts to reside in a suitable cell on the designated frequency (i.e., the redirected frequency) according to the redirection information. If a suitable cell is found on the designated frequency and resides in the suitable cell, the terminal device can request RRC connection establishment or RRC connection recovery from the suitable cell, for example, when the terminal device has a service transmission requirement;

[0139] (2) If the terminal device cannot find a suitable cell on the specified frequency, the terminal device attempts to reside in a cell on the specified RAT (i.e., the redirected RAT). If a suitable cell is found on the specified RAT and resides in the suitable cell, for example, when the terminal device has a service transmission requirement, the terminal device can request RRC connection establishment or RRC connection recovery from the suitable cell;

[0140] (3) If the terminal device cannot select a suitable cell on the specified RAT, the terminal device will perform a cell selection process to select a suitable cell based on the actual network conditions or its own stored information. If the terminal device finds a suitable cell through the cell selection process and resides in the suitable cell, then, for example, when the terminal device has a service transmission requirement, the terminal device may request RRC connection establishment or RRC connection recovery from the suitable cell. It should be noted that the suitable cell may not be a cell on the specified frequency and RAT in the redirection information.

[0141] It is understandable that whether the terminal device requests RRC connection establishment or RRC connection recovery is related to the state of the terminal device. For example, if the RRC release message received by the terminal device does not include a suspend configuration (suspend Config), the terminal device enters the RRC idle state (RRC_IDLE) state. When the terminal device has a service transmission requirement, the terminal device requests the network device to establish an RRC connection and executes the RRC connection establishment process. For another example, if the RRC release message received by the terminal device includes a suspend configuration, the terminal device enters the RRC inactive (RRC_INACTIVE) state. When the terminal device has a service transmission requirement, the terminal device requests the network device to resume the RRC connection and executes the RRC connection recovery process.

[0142] In step 502, the terminal device sends an RRC establishment request message or an RRC recovery request message to the second network device, wherein the RRC establishment request message is used to request to establish a connection to the first cell, and the RRC establishment request message includes an establishment reason; the RRC recovery request message is used to request to restore the connection to the first cell, and the RRC recovery request message includes a recovery reason.

[0143] If the first condition is met, the terminal device sets the establishment reason or the restoration reason to the first reason value, otherwise, the terminal device sets the establishment reason or the restoration reason to the second reason value. The first condition is related to at least one of the MPS priority indication or the redirected frequency.

[0144] In this embodiment, if the terminal device successfully resides in the first cell, for example, when the terminal device has a service transmission requirement, the terminal device may send an RRC establishment request message or an RRC recovery request message to the second network device where the first cell is located. The terminal device may determine the establishment reason or recovery reason carried in the establishment request message or the recovery request message based on whether the first condition is met.

[0145] Exemplarily, after receiving the RRC establishment request message or the RRC recovery request message, the second network device can learn the reason for connection establishment or recovery through the establishment reason or the recovery reason, or learn the service-related information that triggers the connection establishment or connection recovery, and thereby determine whether to accept or reject the connection establishment or recovery request, or determine the priority of the connection establishment or connection recovery.

[0146] It should be noted that, in actual operation, the first network device and the second network device may be the same or different. The specific judgment can be made based on the network range of the first network device and the second network device where the redirected first cell is located, as well as the network division standards, etc., which are not limited here.

[0147] It is understandable that in the prior art, the MPS priority indication carried in the redirection is only used for connection establishment or connection recovery after the redirection, but the effective application period and scope of the MPS priority indication are not clear. For example, it is mainly reflected in the following scenarios:

[0148] Scenario 1: The first network device redirects the terminal device to a designated frequency, but the terminal device does not find a suitable cell on the designated frequency. The terminal device attempts to camp on the designated RAT and finds and camps on a suitable cell on a non-designated frequency. When initiating connection establishment or connection recovery with a cell on the non-designated frequency, it cannot determine whether to connect.

[0149] In scenario 1, the cell in which the terminal device resides and attempts to access belongs to the RAT specified by the redirection. The terminal device initiates connection establishment or connection recovery in the cell and cannot determine whether to access according to the MPS priority indication. For example, the first network device instructs the terminal device to redirect to NR frequency f1. The terminal device does not find a suitable cell on frequency f1, but eventually finds a suitable NR cell on frequency f2 and establishes or recovers a connection on the cell. At this time, the terminal device cannot determine whether to access according to the MPS priority indication.

[0150] In scenario one, the cell in which the terminal device resides and attempts to access does not belong to the redirection indication RAT. The terminal device initiates connection establishment or connection recovery in the cell and cannot determine whether to access according to the MPS priority indication. For example, the first network device instructs the terminal device to redirect to LTE frequency f3. The terminal device does not find a suitable cell on frequency f3, nor does it find a suitable cell in E-UTRA. It eventually finds a suitable cell on NR frequency f4 and establishes or recovers a connection on the cell. At this time, the terminal device cannot determine whether to access according to the MPS priority indication.

[0151] Scenario 2: The first network device redirects the terminal device to a designated frequency, but the terminal device fails to find a suitable cell on the designated frequency and RAT. After a long period of multiple rounds of cell search and selection, the terminal device successfully camps on a cell on a non-designated frequency or RAT. The terminal device is unable to determine whether to access the cell according to the MPS priority indication.

[0152] It is understandable that, when the first condition is met, the terminal device can set the establishment reason or recovery reason to the first reason value. Alternatively, the terminal device needs to meet other conditions before setting the establishment reason or recovery reason to the first reason value. When the first condition is not met, the terminal device will not set the establishment reason or recovery reason to the first reason value. That is, the terminal device may set the establishment reason or recovery reason to the first reason value only when the first condition is met. It should be noted that the logic of meeting the first condition below is similar and will not be repeated here. For other conditions that the terminal device needs to meet, please refer to the specific examples.

[0153] Optionally, in a possible implementation, before step 502, the following steps are further included:

[0154] In step 501a, the terminal device receives first indication information sent by the second network device, where the first indication information is used to indicate that the first access identifier or the first access level allows access.

[0155] Step 501b: When the first condition is met, the terminal device considers that the access attempt is allowed.

[0156] In this implementation, the terminal device performs access barring check before sending the RRC setup request message or the RRC resume request message. If the RRC connection establishment or resume request initiated by the terminal device is the result of the release including the MPS priority indication and redirection, the terminal device determines whether the first access identity or the first access class is barred according to the first indication information. If the first access identity or the first access class is not barred and the first condition is met, the terminal device determines that the second network device allows the terminal device to access according to the MPS priority indication. The first access identity can be an access identity corresponding to the MPS, and the first access class can be an access class corresponding to the MPS or a high-priority access class.

[0157] For example, if the first cell is an NR cell, the first access identity is access identity 1, and a bit corresponding to the access identity 1 is set to 0 to indicate that the access attempt is allowed. If the RRC connection establishment request or the resume request initiated by the terminal device is the result of the release including the MPS priority indication and redirection, and the bit corresponding to the access identity 1 is set to 0 and the first condition is met, the terminal device considers the access attempt as allowed, or the terminal device determines that the second network device allows the access attempt.

[0158] For example, if the first cell is an LTE or E-UTRA cell, the first access class is access class 12, 13, or 14. A bit corresponding to the access class 12, 13, or 14 is set to 0 to indicate that the access attempt is allowed. If the RRC connection establishment request or the resume request initiated by the terminal device is the result of the release including the MPS priority indication and redirection, and the bit corresponding to any one of the access class 12, 13, or 14 is set to 0 and the first condition is met, the terminal device considers the access attempt as allowed, or the terminal device determines that the second network device allows the access attempt.

[0159] Optionally, in a possible implementation, if the first access identity or the first access class is barred or the first condition is not met, the terminal device continues to determine whether the access is allowed according to other indication information.

[0160] In this implementation, for example, the terminal device can determine whether the access is allowed according to the size relationship between a random number generated by the terminal device and a network-indicated access control barring factor (Uac-Barring Factor).

[0161] Optionally, in a possible implementation, the terminal device can consider the MPS priority indication as invalid, discard the MPS priority indication, or release the MPS priority indication when the first condition is not met. Only when the MPS priority indication is valid, the terminal device can access according to the MPS priority indication.

[0162] Optionally, in a possible implementation, the first condition includes at least one of the following:

[0163] The first cell belongs to the redirected frequency point; or, the first cell and the redirected frequency point correspond to the same RAT; or, the RRC setup request message or the RRC resume request message is the first RRC setup request message or RRC resume request message sent after the RRC release message is received; or, the timer is not expired, and the timer is used to indicate the validity duration of the MPS priority indication; or, the first cell belongs to the first area, and the first area is a home area or a service area of the terminal device.

[0164] In this implementation manner, the specific description of each condition is as follows:

[0165] Condition 1: The first cell belongs to the redirected frequency point.

[0166] The terminal device determines the establishment cause or the resume cause carried in the establishment request message or the resume request message according to Condition 1. In the case of satisfying Condition 1, the establishment cause or the resume cause is the first reason value, otherwise, the establishment cause or the resume cause is the second reason value. It can be understood that the terminal device determines whether the first cell establishing or resuming the RRC connection is on the redirected frequency point. If the first cell is on the redirected frequency point, the terminal device can set the establishment cause or the resume cause to the first reason value, otherwise, the terminal device sets the establishment cause or the resume cause to the second reason value.

[0167] Exemplarily, the following one or more can be included:

[0168] 1.1. When setting the RRC establishment request establishment cause content, if the RRC connection establishment is the result of (or occurs after) including the MPS priority indication and the redirected release, and the RRC connection establishment is on the redirected frequency point, the terminal device sets the establishment cause to the first reason value, otherwise, the terminal device sets the establishment cause to the second reason value.

[0169] 1.2. When setting the RRC resume request resume cause content, if the RRC connection resume occurs after (or is the result of) including the MPS priority indication and the redirected release, and the RRC connection resume is on the redirected frequency point, the terminal device sets the resume cause to the first reason value, otherwise, the terminal device sets the resume cause to the second reason value.

[0170] 1.3. When the terminal device performs an access barring check, if the access attempt is the result of a release including an MPS priority indication and redirection (or occurs after a release including an MPS priority indication and redirection), and the RRC connection establishment or RRC connection recovery is on the redirected frequency, and the first access identifier or the first access level is indicated as allowing access, the terminal device sets the establishment cause or recovery cause to the first cause value; otherwise, the terminal device sets the establishment cause or recovery cause to the second cause value.

[0171] Optionally, in one possible implementation, if the first cell in which the terminal device establishes an RRC connection or restores an RRC connection is not on the redirected frequency, the terminal device may consider the MPS priority indication invalid, discard the MPS priority indication, or release the MPS priority indication. Only when the MPS priority indication is valid can the terminal device access according to the MPS priority indication.

[0172] Condition 1 clarifies that the MPS priority indication is only valid at the redirected frequency, or that access can only be made according to the MPS priority indication at the redirected frequency, thereby clarifying the valid range of the MPS priority indication.

[0173] Condition 2: The first cell and the redirected frequency correspond to the same RAT.

[0174] The terminal device determines the establishment reason or recovery reason carried in the establishment request message or the recovery request message according to condition 2. When condition 2 is met, the establishment reason or recovery reason is the first reason value; otherwise, the establishment reason or recovery reason is the second reason value. It can be understood that the terminal device determines whether the first cell for establishing an RRC connection or restoring an RRC connection is on the redirected RAT. If the first cell is on the redirected RAT, the terminal device can set the establishment reason or recovery reason to the first reason value; otherwise, the terminal device sets the establishment reason or recovery reason to the second reason value. At this time, the RRC release message also includes the redirected RAT. The redirected RAT can be understood as the RAT corresponding to the redirected frequency.

[0175] For example, it may specifically include:

[0176] 2.1. When the terminal device sets the establishment cause content of the RRC establishment request, if the RRC connection establishment is the result of a release including an MPS priority indication and redirection (or occurs after a release including an MPS priority indication and redirection), and the RRC connection establishment is on the redirected RAT, the terminal device sets the establishment cause to the first cause value; otherwise, the terminal device sets the establishment cause to the second cause value.

[0177] 2.2. When the terminal device sets the recovery reason content of the RRC recovery request, if the RRC connection recovery occurs after the release including the MPS priority indication and redirection (or the RRC connection recovery is the result of the release including the MPS priority indication and redirection), and the RRC connection recovery is on the redirected RAT, the terminal device sets the recovery reason to the first reason value; otherwise, the terminal device sets the recovery reason to the second reason value.

[0178] 2.3. When the terminal device performs an access barring check, if the access attempt is the result of a release including an MPS priority indication and redirection (or occurs after a release including an MPS priority indication and redirection), the RRC connection establishment or RRC connection recovery is on the redirected RAT, and the first access identifier or the first access level is indicated as allowing access, the terminal device sets the establishment cause or recovery cause to the first cause value; otherwise, the terminal device sets the establishment cause or recovery cause to the second cause value.

[0179] Optionally, if the first cell in which the terminal device establishes an RRC connection or resumes an RRC connection is not on the redirected RAT, the terminal device may consider the MPS priority indication invalid or discard the MPS priority indication or release the MPS priority indication. Only when the MPS priority indication is valid can the terminal device access according to the MPS priority indication.

[0180] Condition 2 clarifies that the MPS priority indication is only valid in the redirected RAT, or that access can be performed according to the MPS priority indication only in the redirected RAT, thereby clarifying the valid range of the MPS priority indication.

[0181] Condition 3: The RRC setup request message or RRC resume request message is the first RRC setup request message or RRC resume request message sent after receiving the RRC release message.

[0182] The terminal device determines the establishment cause or recovery cause carried in the establishment request message or the recovery request message according to condition 3. If condition 3 is met, the establishment cause or recovery cause is the first cause value; otherwise, the establishment cause or recovery cause is the second cause value. It can be understood that the terminal device determines whether the establishment of the RRC connection or the restoration of the RRC connection is the first RRC establishment request message or RRC recovery request message sent after receiving the RRC release message. If it is the first RRC establishment request message or RRC recovery request message, the terminal device can set the establishment cause or recovery cause to the first cause value; otherwise, the terminal device sets the establishment cause or recovery cause to the second cause value.

[0183] For example, it may specifically include:

[0184] 3.1, When the terminal device sets the establishment cause of the RRC setup request, if the RRC connection setup is the result of (or occurs after) the release including the MPS priority indication and redirection, and the RRC connection setup is the first access attempt after the release, the terminal device sets the establishment cause to the first cause value; otherwise, it is considered that the first condition is not met, and the terminal device sets the establishment cause to the second cause value.

[0185] 3.2, When the terminal device sets the establishment cause of the RRC resume request, if the RRC connection resume is after (or the result of) the release including the MPS priority indication and redirection, and the RRC connection resume is the first attempt after the release, the terminal device sets the resume cause to the first cause value; otherwise, it is considered that the first condition is not met, and the terminal device sets the resume cause to the second cause value.

[0186] 3.3, When the terminal device performs the access barring check, if the access attempt is the result of (or occurs after) the release including the MPS priority indication and redirection, the access attempt is the first attempt after the release, and the first access identity or the first access class is indicated to allow access, the terminal device sets the establishment cause or the resume cause to the first cause value, otherwise, the terminal device sets the establishment cause or the resume cause to the second cause value.

[0187] Optionally, if the RRC connection setup is the first access attempt after the release including the MPS priority indication and redirection, the terminal device can consider the MPS priority indication invalid, or discard the MPS priority indication or release the MPS priority indication. Only when the MPS priority indication is valid, the terminal device can access according to the MPS priority indication.

[0188] Through condition 3, it is clear that the MPS priority indication is only valid for the first access attempt after the release including the MPS priority indication and redirection, or only the first access attempt after the release including the MPS priority indication and redirection can access according to the MPS priority indication, thereby clarifying the effective range of the MPS priority indication.

[0189] Condition 4: The timer is not expired, and the timer is used to indicate the effective duration of the MPS priority indication.

[0190] The terminal device determines the establishment reason or recovery reason carried in the establishment request message or the recovery request message according to condition 4. If condition 4 is met, the establishment reason or recovery reason is the first reason value; otherwise, the establishment reason or recovery reason is the second reason value. It can be understood that the terminal device determines whether the timer has timed out. If the timer has timed out, the terminal device can set the establishment reason or recovery reason to the first reason value; otherwise, the terminal device sets the establishment reason or recovery reason to the second reason value.

[0191] It can be understood that the fact that the timer has not timed out can be understood as the timer is running. During the timer operation, the MPS priority indication remains valid. When the timer is running or the timer has not timed out, the terminal device can use this indication to initiate RRC connection establishment or connection recovery, and access according to the MPS priority indication, for example, setting the establishment reason or recovery reason to the first reason value. In the case of timer timeout, it is deemed that the first condition is not met, and the MPS priority indication is invalid. In the case of timer timeout, the terminal device does not refer to this indication when initiating connection establishment or connection recovery, and cannot access according to the MPS priority indication. At this time, condition 4 can be understood as the MPS priority indication is valid.

[0192] For example, it may specifically include:

[0193] 4.1. When the terminal device sets the RRC establishment request content, if the RRC connection establishment is the result of a release including an MPS priority indication and redirection (or occurs after a release including an MPS priority indication and redirection), and the timer is running or the MPS priority indication is valid, the terminal device sets the establishment cause to the first cause value; otherwise, it is deemed that the first condition is not met, and the terminal device sets the establishment cause to the second cause value.

[0194] 4.2. When the terminal device sets the RRC recovery request content, if the RRC connection recovery occurs after the release including the MPS priority indication and redirection (or the RRC connection recovery is the result of the release including the MPS priority indication and redirection), and the timer is running or the MPS priority indication is valid, the terminal device will set the recovery cause to the first cause value; otherwise, it is deemed that the first condition is not met, and the terminal device will set the recovery cause to the second cause value.

[0195] 4.3、When the terminal device performs the access barring check, if the access attempt is the result of (or occurs after) the release including the MPS priority indication and redirection, the timer is running or the MPS priority indication is valid, and the first access identity or the first access class is indicated to allow access, the terminal device sets the establishment cause or the resume cause to the first cause value, otherwise, the terminal device sets the establishment cause or the resume cause to the second cause value.

[0196] It should be noted that the timer duration can be configured by the network, or can be a fixed duration, which is not limited here. Illustratively, the timer can be configured by the network, for example, the timer duration is included in the RRC release message. Alternatively, if the network includes the MPS priority indication in the RRC release message and does not include the timer duration configuration, the MPS priority indication is always valid until the terminal device receives the RRC release message without the MPS priority indication.

[0197] Illustratively, if the timer is configured by the network, the specific use case of the timer can be as follows:

[0198] 1. At time T1, the network device sends an RRC release message to the terminal device, wherein the RRC release message includes the configuration of the MPS priority indication and the timer configuration.

[0199] 2. After receiving the RRC release message, the terminal device performs the redirection process and starts the timer.

[0200] 3. From time T1 to time T2, the timer is running and the MPS priority indication is valid and available, during which the terminal device initiates connection establishment or connection recovery.

[0201] 4. At time T2, the timer expires, the terminal device releases or discards the MPS priority indication, and the terminal device subsequently initiates connection establishment or recovery without accessing according to the MPS priority indication.

[0202] In addition, it should be noted that the timer can use various calculation methods such as time period subtraction and countdown, which are not limited here, but are only for illustration.

[0203] Illustratively, the terminal device starts or restarts the timer when it receives the RRC release message including the MPS priority indication, or the terminal device starts or restarts the timer when it receives the RRC message including the timer duration configuration.

[0204] Exemplarily, the terminal device stops the timer in a case that the RRC connection setup is successful or the RRC connection resume is successful. Or the terminal device stops the timer when entering the RRC connected state. Or the terminal device stops the timer when the RRC state transition occurs.

[0205] By condition 4, it is clear that the MPS priority indication is only valid during the running of the timer, or only during the running of the timer can be accessed according to the MPS priority indication, so as to clarify the valid time length of the MPS priority indication.

[0206] Condition 5: The first cell belongs to the first area, and the first area is a home area or a service area of the terminal device.

[0207] The home area can be a home country, or the home area can be a home public land mobile network (HPLMN) and / or its equivalent PLMN. The home country or the home PLMN can be understood as the country or the registered PLMN of the terminal device. The service area can be a service PLMN (currentPLMN or serving PLMN) or a service country of the terminal device. The service PLMN or the service country can be understood as the PLMN or the country that provides service to the terminal device when receiving the RRC release message. Considering that the MPS priority related access identification or access level issued under the non-access layer is only valid in the home country, therefore, the MPS priority indication allocated by the network can also be limited to be valid only in the home country or the HPLMN. On the other hand, if the terminal device receives the RRC release message in the current service PLMN or service country, it is given the MPS priority, which does not necessarily mean that the terminal device can use the MPS priority in other PLMNs or other countries.

[0208] The terminal device determines the establishment cause or the resume cause carried in the establishment request message or the resume request message according to condition 5. In a case that the condition 5 is met, the establishment cause or the resume cause is a first reason value, otherwise, the establishment cause or the resume cause is a second reason value. It can be understood that the terminal device determines whether the first cell belongs to the first area. If the first cell belongs to the first area, the terminal device can set the establishment cause to the first reason value, otherwise, the terminal device sets the establishment cause to the second reason value.

[0209] Exemplarily, it can specifically include:

[0210] 5.1. When the terminal device sets the RRC establishment request content, if the RRC connection establishment is the result of a release including an MPS priority indication and redirection (or occurs after a release including an MPS priority indication and redirection), and the RRC connection establishment is within the first area, the terminal device sets the establishment cause to the first cause value; otherwise, it is deemed that the first condition is not met, and the terminal device sets the establishment cause to the second cause value.

[0211] 5.2. When the terminal device sets the RRC recovery request content, if the RRC connection recovery occurs after the release including the MPS priority indication and redirection (or the RRC connection recovery is the result of the release including the MPS priority indication and redirection), and the RRC connection recovery is within the first area, the terminal device will set the recovery cause to the first cause value; otherwise, it is deemed that the first condition is not met, and the terminal device will set the recovery cause to the second cause value.

[0212] 5.3. When the terminal device performs an access prohibition check, if the access attempt is the result of a release including an MPS priority indication and redirection (or occurs after a release including an MPS priority indication and redirection), the access attempt is within the first area, and the first access identifier or the first access level is indicated as allowing access, the terminal device sets the establishment cause or the restoration cause to the first cause value; otherwise, the terminal device sets the establishment cause or the restoration cause to the second cause value.

[0213] It should be noted that, in this embodiment, for scenario 2, the following special scenarios, which theoretically can use MPS priority indication, are excluded:

[0214] If the terminal device fails to search for a suitable cell on the redirected RAT, and if the terminal device continues to try on other RATs and still fails to search for a suitable cell, the non-access layer will trigger the terminal device to continue searching. If the terminal device eventually finds a suitable cell on the redirected RAT or the redirected frequency, it can request RRC connection establishment access or request RRC connection recovery in that cell. At this time, it is deemed that the first condition is not met, and the terminal device should regard the MPS priority indication as invalid. In the above scenario, the reason why the terminal device regards the MPS priority indication as invalid is that requesting RRC connection establishment or requesting RRC connection recovery at this time is not the result of redirection, but the result of the upper layer triggering the terminal device to search the network.

[0215] Optionally, in a possible implementation, the terminal device determines the first condition based on second indication information sent by the network device.

[0216] In this possible implementation, after receiving the second indication information, the terminal device determines the first condition according to the second indication information. After determining the first condition, the terminal device determines whether to access according to the MPS priority indication.

[0217] Exemplarily, the RRC release message also includes second indication information, which is used to determine a condition for the validity of the MPS priority indication, i.e., the first condition described above. For example, the second indication information is used to indicate whether access is performed on the redirected frequency or on the redirected RAT in accordance with the MPS priority indication.

[0218] Through this implementation, the first condition can be obtained from the network device, thereby more flexibly configuring the validity of the MPS priority indication.

[0219] In this embodiment, by setting the first condition, the effective usage scope and effective usage duration of the MPS priority indication can be clarified. Only when the first condition is met can the terminal device access the network according to the MPS priority indication to solve the problem in the above scenario, thereby managing the validity of the MPS priority indication during the redirection process.

[0220] Optionally, in a possible implementation, the first cause value is an MPS priority access (mps-PriorityAccess) cause value or a high priority access (highPriorityAccess) cause value, and the second cause value is a cause value received from a non-access stratum (NAS).

[0221] Exemplarily, the first cause value is set to MPS priority access (mps-PriorityAccess). At this time, the first cell to establish a connection or restore a connection is an NR cell.

[0222] Exemplarily, the first cause value is set to high priority access (highPriorityAccess). In this case, the first cell for establishing a connection or restoring a connection is an LTE or E-UTRA cell.

[0223] In this implementation, different cause values ​​are set so that the terminal device can access the service according to the priority of the MPS during the connection establishment or recovery process after redirection, thereby ensuring service priority and service continuity.

[0224] Optionally, in a possible implementation, each condition included in the first condition can be selected as one or combined into multiple conditions for operation.

[0225] In this implementation, illustratively:

[0226] 1. Condition 1 is used in combination with condition 4: the terminal device determines whether the timer has expired and whether the first cell for establishing an RRC connection or restoring an RRC connection is on the redirected frequency. If the timer has not expired and the first cell is on the redirected frequency, the terminal device may set the establishment cause or the restoration cause to the first cause value; otherwise, the terminal device sets the establishment cause or the restoration cause to the second cause value.

[0227] For example, it may specifically include:

[0228] a. When the terminal device sets the RRC establishment request content, if the RRC connection establishment is the result of a release including an MPS priority indication and redirection (or occurs after a release including an MPS priority indication and redirection), the RRC connection establishment is on the redirected frequency, and the timer is running, the terminal device sets the establishment cause to the first cause value; otherwise, the terminal device sets the establishment cause to the second cause value.

[0229] b. When the terminal device sets the RRC recovery request content, if the RRC connection recovery occurs after the release including the MPS priority indication and redirection (or the RRC connection recovery is the result of the release including the MPS priority indication and redirection), the RRC connection recovery is on the redirected frequency, and the timer is running, the terminal device sets the recovery cause to the first cause value; otherwise, the terminal device sets the recovery cause to the second cause value.

[0230] c. When the terminal device performs an access prohibition check, if the access attempt is the result of a release including an MPS priority indication and redirection (or occurs after a release including an MPS priority indication and redirection), the RRC connection establishment is on the redirected frequency, the timer is running, and the first access identifier or the first access level is indicated as allowing access, the terminal device sets the recovery cause and the establishment cause to the first cause value; otherwise, the terminal device sets the establishment cause to the second cause value.

[0231] For example, when the timer is running, the MPS priority indication remains valid. If the terminal device initiates connection establishment, connection recovery, or access prohibition check on the redirected frequency during this period, the MPS priority indication can be used, and the establishment reason is access according to the MPS priority indication.

[0232] For example, when the timer is running, if the terminal device initiates connection establishment or connection recovery on a non-designated frequency point, the terminal device initiates connection establishment or connection recovery or access prohibition check without referring to the MPS priority indication and without determining the reason for access establishment according to the MPS priority indication.

[0233] 2. Condition 2 is used in combination with condition 4: The terminal device determines whether the timer is expired and whether the first cell where the RRC connection is established or resumed is on the redirected RAT. If the timer is not expired and the first cell is on the redirected RAT, the terminal device can set the establishment cause or the resume cause to the first cause value, otherwise the terminal device sets the establishment cause or the resume cause to the second cause value.

[0234] For example, it can specifically include:

[0235] a. When setting the RRC establishment request content, if the RRC connection establishment is the result of (or occurs after) the release with MPS priority indication and redirection, the RRC connection establishment is on the redirected RAT, and the timer is running, the terminal device sets the establishment cause to the first cause value, otherwise, the terminal device sets the establishment cause to the second cause value.

[0236] b. When setting the RRC resume request content, if the RRC connection resume is the result of (or occurs after) the release with MPS priority indication and redirection, the RRC connection resume is on the redirected RAT, and the timer is running, the terminal device sets the resume cause to the first cause value, otherwise, the terminal device sets the resume cause to the second cause value.

[0237] c. When performing the access barring check, if the access attempt is the result of (or occurs after) the release with MPS priority indication and redirection, the RRC connection establishment is on the redirected RAT, the timer is running, and the first access identity or the first access class is indicated to allow access, the terminal device sets the establishment cause to the first cause value, otherwise, the terminal device sets the establishment cause to the second cause value.

[0238] For example, when the timer is running, the MPS priority indication remains valid, and if the terminal device initiates connection establishment or connection resume or access barring check on the redirected RAT during this period, it can use the MPS priority indication and access according to the MPS priority indication.

[0239] For example, when the timer is running, if the terminal device initiates connection establishment or connection resume on a non-specified RAT, the terminal device does not refer to the MPS priority indication when initiating connection establishment or connection resume or access barring check, and does not access according to the MPS priority indication.

[0240] 3. Condition 2 is used in combination with Condition 3: The terminal device determines whether the RRC establishment request or RRC recovery request is the first attempt on the redirected RAT. If it is the first attempt on the redirected RAT, the terminal device can set the establishment cause or recovery cause to the first cause value; otherwise, the terminal device sets the establishment cause or recovery cause to the second cause value.

[0241] For example, it may specifically include:

[0242] a. When the terminal device sets the RRC establishment request content, if the RRC connection establishment is the result of a release including an MPS priority indication and redirection (or occurs after a release including an MPS priority indication and redirection), and the RRC establishment request is the first attempt on the redirected RAT, the terminal device sets the establishment cause to the first cause value; otherwise, the terminal device sets the establishment cause to the second cause value.

[0243] b. When the terminal device sets the RRC recovery request content, if the RRC connection recovery occurs after a release including MPS priority indication and redirection (or the RRC connection recovery is the result of a release including MPS priority indication and redirection), and the RRC recovery request is the first attempt on the redirected RAT, the terminal device sets the recovery cause to the first cause value; otherwise, the terminal device sets the recovery cause to the second cause value.

[0244] c. When the terminal device performs an access barring check, if the access attempt is the result of a release including an MPS priority indication and redirection (or occurs after a release including an MPS priority indication and redirection), the RRC establishment request or RRC recovery request is the first attempt on the redirected RAT, and the first access identifier or the first access level is indicated as allowing access, the terminal device sets the establishment cause or the recovery cause to the first cause value; otherwise, the terminal device sets the establishment cause to the second cause value.

[0245] 4. Condition 2, Condition 3, and Condition 5 are used in combination: The terminal device determines whether the RRC establishment request or RRC resumption request is the first attempt on the RAT redirected within the first area. If it is the first attempt on the RAT redirected within the first area, the terminal device may set the establishment cause or resumption cause to the first cause value; otherwise, the terminal device may set the establishment cause or resumption cause to the second cause value. Specifically, it may include:

[0246] a. When setting the content of the RRC setup request, if the RRC connection setup is the result of (or occurs after) the release including the MPS priority indication and redirection, and the RRC setup request is the first attempt on the RAT redirected within the first area, the terminal device sets the setup cause to the first cause value; otherwise, the terminal device sets the setup cause to the second cause value.

[0247] b. When setting the content of the RRC resume request, if the RRC connection resume is the result of (or occurs after) the release including the MPS priority indication and redirection, and the RRC resume request is the first attempt on the RAT redirected within the first area, the terminal device sets the resume cause to the first cause value; otherwise, the terminal device sets the resume cause to the second cause value.

[0248] c. When performing the access barring check, if the access attempt is the result of (or occurs after) the release including the MPS priority indication and redirection, the RRC setup request or the RRC resume request is the first attempt on the RAT redirected within the first area, and the first access identity or the first access class is indicated to allow access, the terminal device sets the setup cause or the resume cause to the first cause value; otherwise, the terminal device sets the setup cause or the resume cause to the second cause value.

[0249] It should be noted that those skilled in the art can clearly understand that, in actual operation, each condition included in the first condition can be combined according to actual needs or tests. For the convenience and brevity of description, the specific description of the combination process of each condition in the first condition can refer to the description of the above several combinations, and will not be repeated here.

[0250] It can be understood that, in order to realize the functions in the above embodiments, the network device and the terminal device include the corresponding hardware structure and / or software module for executing each function. Those skilled in the art should easily realize that, in combination with the units and method steps of the examples described in the embodiments disclosed in the present application, the present application can be realized in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in hardware or computer software driven hardware depends on the specific application scenario and design constraints of the technical solution.

[0251] Please refer to Figure 6 , Figure 6 Another flowchart of an MPS management method provided by the embodiments of the present application is shown. In the flowchart, Figure 1 The MPS management method shown in the flowchart is applied to Figure 6The terminal device and the network device are shown in FIG. 1. Figure 7 As shown in FIG. 6, the MPS management method includes steps 601-602.

[0252] Step 601: receiving a radio resource control (RRC) release message sent by a network device, wherein the RRC release message includes a multimedia priority service (MPS) priority indication (mpsPriorityIndication) and a redirected frequency point.

[0253] It should be noted that step 601 is similar to step 501 described above, and the specific implementation and technical details are described in step 501 above, which will not be described here.

[0254] Step 602: discarding the MPS priority indication if a second condition is met.

[0255] In this embodiment, after the terminal device receives the RRC release message sent by the network device, the MPS priority indication is discarded or released if the second condition is met, and the MPS priority indication is considered invalid. After the MPS priority indication is discarded or released, the terminal device no longer accesses according to the MPS priority indication in the RRC connection establishment or connection recovery or access barring check initiated by the terminal device.

[0256] Optionally, in one possible implementation, the second condition includes at least one of the following:

[0257] The terminal device does not find a suitable cell on the redirected frequency point; or the terminal device does not find a suitable cell on the redirected RAT; or the terminal device sends an RRC setup request message or an RRC resume request message; or a timer expires, the timer being used to indicate the validity duration of the MPS priority indication; or the terminal device camps on or accesses a cell outside the first area.

[0258] In this implementation, the specific description of each condition in the second condition is as follows:

[0259] Condition 6: the terminal device does not find a suitable cell on the redirected frequency point.

[0260] After receiving the RRC release message containing redirection information and the MPS priority indication, the terminal device searches for a suitable cell on the redirected frequency point according to the redirection information. If the terminal device does not find a suitable cell on the redirected frequency point, the terminal device discards the MPS priority indication.

[0261] Condition 7: the terminal device does not find a suitable cell on the redirected RAT; or the terminal device starts a cell selection process.

[0262] After receiving the RRC release message containing the redirection information and the MPS priority indication, the terminal device searches for a suitable cell on the redirected frequency according to the redirection information. If the terminal device does not find a suitable cell on the redirected frequency, the terminal device searches for a suitable cell on the redirected RAT. If the terminal device does not find a suitable cell on the suitable RAT, the terminal device performs the cell selection process and discards the MPS priority indication.

[0263] Condition 8: The terminal device sends an RRC establishment request message or an RRC recovery request message.

[0264] After receiving the RRC release message containing redirection information and MPS priority indication, the terminal device finds a suitable cell to reside in and initiates connection establishment or connection recovery, and the terminal device discards the MPS priority indication.

[0265] Condition 9: The timer times out. The timer is used to indicate the validity period of the MPS priority indication.

[0266] After receiving the RRC release message including the redirection information and the MPS priority indication, if the timer times out, the terminal device discards the MPS priority indication. Specific instructions on starting, restarting, or stopping the timer can be found in step 502 of the above embodiment.

[0267] Condition 10: The terminal device resides in or accesses a cell outside the first area.

[0268] After receiving the RRC release message including the redirection information and the MPS priority indication, if the terminal device resides in or accesses a cell outside the first area, the terminal device discards the MPS priority indication.

[0269] It should be noted that those skilled in the art can clearly understand that, in actual operation, one of the second conditions can be optionally implemented according to actual needs or experiments, or the various conditions included in the second condition can be combined and implemented. For the convenience and conciseness of description, the specific description of the combined implementation process of each condition in the second condition can refer to the description of conditions 1 to 5 in the above embodiment, and will not be repeated here.

[0270] See also Figure 7 , Figure 1 This is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. The communication device 7000 may be as follows: Figure 5 One of the terminal devices 120a-120j shown may also be a component of the terminal device (e.g., a processor, a chip, or a chip system). The communication device 7000 includes:

[0271] The receiving unit 7001 is configured to receive a radio resource control (RRC) release message, wherein the RRC release message includes a multimedia priority service (MPS) priority indication and a redirected frequency;

[0272] a sending unit 7002, configured to send an RRC establishment request message or an RRC recovery request message, wherein the RRC establishment request message is used to request establishment of a connection to the first cell, and the RRC establishment request message includes an establishment cause; and the RRC recovery request message is used to request restoration of the connection to the first cell, and the RRC recovery request message includes a restoration cause;

[0273] Among them, when the first condition is met, the establishment reason or the recovery reason is the first reason value, otherwise, the establishment reason or the recovery reason is the second reason value, and the first condition is related to at least one of the MPS priority indication or the redirected frequency.

[0274] It should be noted that, in actual operation, the receiving unit 7001 and the sending unit 7002 may be located inside the same module of the same communication device, or in different modules of the same communication device, or in different communication devices. The specific judgment can be made based on the network range of the receiving unit 7001 and the sending unit 7002 and the network division standard, etc., and is not limited here.

[0275] In one possible implementation, the first condition includes at least one of the following:

[0276] The first cell belongs to the redirected frequency; or, the first cell and the redirected frequency correspond to the same RAT; or, the RRC establishment request message or the RRC recovery request message is the first RRC establishment request message or RRC recovery request message sent after receiving the RRC release message; or, the timer has not timed out, and the timer is used to indicate the valid duration of the MPS priority indication; or, the first cell belongs to the first area, and the first area is the home area or service area of ​​the terminal device.

[0277] It should be noted that technical personnel in the relevant field can clearly understand that in actual operation, the various conditions included in the first condition can be combined according to actual needs or experiments. For the convenience and conciseness of description, the specific description of the combined working process of each condition in the first condition can refer to the description of the above-mentioned combinations and will not be repeated here.

[0278] In a possible implementation, the first cause value is an MPS priority access cause value.

[0279] In a possible implementation, the first cause value is a high-priority access cause value.

[0280] In a possible implementation, the second cause value is a cause value received from the non-access stratum.

[0281] In a possible implementation, when the first condition is not met, the MPS priority indication is invalid.

[0282] In one possible implementation, before sending the RRC establishment request message or the RRC recovery request message, the receiving unit 7001 is further configured to:

[0283] receiving indication information, where the indication information is used to indicate that the first access identifier or the first access level allows access;

[0284] In case the first condition is met, the access attempt is considered to be allowed.

[0285] In a possible implementation, the terminal device determines the first condition according to a currently used mobile communication protocol.

[0286] In one possible implementation, the RRC release message further includes a first condition;

[0287] After receiving the radio resource control RRC release message, the receiving unit determines the first condition according to the RRC release message sent by the network device.

[0288] In this embodiment, the terminal device receives an RRC establishment request message or an RRC recovery request message through the receiving unit 7001, and when successfully camped on the first cell and detecting that the first condition is met, sends the RRC establishment request message or the RRC recovery request message through the sending unit 7002. Thus, by clarifying the conditions for the terminal device to use the priority of the MPS, the validity of the MPS priority is managed, avoiding the communication impact on other terminal devices accessing the network caused by the terminal device erroneously accessing the network according to the priority of the MPS.

[0289] In this embodiment, the operations performed by each unit in the communication device 7000 are the same as those described above. Figure 8 The method described in the embodiment shown is similar and can be used for the functions of the terminal device in the above method embodiment, and can also achieve the beneficial effects of the above method embodiment, which will not be repeated here.

[0290] See also Figure 8 , Figure 1 is a structural diagram of another communication device provided in an embodiment of the present application. The communication device 8000 may be as follows Figure 5 The network device 110a or 110b shown may also be a component of a network device (e.g., a processor, a chip, or a chip system). The communication apparatus 8000 includes:

[0291] The sending unit 8001 is configured to send a radio resource control (RRC) release message to the terminal device, wherein the RRC release message includes a multimedia priority service (MPS) priority indication and a redirected frequency;

[0292] Receiving unit 8002 is used to receive an RRC establishment request message or an RRC recovery request message, wherein the RRC establishment request message is used to request to establish a connection to the first cell, and the RRC establishment request message includes an establishment cause. The RRC recovery request message is used to request to restore the connection to the first cell, and the RRC recovery request message includes a recovery cause. The establishment cause or the recovery cause is a first cause value or a second cause value. The first cause value or the second cause value is related to a first condition, and the first condition is related to at least one of the MPS priority indication or the redirected frequency.

[0293] It should be noted that, in actual operation, the receiving unit 8001 and the sending unit 8002 may be located inside the same module of the same communication device, or in different modules of the same communication device, or in different communication devices. The specific judgment can be made based on the network range of the receiving unit 8001 and the sending unit 8002 and the network division standard, etc., and is not limited here.

[0294] In one possible implementation, the first condition includes at least one of the following:

[0295] The first cell belongs to the redirected frequency; or, the first cell and the redirected frequency correspond to the same RAT; or, the RRC establishment request message or the RRC recovery request message is the first RRC establishment request message or RRC recovery request message sent after receiving the RRC release message; or, the timer has not timed out, and the timer is used to indicate the valid duration of the MPS priority indication; or, the first cell belongs to the first area, and the first area is the home area or service area of ​​the terminal device.

[0296] It should be noted that technical personnel in the relevant field can clearly understand that in actual operation, the various conditions included in the first condition can be combined according to actual needs or experiments. For the convenience and conciseness of description, the specific description of the combined working process of each condition in the first condition can refer to the description of the above-mentioned combinations and will not be repeated here.

[0297] In a possible implementation, the first cause value is an MPS priority access cause value.

[0298] In a possible implementation, the first cause value is a high-priority access cause value.

[0299] In a possible implementation, the second cause value is a cause value received from the non-access stratum.

[0300] In one possible implementation, before receiving the RRC establishment request message or the RRC recovery request message, the sending unit 8001 is further configured to:

[0301] Send indication information, where the indication information is used to indicate that the first access identifier or the first access level allows access.

[0302] In a possible implementation, the mobile communication protocol currently used by the terminal device indicates the first condition.

[0303] In a possible implementation manner, the RRC release message also includes the first condition.

[0304] In this embodiment, based on load balancing considerations, the first network device will send an RRC release message to the terminal device through the sending unit 8001. The terminal device will attempt to reside on the redirected frequency or a suitable cell on the designated RAT according to the redirection information in the RRC release message. If the residency on the designated frequency or designated RAT is successful, access will be performed according to the MPS priority indication. If the terminal device fails to redirect to the designated frequency or designated RAT, it will continue to try to search for and reside on other frequencies or RATs. If the receiving unit 8002 receives an RRC establishment request message or an RRC recovery request message, the RRC establishment request message or the RRC recovery request message includes a first cause value, and the first cause value is related to the first condition, and the first condition is related to at least one of the MPS priority indication or the redirected frequency, it means that the terminal device accesses the second network device while using the MPS priority. Therefore, by clarifying the conditions for the terminal device to use the MPS priority, the validity of the MPS priority is managed, avoiding the communication impact caused by the terminal device mistakenly accessing according to the MPS priority on other terminal devices accessing the network.

[0305] In this embodiment, the operations performed by each unit in the communication device 8000 are the same as those described above. Figure 9 The method described in the embodiment shown is similar and can be used for the functions of the network device in the above method embodiment, and can also achieve the beneficial effects of the above method embodiment, which will not be repeated here.

[0306] See also Figure 9 , Figure 1 is a structural diagram of another communication device provided in an embodiment of the present application. The communication device 9000 may be as follows Figure 6 One of the terminal devices 120a-120j shown may also be a component of the terminal device (such as a processor, a chip, or a chip system). The communication device 9000 includes:

[0307] The receiving unit 9001 is configured to receive a radio resource control (RRC) release message sent by a network device, wherein the RRC release message includes a multimedia priority service (MPS) priority indication (Mps Priority Indication) and a redirected frequency.

[0308] The processing unit 9002 is configured to discard the MPS priority indication when the second condition is met.

[0309] In this embodiment, after the receiving unit 9001 receives the RRC release message sent by the network device, the processing unit 9002 will discard or release the MPS priority indication if it is determined that the second condition is met. After discarding or releasing the MPS priority indication, the terminal device will no longer access according to the MPS priority indication in the RRC connection establishment or connection recovery or access barring check initiated by the terminal device.

[0310] In one possible implementation, the second condition includes at least one of the following:

[0311] The terminal device does not find a suitable cell on the redirected frequency; or, the terminal device does not find a suitable cell on the redirected RAT; or the terminal device sends an RRC establishment request message or an RRC recovery request message; or the timer times out, the timer is used to indicate the valid duration of the MPS priority indication; or, the terminal device resides in or accesses a cell outside the home area.

[0312] It should be noted that those skilled in the art can clearly understand that, in actual operation, one of the second conditions can be optionally implemented according to actual needs or experiments, or the various conditions included in the second condition can be combined and implemented. For the convenience and conciseness of description, the specific description of the combined implementation process of each condition in the second condition can refer to the description of conditions 1 to 5 in the above embodiment, and will not be repeated here.

[0313] In this embodiment, the operations performed by each unit in the communication device 9000 are the same as those described above. Figure 10 The method described in the embodiment shown is similar and can be used for the functions of the terminal device in the above method embodiment, and can also achieve the beneficial effects of the above method embodiment, which will not be repeated here.

[0314] See also Figure 10 , Figure 5 This is a schematic diagram of the structure of another communication device provided in an embodiment of the present application. The communication device 1000 can be a network device, a terminal device, or a chip, a chip system, a processor, etc. that supports the terminal device or network device to implement the above method. The device can be used to implement the embodiment of the present application. Figure 10 For details of the described method, please refer to the description in the above method embodiment.

[0315] The apparatus 1000 includes one or more processors 1001 and an interface circuit 1002. The processor 1001 and the interface circuit 1002 are coupled to each other. It is understood that the interface circuit 1002 may be a transceiver or an input / output interface.

[0316] Optionally, the communication device 1000 may include one or more memories 1003 for storing instructions executed by the processor 1001 or storing input data required by the processor 1001 to run instructions or storing data generated after the processor 1001 runs instructions.

[0317] In another optional design, processor 1001 may include a transceiver unit for implementing receiving and transmitting functions. For example, the transceiver unit may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the receiving and transmitting functions may be separate or integrated. The transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or the transceiver circuit, interface, or interface circuit may be used for transmitting or delivering signals.

[0318] In another possible design, the communication device 1000 may include a circuit that can implement the functions of sending, receiving, or communicating in the aforementioned method embodiments.

[0319] When the communication device 1000 is a chip used in a terminal device, the terminal chip implements the functions of the terminal device in the above method embodiments. The terminal chip receives information from other modules in the terminal device (such as a radio frequency module or antenna), and the information is sent by the network device to the terminal device; or the terminal chip sends information to other modules in the terminal device (such as a radio frequency module or antenna), and the information is sent by the terminal device to the network device.

[0320] When the communication device 1000 is a module applied to a network device, the network device module of the network device implements the functions of the network device in the above method embodiment. The network device module receives information from other modules in the network device (such as a radio frequency module or antenna), and the information is sent by the terminal device to the network device; or the network device module sends information to other modules in the network device (such as a radio frequency module or antenna), and the information is sent by the network device to the terminal device. The network device module here can be a baseband chip of the network device, or it can be a DU or other module. The DU here can be a DU under the open radio access network (O-RAN) architecture.

[0321] It is to be understood that the processor 1001 in the embodiments of the present application can be a central processing unit (CPU), and can also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. The general-purpose processor can be a microprocessor or any conventional processor.

[0322] The method steps in the embodiments of the present application can be implemented in hardware, or in software instructions executable by a processor. The software instructions can be composed of corresponding software modules, which can be stored in random access memories, flash memories, read-only memories, programmable read-only memories, erasable programmable read-only memories, electrically erasable programmable read-only memories, registers, hard disks, mobile hard disks, CD-ROMs or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor, so that the processor can read information from, and write information to, the storage medium. The storage medium can also be a component of the processor. The processor and the storage medium can be located in an ASIC. In addition, the ASIC can be located in a network device or a terminal device. The processor and the storage medium can also exist as discrete components in the network device or the terminal device.

[0323] The apparatus described in the above embodiments can be a network device or a terminal device, but the scope of the apparatus described in the present application is not limited thereto, and the structure of the apparatus can not be limited by the description in the embodiments. The apparatus can be a stand-alone device or can be a part of a larger device. For example, the apparatus can be: Figure 11

[0324] (1) a stand-alone integrated circuit IC, or a chip, or a chip system or a subsystem;

[0325] (2) a set of one or more ICs, optionally including a storage component for storing data and / or instructions;

[0326] (3) an ASIC, such as a modem system-on-chip (MSM);

[0327] (4) a module that can be embedded in other devices;

[0328] ​(5) Receivers, terminals, smart terminals, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, network devices, cloud devices, artificial intelligence devices, machine devices, home devices, medical devices, industrial equipment, etc.;

[0329] (6)Others, etc.

[0330] When the communication device in the embodiment of the present application is a network device, the communication device can be as follows: Figure 8 The communication device may include one or more radio frequency units, such as a remote radio unit (RRU) 1110 and one or more baseband units (BBU) (also referred to as digital units, DU) 1120. The RRU 1110 may be referred to as a transceiver module, which may include a transmitting module and a receiving module, or the transceiver module may be a module capable of both transmitting and receiving functions. The transceiver module may be connected to Figure 8 The RRU 1110 corresponds to the transmitting unit 8001 or the receiving unit 8002 in the base station, that is, the transceiver module performs the actions performed by the transmitting unit 8001 and the receiving unit 8002. Optionally, the transceiver module can also be called a transceiver, a transceiver circuit, or a transceiver, etc., and may include at least one antenna 1111 and a radio frequency unit 1112. The RRU 1110 is mainly used for transmitting and receiving radio frequency signals and converting radio frequency signals into baseband signals. The BBU 1110 is mainly used for baseband processing, controlling the base station, etc. The RRU 1110 and the BBU 1120 can be physically arranged together or physically separated, that is, a distributed base station.

[0331] The BBU 1120 is the control center of the base station, which can also be called a processing module. It is mainly used to complete baseband processing functions such as channel coding, multiplexing, modulation, spread spectrum, etc. In addition, the processing module can control ​ For example, the BBU (processing module) can be used to control the base station to execute the operation process of the network device in the above method embodiment.

[0332] In one example, the BBU 1120 can be composed of one or more single boards, and multiple single boards can jointly support a wireless access network with a single access standard (such as an LTE network), or can separately support wireless access networks with different access standards (such as an LTE network, a 5G network, or other networks). The BBU 1120 also includes a memory 1121 and a processor 1122. The memory 1121 is used to store necessary instructions and data. The processor 1122 is used to control the base station to perform necessary actions, such as controlling the base station to execute the operation process of the network device in the above method embodiment. The memory 1121 and the processor 1122 can serve one or more single boards. That is, a memory and a processor can be set separately on each single board. Alternatively, multiple single boards can share the same memory and processor. In addition, necessary circuits can also be set on each single board.

[0333] An embodiment of the present application further provides a computer-readable medium on which a computer program is stored. When the computer program is executed by a computer, the functions of any of the above method embodiments are realized.

[0334] The embodiments of the present application also provide a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.

[0335] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. Available media may be magnetic media (eg, floppy disks, hard disks, tapes), optical media (eg, high-density digital video discs (DVDs)), or semiconductor media (eg, solid state disks (SSDs)).

[0336] It is understood that the systems, devices, and methods described in this application may also be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not performed. In addition, the coupling or direct coupling or communication connection shown or discussed may be through some interface, indirect coupling or communication connection of devices or units, and may be electrical, mechanical, or other forms.

[0337] The above is only a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be included in the scope of protection of the present application. The various numerical numbers involved in the embodiments of the present application are only for the convenience of description and are not used to limit the scope of the embodiments of the present application. The size of the sequence number of each process does not mean the order of execution. The order of execution of each process should be determined by its function and internal logic.

Claims

1. A multimedia priority service MPS management method, characterized in that: include: receiving a radio resource control (RRC) release message, wherein the RRC release message includes an MPS priority indication and a redirected frequency; Sending an RRC establishment request message or an RRC recovery request message, wherein the RRC establishment request message is used to request establishment of a connection to the first cell, and the RRC establishment request message includes an establishment cause; the RRC recovery request message is used to request restoration of the connection to the first cell, and the RRC recovery request message includes a restoration cause; Wherein, if the first condition is met, the establishment reason or the restoration reason is a first reason value; otherwise, the establishment reason or the restoration reason is a second reason value, the first condition is related to at least one of the MPS priority indication or the redirected frequency, and the first condition is used to control the terminal device to use the MPS priority indication; The first condition includes at least one of the following: The first cell belongs to the redirected frequency point; or, The first cell and the redirected frequency point correspond to the same radio access technology RAT; or, The RRC establishment request message or the RRC resumption request message is the first RRC establishment request message or RRC resumption request message sent after receiving the RRC release message; or, A timer has not timed out, the timer being used to indicate the validity period of the MPS priority indication; or The first cell belongs to a first area, which is a home area or a service area of ​​a terminal device.

2. The method according to claim 1, characterized in that The first cause value is an MPS priority access cause value.

3. The method according to claim 1, characterized in that The first cause value is a high priority access cause value.

4. The method according to any one of claims 1 to 3, characterized in that The second cause value is a cause value received from the non-access stratum.

5. The method according to any one of claims 1 to 3, characterized in that Before sending the RRC establishment request message or the RRC recovery request message, the method further includes: receiving first indication information, where the first indication information is used to indicate that access is allowed by a first access identifier or a first access level; In case the first condition is met, the access attempt is considered to be allowed.

6. The method according to any one of claims 1 to 3, characterized in that If the first condition is not met, the MPS priority indication is invalid.

7. A MPS management method, characterized in that: include: Sending a radio resource control (RRC) release message to the terminal device, wherein the RRC release message includes a multimedia priority service (MPS) priority indication and a redirected frequency; Receiving an RRC establishment request message or an RRC recovery request message, wherein the RRC establishment request message is used to request establishment of a connection to the first cell, the RRC establishment request message includes an establishment cause, the RRC recovery request message is used to request restoration of the connection to the first cell, the RRC recovery request message includes a recovery cause, the establishment cause or the recovery cause is a first cause value or a second cause value, the first cause value or the second cause value is related to a first condition, the first condition is related to at least one of the MPS priority indication or the redirected frequency, and the first condition is used to control the terminal device to use the MPS priority indication; The first condition includes at least one of the following: The first cell belongs to the redirected frequency point; or, The first cell and the redirected frequency point correspond to the same RAT; or, The RRC establishment request message or the RRC resumption request message is the first RRC establishment request message or RRC resumption request message sent after receiving the RRC release message; or, A timer has not timed out, the timer being used to indicate the validity period of the MPS priority indication; or The first cell belongs to a first area, which is a home area or a service area of ​​a terminal device.

8. The method according to claim 7, characterized in that The first cause value is an MPS priority access cause value.

9. The method according to claim 7, characterized in that The first cause value is a high priority access cause value.

10. The method according to any one of claims 7 to 9, characterized in that The second cause value is a cause value received from the non-access stratum.

11. The method according to any one of claims 7 to 9, characterized in that Before receiving the RRC establishment request message or the RRC recovery request message, the method further includes: First indication information is sent, where the first indication information is used to indicate that the first access identifier or the first access level allows access.

12. A communication device, characterized in that: include: A receiving unit, configured to receive a radio resource control (RRC) release message, wherein the RRC release message includes a multimedia priority service (MPS) priority indication and a redirected frequency; a sending unit, configured to send an RRC establishment request message or an RRC recovery request message, wherein the RRC establishment request message is used to request establishment of a connection to the first cell, and the RRC establishment request message includes an establishment cause; and the RRC recovery request message is used to request restoration of the connection to the first cell, and the RRC recovery request message includes a restoration cause; Wherein, if the first condition is met, the establishment reason or the restoration reason is a first reason value; otherwise, the establishment reason or the restoration reason is a second reason value, the first condition is related to at least one of the MPS priority indication or the redirected frequency, and the first condition is used to control the terminal device to use the MPS priority indication; The first condition includes at least one of the following: The first cell belongs to the redirected frequency point; or, The first cell and the redirected frequency point correspond to the same RAT; or, The RRC establishment request message or the RRC resumption request message is the first RRC establishment request message or RRC resumption request message sent after receiving the RRC release message; or, A timer has not timed out, the timer being used to indicate the validity period of the MPS priority indication; or The first cell belongs to a first area, which is a home area or a service area of ​​a terminal device.

13. The device according to claim 12, characterized in that The first cause value is an MPS priority access cause value.

14. The device according to claim 12, characterized in that The first cause value is a high priority access cause value.

15. The device according to any one of claims 12 to 14, characterized in that The second cause value is a cause value received from the non-access stratum.

16. The device according to any one of claims 12 to 14, characterized in that Before sending the RRC establishment request message or the RRC recovery request message, the receiving unit is further configured to: receiving first indication information, where the first indication information is used to indicate that access is allowed by a first access identifier or a first access level; In case the first condition is met, the access attempt is considered to be allowed.

17. The device according to any one of claims 12 to 14, characterized in that If the first condition is not met, the MPS priority indication is invalid.

18. A communication device, characterized in that: include: A sending unit, configured to send a radio resource control RRC release message to the terminal device, wherein the RRC release message includes a multimedia priority service MPS priority indication and a redirected frequency; a receiving unit, configured to receive an RRC establishment request message or an RRC recovery request message, wherein the RRC establishment request message is used to request establishment of a connection to the first cell, the RRC establishment request message includes an establishment cause, the RRC recovery request message is used to request restoration of the connection to the first cell, the RRC recovery request message includes a recovery cause, the establishment cause or the recovery cause is a first cause value or a second cause value, the first cause value or the second cause value is related to a first condition, the first condition is related to at least one of the MPS priority indication or the redirected frequency, and the first condition is used to control the terminal device to use the MPS priority indication; The first condition includes at least one of the following: The first cell belongs to the redirected frequency point; or, The first cell and the redirected frequency point correspond to the same RAT; or, The RRC establishment request message or the RRC resumption request message is the first RRC establishment request message or RRC resumption request message sent after receiving the RRC release message; or, A timer has not timed out, the timer being used to indicate the validity period of the MPS priority indication; or The first cell belongs to a first area, which is a home area or a service area of ​​a terminal device.

19. The device according to claim 18, characterized in that The first cause value is an MPS priority access cause value.

20. The device according to claim 18, characterized in that The first cause value is a high priority access cause value.

21. The device according to any one of claims 18 to 20, characterized in that The second cause value is a cause value received from the non-access stratum.

22. The device according to any one of claims 18 to 20, characterized in that Before receiving the RRC establishment request message or the RRC recovery request message, the sending unit is further configured to: First indication information is sent, where the first indication information is used to indicate that the first access identifier or the first access level allows access.

23. A communication device, characterized in that: The method comprises a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices and transmit them to the processor or send signals from the processor to other communication devices, and the processor is used to implement the method according to any one of claims 1 to 6 through a logic circuit or executing code instructions.

24. A communication device, characterized in that: The method comprises a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices and transmit them to the processor or send signals from the processor to other communication devices, and the processor is used to implement the method as claimed in any one of claims 7 to 11 through a logic circuit or executing code instructions.

25. A communication system, characterized in that: include: The communication device according to claim 23, and / or the communication device according to claim 24.

26. A computer program product, characterized in that When the computer program product is executed by a computer, the method according to any one of claims 1 to 6 is realized or the method according to any one of claims 7 to 11 is executed.

27. A computer-readable storage medium, characterized in that The storage medium stores a computer program or instruction. When the computer program or instruction is executed by the communication device, the method according to any one of claims 1 to 6 is implemented or the method according to any one of claims 7 to 11 is executed.

Images