Communication methods and communication devices

Abstract

A communication method and a communication device are disclosed. The method includes the following. That is, for a terminal device that transitions to the non-connection mode, when a network device calls the terminal device to receive the first multicast service, the network device may further instruct the terminal device in the RRC non-connection mode whether to provide the first multicast service. The terminal device may perform at least one of the following based on the paging and instruction of the network device. That is, receiving the first multicast service in the RRC non-connection mode. Or, performing an RRC connection control procedure. According to this method, network congestion caused by the simultaneous access of a large number of terminal devices can be avoided, and the access of the terminal device can be effectively managed.

Description

Technical Field

[0001] Embodiments of the present application relate to the field of communications, and more specifically, to a communication method and a communication device.

Background Art

[0002] This application was filed with the China National Intellectual Property Administration on May 26, 2022, and claims priority to Chinese Patent Application No. 202210580782.5, titled "Communication Method and Communication Device", which is hereby incorporated by reference in its entirety.

[0003] Multicast and broadcast services (MBS) are classified into two types, namely broadcast services and multicast services. When network congestion occurs, for terminal devices receiving multicast services, the network device may release the terminal device from the radio resource control (RRC) connected mode to the RRC disconnected mode, whereby the terminal device receives the multicast service in the RRC disconnected mode. When the network congestion is alleviated, the network device may send a paging message to call a plurality of terminal devices receiving the multicast service in the RRC disconnected mode and cause them to transition to the connected mode. The plurality of called terminal devices may simultaneously execute an RRC connection establishment procedure or an RRC connection resume procedure. However, when a large number of terminal devices access the network simultaneously, network congestion occurs.

Summary of the Invention

[0004] Embodiments of the present application provide a communication method and a communication device to more effectively manage the access of terminal devices.

[0005] According to the first embodiment, a communication method is provided. This method may be performed by a terminal device or by a component (such as a chip or circuit) of the terminal device. This is not limited to the foregoing. For the sake of clarity, an example of this method being performed by a terminal device is described below.

[0006] This method may include the following: a terminal device receives a group paging message from a network device, where the group paging message includes first information, which is used to call a terminal device group to receive the first multicast service, and the terminal device group includes terminal devices; and the terminal device performs at least one of the following based on the first and second information, where the second information is used to call a network device to control radio resources ( RRC ) Indicates whether to provide the initial multicast service to a group of terminal devices in disconnected mode. That is, the step of receiving the initial multicast service in RRC disconnected mode, or the step of performing an RRC connection control procedure.

[0007] In the technical solution described above, terminal devices are notified whether or not they should receive the initial multicast service in RRC-disconnected mode. This allows some terminal devices to switch to RRC-disconnected mode to receive multicast services, while others can switch to RRC-connected mode to receive multicast services. The access control procedure is extended, which avoids network congestion caused by a large number of terminal devices accessing simultaneously after receiving a paging message, and allows for effective management of terminal device access.

[0008] In some implementations of the first aspect, a terminal device deciding to receive the first multicast service in RRC-disconnected mode based on the first and second pieces of information includes: if the second piece of information indicates that a network device will provide the first multicast service to a group of terminal devices in RRC-disconnected mode, the terminal device receives the first multicast service in RRC-disconnected mode; or, if the terminal device initiates an access control procedure based on the first piece of information and is not permitted access to the network device, the terminal device receives the first multicast service in RRC-disconnected mode, and the second piece of information indicates that a network device will provide the first multicast service to a group of terminal devices in RRC-disconnected mode.

[0009] In some implementations of the first aspect, if the second information indicates that a network device provides the initial multicast service to a terminal device that is in disconnected mode, the terminal device does not initiate an access control procedure.

[0010] In some implementations of the first aspect, a terminal device deciding to receive the first multicast service in RRC-disconnected mode based on the first and second pieces of information includes: if the second piece of information indicates that the network equipment will not provide the first multicast service to a group of terminal devices in RRC-disconnected mode, the terminal device performs an RRC connection control procedure; or, if the terminal device initiates an access control procedure based on the first piece of information and is permitted access to the network equipment, the terminal device performs an RRC connection control procedure.

[0011] In some implementations of the first embodiment, the second information is carried in a group paging message, or the second information is carried over a multicast control channel.

[0012] In some implementations of the first embodiment, if a terminal device is not permitted to access a network device, the method further includes: that the terminal device, within the execution time of the first timer, the physical downlink control channel corresponding to the multicast control channel ( PDCCH ) When monitoring and obtaining configuration information for the initial multicast service, the terminal device should either terminate the access control procedure or stop initiating the access control procedure after the first timer expires.

[0013] In some implementations of the first embodiment, if a terminal device is not permitted to access a network device, the method further includes: if the terminal device has not obtained configuration information for the first multicast service by monitoring the PDCCH of the multicast control channel within the execution time of the first timer, the terminal device restarts the access control procedure after the first timer has expired, where the execution time of the first timer is the duration for which the terminal device must wait after being denied access to the network device before restarting the access control procedure.

[0014] In some implementations of the first embodiment, if a terminal device is not permitted to access a network device, the method further includes: that the terminal device, within the execution time of the first timer, the physical downlink control channel corresponding to the multicast control channel ( PDCCH ) When configuration information for the initial multicast service is obtained by monitoring, the terminal device receives the initial multicast service in RRC-disconnected mode, but restarts the access control procedure after the first timer expires without stopping the first timer. Here, the execution time of the first timer is the duration for which the terminal device must wait after being denied access to the network device before restarting the access control procedure.

[0015] In some implementations of the first embodiment, if a terminal device is not permitted to access a network device, the method further includes: if a group paging message contains second information, and the second information indicates that a network device will provide the first multicast service to a terminal device that is in disconnected mode, the terminal device terminates the access control procedure, or the terminal device skips the start of the first timer, or the terminal device stops the start of the access control procedure after the first timer has expired. Here, the execution time of the first timer is the duration for which the terminal device must wait after being denied access to the network device before restarting the access control procedure.

[0016] A second aspect provides a communication method. This method may be performed by network equipment or by components (such as chips or circuits) of network equipment. This is not limited herein. For ease of explanation, an example of this method being performed by network equipment is described below.

[0017] This method may include the following: a network device sends a group paging message to a terminal device, where the group paging message includes first information, which is used to call a terminal device group to receive the first multicast service, and the terminal device group includes terminal devices, where the network device sends second information to the terminal device, which is used to call the network device to control radio resources ( RRC ) Indicates whether to provide the initial multicast service to a group of terminal devices in disconnected mode.

[0018] In some implementations of the second aspect, the second information is carried in a group paging message, or the second information is carried over a multicast control channel.

[0019] For the effects corresponding to the second embodiment, please refer to the description of the effects in the first embodiment. Further details will not be provided in this specification.

[0020] A third aspect provides a communication method. This method may be performed by a terminal device or by a component (such as a chip or circuit) of the terminal device. This is not limited to the foregoing. For ease of explanation, an example of this method being performed by a terminal device is described below.

[0021] This method may include the following: namely, terminal equipment controlling wireless resources. ( RRC ) If in connection mode, the step of joining a multicast service. If the terminal device is in RRC connection mode, the step of receiving first information from the network device, the first information being multicast radio bearer ( MRB ) The steps include: 1) describing the configuration, where the MRB configuration is the MRB configuration used by the terminal device to receive multicast services in RRC-disconnected mode; and 2) the terminal device determining the MRB configuration based on the first information.

[0022] In the technical solution described above, the MRB configuration used to receive multicast services when the terminal device is deactivated into disconnected mode is specified. Therefore, the terminal device can determine the MRB configuration used to receive multicast services in disconnected mode early on, before being deactivated into disconnected mode, thereby facilitating the continuation of multicast service reception during the process of the terminal device being deactivated into disconnected mode.

[0023] In some implementations in the third aspect, the second information from the network device is received when the terminal device is in the RRC connected mode. Here, the second information indicates to the terminal device to receive the multicast service in the RRC idle mode. The terminal device transitions to the RRC idle mode. And when the terminal device is in the RRC idle mode, the multicast service is received by using the determined MRB configuration.

[0024] For example, the second information may be carried in an RRC release message, and the RRC release message indicates to the terminal device to transition to the RRC idle mode. Further, after the terminal device transitions to the idle mode, it may still receive the multicast service based on the second information. In this application, it can be understood that the reason for the terminal device to release the RRC connection is to receive the multicast service in the RRC idle mode.

[0025] In some implementations in the third aspect, the first information is used to operate the terminal device to obtain the MRB configuration, and the terminal device determining the MRB configuration based on the first information includes the following. That is, the terminal device monitors the physical downlink control channel corresponding to the multicast control channel ( PDCCH ) based on the first information. And the terminal device determines the MRB configuration carried on the multicast control channel.

[0026] In some implementations of the third aspect, the first information indicates to the terminal device that, when the terminal device is in RRC non-connected mode, it will receive multicast services by receiving multicast services in RRC connected mode using the MRB configuration used by the terminal device. The terminal device determining the MRB configuration based on the first information includes: that the terminal device determines, based on the first information, that the MRB configuration used by the terminal device to receive multicast services in RRC connected mode is an MRB configuration.

[0027] A fourth aspect provides a communication method. This method may be performed by network equipment or by components (such as chips or circuits) of network equipment. This is not limited to the foregoing. For ease of explanation, an example of this method being performed by network equipment is described below.

[0028] This method may include the following: the network device deciding that the terminal device will participate in the multicast service; and the network device controlling the wireless resources. ( RRC ) To transmit the first piece of information to a terminal device in connection mode. Here, the first piece of information is multicast radio bearer ( MRB ) The configuration is shown, and the MRB configuration is an MRB configuration used by terminal equipment to receive multicast services in RRC-disconnected mode.

[0029] In some implementations of the fourth aspect, the method further includes: the network device receives multicast service by transmitting second information to the terminal device, and fourth information indicating to the terminal device that it is transitioning to RRC disconnected mode.

[0030] In some implementations of the fourth aspect, the first information is used to activate terminal equipment to obtain the MRB configuration, and the method further includes: the network equipment transmits the MRB configuration to the terminal equipment, where the MRB configuration is carried in multicast control channel information.

[0031] In some implementations of the fourth aspect, the transmission of first information by a network device to a terminal device in RRC connection mode includes: the network device determining that the MRB configuration is the MRB configuration used by the terminal device to receive multicast services in RRC connection mode; and the network device transmitting first information to the terminal device in connection mode, where the first information indicates to the terminal device that, if the terminal device is in RRC non-connection mode, it will receive multicast services by receiving multicast services in RRC connection mode using the MRB configuration used by the terminal device.

[0032] In some implementations of the fourth aspect, the method further includes: a network device receiving first instruction information from a core network device, where the first instruction information indicates the priority of one or more terminal devices; and the network device determining, based on the first instruction information, which terminal devices need to be disconnected to receive multicast services.

[0033] For the effects corresponding to the fourth aspect, please refer to the description of the effects in the third aspect. Further details will not be provided in this specification.

[0034] According to a fifth aspect, a communication device is provided. The device is configured to perform a method provided in the first or second aspect. Specifically, the device may include units and / or modules, such as a processing unit and / or a communication unit, configured to perform a method in the first or second aspect and any possible implementation of the first or second aspect.

[0035] In one implementation, this device is a terminal device. When this device is a terminal device, the communication unit may be a transceiver or an input / output interface, and the processing unit may be at least one processor. Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0036] In another implementation, the device is a chip, chip system, or circuit used within a terminal device. If the device is a chip, chip system, or circuit used within a terminal device, the communication unit may be an input / output interface, interface circuit, output circuit, input circuit, pin, associated circuit, or similar on the chip, chip system, or circuit. The processing unit may be at least one processor, processing circuit, logic circuit, or similar. If the device is a chip, chip system, or circuit used within a terminal device, the device may be understood as the terminal device in the method of the first or second embodiment, and in any possible implementation of the first or second embodiment.

[0037] According to the sixth aspect, a communication device is provided. The device is configured to perform a method provided in the third or fourth aspect. Specifically, the device may include units and / or modules, such as a processing unit and / or a communication unit, configured to perform the method in the third or fourth aspect and any possible implementation of the third or fourth aspect.

[0038] In one implementation, this device is a network device. When this device is a network device, the communication unit may be a transceiver or an input / output interface, and the processing unit may be at least one processor. Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0039] In another implementation, the device is a chip, chip system, or circuit used within a network device. If the device is a chip, chip system, or circuit used within a network device, the communication unit may be an input / output interface, interface circuit, output circuit, input circuit, pin, associated circuit, or similar on the chip, chip system, or circuit. The processing unit may be at least one processor, processing circuit, logic circuit, or similar. If the device is a chip, chip system, or circuit used within a network device, the device may be understood as a terminal device in the method of the third or fourth embodiment and in any possible implementation of the third or fourth embodiment.

[0040] According to the seventh aspect, a communication device is provided, the device including, namely, at least one processor, wherein the at least one processor is coupled to at least one memory, the at least one memory is configured to store computer programs or instructions, and the at least one processor is configured to call computer programs or instructions from the at least one memory and execute the computer programs or instructions, thereby enabling the communication device to perform the methods of the first or second aspect and any possible implementations of the first or second aspect.

[0041] In one implementation, this device is a terminal device.

[0042] In another implementation, the device is a chip, chip system, or circuit used within a terminal device. If the device is a chip, chip system, or circuit used within a terminal device, then the terminal device may be understood to be the device in the method of the first or second embodiment, and in any possible implementation of the first or second embodiment.

[0043] According to the eighth aspect, a communication device is provided, the device including at least one processor, wherein the at least one processor is coupled to at least one memory, the at least one memory is configured to store a computer program or instruction, and the at least one processor is configured to call a computer program or instruction from the at least one memory and execute the computer program or instruction, thereby enabling the communication device to perform the method of the third or fourth aspect and any possible implementation of the third or fourth aspect.

[0044] In one implementation, this device is a network device.

[0045] In another implementation, the device is a chip, chip system, or circuit used within a network device. If the device is a chip, chip system, or circuit used within a network device, then the terminal device in the method of the third or fourth embodiment, and in any possible implementation of the third or fourth embodiment, may be understood as the device.

[0046] According to the ninth aspect, the present application provides a processor configured to perform the method provided in the above-described aspects.

[0047] Unless otherwise specified, or unless the operation is inconsistent with the actual function or internal logic of the operation in the description to which it relates, operations such as the output and reception or input of the processor, or operations such as the transmission and reception performed by radio frequency circuits and antennas, may be understood as such. This is not limited to the present application.

[0048] According to the tenth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores program code to be executed by a device, and the program code is used to execute the methods of the first, second, third, or fourth aspect, and any possible implementation of the first, second, third, or fourth aspect.

[0049] According to the eleventh aspect, a computer program product including instructions is provided. When this computer program product is executed on a computer, the computer becomes capable of executing the methods in the first, second, third, or fourth aspect, and any possible implementations of the first, second, third, or fourth aspect.

[0050] According to the twelfth aspect, a chip is provided, which includes a processor and a communication interface. The processor reads instructions stored in memory via the communication interface and executes the methods of the first, second, third, or fourth aspect, and any possible implementation of the first, second, third, or fourth aspect.

[0051] Optionally, in one implementation, the chip further includes memory, which stores computer programs or instructions. The processor is configured to execute the computer programs or instructions stored in the memory. When the computer programs or instructions are executed, the processor is configured to execute the methods in the first, second, third, or fourth embodiment, and any possible implementations in the first, second, third, or fourth embodiment.

[0052] According to the thirteenth aspect, a communication system is provided. This communication system includes the communication devices shown in the seventh and eighth aspects. [Brief explanation of the drawing]

[0053] [Figure 1] This figure shows a communication system according to an embodiment of the present application. [Figure 2] This diagram shows the MBS service transmission process. [Figure 3] This diagram shows the multicast service transmission process. [Figure 4] This diagram shows a specific MCCH transmission mechanism. [Figure 5] This diagram shows the procedure for disabling an MBS session. [Figure 6] This diagram shows the procedure for activating an MBS session. [Figure 7] This diagram shows the procedure for canceling an MBS session. [Figure 8] This diagram shows the wireless access network protocol stack structure. [Figure 9] This is a diagram of the three MRB types. [Figure 10] This is a schematic flowchart illustrating the RRC connection settings. [Figure 11] This is a schematic flowchart illustrating the resumption of the RRC connection. [Figure 12] This is a schematic flowchart illustrating the communication method related to this application. [Figure 13]This is a schematic flowchart illustrating another communication method related to this application. [Figure 14] This is a schematic flowchart illustrating how terminal devices perform access control in the disconnected mode as described in this application. [Figure 15] This is another schematic flowchart illustrating how terminal devices perform access control in the disconnected mode as described in this application. [Figure 16] This is yet another schematic flowchart illustrating how terminal devices perform access control in the disconnected mode according to this application. [Figure 17] This is a block diagram of the communication device 1000 related to this application. [Figure 18] This figure shows the configuration of the communication device 10 according to this application. [Modes for carrying out the invention]

[0054] Referring to the attached drawings, the technical solutions of the embodiments of this application are described below.

[0055] The technical solutions in the embodiments of this application can be applied to various communication systems, such as wireless communications related to long-term evolution (LTE), 5th generation (5G), new radio (NR), Internet of Things (IoT), wireless fidelity (Wi-Fi), the 3rd generation partnership project (3GPP), or other wireless communications that may emerge in the future.

[0056] The technical solutions provided in this application may be further applied to machine-type communication (MTC), device-to-device (D2D) networks, machine-to-machine (M2M) networks, Internet of Things (IoT) networks, or other networks.

[0057] Figure 1 shows a communication system according to one embodiment of the present application. The communication system includes at least one network device, for example, the network device 110 shown in Figure 1. The communication system 100 may further include at least one terminal device, for example, the terminal device 120 and / or terminal device 130 shown in Figure 1. The network device 110 can communicate with the terminal devices 120 / 130 via a wireless link to exchange information. The network device and terminal devices may also be understood to be referred to as communication devices.

[0058] Network equipment is network-side equipment that has wireless transceiver functionality. Network equipment can be a device located within a radio access network (RAN) that provides wireless communication functionality to terminal equipment, and is called a RAN device. For example, network equipment may be a base station, an evolved NodeB (eNodeB), a next-generation NodeB (gNB) in a 5G mobile communication system, a successor evolved 3GPP base station, a transmission reception point (TRP), an access node in a Wi-Fi system, a radio relay node, or a radio backhaul node. In communication systems using various radio access technologies (RATs), the name of a device with base station functionality may differ. For example, a base station may be called an eNB or an eNodeB in an LTE system, and a gNB in ​​a 5G system or an NR system. The specific name of a base station is not limited in this application. Network equipment may include one or more transmission points at joint or non-joint sites. As another example, network equipment may include one or more central units (CUs), one or more distributed units (DUs), or one or more CUs and one or more DUs. For example, the functions of a CU may be implemented by one entity or various entities. For example, the functions of a CU may be further subdivided. In other words, the control plane and user plane are separated and implemented by various entities, which are control plane CU entities (i.e., CU-CP entities) and user plane CU entities (i.e., CU-UP entities), respectively. The CU-CP entities and CU-UP entities may be coupled to DUs to jointly complete the functions of access network equipment.For example, the CU is responsible for processing non-real-time protocols and services, and for implementing the functions of the radio resource control (RRC) layer and the packet data convergence protocol (PDCP) layer. The DU is responsible for processing physical layer protocols and real-time services, and for implementing the functions of the radio link control (RLC) layer, the media access control (MAC) layer, and the physical (PHY) layer. In this way, some functions of a radio access network device may be implemented by multiple network function entities. These network function entities may be network elements within a hardware device, software functions running on dedicated hardware, or virtual functions instantiated on a platform (e.g., a cloud platform). The network device may further include an active antenna unit (AAU). The AAU implements several physical layer processing functions and functions related to radio frequency processing and active antennas. Information in the RRC layer ultimately becomes information in the PHY layer, or is converted from information in the PHY layer. Therefore, in this architecture, higher-layer signaling, such as RRC layer signaling, may also be considered as a target for transmission by the DU, or by both the DU and AAU. Network equipment may be understood as a device that includes one or more of CU nodes, DU nodes, and AAU nodes. Furthermore, a CU may be classified as network equipment within an access network (RAN), or a CU may be classified as network equipment within a core network (CN). This is not limited to the present application.As another example, in vehicle-to-everything (V2X) technology, access network equipment may be roadside units (RSUs). Multiple access network devices in a communication system may be base stations of the same type or of different types. Base stations may communicate with terminal equipment or communicate with terminal equipment via relay stations. In embodiments of this application, the device configured to implement the functions of network equipment may be network equipment, or a device capable of supporting network equipment in implementing its functions, such as a chip system or composite component, or a component capable of implementing the functions of access network equipment. The device may be installed within network equipment. In embodiments of this application, the chip system may include a chip, or it may include a chip and other separate components.

[0059] Terminal devices are user-side devices with wireless transceiver functionality and can be fixed devices, mobile devices, handheld devices (e.g., mobile phones), wearable devices, in-vehicle devices, or wireless devices (e.g., communication modules, modems, or chip systems) embedded in the aforementioned devices. Terminal devices are configured to connect people, things, mines, and similar entities and can be widely used in various scenarios, such as device-to-device (D2D) communication, V2X communication, machine-to-machine / machine-type communication (M2M / MTC) communication, the Internet of Things, virtual reality (VR), augmented reality (AR), industrial control, self-driving, remote medical care, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, unmanned aerial vehicles, and robots. For example, terminal equipment may be a handheld terminal in cellular communications, communication equipment in D2D communications, Internet of Things equipment in MTC, surveillance cameras in smart transport and smart cities, or communication equipment in unmanned aerial vehicles. Terminal equipment may also be called user equipment (UE), user terminal, user device, participant unit, participant station, terminal, access terminal, access station, UE station, remote station, mobile device, wireless communication device, or similar. In embodiments of this application, a device configured to implement the functions of terminal equipment may be terminal equipment, or a device that can support terminal equipment in implementing functions, such as a chip system or composite component, or a component that can implement the functions of terminal equipment. This device may be installed within terminal equipment. For simplicity of explanation, terminal equipment will be used as an example in this application.

[0060] To facilitate understanding of the technical solutions presented in this application, relevant concepts in the embodiments of this application will be briefly described.

[0061] 1. RRC mode

[0062] There are three modes for NR: RRC_IDLE mode, RRC_INACTIVE mode, and RRC_CONNECTED mode. The following is a brief explanation of these three RRC modes.

[0063] (1) RRC_CONNECTED (RRC connection mode): The RAN has the context of the UE, and the UE has a signaling connection with the RAN. The UE may receive system messages and messages delivered by the RAN that are used to control the UE to perform data transmission and handover and to notify the UE of relevant scheduling information, and the RAN may receive channel quality information fed back by the UE.

[0064] (2) RRC_INACTIVE (RRC inactive mode): The connection between the RAN and the core network is maintained, and resources are not allocated to the air interface, allowing services to be restored quickly and improving the experience of latency-sensitive applications. Furthermore, the power saving effect on the user terminal in inactive mode is almost equivalent to the power saving effect in hibernation mode. This extends the battery life of the mobile phone.

[0065] (3) RRC_IDLE (RRC idle mode): The RAN does not have the context of the UE, and the UE does not have a signaling connection with the RAN. In this mode, the UE can receive system messages and paging messages for cell selection and reselection. If the UE needs to establish a connection with the network for a specific purpose (such as service requests, location updates, and paging), the establishment of an RRC connection is triggered. After the RRC connection is established, the UE transitions to RRC connected mode.

[0066] It should be understood that the RRC disconnection mode in this application may be the RRC pause mode and / or the RRC inactive mode. The disconnection mode in this application may be replaced by the RRC pause mode and / or the RRC inactive mode.

[0067] Furthermore, UE connection management (CM) modes include idle mode (CM-IDLE), connection mode with RRC_INACTIVE, and connection mode (CM-CONNECTED). In CM-IDLE mode, it should be understood that the UE does not establish a signaling connection with the core network. For example, in RRC_IDLE mode, the UE moves between different cells through cell reselection. In CM-CONNECTED mode, the UE establishes a signaling connection with the core network, such as RRC_CONNECTED mode and RRC_INACTIVE mode.

[0068] 2. Multicast and broadcast service (MBS)

[0069] MBS is a service targeting multiple UEs, such as live broadcast services, scheduled program playback services, and batch software update services. From the perspective of inter-terminal management and control procedures, as well as transmission methods, MBS designed for NR can be classified into two types: broadcast services and multicast services. As shown in Figure 2, MBS is transmitted from a data server. First, the data server transmits the MBS data to core network equipment, then the core network equipment transmits the MBS data to base stations, and finally, the base stations transmit the MBS data to at least one UE receiving the MBS. When core network equipment transmits base MBS data to base stations, the MBS data is transmitted through public transmission channel MBS sessions, each MBS session may contain at least one MBS quality of service (QoS) flow. When base stations transmit MBS data to UEs, the MBS data is transmitted through MBS radio bearers. For a single MBS radio bearer, two transmission methods exist. Specifically, firstly, it is a point-to-multipoint (PTM) transmission method, and secondly, it is a point-to-point (PTP) transmission method.

[0070] 3. Multicast service

[0071] Multicast services are designed for services with high QoS requirements. Multicast services can provide the same QoS level as unicast services. In existing protocols, multicast services are wireless resource control ( RRC )Provided only to UEs in connected mode, access network equipment and core network equipment must maintain UE information corresponding to multicast service groups. Specifically, for multicast services, the core network must manage the joining and leaving of UEs. Control signaling between the core network and base stations relies on protocol data unit (PDU) sessions, and a new MBS QoS flow is introduced. Base stations support two methods of transmitting data to UEs, namely PTP and PTM, and dynamic switching between PTP and PTM, which is controlled by the base station. As shown in Figure 3, a base station can transmit the same multicast service to multiple UEs, i.e., perform PTM transmission, by using a group radio network temporary identifier (G-RNTI). Furthermore, the base station may assign a cell radio network temporary identifier (C-RNTI) corresponding to each UE, where the C-RNTI is used to perform PTP transmission as needed. Multicast services further support the disabling or enabling of MBS sessions caused by the core network. The UE does not recognize service mode.

[0072] 4. Broadcast Service

[0073] Broadcast services are designed for services with low QoS requirements. Broadcast services support UEs in any RRC mode. The core network and base stations do not need to maintain a group of UEs receiving the relevant broadcast service. When a broadcast service is available, UEs autonomously receive it based on their configuration information. Similar to multicast services, broadcast services are designed for downlink (downlink, DL) only. Unlike multicast services, broadcast services support only the PTM transmission scheme. For UEs, the configuration for receiving broadcast services is completely independent of the configuration for receiving multicast services.

[0074] 5. Multicast control channel and multicast traffic channel

[0075] Two logical channels, namely multicast control channels ( Firewall control channel (MCCH) and multicast traffic channel ( FirewallA traffic channel (MTCH) is introduced into the broadcast technology of NR MBS. The MCCH is used to transmit control information, and it periodically transmits control information. MBS broadcast configuration information is carried over the MCCH, and MBS broadcast configuration information is the configuration information of the MTCH. For example, the MTCH configuration information includes the configuration required to receive broadcast services, such as the G-RNTI corresponding to the MTCH and the temporary multicast group identifier (TMGI). The MTCH carries user data for broadcast services. The MTCH is scheduled through the MCCH. An MTCH is configured per G-RNTI, i.e., per MBS. A base station can simultaneously schedule service data to multiple UEs through the G-RNTI, and each G-RNTI can be associated with at least one broadcast service.

[0076] It should be understood that in various communication systems, the channels described above may correspond to various names. For example, in a fourth-generation (4G) communication system, a multicast control channel may be a single-cell multicast traffic control channel (SC-MCCH). As another example, in a 5G communication system, a multicast control channel may be an MC-MCCH. In future technological development processes, channels having similar functions to those of a multicast traffic control channel may have different names, or channels with the same functions may have different names in various communication environments, communication scenarios, or communication technologies. However, different names for channels with similar or the same functions in various systems do not constitute a limitation on channel content and functionality. In this application, a multicast control channel may be used to transmit control information, and a multicast traffic channel may be used to transmit user data.

[0077] 6. Multicast Control Channel Change Notification (MCCH change notification)

[0078] As shown in Figure 4, the MCCH is transmitted repeatedly during each modification period (MP), and the repetition period (RP) is included in the figure. The content of the MCCH is the same in one MP. When the MCCH changes in different MPs, the network device transmits a physical downlink control channel (PDCCH), which contains an MCCH change notification. When the UE detects a field on the PDCCH corresponding to the MCCH change notification, for example, two bits, it considers that the content of the MCCH has changed, and the UE reacquires the MCCH. The first bit in the MCCH change notification indicates that the reason for changing the MCCH is session start, and the second bit indicates that the reason for changing the MCCH is session change, session termination, or update of the adjacent cell list. When acquiring the MCCH, the UE needs to detect the scrambled PDCCH using MCCH-RNTI to obtain the MCCH scheduling information.

[0079] 7. Multicast Session Identifier (MBS session ID)

[0080] The MBS session ID identifies multicast and broadcast services. For example, one multicast session identifier may be associated with one multicast and broadcast service. For instance, the multicast session identifier could be a TMGI.

[0081] 8. Procedures for disabling, enabling, and deactivating MBS sessions

[0082] The MBS session invalidation procedure is applicable to multicast. The MBS session invalidation procedure is activated by a multicast session management function (MB-SMF) network element. If there is no downlink data to transmit within a certain time period, the MB-SMF receives a notification from a user plane function (MB-UPF) network element, or directly receives a request forwarded by an application layer function (AF) network element or a network exposure function (NEF). The MBS session invalidation procedure is then used to invalidate the MBS data resources of the 5G access network (NG-RAN) node. As shown in Figure 5, when activated by the 5G core network (5GC), for example, the access and mobility management function (AMF) network element in Figure 5 sends a multicast session invalidation request to the RAN, which then releases the multicast session's radio resources and stops transmitting multicast session data to the UE. The multicast session mode changes from active to inactive. The base station may or may not disconnect the UE's RRC connection, but the base station will not explicitly notify the UE of the MBS session being disabled.

[0083] The MBS session activation process is applicable only to multicast. The MBS session activation process is initiated by the MB-SMF. The MBS session activation procedure is initiated when the MB-SMF receives notification of MBS downlink data from the MB-UPF, or when the MB-SMF directly receives a request forwarded by the AF or NEF. The MBS session activation procedure is used to activate MBS data resources on NG-RAN nodes, such as radio resources, to establish a multicast session and to send multicast session data to the UE. Furthermore, UEs participating in the multicast session that are in CM-IDLE mode and CM-CONNECTED+RRC disabled mode, i.e., RRC unconnected mode, are invoked (paged). The activation procedure for these UEs can be initiated by an AF request or notification of data from the MB-UPF, and the multicast session mode changes from disabled mode to enabled mode. In Figure 6, the message used by the AMF to invoke a UE in CM-IDLE mode may be a group paging message (if the base station supports multicast) or a unicast paging message (if the base station does not support multicast and multicast service is provided in a unicast manner). When the AMF sends a multicast session activation request message to the RAN, the RAN's paging procedure may be activated.

[0084] The MBS deactivation procedure is initiated by the core network. If the CN decides to deactivate a multicast service or remove a UE from a multicast service, the procedure shown in Figure 7 may be performed. If the CN determines that there is a UE in CM-IDLE mode, as shown in Figure 7, the CN initiates paging to allow the UE to transition to connected mode. After the UE has transitioned to connected mode, the CN may initiate a PDU session change request to the RAN. The detailed message sent for paging may be a group paging message (if the base station supports multicast) or a unicast paging message (if the multicast service is provided in a unicast manner without the base station supporting multicast).

[0085] Unless otherwise specified in this application, it should be understood that the mode of an MBS may also be understood as the mode of an MBS session, and that deactivating an MBS may also be understood as deactivating an MBS session. In other words, unless otherwise specified in this application, "service" and "session" are interchangeable.

[0086] 9. Multicast Wireless Bearer ( Firewall Radio Bearer (MRB)

[0087] Network devices and terminal devices communicate with each other using a specific protocol stack structure. As shown in Figure 8, the user-plane protocol stack structure may include the RRC layer, service data adaptation protocol (SDAP) layer, PDCP layer, RLC layer, MAC layer, physical (PHY) layer, and similar layers. The physical layer is located at the lowest layer (layer 1), the MAC layer, RLC layer, PDCP layer, and SDAP layer belong to the second layer (layer 2), and the RRC layer belongs to the third layer (layer 3). For the user-plane protocol stack of MBS transmission, data is transmitted in the direction indicated by the arrows in Figure 8 (for MBS services, the transmission direction is from base station to UE). The data first arrives at the base station's SDAP layer, is mapped by the SDAP layer, and then transmitted to the corresponding PDCP entity. After processing by the base station's PDCP layer, the data is transmitted to the RLC layer and MAC layer. After corresponding processing, the data is transmitted from the physical layer and transmitted to the UE side through the air interface. Next, each protocol layer on the UE side sequentially executes the corresponding processing on the data packet in the reverse order of processing at the base station. At both the base station and the UE side, the processing performed on the data packet by each layer is sometimes collectively referred to as a radio bearer (RB). Each part of the data within the radio bearer needs to be processed by the corresponding layer, and each layer has a corresponding functional entity that performs the corresponding function. Each radio bearer configuration includes one PDCP entity, and each radio bearer configuration is associated with at least one RLC entity, and each RLC entity corresponds to one logical channel.

[0088] It should be understood that the protocol stack structure described in Figure 8 is merely an example and does not constitute a limitation. The number of layers may be fewer or more, the functions of some layers may be integrated into one of the layers, or structural modifications may be made. This is not limited to this application.

[0089] For MBS, user plane data is carried by MRBs. Specifically, MRBs include three types: PTP-only MRBs, PTM-only MRBs, and split MRBs. Here, split MRBs include PTP MRBs and PTM MRBs. As shown in Figure 9, a PTP-only MRB is associated with one PTP RLC entity, a PTM-only MRB is associated with one PTM RLC entity, and a split MRB is associated with one PTM RLC entity and one PTP RLC entity. The PTM RLC is the same for multiple UEs, and multiple UEs monitor the PDCCH by using the same G-RNTI. The PTP RLC is independent for each UE, and each UE monitors the PDCCH by using its own C-RNTI.

[0090] It should be understood that a single MBS session can correspond to one or more MRBs, meaning that a single service can correspond to one or more MRBs.

[0091] Furthermore, it should be understood that while one MRB corresponds to only one G-RNTI, one G-RNTI can correspond to multiple MRBs, and the multiple MRBs corresponding to one G-RNTI may or may not be MRBs for the same service.

[0092] 10. Access Control

[0093] Access control is a solution for controlling network congestion on the network side. In possible scenarios, when the network load is heavy, terminal devices must perform access control to determine whether they are permitted to perform access before initiating RRC connection control. In this way, some terminal devices may be prohibited from initiating RRC connection control, thereby limiting the network load. Optionally, terminal devices may be prohibited from initiating RRC connection control access within a timer. RRC connection control includes an RRC connection establishment procedure (specific procedures are shown in Figure 10) or an RRC connection reactivation procedure (specific procedures are shown in Figure 11).

[0094] Unified Access Control (UAC) is a common access control method in 5G and LTE systems. The random mechanism of UAC can isolate access opportunities for UEs (User Entities). In 5G systems, UEs can determine whether or not their access is prohibited according to UAC parameters. The steps of UAC are briefly described below.

[0095] Step 1: The UE receives UAC parameters broadcast by network devices through the system information block (SIB) 1.

[0096] Step 2: When the UE starts a service, the UE's non-access stratum (NAS) determines an access category (AC) based on the service type of the service, so that the UE's RRC stratum can make access decisions.

[0097] Step 3: Based on the AC, the UE determines whether or not access to the UE is prohibited.

[0098] If the value of AC is 0, it means that the UE is allowed to perform access, and the RRC connection control procedure is performed. If the value of AC is not equal to 0, it means that the UE is denied access, and step 4 is performed.

[0099] Step 4: Based on the AC, the UE determines a set of barring parameters in the UAC parameters that correspond to the AC (referred to herein as parameter #1). Here, parameter #1 includes barring for access identity, barring factor, and barring time. The barring factor can be understood as the percentage of time the terminal device is permitted to perform access.

[0100] Step 5: The UE determines an access identity (AI) based on the UE's configuration. If the bit corresponding to the AI ​​determined by the UE for the barring for access identity in parameter #1 is 0, it means the UE is permitted to perform access. If the bit corresponding to the AI ​​determined by the UE for the barring for access identity in parameter #1 is not 0, it means the UE's access is denied, and access control decisions continue to be made based on the barring factor and barring time in parameter #1.

[0101] The two parameters are used as follows: The UE randomly selects a value between [0,1]. If the random value is less than the prohibition coefficient (e.g., the prohibition coefficient is 50%), it means that the UE is allowed to perform the access. If the random value is greater than or equal to the prohibition coefficient (e.g., the prohibition coefficient is 50%), the UE's access is prohibited. If the UE's access is prohibited, the UE continues to determine duration #1 based on the prohibition time (e.g., the prohibition time is 128 seconds) and starts the timer. The timer runs for duration #1. The terminal device can only restart the UAC access determination after the timer has expired. For example, the timer may be T390 or T302. T390 is a timer that is started when an access attempt is prohibited during an access prohibition check for an access category. T302 is a timer that is started when the UE receives an RRC connection denial, or after receiving an RRC connection denial within a certain duration.

[0102] It should be understood that the procedures described above are merely a brief explanation of some implementation steps in a UAC procedure. No specific UAC procedure constitutes a limitation to this application, and other ACs not mentioned, or special designs, may exist.

[0103] When network congestion occurs, network equipment can disconnect a UE receiving multicast services from RRC connected mode (referred to in this application as "connected mode") to RRC disconnected mode (referred to in this application as "disconnected mode"), thereby allowing the UE to receive multicast services in disconnected mode. However, currently, the MRB processing for UEs disconnected from connected mode to disconnected mode when a UE receives multicast services in disconnected mode is not specified, and it is currently unclear which UEs can be disconnected to disconnected mode to receive multicast services.

[0104] From this perspective, this application provides a method for effectively solving the technical problems described above. The method provided in this application will be described in detail below.

[0105] Figure 12 is a schematic flowchart illustrating the communication method according to this application. This method may include the following steps.

[0106] S1201: The terminal device participates in the multicast service in connection mode. Accordingly, the network device determines that the terminal device is participating in the multicast service.

[0107] It should be understood that when a terminal device participates in a multicast service, it can be understood that the terminal device can receive multicast service data when network devices transmit multicast services.

[0108] Furthermore, it should be understood that even if a terminal device participates in a multicast service in connection mode, if the network equipment does not transmit any multicast service data at all, the terminal device will not receive the multicast service data.

[0109] Therefore, network devices may optionally send multicast services to terminal devices in connected mode. In response, terminal devices in connected mode receive multicast services from network devices.

[0110] S1202: The network device transmits first information to a terminal device in connected mode. Here, first information indicates the MRB configuration, which is the MRB configuration used by the terminal device to receive multicast services in disconnected mode. Accordingly, the terminal device in connected mode receives first information from the network device.

[0111] If the network equipment determines that a terminal device optionally participates in multiple multicast services, the first information may indicate some or all of the MRB configurations for some or all of the multiple multicast services. For example, if the network equipment determines in S1201 that the terminal device participates in multicast service #1, multicast service #2, and multicast service #3, the first instruction in S1202 may instruct the terminal device to receive some or all of the MRB configurations for multicast services in multicast service set #1 in disconnected mode. Multicast service set #1 includes at least one of multicast service #1, multicast service #2, and multicast service #3.

[0112] To facilitate explanation, in S1202, when a terminal device receives services within multicast service set #1 in disconnected mode, some or all of the required MRB configuration will be described below using an example shown in the first information.

[0113] It should be understood that the terminal device that receives the first information may then be disconnected to disconnected mode and need to receive multicast services, and is determined by the network device. Therefore, optionally, before S1202, the method further includes the following: namely, the network device determines at least one terminal device that needs to be disconnected to disconnected mode and need to receive multicast services. For example, the network device may determine which terminal device needs to disconnect the RRC connection in the following manner.

[0114] Method 1: The network device determines which terminal devices need to disconnect the RRC connection based on the type of multicast service received by the terminal device. For example, the network device determines that terminal devices that receive only multicast services are terminal devices that need to disconnect the RRC connection, or the network device determines that terminal devices that receive only multicast services and for which the network device provides multicast services when the terminal device is in disconnected mode are terminal devices that need to disconnect the RRC connection.

[0115] Method 2: Network devices determine which terminal devices need to disconnect from the RRC connection based on priority information of terminal devices from the core network. As can be seen from the explanation above, the core network needs to manage terminal devices participating in multicast services. Therefore, the core network may provide network devices with priority information of terminal devices.

[0116] In possible implementations, terminal device priority information can be indicated by using a value. Optionally, a higher value indicates a higher priority terminal device (i.e., a more important terminal device), or a lower value indicates a less important terminal device. Optionally, the terminal device priority can be one of several positive integers, such as 1, 2, and 3. Optionally, the priority information can indicate the importance of the terminal device. For example, a priority of 1 indicates that the terminal device is important. Or, a priority of 2 or less indicates that the terminal device is important. Or, a priority of 2 or greater indicates that the terminal device is important. In this implementation, based on the terminal device priority information, network devices may determine that important terminal devices should remain in connected mode, and that some less important terminal devices should disconnect from the RRC connection.

[0117] In other possible implementations, terminal device priority information may be indicated through fields or information elements with enumeration values ​​{important, unimportant}, {priority, nonpriority}, or {yes, no}. For example, terminal device priority may be indicated through the enumeration value {important}, indicating that the terminal device is an important terminal device, and the network device will keep the terminal device in connected mode. Alternatively, terminal device priority may be indicated through the enumeration value {unimportant}, indicating that the terminal device is an unimportant terminal device. The network device will determine that the terminal device is a terminal device that can be disconnected.

[0118] In yet another possible implementation, terminal device priority information can be indicated through enumeration values ​​{Important}, {Priority}, or {Yes}. If an enumeration value exists, it indicates that the corresponding terminal device is an important terminal device. If an enumeration value does not exist, it indicates that the corresponding terminal device is an unimportant terminal device.

[0119] As can be seen, in the implementation described above, the terminal devices that need to disconnect from the RRC connection are determined based on various requirements. For example, terminal devices with lower priority perform the RRC disconnection, while terminal devices with higher priority maintain the RRC connection mode, allowing for a more precise selection of terminal devices that need to be disconnected to disconnect mode to receive multicast services.

[0120] S1203: The terminal device determines the MRB configuration based on the first information. This MRB configuration is part or all of the MRB configuration required by the terminal device to receive services in multicast service set #1 in disconnected mode.

[0121] For example, based on the various instruction methods in the first piece of information, there may be several ways in which the first piece of information indicates the MRB configuration and how the terminal equipment determines the MRB configuration.

[0122] Method 1:

[0123] The first piece of information is used to activate the terminal device to acquire the MRB configuration. Accordingly, the terminal device in connected mode monitors the PDCCH corresponding to the multicast control channel based on the first piece of information and acquires the MRB configuration contained within the multicast control channel in connected mode. Alternatively, the terminal device in connected mode starts monitoring the PDCCH corresponding to the multicast control channel based on the first piece of information and acquires a portion of the MRB configuration. During the process of acquiring the MRB configuration, the terminal device may transition to disconnected mode, and after transitioning to disconnected mode, the terminal device continues to acquire the remaining portion of the MRB configuration.

[0124] The MRB configuration in Method 1 can be understood as the entirety of the MRB configuration required by the terminal device to receive services in multicast service set #1 in disconnected mode.

[0125] For example, a multicast control channel may be a multicast control channel for multicast or a multicast control channel for multiplexed broadcast. This is not particularly limited in this application. In this embodiment of this application, MCCH represents a multicast control channel, but it should be understood that MCCH does not constitute any limitation on the content and functionality of the channel. This application does not exclude the possibility of naming a multicast control channel by using a different name. For example, a multicast control channel for multicast may continue to use the name MCCH used for a broadcast multicast control channel, or it may use a different name.

[0126] For example, the first piece of information may be a MAC control element (CE) or downlink control information (DCI). For example, if the first piece of information is a MAC CE, the MAC CE may be scrambled by using the C-RNTI of the terminal device or by using the G-RNTI of a service in multicast service set #1 monitored by a terminal device in connected mode.

[0127] In one implementation, after determining the MRB configuration, the terminal device may, based on the MRB configuration, establish a new MRB to be used by the terminal device to receive services in multicast service set #1 in connected mode and disconnected mode. After transitioning to disconnected mode, the terminal device may release or suspend the MRB previously used by the terminal device to receive services in multicast service set #1 in connected mode and reserve a newly established MRB to be used by the terminal device to receive services in multicast service set #1 in disconnected mode.

[0128] In another implementation, after determining the MRB configuration and transitioning to disconnected mode, the terminal device establishes a new MRB based on the MRB configuration to be used by the terminal device to receive services in multicast service set #1 in disconnected mode, and releases or suspends the MRB previously used by the terminal device to receive services in multicast service set #1 in connected mode.

[0129] It should be understood that the MRB used by terminal devices to receive services within multicast service set #1 in disconnected mode (referred to as "disconnected mode MRB" in Method 1) is established based on the MRB configuration used by terminal devices to receive services within multicast service set #1 in disconnected mode (referred to as "MRB configuration in disconnected mode" in Method 1). The MRB used by terminal devices to receive services within multicast service set #1 in connected mode (referred to as "connected mode MRB" in Method 1) is established based on the MRB configuration used by terminal devices to receive services within multicast service set #1 in connected mode (referred to as "MRB configuration in connected mode" in Method 1).

[0130] As can be seen, in the above-described method, the network device operates the terminal device to acquire the MRB configuration in disconnected mode in advance in connected mode through the first information. In this way, the terminal device in RRC connected mode can establish the MRB in disconnected mode in advance based on the MRB configuration in disconnected mode, thereby ensuring the continuity of multicast service reception by the terminal device when it is disconnected from connected mode to disconnected mode by using the established MRB in disconnected mode. Compared to the case where the terminal device starts acquiring the MRB configuration in disconnected mode after transitioning to disconnected mode, in this embodiment, after transitioning to disconnected mode, the terminal device may establish the MRB in disconnected mode by using the previously acquired MRB configuration in disconnected mode, or it may acquire a portion of the MRB configuration in advance before transitioning to disconnected mode. In this way, the time period of interruption in multicast service reception by the terminal device can be shortened and the continuity of multicast service can be improved.

[0131] Method 2:

[0132] The first piece of information indicates whether a terminal device in disconnected mode will receive services within multicast service set #1 by using the MRB configuration that the terminal device would use to receive services within multicast service set #1 in connected mode.

[0133] Optionally, the first piece of information indicates each MRB corresponding to each service within multicast service set #1. That is, the granularity of the first piece of information is each individual MRB. For example, the first piece of information indicates that MRB #11 for service #1 in multicast service set #1 is still available, and MRB #12 for service #1 in multicast service set #1 is still unavailable. Furthermore, the first piece of information indicates that MRB #21 for service #2 in multicast service set #1 is still unavailable, and MRB #22 for service #2 in multicast service set #1 is still unavailable. Further details are not described herein.

[0134] Optionally, the first piece of information indicates all MRBs for each service within multicast service set #1. That is, the granularity of the first piece of information is each individual service. For example, the first piece of information indicates that all MRBs for service #1 within multicast service set #1 remain available. Another example is indicating that all MRBs for service #2 within multicast service set #1 remain unavailable. Further details are not provided herein.

[0135] Optionally, the first piece of information indicates all MRBs for all services in multicast service set #1. That is, the granularity of the first piece of information is each UE. For example, the first piece of information indicates that all MRBs for all services in multicast service set #1 are still available. As another example, the first piece of information indicates that all MRBs for all services in multicast service set #1 are still unavailable.

[0136] [1] If the first piece of information indicates that the MRB configuration used by the terminal device can still be used to receive services in multicast service set #1 in connection mode, the terminal device will continue to use all or part of the MRB configuration used by the terminal device to receive service #1 in connection mode.

[0137] It should be understood that, regardless of whether the primary information directive is at the level of each MRB, each service, or each UE, further processing needs to be performed for each type of MRB. To facilitate understanding, the following further details will be illustrated using an example where multicast service set #1 contains service #1, and the MRB corresponding to service #1 contains MRB #1. For example, in case [1], the terminal device may perform at least one of the following actions:

[0138] (1) If the MRB#1 used by the terminal device to receive service #1 in connected mode is a PTP-only MRB, the PTP-only MRB is suspended. In this case, the terminal device may monitor the PDCCH corresponding to the MCCH in connected or disconnected mode to obtain (determine) the MRB configuration used by the terminal device to receive service #1 in disconnected mode. Based on the MRB configuration, the terminal device establishes a new MRB to receive service #1 in disconnected mode.

[0139] It should be understood that when terminal equipment is in disconnected mode, the MRB configuration used to receive service #1 is carried over the MCCH.

[0140] Furthermore, if the granularity of the first information is each MRB, and MRB#1 used to receive service #1 in connection mode is a PTP-only MRB, then the first information may also indicate that MRB#1 cannot be used any longer.

[0141] (2) If the MRB#1 used to receive service #1 when the terminal device is in connected mode is a PTM-dedicated MRB, the PTM-dedicated MRB will not be suspended, and the terminal device will continue to receive service #1 in disconnected mode by using the PTM-dedicated MRB.

[0142] (3) If the MRB#1 used to receive service #1 when the terminal device is in connected mode is a split MRB, the terminal device will continue to receive service #1 in disconnected mode by using the PTM MRB within the split MRB. Optionally, the PTP MRB within the split MRB will be suspended.

[0143] [2] If the first piece of information indicates that the MRB configuration used by the terminal device is not used to receive services in multicast service set #1 in connected mode, the terminal device suspends all MRBs used by the terminal device to receive services in multicast service set #1 in connected mode. The terminal device obtains the MRB configuration used to receive services in multicast service set #1 through monitoring and establishes a new MRB based on the MRB configuration obtained to receive services in multicast service set #1 in disconnected mode.

[0144] [3] If the first information is unavailable, i.e., does not indicate whether the network equipment can continue to use the MRB configuration in connected mode, the terminal equipment determines whether it can use the MRB in connected mode. If it can use the MRB in connected mode, the terminal equipment receives the services in multicast service set #1 in disconnected mode. If it cannot use the MRB in connected mode (for example, the MRB in connected mode is a PTP-only MRB), the terminal equipment pauses the MRB that cannot be used and establishes a new MRB in disconnected mode to receive the services in multicast service set #1.

[0145] To facilitate understanding, we will use an example where multicast service set #1 contains service #1 and the MRB for service #1 contains MRB #1 to illustrate this in more detail below. For example, in case [3], the terminal equipment may perform the following actions:

[0146] (1) If the MRB used by the terminal device to receive service #1 in connected mode is a PTP-only MRB, the PTP-only MRB is suspended. In this case, the terminal device may monitor the PDCCH corresponding to the MCCH in connected mode and obtain the MRB configuration contained within the MCCH that the terminal device will use to receive service #1 in disconnected mode. Based on the MRB configuration, the terminal device establishes a new MRB to receive service #1 in disconnected mode.

[0147] (2) If the MRB used by the terminal device to receive service #1 in connected mode is a PTM-dedicated MRB, the terminal device may obtain the MRB configuration used by the terminal device to receive service #1 in disconnected mode through monitoring in connected or disconnected mode. The terminal device checks whether it needs to update the MRB used by the terminal device to receive service #1 in connected mode. If it does need to update the MRB used by the terminal device to receive service #1 in connected mode, the terminal device establishes a new MRB based on the MRB configuration obtained through monitoring and receives service #1 in disconnected mode. If it does not need to update the MRB used by the terminal device to receive service #1 in connected mode, the terminal device continues to receive service #1 in disconnected mode by using the PTM-dedicated MRB.

[0148] (3) If the MRB used by the terminal device to receive service #1 in connected mode is a split MRB, the terminal device may, through monitoring, obtain the MRB configuration used to receive service #1 in connected mode and check whether it is necessary to update the PTM MRB in the split MRB. If it is necessary to update the PTM MRB in the split MRB, the terminal device establishes a new PTM MRB based on the MRB configuration obtained through monitoring. This new PTM MRB is used to receive service #1 in disconnected mode. If it is not necessary to update the PTM MRB in the split MRB, the terminal device continues to receive service #1 in disconnected mode by using the PTM MRB in the split MRB and optionally suspends the PTM MRB in the split MRB.

[0149] As can be seen, in the above-described method, the terminal device can determine in advance, through the first information, whether the MRB configuration in disconnected mode is the same as the MRB configuration in connected mode. If the MRB configuration in disconnected mode is the same as the MRB configuration in connected mode, the terminal device does not need to establish a new MRB, reducing energy consumption of the terminal device and network equipment, and allowing the terminal device to start receiving services in disconnected mode sooner. If the MRB configuration in disconnected mode is different from the MRB configuration in connected mode, the terminal device can acquire the MRB configuration in disconnected mode in advance. In this way, when the terminal device establishes a new MRB in disconnected mode based on the MRB configuration in disconnected mode while in connected mode, the continuity of multicast service reception can be ensured when the terminal device is deactivated from connected mode to disconnected mode. Compared to the case where the terminal device starts acquiring the MRB configuration in disconnected mode after transitioning to disconnected mode, in this embodiment, it can be understood that after transitioning to disconnected mode, the terminal device establishes a new MRB in disconnected mode based on the MRB configuration in disconnected mode. In this way, terminal devices can reduce the duration of interruptions in multicast service reception and improve the continuity of multicast services.

[0150] Method 3:

[0151] Method 3 may be a combination of Method 1 and Method 2. The terminal device receives the first information in Method 1 and the first information in Method 2, and based on the first information in Method 1 and the first information in Method 2, the terminal device determines whether to continue using or reacquire all or part of the MRB configuration used by the terminal device to receive service #1 in connected mode. For example, the terminal device determines, based on the first information in Method 2, whether the MRB configuration in disconnected mode is the same as the MRB configuration in connected mode. If the MRB configuration in disconnected mode is the same as the MRB configuration in connected mode, after being deactivated into disconnected mode, the terminal device continues to receive services in multicast service set #1 by using the MRB in connected mode. If the MRB configuration in disconnected mode is different (completely different or partially different) from the MRB configuration in connected mode, the terminal device may establish a new disconnected mode MRB in connected mode based on the MRB configuration in disconnected mode indicated by the first information in Method 1. Furthermore, after transitioning to disconnected mode, the terminal device receives services within multicast service set #1 based on the newly established disconnected mode MRB. Alternatively, the terminal device may establish a new MRB in connected mode. The MRB corresponds to the difference between the MRB configuration in disconnected mode and the MRB configuration in connected mode, and the MRBs corresponding to the same MRB configuration in disconnected mode and in disconnected mode are reserved and remain unchanged. After transitioning to disconnected mode, the terminal device receives services within multicast service set #1 based on the newly established MRB and the reserved MRB.

[0152] As can be seen, the above-described method, compared to the case where the acquisition of the MRB configuration in disconnected mode is initiated after the terminal device has transitioned to disconnected mode, can shorten the duration of interruption in multicast service reception by the terminal device and improve the continuity of multicast service.

[0153] Method 4:

[0154] The first piece of information indicates which MRBs need to be reserved or paused in order for the terminal device to receive services within multicast service set #1 in connected mode.

[0155] Optionally, the first piece of information indicates the MBS session ID of the multicast service received by the terminal device in connection mode, which MBS session IDs need to be reserved or suspended. As can be seen from the above, one MBS session can correspond to one or more MRBs. Therefore, the need to reserve or suspend one MBS session implicitly indicates that multiple MRBs corresponding to that MBS session need to be reserved or suspended.

[0156] Optionally, the first piece of information indicates which G-RNTIs in the multicast service received by a terminal device in connection mode need to be reserved or paused. As can be seen from the above, one MRB corresponds to only one G-RNTI, but one G-RNTI can correspond to multiple MRBs. Therefore, the need to reserve or pause one G-RNTI implicitly indicates that one or more MRBs corresponding to that G-RNTI need to be reserved or paused.

[0157] Optionally, this method further includes the following: The terminal device receives second information from the network device in connected mode, where the second information instructs the terminal device to receive services in multicast service set #1 in disconnected mode. The terminal device transitions to disconnected mode based on an RRC release message, and in disconnected mode, the terminal device continues to receive services in multicast service set #1 based on the second information by using the MRB (or MRB configuration) determined in S1203.

[0158] Optionally, the first piece of information may be transmitted to the terminal device before the second piece of information, or the first and second pieces of information may be transmitted to the terminal device simultaneously.

[0159] Optionally, the second piece of information may be carried in an RRC deactivation message sent to the terminal device by the network device, which instructs the terminal device to switch to disconnected mode, and the second piece of information indicates that the reason the terminal device is deactivating the RRC connection is so that it can receive multicast services in disconnected mode.

[0160] In the embodiment described above, the MRB configuration used to receive multicast services is specified when the terminal device is deactivated into disconnected mode. Therefore, before being deactivated into disconnected mode, the terminal device can determine the MRB configuration used to receive multicast services in disconnected mode, thereby facilitating the continuity of multicast service reception during the process of the UE being deactivated into disconnected mode.

[0161] When network congestion is alleviated (completely alleviated or partially alleviated), multicast services are enabled, or multicast services need to be deactivated, network devices may, through paging messages, further invoke terminal devices that are being deactivated into disconnected mode in order to receive the multicast service and transition into connected mode. After receiving the paging message, terminal devices perform access control, such as UAC processing. If a terminal device is permitted to perform access, it initiates the RRC connection control procedure and transitions into RRC connected mode. However, for terminal devices receiving multicast services in RRC disconnected mode, after receiving the paging message, the AC corresponding to the paging service becomes equal to 0, so multiple terminal devices invoked by the paging message may directly invoke the RRC connection control procedure. In this case, a large number of terminal devices may access the network simultaneously, potentially causing network congestion.

[0162] From this perspective, this application provides an alternative method for effectively solving the technical problems described above. The method provided in this application will be described in detail below.

[0163] Figure 13 is a schematic flowchart illustrating another communication method according to this application. This method includes the following steps:

[0164] S1301: The network device sends a group paging message to the terminal device. In response, the terminal device receives the group paging message from the network device.

[0165] Optionally, a group paging message may contain a first piece of information, which is used to invoke a terminal device group to receive the first multicast service. Here, the terminal device group includes terminal devices that receive group paging messages.

[0166] It should be understood that the group of terminal devices summoned through the first piece of information are terminal devices participating in the initial multicast service and are in disconnected mode.

[0167] S1302: Based on the first and second pieces of information, the terminal device performs at least one of the following: namely, receiving the first multicast service in disconnected mode, or performing the RRC connection control procedure. The second piece of information indicates whether the network device will provide the first multicast service to the terminal device in disconnected mode.

[0168] It should be understood that when a network device provides the initial multicast service to a device in disconnected mode, the terminal device in disconnected mode can receive the initial multicast service simply by participating in the initial multicast service in connected mode. Therefore, the second piece of information can be understood to indicate whether or not the network device provides the initial multicast service to the called group of terminal devices in disconnected mode.

[0169] Optionally, the second information may be carried in a group paging message, or on a multicast control channel, or in a separate message. This is not limited to the present application. For example, both the first and second information may be carried in a group paging message, the first information may be the TMGI of the first multicast service, and the second information may be a 1-bit indicator. For example, 0 indicates that the network device provides the first multicast service to a terminal device in disconnected mode, 1 indicates that the network device does not provide the first multicast service to a terminal device in disconnected mode, and vice versa. As another example, the first information may be carried in a group paging message and the second information may be carried on a multicast control channel.

[0170] For example, a multicast control channel may be a multicast control channel for a multicast or a multicast control channel for a multiplexed broadcast. This is not particularly limited in this application. In this embodiment of this application, MCCH represents a multicast control channel, but it should be understood that MCCH does not constitute any limitation on the content and functionality of the channel. This application does not exclude the possibility of naming a multicast control channel by using a different name. For example, a multicast control channel for a multicast may continue to use the name MCCH used for a broadcast multicast control channel, or it may use a different name.

[0171] As can be seen from the above explanation, it should be understood that terminal equipment usually needs to perform an access control procedure first before executing the RRC connection control procedure. Several possible implementations of S1302 are provided below with reference to Figures 14, 15, and 16. For example, an example in which both the first and second pieces of information are carried in a group paging message is described below.

[0172] Figure 14 is a flowchart of the first implementation. In this implementation, the terminal device decides to receive the first multicast service in disconnected mode or to perform the RRC connection control procedure based on the second piece of information. This implementation may include the following steps in particular.

[0173] Step 1: Based on the second piece of information, the terminal device determines whether the network device will provide the initial multicast service to the terminal device in disconnected mode.

[0174] If the second piece of information indicates that a network device optionally provides the initial multicast service to a terminal device in disconnected mode, the terminal device will receive the initial multicast service in disconnected mode without performing access control procedures or subsequent RRC connection control procedures. If the second piece of information indicates that a network device provides the initial multicast service to a terminal device in disconnected mode, it should be understood that the terminal device may obtain the configuration information for the initial multicast service by monitoring the PDCCH corresponding to the MCCH, and the terminal device will receive the initial multicast service based on the obtained configuration information for the initial multicast service.

[0175] Optionally, if the second piece of information indicates that the network device does not provide the initial multicast service used to be received by terminal devices in disconnected mode, step 2 is performed.

[0176] Optionally, if a terminal device has a high priority or is a critical or specific terminal device designated by the core network, the terminal device may ignore the second information, skip the access control procedure, and directly perform the RRC connection control procedure; or the terminal device may ignore the second information and perform the access control procedure, the terminal device may be permitted to perform access, and the terminal device may continue to perform the RRC connection control procedure.

[0177] Step 2: The terminal device performs the access control procedure. Then, the terminal device performs Step 3.

[0178] For example, access control procedures can be User Account Control (UAC).

[0179] For example, the access control procedure can be further implemented in the following two ways: Method 1: The group paging message includes a set of prohibition parameters (which can be understood as a function, and whose meaning or value range is equivalent to the prohibition parameters in step 4 of conceptual explanation 10). In this way, compared to the UAC procedure, the terminal device does not need to determine the AC and can directly determine whether it is permitted to perform access based on the set of prohibition parameters provided in the group paging message (i.e., it can perform step 3). Method 2: The group paging message includes an index corresponding to the set of prohibition parameters. In this way, the terminal device does not need to determine the AC and can directly determine the corresponding set of prohibition parameters (which can be understood as a function, and whose meaning or value range is equivalent to the prohibition parameters in step 4 of conceptual explanation 10) based on the index, and then can determine whether it is permitted to perform access (i.e., it can perform step 3).

[0180] Step 3: The terminal device determines whether or not it is permitted to perform the access.

[0181] If the terminal device is optionally permitted to perform access, it will execute the RRC connection control procedure.

[0182] If access to the terminal device is optionally prohibited, the terminal device will perform step 4.

[0183] For example, if the access control procedure is UAC, in the step of determining whether access is permitted under UAC, the terminal device determines that the AC corresponding to the group paging service may be the same as the AC of an existing paging service, i.e., the AC is 0, or that the AC of the paging service may be extended, thereby determining that the AC is not equal to 0. If the AC is equal to 0, the terminal device is permitted to perform access and performs the RRC connection control procedure. If the AC is not equal to 0, the terminal device may not be permitted to perform access, or access may be prohibited.

[0184] For example, if the access control procedure is UAC, and AC is not equal to 0, but the network device expects that all terminal devices can access directly, i.e., that there are no terminal devices whose access is denied, then the deny parameter corresponding to AC in the UAC parameters may be removed from the SIB. In this way, if a terminal device cannot find a deny parameter corresponding to AC, the terminal device will access directly, thereby allowing all terminal devices to access directly. Alternatively, a 100% percentage may be introduced for the value of the deny coefficient of AC in the group paging service, thereby allowing all terminal devices to access directly. This method is an improvement based on the fact that the maximum value of the deny coefficient corresponding to AC in the existing UAC parameters is 95%, not 100%.

[0185] For example, if the access control procedure is implemented in Method 1 or Method 2 within Step 2, and the network device expects all terminal devices to be able to access directly, the network device cannot include prohibition parameters in the paging message. In this way, if a terminal device cannot find the prohibition parameter, it will access directly, and thus all terminal devices will be able to access directly.

[0186] For example, if a network device expects all terminal devices to be able to perform access directly, the network device may more directly indicate that the called group of terminal devices is permitted to perform access.

[0187] Step 4: The terminal device determines the first duration based on the prohibition time in the prohibition parameters, and then starts the first timer. The execution time of the first timer is the first duration.

[0188] The terminal device is prohibited from restarting the access control procedure before the first timer expires. After the first timer expires, the terminal device performs step 2, i.e., restarts the access control procedure.

[0189] Optionally, a terminal device may continue monitoring the MCCH's PDCCH within the execution time of the first timer to detect whether the network device will provide the initial multicast service to a terminal device in disconnected mode. It should be understood that the reason a terminal device continues monitoring when its access is prohibited is that, while the network device may not provide the initial multicast service to a terminal device in disconnected mode when sending the second piece of information, it may provide the initial multicast service to the terminal device in disconnected mode after sending the second piece of information. For example, when the network device performs paging, there are no terminal devices making access. In this case, the network device considers that no terminal devices made access and therefore does not provide the configuration information for the initial multicast service in disconnected mode. After a terminal device has successfully accessed the network, the network device may begin providing the configuration information for the initial multicast service in disconnected mode to reduce simultaneous access from a large number of terminal devices during the same time period. Therefore, if a terminal device's access is prohibited, the prohibited terminal device may obtain the configuration information for the initial multicast service through monitoring within the execution time of the first timer.

[0190] Optionally, monitoring the PDCCH of the MCCH within the execution time of the first timer can be understood as another way for the terminal device to obtain the second information, to detect whether the network device provides the initial multicast service to the terminal device in disconnected mode. Optionally, whether the terminal device needs to perform the monitoring procedure after its access is denied can be controlled through the first directive information. For example, the first directive information may indicate whether the current cell supports multicast service in disconnected mode, or whether the current cell has multicast service in disconnected mode, or whether the current cell provides transmission for service in disconnected mode. For example, if the first directive information indicates that the current cell does not support multicast service in disconnected mode, the terminal device does not need to perform the procedure described above. It should be understood that the current cell is the cell from which the terminal device receives group paging messages, and the current cell is the cell from which the network device provides services.

[0191] Optionally, the first instruction information may be included in the SIB message, or, if the terminal device is in connected mode, the first instruction information may be carried in dedicated signaling.

[0192] In this case, the terminal device may have several specific implementations depending on whether the configuration information for the first multicast service is obtained through monitoring within the execution time of the first timer. These implementations are applicable to other implementation procedures provided in S1302 of this application.

[0193] (1) If the configuration information for the first multicast service is obtained through monitoring within the execution time of the first timer, the terminal device receives the first multicast service in disconnected mode and stops attempting to access the network device. The terminal device stopping attempting to access the network device can also be understood as the terminal device directly terminating the access control procedure, or, after the first timer expires, the terminal device stopping the access control procedure, or the terminal device stopping the first timer and stopping the access control procedure.

[0194] It should be noted that currently, if the timer prohibiting access to a terminal device expires or stops, the restriction on access to the terminal device is lifted, meaning the terminal device is considered to be able to initiate the next access control procedure.

[0195] (2) If the configuration information for the first multicast service is obtained through monitoring within the execution time of the first timer, the terminal device in disconnected mode may receive the first multicast service, but without stopping the first timer, it will restart the access control procedure after the first timer expires.

[0196] (3) If the configuration information for the first multicast service is not obtained through monitoring within the execution time of the first timer, the terminal device restarts the access control procedure after the first timer expires.

[0197] Optionally, the terminal device may further monitor whether the MCCH contains wake-up information indicating that it will wake up the terminal device within the execution time of the first timer. Here, the wake-up information is used to enable the terminal device to transition from disconnected mode to connected mode. If wake-up information is obtained through monitoring, the terminal device stops the first timer and performs step 2. If wake-up information is not obtained through monitoring, the terminal device performs step 2 after the first timer has expired. In possible scenarios, the terminal device stops the first timer Execution time If a wait is placed within the MCCH for a second attempt at access, the current congestion on network equipment is alleviated, and some terminals that were denied access may attempt to access again. Therefore, network equipment may include wake-up information within the MCCH. In this way, terminal equipment can stop the first timer after receiving the wake-up information and attempt to access again. For example, wake-up information may be explicitly indicated through the MCCH, or it may be implicitly indicated through the TMGI of the first multicast service that is not present in the MCCH's TMGI list.

[0198] The first implementation shown in Figure 14 can be used in various scenarios, such as enabling multicast services, disabling multicast services, completely mitigating network congestion, or partially mitigating network congestion. For example, the following are possible implementations in which the first implementation can be used in various scenarios:

[0199] [1] Enable multicast service

[0200] It should be understood that the reason the called terminal device is deactivated to disconnected mode in S1301 is that the terminal device may receive multicast services or disable RRC in disconnected mode.

[0201] Optionally, in this scenario, if the second piece of information indicates that a network device provides multicast services to terminal devices in disconnected mode, the called terminal device group may, based on the instructions of the second piece of information, remain in disconnected mode and receive multicast services, regardless of whether the reason the terminal device is decoupled is that it needs to receive multicast services in disconnected mode or that RRC is disabled.

[0202] Optionally, in this scenario, if the second piece of information indicates that the network device does not provide multicast service to terminal devices in disconnected mode, the terminal device performs an access control procedure. In one implementation, the access control prohibition parameter may be set to allow all called terminal devices to access, thereby enabling all called terminal devices to access. For any possible specific configuration methods, see the description in step 3 in the embodiment in Figure 14. Further details are not described herein.

[0203] Optionally, in this scenario, if the reason the terminal device is disconnected is the RRC is disabled, the terminal device may either ignore the second piece of information and directly perform the RRC connection control procedure, or the terminal device may ignore the second piece of information and perform the access control procedure.

[0204] [2] Disconnecting multicast services

[0205] In a multicast service deactivation scenario, when the core network activates multicast service deactivation, network devices typically do not provide multicast services to terminal devices in disconnected mode. In this case, the called terminal device needs to return to connected mode as much as possible to receive multicast services. Therefore, network devices may instruct, through second information, that they do not provide multicast services to terminal devices in disconnected mode. In this case, the terminal device performs access control. In one implementation, the access control prohibition parameter may be set to allow all called terminal devices to access, in order to enable all called terminal devices to access. For specific configuration methods, please refer to the explanation in step 3 in the embodiment in Figure 14. Further details will not be explained further in this specification.

[0206] [3] Congestion relief (complete)

[0207] In a scenario where network congestion is completely relieved, the called terminal device needs to return to connected mode as much as possible in order to receive multicast services. Therefore, the network device may instruct, through second information, not to provide multicast services to terminal devices that are in disconnected mode. In this way, the terminal device performs access control. For example, to enable all called terminal devices to access, see the description in step 3 in the embodiment in Figure 14 for a specific configuration method. Further details are not described herein.

[0208] [4] Congestion relief (partial)

[0209] If a network device has several resources that can be used to provide multicast services in connected mode, some terminal devices in a called terminal device need to be controlled to access the network device. In this case, it should be understood that the network device may further provide multicast services to the called terminal device in disconnected mode, thereby allowing the terminal device to receive multicast services if access to the terminal device is prohibited. Furthermore, if the called terminal device determines that the network device is providing multicast services to the terminal device in disconnected mode after receiving a group paging message, it should be understood that the called terminal device will remain in disconnected mode. Therefore, in this scenario, the network device may / can provide further multicast services to the called terminal device in disconnected mode, but the network device also needs to indicate through second information that the network device will not provide multicast services to the terminal device in disconnected mode. Furthermore, the terminal device also supports checking whether the MCCH has multicast service configuration information within the duration of the timer that prohibits access to the terminal device. In this way, the terminal device in disconnected mode performs access control procedures. In this way, some terminal devices are permitted to perform access, while others are denied access. Terminal devices in disconnected mode that are denied access may acquire an MCCH and receive multicast services when access is denied.

[0210] Optionally, in this scenario, during the process of executing access control procedures, the terminal device receives multicast services without interruption and continuously monitors the PDCCH corresponding to the MCCH.

[0211] Optionally, terminal devices in disconnected mode that are unable to perform access may remain in disconnected mode, receive multicast services, or re-enable access control after the timer prohibiting access to the terminal device has expired.

[0212] Figure 15 is a flowchart of the second implementation. The difference from the procedure in Figure 14 is that in this implementation, the terminal device first performs an access control procedure after receiving a group paging message, and then, after the terminal device is not permitted to perform access, determines the subsequent steps based on the second piece of information. This implementation may include the following steps:

[0213] Step 1: The terminal device performs the access control procedure. Then, the terminal device performs Step 2.

[0214] For specific methods that can implement access control procedures, please refer to the explanation in Step 2 in Figure 14. Further details will not be provided in this specification.

[0215] Optionally, if a terminal device has high priority or is a critical or specific terminal device designated by the core network, the terminal device may skip the access control procedure and directly perform the RRC connection control procedure, or the terminal device may perform the access control procedure, the terminal device may be permitted to perform access, and the terminal device may continue to perform the RRC connection control procedure.

[0216] Step 2: The terminal device determines whether or not it is permitted to perform the access.

[0217] If the terminal device is optionally permitted to perform access, it will perform either the RRC connection restart procedure or the RRC connection establishment procedure.

[0218] If access to a terminal device is optionally prohibited, after the access is prohibited, the terminal device must determine a second duration based on the prohibition time of the access control prohibition parameter. Here, the second duration is the execution time of the second timer.

[0219] Optionally, in this implementation, the terminal device must first perform step 3 before determining whether or not to start the second timer. For example, if the access control procedure is UAC, in the step of determining whether access is permitted under UAC, the terminal device determines that the AC corresponding to the group paging service may be the same as the AC of an existing paging service, i.e., the AC is 0, or the AC of the paging service may be extended, thereby determining that the AC is not equal to 0. If the AC is equal to 0, the terminal device is permitted to perform access and performs the RRC connection control procedure. If the AC is not equal to 0, the terminal device may not be permitted to perform access, or access may be prohibited.

[0220] For example, if the access control procedure is User Account Control (UAC), and a network device wants to control the access so that none of the terminal devices are allowed to perform access, the network device can extend the AC for the group paging service so that the AC is not equal to 0, and then set the prohibition coefficient of the prohibition parameter in the group paging AC to 0. In this way, none of the terminal devices are allowed to perform access, and all terminal devices remain in disconnected mode to receive the initial multicast service.

[0221] For example, if a network device wants to control whether any terminal devices are allowed to perform access, the network device can instead directly instruct the called group of terminal devices to deny access.

[0222] Step 3: Based on the second piece of information, the terminal device determines whether the network device will provide the initial multicast service to the terminal device in disconnected mode.

[0223] Optionally, if the second piece of information indicates that the network device will provide the first multicast service to a terminal device in disconnected mode, the terminal device will either not start the second timer or terminate the access control procedure (i.e., stop attempting to access the network device), and the terminal device will monitor the PDCCH corresponding to the MCCH in disconnected mode to obtain the configuration information for the first multicast service. The terminal device will then receive the first multicast service in disconnected mode based on the multicast configuration information obtained for the first multicast service.

[0224] Optionally, if the second piece of information indicates that the network device will not provide the initial multicast service to terminal devices that are in disconnected mode, step 4 is performed.

[0225] Step 4: The terminal device starts a second timer. The terminal device is prohibited from restarting the access control procedure before the second timer expires. After the second timer expires, Step 1 is executed, and the terminal device restarts the access control procedure.

[0226] Optionally, a terminal device may monitor whether a network device provides the initial multicast service to a terminal device in disconnected mode within the execution time of the second timer. Figure 15 shows the actions that can be taken after the terminal device obtains, or fails to obtain, the configuration information for the initial multicast service within the second timer through monitoring. For a specific explanation, see the explanation in step 4 in Figure 14. Further details are not provided herein.

[0227] Optionally, in this implementation, the terminal device may also directly perform step 4 after step 2. Specifically, the terminal device starts the second timer regardless of whether the second information indicates that the first multicast service will be provided. If the second information indicates that the network device will provide the first multicast service to the terminal device, the terminal device in disconnected mode will receive the first multicast service within the execution period of the second timer and then perform the access control procedure again after the first timer expires. It should be understood that in this implementation, the order of step 3 does not need to constitute a limitation to this application. The terminal device may, after receiving the second information, determine based on the second information at any point in time whether the network device will provide the first multicast service to the terminal device in disconnected mode, for example, before step 1, based on the second information whether the network device will provide the first multicast service to the terminal device in disconnected mode.

[0228] For example, regarding the second implementation corresponding to Figure 15, the possible execution methods in various scenarios are as follows:

[0229] [1] Enable multicast service

[0230] Please understand that the reason the called terminal device is deactivated to disconnected mode in S1301 is that the terminal device may receive multicast services or disable them while in disconnected mode.

[0231] Optionally, in this scenario, the access control procedure is performed first. If the second piece of information indicates that access to a terminal device is denied and that a network device provides multicast services to terminal devices in disconnected mode, then both terminal devices that were disconnected due to the need to receive multicast services in disconnected mode and terminal devices that were disconnected due to inactivation may remain in disconnected mode based on the instructions of the second piece of information in order to receive multicast services.

[0232] Optionally, in this scenario, the access control procedure is performed first. If the second piece of information indicates that access to the terminal device is prohibited and that the network device will not provide multicast services to the terminal device in disconnected mode, the terminal device performs the access control procedure. In one implementation, the prohibit parameter may be set to allow access to all called terminal devices in order to enable access to all called terminal devices. For specific configuration methods, see the explanation in step 3 in Figure 14. Further details are not provided herein.

[0233] Optionally, in this scenario, if the reason for the terminal device being disconnected into disconnected mode is invalid, the terminal device may either ignore the second information and directly perform the RRC connection control procedure, or it may also be stipulated that the terminal device ignores the second information and perform the access control procedure.

[0234] [2] Disconnecting multicast services

[0235] In a multicast service deactivation scenario, it is necessary to ensure that terminal devices can access network devices as much as possible. Typically, when the core network activates multicast service deactivation, network devices will not provide multicast services to terminal devices in disconnected mode. Therefore, when multicast service is deactivated, the second piece of information may indicate that network devices will not provide multicast services to terminal devices in disconnected mode. In one implementation corresponding to Figure 15, the terminal device first performs access control, and if access is denied, it repeats the access control procedure based on the instruction content of the second piece of information. For example, to allow all terminal devices to access, the prohibition parameter may be set to allow all called terminal devices to access. For specific configuration methods, see the explanation in step 3 in Figure 14. Further details are not described herein.

[0236] [3] Congestion relief (complete)

[0237] If network congestion is completely relieved, terminal devices should return to connected mode as much as possible to receive multicast services. Therefore, in this scenario, all called terminal devices may be allowed to perform access during access control. For example, to enable all called terminal devices to access, please refer to the explanation in Step 3 corresponding to Figure 11 for specific configuration methods. Further details will not be explained again in this specification.

[0238] [4] Congestion relief (partial)

[0239] If a network device has several resources that can be used to provide multicast services in connected mode, some terminal devices in the called terminal device need to be controlled to access the network device. In this scenario, the desired effect can be achieved if the network device configures appropriate prohibition parameters for access control to the terminal devices. For example, by setting prohibition coefficients within the appropriate prohibition parameters, the percentage of terminal devices allowed to perform access can be controlled.

[0240] In this case, it should be understood that the network device further provides multicast services to the called terminal device in disconnected mode, thereby allowing the terminal device to receive multicast services if access to the terminal device is denied. In one implementation corresponding to Figure 15, when a terminal device first performs an access control procedure after receiving a group paging message, some terminal devices are permitted to perform access, and some terminal devices are denied access. Subsequently, terminal devices in disconnected mode whose access is denied may decide, based on the instructions of the second piece of information, to receive multicast services or to perform an RRC connection control procedure in disconnected mode.

[0241] Figure 16 is a flowchart of the third implementation. In this implementation, the network device does not transmit the second information; that is, the group paging message does not carry the second information, which implicitly indicates that the network device does not provide the initial multicast service to terminal devices in disconnected mode. This implementation may include the following steps:

[0242] Step 1: If the group paging message does not indicate whether the initial multicast service is provided to a terminal device in disconnected mode (i.e., if the second information is not present in the group paging message), the terminal device performs the access control procedure. The terminal device then performs Step 2.

[0243] Optionally, if a terminal device has a high priority or is a critical or specific terminal device designated by the core network, the terminal device may ignore the second information, skip the access control procedure, and directly perform the RRC connection control procedure; or the terminal device may ignore the second information and perform the access control procedure, the terminal device may be permitted to perform access, and the terminal device may continue to perform the RRC connection control procedure.

[0244] Step 2: The terminal device determines whether or not it is permitted to perform the access.

[0245] If the terminal device is optionally permitted to perform access, it will execute the RRC connection control procedure.

[0246] If access to the terminal device is optionally prohibited, the terminal device will perform step 3.

[0247] For example, if the access control procedure is User Account Control (UAC), and a network device wants to control the access so that none of the terminal devices are allowed to perform access, the network device can extend the AC for the group paging service so that the AC is not equal to 0, and then set the prohibition coefficient of the prohibition parameter in the group paging AC to 0. In this way, none of the terminal devices are allowed to perform access, and the terminal devices remain in disconnected mode and receive the initial multicast service.

[0248] For example, if the access control procedure is User Account Control (UAC), and a network device wants to control the access so that none of the terminal devices are allowed to perform access, the network device can extend the AC for the group paging service so that the AC is not equal to 0, and then set the prohibition coefficient of the prohibition parameter in the group paging AC to 0. In this way, none of the terminal devices are allowed to perform access, and the terminal devices remain in disconnected mode and receive the initial multicast service.

[0249] Similarly, for example, if the access control procedure is implemented in Method 1 or Method 2 in Step 2 of Figure 14, and the network device wants to control the situation so that none of the terminal devices are allowed to perform access, the network device may set the prohibition coefficient in the set of prohibition parameters included in the paging message to 0. In this way, none of the terminal devices are allowed to perform access, and the terminal devices remain in disconnected mode and receive the initial multicast service.

[0250] For example, if a network device wants to control whether any terminal devices are allowed to perform access, the network device can instead directly instruct the called group of terminal devices to deny access.

[0251] Step 3: The terminal device determines a third duration based on the prohibition time of the access control prohibition parameter, and then the terminal device starts a third timer. The execution time of the third timer is the third duration.

[0252] It should be understood that the terminal device is prohibited from restarting the access control procedure before the third timer expires. After the third timer expires, the terminal device performs step 1, i.e., restarts the access control procedure.

[0253] Optionally, a terminal device may monitor within a third duration whether a network device provides the initial multicast service to a terminal device in disconnected mode. Figure 16 shows the actions that a terminal device may take after obtaining, or failing to obtain, the configuration information for the initial multicast service within the third timer through monitoring. See the explanation in Figure 14 for a detailed explanation. Further details are not provided herein.

[0254] Regarding the third implementation shown in Figure 16, the possible execution methods in various scenarios are as follows:

[0255] [1] Enable multicast service

[0256] Optionally, in this scenario, the access control procedure is performed first. If access to a terminal device is denied, the terminal device decides to perform the access control procedure based on the case where the network device does not provide multicast service to terminal devices in disconnected mode. To allow all called terminal devices to access, the access control deny parameter can be set to allow all called terminal devices to access. For specific configuration methods, see the explanation in Step 3 in Figure 14. Further details are not provided herein.

[0257] Optionally, in this scenario, if the reason for the terminal device being disconnected to disconnected mode is invalid, the terminal device may also be required to ignore the content implicitly indicated by the group paging message and directly perform the RRC connection control procedure or access control procedure.

[0258] [2] Disconnecting multicast services

[0259] In a multicast service deactivation scenario, it is necessary to ensure that terminal devices can access network devices as much as possible. Normally, when the core network activates multicast service deactivation, network devices will not provide multicast services to terminal devices in disconnected mode. Therefore, if a group paging message is sent due to multicast service deactivation, the second piece of information within the group paging message may indicate that network devices will not provide multicast services to terminal devices in disconnected mode. In one implementation corresponding to Figure 16, the terminal device first performs access control, and if access control is denied, the terminal device monitors whether configuration information corresponding to multicast services exists. For example, to enable access for all terminal devices, see the explanation in step 3 in Figure 14 for specific configuration methods. Further details are not provided herein.

[0260] [3] Congestion relief (complete)

[0261] Once network congestion is completely relieved, terminal devices should return to connected mode as much as possible to receive multicast services. For example, in this scenario, to enable access for all terminal devices, please refer to the explanation in Step 3 in Figure 14 for specific configuration methods. Further details will not be explained again in this specification.

[0262] [4] Congestion relief (partial)

[0263] If a network device has several resources that can be used to provide multicast services in connected mode, some terminal devices within a called group of terminal devices need to be controlled to access the network device. In this scenario, the desired effect can be achieved if the network device configures appropriate access control prohibition parameters for the terminal devices.

[0264] In this case, it should be understood that the network device further provides multicast services to the called group of terminal devices in disconnected mode, thereby allowing the terminal devices to receive multicast services if their access is denied. In one implementation corresponding to Figure 16, when terminal devices perform UAC access determination after receiving a group paging message, some terminal devices are allowed to perform access and some are denied access. For example, a terminal device in disconnected mode whose access is denied may then decide, based on the PDCCH of the MCCH obtained through monitoring, whether to receive multicast services or to perform the RRC connection control procedure in disconnected mode.

[0265] According to this embodiment, the access control procedure is extended for terminal devices that transition to disconnected mode, so that some terminal devices can receive multicast services in disconnected mode, and some terminal devices can transition to connected mode to receive multicast services, thereby avoiding network congestion caused by simultaneous access from a large number of terminal devices and effectively managing terminal device access.

[0266] The above will be illustrated by using an example in which the first and second pieces of information are carried in a group paging message. The method described above will continue to be explained below by using an example in which the first and second pieces of information are carried on MCCH. This method includes the following steps.

[0267] S1801: The network device transmits the first and second pieces of information to the terminal device. Here, the first and second pieces of information are carried over the MCCH. In response, the terminal device receives the first and second pieces of information from the network device. The first piece of information is used to call a terminal device group to receive the first multicast service, the terminal device group includes the terminal device that receives the first piece of information, and the second piece of information indicates whether the network device will provide the first multicast service to a terminal device that is in disconnected mode.

[0268] Optionally, the first information on the MCCH may be understood as wake-up information in the first implementation of S1302.

[0269] S1802: Based on the first and second pieces of information, the terminal device performs at least one of the following: namely, the step of receiving the first multicast service in disconnected mode; or the step of performing the RRC connection control procedure.

[0270] For a detailed explanation of S1802, please refer to S1302. Further details will not be provided in this specification.

[0271] As can be seen from the above explanation, it should be understood that terminal equipment usually needs to perform access control procedures first before executing the RRC connection control procedure. Referring to Figures 14, 15, and 16, several possible implementations of S1802 are described below.

[0272] Figure 14 can also be considered a flowchart showing a first implementation of S1802. In this implementation, the terminal device decides, based on the second piece of information, to receive the first multicast service in disconnected mode, or to perform the RRC connection control procedure. This implementation may include, in particular, the following steps:

[0273] Step 1: Based on the second information, the terminal device determines whether the network device provides the first multicast service to the terminal device in the disconnected mode.

[0274] Step 2: The terminal device starts to execute the UAC access control procedure. Then, the terminal device executes Step 3.

[0275] Step 3: The terminal device determines whether the execution of access by the terminal device is permitted.

[0276] Optionally, when the execution of access by the terminal device is permitted, the terminal device executes the RRC connection control procedure.

[0277] Optionally, when the access by the terminal device is prohibited, the terminal device executes Step 4.

[0278] Step 4: Based on the prohibited time in the prohibition parameter, the terminal device determines the first duration, and then starts the first timer. The execution time of the first timer is the first duration. Before the first timer expires, the restart of the access control procedure is prohibited for the terminal device. After the first timer expires, the terminal device executes Step 2, that is, executes the access control procedure again.

[0279] For other descriptions of Steps 1 to 4 and the application of the implementation in various scenarios, refer to the description of FIG. 14 in S1302. Details are not described again in this specification.

[0280] FIG. 15 can also be regarded as the flowchart of the second implementation of S1802. The difference from the second implementation of S1802 is that in this implementation, after receiving the group paging message, the terminal device first executes the access control UAC procedure, and after the execution of access by the terminal device is not permitted, subsequent steps are determined based on the second information. This implementation may include the following steps.

[0281] Step 1: The terminal device begins executing the access control procedure. Then, the terminal device performs Step 2.

[0282] Step 2: The terminal device determines whether or not it is permitted to perform the access.

[0283] If the terminal device is optionally permitted to perform access, it will execute the RRC connection control procedure.

[0284] If access to the terminal device is optionally prohibited, after access is prohibited, the terminal device must determine a second duration based on the prohibition time specified in the prohibition parameter. Here, the second duration is the execution time of the second timer. It should be noted that in this implementation, the terminal device must first perform step 3 before deciding whether or not to start the second timer.

[0285] Step 3: Based on the second piece of information, the terminal device determines whether the network device will provide the initial multicast service to the terminal device in disconnected mode.

[0286] If the second piece of information indicates that a network device will provide the first multicast service to a terminal device in disconnected mode, the terminal device will, without starting the second timer, monitor the PDCCH corresponding to the MCCH in disconnected mode to obtain the configuration information for the first multicast service. The terminal device will then receive the first multicast service in disconnected mode based on the multicast configuration information obtained for the first multicast service.

[0287] Optionally, if the second piece of information indicates that the network device will not provide the initial multicast service to terminal devices in disconnected mode, step 4 is performed.

[0288] Step 4: The terminal device starts a second timer. The terminal device is prohibited from restarting the access control procedure before the second timer expires. After the second timer expires, Step 1 is executed, and the terminal device restarts the access control procedure.

[0289] For further explanations of Steps 1 through 4 and their application in various scenarios, please refer to the explanation in Figure 15 in S1302. Further details will not be provided in this specification.

[0290] Figure 16 can also be considered a flowchart showing a third implementation of S1802. In this implementation, the network device does not transmit the second information; that is, in this scheme, the MCCH does not carry the second information, which implicitly indicates that the network device does not provide the initial multicast service to terminal devices in disconnected mode. This implementation may include the following steps.

[0291] Step 1: If the MCCH does not indicate whether or not to provide the initial multicast service in disconnected mode, the terminal device begins executing the access control procedure. The terminal device then performs Step 2.

[0292] Step 2: The terminal device determines whether or not it is permitted to perform the access.

[0293] If the terminal device is optionally permitted to perform access, it will execute the RRC connection control procedure.

[0294] If access to the terminal device is optionally prohibited, the terminal device will perform step 3.

[0295] Step 3: The terminal device determines a third duration based on the prohibition time of the access control prohibition parameter, and then the terminal device starts a third timer. The execution time of the third timer is the third duration.

[0296] It should be understood that the terminal device is prohibited from restarting the access control procedure before the third timer expires. After the third timer expires, the terminal device executes Step 1, that is, executes the access control procedure again.

[0297] For other descriptions of Steps 1 to 3 and the application of the implementation in various scenarios, refer to the description of FIG. 16 in S1302. Details will not be described again in this specification.

[0298] Optionally, the first information and the second information may be further separately carried in any one of the group paging message, unicast paging message, MCCH message, system message, and message (MSG 2 / 4 / B) in the random access procedure, or may be jointly carried in one of the above-mentioned messages. This is not limited in this application. For specific implementation procedures, refer to the above description. Details will not be described again in this specification.

[0299] It should be understood that the sequence numbers of the above-mentioned processes do not mean the execution order. The execution order in the process needs to be determined based on the functions and internal logics of the processes, and there is no need to constitute any limitation to the implementation process of the embodiments of this application.

[0300] Furthermore, in various embodiments of this application, unless otherwise specified or there is no logical contradiction, the terms and / or descriptions in various embodiments are consistent and can be cross-referenced to each other. It should be understood that the technical features in various embodiments can be combined based on their internal logical relationships to form new embodiments.

[0301] Furthermore, it should be understood that in some of the embodiments described above, devices in existing network architectures are used primarily as examples for illustrative purposes. It should be understood that the specific form of the devices is not limited to the embodiments of this application. For example, all devices that can implement the same functionality in the future are applicable to the embodiments of this application.

[0302] In the embodiments of the methods described above, it can also be understood that the methods and operations implemented by a device (such as a terminal device or network device) may be implemented by a component of the device (such as a chip or circuit).

[0303] The above will be described in detail with reference to Figures 12 and 16, relating to the methods provided in the embodiments of this application. The methods described above will be described primarily in terms of the interaction between terminal equipment and network equipment. To implement the functions described above, the terminal equipment and network equipment may be understood to include corresponding hardware configurations and / or software modules for performing each function.

[0304] Those skilled in the art should recognize, in combination with the example units and algorithmic steps described in the embodiments disclosed herein, that this application may be implemented by hardware or by a combination of hardware and computer software. Whether the functions are performed by hardware or by hardware driven by computer software depends on the specific application and the design constraints of the technical solution. Those skilled in the art may use various methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0305] The communication device provided in the embodiments of this application will be described in detail below with reference to Figures 17 and 18. It should be understood that the description of the device embodiment corresponds to the description of the method embodiment. Therefore, for matters not described in detail, please refer to the method embodiment. For the sake of brevity, some matters will not be described again in this specification. In the embodiments of this application, based on the method example described above, a terminal device or network device may be divided into functional modules. For example, each functional module may be obtained through division based on each corresponding function, or two or more functions may be integrated into a single processing module. The integrated module may be implemented in hardware form or in the form of a software functional module. It should be noted that in the embodiments of this application, the module division is an example and is merely a logical functional division. Other division methods may be used in actual implementation. The following explanation is provided by using an example in which each functional module is obtained through division based on each corresponding function.

[0306] Figure 17 is a block diagram of the communication device 1000 according to this application.

[0307] In a possible design, the communication device 1000 includes a receiving unit 1100 and a processing unit 1200. The communication device 1000 may implement steps or procedures performed by the terminal equipment in the embodiments of the method described above, or corresponding steps or procedures. For example, the communication device 1000 may be a terminal device, or a chip or circuit within a terminal device. The receiving unit 1100 is configured to perform the receiving-related operations in the terminal equipment in the embodiments of the method described above, and the processing unit 1200 is configured to perform the processing-related operations in the terminal equipment in the embodiments of the method described above.

[0308] In possible implementations, the processing unit 1200 controls the wireless resources of terminal devices. ( RRC )When in connection mode, the receiving unit 1100 is configured to participate in multicast services and is configured to receive first information from network equipment when the terminal equipment is in RRC connection mode. Here, the first information is multicast radio bearer ( MRB ) The configuration is shown, and the MRB configuration is an MRB configuration used by terminal equipment to receive multicast services in RRC-disconnected mode. The processing unit 1200 is further configured to determine the MRB configuration based on the first information.

[0309] Optionally, the receiving unit 1100 is further configured to receive second information from the network device when the terminal device is in RRC connected mode, where the second information indicates to the terminal device that it will receive multicast services in RRC non-connected mode. The processing unit 1200 is further configured to enable the terminal device to transition to RRC non-connected mode. The receiving unit 1100 is then configured to receive multicast services by using an MRB configuration when the terminal device is in RRC non-connected mode.

[0310] Optionally, the first piece of information is used to activate terminal equipment to acquire the MRB configuration, and the processing unit 1200 is configured, in particular, to do the following based on the first piece of information: namely, the physical downlink control channel corresponding to the multicast control channel. ( PDCCH ) To monitor the following: and to determine the MRB configuration to be carried over the multicast control channel.

[0311] Optionally, the first piece of information instructs the terminal device to receive multicast services by using the MRB configuration used by the terminal device to receive multicast services in RRC connected mode, when the terminal device is in RRC non-connected mode. The processing unit 1200 is configured to do the following, in particular: In other words, based on the first piece of information, it is determined that the MRB configuration used by the receiving unit to receive multicast services in RRC connection mode is an MRB configuration.

[0312] In another possible implementation, the receiving unit 1100 is configured to receive a group paging message from a network device, where the group paging message includes first information, which is used to call a terminal device group to receive the first multicast service, and the terminal device group includes terminal devices. The processing unit 1200 is then configured to perform at least one of the following based on the first and second information: namely, the receiving unit performs radio resource control ( RRC ) To enable the reception of the initial multicast service in disconnected mode, or to have the processing unit perform the RRC connection control procedure. Here, the second piece of information indicates whether the network device will provide the initial multicast service to the group of terminal devices in RRC disconnected mode.

[0313] If the second piece of information indicates that the network device provides the first multicast service to a group of terminal devices that are in RRC-disconnected mode, the receiving unit 1100 receives the first multicast service if the terminal devices are in RRC-disconnected mode. Alternatively, the processing unit 1200 initiates an access control procedure based on the first piece of information, and if the second piece of information indicates that the network device provides the first multicast service to a group of terminal devices that are in RRC-disconnected mode without allowing the terminal devices to access the network device, the receiving unit 1100 receives the first multicast service if the terminal devices are in RRC-disconnected mode.

[0314] Optionally, the processing unit 1200 executes an RRC connection control procedure if the second piece of information indicates that the network device will not provide initial multicast service to a group of terminal devices in RRC non-connection mode. Alternatively, the processing unit 1200 initiates an access control procedure based on the first piece of information, and if the terminal devices are permitted to access the network device, the processing unit 1200 executes an RRC connection control procedure.

[0315] Optionally, the processing unit 1200 is further configured to monitor the physical downlink control channel PDCCH corresponding to the multicast control channel during the execution time of the first timer to obtain second information. Here, the duration of the first timer is the duration during which the terminal device must wait after it is no longer permitted to access the network device before it restarts the access control procedure. The processing unit 1200 is then further configured to stop the first timer and / or stop the start of the access control procedure. Alternatively, the group paging message contains second information, and the processing unit 1200 is further configured to skip starting the first timer and / or stop the start of the access control procedure.

[0316] Optionally, the communication device 1000 further includes a transmitting unit 1300. The transmitting unit 1300 and the receiving unit 1100 may be integrated into a single transceiver unit that has both receiving and transmitting functions. This is not limited herein.

[0317] In one implementation where the communication device 1000 is optionally a terminal device in the embodiment of the method, the transmitting unit 1300 may be a transmitter and the receiving unit 1100 may be a receiver. The receiver and transmitter may also be integrated into a single transceiver. The processing unit 1200 may be a processing unit.

[0318] The functions of the processing unit may be implemented by hardware, or by hardware running corresponding software. For example, the processing unit may include memory and a processor. The memory is configured to store computer programs, and the processor reads and executes the computer programs stored in the memory, enabling the communication device 1000 to perform operations and / or processes performed by terminal equipment in an embodiment of the method. Optionally, the processing unit may include only a processor, with the memory configured to store computer programs located outside the processing unit. The processor is connected to the memory via circuitry / wiring to read and execute the computer programs stored in the memory. As another example, the processing unit may be a chip or an integrated circuit.

[0319] In one implementation where the communication device 1000 is a chip or integrated circuit installed within a terminal device, the transmitting unit 1300 and the receiving unit 1100 may be a communication interface or an interface circuit. For example, the transmitting unit 1300 may be an output interface or output circuit, and the receiving unit 1100 may be an input interface or input circuit. The processing unit 1200 may be a processor or microprocessor integrated on a chip or integrated circuit. This is not limited herein.

[0320] In another possible design, the communication device 1000 includes a processing unit 1200 and a transmitting unit 1300. The communication device 1000 may implement steps or procedures performed by the network device in the embodiments of the method described above, or corresponding steps or procedures. For example, the communication device 1000 may be a network device, or a chip or circuit within a network device. The processing unit 1200 is configured to perform processing-related operations of the network device in the embodiments of the method described above. The transmitting unit 1300 is configured to perform receiving-related operations of the network device in the embodiments of the method described above.

[0321] In possible implementations, the processing unit 1200 is configured to determine whether terminal equipment will participate in the multicast service. The transmitting unit 1300 then controls the wireless resource. ( RRC ) It is configured to send first information to terminal devices in connection mode. Here, the first information is multicast radio bearer ( MRB ) The configuration is shown, and the MRB configuration is an MRB configuration used by terminal equipment to receive multicast services in RRC-disconnected mode.

[0322] Optionally, the transmitting unit 1300 is further configured to transmit a second piece of information to a terminal device, instructing the terminal device to switch to RRC-disconnected mode to receive multicast services.

[0323] Optionally, the processing unit 1200 is further configured to determine that the MRB configuration is the MRB configuration used by the terminal device to receive multicast services in RRC connection mode. The transmitting unit 1300 is further configured to transmit first information to the terminal device in connection mode, where the first information instructs the terminal device to receive multicast services by using the MRB configuration used by the terminal device to receive multicast services in RRC connection mode, when the terminal device is in RRC non-connection mode.

[0324] Optionally, the device 1000 further includes a receiving unit 1100. The receiving unit 1100 is configured to perform the receiving-related operations of the network equipment in the embodiments of the method described above. The receiver 1100 is configured to receive first instruction information from the core network equipment, where the first instruction information indicates the priority of one or more terminal devices. The processing unit 1200 is then further configured to determine, based on the first instruction information, which terminal devices need to be disconnected to receive multicast services.

[0325] Optionally, the transmitting unit 1300 and the receiving unit 1100 may be integrated into a single transceiver unit that has both receiving and transmitting functions. This is not limited to the foregoing.

[0326] In another possible implementation, the transmitting unit 1300 is configured to send a group paging message to a terminal device, where the group paging message includes a first piece of information used to call a terminal device group to receive the first multicast service, and the terminal device group includes terminal devices. The transmitting unit 1300 is further configured to send a second piece of information to the terminal device, where the second piece of information indicates whether the network device will provide the first multicast service to the terminal device group, which is in Radio Resource Control (RRC) disconnected mode.

[0327] Optionally, the second piece of information may be carried in a group paging message, or it may be carried over a multicast control channel.

[0328] Optionally, the communication device 1000 further includes a receiving unit 1100. The transmitting unit 1300 and the receiving unit 1100 may be integrated into a single transceiver unit that has both receiving and transmitting functions. This is not limited herein.

[0329] In one implementation where the communication device 1000 is a network device in an embodiment of the method, the transmitting unit 1300 may be a transmitter, and the receiving unit 1100 may be a receiver. The receiver and transmitter may also be integrated into a single transceiver. The processing unit 1200 may be a processing unit.

[0330] The functions of the processing unit may be implemented by hardware, or by hardware running corresponding software. For example, the processing unit may include memory and a processor. The memory is configured to store computer programs, and the processor reads and executes the computer programs stored in the memory, enabling the communication device 1000 to perform operations and / or processes performed by network equipment in a method embodiment. Optionally, the processing unit may include only a processor, with the memory configured to store computer programs located outside the processing unit. The processor is connected to the memory via circuitry / wiring to read and execute the computer programs stored in the memory. As another example, the processing unit may be a chip or an integrated circuit.

[0331] In one implementation where the communication device 1000 is a chip or integrated circuit installed within a network device, the transmitting unit 1300 and the receiving unit 1100 may be communication interfaces or interface circuits. For example, the transmitting unit 1300 may be an output interface or output circuit, and the receiving unit 1100 may be an input interface or input circuit. The processing unit 1200 may be a processor or microprocessor integrated on a chip or integrated circuit. This is not limited herein.

[0332] Figure 18 shows the configuration of the communication device 10 according to this application. The device 10 includes a processor 11. The processor 11 is coupled to a memory 12. The memory 12 is configured to store computer programs or instructions and / or data. The processor 11 is configured to: execute computer programs or instructions stored in the memory 12; or read data stored in the memory 12 and perform the method in the embodiment of the method described above.

[0333] Optionally, there may be one or more processors 11.

[0334] There may be one or more memory locations 12, at the discretion of the user.

[0335] Optionally, the memory 12 and processor 11 may be integrated together or disposed separately.

[0336] Optionally, the device 10 further includes a transceiver 13, as shown in Figure 18. The transceiver 13 is configured to receive and / or transmit signals. For example, the processor 11 is configured to control the transceiver 13 to receive and / or transmit signals.

[0337] In the solution, the device 10 is configured to implement the operations performed by the terminal equipment in the embodiment of the method described above.

[0338] For example, the processor 11 is configured to execute computer programs or instructions stored in memory 12 to implement the relevant operations performed by the terminal device in the embodiments of the method described above, for example, the methods performed by the terminal device in the embodiments shown in Figure 12 or Figure 13.

[0339] In an alternative solution, device 10 is configured to implement the operations performed by the network device in the embodiment of the method described above.

[0340] For example, the processor 11 is configured to execute computer programs or instructions stored in memory 12 to implement the relevant operations performed by the network device in the embodiments of the method described above, for example, the methods performed by the network device in the embodiments shown in Figure 12 or Figure 13.

[0341] Furthermore, this application further provides a computer-readable storage medium that stores computer instructions. When the computer instructions are executed on a computer, the operations and / or procedures performed by the terminal or network equipment in the embodiments of the method of this application are executed.

[0342] This application further provides a computer program product, which includes computer program code or instructions. When the computer program code or instructions are executed on a computer, the operations and / or procedures performed by terminal equipment or network equipment in embodiments of the method of this application are executed.

[0343] In addition, this application further provides a chip, which includes a processor. Memory configured to store computer programs is disposed independently of the chip. The processor is configured to execute the computer programs stored in the memory, thereby performing operations and / or processes performed by terminal or network equipment in any embodiment.

[0344] Furthermore, the chip may further include a communication interface. This communication interface could be an input / output interface, an interface circuit, or something similar. Additionally, the chip may further include memory.

[0345] In addition, this application further provides a communication system, which includes terminal equipment and network equipment in the embodiments of this application.

[0346] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip and has signal processing capabilities. In the implementation process, each step of the embodiments of the method described above may be completed by using integrated logic circuits of hardware in the processor or instructions in the form of software. The processor may be a central processing unit (CPU), or another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or another programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or the like. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor or the like. The steps of the method disclosed in the embodiments of this application may be performed and completed directly by a hardware encoding processor, or by using a combination of hardware in the encoding processor and software modules. The software module may be located in a storage medium that is mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. The storage medium is located in memory. The processor reads the information in memory and, in combination with the processor hardware, completes the steps of the method described above.

[0347] The memory in the embodiments of this application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may be random access memory (RAM) used as an external cache. Many forms of RAM may be used, for example, but this is not an exhaustive description. Examples include static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchlink dynamic random access memory (synchlink DRAM, SLDRAM), and direct rambus dynamic random access memory (direct rambus RAM, DR RAM).

[0348] It should be noted that if the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, then memory (storage module) may be integrated into the processor.

[0349] It should be further noted that the memories described herein are intended to include, but are not limited to, these memories and any other suitable type of memory.

[0350] Those skilled in the art will recognize, in combination with the examples described in the embodiments disclosed herein, that units and algorithmic steps can be implemented by electronic hardware, or by a combination of computer software and electronic hardware. Whether a function is performed by hardware or by software depends on the specific application and the design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application. For the purpose of convenience and simplicity, it will be obvious to those skilled in the art that detailed operating processes of the systems, devices, and units described above can be seen by referring to the corresponding processes in the embodiments of the methods described above. Further details are not described herein. It should be understood that in some embodiments provided in this application, the disclosed systems, devices, and methods can be implemented in other ways. For example, the embodiments of the devices described are merely examples. For example, the division into units is merely a logical functional division, and actual implementations may involve other divisions. For example, multiple units or components may be combined or integrated into another system, or some functions may be ignored or not performed. Furthermore, the mutual coupling, direct coupling, or communication connection described or indicated may be implemented through several interfaces. Indirect coupling or communication connection between devices or units may be implemented in an electrical, mechanical, or other form. Units described as separate parts may or may not be physically separate, and parts indicated as units may or may not be physical units, or may be located in one place or distributed across multiple network units. Some or all of the units may be selected based on the actual requirements in order to achieve the objectives of the solution of the embodiment.In addition, the functional units in the embodiments of this application may be integrated into a single processing unit, each unit may exist physically independently, or two or more units may be integrated into a single unit. It's fine. .

[0351] When a function is implemented in the form of a software function unit and sold or used as an independent product, that function may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application may be implemented in the form of a software product. A computer software product is stored in a storage medium and includes several instructions for instructing a computer device (which may be a personal computer, server, or network device) to perform all or part of the steps of the method described in the embodiments of this application. The storage medium mentioned above includes, namely, any medium capable of storing program code, such as a USB flash drive, removable hard disk, ROM, RAM, magnetic disk, or optical disk.

[0352] It should be understood that the term "one embodiment" as used throughout this specification means that certain features, structures, or characteristics related to an embodiment are included in at least one embodiment of this application. Therefore, embodiments throughout this specification do not necessarily refer to the same embodiment. In addition, these particular features, structures, or characteristics may be combined in one or more embodiments in any suitable manner.

[0353] Furthermore, it should be understood that the ordinal numbers such as "first" and "second" in the embodiments of this application are for distinguishing between multiple objects, but do not limit the size, content, order, chronological order, priority, importance, or similar aspects of the multiple objects. For example, the first piece of information and the second piece of information do not indicate differences in information quantity, content, priority, importance, or similar aspects.

[0354] Furthermore, it should be understood that in this application, both "when" and "if" mean that the network element performs the corresponding process in an objective situation, and are not intended to limit time, nor do they imply that the network element is required to perform a decision action during implementation, nor do they imply any other limitations.

[0355] Furthermore, it should be understood that in this application, “at least one” means one or more, and “multiple” means two or more. “At least one item (part)” or similar expressions refer to one item (part) or more items (parts), i.e., any combination of singular items (parts) or multiple items (parts). For example, at least one of a, b, or c represents a, b, c, a and b, a and c, b and c, or a and b and c.

[0356] Furthermore, unless otherwise specified, the same meaning as "The item includes one or more of the following: namely A, B, and C" in this application should be understood to generally mean that the item can be any one of the following: namely A, B, C, A and B, A and C, B and C, A, A and A, A and A, A and B, A, A and C, A, B and B, A, C and C, B and B, B, B and B, B, B and C, C and C, C and C, C and C, as well as other combinations of A, B, and C. The foregoing uses the three elements A, B, and C as an example to describe an optional item in the project. If the expression is "The item includes at least one of the following: namely A, B, ..., and X," i.e., if there are more elements in the expression, the items that can be applied to the item may also be obtained according to the rules above.

[0357] Furthermore, it should be understood that the term "and / or" in this application describes only the relationship between related objects, and indicates that three relationships may exist. For example, A and / or B may represent the following cases: A existing alone, both A and B existing, and B existing alone. Here, A and B may be singular or plural. The letter " / " generally indicates the relationship "or" between related objects. For example, A / B indicates A or B.

[0358] Furthermore, in the embodiments of this application, it should be understood that "B corresponding to A" indicates that B is associated with A and that B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A, and that B can be determined based on A and / or other information.

[0359] The above description is merely a specific implementation in this application, but does not limit the scope of protection of this application. Any modification or substitution that is readily conceivable to a person skilled in the art within the scope of the technical scope disclosed in this application shall fall within the scope of protection of this application. Accordingly, the scope of protection of this application shall be subject to the scope of protection of the claims.

Claims

1. A method of communication Step (A) is a terminal device in Radio Resource Control (RRC) disconnected mode that receives a group paging message from a network device, wherein the group paging message includes first information, which is used to invoke a group of terminal devices to receive the first multicast service after the invocation in the RRC disconnected mode, and the group of terminal devices includes the terminal device. Based on the first and second pieces of information, the terminal device will The step of receiving the first multicast service in the RRC non-connected mode, or Steps to perform the RRC connection control procedure Step (B) is a step in which any one of the following is performed, wherein the second information indicates whether the network device provides the first multicast service to the group of terminal devices that are in RRC non-connected mode. A method that includes [a certain feature].

2. If the terminal device performs the step of receiving the first multicast service in the RRC non-connected mode based on the first information and the second information, the step (B) to be performed is: The following steps, namely, If the second piece of information indicates that the network device provides the initial multicast service to the group of terminal devices in RRC non-connected mode, the terminal devices may take the step of receiving the initial multicast service in RRC non-connected mode, or The terminal device initiates an access control procedure based on the first information. Choose one of the following, If the terminal device is not permitted to access the network device, and the second information indicates that the network device provides the initial multicast service to the group of terminal devices in RRC disconnected mode, the terminal device receives the initial multicast service in RRC disconnected mode. The method according to claim 1, including the method described in claim 1.

3. When the terminal device performs the step of executing the RRC connection control procedure based on the first information and the second information, the step (B) to be performed is: If the second piece of information indicates that the network device does not provide the initial multicast service to the group of terminal devices that are in RRC non-connection mode, the terminal device may perform the RRC connection control procedure, or The terminal device initiates an access control procedure based on the first information, and if the terminal device is permitted to access the network device, it executes the RRC connection control procedure. The method according to claim 1, including the method described in claim 1.

4. The second piece of information is conveyed via the group paging message, or The second piece of information is transmitted over a multicast control channel. The method according to claim 1.

5. If the terminal device performs the step of initiating an access control procedure based on the first information, and the terminal device is not permitted to access the network device, the method The steps include: a terminal device monitoring a physical downlink control channel (PDCCH) corresponding to a multicast control channel within the execution time of a first timer and obtaining the second information, wherein the execution time of the first timer is the duration during which the terminal device must wait after being denied access to the network device before restarting the access control procedure; The following steps, namely, After the first timer expires, the terminal device terminates the access control procedure, or the terminal device stops the start of the access control procedure, or If the group paging message contains the second information, the terminal device terminates the access control procedure, or the terminal device skips starting the first timer, or the terminal device stops starting the access control procedure after the first timer has expired, wherein the execution time of the first timer is the duration during which the terminal device must wait after being denied access to the network device before restarting the access control procedure. One of the following The method according to claim 2, further comprising:

6. A method of communication A step of a network device sending a group paging message to a terminal device in radio resource control (RRC) disconnected mode, wherein the group paging message includes first information, which is used to invoke a terminal device group to receive the first multicast service after the invoke in the RRC disconnected mode, and the terminal device group includes the terminal device; A step of transmitting second information to the terminal device by the network device, wherein the second information indicates whether the network device provides the first multicast service to the group of terminal devices that are in RRC non-connection mode. A method that includes [a certain feature].

7. The second piece of information is conveyed via the group paging message, or The second piece of information is transmitted over a multicast control channel. The method according to claim 6.

8. A communication device A receiving unit configured to receive group paging messages from network equipment, wherein the group paging message includes first information, which is used to invoke a group of terminal equipment to receive the first multicast service after the invocation in the RRC disconnected mode, and the group of terminal equipment includes terminal equipment, the receiving unit and Based on the first and second pieces of information mentioned above, The receiving unit is enabled to receive the initial multicast service in Radio Resource Control (RRC) disconnected mode, or The processing unit executes the RRC connection control procedure. A processing unit configured to perform one of the following, wherein the second information indicates whether the network device provides the initial multicast service to the group of terminal devices that are in RRC disconnected mode, and A communication device equipped with the following features.

9. The following, namely, If the second piece of information indicates that the network device provides the initial multicast service to the group of terminal devices that are in RRC non-connection mode, the receiving unit will receive the initial multicast service if the terminal devices are in RRC non-connection mode, or The processing unit initiates an access control procedure based on the first information. Do one of the following: If the second information indicates that the network device provides the initial multicast service to the group of terminal devices in RRC disconnection mode without the terminal device being permitted to access the network device, the receiving unit receives the initial multicast service if the terminal device is in RRC disconnection mode. The apparatus according to claim 8.

10. If the processing unit determines that the second information indicates that the network device does not provide the initial multicast service to the group of terminal devices that are in RRC non-connection mode, it executes the RRC connection control procedure, or The processing unit initiates an access control procedure based on the first information, and if the terminal device is permitted to access the network device, the processing unit executes the RRC connection control procedure. The apparatus according to claim 8.

11. The apparatus according to claim 8, wherein the second information is carried in the group paging message, or the second information is transmitted over a multicast control channel.

12. When the processing unit initiates the access control procedure based on the first information, The processing unit is further configured to monitor the physical downlink control channel (PDCCH) corresponding to the multicast control channel and acquire the second information within the execution time of the first timer, the execution time of the first timer being the duration during which the terminal device must wait after being denied access to the network device before restarting the access control procedure. The following, namely, The processing unit is further configured to terminate the access control procedure or to stop the terminal device from starting the access control procedure after the first timer has expired, or If the group paging message contains the second information, the processing unit terminates the access control procedure, skips starting the first timer, or stops the access control procedure from starting after the first timer has expired, wherein the execution time of the first timer is the duration during which the terminal device must wait before restarting the access control procedure after it has not been permitted to access the network device. Do one of the following: The apparatus according to claim 9.

13. A communication device A transmitting unit configured to send group paging messages to terminal devices, wherein the group paging messages include first information, which is used to invoke a group of terminal devices to receive the first multicast service after the invocation in the RRC disconnected mode, and the group of terminal devices includes the terminal devices. The transmitting unit is further configured to transmit a second piece of information to the terminal equipment, the second piece of information indicating whether the network equipment provides the first multicast service to the group of terminal equipment that is in radio resource control (RRC) disconnected mode. Communication device.

14. The apparatus according to claim 13, wherein the second information is carried in the group paging message, or the second information is carried in a multicast control channel.

15. A communication device comprising at least one processor and at least one memory, wherein the at least one memory is configured to store a computer program or instruction, and the at least one processor is configured to execute the computer program or instruction in the memory, thereby enabling the method according to any one of claims 1 to 5 to be performed.

16. A communication device comprising at least one processor and at least one memory, wherein the at least one memory is configured to store a computer program or instruction, and the at least one processor is configured to execute the computer program or instruction in the memory, thereby enabling the method according to claim 6 or 7 to be executed.

17. A computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and when the computer instructions are executed on a computer, the method according to any one of claims 1 to 5 is executed.

18. A computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and when the computer instructions are executed on a computer, the method according to claim 6 or 7 is executed.

19. A computer program comprising computer program code, wherein when the computer program code is executed on a computer, the method according to any one of claims 1 to 5 is executed.

20. A computer program comprising computer program code, wherein when the computer program code is executed on a computer, the method according to claim 6 or 7 is executed.

Images