Method and device for determining configuration information and terminal equipment

Abstract

The embodiment of the invention provides a method and device for determining configuration information and terminal equipment, and the method comprises the steps: determining target multimedia broadcast service (MBS) configuration information under the condition that the terminal equipment executes cell selection and reselects to a target cell, and receiving multicast MBS service based on the target MBS configuration information.

Description

[0001] This application is a divisional application of the PCT international patent application PCT / CN2022 / 072144 with an application date of January 14, 2022, which entered the Chinese national phase with Chinese patent application number 202280088001.9 and the invention name being “A method, device and terminal device for determining configuration information”. Technical Field

[0002] The embodiments of the present application relate to the field of mobile communication technology, and specifically to a method and apparatus for determining configuration information, and a terminal device. Background Art

[0003] In the New Radio (NR) system, many scenarios need to support multicast and broadcast service requirements, such as in the Internet of Vehicles and the Industrial Internet. Therefore, it is necessary to introduce multicast and broadcast Multimedia Broadcast Service (MBS) services in NR.

[0004] Currently, terminal devices can only receive multicast MBS services in the Radio Resource Control (RRC) connection state. In order to save energy, terminal devices can receive multicast MBS services in the RRC inactive state. How terminal devices receive multicast MBS services in the RRC inactive state needs to be improved. Summary of the invention

[0005] Embodiments of the present application provide a method and apparatus for determining configuration information, a terminal device, a chip, a computer-readable storage medium, a computer program product, and a computer program.

[0006] The method for determining configuration information provided in an embodiment of the present application includes:

[0007] When the terminal device performs cell selection and reselects to the target cell, it determines the target MBS configuration information and receives the multicast MBS service based on the target MBS configuration information.

[0008] The device for determining configuration information provided in an embodiment of the present application is applied to a terminal device, and the device includes:

[0009] An acquisition unit, configured to determine target MBS configuration information when the terminal device performs cell selection and reselects to a target cell;

[0010] A communication unit is configured to receive a multicast MBS service based on the target MBS configuration information.

[0011] The terminal device provided in the embodiment of the present application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the above-mentioned method for determining configuration information.

[0012] The chip provided in the embodiment of the present application is used to implement the above-mentioned method for determining configuration information.

[0013] Specifically, the chip includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes the above-mentioned method for determining configuration information.

[0014] The computer-readable storage medium provided in the embodiment of the present application is used to store a computer program, which enables a computer to execute the above-mentioned method for determining configuration information.

[0015] The computer program product provided in the embodiment of the present application includes computer program instructions, which enable a computer to execute the above-mentioned method for determining configuration information.

[0016] The computer program provided in the embodiment of the present application, when executed on a computer, enables the computer to execute the above-mentioned method for determining configuration information.

[0017] Through the above technical solution, the terminal device can perform cell selection and reselect to the target cell in the RRC inactive state, determine the target MBS configuration information, and receive the multicast MBS service based on the target MBS configuration information. In this way, the terminal device can continue to receive the multicast MBS service in the RRC inactive state. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0019] Figure 1 It is a schematic diagram of an application scenario of an embodiment of the present application;

[0020] Figure 2 It is a schematic diagram of the protocol stack corresponding to the PTM mode and the PTP mode of the embodiment of the present application;

[0021] Figure 3 is a flowchart of a method for determining configuration information provided in an embodiment of the present application;

[0022] Figure 4 It is a flowchart of obtaining updated MBS configuration information during the RRC recovery process provided by an embodiment of the present application;

[0023] Figure 5 is a schematic diagram of the structure of the device for determining configuration information provided in an embodiment of the present application;

[0024] Figure 6 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0025] Figure 7 is a schematic structural diagram of a chip according to an embodiment of the present application;

[0026] Figure 8 It is a schematic block diagram of a communication system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0027] The following will describe the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0028] Figure 1 It is a schematic diagram of an application scenario of an embodiment of the present application.

[0029] like Figure 1 As shown, the communication system 100 may include a terminal device 110 and a network device 120. The network device 120 may communicate with the terminal device 110 via an air interface. The terminal device 110 and the network device 120 support multi-service transmission.

[0030] It should be understood that the embodiments of the present application are only exemplified by the communication system 100, but the embodiments of the present application are not limited thereto. That is to say, the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Internet of Things (IoT) system, Narrow Band Internet of Things (NB-IoT) system, enhanced Machine Type Communications (eMTC) system, 5G communication system (also called New Radio (NR) communication system), or future communication systems, etc.

[0031] exist Figure 1In the communication system 100 shown, the network device 120 may be an access network device that communicates with the terminal device 110. The access network device may provide communication coverage for a specific geographical area, and may communicate with the terminal device 110 (eg, UE) located in the coverage area.

[0032] The network device 120 may be an evolved Node B (eNB or eNodeB) in a Long Term Evolution (LTE) system, or a Next Generation Radio Access Network (NG RAN) device, or a base station (gNB) in an NR system, or a wireless controller in a Cloud Radio Access Network (CRAN), or the network device 120 may be a relay station, an access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, or a network device in a future evolved Public Land Mobile Network (PLMN), etc.

[0033] The terminal device 110 may be any terminal device, including but not limited to a terminal device connected to the network device 120 or other terminal devices by wire or wireless connection.

[0034] For example, the terminal device 110 may refer to an access terminal, a user equipment (UE), a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device. The access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, an IoT device, a satellite handheld terminal, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolution network, etc.

[0035] The terminal device 110 may be used for device-to-device (D2D) communication.

[0036] The wireless communication system 100 may also include a core network device 130 for communicating with the base station, and the core network device 130 may be a 5G core network (5G Core, 5GC) device, for example, an access and mobility management function (Access and Mobility Management Function, AMF), and for example, an authentication server function (Authentication Server Function, AUSF), and for example, a user plane function (User Plane Function, UPF), and for example, a session management function (Session Management Function, SMF). Optionally, the core network device 130 may also be an evolved packet core (Evolved Packet Core, EPC) device of the LTE network, for example, a session management function + a data gateway (Session Management Function + Core Packet Gateway, SMF + PGW-C) device of the core network. It should be understood that SMF + PGW-C can simultaneously implement the functions that SMF and PGW-C can implement. In the process of network evolution, the above-mentioned core network device may also be called other names, or a new network entity may be formed by dividing the functions of the core network, which is not limited to the embodiments of the present application.

[0037] The functional units in the communication system 100 may also establish connections through next generation (NG) network interfaces to achieve communication.

[0038] For example, the terminal device establishes an air interface connection with the access network device through the NR interface for transmitting user plane data and control plane signaling; the terminal device can establish a control plane signaling connection with the AMF through the NG interface 1 (N1 for short); the access network device, such as the next generation wireless access base station (gNB), can establish a user plane data connection with the UPF through the NG interface 3 (N3 for short); the access network device can establish a control plane signaling connection with the AMF through the NG interface 2 (N2 for short); the UPF can establish a control plane signaling connection with the SMF through the NG interface 4 (N4 for short); the UPF can exchange user plane data with the data network through the NG interface 6 (N6 for short); the AMF can establish a control plane signaling connection with the SMF through the NG interface 11 (N11 for short); the SMF can establish a control plane signaling connection with the PCF through the NG interface 7 (N7 for short).

[0039] Figure 1A base station, a core network device and two terminal devices are shown exemplarily. Optionally, the wireless communication system 100 may include multiple base station devices and each base station may include another number of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[0040] It should be noted that Figure 1 It is only to illustrate the system to which the present application is applicable in the form of an example. Of course, the method shown in the embodiment of the present application can also be applied to other systems. In addition, the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship. It should also be understood that the "indication" mentioned in the embodiment of the present application can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, B can be obtained through C; it can also mean that there is an association relationship between A and B. It should also be understood that the "correspondence" mentioned in the embodiment of the present application can mean that there is a direct or indirect correspondence relationship between the two, or it can mean that there is an association relationship between the two, or it can mean that there is an indication and being indicated, configuration and being configured, etc. It should also be understood that the "predefined" or "predefined rules" mentioned in the embodiments of the present application can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in devices (for example, including terminal devices and network devices), and the present application does not limit its specific implementation method. For example, predefined can refer to the definition in the protocol. It should also be understood that in the embodiments of the present application, the "protocol" may refer to a standard protocol in the field of communications, such as LTE protocols, NR protocols, and related protocols used in future communication systems, and the present application does not limit this.

[0041] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following related technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all belong to the protection scope of the embodiments of the present application.

[0042] With the pursuit of speed, latency, high-speed mobility, energy efficiency and the diversity and complexity of services in future life, the Third Generation Partnership Project (3GPP) rdThe 3rd Generation Partnership Project (3GPP) international standard organization has begun to develop 5G. The main application scenarios of 5G are: enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC).

[0043] On the one hand, eMBB still aims at users to obtain multimedia content, services and data, and its demand is growing rapidly. On the other hand, since eMBB may be deployed in different scenarios, such as indoors, in urban areas, and in rural areas, its capabilities and requirements vary greatly, so it cannot be generalized and must be analyzed in detail in combination with specific deployment scenarios. Typical applications of URLLC include: industrial automation, power automation, remote medical operations (surgery), traffic safety, etc. Typical features of mMTC include: high connection density, small data volume, latency-insensitive services, low cost and long service life of modules, etc.

[0044] Multimedia Broadcast Multicast Service (MBMS) is a technology that transmits data from one data source to multiple terminal devices by sharing network resources. This technology can effectively utilize network resources while providing multimedia services, and realize broadcast and multicast of multimedia services at a higher rate (such as 256kbps).

[0045] Since MBMS spectrum efficiency is low, it is not enough to effectively carry and support the operation of mobile TV services. Therefore, in LTE, 3GPP explicitly proposed to enhance the support capability for downlink high-speed MBMS services and determined the design requirements for the physical layer and air interface.

[0046] 3GPP R9 introduced evolved MBMS (eMBMS) into LTE. eMBMS proposed the concept of Single Frequency Network (SFN), namely Multimedia Broadcast multicast service Single Frequency Network (MBSFN). MBSFN uses a unified frequency to send service data in all cells at the same time, but synchronization between cells must be guaranteed. This method can greatly improve the overall signal-to-noise ratio distribution of the cell, and the spectrum efficiency will also be greatly improved accordingly. eMBMS implements broadcast and multicast of services based on the IP multicast protocol.

[0047] In LTE or LTE-Advanced (LTE-A), MBMS has only a broadcast bearer mode but no multicast bearer mode.

[0048] It should be noted that, although the above solution is described by taking MBMS as an example, the description of "MBMS" can also be replaced by "MBS". The embodiment of the present application is described by taking MBS as an example, and the description of "MBS" can also be replaced by "MBMS".

[0049] In the NR system, many scenarios need to support multicast and broadcast service requirements, such as in the Internet of Vehicles and the Industrial Internet. Therefore, it is necessary to introduce multicast and broadcast MBS services in NR. It should be noted that multicast MBS services refer to MBS services transmitted by multicast. Broadcast MBS services refer to MBS services transmitted by broadcast.

[0050] For multicast type MBS services, the network side configures the configuration information (MBS configuration information for short) received by the MBS service through RRC dedicated signaling. Optionally, the MBS configuration information includes at least one of the following: MBS identification information, group-radio network temporary identification (Group-RNTI, G-RNTI), MBS Radio Bearer (MBS Radio Bearer, MRB) configuration, physical channel configuration, feedback resource configuration, etc. For MBS services with relatively high quality of service (QoS) requirements (such as MBS services with relatively high reliability requirements), the terminal device needs to receive multicast MBS services in the RRC connected state. For broadcast type MBS services, the network side configures the multicast control channel (Multicast Control Channel, MCCH) through system messages (such as MBS SIB), and configures the multicast transport channel (Multicast Transport Channel, MTCH) through MCCH signaling. The terminal device can receive broadcast MBS services in the RRC connected state, RRC idle state, and RRC inactive state.

[0051] For multicast MBS services, the MBS services are sent to all terminal devices in a group. When receiving multicast MBS services in the RRC connection state, the terminal device can receive multicast MBS service data in a point-to-multipoint (PTM) or point-to-point (PTP) mode. Figure 2 The MBS service data of the PTM mode is scrambled with the corresponding scheduling information through the G-RNTI configured on the network side, and the MBS service data of the PTP mode is scrambled with the corresponding scheduling information through the C-RNTI. Optionally, during the MBS service transmission process, there is a scenario in which PTP is used for PTM retransmission.

[0052] For multicast type MBS services, after the base station receives the MBS service sent by the core network from the shared tunnel, it can send the MBS service to all terminal devices in a group through the air interface. Here, the base station can send the MBS service to all terminal devices in a group through the PTP method and / or the PTM method. For example: a group includes terminal device 1, terminal device 2 and terminal device 3, the base station can send the MBS service to terminal device 1 through the PTP method, send the MBS service to terminal device 2 through the PTP method, and send the MBS service to terminal device 3 through the PTP method; or, the base station can send the MBS service to terminal device 1 through the PTP method, and send the MBS service to terminal device 2 and terminal device 3 through the PTM method; or, the base station can send the MBS service to terminal device 1, terminal device 2 and terminal device 3 through the PTM method. A shared GTP tunnel is used between the core network and the base station to transmit MBS services, that is, both PTM and PTP MBS services share this GTP tunnel. The base station sends MBS service data to UE1 and UE2 in PTM mode, and sends MBS service data to UE3 in PTP mode.

[0053] For multicast type MBS services (MBS multicast services for short), a DRX mechanism is introduced for energy saving of terminal devices. For the sake of distinction, the DRX used for receiving MBS multicast services is called MBSDRX (or multicast DRX), and the DRX used for receiving traditional unicast services is called unicast DRX. MBSDRX and unicast DRX are independent of each other. As an example, the parameters related to MBSDRX can refer to the following Table 1. The network side can configure the parameters shown in Table 1 through RRC signaling, so as to control the MBSDRX operation through these parameters. It should be noted that MBSDRX is configured per G-RNTI or per G-CS-RNTI. For terminal devices, the DRX activation time includes the time when the following timers run: drx-onDurationTimerPTM, drx-InactivityTimerPTM, drx-RetransmissionTimer-DL-PTM.

[0054]

[0055] Table 1

[0056] In order to reduce air interface signaling and quickly restore wireless connections and data services, 5G defines a new RRC state, namely the RRC inactive (RRC_INACTIVE) state. This state is different from the RRC idle (RRC_IDLE) state and the RRC active (RRC_ACTIVE) state.

[0057] 1) RRC_IDLE state (abbreviated as idle state): Mobility is based on cell selection and reselection of the terminal device, paging is initiated by the core network (CN), and the paging area is configured by the CN. There is no UE context on the base station side and no RRC connection.

[0058] 2) RRC_CONNECTED state (referred to as connected state): There is an RRC connection, and UE context exists on the base station side and the terminal device side. The network side knows the location of the terminal device at the specific cell level. Mobility is mobility controlled by the network side. Unicast data can be transmitted between the terminal device and the base station.

[0059] 3) RRC_INACTIVE state (abbreviated as inactive state): Mobility is based on cell selection reselection of the terminal device, there is a connection between CN-NR, the UE AS context exists on a certain base station, paging is triggered by RAN, and the paging area based on RAN is managed by RAN. The network side knows the location of the terminal device based on the paging area level of RAN.

[0060] When the terminal device is in the RRC inactive state, the network side (RAN) will configure the RAN paging area for the terminal device through RRC dedicated signaling. The RAN paging area can be one cell or multiple cells. When the terminal device moves within the area, it does not need to notify the network side and follows the mobility behavior in the RRC idle state, that is, the cell selection and reselection principle. When the terminal device moves out of the RAN's paging area, it will trigger the terminal device to restore the RRC connection and reacquire the RAN's paging area. When downlink data arrives at the terminal device, the base station that maintains the connection between the RAN and CN for the terminal device will trigger all cells in the RAN's paging area to send a paging message to the terminal device, so that the terminal device in the RRC inactive state can restore the RRC connection and receive data.

[0061] Therefore, when the terminal device enters the RRC connected state from the RRC inactive state, there are three situations:

[0062] First, when downlink data arrives at the terminal device, the network side initiates RAN initial paging, prompting the terminal device to enter the RRC connected state.

[0063] Second, the terminal device itself initiates a RAN location area update, such as a periodic RAN location update or a cross-area location update.

[0064] Third, the terminal device has a need to send uplink data, prompting the terminal device to enter the RRC connection state.

[0065] The RRC recovery process is as follows:

[0066] 1. The terminal device sends a preamble code to the current serving base station.

[0067] 2. The current serving base station sends a random access response (RAR) to the terminal device.

[0068] 3. The terminal device sends an RRC recovery request message to the current serving base station.

[0069] 4. The current serving base station interacts with the base station storing the UE context of the terminal device and requests the UE context.

[0070] 5. The current serving base station sends an RRC recovery message to the terminal device.

[0071] 6. The terminal device sends an RRC recovery completion message to the current serving base station.

[0072] At present, terminal devices can only receive multicast MBS services in the RRC connected state. In order to save energy in terminal devices, terminal devices can receive multicast MBS services in the RRC inactive state. However, the configuration information for receiving MBS services (referred to as MBS configuration information) is configured to the terminal device through RRC dedicated signaling. Therefore, when the terminal device receives multicast MBS services in the RRC inactive state, cell selection reselection occurs. How to obtain the MBS configuration information of the target cell is a problem that needs to be solved. To this end, the following technical solutions of the embodiments of the present application are proposed.

[0073] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The above related technologies can be combined arbitrarily with the technical solutions of the embodiments of the present application as optional solutions, and they all belong to the protection scope of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0074] Figure 3 is a flow chart of a method for determining configuration information provided in an embodiment of the present application, such as Figure 3 As shown, the method for determining configuration information includes the following steps:

[0075] Step 301: When the terminal device performs cell selection and reselects to a target cell, it determines target MBS configuration information and receives a multicast MBS service based on the target MBS configuration information.

[0076] In some optional implementations, the network side may configure at least one indication information through a first signaling, and the indication information is used to indicate whether the terminal device can continue to receive the MBS service in the RRC inactive state. Here, optionally, the indication information may be configured per G-RNTI, that is, each G-RNTI is associated with one indication information. For the terminal device, the terminal device receives a first signaling, and the first signaling is used to configure at least one indication information, and the indication information is used to indicate whether the terminal device can continue to receive the multicast MBS service in the RRC inactive state. Here, optionally, the first signaling is an RRC dedicated signaling, for example, the first signaling is an RRC reconfiguration (RRCReconfiguration) message or an RRC release (RRCRelease) message.

[0077] In some optional embodiments, each indication information in the at least one indication information is associated with a G-RNTI. In other words, the indication information is configured per G-RNTI. For example: indication information 1 (associated with G-RNTI 1) is used to indicate that the terminal device can continue to receive multicast MBS services in the RRC inactive state, and the G-RNTI of the MBS service here is G-RNTI 1 associated with indication information 1. Indication information 2 (associated with G-RNTI 2) is used to indicate that the terminal device cannot continue to receive multicast MBS services in the RRC inactive state, and the G-RNTI of the MBS service here is G-RNTI 2 associated with indication information 2.

[0078] In some optional implementations, the at least one indication information includes first indication information, the first indication information is associated with the first G-RNTI, and the first indication information is used to indicate that the terminal device can continue to receive the multicast MBS service in the RRC inactive state; after the terminal device enters the RRC inactive state, at least one of the following actions is performed:

[0079] Keeping the MBS bearer (MRB) associated with the first G-RNTI not suspended;

[0080] Perform a partial MAC reset;

[0081] Keep the DRX operation associated with the first G-RNTI continuing.

[0082] Here, keeping the DRX operation associated with the first G-RNTI continued can also be understood as keeping the DRX timer associated with the first G-RNTI (here refers to other DRX timers except the RTT timer and the retransmission timer) unaffected. If the DRX configuration associated with the first G-RNTI includes the configuration of the round-trip time RTT timer and / or the retransmission timer, the terminal device ignores the configuration of the RTT timer and / or the retransmission timer; or, if the RTT timer and / or the retransmission timer associated with the first G-RNTI is running, the terminal device stops the RTT timer and / or the retransmission timer.

[0083] It should be noted that MAC reset means that when the MAC entity is requested to be reset by the upper-layer entity, the MAC entity executes the items shown in the following Table 2.

[0084]

[0085]

[0086] Table 2

[0087] If the MAC entity is requested by the upper layer to reset the sideline specifically for the PC5-RRC connection, the MAC entity performs the following

[0088] The entries are shown in Table 3.

[0089]

[0090] Table 3

[0091] In the embodiment of the present application, partial MAC reset means: MAC reset (reset), but some entries are not executed. As an example: MAC reset, but the following actions related to downlink hybrid automatic repeat request (DL HARQ) are not executed:

[0092] 1> flush the soft buffers for all DL HARQ processes;

[0093] 1> For each DL HARQ process, consider the next received transmission for a TB as the very first transmission.

[0094] In some optional implementations, the at least one indication information includes second indication information, the second indication information is associated with the second G-RNTI, and the second indication information is used to indicate that the terminal device cannot continue to receive the multicast MBS service in the RRC inactive state; after the terminal device enters the RRC inactive state, at least one of the following actions is performed:

[0095] Suspending the MBS bearer associated with the second G-RNTI;

[0096] Stop performing the DRX operation associated with the second G-RNTI.

[0097] As an example: Indication information 1 (associated G-RNTI 1) is used to indicate that the terminal device can continue to receive multicast MBS services in the RRC inactive state. Here, the G-RNTI of the MBS service is G-RNTI 1 associated with indication information 1. After the terminal device enters the RRC inactive state, it performs at least one of the following actions: keep the MBS bearer (MRB) associated with G-RNTI 1 not suspended; perform a partial MAC reset; keep the DRX operation associated with G-RNTI 1 (that is, the DRX operation corresponding to the MBS service) continuing to execute. Indication information 2 (associated G-RNTI 2) is used to indicate that the terminal device cannot continue to receive multicast MBS services in the RRC inactive state. Here, the G-RNTI of the MBS service is G-RNTI 2 associated with indication information 2. After the terminal device enters the RRC inactive state, it performs at least one of the following actions: suspend the MBS bearer associated with G-RNTI 2; stop executing the DRX operation associated with G-RNTI 2.

[0098] In some optional implementations, after the terminal device enters the RRC idle state from the RRC inactive state, the UE context is released and the terminal device autonomously enters the RRC connected state; the terminal device obtains MBS configuration information in the RRC connected state, and receives the multicast MBS service based on the MBS configuration information. Here, there are many reasons why the terminal device enters the RRC idle state from the RRC inactive state. For example, the terminal device enters the RRC idle state from the RRC inactive state due to an abnormality. In this case, the terminal device releases the UE AS context, including the context of the MBS service data, and autonomously enters the RRC connected state to continue to obtain the MBS configuration information and continue to receive the MBS service according to the MBS configuration information.

[0099] Through the above solution, the terminal device can learn through the first signaling which MBS services can continue to be received in the RRC inactive state.

[0100] In the embodiment of the present application, when the terminal device is in the RRC inactive state, its mobility behavior follows the cell selection reselection. When the terminal device performs cell selection reselection to the target cell, it determines the target MBS configuration information and receives the multicast MBS service based on the target MBS configuration information. The following describes how the terminal device determines the MBS configuration information. It should be noted that the "target MBS configuration information" in the embodiment of the present application can also be understood as updated MBS configuration information.

[0101] Solution 1: The network configures MBS configuration information at a per area granularity.

[0102] In some optional implementations, the terminal device receives a second signaling, the second signaling is used to configure at least one MBS configuration information; when the terminal device performs cell selection and reselects to a target cell, the target MBS configuration information is acquired based on the second signaling. Specifically, the second signaling is used to configure the first MBS configuration information, and the second signaling is also used to configure the first area information, the first area information is used to indicate the first area where the first MBS configuration information is valid.

[0103] Here, optionally, the MBS configuration information includes at least one of the following: MBS identification information, G-RNTI, MRB bearer configuration, frequency domain resource information when receiving MBS multicast services, physical channel configuration, feedback resource configuration, etc.

[0104] Here, optionally, the first area information includes at least one of the following: a cell identifier list, an RNA list, and a system broadcast area identifier.

[0105] Here, optionally, the second signaling is RRC dedicated signaling, and the second signaling may be the same as or different from the first signaling in the above solution. For example, the second signaling is an RRC reconfiguration message or an RRC release message.

[0106] As an example: the terminal device receives the configuration information about the reception of multicast MBS services (i.e., the first MBS configuration information) sent by the network side through RRC dedicated signaling in the RRC connected state. At the same time, the RRC dedicated signaling also configures an area information (i.e., the first area information). The first area information is used to indicate the first area where the MBS configuration information is valid. When the terminal device reselects a cell within the first area, it does not need to re-acquire the MBS configuration information, and the previous MBS configuration information (i.e., the MBS configuration information obtained through RRC dedicated signaling) is still valid.

[0107] In some optional implementations, when the terminal device performs cell selection and reselects to a target cell, if the target cell is located in the first area, the first MBS configuration information is determined as the target MBS configuration information.

[0108] In some optional implementations, if the target cell is located outside the first area, the terminal device initiates an RRC recovery process and obtains the target MBS configuration information through the RRC recovery process.

[0109] Solution 2: The network configures MBS configuration information at a per cell granularity.

[0110] In some optional implementations, the terminal device receives a second signaling, the second signaling being used to configure at least one MBS configuration information; when the terminal device performs cell selection and reselects to a target cell, the target MBS configuration information is acquired based on the second signaling. Specifically, each MBS configuration information in the at least one MBS configuration information is associated with a cell identification information, and the MBS configuration information is valid in the cell corresponding to the cell identification information associated with it.

[0111] Here, optionally, the MBS configuration information includes at least one of the following: MBS identification information, G-RNTI, MRB bearer configuration, frequency domain resource information when receiving MBS multicast services, physical channel configuration, feedback resource configuration, etc.

[0112] Here, optionally, the cell identification information includes at least one of the following: a cell identification, a frequency, and a physical cell identification (PCI).

[0113] In some optional implementations, when the terminal device performs cell selection to reselect a target cell, if the cell identification information of the target cell matches the cell identification information associated with the first MBS configuration information in the at least one MBS configuration information, the first MBS configuration information is determined as the target MBS configuration information.

[0114] In some optional implementations, if the cell identification information of the target cell does not match the cell identification information associated with any MBS configuration information in the at least one MBS configuration information, the terminal device initiates an RRC recovery process and obtains the target MBS configuration information through the RRC recovery process.

[0115] As an example: the terminal device receives configuration information about receiving multicast MBS services through RRC dedicated signaling in the RRC connected state, where the RRC dedicated signaling configures multiple MBS configuration information, and each configuration information is associated with a cell identification information. When the terminal device performs cell selection to reselect to the target cell, if the cell identification information of the target cell matches the cell identification information associated with one of the MBS configuration information, the terminal device enables the MBS configuration information associated with the cell identification information, and if they do not match, the terminal device initiates the RRC recovery process and obtains the updated MBS configuration information through the RRC recovery process.

[0116] Solution 3: Update MBS configuration information through a 2-step RRC resume process.

[0117] In some optional implementations, when the terminal device performs cell selection and reselects to a target cell, an RRC recovery process is initiated, and target MBS configuration information is acquired through the RRC recovery process.

[0118] In some optional implementations, the network side configures updated MBS configuration information through an RRC release message, and the terminal device obtains the target MBS configuration information through the RRC release message.

[0119] As an example: when the terminal device performs cell selection and reselects to the target cell, it initiates the RRC recovery process and obtains the updated MBS configuration information through the RRC recovery process.

[0120] For any of the above schemes, the terminal device obtains the target MBS configuration information through the RRC recovery process or through the RRC release message, including: the terminal device sends an RRC recovery request message to a first base station, and the first base station is the base station corresponding to the target cell; the terminal device receives the RRC release message sent by the first base station, and the RRC release message carries the updated MBS configuration information, and the terminal device determines the updated MBS configuration information as the target MBS configuration information.

[0121] Here, optionally, after the terminal device sends an RRC recovery request message to the first base station, the first base station sends a UE context request message to the second base station; the second base station is a base station that stores the UE context of the terminal device; the first base station receives a UE context request response message sent by the second base station, and the UE context request response message carries the UE context of the terminal device; the first base station updates the MBS configuration information based on the UE context of the terminal device.

[0122] In the above scheme, optionally, the RRC recovery request message carries a recovery reason, and the value of the recovery reason is a first reason value, and the first reason value is used to indicate that the purpose of the terminal device initiating the RRC recovery is to update the MBS configuration information.

[0123] In the above scheme, optionally, the UE context request message carries a first cause value, and the first cause value is used to indicate that the purpose of the terminal device initiating RRC recovery is to update MBS configuration information.

[0124] Figure 4 The process of obtaining updated MBS configuration information during RRC recovery is shown, such as Figure 4 As shown, the following steps are included:

[0125] 1. The terminal device is in the RRC inactive state and performs cell selection to reselect to the target cell. It needs to obtain updated MBS configuration information (that is, configuration information for receiving multicast MBS services).

[0126] 2. The terminal device sends a preamble code to the first base station.

[0127] Here, the first base station is the base station currently served by the terminal device, that is, the base station corresponding to the target cell.

[0128] 3. The first base station sends the RAR to the terminal device.

[0129] 4. The terminal device sends an RRC recovery request message to the first base station, carrying the recovery reason: MBSconfigupdate.

[0130] Here, MBSconfigupdate is also the first cause value, which is used to indicate that the purpose of the terminal device initiating RRC recovery is to update the MBS configuration information.

[0131] 5. After receiving the RRC recovery request message, the first base station knows through the recovery reason that the purpose of the terminal device initiating the RRC recovery is to update the updated MBS configuration information caused by the cell selection reselection, and then sends a UE context request message to the second base station that stores the UE context of the terminal device according to the I-RNTI, carrying the recovery reason: MBSconfigupdate.

[0132] 6. The second base station sends a UE context request response message to the first base station, carrying the UE context.

[0133] 7. The first base station updates the MBS configuration information according to the configuration information of the multicast MBS service in the UE context, and configures the updated MBS configuration information to the terminal device through an RRC release message.

[0134] 8. The terminal device maintains the RRC inactive state, replaces the previous MBS configuration information with the updated MBS configuration information in the RRC release message, and continues to receive the multicast MBS service using the updated MBS configuration information.

[0135] In an embodiment of the present application, in order to ensure service continuity, that is, to enable the terminal device to reselect to a cell where the terminal device is receiving MBS services as much as possible, thereby ensuring the continuity of MBS service reception, the terminal device refers to the frequency priority when performing cell selection reselection. Specifically, for a terminal device that enters an RRC inactive state and receives MBS services, the terminal device considers that the frequency corresponding to the current cell has the highest priority during the cell reselection process, or determines the highest priority frequency based on the frequency priority configuration information for MBS service reception configured on the network side, and then performs cell selection reselection according to the highest priority frequency.

[0136] In some optional implementations, for any of the above-mentioned solutions 1, 2, and 3, the RRC release message also carries frequency priority configuration information, and the frequency priority configuration information is used by the terminal device to reselect a cell for the MBS service. Further, if the MBS service ends, the terminal device releases the frequency priority configuration information.

[0137] Here, the RRC release message carries the frequency priority configuration (i.e., frequency priority configuration information) set by the terminal device to ensure the continuity of the MBS service. The terminal device uses this configuration to reselect the cell, thereby ensuring priority reselection to the cell with MBS service. If the MBS service ends, the terminal device releases the frequency priority configuration information.

[0138] In some optional implementations, for any one of the above-mentioned schemes 1, 2, and 3, the RRC release message also carries third indication information, and the third indication information is used to indicate that the terminal device can continue to receive multicast MBS services in an RRC inactive state and / or that the frequency priority of the current cell is the highest, and the third indication information is used by the terminal device to reselect the cell for the MBS service.

[0139] Here, the RRC release message carries an indication information, which is used to indicate that the terminal device can continue to receive multicast MBS services when it returns to the RRC inactive state. After the terminal device receives the RRC release message and enters the RRC inactive state, it can be considered that the frequency priority of the current cell is the highest according to the indication information, and the cell selection is reselected accordingly.

[0140] In some optional implementations, for the above-mentioned scheme three, the RRC release message also carries a first neighboring cell list in which the MBS service exists; if the terminal device determines based on the first neighboring cell list that the MBS service does not exist in the neighboring cell of the cell reselection, the terminal device enters the RRC connection state and receives the MBS service in the RRC connection state; if the terminal device determines based on the first neighboring cell list that the MBS service exists in the neighboring cell of the cell reselection, the terminal device performs cell reselection and continues to receive the MBS service in the neighboring cell to which the cell is reselected.

[0141] Here, the network side configures a neighboring cell list (called the first neighboring cell list) with MBS services in the RRC release message. If the terminal device determines that there is no MBS service in the neighboring cell of the cell reselection according to the neighboring cell list before the cell selection reselection, the terminal device enters the RRC connection state to receive the MBS service, and then continues to receive the MBS service by switching. If there is MBS service in the neighboring cell of the cell reselection, the terminal device continues to receive the MBS service by cell reselection.

[0142] In some optional implementations, when the terminal device determines that the MBS service is terminated, the terminal device performs at least one of the following actions:

[0143] Stop monitoring the scheduling information of MBS services scrambled by G-RNTI;

[0144] releasing the bearer configuration associated with the G-RNTI;

[0145] The MBS configuration information associated with the G-RNTI is released.

[0146] In the above solution, the terminal device may determine that the MBS service is terminated by:

[0147] Method 1) The terminal device determines that the MBS service ends based on the MAC CE sent by the network side, and the MAC CE is used to notify the end of the MBS service.

[0148] Option 1) The MAC CE carries identification information of the MBS service; the terminal device determines the MBS service to be terminated based on the identification information of the MBS service carried in the MAC CE.

[0149] Option 2) The terminal device determines the MBS service to be terminated based on the G-RNTI of the PDCCH corresponding to the scheduling of the MAC CE. Here, optionally, the MAC CE only includes a MAC CE subheader.

[0150] As an example: if the MBS service ends, the network notifies the end of the MBS service through MAC CE. After the terminal device learns that the MBS service has ended, it stops monitoring the MBS service encrypted by G-RNTI, and / or autonomously releases the bearer configuration associated with the G-RNTI and all associated MBS configurations. As an implementation method, the MAC CE contains identification information of the MBS service to be released (i.e., stopped), such as TMGI or G-RNTI. As another implementation method, the PDCCH corresponding to the MAC CE implicitly indicates the release (i.e., stop) of the MBS service corresponding to the G-RNTI based on which G-RNTI is scheduled (or encrypted). At this time, the MAC CE can be a MAC CE with only a MAC CE subheader but no MAC CE content, that is, the network side determines that a certain MBS service has ended through the MAC CE subheader.

[0151] Mode 2) The terminal device determines the end of the MBS service based on a timer configured on the network side. Here, optionally, the timer is configured for G-RNTI; or the timer is configured for multiple MBS services.

[0152] Specifically, when the terminal device receives the PDCCH that schedules the MBS service, it starts or restarts the timer. If the timer times out, it determines that the MBS service is terminated.

[0153] As an example: the network side configures a timer. If the terminal device receives MBS service scheduling data (i.e., PDCCH scrambled by G-RNTI), the terminal device restarts the timer. If the timer times out, it means that the MBS service ends. The timer here can be configured per G-RNTI, or one timer can be configured for all MBS services.

[0154] The preferred embodiments of the present application are described in detail above in conjunction with the accompanying drawings. However, the present application is not limited to the specific details in the above embodiments. Within the technical concept of the present application, the technical solution of the present application can be subjected to a variety of simple modifications, and these simple modifications all belong to the protection scope of the present application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, the present application will not further explain various possible combinations. For another example, the various different embodiments of the present application can also be arbitrarily combined, as long as they do not violate the idea of ​​the present application, they should also be regarded as the contents disclosed in the present application. For another example, under the premise of no conflict, the various embodiments and / or the technical features in the various embodiments described in the present application can be arbitrarily combined with the prior art, and the technical solution obtained after the combination should also fall within the protection scope of the present application.

[0155] It should also be understood that in various method embodiments of the present application, the size of the sequence number of each process does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application. In addition, in the embodiment of the present application, the terms "downlink", "uplink" and "side" are used to indicate the transmission direction of the signal or data, wherein "downlink" is used to indicate that the transmission direction of the signal or data is the first direction sent from the site to the user equipment of the cell, "uplink" is used to indicate that the transmission direction of the signal or data is the second direction sent from the user equipment of the cell to the site, and "side" is used to indicate that the transmission direction of the signal or data is the third direction sent from user equipment 1 to user equipment 2. For example, "downlink signal" indicates that the transmission direction of the signal is the first direction. In addition, in the embodiment of the present application, the term "and / or" is only a description of the association relationship of the associated objects, indicating that three relationships can exist. Specifically, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the front and back associated objects are in an "or" relationship.

[0156] Figure 5 Schematic diagram of the structure of the device for determining configuration information provided by the embodiment of the present application, which is applied to a terminal device, such as Figure 5 As shown, the device for determining configuration information includes:

[0157] An acquisition unit 501 is configured to determine target MBS configuration information when a terminal device performs cell selection and reselects a target cell;

[0158] The communication unit 502 is configured to receive a multicast MBS service based on the target MBS configuration information.

[0159] In some optional implementations, the communication unit 502 is further used to receive a first signaling, where the first signaling is used to configure at least one indication information, where the indication information is used to indicate whether the terminal device can continue to receive the multicast MBS service in an RRC inactive state.

[0160] In some optional implementations, each indication information in the at least one indication information is associated with a G-RNTI.

[0161] In some optional implementations, the at least one indication information includes first indication information, the first indication information is associated with the first G-RNTI, and the first indication information is used to indicate that the terminal device can continue to receive the multicast MBS service in the RRC inactive state;

[0162] The apparatus further includes: a processing unit 503, configured to perform at least one of the following actions after the terminal device enters the RRC inactive state:

[0163] Keeping the MBS bearer associated with the first G-RNTI unsuspended;

[0164] Perform a partial MAC reset;

[0165] Keep the DRX operation associated with the first G-RNTI continuing.

[0166] In some optional embodiments, the processing unit 503 is further used to ignore the configuration of the RTT timer and / or the retransmission timer if the DRX configuration associated with the first G-RNTI includes the configuration of the round-trip time RTT timer and / or the retransmission timer; and stop the RTT timer and / or the retransmission timer if the RTT timer and / or the retransmission timer associated with the first G-RNTI is running.

[0167] In some optional implementations, the at least one indication information includes second indication information, the second indication information is associated with the second G-RNTI, and the second indication information is used to indicate that the terminal device cannot continue to receive the multicast MBS service in the RRC inactive state;

[0168] The apparatus further includes: a processing unit 503, configured to perform at least one of the following actions after the terminal device enters the RRC inactive state:

[0169] Suspending the MBS bearer associated with the second G-RNTI;

[0170] Stop performing the DRX operation associated with the second G-RNTI.

[0171] In some optional implementations, the processing unit 503 is further configured to release the UE context and autonomously enter the RRC connected state after the terminal device enters the RRC idle state from the RRC inactive state;

[0172] The acquisition unit 501 is further used to acquire MBS configuration information when the terminal device is in an RRC connected state, and the communication unit 502 is further used to receive multicast MBS services based on the MBS configuration information.

[0173] In some optional implementations, the first signaling is RRC dedicated signaling.

[0174] In some optional embodiments, the communication unit 502 is further used to receive a second signaling, where the second signaling is used to configure at least one MBS configuration information; the acquisition unit 501 is used to acquire the target MBS configuration information based on the second signaling when the terminal device performs cell selection and reselects to the target cell.

[0175] In some optional implementations, the second signaling is used to configure first MBS configuration information, and the second signaling is further used to configure first area information, where the first area information is used to indicate a first area in which the first MBS configuration information is valid.

[0176] In some optional implementations, the first area information includes at least one of the following: a cell identifier list, an RNA list, and a system broadcast area identifier.

[0177] In some optional implementations, the acquisition unit 501 is configured to, when the terminal device performs cell selection and reselects to a target cell, determine the first MBS configuration information as the target MBS configuration information if the target cell is located in the first area.

[0178] In some optional implementations, the acquisition unit 501 is further configured to initiate an RRC recovery process if the target cell is located outside the first area, and acquire the target MBS configuration information through the RRC recovery process.

[0179] In some optional implementations, each piece of MBS configuration information in the at least one piece of MBS configuration information is associated with a cell identification information, and the MBS configuration information is valid in a cell corresponding to the cell identification information associated with the MBS configuration information.

[0180] In some optional implementations, the cell identification information includes at least one of the following: a cell identification, a frequency, and a PCI.

[0181] In some optional embodiments, the acquisition unit 501 is used to determine the first MBS configuration information as the target MBS configuration information if the cell identification information of the target cell matches the cell identification information associated with the first MBS configuration information in the at least one MBS configuration information when the terminal device performs cell selection and reselects to the target cell.

[0182] In some optional implementations, the acquisition unit 501 is further used to initiate an RRC recovery process if the cell identification information of the target cell does not match the cell identification information associated with any MBS configuration information in the at least one MBS configuration information, and acquire the target MBS configuration information through the RRC recovery process.

[0183] In some optional implementations, the acquisition unit 501 is used to initiate an RRC recovery process when the terminal device performs cell selection and reselects to a target cell, and acquire the target MBS configuration information through the RRC recovery process.

[0184] In some optional implementations, the communication unit 502 is further used to send an RRC recovery request message to a first base station, where the first base station is the base station corresponding to the target cell; receive an RRC release message sent by the first base station, where the RRC release message carries updated MBS configuration information, and the acquisition unit 501 determines the updated MBS configuration information as the target MBS configuration information.

[0185] In some optional implementations, the RRC recovery request message carries a recovery reason, and the value of the recovery reason is a first cause value, and the first cause value is used to indicate that the purpose of the terminal device initiating the RRC recovery is to update the MBS configuration information.

[0186] In some optional implementations, the first base station sends a UE context request message to a second base station; the second base station is a base station that stores the UE context of the terminal device; the first base station receives a UE context request response message sent by the second base station, and the UE context request response message carries the UE context of the terminal device; the first base station updates the MBS configuration information based on the UE context of the terminal device.

[0187] In some optional implementations, the UE context request message carries a first cause value, and the first cause value is used to indicate that the purpose of the terminal device initiating RRC recovery is to update MBS configuration information.

[0188] In some optional implementations, the RRC release message further carries frequency priority configuration information, and the frequency priority configuration information is used by the terminal device to perform cell selection reselection for the MBS service.

[0189] In some optional implementations, the processing unit 503 is further configured to release the frequency priority configuration information if the MBS service ends.

[0190] In some optional embodiments, the RRC release message also carries third indication information, and the third indication information is used to indicate that the terminal device can continue to receive multicast MBS services and / or that the frequency priority of the current cell is the highest in the RRC inactive state, and the third indication information is used by the terminal device to reselect the cell for the MBS service.

[0191] In some optional implementations, the RRC release message also carries a first neighboring cell list in which MBS services exist; the communication unit 502 is further used to enter an RRC connection state and receive the MBS service in the RRC connection state if it is determined based on the first neighboring cell list that the MBS service does not exist in the neighboring cell for cell reselection; if it is determined based on the first neighboring cell list that the MBS service exists in the neighboring cell for cell reselection, perform cell reselection and continue to receive the MBS service in the neighboring cell to which the cell is reselected.

[0192] In some optional implementations, the processing unit 503 is further configured to, when it is determined that the MBS service is terminated, perform at least one of the following actions:

[0193] Stop monitoring the scheduling information of MBS services scrambled by G-RNTI;

[0194] releasing the bearer configuration associated with the G-RNTI;

[0195] The MBS configuration information associated with the G-RNTI is released.

[0196] In some optional implementations, the processing unit 503 is configured to determine the end of the MBS service based on a MAC CE sent by the network side, where the MAC CE is used to notify the end of the MBS service.

[0197] In some optional implementations, the MAC CE carries identification information of the MBS service; and the processing unit 503 is configured to determine the terminated MBS service based on the identification information of the MBS service carried in the MAC CE.

[0198] In some optional implementations, the processing unit 503 is configured to determine the terminated MBS service based on the G-RNTI of the PDCCH corresponding to the scheduling of the MAC CE.

[0199] In some optional implementations, the MAC CE only includes a MAC CE subheader.

[0200] In some optional implementations, the processing unit 503 is configured to determine the end of the MBS service based on a timer configured on the network side.

[0201] In some optional implementations, the processing unit 503 is configured to start or restart the timer when the communication unit 502 receives a PDCCH scheduling an MBS service, and determine that the MBS service is terminated if the timer times out.

[0202] In some optional implementations, the timer is configured for a G-RNTI; or, the timer is configured for multiple MBS services.

[0203] Those skilled in the art should understand that the relevant description of the above-mentioned device for determining configuration information in the embodiment of the present application can be understood by referring to the relevant description of the method for determining configuration information in the embodiment of the present application.

[0204] Figure 6 600 is a schematic structural diagram of a communication device 600 provided in an embodiment of the present application. The communication device may be a terminal device or a network device. Figure 6 The communication device 600 shown includes a processor 610, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0205] Alternatively, if Figure 6 As shown, the communication device 600 may further include a memory 620. The processor 610 may call and run a computer program from the memory 620 to implement the method in the embodiment of the present application.

[0206] The memory 620 may be a separate device independent of the processor 610 , or may be integrated into the processor 610 .

[0207] Alternatively, if Figure 6 As shown, the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.

[0208] The transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include an antenna, and the number of the antennas may be one or more.

[0209] Optionally, the communication device 600 may specifically be a network device of an embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the network device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0210] Optionally, the communication device 600 may specifically be a mobile terminal / terminal device of an embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the mobile terminal / terminal device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0211] Figure 7 It is a schematic structural diagram of the chip of an embodiment of the present application. Figure 7 The chip 700 shown includes a processor 710, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0212] Alternatively, if Figure 7 As shown, the chip 700 may further include a memory 720. The processor 710 may call and run a computer program from the memory 720 to implement the method in the embodiment of the present application.

[0213] The memory 720 may be a separate device independent of the processor 710 , or may be integrated into the processor 710 .

[0214] Optionally, the chip 700 may further include an input interface 730. The processor 710 may control the input interface 730 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0215] Optionally, the chip 700 may further include an output interface 740. The processor 710 may control the output interface 740 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0216] Optionally, the chip can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0217] Optionally, the chip can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0218] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0219] Figure 8 8 is a schematic block diagram of a communication system 800 provided in an embodiment of the present application. Figure 8 As shown, the communication system 800 includes a terminal device 810 and a network device 820 .

[0220] Among them, the terminal device 810 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 820 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, they are not repeated here.

[0221] It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by the hardware integrated logic circuit or software instructions in the processor. The above processor can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor are combined and performed. The software module can be located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, and other mature storage media in the art. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0222] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can 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 can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0223] It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiments of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.

[0224] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0225] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0226] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0227] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0228] Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0229] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0230] The embodiment of the present application also provides a computer program.

[0231] Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods in the embodiments of the present application. For the sake of brevity, they are not described here.

[0232] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0233] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0234] Those skilled in the art can 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.

[0235] In the several embodiments provided in the present 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 only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, 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.

[0236] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0237] 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.

[0238] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0239] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method for determining configuration information, the method comprising: When the terminal device performs cell selection and reselects to a target cell, it determines target multimedia broadcast service MBS configuration information and receives multicast MBS services based on the target MBS configuration information.

2. The method according to claim 1, wherein: The method further comprises: The terminal device receives a first signaling, where the first signaling is used to configure at least one indication information, where the indication information is used to indicate whether the terminal device can continue to receive the multicast MBS service in an inactive state of the radio resource control RRC.

3. The method according to claim 2, wherein: Each indication information in the at least one indication information is associated with a group-radio network temporary identifier G-RNTI.

4. The method according to claim 2 or 3, wherein: The at least one indication information includes first indication information, the first indication information is associated with the first G-RNTI, and the first indication information is used to indicate that the terminal device can continue to receive the multicast MBS service in the RRC inactive state; The method further includes: after the terminal device enters the RRC inactive state, performing at least one of the following actions: Keeping the MBS bearer associated with the first G-RNTI unsuspended; Perform partial media access control MAC reset; Keep the discontinuous reception DRX operation associated with the first G-RNTI continuing.

5. The method according to claim 2 or 3, wherein: The at least one indication information includes second indication information, the second indication information is associated with the second G-RNTI, and the second indication information is used to indicate that the terminal device cannot continue to receive the multicast MBS service in the RRC inactive state; The method further includes: after the terminal device enters the RRC inactive state, performing at least one of the following actions: Suspending the MBS bearer associated with the second G-RNTI; Stop performing the DRX operation associated with the second G-RNTI.

6. The method according to any one of claims 2 to 5, wherein: The first signaling is RRC dedicated signaling.

7. A device for determining configuration information, applied to a terminal device, the device comprising: An acquisition unit, configured to determine target MBS configuration information when the terminal device performs cell selection and reselects to a target cell; A communication unit is configured to receive a multicast MBS service based on the target MBS configuration information.

8. A terminal device, comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method as claimed in any one of claims 1 to 6.

9. A chip, comprising: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 6.

10. A computer-readable storage medium for storing a computer program, wherein the computer program enables a computer to execute the method according to any one of claims 1 to 6.

Images