Communication method, apparatus and system
By sending RRC recovery request message and restoring MRB in the terminal device, the problem of the inability to restore the anchor base station configuration after cell reselecting in the RRC inactive state is solved, and the multicast reception efficiency and continuity are improved.
Patent Information
- Application Number
- PCT/CN2024/091936
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-13
- Filing Date
- 2024-05-09
- Publication Date
- 2024-11-21
AI Technical Summary
When the terminal device is in the RRC inactive state, frequent cell reselection causes the MRB configured by the anchor base station to be unable to recover, thereby affecting the correct reception of multicast services.
By sending an RRC recovery request message to the first network device, receiving an RRC recovery message and entering an RRC connection state, the MRB is restored based on the RRC recovery message and the pre-saved multicast configuration information to ensure that the terminal device can correctly receive multicast.
Improve the reception efficiency of multicast services, ensure that the terminal equipment can correctly receive multicast in the RRC connected state, reduce the interruption and power consumption overhead caused by reacquisition of multicast configuration, and improve the network equipment to provide non-connected multicast Flexibility of configuration.
Smart Images

Figure CN2024091936_21112024_PF_FP_ABST
Abstract
Description
Communication method, device and system
[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on May 13, 2023, with application number 202310541342.3 and application name “A Communication Method, Device and System”, the entire contents of which are incorporated by reference into this application. Technical Field
[0002] The present application relates to the field of communication technology, and in particular to a communication method, device, and system. Background Art
[0003] A terminal device in the RRC inactive state will reselect multiple cells during its mobility. After each reselection, if the serving cell it resides in can provide multicast for the terminal device in the RRC inactive state, the terminal device will obtain the corresponding multicast configuration information from the MCCH message sent by the serving cell for multicast configuration.
[0004] However, for the same multicast, the multicast configuration information provided by each serving cell in which the terminal device chooses to reside may include different MRB configuration information, and the terminal device will receive the first multicast based on different MRBs in different serving cells. After the terminal device restores the RRC connected state, the serving base station will transmit the corresponding multicast based on the MRB configured by the anchor base station. However, after multiple cell reselections, the terminal device may no longer be able to restore the MRB configured by the anchor base station, resulting in difficulty for the terminal device to correctly receive the multicast after restoring the RRC connected state.
[0005] Summary of the Invention
[0006] The embodiments of the present application provide a communication method, device, and system that can improve the reception efficiency of multicast services.
[0007] In a first aspect, an embodiment of the present application provides a communication method, applied to a terminal device or a chip in the terminal device, the method comprising:
[0008] Send a radio resource control (RRC) recovery request message to a first network device; receive an RRC recovery message sent by the first network device; enter an RRC connected state from an RRC inactive state; receive a first multicast based on a first multicast broadcast service radio bearer (MRB), wherein the first MRB is determined by the RRC recovery message and first multicast configuration information, and the first multicast configuration information is obtained from a second network device, and the second network device is a network device of the last serving cell in the RRC connected state.
[0009] Using the communication method provided in this application, after the terminal device enters the RRC connected state, the first MRB can be restored based on the RRC recovery message and the pre-saved first multicast configuration information. In this way, the configuration information of the MRB determined by the first network device and the terminal device is the same. Therefore, the terminal device can correctly receive the first multicast sent by the first network device based on the first MRB, thereby improving the efficiency of multicast reception.
[0010] In a possible implementation, before sending the RRC recovery request message to the first network device, the method includes:
[0011] Receive the first multicast configuration information sent by the second network device in the RRC connected state; receive the first multicast based on the first MRB; receive the first RRC release message sent by the second network device; and enter the RRC inactive state from the RRC connected state.
[0012] In a possible implementation, after entering the RRC inactive state from the RRC connected state and before sending the RRC recovery request message to the first network device, the method further includes:
[0013] The first multicast is received according to the second multicast configuration information.
[0014] In a possible implementation, the second multicast configuration information is sent by the first network device, the second network device, or a third network device, where the third network device is a network device of a serving cell in an RRC inactive state.
[0015] In a possible implementation, both the first multicast configuration information and the second multicast configuration information include configuration information of the first MRB.
[0016] In one possible implementation, the first multicast configuration information includes an identifier of the first MRB, and the first multicast configuration information also includes at least one of a packet data channel PDCP configuration, a radio link control RLC configuration, a medium access control MAC configuration, and a physical layer configuration of the first MRB.
[0017] In a second aspect, an embodiment of the present application provides a communication method, applied to a terminal device or a chip in the terminal device, the method comprising:
[0018] Receive a first radio resource control RRC release message sent by a second network device, where the first RRC release message indicates second multicast configuration information, where the second multicast configuration information is configuration information for receiving the first multicast in the first cell in an RRC non-connected state; and enter the RRC non-connected state from the RRC connected state.
[0019] By adopting the communication method provided in the present application, a terminal device can determine the second multicast configuration information sent by the second network device in the first RRC release message, which can be used to receive the first multicast in the first cell in the RRC non-connected state. As a result, after the terminal device selects and resides in the first cell, it can directly use the second multicast configuration information in the first RRC release message to receive the first multicast without having to re-acquire the second multicast configuration information. On the one hand, this reduces the multicast reception interruption caused by re-acquiring the multicast configuration, improves the continuity of multicast reception, and reduces the power consumption overhead of the terminal device. On the other hand, it improves the flexibility of the network device in providing the non-connected multicast configuration, and the network device can choose which cell's multicast configuration to provide.
[0020] In a possible implementation, after entering the RRC unconnected state from the RRC connected state, the method further includes:
[0021] In case of cell selection and camping on the first cell, the first multicast is received in the first cell based on the second multicast configuration information in an RRC non-connected state.
[0022] In a possible implementation, when performing cell selection, the first cell is preferentially selected as the serving cell.
[0023] In a possible implementation, the first RRC release message includes an identifier of the first cell.
[0024] In a possible implementation manner, the first cell is a serving cell configured with a first common frequency domain resource CFR, and the first common frequency domain resource is used to transmit the first multicast.
[0025] In a possible implementation, the second multicast configuration information includes at least one of an identifier of the first multicast, an activation state of the first multicast, a multicast broadcast service control channel MCCH configuration, and a point-to-multipoint PTM configuration of the first multicast.
[0026] In a third aspect, an embodiment of the present application provides a communication method, applied to a network device or a chip in a network device, the method comprising:
[0027] A first radio resource control (RRC) release message is sent to the terminal device, where the first RRC release message indicates second multicast configuration information, where the second multicast configuration information is configuration information for receiving the first multicast in the first cell in an RRC non-connected state.
[0028] Using the communication method provided in this application, the second network device can select which cell's multicast configuration to provide, thereby increasing the flexibility of the network device in providing non-connected multicast configuration. This allows the terminal device to be directly instructed that the second multicast configuration information sent by the second network device in the first RRC release message can be used to receive the first multicast in the first cell in the RRC non-connected state. This allows the terminal device, after selecting and residing in the first cell, to directly use the second multicast configuration information in the first RRC release message to receive the first multicast without having to reacquire the second multicast configuration information. This reduces the multicast reception interruption caused by reacquiring the multicast configuration, improves the continuity of multicast reception, and reduces the power consumption overhead of the terminal device.
[0029] In a possible implementation, the first RRC release message includes an identifier of the first cell.
[0030] In a possible implementation manner, the first cell is a serving cell configured with a first common frequency domain resource CFR, and the first common frequency domain resource is used to transmit the first multicast.
[0031] In a possible implementation, the second multicast configuration information includes at least one of an identifier of the first multicast, an activation state of the first multicast, a multicast broadcast service control channel MCCH configuration, and a point-to-multipoint PTM configuration of the first multicast.
[0032] In a fourth aspect, an embodiment of the present application provides a communication method, applied to a terminal device or a chip in the terminal device, the method comprising:
[0033] Receive a first radio resource control (RRC) release message sent by a second network device, where the first RRC release message indicates a first radio access network notification area (RNA); enter an RRC inactive state from an RRC connected state; when the first condition and the second condition are met, send an RRC connection recovery request message to the first network device, where the first network device is a network device of a serving cell, and the first condition is that a first timer times out or the serving cell does not belong to the first RNA; the RRC connection recovery request message carries a first cause value; the second condition is that multicast is not received in the RRC inactive state, or that multicast is received in the RRC inactive state and the serving cell sends second multicast configuration information; the second multicast configuration information is configuration information for receiving the first multicast in the serving cell in the RRC inactive state.
[0034] By adopting the communication method provided in the present application, by setting the first reason value, it is indicated that the terminal device meets the first condition and the second condition, so that the network device can accurately know the status of the terminal device according to the first reason value, thereby improving the accuracy of the network device in executing the response according to the status of the terminal device, and facilitating the network device to meet the performance requirements of the terminal device for data transmission.
[0035] In a possible implementation, the first cause value is RNA update.
[0036] In the above possible implementation method, the condition for using "RNA update" as the recovery reason value is reset. Only when the first condition and the second condition are met, the terminal device will use "RNA update" as the recovery reason value to request the first network device to restore the RRC connection. This avoids the situation where the terminal device is updated with RNA at the same time and needs to obtain multicast configuration. The first network device still releases the terminal device to the RRC non-connected state based on the reason value of the RNA update, and does not provide the terminal device with the multicast configuration of the RRC inactive state, resulting in the terminal device being unable to successfully receive multicast.
[0037] In a possible implementation, the first multicast is a joined multicast in an activated state.
[0038] In a possible implementation manner, the second multicast configuration information is carried in the first MCCH message.
[0039] In a possible implementation manner, the second multicast configuration information includes at least one of an identifier of the first multicast, a G-RNTI of the first multicast, and an MRB configuration of the first multicast.
[0040] In a fifth aspect, the present application provides a communication method, applied to a terminal device or a chip in the terminal device, the method comprising:
[0041] Receive a first radio resource control RRC release message sent by a second network device, where the first RRC release message indicates a first radio access network notification area RNA; enter an RRC inactive state from an RRC connected state; when the first condition and the third condition are met, send an RRC connection recovery request message to the first network device, where the first network device is a network device of a serving cell, and the first condition is that a first timer times out or the serving cell does not belong to the first RNA; the RRC connection recovery request message carries a second cause value; the third condition is that the first RRC release message indicates that multicast is received in an RRC inactive state and the serving cell does not send second multicast configuration information; the second multicast configuration information is configuration information for receiving the first multicast in the serving cell in the RRC inactive state.
[0042] Based on the communication method provided in the embodiment of the present application, when the terminal device simultaneously updates the RNA and needs to re-acquire the multicast configuration, the second cause value is used as the recovery cause value to ensure that the first network device can obtain the terminal device context from the second network device (last serving gNB) based on the RRC recovery request message of the terminal device, thereby allowing the terminal device to enter the RRC connected state and provide multicast to the terminal device; or provide the terminal device with the RRC inactive state multicast configuration and provide multicast to the inactive terminal device, thereby ensuring that the terminal device can smoothly receive the multicast and improving the multicast reception efficiency.
[0043] In a possible implementation, the first multicast is a joined multicast in an activated state.
[0044] In a possible implementation manner, the second multicast configuration information is carried in the first MCCH message.
[0045] In a possible implementation manner, the serving cell not sending the second multicast configuration information includes:
[0046] The first multicast broadcast service control channel MCCH message sent by the serving cell does not include the second multicast configuration information; or the serving cell does not send a first system message, and the first system message is used to send the configuration information of the first MCCH.
[0047] In a possible implementation, the second cause value is one of mobile originated data mo-Data, mobile originated signaling mo-Signalling, mobile terminal access mt-Access, or multicast broadcast service access.
[0048] Based on the above possible implementation methods, when the terminal device simultaneously updates RNA and needs to re-acquire multicast configuration, one of mobile originating data mo-Data, mobile originating signaling mo-Signalling, mobile terminal access mt-Access, or multicast broadcast service access is used as the recovery cause value to ensure that the first network device can obtain the terminal device context from the second network device (last serving gNB) based on the RRC recovery request message of the terminal device, thereby allowing the terminal device to enter the RRC connected state and provide multicast to the terminal device; or provide the terminal device with RRC inactive state multicast configuration and provide multicast to the inactive terminal device, thereby ensuring that the terminal device can smoothly receive multicast and improving the efficiency of multicast reception.
[0049] In a possible implementation, the second cause value is a third cause value, and the third cause value indicates that a multicast broadcast service is accessed and an RNA is updated.
[0050] Based on the above possible implementation methods, when the terminal device simultaneously updates RNA and needs to re-acquire multicast configuration, by setting the third cause value as the recovery cause value, it is ensured that the first network device can obtain the terminal device context from the second network device (last serving gNB) based on the RRC recovery request message of the terminal device, thereby allowing the terminal device to enter the RRC connected state and provide multicast to the terminal device; or provide the RRC inactive state multicast configuration to the terminal device and provide multicast to the inactive terminal device, thereby ensuring that the terminal device can smoothly receive multicast and improving the multicast reception efficiency.
[0051] In a possible implementation, after sending the RRC connection recovery request message to the first network device, the method further includes: receiving a second RRC release message sent by the first network device;
[0052] Acquire the second multicast configuration information.
[0053] In a possible implementation manner, the second multicast configuration information is carried in the second RRC release message, or the second multicast configuration information is carried in the first system message and / or the first MCCH message of the serving cell.
[0054] In a sixth aspect, an embodiment of the present application provides a communication method, applied to a network device or a chip in a network device, the method comprising:
[0055] A first radio resource control (RRC) connection recovery request message is received from a terminal device, wherein the RRC connection recovery request message carries a third cause value, and the third cause value indicates that the RNA is updated and the service cell does not send the second multicast configuration information; the second multicast configuration information is the configuration information of the first multicast received in the service cell when the RRC is in an inactive state.
[0056] In a possible implementation, the method further includes:
[0057] In a case where RRC inactive multicast can be provided, sending a context retrieval request message to the second network device, where the context retrieval request message carries the third cause value;
[0058] receiving a context retrieval failure message sent by the second network device, where the context retrieval failure message includes a second RRC release message and an identifier of the first multicast;
[0059] Send the second multicast configuration information and the second RRC release message to the terminal device.
[0060] In a possible implementation, the second multicast configuration information is carried in the second RRC release message, or the second multicast configuration information is carried in the first system message and / or the first multicast broadcast service control channel MCCH message of the serving cell.
[0061] In a possible implementation, the context retrieval request message further carries a set of RRC inactive multicast identifiers that can be provided by the first network device, and the set of multicast identifiers includes the first multicast identifier.
[0062] In a possible implementation, the method further includes:
[0063] In a case where providing RRC inactive multicast is not supported, sending a context retrieval request message to the second network device, wherein the context retrieval request message does not carry the third cause value;
[0064] receiving a context retrieval response message sent by the second network device, where the context retrieval response message includes the context of the terminal device;
[0065] An RRC recovery message is sent to the terminal device, where the RRC recovery message instructs the terminal device to enter an RRC connected state from an RRC inactive state.
[0066] In a seventh aspect, an embodiment of the present application provides a communication method, applied to a network device or a chip in a network device, the method comprising:
[0067] Sending a first radio resource control RRC release message to the terminal device, where the first RRC release message indicates a first radio access network-based notification area RNA;
[0068] Receiving a context retrieval request message sent by a first network device, the context retrieval request message carrying a third cause value, the third cause value indicating that the RNA is updated and the serving cell of the terminal device does not send second multicast configuration information; the second multicast configuration information is configuration information for receiving the first multicast in the serving cell in an RRC inactive state; the first network device is a network device of the serving cell;
[0069] If the serving cell belongs to the first RNA, sending a context retrieval failure message to the first network device, where the context retrieval failure message carries a second RRC release message and an identifier of the first multicast;
[0070] If the serving cell does not belong to the first RNA, a context retrieval response message is sent to the first network device, where the context retrieval response message includes the context of the terminal device.
[0071] In a possible implementation, the context retrieval request message further carries a set of RRC inactive multicast identifiers that can be provided by the first network device, and the set of multicast identifiers includes the identifier of the first multicast.
[0072] In the eighth aspect, a communication device is provided, which is configured to perform the various steps of the method in the first aspect, any possible implementation of the first aspect, the second aspect or any possible implementation of the second aspect, the fourth aspect or any possible implementation of the fourth aspect, and the fifth aspect or any possible implementation of the fifth aspect.
[0073] In a possible implementation of the eighth aspect, the communication device includes: a unit or module for executing the method in the above first aspect, any possible implementation of the first aspect, the second aspect or any possible implementation of the second aspect, the fourth aspect or any possible implementation of the fourth aspect, the fifth aspect or any possible implementation of the fifth aspect.
[0074] In a possible implementation of the eighth aspect, the communication device includes: at least one processor and a memory, and the at least one processor is used to execute: the method in the above first aspect, any possible implementation of the first aspect, the second aspect or any possible implementation of the second aspect, the fourth aspect or any possible implementation of the fourth aspect, and the fifth aspect or any possible implementation of the fifth aspect.
[0075] In a ninth aspect, a terminal device is provided, which includes the communication apparatus provided in the eighth aspect.
[0076] In the tenth aspect, a communication device is provided, which is configured to execute at least one processor and memory as described above, and the at least one processor is used to execute: the various steps of the method in the third aspect, any possible implementation of the third aspect, the sixth aspect or any possible implementation of the sixth aspect, the seventh aspect or any possible implementation of the seventh aspect.
[0077] In a possible implementation of the tenth aspect, the communication device includes: at least one processor and memory for executing the above, and the at least one processor is used to execute: a unit or module of the method in the above third aspect, any possible implementation of the third aspect, the sixth aspect or any possible implementation of the sixth aspect, the seventh aspect or any possible implementation of the seventh aspect.
[0078] In a possible implementation of the tenth aspect, the communication device includes: at least one processor and a memory, the at least one processor being used to execute: at least one processor and a memory, the at least one processor being used to execute: the method in the above third aspect, any possible implementation of the third aspect, the sixth aspect or any possible implementation of the sixth aspect, the seventh aspect or any possible implementation of the seventh aspect.
[0079] In the eleventh aspect, a network device is provided, and the terminal includes the communication device provided in the tenth aspect.
[0080] In a twelfth aspect, a computer program product is provided, which includes a computer program, and when the computer program is executed by a processor, it is used to execute the method in any one of the above aspects or any possible implementation of any one of the aspects.
[0081] In the thirteenth aspect, a computer-readable storage medium is provided, in which a computer program is stored. When the computer program is executed, it is used to execute the method in any one of the above aspects or any possible implementation of any one of the aspects.
[0082] In a fourteenth aspect, a communication system is provided, which includes the above-mentioned terminal device and network device.
[0083] In a fifteenth aspect, a chip system is provided, wherein the chip system includes a processor, and is used to implement the method described in any one of the above aspects.
[0084] In one possible design, the chip system may further include a memory for implementing the method described in any of the above aspects. BRIEF DESCRIPTION OF THE DRAWINGS
[0085] FIG1 is a system block diagram of a communication system provided in an embodiment of the present application;
[0086] FIG2 is a flow chart of a communication method according to an embodiment of the present application;
[0087] FIG3 is a second flow chart of a communication method provided in an embodiment of the present application;
[0088] FIG4 is a third flow chart of a communication method provided in an embodiment of the present application;
[0089] FIG5 is a fourth flow chart of a communication method provided in an embodiment of the present application;
[0090] FIG6 is a fifth flow chart of a communication method provided in an embodiment of the present application;
[0091] FIG7 is a sixth flow chart of a communication method provided in an embodiment of the present application;
[0092] FIG8 is a schematic block diagram of a communication device according to an embodiment of the present application;
[0093] FIG9 is a schematic block diagram of another communication device provided in an embodiment of the present application;
[0094] FIG10 is a schematic block diagram of another communication device provided in an embodiment of the present application;
[0095] FIG11 is a schematic block diagram of another communication device provided in an embodiment of the present application;
[0096] FIG12 is a schematic block diagram of a terminal provided in an embodiment of the present application;
[0097] FIG13 is a schematic block diagram of a network device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0098] The technical solution in this application will be described below with reference to the accompanying drawings.
[0099] To facilitate understanding of the embodiments of the present application, the communication system shown in FIG. 1 is first used as an example. The exemplary description is applicable to the communication system of the embodiments of the present application. FIG. 1 shows an architectural diagram of a communication system 1000 used in the embodiments of the present application. The communication system includes a radio access network (RNA) 100 and a core network 200. Optionally, the communication system 1000 may also include the Internet 300. The radio access network 100 may include at least one radio access network device (such as 110a and 110b in FIG. 1 , also referred to as an RNA node) and at least one terminal device (such as 120a-120j in FIG. 1 ). The terminal device is wirelessly connected to the radio access network device, and the radio access network device is wirelessly or wiredly connected to the core network. The core network device and the radio access network device may be independent and distinct physical devices, or the core network device's functions and the radio access network device's logical functions may be integrated into the same physical device. Alternatively, a single physical device may integrate some of the core network device's functions and some of the radio access network device's functions. Terminal devices and wireless access network devices can be connected to each other via wired or wireless means. Figure 1 is merely a schematic diagram. The communication system may also include other network devices, such as wireless relay devices and wireless backhaul devices, which are not shown in Figure 1.
[0100] The wireless access network device can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next generation NodeB (gNB) in a fifth generation (5G) mobile communication system, a next generation base station in a sixth generation (6G) mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system, etc.; it can also be a module or unit that performs some of the functions of a base station. The wireless access network device can be a macro base station (such as 110a in Figure 1), a micro base station or an indoor station (such as 110b in Figure 1), a relay node or a donor node, etc. The embodiments of the present application do not limit the specific technology and specific device form adopted by the wireless access network device. For the sake of convenience, the following description uses a base station as an example of a wireless access network device.
[0101] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, and different RAN nodes respectively implement part of the functions of the base station. For example, the RAN node can be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU can be set separately, or they can be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).
[0102] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, CU may also be called O-CU (Open CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, CU-UP may also be called O-CU-UP, and RU may also be called O-RU. For the convenience of description, this application uses CU, CU-CP, CU-UP, DU and RU as examples for description. Any unit of CU (or CU-CP, CU-UP), DU and RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.
[0103] Terminal devices may also be referred to as UE, mobile stations, mobile terminals, etc. Terminal devices can be widely used in various scenarios, for example, device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IOT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, etc. Terminal devices may be mobile phones, tablet computers, computers with wireless transceiver functions, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiments of this application do not limit the specific technology and specific device form adopted by the terminal devices.
[0104] Base stations and terminal devices can be fixed or mobile. They can be deployed on land, indoors or outdoors, handheld or vehicle-mounted; on water; or on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of base stations and terminal devices.
[0105] The roles of base stations and terminal devices can be relative. For example, the helicopter or drone 120i in Figure 1 can be configured as a mobile base station. For terminal devices 120j accessing the wireless access network 100 via 120i, terminal device 120i is a base station. However, for base station 110a, 120i is a terminal device, meaning that communication between 110a and 120i occurs via a wireless air interface protocol. Of course, communication between 110a and 120i can also occur via a base station-to-base station interface protocol. In this case, 120i is also a base station relative to 110a. Therefore, base stations and terminal devices can be collectively referred to as communication devices. 110a and 110b in Figure 1 can be referred to as communication devices with base station functionality, and 120a-120j in Figure 1 can be referred to as communication devices with terminal functionality.
[0106] Communication between base stations and terminal devices, between base stations, and between terminal devices can be carried out through authorized spectrum, unauthorized spectrum, or both; communication can be carried out through spectrum below 6 gigahertz (GHz), spectrum above 6 GHz, or spectrum below 6 GHz and spectrum above 6 GHz. The embodiments of the present application do not limit the spectrum resources used for wireless communication.
[0107] In the embodiments of the present application, the network device described below may refer to the wireless access network device in the communication system shown in Figure 1, or a module (such as a chip) in the wireless access network device, or a control subsystem including base station functions. The control subsystem including base station functions herein may be a control center in the above-mentioned application scenarios such as smart grid, industrial control, intelligent transportation, and smart city.
[0108] The terminal device described below may refer to the terminal device in the communication system shown in Figure 1, or a module (such as a chip or a modem) in the terminal device, or a device that includes the functions of the terminal device.
[0109] The key technical features involved in this application are explained below:
[0110] "Sending" and "receiving" in this application indicate the direction of signal / information transmission. For example, "sending information to a network device" can be understood as the destination end of the information being the network device, which can include direct sending through the air interface, and also includes indirect sending through the air interface by other units or modules. "Receiving information from a terminal device" can be understood as the source end of the information being the terminal device, which can include direct receiving from the terminal device through the air interface, and also includes indirect receiving from the terminal device through the air interface from other units or modules. "Sending" can also be understood as the "output" of the chip interface, and "receiving" can also be understood as the "input" of the chip interface. In other words, sending and receiving can be carried out between devices, for example, between a network device and a terminal device, or can be carried out within a device, for example, sending or receiving between components, modules, chips, software modules or hardware modules within the device through a bus, trace or interface.
[0111] Radio Resource Control (RRC) state: In the 5G New Radio (NR) system, there are currently three RRC states for terminal devices, namely RRC idle state, RRC inactive state, and RRC connected state.
[0112] When the terminal device is in the RRC connected state, an RRC connection is established between the terminal device and the network device, the terminal device can transmit data normally with the network device, and the network device can also maintain the context information of the terminal device. When the terminal device is in the RRC inactive state, no RRC connection is established between the terminal device and the network device, and no data is transmitted between the terminal device and the network device, but the network device can continue to maintain the context information of the terminal device so that the RRC connection can be quickly restored when there is a need for data transmission between the terminal device and the network device. When the terminal device is in the RRC idle state, no RRC connection is established between the terminal device and the network device, and no data is transmitted between the terminal device and the network device.
[0113] In one embodiment, the network device can release the terminal device to the RRC idle state or RRC inactive state by sending an RRCRelease (RRC release) message to the terminal device in the RRC connected state. For example, if the RRCRelease message carries the suspend configuration (suspendConfig), the terminal device enters the RRC inactive state from the RRC connected state, the terminal device suspends the RRC connection with the network device, and the network device continues to maintain the context downlink of the terminal device. In some examples, for terminal devices with infrequent data transmission, the network device can keep the terminal device in the RRC inactive state. Afterwards, when the terminal device in the RRC inactive state meets certain triggering conditions, such as the arrival of uplink services, receiving a paging message sent by the network device, etc., the terminal device can request the network device to restore the RRC connection. For example, the terminal device sends an RRCResumeRequest (RRC recovery request) message to the network device. According to the actual scenario and needs, the network device sends an RRCResume (RRC recovery) message to the terminal device to make the terminal device enter the RRC connected state; or sends an RRCRelease message carrying suspendConfig to the terminal device to make the terminal device remain in the RRC inactive state; or sends an RRCRelease message without suspendConfig to the terminal device to make the terminal device enter the RRC idle state.
[0114] If the RRCRelease message sent by the network device does not include suspendConfig, the terminal device directly enters the RRC idle state from the RRC connected state. When the terminal device in the RRC idle state has data transmission requirements, the terminal device can request the network device to reestablish the RRC connection. For example, the terminal device sends an RRCSetupRequest (RRC establishment request) message to the network device, and after receiving the RRCSetup (RRC establishment) message sent by the network device, it enters the RRC connected state.
[0115] Cell reselection and cell selection: When a terminal device enters the RRC idle state or the RRC inactive state, it will measure the received power and signal quality of the cell according to the cell selection criterion (also known as the S criterion) during its movement, determine whether the cell is suitable for access, and select an accessible cell to reside in. This process is called cell selection. When the terminal device resides in a serving cell, it will measure the signal quality of the serving cell and the neighboring cell according to the cell reselection criterion (also known as the R criterion). If the quality of the serving cell is poor and the signal quality of the neighboring cell is good, the terminal device will actively reselect the cell with better signal quality as the serving cell. This process is called cell reselection.
[0116] Among them, the service cell of the terminal device in the RRC non-connected state refers to the cell where the terminal device is camped (Camp on), or it can also be called the camped service cell.
[0117] Update of the Radio Access Network Notification Area (RNA): For terminal devices that enter the RRC idle or RRC inactive state, cell reselection may occur because the terminal device may be in a mobile state. Therefore, to enable network equipment to find the terminal device at any time, a tracking area (TA) is defined. A TA includes multiple cells, and the core network sends paging messages in a tracking area to track the terminal device.
[0118] In order to save transmission overhead, multiple cells within a TA range are divided into multiple RNAs, and an RNA may include several cells. RNA is managed by a network device (such as a gNB). In one embodiment, the network device of the service cell where the terminal device last resides when it is in the RRC connected state is called an anchor base station, or the last serving gNB; after the terminal device enters the RRC inactive state, the network device that selects the service cell to reside in after cell reselection / cell selection is called a serving base station. The serving base station and the anchor base station may be the same network device or different network devices. When the anchor base station instructs the terminal device to enter the RRC inactive state from the RRC connected state by sending an RRCRelease message, the anchor base station indicates the information of the RNA where the RAN terminal device is located when it is in the RRC connected state in the RRCRelease message. For example, one possible way is to carry the RNAID in the RRCRelease message. Currently, the RNA ID consists of a tracking area code and a RAN area code. For another example, in another manner, the RRCRelease message carries the cell list included in the RNA, and the cells in the cell list can be indicated by cell identifiers.
[0119] After the terminal device enters the RRC inactive state or the RRC idle state, when the anchor base station receives a downlink signal to be sent to the terminal device from the core network, for example, when it receives downlink signaling from the Access and Mobility Management Function (AMF) network element, or receives downlink data from the User Plane Function (UPF) network element, the anchor base station sends a paging message (RAN paging) to all cells within the RNA range carried in the RRCRelease message. Moreover, if the RNA range includes cells of one or more neighboring network devices, the anchor base station sends RNA paging to the neighboring network devices through the Xn interface between the anchor base station and the neighboring network devices, so that the neighboring cells are paged within their cells. After receiving the paging message, the terminal device in the RRC inactive state or the RRC idle state will trigger RRC recovery or RRC establishment.
[0120] Since the terminal device may move outside the RNA range configured by the anchor base station, the terminal needs to trigger the RAN update in time so that the serving base station can update the RAN in time to avoid the terminal device not receiving the paging message and affecting the reception of the downlink signal. In one example, for a terminal device in the RRC inactive state, the terminal device can periodically (for example, set a first timer to indicate the duration of triggering the RAN update) send an RRCResumeRequest message to the serving base station, and carry the RRC recovery cause value (Resume Cause) as RNA update (rna-Update) in the RRCResumeRequest message to notify the serving base station to determine whether the terminal device is still in the RAN configured by the anchor base station. The periodic RNA update timer can be started when the terminal device receives the RRCRelease message, and after the timer expires, the terminal device triggers the RRC recovery request. The duration of the timer can be configured by the anchor base station in the RRCRelease message.
[0121] In another example, when the terminal device performs cell reselection, it obtains the physical cell identity (PCID) of the target cell to be accessed through the synchronization signal and physical broadcast channel block (SSB) signal of the target cell, thereby determining whether the PCID of the target cell belongs to the cell list included in the RNA configured by the anchor base station. Or after accessing the target cell, the RNA ID of the RNA where the target cell is located is obtained through the SIB1 (System Information Block) of the target cell, thereby determining whether the RNA ID of the RNA where the target cell is located is the same as the RNA ID configured by the anchor base station. If the terminal device determines that the target cell is not within the RNA range configured by the anchor base station, the terminal device sends an RRCResumeRequest message to the serving base station, and carries the rna-Update reason value in the RRCResumeRequest message to notify the serving base station to determine that the terminal device is no longer in the RAN configured by the anchor base station.
[0122] If the serving base station is not an anchor base station, the serving base station sends a UE context retrieval request (RETRIEVE UE CONTEXT REQUEST) message to the anchor base station after receiving the RRCResumeRequest message, and the UE context retrieval request message carries rna-Update and I-RNTI. The anchor base station obtains the saved context information of the terminal device based on the I-RNTI, and determines whether the terminal device has moved out of the RNA configured by the anchor base station. If the terminal device has moved out of the RNA configured by the anchor base station, the anchor base station sends a UE context retrieval response (RETRIEVE UE CONTEXT RESPONSE) message to the serving base station, which includes the context of the terminal device. The serving base station sends an RRCResume message to the terminal device based on the context of the terminal device, so that the terminal device enters the RRC connected state from the RRC inactive state, and the serving base station continues to maintain the context information of the terminal device. Alternatively, the serving base station may also send an RRCRelease message to the terminal device to keep the terminal device from returning to the RRC inactive state or migrating to the RRCA idle state, and the serving base station indicates the updated RNA in the RRCRelease message.
[0123] If the anchor base station determines that the terminal device is still staying in the RNA, the anchor base station will send a UE context retrieval failure (RETRIEVE UE CONTEXT FAILURE) message to the serving base station, and will not send the context information of the terminal device. The context information is still managed by the anchor base station. The UE context retrieval failure message may include an encapsulated RRCRelease message, and the RRCRelease message carries the suspendConfig information element. The serving base station forwards the RRCRelease message to the terminal device, and the terminal device returns to the RRC inactive state again. In particular, if the terminal device has no business for a long time, the anchor base station may also decide to migrate the terminal device from the RRC inactive state to the RRCA idle state, that is, the anchor base station includes the encapsulated RRCRelease message (excluding suspendConfig) in the UE context retrieval failure message. After the gNB forwards the RRCRelease message to the UE, the UE enters the RRC Idle state.
[0124] Multicast Broadcast Service (MBS): Broadcast communication service refers to a communication service that provides the same service and the same specific content data to all terminal devices in the broadcast coverage area at the same time, that is, all terminal devices in the broadcast coverage area can receive the same data. In NR MBS, broadcast supports reception in RRC idle state, RRC inactive state and RRC connected state. Broadcast adopts point-to-multipoint (PTM) transmission mode, that is, the network device can send a copy of the downlink data of the broadcast session (or called MBS data packet) to multiple terminal devices through the air interface. The terminal device can descramble the received multicast using the common RNTI (G-RNTI). The terminal device can obtain the configuration of the broadcast MBS control channel (MCCH) from the system message of the serving cell (for example, SIB20), receive the second MCCH message according to the configuration of the second MCCH, and determine the broadcast sessions that the serving cell can provide and the configuration of each broadcast session based on the indication of the second MCCH message. Exemplarily, the configuration information of the broadcast session may include the temporary mobile group identity (TMGI) of the broadcast session, the G-RNTI for descrambling the broadcast MTCH, the broadcast MRB configuration, the scheduling information of the broadcast MTCH (such as DRX configuration), the list of neighboring cells providing the broadcast session, etc.
[0125] NR MBS multicast: in the embodiment of the present application, it can be referred to as MBS multicast service, MBS multicast session, multicast service, multicast session, multicast, etc. Typical MBS multicasts may include public safety services (such as earthquake rescue communications, firefighter communications), sports programs or concert broadcasts, etc. MBS multicast can be transmitted using PTP or PTM. The terminal device can apply to join the MBS multicast by performing an authentication process with the core network. The network device then sends multicast configuration information to the terminal device through dedicated signaling, including the identifier of the multicast session that the terminal device requests to receive (for example, TMGI), the configuration of the MRB of the multicast (including one or more of PDCP configuration, RLC configuration, MAC configuration and physical layer configuration), and the G-RNTI for descrambling the multicast MTCH, multicast MTCH scheduling information, etc.
[0126] In Rel-17, MBS multicast only supports transmission in the RRC connected state, and terminal devices can receive multicast sessions in the serving cell, which can be a primary cell (PCell) or a secondary cell (SCell). However, when the number of users participating in multicast in a cell is too large, it may exceed the number of users in the RRC connected state that the cell can accommodate. Therefore, in order to alleviate network congestion, Rel-18 supports terminal devices that join multicast to receive multicast in the RRC inactive state. Terminal devices in the RRC inactive state can receive multicast using PTM, and the multicast configuration information provided by the network device can also be called PTM configuration information. The PTM configuration information may include one or more of the following: an identifier of the multicast that the terminal device requests to receive (such as TMGI), the configuration of the MRB for the multicast (including one or more of PDCP configuration, RLC configuration, MAC configuration, and physical layer configuration), and the G-RNTI for descrambling the multicast MTCH, multicast MTCH scheduling information, etc.
[0127] Currently, the network device provides two configuration methods for the multicast configuration information of the RRC Inacitve state: one is that when the network device sends the RRCRelease message to the terminal device, the multicast configuration information is carried in the RRCRelease message and sent to the terminal device. The other is that the network device sends the multicast configuration information through the first MCCH message. For example, when the network device sends the RRCRelease message to the terminal device, the RRCRelease message carries the configuration of the first MCCH of the cell, so that after the terminal device enters the RRC inacitve state, it receives the first MCCH message according to the configuration of the first MCCH. Alternatively, the network device may also configure the first MCCH in the system message (for example, SIB1), and after receiving the system message, the terminal device in the RRC inactive state obtains the configuration of the first MCCH from the system message, receives the first MCCH message based on the configuration of the first MCCH, and obtains the multicast configuration information of the multicast requested to be received from the first MCCH message. The configuration information of the first MCCH includes at least one of the following: a repetition period and an offset of the first MCCH; a window start position of the first MCCH; a window duration of the first MCCH; and a modification period of the first MCCH.
[0128] It is worth noting that, for the same multicast, the multicast configuration information configured by the network device for the RRC inactive state and the multicast configuration information configured for the RRC connected state may be the same or different.
[0129] After a terminal device in the RRC inacitve state performs cell reselection / cell selection, in the service cell where it resides, it can obtain the multicast configuration information of the service cell for the multicast (assuming it is the first multicast) that the terminal device requests to receive through the first MCCH message of the service cell. If the terminal device cannot obtain the first MCCH message of the service cell, or the first MCCH message does not include the multicast configuration information of the first multicast, then the terminal device needs to request the network device that manages the service cell to restore the RRC connection in order to enter the RRC connected state to obtain the multicast. One possible scenario is that the service cell does not provide the first multicast to the terminal device in the RRC inacitve state, but provides the first multicast to the terminal device in the RRC connected state, then the terminal device can receive the first multicast after entering the RRC connected state. Another possible scenario is that if the service cell does not support the provision of the first multicast, then the terminal device can request the network device to provide the first multicast after entering the RRC connected state.
[0130] In one possible scenario, a terminal device in an RRC inactive state will reselect cells multiple times during movement. After each reselection, if the resident service cell can provide the first multicast, the terminal device will obtain the multicast configuration information for the first multicast based on the first MCCH message of the service cell. The multicast configuration information provided by each service cell may include configuration information of different MRBs, and the terminal device may receive the first multicast based on different MRBs in different service cells. Afterwards, when the terminal device in the RRC inactive state reselects a cell again, the terminal device cannot obtain the multicast configuration information for receiving the first multicast in the RRC inactive state in the selected resident service cell, and the terminal device needs to request the service base station that manages the service cell to restore the RRC connection. The service base station obtains the context information of the terminal device by sending a context retrieval request to the anchor base station of the terminal device. The context information includes the multicast configuration information configured by the anchor base station for the terminal device in the RRC connected state. The serving base station determines the MRB configuration for transmitting the first multicast based on the multicast configuration information. For example, for the same MRB, the configuration of the MRB for use in the connected state is provided in the RRCResume message by means of a delta configuration (or incremental configuration). However, compared with the MRB configuration used to receive the first multicast in the RRC connected state, the terminal device may have modified the configuration of the MRB after entering the RRC inactive state to receive the multicast, and received the multicast in the inactive state based on the modified MRB configuration. In addition, when the terminal device reselects a cell, the reselected cell may also modify the configuration of the MRB. At this time, if the terminal device restores the MRB based on the currently used MRB configuration and the incremental configuration provided by the serving base station in the RRCResume message when restoring the RRC connection, the configuration of the MRB cannot be aligned with the serving base station, resulting in the MRB configuration used by the terminal device being different from the MRB configuration used by the network device, which causes the UE to be unable to correctly receive the first multicast.
[0131] To this end, an embodiment of the present application provides a communication method, whereby a terminal device saves first multicast configuration information in context information, and after restoring an RRC connection, determines a first MRB for transmitting a first multicast according to the first multicast configuration information.
[0132] The communication method provided in this application is exemplarily described below with reference to FIG2 .
[0133] FIG2 is a flow chart of a communication method provided in an embodiment of the present application, which includes:
[0134] S101: A second network device sends first multicast configuration information to a terminal device.
[0135] Exemplarily, the above-mentioned first multicast configuration information is carried in an RRC reconfiguration message (RRCReconfiguration) message. The first multicast configuration information is the configuration information for receiving the first multicast in the RRC connected state. The first multicast configuration information may include a multicast MRB configuration. Exemplarily, the first multicast configuration information may include an identifier of at least one multicast MRB, and the first multicast configuration information also includes at least one of the PDCP configuration, RLC configuration, MAC configuration and physical layer configuration of each MRB. It can be understood that when the terminal device is in the RRC connected state, it can receive the first multicast based on the at least one MRB. The first multicast is a multicast that the terminal device has joined. Exemplarily, the first multicast configuration information includes configuration information of multicast MRB-1.
[0136] In this application, the first multicast may also be replaced by the first MBS multicast, the first multicast session, or the first multicast service.
[0137] After receiving the first multicast configuration information, the terminal device saves the first multicast configuration information locally.
[0138] S102: The second network device sends a first RRC release message to the terminal device, wherein the first RRC release message carries a suspend configuration (suspendConfig).
[0139] The first RRC release message also instructs the terminal device to receive multicast configuration information in the RRC inactive state.
[0140] S103, the terminal device enters the RRC inactive state from the RRC connected state.
[0141] After the terminal device enters the RRC inactive state, it performs cell selection and / or cell reselection. In one example, as the terminal device moves, the terminal device may perform multiple cell reselections.
[0142] For example, after the terminal device enters the RRC Inactive state from the RRC Connected state, it continues to use multicast MRB-1 to receive the first multicast according to the second multicast configuration information indicated in the RRCRelease message.
[0143] For another example, after the terminal device performs cell reselection, the serving cell (assuming it is cell 2) selected for resident may still be the cell managed by the second network device. The terminal device can receive the second multicast configuration information sent by the second network device and receive the first multicast according to the second multicast configuration information in cell 2. The second multicast configuration information can be carried in a system message and / or a multicast MCCH message broadcast by cell 2.
[0144] The second multicast configuration information is the configuration information for receiving the first multicast in the RRC inactive state. Exemplarily, the second multicast configuration information may include the identifier of at least one MRB, and the second multicast configuration information also includes at least one of the PDCP configuration, RLC configuration, MAC configuration and physical layer configuration of each MRB. The second multicast configuration information may come from a second network device, or from a network device corresponding to a service cell where other terminal devices reside. It should be noted that this application does not limit the terminal device to providing the same multicast configuration in the service cell where the terminal device resides in the RRC inactive state, that is, the terminal device receives the second multicast configuration information on cell 2, and the second multicast configuration information received after the cell is reselected to cell 3 may be different from the second multicast configuration information received on cell 2. In this application, the second multicast configuration information is only used to refer to the multicast configuration information used for the terminal device to receive multicast in the RRC inactive state.
[0145] In one example, both the second multicast configuration information and the first multicast configuration information may include configuration information of the first MRB. That is, the second network device configures at least one identical first MRB for transmission of the first multicast in both the RRC inactive state and the RRC connected state, and the terminal device can receive the first multicast based on the first MRB in both the RRC inactive state and the RRC connected state.
[0146] Optionally, after the terminal device performs cell reselection, the service cell selected to reside (assuming it is cell 3) may be a cell managed by a third network device. The terminal device in the RRC inactive state can obtain the second multicast configuration information in the first system message of cell 3 and / or the first MCCH message of cell 3, and receive the first multicast in cell 3 according to the second multicast configuration information.
[0147] Optionally, after the terminal device performs cell reselection, the service cell selected for resident (assuming it is cell 1) may also be the cell managed by the first network device.
[0148] It is understandable that after the terminal device enters the RRC inactive state, it may directly reside in cell 1 through cell reselection, or it may first reside in cell 2 and / or cell 3 and then reside in cell 1.
[0149] S104, the terminal device sends an RRC recovery request message to the first network device.
[0150] In one example, the terminal device needs to receive the first multicast in the RRC inactive state, but cell 1 does not send the second multicast configuration information. At this time, the terminal device can send an RRC recovery request message to the first network device to request to restore the RRC connection.
[0151] Among them, the fact that cell 1 does not send the second multicast configuration information can be understood as: cell 1 does not send the first system information, the above-mentioned first system message is used to configure the first MCCH, and the first MCCH is the multicast MCCH; or, the SIB1 sent by cell 1 does not contain the scheduling information of the first system information; or, the first MCCH message sent by cell 1 does not include the second multicast configuration information.
[0152] In another example, when the terminal device can receive the second multicast configuration information in cell 1 and can receive the first multicast sent by cell 1 in the RRC inactive state according to the second multicast configuration information, when the terminal device has a data transmission requirement, the terminal device can send an RRC recovery request message to the first network device to request to restore the RRC connection.
[0153] For example, the terminal device receives a paging message sent by the first network device and determines based on the paging message that the RRC connection needs to be restored to receive downlink data or downlink control signaling. For another example, the terminal device needs to restore the RRC connection to send uplink data to the first network device.
[0154] Optionally, after determining that cell 1 does not belong to the RNA range configured by the second network device, the terminal device may also send an RRC recovery request message to the first network device to request to restore the RRC connection.
[0155] S105: The first network device sends a context retrieval request message to the second network device.
[0156] S106: The second network device sends a context retrieval response message to the first network device.
[0157] After receiving the context retrieval request message, the second network device sends a context retrieval response message to the first network device, wherein the context information of the terminal device is carried, and the context information includes the first multicast configuration information.
[0158] S107, the first network device sends an RRC recovery message to the terminal device.
[0159] The RRC recovery message includes the third multicast configuration information.
[0160] If the first network device is capable of providing the first multicast, and the third multicast configuration information is configured for the first multicast, and the third multicast configuration information includes the configuration information of at least one MRB, then the first network device can provide the third multicast configuration information for the multicast MRB configured in the first multicast configuration based on the incremental (delta) configuration method. Assuming that the first multicast configuration information and the third multicast configuration information both include the configuration information of the first MRB, then the first network device can provide incremental configuration for the first MRB in the RRCResume message, so as to avoid repeatedly carrying the same configuration and reduce signaling overhead. Accordingly, after receiving the third multicast configuration information, the terminal device restores the first MRB according to the configuration information of the first MRB in the first multicast configuration and the third multicast configuration information.
[0161] S108, the terminal device enters the RRC connected state from the RRC inactive state.
[0162] S109: The terminal device receives a first multicast based on a first MRB, where the first MRB is determined according to the first multicast configuration information and the RRC recovery message.
[0163] Accordingly, after the terminal device enters the RRC connected state, it can receive the first multicast based on the first MRB restored according to the third multicast configuration information carried in the RRC recovery message and the pre-saved first multicast configuration information. In this way, the configuration information of the MRB determined by the first network device and the terminal device is the same. Therefore, the terminal device can correctly receive the first multicast sent by the first network device based on the first MRB.
[0164] Optionally, if the third multicast configuration information also includes the configuration information of the second MRB, but the first multicast configuration information does not include the configuration information of the second MRB, the terminal device can also create a new second MRB, so that the first network device and the terminal device can receive the first multicast based on the first MRB and the second MRB.
[0165] In one possible scenario, based on FIG2 and FIG3 , before S102 above, that is, before the second network device releases the RRC connection between the second network device and the terminal device, the method further includes:
[0166] S110, the terminal device in the RRC connected state receives the first multicast sent by the second network device based on the first multicast configuration information.
[0167] In one possible scenario, if the anchor base station supports the terminal device to receive multicast in a non-connected state, it will carry multicast configuration information in the RRC release message for the terminal device to receive the corresponding multicast in the RRC non-connected state. However, if the RRC release message can only send the multicast configuration information of the primary service cell PCell of the terminal device in the RRC connected state, on the one hand, it limits the flexibility of the anchor base station in providing non-connected multicast configuration through dedicated signaling. On the other hand, when the terminal device selects and resides on other cells after entering the RRC non-connected state, it needs to obtain the system message and multicast MCCH message of the cell to obtain the multicast configuration before it can start receiving multicast services. This will cause interruption of multicast reception and affect the continuity of the terminal device receiving multicast services. One possible scenario is that the terminal device receives multicast services on the secondary service cell SCell in the RRC connected state. When entering the RRC non-connected state, the terminal device may select and reside on the cell again to receive multicast. At this time, the terminal device re-acquires the multicast configuration, which will cause interruption of multicast reception.
[0168] In addition, since it is currently difficult for terminal devices to determine which cell the anchor base station is configured for by carrying the multicast configuration information in the RRC release message, the terminal device needs to re-acquire the first MCCH message of the resident service cell after completing the cell selection to obtain the multicast configuration information corresponding to the service cell, which is not conducive to the continuity of multicast reception and increases the power consumption overhead of the terminal device.
[0169] To address this issue, the present application also provides another communication method, which enables the terminal device to determine the second multicast configuration information sent by the second network device in the first RRC release message, which can be used to receive the first multicast in the first cell in the RRC non-connected state. The first cell can be the main service cell or service cell of the terminal device in the RRC connected state. As a result, after the terminal device selects and resides in the first cell, it can directly use the second multicast configuration information in the first RRC release message to receive the first multicast without having to re-acquire the second multicast configuration information. On the one hand, it reduces the multicast reception interruption caused by re-acquiring the multicast configuration, improves the continuity of multicast reception, and reduces the power consumption overhead of the terminal device; on the other hand, it improves the flexibility of the network device in providing non-connected multicast configuration, and the network device can choose which cell's multicast configuration to provide.
[0170] As shown in FIG4 , which is a flowchart of another communication method provided in an embodiment of the present application, the method includes:
[0171] S401, the second network device sends a first RRC release message to the terminal device, the first RRC release message indicates second multicast configuration information, and the second multicast configuration information is configuration information for receiving the first multicast in the first cell in an RRC non-connected state.
[0172] In the embodiment of the present application, the RRC non-connected state includes an RRC inactive state or an RRC idle state. The first cell may be a primary serving cell (PCell) or a secondary serving cell (SCell).
[0173] In one example, if the terminal device has started receiving the first multicast in the RRC connected state, then when the second network device releases the RRC connection between the terminal device and the service cell, it can send the second multicast configuration information for receiving the multicast in the RRC non-connected state on the service cell where the terminal device received the first multicast in the RRC connected state, and carry it in the first RRC release message to send it to the terminal device.
[0174] Accordingly, when the terminal device receives the first RRC release message, it can obtain the second multicast configuration information carried in the first RRC release message, which is used for receiving the configuration information of the first multicast in the first cell in the RRC non-connected state, wherein the first cell can be the service cell for the terminal device to receive the first multicast when it is in the RRC connected state, or the first cell is a service cell configured with a first common frequency domain resource (CFR), and the first common frequency domain resource is used to transmit the first multicast in the RRC connected state. In this example, the terminal device can determine the first cell based on the cell that receives the multicast service in the connected state, or it can be understood that the second network device indicates the first cell to the terminal device in an implicit manner.
[0175] In this example, the second network device can continue to provide multicast in the RRC non-connected state on the service cell that provides multicast in the RRC connected state, and can use the same time domain / frequency domain resources for the same multicast in the RRC connected state and the RRC non-connected state, thereby saving the overhead of air interface resources and improving resource utilization efficiency.
[0176] Optionally, the first RRC release message includes an identifier of the first cell. That is, the first RRC release message sent by the second network device displays the identifier of the first cell, indicating that the second multicast configuration information indicated in the first RRC release message is configured by the second network device for the first cell. Accordingly, the terminal device can directly determine the cell to which the second multicast configuration information applies based on the identifier of the first cell.
[0177] In one example, the first RRC release message may indicate one or more second multicast configuration information. When the first RRC release message indicates multiple second multicast configuration information, each second multicast configuration information corresponds to a corresponding first cell, that is, the first RRC release message may indicate multiple first cells, and each first cell has a one-to-one correspondence with the second multicast configuration information. Each second multicast configuration information is configuration information for receiving the first multicast in the first cell corresponding to the second multicast configuration information in an RRC non-connected state.
[0178] In an example, the second multicast configuration information includes at least one of an identifier of the first multicast, an activation state of the first multicast, a first MCCH configuration, and a PTM configuration of the first multicast.
[0179] It should be noted that the first MCCH configuration of the second network device is configured for the first cell. The first cell can provide multiple multicasts, and the first MCCH configuration of the multiple multicasts is the same. The multicast identifier, activation state, and PTM configuration are configured by the second network device for each multicast provided by each cell.
[0180] S402, the terminal device enters the RRC non-connected state from the RRC connected state.
[0181] It is understandable that if the first RRC release message carries the suspend configuration, the terminal device is released from the RRC connected state to the RRC inactive state. If the first RRC release message does not carry the suspend configuration, the terminal device is released from the RRC connected state to the RRC idle state.
[0182] The terminal device enters the RRC non-connected state and performs cell selection. Optionally, during the cell selection process, the terminal device may prioritize determining whether the first cell meets the S criterion, that is, determining whether the received power value of the first cell is greater than a first preset threshold, and whether the signal quality of the first cell is greater than a second preset threshold. If the first cell meets the S criterion, the terminal device may prioritize selecting the first cell as the serving cell to reside in the RRC non-connected state.
[0183] In an example, if the terminal device performs cell selection and camps on the first cell, after S402, the method may further include:
[0184] S403: Receive a first multicast in the first cell based on the second multicast configuration information in the RRC unconnected state.
[0185] In this example, the terminal device preferentially resides on the first cell. This allows the terminal device to directly receive the first multicast message using the second multicast configuration information indicated by the second network device via the first RRC release message, eliminating the need to reacquire the second multicast configuration information via the first MCCH message of the first cell. This reduces the power consumption of the terminal device. Furthermore, because the time required to reacquire the second multicast configuration information is saved, the problem of multicast reception interruption caused by RRC state transitions is reduced to a certain extent, thereby improving the efficiency and continuity of multicast reception.
[0186] On the other hand, the second network device can flexibly provide the non-connected multicast configuration and the corresponding cell through dedicated signaling (such as RRC release message). For example, the second network device can use the same configuration to provide multicast services in the same cell in the RRC non-connected state and the RRC connected state, thereby improving resource utilization efficiency.
[0187] In one possible scenario, a terminal device in the RRC inactive state sends an RRC recovery request message to the first network device to request the restoration of the RRC connection when certain trigger conditions are met. By carrying a recovery cause value corresponding to the trigger condition in the RRC recovery request message, the network device is instructed to perform the corresponding operation. However, the current recovery cause value cannot fully indicate the status of the terminal device, resulting in the network device being unable to meet the performance requirements of the terminal device's data transmission.
[0188] To this end, the present application also provides another communication method that can fully reflect the status of the terminal device and improve the resource transmission efficiency of the terminal device. The following is an exemplary description of the communication method provided by the present application in conjunction with the embodiments shown in Figures 5 to 7:
[0189] FIG5 is a flow chart of another communication method provided in an embodiment of the present application, wherein the method includes:
[0190] S501: A second network device sends a first RRC release message to a terminal device, where the first RRC release message indicates a first RNA.
[0191] The first RNA may be indicated by an RNA ID, or may be indicated by an ID of a cell included in the first RNA. The cell included in the first RNA is the cell constituting the first RNA.
[0192] The first RNA is the RNA that the above-mentioned terminal device is in when receiving the first RRC release message.
[0193] The first RRC release message includes a suspend configuration (suspendConfig).
[0194] S502, the terminal device enters the RRC inactive state (RRC Inactive state) from the RRC connected state.
[0195] S503: When the first condition and the second condition are met, an RRC connection recovery request message is sent to the first network device, where the RRC connection recovery request message carries a first cause value.
[0196] The first network device is a network device of a service cell, and the service cell is a cell where the terminal device resides in an RRC inactive state.
[0197] The first condition is that the first timer times out or the service cell does not belong to the first RNA. The first timer is a timer indicating the RAN update period (for example, the first timer is T380). The first timer can be started when the terminal device receives the first RRC release message, and the duration of the first timer is configured in the first RRC release message. When the first timer times out, the terminal device may need to update the RAN. The fact that the service cell does not belong to the first RNA can be determined by the SIB1 of the service cell. Specifically, when the terminal device receives the SIB1 of the service cell, and the RNA identifier indicating the service cell in the SIB1 of the service cell is different from the RNA identifier (first RNA) where the terminal device is located, the terminal device determines that the service cell does not belong to the first RNA. Alternatively, the fact that the service cell does not belong to the first RNA can also be determined based on the identifier of the service cell. Specifically, when the first RRC release message indicates the service cells constituting the first RNA, the terminal device determines that the resident service cell does not belong to the service cell of the first RNA, then determines that the service cell does not belong to the first RNA.
[0198] The second condition is that the multicast is not received in the RRC inactive state, or that the multicast is received in the RRC inactive state and the serving cell sends the second multicast configuration information. The so-called "not receiving the multicast in the RRC inactive state" can be understood as: the first RRC release message is not configured to receive the multicast in the RRC inactive state, that is, the terminal device does not need to receive the multicast in the RRC inactive state.
[0199] The so-called receiving multicast in the RRC inactive state and the serving cell sending the second multicast configuration information can be understood as: the first RRC release message configures the reception of multicast in the RRC inactive state, and the terminal device is able to receive the second multicast configuration information sent by the serving cell. In other words, the terminal device needs to receive multicast in the RRC inactive state, and the terminal device can also obtain the status of the serving cell's multicast configuration in the RRC inactive state.
[0200] The second multicast configuration information is configuration information for receiving the first multicast in the serving cell in the RRC inactive state, and includes at least one of the first multicast identifier, the first multicast G-RNTI, and the first multicast MRB configuration.
[0201] The first multicast is a multicast that the terminal device applies to join and is in an activated state.
[0202] The serving cell may carry the second multicast configuration information in a first MCCH message and send it to the terminal device. The first MCCH message is an MCCH message used for multicast configuration.
[0203] In an example, the first cause value may be a newly set recovery cause value, indicating that the terminal device may need to perform an RNA update but does not need to obtain a multicast configuration.
[0204] Optionally, the first reason value is RNA update. In this example, the condition for using "RNA update" as the recovery reason value is reset. Only when the first condition and the second condition are met will the terminal device use "RNA update" as the recovery reason value and request the first network device to restore the RRC connection. This avoids the situation where, when the terminal device is simultaneously updated with RNA and needs to obtain multicast configuration, the first network device still releases the terminal device to the RRC non-connected state based on the reason value of the RNA update, and does not provide the terminal device with the multicast configuration of the RRC inactive state, resulting in the terminal device being unable to successfully receive multicast.
[0205] FIG6 is a flow chart of another communication method provided in an embodiment of the present application, wherein the method includes:
[0206] S601: The second network device sends a first RRC release message to the terminal device, where the first RRC release message indicates a first RNA.
[0207] S602, the terminal device enters the RRC inactive state from the RRC connected state.
[0208] S603, when the first condition and the third condition are met, an RRC connection recovery request message is sent to the first network device; the RRC connection recovery request message carries a second cause value, and the second cause value is one of mobile originating data mo-Data, mobile originating signaling mo-Signalling, mobile terminal access mt-Access, or multicast broadcast service access.
[0209] The first condition is that the first timer times out or the serving cell does not belong to the first RNA.
[0210] The third condition is that the first RRC release message indicates that multicast is received in the RRC inactive state and the serving cell does not send the second multicast configuration information; the second multicast configuration information is the configuration information of the first multicast received in the serving cell in the RRC inactive state.
[0211] The fact that the serving cell does not send the second multicast configuration information may be that the first MCCH message sent by the serving cell does not include the second multicast configuration information. It is understood that the first MCCH message is an MCCH message used to configure multicast. The first MCCH message of the serving cell may include multicast configuration information for one or more multicasts that the serving cell can currently provide, but does not include the second multicast configuration information, indicating that the serving cell may not provide the first multicast, or that the serving cell does not provide transmission of the first multicast in an RRC inactive state.
[0212] Alternatively, the serving cell not sending the second multicast configuration information may also mean that the serving cell does not send the first system message, where the first system message is used to send the configuration information of the first MCCH. The configuration information of the first MCCH is used by the terminal device to receive the first MCCH message. Exemplarily, the configuration information of the first MCCH includes at least one of the following: a repetition period and offset of the first MCCH, a window starting position of the first MCCH, a window duration of the first MCCH, and a modification period of the first MCCH.
[0213] Alternatively, the serving cell does not send the second multicast configuration may also be: the system information SIB1 of the serving cell does not include scheduling information of the first system message, and the first system message is used to send configuration information of the first MCCH.
[0214] The MBS access indication indicates the MBS-related access type. The MBS access indication can be understood as an MBS resume indication or a multicast resume indication. It indicates that the terminal device is unable to receive multicast in the RRC inactive state; or that the terminal device is unable to receive multicast configuration information in the RRC inactive state; or that the terminal device is requesting to enter the RRC connected state to receive multicast.
[0215] Based on the communication method provided in the embodiment of the present application, when the terminal device simultaneously updates RNA and needs to re-acquire the multicast configuration, one of mobile origin data mo-Data, mobile origin signaling mo-Signalling, mobile terminal access mt-Access, or multicast broadcast service access is used as the recovery reason value to ensure that the first network device can obtain the terminal device context from the second network device (last serving gNB) based on the RRC recovery request message of the terminal device, thereby allowing the terminal device to enter the RRC connected state and provide multicast to the terminal device; or provide the terminal device with the RRC inactive state multicast configuration and provide multicast to the inactive terminal device, thereby ensuring that the terminal device can smoothly receive the multicast and improving the multicast reception efficiency.
[0216] FIG7 is a flow chart of another communication method provided in an embodiment of the present application, wherein the method includes:
[0217] S701: The second network device sends a first RRC release message to the terminal device, where the first RRC release message indicates a first RNA.
[0218] S702, the terminal device enters the RRC inactive state from the RRC connected state.
[0219] S703. When the first condition and the third condition are met, an RRC connection recovery request message is sent to the first network device; the RRC connection recovery request message carries a second cause value, the second cause value is a third cause value, and the third cause value indicates an MBS access indication and an RNA update.
[0220] The description of the first condition and the third condition may be specifically referred to the description in S603 above, and will not be set here.
[0221] S704: The first network device determines whether it can provide RRC inactive multicast.
[0222] After receiving the RRC connection recovery request message, the first network device first determines whether the first network device can provide RRC inactive multicast. If it can provide RRC inactive multicast, the process jumps to step S705 to continue, otherwise the process jumps to step S713 to continue.
[0223] S705: The first network device sends a context retrieval request message to the second network device, where the context retrieval request message carries a third cause value.
[0224] Optionally, the context retrieval request message may also carry a set of RRC inactive multicast identifiers that can be provided by the first network device, and the set of multicast identifiers may include the identifier of the first multicast, or may not include the identifier of the first multicast.
[0225] S706: The second network device determines whether the serving cell belongs to the first RNA.
[0226] After receiving the context retrieval request message, the second network device may first determine whether the serving cell belongs to the first RNA based on the third cause value. If the serving cell belongs to the first RNA, the second network device jumps to step S707 to continue execution, otherwise jumps to step S710 to continue execution.
[0227] S707: The second network sends a context retrieval failure message to the first network device, where the context retrieval failure message carries the second RRC release message and the first multicast identifier.
[0228] When the serving cell belongs to the first RNA, the terminal device can continue to maintain the RRC inactive state. Therefore, the second network device sends a second RRC release message and the identifier of the first multicast to the first network device to instruct the first network device to maintain the RRC inactive state of the terminal device and provide the terminal device with the multicast configuration information of the first multicast.
[0229] In one example, if the context retrieval request message carries a set of identifiers of multicasts in the RRC inactive state that the first network device can provide, the second network device may also first determine, based on the set, whether the second network device can provide the first multicast in the RRC inactive state. If the set includes the identifier of the first multicast and the serving cell belongs to the first RNA, the second network device executes S707.
[0230] If the set does not include the identifier of the first multicast, one possible scenario is that the first network device has not yet started providing the first multicast. Therefore, the second network device may also execute S707 to send the identifier of the first multicast to the first network device, so that the first network device starts providing the first multicast. Another possible scenario is that the first network device cannot provide RRC non- or dynamic first multicast. In this example, the second network device may also send a context retrieval response message to the first network device to enable the first network device to restore the RRC connection with the terminal device, so that the terminal device can receive the first multicast in the RRC connected state.
[0231] S708: The first network device sends second multicast configuration information and a second RRC release message to the terminal device.
[0232] The first network device may obtain the second multicast configuration information according to the identifier of the first multicast.
[0233] For example, if the RRC inactive multicasts that the first network device can provide include the first multicast, the first network device can directly determine the pre-configured second multicast configuration information based on the identifier of the first multicast. If the RRC inactive multicasts that the first network device can provide do not include the first multicast, one possible scenario is that the first network device has not yet started providing the first multicast. Therefore, when the terminal device receives the identifier of the first multicast, it can configure the second multicast configuration information and start providing the first multicast.
[0234] Another possible scenario is that the first network device can provide the first multicast in the RRC connected state, but does not provide the first multicast in the RRC inactive state. In this case, upon receiving the identifier of the first multicast, the first network device can send an RRC resume message to the terminal device, so that the terminal device enters the RRC connected state from the RRC inactive state and receives the first multicast in the RRC connected state.
[0235] In an embodiment of the present application, the second multicast configuration information may be carried in a second RRC release message and sent to the terminal device. Alternatively, the second multicast configuration information may also be carried in a first system message and / or a first MCCH message of the serving cell.
[0236] S709: The terminal device receives the first multicast according to the second configuration information.
[0237] S710: The second network sends a context retrieval response message to the first network device, where the context retrieval response message includes the context of the terminal device.
[0238] S711. The first network device sends an RRC recovery message to the terminal device according to the context of the terminal device.
[0239] S712, entering the RRC connected state from the RRC inactive state.
[0240] After the terminal device enters the RRC connection state, it can request the first network device to receive the first multicast. After obtaining the multicast configuration information sent by the first network device, it receives the first multicast sent by the first network device in the RRC connection state according to the multicast configuration information.
[0241] S713: The first network device sends a context retrieval request message to the second network device, where the context retrieval request message does not carry the third cause value.
[0242] S714: The second network sends a context retrieval response message to the first network device, where the context retrieval response message includes the context of the terminal device.
[0243] After the second network receives the context retrieval request message, since the context retrieval request message does not carry a restoration reason value, the second network device can assume that the RRC connection between the first network device and the terminal device needs to be restored, so that the second network device can directly carry the context of the terminal device in the context retrieval response message and send it to the first network device, and the first network device maintains the context of the terminal device.
[0244] S715. The first network device sends an RRC recovery message to the terminal device according to the context of the terminal device.
[0245] S716, the terminal device enters the RRC connected state from the RRC inactive state.
[0246] Based on the communication method provided in the embodiment of the present application, when the terminal device simultaneously updates RNA and needs to re-acquire the multicast configuration, by setting the third cause value as the recovery cause value, it is ensured that the first network device can obtain the terminal device context from the second network device (last serving gNB) based on the RRC recovery request message of the terminal device, thereby allowing the terminal device to enter the RRC connected state and provide multicast to the terminal device; or provide the terminal device with the RRC inactive state multicast configuration and provide multicast to the inactive terminal device, thereby ensuring that the terminal device can smoothly receive the multicast and improving the multicast reception efficiency.
[0247] The various embodiments in this application can be used independently or in combination. The different steps in each embodiment can also be used independently or in combination. If there are similar steps in different embodiments, their descriptions can be referenced and compared with each other.
[0248] The signal transmission method of the embodiment of the present application is described in detail above with reference to Figures 1 to 7. The communication device of the embodiment of the present application is described in detail below with reference to Figures 8 to 13.
[0249] In this embodiment, terminal devices and network devices can be divided into functional modules according to the above method. For example, each function can be divided into separate functional modules, or two or more functions can be integrated into a single processing module. The integrated modules can be implemented in hardware. It should be noted that the module division in this embodiment is illustrative and represents only a logical functional division. In actual implementation, other division methods may be used.
[0250] It should be noted that the relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.
[0251] The terminal device and network device provided in the embodiments of the present application are used to perform any of the communication methods provided in the above-mentioned method embodiments, thereby achieving the same effect as the above-mentioned implementation method. In the case of an integrated unit, the terminal device or network device may include a processing module, a storage module, and a communication module. Among them, the processing module can be used to control and manage the actions of the terminal device or network device. For example, it can be used to support the terminal device or network device to execute the steps performed by the processing unit. The storage module can be used to support the storage of program code and data, etc. The communication module can be used to support communication between the terminal device or network device and other devices.
[0252] The processing module may be a processor or a controller. It may implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of digital signal processing (DSP) and a microprocessor, and so on. The storage module may be a memory. The communication module may specifically be a device that interacts with other electronic devices, such as a radio frequency circuit, a Bluetooth chip, or a Wi-Fi chip.
[0253] For example, Figure 8 shows a schematic block diagram of a communication device 500 of an embodiment of the present application. The communication device 500 may correspond to the terminal device described in the above-mentioned communication method, or may be a chip or component applied to the terminal device. Moreover, each module or unit in the communication device 500 is respectively used to execute each action or processing process performed by the terminal device in any one of the above-mentioned communication methods.
[0254] As shown in FIG8 , the communication device 500 includes a transceiver unit 510 and a processing unit 520. The transceiver unit 510 is configured to perform specific signal transmission and reception under the drive of the processing unit 520.
[0255] Furthermore, the communication device 500 may also include a storage unit, and the transceiver unit 510 may be a transceiver, an input / output interface, or an interface circuit. The storage unit is used to store instructions executed by the transceiver unit 510 and the processing unit 520. The transceiver unit 510, the processing unit 520, and the storage unit are coupled to each other. The storage unit stores instructions, the processing unit 520 is used to execute the instructions stored in the storage unit, and the transceiver unit 510 is used to perform specific signal transmission and reception under the control of the processing unit 520.
[0256] It should be understood that the specific process of each unit in the communication device 500 executing the above corresponding steps can be referred to the description related to the terminal device in the communication method in the previous text. For the sake of brevity, it is not repeated here.
[0257] Optionally, the transceiver unit 510 may include a receiving unit (module) and a sending unit (module), which are used to execute the steps of the terminal device receiving information and sending information in each embodiment of the aforementioned communication method.
[0258] It should be understood that the transceiver unit 510 can be a transceiver, an input / output interface, or an interface circuit. The storage unit can be a memory. The processing unit 520 can be implemented by a processor. As shown in Figure 9, the communication device 600 can include a processor 610, a memory 620, a transceiver 630, and a bus system 640. The various components of the communication device 600 are coupled together via the bus system 640. In addition to including a data bus, the bus system 640 may also include a power bus, a control bus, and a status signal bus. However, for the sake of clarity, in Figure 9, various buses are labeled as the bus system 640. For ease of illustration, Figure 9 is only schematically drawn.
[0259] The communication device 500 shown in FIG8 or the communication device 600 shown in FIG9 can implement the steps performed by the terminal device in each embodiment of the aforementioned communication method. Similar descriptions can refer to the descriptions of the corresponding methods described above. To avoid repetition, they will not be repeated here.
[0260] The communication device 500 shown in FIG. 8 or the communication device 600 shown in FIG. 9 may be a terminal device.
[0261] Figure 10 shows a schematic block diagram of a communication device 700 of an embodiment of the present application. The communication device 700 may correspond to the network device described in the above communication method, or may be a chip or component applied to the network device. Moreover, each module or unit in the communication device 700 is respectively used to execute each action or processing process performed by the network device in the above communication method.
[0262] As shown in FIG10 , the communication device 700 may include a processing unit 710 and a transceiver unit 720. The transceiver unit 720 is configured to perform specific signal transmission and reception under the drive of the processing unit 710.
[0263] It should be understood that the specific process of each unit in the communication device 700 executing the above corresponding steps can be referred to the description related to the network equipment in the communication method in the previous text. For the sake of brevity, it is not repeated here.
[0264] Optionally, the transceiver unit 720 may include a receiving unit (module) and a sending unit (module), configured to execute the steps of the network device receiving information and sending information in each embodiment of the aforementioned communication method.
[0265] Furthermore, the communication device 700 may also include a storage unit. The transceiver unit 720 may be a transceiver, an input / output interface, or an interface circuit. The storage unit is used to store instructions executed by the transceiver unit 720 and the processing unit 710. The transceiver unit 720, the processing unit 710, and the storage unit are coupled to each other. The storage unit stores instructions, the processing unit 710 is used to execute the instructions stored in the storage unit, and the transceiver unit 720 is used to perform specific signal transmission and reception under the control of the processing unit 710.
[0266] It should be understood that the transceiver unit 720 may be a transceiver, an input / output interface, or an interface circuit. The storage unit may be a memory. The processing unit 710 may be implemented by a processor. As shown in FIG11 , the communication device 800 may include a processor 810, a memory 820, and a transceiver 830.
[0267] The communication device 700 shown in FIG10 or the communication device 800 shown in FIG11 can implement the steps performed by the network device in the embodiment of the aforementioned communication method. Similar descriptions can refer to the descriptions of the corresponding methods described above. To avoid repetition, they will not be repeated here.
[0268] It should also be understood that the communication device 700 shown in FIG. 10 or the communication device 800 shown in FIG. 11 may be a network device.
[0269] It should also be understood that the division of units in the above device is merely a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. Moreover, the units in the device can all be implemented in the form of software called through processing elements; or all be implemented in the form of hardware; or some units can be implemented in the form of software called through processing elements, and some units can be implemented in the form of hardware. For example, each unit can be a separately established processing element, or it can be integrated into a certain chip of the device. In addition, it can also be stored in a memory in the form of a program, and called by a certain processing element of the device to execute the function of the unit. Here, the processing element can also be called a processor, which can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each unit above can be implemented by the integrated logic circuit of the hardware in the processor element or in the form of software called through the processing element.
[0270] In one example, the unit in any of the above devices may be one or more integrated circuits configured to implement the above method, such as one or more application specific integrated circuits (ASICs), or one or more digital signal processors (DSPs), or one or more field programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms. For another example, when the unit in the device can be implemented in the form of a processing element scheduler, the processing element may be a general-purpose processor, such as a central processing unit (CPU) or other processor that can call a program. For another example, these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).
[0271] Figure 12 is a schematic diagram of the structure of a terminal device 900 provided in this application. The above-mentioned communication device 500 or communication device 600 can be configured in the terminal device 900. Alternatively, the communication device 600 or communication device 500 itself can be the terminal device 900. In other words, the terminal device 900 can perform the actions performed by the terminal device in the above-mentioned communication method. Optionally, for ease of explanation, Figure 12 only shows the main components of the terminal device. As shown in Figure 12, the terminal device 900 includes a processor, memory, control circuitry, an antenna, and input / output devices.
[0272] The processor is primarily used to process communication protocols and communication data, control the entire terminal device, execute software programs, and process software program data, such as supporting the terminal device in performing the actions described in the above-mentioned signal transmission method embodiments. The memory is primarily used to store software programs and data, such as the antenna port indication table described in the above-mentioned embodiments. The control circuit is primarily used to convert baseband signals into radio frequency signals and process radio frequency signals. The control circuit and antenna together can also be called a transceiver, which is primarily used to transmit and receive radio frequency signals in the form of electromagnetic waves. Input and output devices, such as touch screens, displays, and keyboards, are primarily used to receive data input by the user and output data to the user.
[0273] When the terminal device is turned on, the processor can read the software program in the storage unit, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be sent wirelessly, the processor performs baseband processing on the data to be sent and outputs the baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal and then transmits the radio frequency signal to the outside in the form of electromagnetic waves through the antenna. When data (such as the first configuration information mentioned above) is sent to the terminal device, the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor. The processor converts the baseband signal into data and processes the data.
[0274] Those skilled in the art will appreciate that, for ease of explanation, FIG12 shows only one memory and processor. In an actual terminal device, multiple processors and memories may exist. The memory may also be referred to as a storage medium or storage device, etc., which is not limited in the present embodiment.
[0275] For example, a processor may include a baseband processor and a central processing unit (CPU). The baseband processor is primarily responsible for processing communication protocols and communication data, while the CPU is primarily responsible for controlling the entire terminal device, executing software programs, and processing data from software programs. The processor in Figure 12 integrates the functions of both the baseband processor and the CPU. Those skilled in the art will appreciate that the baseband processor and the CPU may also be independent processors interconnected via a bus or other technology. Those skilled in the art will appreciate that a terminal device may include multiple baseband processors to accommodate different network standards, multiple CPUs to enhance its processing capabilities, and that the various components of the terminal device may be connected via various buses. The baseband processor may also be referred to as a baseband processing circuit or a baseband processing chip. The CPU may also be referred to as a central processing circuit or a central processing chip. The functionality for processing communication protocols and communication data may be built into the processor or stored as a software program in a storage unit, with the processor executing the software program to implement the baseband processing functionality.
[0276] For example, in the embodiment of the present application, the antenna and control circuit with transceiver functions can be regarded as the transceiver unit 901 of the terminal device 900, and the processor with processing function can be regarded as the processing unit 902 of the terminal device 900. As shown in Figure 12, the terminal device 900 includes a transceiver unit 901 and a processing unit 902. The transceiver unit can also be referred to as a transceiver, a transceiver, a transceiver device, etc. Optionally, the device used to implement the receiving function in the transceiver unit 901 can be regarded as a receiving unit, and the device used to implement the transmitting function in the transceiver unit 901 can be regarded as a transmitting unit, that is, the transceiver unit 901 includes a receiving unit and a transmitting unit. For example, the receiving unit can also be referred to as a receiver, a receiver, a receiving circuit, etc., and the transmitting unit can be referred to as a transmitter, a transmitter, or a transmitting circuit, etc.
[0277] Figure 13 is a structural diagram of a network device 1000 provided in an embodiment of the present application, which can be used to implement the functions of the network device in the above method. The network device 1000 includes one or more radio frequency units, such as a remote radio unit (RRU) 1001 and one or more baseband units (BBU) (also known as digital units, DU) 1002. The RRU 1001 can be called a transceiver unit, a transceiver, a transceiver circuit, or a transceiver, etc., and may include at least one antenna 10011 and a radio frequency unit 10010. The RRU 1001 part is mainly used for receiving and transmitting radio frequency signals and converting radio frequency signals into baseband signals, for example, for sending signaling messages in the above embodiment to terminal devices. The BBU 1002 part is mainly used for baseband processing, controlling network devices, etc. The RRU 1001 and BBU 1002 can be physically set together or physically separated, that is, a distributed base station.
[0278] The BBU 1002 is the control center of the network device, which can also be called a processing unit. It is mainly used to perform baseband processing functions such as channel coding, multiplexing, modulation, spread spectrum, etc. For example, the BBU (processing unit) 1002 can be used to control the network device to execute the operation process of the network device in the above method embodiment.
[0279] In one example, the BBU 1002 may be composed of one or more single boards, and the multiple single boards may jointly support a wireless access network of a single access standard (such as an LTE system or a 5G system), or may respectively support wireless access networks of different access standards. The BBU 1002 also includes a memory 10021 and a processor 10022. The memory 10021 is used to store necessary instructions and data. For example, the memory 10021 stores the antenna port indication table in the above embodiment, etc. The processor 10022 is used to control the network device to perform necessary actions, such as controlling the network device to execute the operation process of the network device in the above method embodiment. The memory 10021 and the processor 10022 can serve one or more single boards. That is, a memory and a processor can be set separately on each single board. Alternatively, multiple single boards may share the same memory and processor. In addition, necessary circuits can also be set on each single board.
[0280] In one possible implementation, with the development of system-on-chip (SoC) technology, all or part of the functions of parts 1002 and 1001 can be implemented using SoC technology. For example, they can be implemented using a network device function chip that integrates a processor, memory, antenna interface, and other components. Programs for network device-related functions are stored in the memory, and the processor executes the programs to implement the network device-related functions. Optionally, the network device function chip can also read memory external to the chip to implement the network device-related functions.
[0281] It should be understood that the structure of the network device illustrated in FIG13 is only one possible form and should not constitute any limitation to the embodiments of the present application. The present application does not exclude the possibility of other forms of network device structures that may appear in the future.
[0282] It should be understood that in the embodiments of the present application, the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.
[0283] It should also be understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM), and direct rambus RAM (DR RAM).
[0284] The above embodiments can be implemented in whole or in part by software, hardware, firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer program are loaded or executed on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that contains one or more available media sets. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium. The semiconductor medium can be a solid-state drive.
[0285] An embodiment of the present application also provides a communication system, which includes: the above-mentioned terminal device and the above-mentioned network device.
[0286] The present invention also provides a computer-readable medium for storing computer program code, wherein the computer program includes instructions for executing the signal transmission method provided in the above-mentioned communication method. The computer-readable medium may be a read-only memory (ROM) or a random access memory (RAM), which is not limited in the present invention.
[0287] The present application also provides a computer program product, which includes instructions. When the instructions are executed, the terminal device performs terminal device operations corresponding to the above method, or the network device performs network device operations corresponding to the above method.
[0288] The present application also provides a chip system, comprising: a processing unit and a communication unit. The processing unit may be, for example, a processor, and the communication unit may be, for example, an input / output interface, a pin, or a circuit. The processing unit may execute computer instructions to cause the chip within the communication device to perform any of the signal transmission methods provided in the above-mentioned embodiments of the present application.
[0289] Optionally, any one of the communication devices provided in the above-mentioned embodiments of the present application may include the chip system.
[0290] Optionally, the computer instructions are stored in a storage unit.
[0291] Optionally, the storage unit is a storage unit within the chip system, such as a register, a cache, etc. The storage unit may also be a storage unit within the terminal device that is located outside the chip system, such as a ROM or other types of static storage devices that can store static information and instructions, RAM, etc. Wherein, the processor mentioned in any of the above may be a CPU, a microprocessor, an ASIC, or one or more integrated circuits for controlling the program execution of the above-mentioned method for main system information transmission. The processing unit and the storage unit may be decoupled and respectively arranged on different physical devices, and connected by wired or wireless means to implement the respective functions of the processing unit and the storage unit, so as to support the chip system to implement the various functions in the above-mentioned embodiments. Alternatively, the processing unit and the memory may also be coupled on the same device.
[0292] The terms "uplink" and "downlink" appearing in this application are used to describe the direction of data / information transmission in specific scenarios. For example, the "uplink" direction generally refers to the direction of data / information transmission from the terminal device to the network side, or the direction of data / information transmission from a distributed unit to a centralized unit. The "downlink" direction generally refers to the direction of data / information transmission from the network side to the terminal device, or the direction of data / information transmission from a centralized unit to a distributed unit. It can be understood that "uplink" and "downlink" are only used to describe the transmission direction of data / information, and the specific starting and ending devices of the data / information transmission are not limited.
[0293] Various objects such as various messages / information / equipment / network elements / systems / devices / actions / operations / processes / concepts that may appear in this application are named. It can be understood that these specific names do not constitute a limitation on the relevant objects. The names assigned may change with factors such as scenarios, contexts or usage habits. The understanding of the technical meaning of the technical terms in this application should be mainly determined from the functions and technical effects embodied / executed in the technical solutions.
[0294] Those skilled in the art will appreciate that the methods in the embodiments of the present application can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, they can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instruction is loaded and executed on a computer, the process or function described in the embodiments of the present application is executed in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program or instruction can be stored in a computer-readable storage medium or transmitted via the computer-readable storage medium. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server that integrates one or more available media.
[0295] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0296] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the unit is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0297] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.
[0298] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
[0299] Those skilled in the art will appreciate that all or part of the process steps in the above-described method embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program can include the process steps in the above-described method embodiments. The aforementioned storage medium can include various media capable of storing program code, such as ROM or random access memory (RAM), magnetic disks, or optical disks.
[0300] The naming or numbering of steps in this application does not mean that the steps in the method flow must be executed in the time / logical sequence indicated by the naming or numbering. The execution order of the named or numbered process steps can be changed according to the technical purpose to be achieved, as long as the same or similar technical effects can be achieved.
[0301] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant description of other embodiments.
[0302] It should be understood that in the description of this application and the appended claims, the terms "comprises," "includes," "has," and any variations thereof are intended to cover non-exclusive inclusions and mean "including but not limited to," unless otherwise specifically emphasized. For example, a process, method, system, product, or apparatus that includes a series of steps or modules is not necessarily limited to those steps or modules explicitly listed, but may include other steps or modules not explicitly listed or inherent to the process, method, product, or apparatus.
[0303] In the description of this application, unless otherwise specified, " / " indicates that the objects associated before and after are in an "or" relationship, for example, A / B can represent A or B; "and / or" in this application is used to describe the association relationship of associated objects, indicating that three relationships can exist, for example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural.
[0304] Furthermore, in the description of this application, unless otherwise specified, "plurality" refers to two or more than two. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, "at least one of a, b, or c" can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or plural.
[0305] As used in this specification and the appended claims, the term "if" can be interpreted as "when" or "upon" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrase "if it is determined" or "if [described condition or event] is detected" can be interpreted as meaning "upon determination" or "in response to determining" or "upon detection of [described condition or event]" or "in response to detecting [described condition or event]," depending on the context.
[0306] In addition, in the description of this application specification and the appended claims, the terms "first," "second," etc. are used to distinguish similar objects, and are not necessarily used to describe a specific order or precedence, nor should they be understood to indicate or imply relative importance or implicitly specify the number of technical features indicated. It should be understood that the terms used in this manner are interchangeable where appropriate, so that the embodiments described herein can be implemented in an order other than that illustrated or described herein; and features specified as "first" or "second" may explicitly or implicitly include at least one of such features.
[0307] In the embodiments of this application, words such as "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplarily" or "for example" in the embodiments of this application should not be interpreted as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplarily" or "for example" is intended to present the relevant concepts in a concrete manner.
[0308] References to "one embodiment" or "some embodiments" in this specification mean that a particular feature, structure, or characteristic described in conjunction with the embodiment is included in one or more embodiments of the present application. Thus, phrases such as "in one embodiment," "in some embodiments," "in other embodiments," and "in yet other embodiments" appearing in various places in this specification do not necessarily refer to the same embodiment, but rather mean "one or more but not all embodiments," unless otherwise specifically emphasized.
[0309] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some or all of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.
Claims
1. A communication method, characterized in that: The method comprises: Sending a radio resource control RRC recovery request message to the first network device; Receiving an RRC recovery message sent by the first network device; Enter the RRC connected state from the RRC inactive state; A first multicast is received based on a first multicast broadcast service wireless bearer MRB, wherein the first MRB is determined by the RRC recovery message and first multicast configuration information, wherein the first multicast configuration information is obtained from a second network device, and the second network device is a network device of the last serving cell in an RRC connected state.
2. The communication method according to claim 1, characterized in that: Before sending the RRC recovery request message to the first network device, the method includes: Receiving the first multicast configuration information sent by the second network device in the RRC connected state; receiving the first multicast based on the first MRB; Receiving a first RRC release message sent by the second network device; Enter the RRC inactive state from the RRC connected state.
3. The communication method according to claim 2, characterized in that: After entering the RRC inactive state from the RRC connected state and before sending the RRC recovery request message to the first network device, the method further includes: The first multicast is received according to the second multicast configuration information.
4. The communication method according to claim 3, characterized in that: The second multicast configuration information is sent by the first network device, the second network device or a third network device, and the third network device is a network device of a serving cell in an RRC inactive state.
5. The communication method according to claim 3 or 4, characterized in that: The first multicast configuration information and the second multicast configuration information both include configuration information of the first MRB.
6. The communication method according to any one of claims 1 to 5, characterized in that: The first multicast configuration information includes an identifier of the first MRB, and the first multicast configuration information also includes at least one of a packet data channel PDCP configuration, a radio link control RLC configuration, a medium access control MAC configuration, and a physical layer configuration of the first MRB.
7. The communication method according to any one of claims 1 to 6, characterized in that: The method comprises: Receive a first radio resource control RRC release message sent by the second network device, where the first RRC release message indicates second multicast configuration information, where the second multicast configuration information is configuration information for receiving the first multicast in the first cell in an RRC non-connected state; Enter RRC disconnected state from RRC connected state.
8. The method according to claim 7, characterized in that The first cell is a serving cell that receives the first multicast in an RRC connected state.
9. The method according to claim 7, characterized in that: The first cell is a secondary serving cell SCell that receives the first multicast in the RRC connected state.
10. A communication method, characterized in that: The method comprises: Receiving a first radio resource control RRC release message sent by a second network device, where the first RRC release message indicates second multicast configuration information, where the second multicast configuration information is configuration information for receiving the first multicast in the first cell in an RRC non-connected state; Enter RRC disconnected state from RRC connected state.
11. The communication method according to claim 10, characterized in that: After entering the RRC non-connected state from the RRC connected state, the method further includes: In case of cell selection and residing on the first cell, the first multicast is received in the first cell based on the second multicast configuration information in an RRC non-connected state.
12. The communication method according to claim 11, characterized in that: When performing cell selection, the first cell is preferentially selected as the serving cell.
13. The communication method according to any one of claims 10 to 12, characterized in that: The first RRC release message includes an identifier of the first cell.
14. The communication method according to any one of claims 10 to 13, characterized in that: The first cell is a service cell configured with a first common frequency domain resource CFR, and the first common frequency domain resource is used to transmit the first multicast.
15. The communication method according to any one of claims 10 to 14, characterized in that: The second multicast configuration information includes at least one of an identifier of the first multicast, an activation state of the first multicast, a multicast broadcast service control channel MCCH configuration, and a point-to-multipoint PTM configuration of the first multicast.
16. The method according to any one of claims 10 to 15, characterized in that: The first cell is a serving cell that receives the first multicast in an RRC connected state.
17. The method according to any one of claims 10 to 15, characterized in that: The first cell is a secondary serving cell SCell that receives the first multicast in the RRC connected state.
18. A communication method, characterized in that: The method comprises: A first radio resource control (RRC) release message is sent to a terminal device, wherein the first RRC release message indicates second multicast configuration information, and the second multicast configuration information is configuration information for receiving the first multicast in the first cell in an RRC non-connected state.
19. The communication method according to claim 18, characterized in that: The first RRC release message includes an identifier of the first cell.
20. The communication method according to claim 19, characterized in that: The first cell is a service cell configured with a first common frequency domain resource CFR, and the first common frequency domain resource is used to transmit the first multicast.
21. The communication method according to any one of claims 18 to 20, characterized in that: The second multicast configuration information includes at least one of an identifier of the first multicast, an activation state of the first multicast, a multicast broadcast service control channel MCCH configuration, and a point-to-multipoint PTM configuration of the first multicast.
22. A communication method, characterized in that: The method comprises: Receiving a first radio resource control RRC release message sent by a second network device, wherein the first RRC release message indicates that the first radio access network notifies an area RNA; Enter RRC inactive state from RRC connected state; When the first condition is met and the second condition is met, an RRC connection recovery request message is sent to a first network device, where the first network device is a network device of a serving cell, and the first condition is that a first timer times out or the serving cell does not belong to the first RNA; the RRC connection recovery request message carries a first cause value; The second condition is that multicast is not received in the RRC inactive state, or that multicast is received in the RRC inactive state and the serving cell sends second multicast configuration information; the second multicast configuration information is configuration information for receiving the first multicast in the serving cell in the RRC inactive state.
23. The communication method according to claim 22, characterized in that: The first reason value is RNA update.
24. The communication method according to claim 22 or 23, characterized in that: The first multicast is a joined multicast in an activated state.
25. The communication method according to any one of claims 22 to 24, characterized in that: The second multicast configuration information is carried in the first MCCH message.
26. The communication method according to any one of claims 22 to 25, characterized in that: The second multicast configuration information includes at least one of an identifier of the first multicast, a G-RNTI of the first multicast, and an MRB configuration of the first multicast.
27. A communication method, characterized in that: Receiving a first radio resource control RRC release message sent by a second network device, wherein the first RRC release message indicates that the first radio access network notifies an area RNA; Enter RRC inactive state from RRC connected state; When the first condition is met and the third condition is met, an RRC connection recovery request message is sent to a first network device, where the first network device is a network device of a serving cell, and the first condition is that a first timer times out or the serving cell does not belong to the first RNA; the RRC connection recovery request message carries a second cause value; The third condition is that the first RRC release message indicates receiving multicast in the RRC inactive state and the serving cell does not send second multicast configuration information; The second multicast configuration information is configuration information for receiving the first multicast in the serving cell in an RRC inactive state.
28. The communication method according to claim 27, characterized in that: The first multicast is a joined multicast in an activated state.
29. The communication method according to claim 27 or 28, characterized in that: The second multicast configuration information is carried in the first MCCH message.
30. The communication method according to any one of claims 27 to 29, characterized in that: The serving cell not sending the second multicast configuration information includes: The first multicast broadcast service control channel MCCH message sent by the serving cell does not include the second multicast configuration information; or, The serving cell does not send a first system message, where the first system message is used to send configuration information of the first MCCH.
31. The communication method according to any one of claims 27 to 30, characterized in that: The second cause value is one of mobile originated data mo-Data, mobile originated signaling mo-Signalling, mobile terminal access mt-Access, or multicast broadcast service access.
32. The communication method according to any one of claims 27 to 30, characterized in that: The second cause value is a third cause value, and the third cause value indicates that a multicast broadcast service is accessed and an RNA is updated.
33. The communication method according to claim 32, characterized in that: After sending the RRC connection recovery request message to the first network device, the method further includes: Receiving a second RRC release message sent by the first network device; The second multicast configuration information is obtained.
34. The communication method according to claim 33, characterized in that: The second multicast configuration information is carried in the second RRC release message, or the second multicast configuration information is carried in the first system message and / or the first MCCH message of the serving cell.
35. A communication method, characterized in that: The method comprises: A first radio resource control (RRC) connection recovery request message is received from a terminal device, wherein the RRC connection recovery request message carries a third cause value, wherein the third cause value indicates that the RNA is updated and the service cell does not send the second multicast configuration information; the second multicast configuration information is the configuration information of the first multicast received in the service cell when the RRC is in an inactive state.
36. The communication method according to claim 35, characterized in that: The method further comprises: In a case where multicast in an RRC inactive state can be provided, sending a context retrieval request message to the second network device, wherein the context retrieval request message carries the third cause value; Receiving a context retrieval failure message sent by the second network device, wherein the context retrieval failure message includes a second RRC release message and an identifier of the first multicast; Send the second multicast configuration information and the second RRC release message to the terminal device.
37. The communication method according to claim 36, characterized in that: The second multicast configuration information is carried in the second RRC release message, or the second multicast configuration information is carried in the first system message and / or the first multicast broadcast service control channel MCCH message of the serving cell.
38. The communication method according to claim 36 or 37, characterized in that: The context retrieval request message also carries a set of identifiers of RRC inactive multicasts that can be provided, and the set of identifiers of multicasts includes the identifier of the first multicast.
39. The method according to claim 36, characterized in that The method further comprises: In a case where providing RRC inactive multicast is not supported, sending a context retrieval request message to the second network device, wherein the context retrieval request message does not carry the third cause value; receiving a context retrieval response message sent by the second network device, wherein the context retrieval response message includes the context of the terminal device; An RRC recovery message is sent to the terminal device, wherein the RRC recovery message instructs the terminal device to enter an RRC connected state from an RRC inactive state.
40. A communication method, characterized in that: The method comprises: Sending a first radio resource control RRC release message to the terminal device, wherein the first RRC release message indicates a first radio access network-based notification area RNA; A context retrieval request message is received from a first network device, the context retrieval request message carries a third cause value, the third cause value indicates that RNA is updated and the service cell of the terminal device does not send second multicast configuration information; the second multicast configuration information is configuration information for receiving the first multicast in the service cell in an RRC inactive state; the first network device is a network of the service cell equipment; If the serving cell belongs to the first RNA, sending a context retrieval failure message to the first network device, where the context retrieval failure message carries a second RRC release message and an identifier of the first multicast; If the serving cell does not belong to the first RNA, a context retrieval response message is sent to the first network device, where the context retrieval response message includes the context of the terminal device.
41. The communication method according to claim 40, characterized in that: The context retrieval request message also carries a set of RRC inactive multicast identifiers that can be provided by the first network device, and the set of multicast identifiers includes the identifier of the first multicast.
42. A communication device, characterized in that: The device is configured to execute the communication method as described in any one of claims 1 to 41 above.
43. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the communication method as described in any one of claims 1 to 41 is implemented.
44. A chip system, characterized in that: It includes a processor coupled to a memory, wherein the processor is used to execute the code in the memory to implement the communication method as described in any one of claims 1 to 41 above.
45. A computer program product, characterized in that The computer program product comprises a computer program, which, when executed by a processor, is used to perform the communication method as described in any one of claims 1 to 41 above.
Citation Information
Patent Citations
Communication method, device and system
CN118972989A
Communication method and device and storage medium
CN116017311A
Method and apparatus for establishing MBS service, and terminal device and network device
WO2022006875A1
