Multicast service processing method, device, related equipment and storage medium

Abstract

The present application discloses a method, device, terminal, network node and storage medium for processing multicast services. The method includes: when the terminal is in an idle state or an inactive state, changing from a first cell to a second cell; sending a first request to a first network node where the second cell is located; the first request is used to request to receive resource information of at least one multicast service; receiving resource information of receiving at least one multicast service sent by the first network node.

Description

Technical Field

[0001] The present application relates to the field of Multimedia Broadcast Multicast Service (MBMS), and in particular to a method, apparatus, related equipment and storage medium for processing a multicast service. Background Art

[0002] In the Long Term Evolution (LTE) system, MBMS is transmitted using the Multimedia Broadcast Multicast Service Single Frequency Network (MBSFN). MBMS is a point-to-multipoint service, such as mobile TV. For MBMS transmission, it is required that the evolved NodeBs (eNBs) of multiple cells in a certain MBSFN area (MBSFN Area) transmit the same data at the same time. In this way, the user equipment (UE) will not be affected by the inter-cell interference when the adjacent cells transmit data, but will also benefit from the superposition of signals from multiple cells. The UE receives and combines signals from multiple eNBs, which can improve the signal-to-noise ratio and effectively improve the transmission efficiency of MBMS. In the current LTE system, a UE with MBMS capability sends MBMS in a cell using the single-cell point-to-multipoint (SC-PTM) technology. The biggest difference between the multicast technology of the fifth generation new radio (NR) and the SC-PTM technology of LTE is that in the SC-PTM technology of LTE, after the upper application layer on the network side obtains a multicast service, it determines that this is a data packet of a multicast service based on the information in the IP header, and then sends a request to establish the multicast service to the core network. Then the core network establishes a shared tunnel with the base station based on the IP address information of the service packet, but neither the core network nor the base station perceives whether there is a UE in the cell that needs to receive the multicast service. In other words, the core network and the base station do not need to specifically trigger the establishment of the control plane, tunnel, and user bearer for the multicast service. However, in the multicast technology of 5G NR, a UE needs to join a multicast session (which can be expressed as join amulticast session in English) to trigger the core network and the base station to establish the control plane, tunnel, and user bearer for the multicast service. If there is no UE that needs to receive the multicast service, the control plane, tunnel, and user bearer of the multicast service will be deleted, so this requires the UE to remain in the connected state when receiving the multicast service. However, being in the connected state will cause the UE to consume more power and occupy more base station resources. Therefore, in order to reduce power consumption, the UE can enter the idle state (IDLE) or inactive state (INACTIVE) in some cases.

[0003] However, for UE, how to perform multicast services in an idle state or an inactive state is a problem that needs to be solved urgently. Summary of the invention

[0004] To solve related technical problems, the embodiments of the present application provide a method, apparatus, related equipment and storage medium for processing a multicast service.

[0005] The technical solution of the embodiment of the present application is implemented as follows:

[0006] The embodiment of the present application provides a method for processing a multicast service, which is applied to a terminal, including:

[0007] The terminal changes from the first cell to the second cell when in an idle state or an inactive state;

[0008] Sending a first request to a first network node where the second cell is located; the first request is used to request receiving resource information of at least one multicast service;

[0009] Receive resource information for receiving at least one multicast service sent by the first network node.

[0010] In the above solution, the first request carries at least one of the following information:

[0011] a temporary mobile group identifier (TMGI) corresponding to at least one multicast service requested to be received;

[0012] a multicast session identifier corresponding to at least one multicast service requested to be received;

[0013] a multicast quality of service (QoS) flow identifier corresponding to at least one multicast service requested to be received;

[0014] a multicast radio bearer (MRB) identifier corresponding to at least one multicast service requested to be received;

[0015] A multicast IP address corresponding to at least one multicast service requested to be received;

[0016] A group radio network temporary identifier (G-RNTI) corresponding to at least one multicast service requested to be received;

[0017] identification information of the terminal;

[0018] First cell information;

[0019] or,

[0020] The first request is a sounding reference signal (SRS) with a multicast broadcast service (MBS) service as the granularity and / or with an MBS group as the granularity.

[0021] In the above scheme, the method further comprises:

[0022] When one of the following conditions is met, a second request is sent to the first network node, where the second request is used to request to establish a multicast session corresponding to at least one multicast service requested to be received:

[0023] receiving a reply message sent by the first network node indicating that at least one requested multicast service does not exist;

[0024] receiving first information sent by the first network node, wherein the first information instructs the terminal to initiate a request to establish a multicast session corresponding to at least one requested multicast service to the network side;

[0025] Second information sent by the first network node is received, where the second information instructs the terminal to send non-access stratum (NAS) configuration information of a multicast service received in a first cell and stored by the terminal.

[0026] In the above solution, the sending the second request to the first network node where the second cell is located includes:

[0027] Sending a multicast session establishment request message of at least one requested multicast service to the first network node;

[0028] Alternatively, the second request carries the NAS configuration information of the multicast service received in the first cell and / or the first cell information saved by the terminal.

[0029] In the above solution, the sending the first request to the first network node where the second cell is located includes:

[0030] It is detected that a multicast session corresponding to at least one requested multicast service and / or a shared tunnel corresponding to at least one requested multicast service in the second cell are not established, and a first request is sent to a first network node where the second cell is located.

[0031] In the above solution, detecting whether a multicast session corresponding to at least one multicast service requested in the second cell and / or a shared tunnel corresponding to at least one multicast service requested is established includes:

[0032] Detecting from the system message of the second cell whether there is control information of at least one multicast service requested to be received;

[0033] When the control information of the at least one requested multicast service exists, determining that a multicast session corresponding to the at least one requested multicast service and / or a shared tunnel corresponding to the at least one requested multicast service in the second cell has been established; or

[0034] When control information of the at least one requested multicast service does not exist, it is determined that a multicast session corresponding to the at least one requested multicast service and / or a shared tunnel corresponding to the at least one requested multicast service in the second cell are not established.

[0035] In the above solution, the resource information includes at least one of the following information:

[0036] The TMGI corresponding to each one or more multicast services of receiving at least one multicast service;

[0037] The session identifier corresponding to each one or more multicast services of receiving at least one multicast service;

[0038] The G-RNTI corresponding to each one or more multicast services of receiving at least one multicast service;

[0039] At least one of time domain information, frequency domain information and spatial domain information corresponding to each one or more multicast services of the received at least one multicast service;

[0040] The receiving scheduling information corresponding to each one or more multicast services of at least one multicast service;

[0041] The receiving of configuration information of the wireless side corresponding to each one or more multicast services of at least one multicast service;

[0042] Multicast service list.

[0043] In the above scheme, the multicast service list includes at least one of the following:

[0044] TMGI corresponding to each multicast service or services;

[0045] A session identifier corresponding to each one or more multicast services;

[0046] G-RNTI corresponding to each multicast service or services;

[0047] The correspondence between point-to-multipoint configuration information and multicast services;

[0048] The mapping relationship between multicast services and logical channels;

[0049] Priority information of multicast services.

[0050] In the above solution, the priority information of the multicast service includes at least one of the following:

[0051] Priority information corresponding to multicast services;

[0052] Priority information of the logical channel corresponding to the multicast service;

[0053] Priority information of the semi-static scheduling (SPS) corresponding to the multicast service;

[0054] Priority information of the newly transmitted data and / or retransmitted data corresponding to the multicast service relative to the newly transmitted data and / or retransmitted data of the unicast service;

[0055] Preemption priority information of new transmission data and / or retransmission data corresponding to the multicast service relative to the new transmission data and / or retransmission data of the unicast service;

[0056] Priority information of data corresponding to the multicast service relative to the measurement interval;

[0057] The priority of the data corresponding to the multicast service relative to the downlink media access control element (MAC CE);

[0058] A mapping relationship between a multicast service and at least one of a multicast or broadcast control channel (MCCH) and a multicast or broadcast traffic channel (MTCH);

[0059] The mapping relationship between multicast services and multicast-related Radio Network Temporary Identifiers (RNTIs);

[0060] Shared tunnel information used for sending or receiving multicast services;

[0061] IP multicast address information used for sending or receiving multicast services;

[0062] The media type of the multicast service;

[0063] MBS area information corresponding to the second cell.

[0064] In the above solution, the receiving resource information for receiving at least one multicast service sent by the first network node includes:

[0065] Resource information for receiving at least one multicast service sent by the first network node is received through radio resource control (RRC) signaling and / or NAS information.

[0066] In the above solution, the terminal enters a connected state from an idle state or an inactive state, and sends a first request to the second cell;

[0067] After receiving the resource information for receiving at least one multicast service sent by the first network node, the idle state or the inactive state is entered again.

[0068] In the above scheme, receiving a system message;

[0069] Acquire configuration information of a first resource from the system message; the first resource is shared by at least two terminals;

[0070] A first request is sent to the first network node over the first resource.

[0071] In the above solution, the step of changing from the first cell to the second cell includes:

[0072] receiving fourth information when in the first cell; the fourth information represents a multicast service being sent by at least one neighboring cell;

[0073] Using the first information, perform at least one of the following operations to change from the first cell to the second cell:

[0074] Cell selection;

[0075] Cell reselection;

[0076] Community reconstruction.

[0077] In the above scheme, the method further includes:

[0078] When the terminal is in an idle state or an inactive state, third information is sent to the second network node where the first cell is located; the third information is used to indicate at least one of the following information:

[0079] The terminal leaves the shared tunnel of the requested at least one multicast service;

[0080] The terminal stops receiving the at least one requested multicast service;

[0081] The terminal stops receiving the requested at least one multicast service in the first cell;

[0082] The terminal leaves the first cell;

[0083] The terminal will enter or has entered the second cell;

[0084] The terminal stops receiving the at least one requested multicast service at a first time point;

[0085] The terminal stops receiving the at least one requested multicast service within a first time range;

[0086] The terminal enters or has entered the second cell at a second time point;

[0087] The terminal enters or has entered the second cell within a second time range.

[0088] In the above solution, the sending the third information to the second network node where the first cell is located includes:

[0089] The third information is sent to the second network node through message 1, message A or message 3 of random access.

[0090] In the above solution, when the second cell and the first cell do not belong to the same MBS area, sending the first request to the second network node;

[0091] When the second cell and the first cell belong to the same MBS area, the multicast service is received directly by using the resource information of the multicast service receiving resources obtained in the first cell.

[0092] In the above solution, the MBS area includes at least one of the following characteristics:

[0093] The MBS area includes at least one cell and at least one of the MBS service types sent between the cells is the same;

[0094] The MBS area includes at least one cell and the MBS service types sent between the cells are the same;

[0095] The time domain resources of MBS services sent by cells within the MBS area are the same;

[0096] The frequency domain resources of MBS services transmitted by cells within the MBS area are the same;

[0097] The RNTI used by different cells in the MBS area to activate MBS services or to scramble the signaling for the paging terminal to enter the connected state to receive MBS services is the same;

[0098] The RNTI used for signaling scrambling of MBS services in different cells within the MBS area is the same;

[0099] Time synchronization between different cells within the MBS area;

[0100] The cells within the MBS area send cell-specific synchronization signal blocks SSB and / or channel state information reference signals CSI-RS, and also send SSB and / or CSI-RS with the MBS area as the granularity;

[0101] The cells within the MBS area send cell-specific SSBs and / or CSI-RSs, and also send SSBs and / or CSI-RSs with a granularity of specific MBS services within the MBS area;

[0102] In addition to sending the cell-specific SSB, the cells within the MBS area also send the same demodulation reference signal DMRS within the MBS area with the specific MBS service within the MBS area as the granularity.

[0103] In the above solution, the MBS area includes at least one of the following characteristics:

[0104] When the terminal is in idle or inactive state, it receives MBS services in a cell within the MBS area and does not need to inform the network when changing from one cell to another;

[0105] The terminal and multiple cells and / or base stations in the MBS area can receive at least one same MBS service in multiple cells through carrier aggregation and / or multi-connection.

[0106] The embodiment of the present application further provides a method for processing a multicast service, which is applied to a first network node and includes:

[0107] A first request sent by a receiving terminal when the receiving terminal is in an idle state or an inactive state; the first request is used to request resource information for receiving at least one multicast service; the terminal in the idle state or the inactive state can receive the requested at least one multicast service in the second cell;

[0108] Send resource information for receiving at least one multicast service to the terminal.

[0109] In the above solution, when a multicast session and / or a shared tunnel corresponding to at least one multicast service requested in the second cell has been established, resource information for receiving at least one multicast service is sent to the terminal.

[0110] In the above scheme, the method further includes:

[0111] When a multicast session and / or a shared tunnel corresponding to at least one multicast service requested in the second cell is not established, sending first information to the terminal, wherein the first information instructs the terminal to initiate a request to establish a multicast session of the requested multicast service to the network side;

[0112] or,

[0113] When a multicast session and / or a shared tunnel corresponding to at least one multicast service requested in the second cell is not established, sending second information to the terminal, wherein the second information instructs the terminal to send NAS configuration information of the multicast service received in the first cell and stored by the terminal;

[0114] or,

[0115] When a multicast session and / or a shared tunnel corresponding to at least one multicast service requested in the second cell is not established, initiating a process of acquiring relevant configuration information of the multicast service received by the terminal in the first cell from a second network node where the first cell is located;

[0116] or,

[0117] When the multicast session and / or shared tunnel corresponding to the at least one multicast service requested in the second cell is not established, reply information indicating that the at least one multicast service requested does not exist is sent to the terminal.

[0118] In the above scheme, the method further includes:

[0119] A second request sent by the terminal is received, where the second request is used to request to establish a multicast session corresponding to at least one multicast service requested to be received.

[0120] In the above solution, the receiving the second request sent by the terminal includes:

[0121] receiving a multicast session establishment request message of at least one requested multicast service sent by the terminal;

[0122] or,

[0123] The second request carries the NAS configuration information of the multicast service received in the first cell and / or the first cell information saved by the terminal.

[0124] In the above scheme, a system message is broadcast; the system message includes configuration information of a first resource; the first resource is shared by at least two terminals;

[0125] A first request sent by the terminal on a first resource is received.

[0126] A method for processing a multicast service in the above solution is applied to a second network node, comprising:

[0127] The receiving terminal sends third information when the receiving terminal is in an idle state or an inactive state; the third information is used to indicate at least one of the following information:

[0128] The terminal leaves a shared tunnel of at least one multicast service;

[0129] The terminal stops receiving at least one multicast service;

[0130] The terminal stops receiving at least one multicast service in the first cell;

[0131] The terminal leaves the first cell;

[0132] The terminal will enter or has entered the second cell;

[0133] The terminal stops receiving at least one multicast service at a first time point;

[0134] The terminal stops receiving at least one multicast service within a first time range;

[0135] The terminal enters or has entered the second cell at a second time point;

[0136] The terminal enters or has entered the second cell within a second time range; wherein,

[0137] When the terminal is in an idle state or an inactive state, the identifier of the terminal is retained in a first list; the first list contains at least one terminal identifier of a shared tunnel using at least one multicast service, or the first list contains at least one terminal identifier for establishing at least one multicast session, or the first list contains at least one terminal identifier for establishing a QoS flow of at least one multicast session, or the first list contains at least one terminal identifier for establishing at least one MRB.

[0138] In the above solution, the receiving terminal sends the third information via message 1, message A or message 3 through random access.

[0139] The embodiment of the present application further provides a method for processing a multicast service, which is applied to a third network node, including:

[0140] receiving a first paging message for at least one multicast service sent by a fourth network node;

[0141] Generate a second paging message using the first paging message; the second paging message is for at least one multicast service;

[0142] Send the second paging message.

[0143] In the above solution, the second paging message is scrambled with the G-RNTI corresponding to the at least one multicast service.

[0144] In the above scheme, when the terminal is in an idle state or an inactive state, the identifier of the terminal is retained in the second list; the second list contains at least one terminal identifier of a shared tunnel using the first multicast service, or the second list contains at least one terminal identifier for establishing at least one multicast session, or the second list contains at least one terminal identifier for a QoS flow for establishing at least one multicast session, or the second list contains at least one terminal identifier for establishing at least one MRB.

[0145] In the above scheme, the method further comprises:

[0146] The paging occasion (PO) and paging frame (PF) are determined using the identifier associated with the multicast service.

[0147] In the above solution, the identifier related to the multicast service includes at least one of the following:

[0148] TMGI corresponding to the multicast service;

[0149] The multicast session identifier corresponding to the multicast service;

[0150] Multicast QoS flow identifier corresponding to the multicast service;

[0151] MRB identifier corresponding to the multicast service;

[0152] G-RNTI corresponding to the multicast service;

[0153] IP address corresponding to the multicast service;

[0154] TMSI corresponding to the multicast service.

[0155] The embodiment of the present application also provides a method for processing a multicast service, which is applied to a terminal, including:

[0156] A second paging message is monitored and received on the PO and / or the PF; the second paging message is for at least one multicast service.

[0157] In the above solution, the second paging message is scrambled with the G-RNTI corresponding to the at least one multicast service.

[0158] In the above scheme, the method further comprises:

[0159] At least two of the following messages are detected or received at the same time period or at the same time point:

[0160] Paging messages for system information updates;

[0161] Paging messages for mobile terminated data;

[0162] Paging message for activation or opening of MBS data;

[0163] A paging message for deactivation or stop of MBS data;

[0164] Reception of paging messages is performed in one of the following reception priority orders:

[0165] The order of receiving priority from high to low is: paging message for system message update, paging message for mobile terminated data, paging message for activation or opening of MBS data, paging message for deactivation or stopping of MBS data;

[0166] The order of receiving priority from high to low is: paging message for updating the first type of system message, paging message for mobile terminated data, paging message for activating or starting MBS data, paging message for updating non-first type of system message, paging message for deactivating or stopping MBS data; the first type of system message includes at least one of the following: main system information block (MIB), system information block 1 (SIB1), earthquake tsunami early warning system (ETWS), public warning system (PWS);

[0167] The order of receiving priority from high to low is: paging message for updating first-category system messages, paging message for mobile terminated data and paging message for activating or starting MBS data, paging message for updating non-first-category system messages, and paging message for deactivating or stopping MBS data; the first-category system message includes at least one of the following: MIB, SIB1, ETWS, PWS; the priority of the paging message for mobile terminated data and the paging message for activating or starting MBS data is determined according to the service priority of one.

[0168] In the above solution, the PO and PF are determined using identifiers related to the multicast service.

[0169] In the above solution, the identifier related to the multicast service includes at least one of the following:

[0170] TMGI corresponding to the multicast service;

[0171] The multicast session identifier corresponding to the multicast service;

[0172] Multicast QoS flow identifier corresponding to the multicast service;

[0173] MRB identifier corresponding to the multicast service;

[0174] G-RNTI corresponding to the multicast service;

[0175] IP address corresponding to the multicast service;

[0176] TMSI corresponding to the multicast service.

[0177] The embodiment of the present application also provides a multicast service processing device, including:

[0178] A changing unit, used for changing from a first cell to a second cell when the terminal is in an idle state or an inactive state;

[0179] A first sending unit, configured to send a first request to a first network node where the second cell is located; the first request is used to request to receive resource information of at least one multicast service;

[0180] The first receiving unit is configured to receive resource information for receiving at least one multicast service sent by the first network node.

[0181] The embodiment of the present application also provides a multicast service processing device, including:

[0182] A second receiving unit is used to receive a first request sent by a terminal in an idle state or an inactive state; the first request is used to request to receive resource information of at least one multicast service; the terminal in the idle state or the inactive state can receive the requested at least one multicast service in the second cell;

[0183] The second sending unit is used to send resource information for receiving at least one multicast service to the terminal.

[0184] The embodiment of the present application also provides a multicast service processing device, including:

[0185] The third receiving unit is configured to receive third information sent when the terminal is in an idle state or an inactive state; the third information is used to indicate at least one of the following information:

[0186] The terminal leaves a shared tunnel of at least one multicast service;

[0187] The terminal stops receiving at least one multicast service;

[0188] The terminal stops receiving at least one multicast service in the first cell;

[0189] The terminal leaves the first cell;

[0190] The terminal will enter or has entered the second cell;

[0191] The terminal stops receiving at least one multicast service at a first time point;

[0192] The terminal stops receiving at least one multicast service within a first time range;

[0193] The terminal enters or has entered the second cell at a second time point;

[0194] The terminal enters or has entered the second cell within a second time range; wherein,

[0195] When the terminal is in an idle state or an inactive state, the identifier of the terminal is retained in a first list; the first list contains at least one terminal identifier of a shared tunnel using at least one multicast service, or the first list contains at least one terminal identifier for establishing at least one multicast session, or the first list contains at least one terminal identifier for establishing a QoS flow of at least one multicast session, or the first list contains at least one terminal identifier for establishing at least one MRB.

[0196] The embodiment of the present application also provides a multicast service processing device, including:

[0197] a fourth receiving unit, configured to receive a first paging message for at least one multicast service sent by a fourth network node;

[0198] A generating unit, configured to generate a second paging message using the first paging message;

[0199] The third sending unit is configured to send the second paging message.

[0200] The embodiment of the present application also provides a multicast service processing device, including:

[0201] The paging unit is used to monitor and receive a second paging message on the PO and / or PF; the second paging message is for at least one multicast service.

[0202] The embodiment of the present application also provides a terminal, comprising: a first processor and a first communication interface; wherein,

[0203] The first processor is used to change from the first cell to the second cell when the terminal is in an idle state or an inactive state; the first communication interface is used to send a first request to a first network node where the second cell is located; the first request is used to request to receive resource information of at least one multicast service; and receive resource information for receiving at least one multicast service sent by the first network node;

[0204] or,

[0205] The first processor is used to monitor and receive a second paging message on the PO and / or PF through the first communication interface; the second paging message is for at least one multicast service.

[0206] The embodiment of the present application further provides a first network node, comprising: a second processor and a second communication interface; wherein,

[0207] The second communication interface is used to receive a first request sent when the terminal is in an idle state or an inactive state; the first request is used to request resource information for receiving at least one multicast service; the terminal in an idle state or an inactive state can receive at least one requested multicast service in a second cell; and resource information for receiving at least one multicast service is sent to the terminal.

[0208] The embodiment of the present application further provides a second network node, including: a third processor and a third communication interface; wherein,

[0209] The third communication interface is used to receive third information sent when the terminal is in an idle state or an inactive state; the third information is used to indicate at least one of the following information:

[0210] The terminal leaves a shared tunnel of at least one multicast service;

[0211] The terminal stops receiving at least one multicast service;

[0212] The terminal stops receiving at least one multicast service in the first cell;

[0213] The terminal leaves the first cell;

[0214] The terminal will enter or has entered the second cell;

[0215] The terminal stops receiving at least one multicast service at a first time point;

[0216] The terminal stops receiving at least one multicast service within a first time range;

[0217] The terminal enters or has entered the second cell at a second time point;

[0218] The terminal enters or has entered the second cell within a second time range; wherein,

[0219] When the terminal is in an idle state or an inactive state, the identifier of the terminal is retained in a first list; the first list contains at least one terminal identifier of a shared tunnel using at least one multicast service, or the first list contains at least one terminal identifier for establishing at least one multicast session, or the first list contains at least one terminal identifier for establishing a QoS flow of at least one multicast session, or the first list contains at least one terminal identifier for establishing at least one MRB.

[0220] The embodiment of the present application further provides a third network node, including: a fourth processor and a fourth communication interface; wherein,

[0221] The fourth communication interface is used to receive a first paging message for at least one multicast service sent by a fourth network node;

[0222] The fourth processor is configured to generate a second paging message using the first paging message; the second paging message is for at least one multicast service;

[0223] The fourth communication interface is further used to send the second paging message.

[0224] The embodiment of the present application further provides a terminal, comprising: a first processor and a first memory for storing a computer program that can be run on the processor,

[0225] Wherein, when the first processor is used to run the computer program, any of the above-mentioned terminal side methods is executed.

[0226] The embodiment of the present application further provides a first network node, comprising: a second processor and a second memory for storing a computer program that can be run on the processor,

[0227] Wherein, the second processor is used to execute the steps of any one of the above-mentioned methods on the first network node side when running the computer program.

[0228] The embodiment of the present application further provides a second network node, comprising: a third processor and a third memory for storing a computer program that can be run on the processor,

[0229] The third processor is used to execute the steps of any one of the above-mentioned methods on the second network node side when running the computer program.

[0230] The embodiment of the present application further provides a third network node, including: a fourth processor and a fourth memory for storing a computer program that can be run on the processor,

[0231] The fourth processor is configured to execute the steps of any one of the above-mentioned methods on the third network node side when running the computer program.

[0232] An embodiment of the present application also provides a storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the computer program implements the steps of any of the methods on the terminal side, or the steps of any of the methods on the first network node side, or the steps of any of the methods on the second network node side, or the steps of any of the methods on the third network node side.

[0233] The method, apparatus, related equipment and storage medium for processing multicast services provided in the embodiments of the present application, when the terminal is in an idle state or an inactive state, it changes from the first cell to the second cell; the first request is sent to the first network node where the second cell is located; the first request is used to request to receive resource information of at least one multicast service; and the resource information for receiving at least one multicast service sent by the first network node is received. In the scheme provided in the embodiments of the present application, when the terminal in an idle state or an inactive state changes from one cell to another cell, it is necessary to perform signaling interaction with another cell to obtain the resources of the multicast service of interest, so as to ensure that the terminal can receive the multicast service of interest in the changed cell. On the other hand, the third network node receives the first paging message for at least one multicast service sent by the fourth network node; generates a second paging message using the first paging message; sends the second paging message; the terminal detects the second paging message for at least one multicast service in PO and / or PF, so that paging for the multicast service is realized. BRIEF DESCRIPTION OF THE DRAWINGS

[0234] Figure 1A flowchart of a method for processing a multicast service according to an embodiment of the present application;

[0235] Figure 2 This is a flow chart of a method for processing a second multicast service according to an embodiment of the present application;

[0236] Figure 3 This is a flowchart of a method for processing a third multicast service according to an embodiment of the present application;

[0237] Figure 4 This is a flowchart of a method for processing a fourth multicast service according to an embodiment of the present application;

[0238] Figure 5 This is a schematic diagram of the interaction between various devices in the processing of the multicast service in the application embodiment of the present application;

[0239] Figure 6 This is a schematic diagram of the structure of a processing device for the first multicast service according to an embodiment of the present application;

[0240] Figure 7 This is a schematic diagram of the structure of a processing device for a second multicast service according to an embodiment of the present application;

[0241] Figure 8 This is a schematic diagram of the structure of a processing device for a third multicast service according to an embodiment of the present application;

[0242] Fig. 9 This is a schematic diagram of the structure of a processing device for a fourth multicast service according to an embodiment of the present application;

[0243] Fig.10 This is a schematic diagram of the structure of a processing device for a fifth multicast service according to an embodiment of the present application;

[0244] Fig.11 This is a schematic diagram of the terminal structure of an embodiment of the present application;

[0245] Fig.12 This is a schematic diagram of the structure of the first network node in an embodiment of the present application;

[0246] Fig.13 This is a schematic diagram of the structure of the second network node in the embodiment of the present application;

[0247] Fig.14 This is a schematic diagram of the third network node structure of an embodiment of the present application. DETAILED DESCRIPTION

[0248] The present application is further described in detail below in conjunction with the accompanying drawings and embodiments.

[0249] In the NR system, for some multicast services with low QoS requirements, the UE can receive these multicast services in the idle state or inactive state. For example, in cell 1, the terminal can join a multicast service through NAS information, called multicast service 1. The reliability requirement of multicast service 1 is not too high, that is, the QoS of multicast service 1 is low. The terminal can also receive multicast service 1 in the idle state or inactive state. In this case, if there is no other dedicated service at this time, the terminal enters the idle state or inactive state and receives the data of the multicast service. As the terminal moves, when the terminal moves from cell 1 to cell 2, if the two cells belong to the same tracking area (TA) or notification area (RANA) of the radio access network, the base station will not perceive the change of the terminal's cell. In this way, when the terminal is in cell 2, if cell 2 currently does not have multicast service 1 sending, the terminal will not receive the data of multicast service 1. That is to say, once the terminal is in an idle or inactive state, if there is a change in the cell belonging to the same TA or RANA area, the network side cannot perceive it. If the new cell is not sending the corresponding multicast service, the terminal will interrupt the reception of the service. Therefore, in this case, how to ensure that the terminal can receive the multicast service normally, there is no effective solution in the relevant technology.

[0250] Based on this, in various embodiments of the present application, when a terminal in an idle or inactive state changes from one cell to another, it is necessary to perform signaling interaction with the other cell (i.e., the network node where the other cell is located) to obtain resources for the multicast service of interest to itself, thereby ensuring that the terminal can receive the multicast service of interest to itself in the changed cell.

[0251] In the embodiment of the present application, the groupcast service may also be referred to as a multicast service. The network node may include at least one of the following:

[0252] Public Land Mobile Network (PLMN);

[0253] Core network control node;

[0254] Base station;

[0255] Centralized Unit (CU);

[0256] Distribution Unit (DU);

[0257] relay;

[0258] Integrated access and backhaul (IAB) nodes;

[0259] Baseband unit (BBU);

[0260] Baseband processing unit.

[0261] The embodiment of the present application provides a method for processing a multicast service, which is applied to a terminal, such as Figure 1 As shown, the method includes:

[0262] Step 101: When the terminal is in an idle state or an inactive state, the terminal changes from a first cell to a second cell;

[0263] Step 102: Send a first request to a first network node where the second cell is located; the first request is used to request to receive resource information of at least one multicast service;

[0264] Step 103: Receive resource information for receiving at least one multicast service sent by the first network node.

[0265] In actual application, the terminal may also be a UE, a relay, an IAB node, an aircraft device with a communication function, an automated device with a communication function, or a user, that is, in different scenarios, the terminal may be a different device.

[0266] In step 101, the terminal performs at least one of the following operations to change from a first cell to a second cell:

[0267] Cell selection;

[0268] Cell reselection;

[0269] Community reconstruction.

[0270] The cell reconstruction refers to the process of re-establishing radio resource control (RRC) after the radio link loses synchronization.

[0271] Here, in actual application, the terminal can periodically obtain information about the multicast services being sent between base stations, so that the terminal can select a cell based on this information and change the cell. Since the multicast services being sent by each cell are taken into consideration when changing the cell, the terminal can ensure the reception of the multicast services after changing the cell.

[0272] Based on this, in one embodiment, the changing from the first cell to the second cell includes:

[0273] receiving fourth information when in the first cell; the fourth information represents a multicast service being sent by at least one neighboring cell;

[0274] Using the fourth information, perform at least one of the following operations to change from the first cell to the second cell:

[0275] Cell selection;

[0276] Cell reselection;

[0277] Community reconstruction.

[0278] Exemplarily, the base station maintains a list of cells that are simultaneously sending multicast services in the system message, i.e., the first information. The information in the cell list may include: cell identification, such as ID; multicast service information supported by the cell; multicast service information being sent by the cell (such as TMGI, tunnel information, QoS flow information); whether it is consistent with the multicast service sent by this cell; if consistent, whether the sent packets are synchronized; if not synchronized, what is the gap (expressed as GAP in English) between the sequence numbers (SN), where the gap can be in units of the SN of the Packet Data Convergence Protocol (PDCP) or the SN of the GPRS Tunnel Protocol-User Plane (GTP-U).

[0279] In actual application, in step 102, the resource information of the multicast service includes at least one of the following:

[0280] resource information of at least one multicast service requested to be received;

[0281] Resource information of a multicast session corresponding to at least one multicast service requested to be received;

[0282] Resource information of a multicast QoS flow corresponding to at least one multicast service requested to be received;

[0283] The resource information of the MRB corresponding to at least one multicast service to be received is requested.

[0284] There is a one-to-one, one-to-many, or many-to-one situation between any two of the multicast service, multicast session, multicast QoS flow and MRB.

[0285] The terminal can actively detect whether a multicast session corresponding to at least one multicast service requested in the second cell and / or a shared tunnel corresponding to at least one multicast service requested have been established, so as to determine whether to directly request resource information for receiving at least one multicast service from the first network node, or to request to establish a multicast session corresponding to at least one multicast service requested and / or a shared tunnel corresponding to at least one multicast service requested.

[0286] Specifically, when the terminal detects that a multicast session corresponding to at least one multicast service requested in the second cell and / or a shared tunnel corresponding to at least one multicast service requested has been established, a first request is sent to the first network node. At this time, the first request is used to request to receive resource information of at least one multicast service.

[0287] When the terminal detects that the multicast session corresponding to at least one multicast service requested in the second cell and / or the shared tunnel corresponding to at least one multicast service requested are not established, a first request is sent to the first network node where the second cell is located. At this time, the first request is used to request to receive resource information of at least one multicast service, and to request to establish a multicast session corresponding to at least one multicast service requested to be received. It can also be understood that the first request is also used to request to establish a multicast session corresponding to at least one multicast service requested and / or a shared tunnel corresponding to at least one multicast service requested.

[0288] In one embodiment, the first request carries at least one of the following information:

[0289] The TMGI corresponding to at least one multicast service requested to be received;

[0290] a multicast session identifier corresponding to at least one multicast service requested to be received, such as a multicast session ID;

[0291] A multicast QoS flow identifier corresponding to at least one multicast service requested to be received, such as a QoS flow ID;

[0292] An MRB identifier corresponding to at least one multicast service requested to be received;

[0293] A multicast IP address corresponding to at least one multicast service requested to be received;

[0294] The G-RNTI corresponding to at least one multicast service requested to be received;

[0295] identification information of the terminal;

[0296] First cell information;

[0297] or,

[0298] The first request is an SRS with an MBS service as the granularity and / or an MBS group as the granularity.

[0299] The first cell information may include: a physical cell identifier (PCI) or a global cell identifier (CGI) of the first cell, and an MBS area to which the first cell belongs, that is, a multicast area to which the first cell belongs.

[0300] The identification information of the terminal may also be identification information of multiple terminals or identification information of a terminal group. For example, when multiple terminals receiving the same MBS service change cells together (e.g., a group of AGVs (Automated Guided Vehicles) receiving commands from a control console together at a port), a master terminal among the multiple terminals sends the first request to the network side. The master terminal informs the network of the information of the multiple terminals. Alternatively, the master terminal informs the network of the identification information of the terminal group.

[0301] The determination of the master terminal may be obtained by negotiation between the terminals through communication means such as a sidelink, Bluetooth, or WiFi. Here, the specific negotiation strategy may be determined based on factors such as information quality and / or the location of the terminal, and the embodiment of the present application does not limit this. The determination of the master terminal may also be configured by the network.

[0302] In one embodiment, the terminal detects from the system message of the second cell whether there is control information of at least one multicast service requested to be received;

[0303] When control information of the at least one requested multicast service exists, determining that a multicast session corresponding to the at least one requested multicast service and / or a shared tunnel corresponding to the at least one requested multicast service in the second cell has been established;

[0304] When control information of the at least one requested multicast service does not exist, it is determined that a multicast session corresponding to the at least one requested multicast service and / or a shared tunnel corresponding to the at least one requested multicast service in the second cell are not established.

[0305] Here, in actual application, the control information can be sent on MCCH or broadcast message, so that after the terminal in idle state or inactive state and receiving multicast service changes to a new cell, it first detects the MCCH in the cell and the content of MTCH, and determines whether it is necessary to send the first request based on this information, that is, determines whether the multicast session corresponding to at least one requested multicast service and / or the shared tunnel corresponding to at least one requested multicast service in the second cell have been established based on this information, and when it is determined that it is necessary to send a request message for establishing the multicast session corresponding to at least one requested multicast service and / or the shared tunnel corresponding to at least one requested multicast service, that is, after determining to send the first request, the first request is sent.

[0306] Here, the multicast session corresponding to the at least one requested multicast service and / or the shared tunnel corresponding to the at least one requested multicast service not being established may include at least one of the following:

[0307] The multicast session and / or shared tunnel is indeed not established;

[0308] The established multicast session and / or shared tunnel is stopped;

[0309] The established multicast session and / or shared tunnel is suspended;

[0310] The established multicast session and / or shared tunnel is deactivated.

[0311] In actual application, the terminal may not actively detect whether the multicast session corresponding to at least one multicast service requested in the second cell and / or the shared tunnel corresponding to at least one multicast service requested have been established, but the network side may notify the terminal whether the multicast session corresponding to at least one multicast service requested in the second cell and / or the shared tunnel corresponding to at least one multicast service requested have been established.

[0312] Specifically, when the multicast session corresponding to at least one multicast service requested in the second cell and / or the shared tunnel corresponding to at least one multicast service requested is not established, the first network node notifies the terminal, thereby triggering the terminal to initiate a multicast session establishment process corresponding to the multicast service.

[0313] Based on this, in one embodiment, the method may further include:

[0314] When one of the following conditions is met, a second request is sent to the first network node, where the second request is used to request to establish a multicast session corresponding to at least one multicast service requested to be received:

[0315] receiving a reply message sent by the first network node indicating that at least one requested multicast service does not exist;

[0316] receiving first information sent by the first network node, wherein the first information instructs the terminal to initiate a request to establish a multicast session corresponding to at least one requested multicast service to the network side;

[0317] Second information sent by the first network node is received, where the second information instructs the terminal to send NAS configuration information of the multicast service received in the first cell and stored by the terminal.

[0318] The second request may be understood as a request to establish a multicast session corresponding to at least one requested multicast service and / or a shared tunnel corresponding to at least one requested multicast service.

[0319] When the terminal receives a reply message sent by the first network node indicating that at least one requested multicast service does not exist, or when the terminal receives a first message sent by the first network node, or when the terminal receives a second message sent by the first network node, it indicates that the multicast session corresponding to at least one requested multicast service in the second cell and / or the shared tunnel corresponding to at least one requested multicast service have not been established, and the terminal needs to initiate a multicast session establishment request so that the core network and the first network node establish a multicast session corresponding to at least one requested multicast service and / or a shared tunnel corresponding to at least one requested multicast service.

[0320] Correspondingly, after receiving the above information, the second request sent by the terminal is also different according to the above different information.

[0321] Based on this, in one embodiment, sending the second request to the first network node where the second cell is located includes:

[0322] Sending a multicast session establishment request message of at least one requested multicast service to the first network node;

[0323] Alternatively, the second request carries NAS configuration information of the multicast service received in the first cell or first cell information saved by the terminal.

[0324] Among them, when receiving the reply information sent by the first network node indicating that the at least one requested multicast service does not exist, the terminal can send a multicast session establishment request message for the at least one requested multicast service to the first network node, that is, the second request is the multicast session establishment request message, or send a second request carrying the NAS configuration information of the multicast service received in the first cell saved by the terminal and / or the first cell information to the first network node, so that the first network node can establish a multicast session corresponding to the at least one requested multicast service and / or a shared tunnel corresponding to the at least one requested multicast service with the core network accordingly.

[0325] When the first information is received, the terminal can send a multicast session establishment request message for at least one requested multicast service to the first network node, so that the first network node can establish a multicast session corresponding to at least one requested multicast service and / or a shared tunnel corresponding to at least one requested multicast service with the core network.

[0326] When receiving the second information, the terminal can send the NAS configuration information of the multicast service received in the first cell saved by the terminal to the first network node, or send the NAS configuration information of the multicast service received in the first cell saved by the terminal and the first cell information, so that the first network node can establish a multicast session corresponding to at least one requested multicast service and / or a shared tunnel corresponding to at least one requested multicast service with the core network based on this.

[0327] Here, the NAS configuration information of the multicast service received in the first cell saved by the terminal may include: (source) IP address, GTP tunnel ID, multicast group identifier (such as TMGI or multicast address), media type, for example, voice, video, extended reality (XR) (XR refers to a real and virtual combination, human-computer interactive environment generated by computer technology and wearable devices, which is a general term for various forms such as augmented reality (AR), virtual reality (VR), and mixed reality (MR)), MBS QoS information, terminal authentication information (such as an external group identifier or a UE ID used for authentication), the entry address of the transport layer used to send multicast data, etc.

[0328] The terminal may enter a connected state from an idle state or an inactive state, then use resources in the connected state (such as RRC resources in the connected state) to send the first request, and then enter an idle state or an inactive state after receiving resource information for receiving at least one multicast service.

[0329] Based on this, in one embodiment, the terminal enters a connected state from an idle state or an inactive state, and sends a first request to the second cell;

[0330] After receiving the resource information for receiving at least one multicast service sent by the first network node, the idle state or the inactive state is entered again.

[0331] In actual application, the terminal may also send a first request in an idle state or an activated state. At this time, the base station broadcasts a shared uplink (UL) resource in the system message. Each multicast service (i.e., a multicast protocol data unit (PDU) session) or at least one QoS flow aggregated into an MRB corresponds to a shared UL resource, which is used for sending request messages for the terminal to join and leave the tunnel. In this way, the terminal does not need to enter a connected state. A default time advance (TA) value is given in the system message, and the TA value may be a TA value calculated based on the terminal farthest from the base station.

[0332] Based on this, in one embodiment, the receiving system message;

[0333] Acquire configuration information of a first resource from the system message; the first resource is shared by at least two terminals;

[0334] A first request is sent to the first network node over the first resource.

[0335] In step 103, resource information for receiving at least one multicast service received by the terminal may be sent via RRC signaling and NAS information.

[0336] Based on this, in one embodiment, the terminal receives resource information for receiving at least one multicast service sent by the first network node through RRC signaling and / or NAS information.

[0337] Here, the RRC signaling may carry resource information of the access stratum (AS); and the NAS information may carry resource information of the NAS.

[0338] In one embodiment, the resource information of receiving at least one multicast service may include at least one of the following information:

[0339] The TMGI corresponding to each one or more multicast services of receiving at least one multicast service may be one TMGI corresponding to each multicast service, or one TMGI corresponding to multiple multicast services;

[0340] The session identifier corresponding to each one or more multicast services of receiving at least one multicast service, such as a session ID, may be one session identifier corresponding to each multicast service, or one session identifier corresponding to multiple multicast services;

[0341] The G-RNTI corresponding to each one or more multicast services receiving at least one multicast service may be one G-RNTI corresponding to one multicast service, or one G-RNTI corresponding to multiple multicast services;

[0342] At least one of time domain information, frequency domain information and spatial domain information corresponding to each one or more multicast services of the received at least one multicast service;

[0343] The receiving scheduling information corresponding to each one or more multicast services of at least one multicast service;

[0344] The receiving of configuration information of the wireless side corresponding to each one or more multicast services of at least one multicast service;

[0345] Multicast service list.

[0346] The resource type in the frequency domain information may include at least one of the following resource types:

[0347] Carrier;

[0348] Bandwidth Part (BWP);

[0349] Common Frequency Resource (CFR);

[0350] Physical Resource Block (PRB).

[0351] The time domain information may include at least one of the following information of receiving the at least one multicast service requested:

[0352] Discontinuous Reception (DRX) information;

[0353] Received periodic information;

[0354] The starting position of reception;

[0355] The received physical downlink control channel (PDCCH) search space (which can be expressed in English as search space) and control resource set (CORESET) configuration information.

[0356] The spatial domain information may include beam precoding information, number of antennas, antenna ports, beam angles, beam directions and other information.

[0357] The scheduling information may include a modulation and coding strategy (MCS), a transport block length, and the like.

[0358] The configuration information of the wireless side may include at least one of the following:

[0359] Point-to-multipoint Service Data Adaptation Protocol (SDAP);

[0360] Configuration information of at least one of SDAP, PDCP, Radio Link Control (RLC), Medium Access Control (MAC), and Physical (PHY) layers.

[0361] The multicast service list includes at least one of the following:

[0362] TMGI corresponding to each multicast service or services;

[0363] A session identifier corresponding to each one or more multicast services;

[0364] G-RNTI corresponding to each multicast service or services;

[0365] The correspondence between the point-to-multipoint configuration information and the multicast service, that is, the correspondence between the point-to-multipoint configuration information and at least one multicast service;

[0366] The mapping relationship between multicast services and logical channels includes the mapping relationship between one multicast service and one logical channel, the mapping relationship between multiple multicast services and one logical channel, and the mapping relationship between one multicast service and multiple logical channels;

[0367] Priority information of multicast services.

[0368] In one embodiment, the priority information of the multicast service includes at least one of the following:

[0369] Priority information corresponding to multicast services;

[0370] Priority information of the logical channel corresponding to the multicast service;

[0371] The priority information of the SPS corresponding to the multicast service;

[0372] Priority information of the newly transmitted data and / or retransmitted data corresponding to the multicast service relative to the newly transmitted data and / or retransmitted data of the unicast service;

[0373] Preemption priority information of new transmission data and / or retransmission data corresponding to the multicast service relative to the new transmission data and / or retransmission data of the unicast service;

[0374] Priority information of data corresponding to the multicast service relative to the measurement interval;

[0375] The priority of the data corresponding to the multicast service relative to the downlink MAC CE;

[0376] A mapping relationship between a multicast service and at least one of the MCCH and the MTCH;

[0377] The mapping relationship between multicast services and multicast-related RNTIs;

[0378] Shared tunnel information used for sending or receiving multicast services;

[0379] IP multicast address information used for sending or receiving multicast services;

[0380] The media type of the multicast service;

[0381] MBS area information corresponding to the second cell.

[0382] The multicast-related RNTI includes at least one of the following:

[0383] RNTI used for MBS service scheduling, such as G-RNTI;

[0384] RNTI used to schedule MCCH modification signaling, such as multicast control RNTI (MC-RNTI);

[0385] RNTI used to schedule content on MCCH.

[0386] The media type includes at least one of the following:

[0387] Voice; Video; XR.

[0388] Among them, XR can specifically include at least one of AR, VR and MR.

[0389] The MBS area information includes at least one of an MBS area identifier, cell information within the MBS area, a multicast service type within the MBS area, a start time and / or an end time of sending a multicast service within the MBS area, and the like.

[0390] The terminal receives the at least one multicast service by using the obtained resources of the at least one multicast service.

[0391] After the terminal changes from the first cell to the second cell, the terminal may send tunnel leaving information to the first cell to notify the first cell that the terminal has left the tunnel.

[0392] Based on this, in one embodiment, the method may further include:

[0393] When the terminal is in an idle state or an inactive state, third information is sent to the second network node where the first cell is located; the third information is used to indicate at least one of the following information:

[0394] The terminal leaves the shared tunnel of the requested at least one multicast service;

[0395] The terminal stops receiving the at least one requested multicast service;

[0396] The terminal stops receiving the requested at least one multicast service in the first cell;

[0397] The terminal leaves the first cell;

[0398] The terminal will enter or has entered the second cell;

[0399] The terminal stops receiving the at least one requested multicast service at a first time point;

[0400] The terminal stops receiving the at least one requested multicast service within a first time range;

[0401] The terminal enters or has entered the second cell at a second time point;

[0402] The terminal enters or has entered the second cell within a second time range.

[0403] Here, in actual application, the terminal may use idle or inactive resources to send the third information.

[0404] Based on this, in one embodiment, the method may further include:

[0405] The third information is sent to the second network node through message 1, message A or message 3 of random access.

[0406] Here, it should be noted that: the terminal can use message 1, message A or message 3 in the random access process in the idle state or inactive state to send the second information to the second network node, or use message 1, message A or message 3 in the random access process in the connected state to send the second information to the second network node, and enter the idle state or inactive state again after sending the third information.

[0407] Exemplarily, when the terminal reselects from cell 1 to cell 2 due to reasons such as signal quality, the terminal and cell 1 perform the following signaling interaction:

[0408] The terminal sends tunnel leaving information to cell 1. The information may be sent in message 1 without the terminal entering the selection state, that is, the terminal identifier and the TMGI and / or PDU session information of the multicast service, and a 1-bit release indication are carried in the preamble; or the terminal identifier and the TMGI and / or PDU session information of the multicast service are carried in message 3, and the cause value is set to tunnel change (or other names, used to indicate the behavior of the terminal leaving the tunnel), or the terminal identifier and the TMGI and / or PDU session information of the multicast service are carried in message A, and the cause value is set to tunnel change (or other names, used to indicate the behavior of the terminal leaving the tunnel);

[0409] When cell 1 receives this message, if there are other terminals in cell 1 receiving the multicast service, the information of the terminal is deleted from the list of multicast terminals and the shared tunnel is kept unchanged; if there are no other terminals in cell 1 receiving the multicast service, the list of multicast terminals is cleared and the shared tunnel information is deleted; at the same time, the shared tunnel deletion information is sent to the core network.

[0410] In this embodiment of the present application, an MBS area may be defined, and when the second cell and the first cell do not belong to the same MBS area, the first request is sent to the second network node;

[0411] When the second cell and the first cell belong to the same MBS area, the multicast service is received directly by using the resource information of the multicast service receiving resources obtained in the first cell.

[0412] Here, in actual application, the terminal can determine whether the second cell and the first cell belong to the same MBS area based on the cell information in the configured MBS area, or can use other methods to determine whether the second cell and the first cell belong to the same MBS area. This embodiment of the present application is not limited to this.

[0413] The MBS area includes at least one of the following characteristics:

[0414] The MBS area includes at least one cell and at least one of the MBS service types sent between the cells is the same;

[0415] The MBS area includes at least one cell and the MBS service types sent between the cells are the same;

[0416] The time domain resources of MBS services sent by cells within the MBS area are the same;

[0417] The frequency domain resources of the MBS services sent by the cells within the MBS area are the same, and the resource type may include at least one of carrier, BWP, CFR and PRB;

[0418] The RNTI used by different cells in the MBS area to activate MBS services or to scramble the signaling for the paging terminal to enter the connected state to receive MBS services is the same;

[0419] The RNTI used for signaling scrambling of MBS services in different cells within the MBS area is the same;

[0420] Time synchronization between different cells within the MBS area;

[0421] The cells within the MBS area send cell-specific SSBs and / or CSI-RSs, and also send SSBs and / or CSI-RSs with the MBS area as the granularity;

[0422] The cells within the MBS area send cell-specific SSBs and / or CSI-RSs, and also send SSBs and / or CSI-RSs with a granularity of a specific MBS service within the MBS area. The SSBs and / or CSI-RSs with a granularity of a specific MBS service are the same within the MBS;

[0423] In addition to sending cell-specific SSBs, cells within the MBS area also send the same DMRS within the MBS area with a specific MBS service within the MBS area as the granularity. The DMRS with a specific MBS service as the granularity is the same within the MBS area.

[0424] In one embodiment, the MBS zone includes at least one of the following characteristics:

[0425] When the terminal is in idle or inactive state, it receives MBS services in a cell within the MBS area and does not need to inform the network when changing from one cell to another;

[0426] The terminal and multiple cells and / or base stations in the MBS area can receive at least one same MBS service in multiple cells through carrier aggregation and / or multi-connection.

[0427] Here, in actual application, multiple cells within a base station can adopt carrier aggregation technology, and multiple base stations can adopt multi-connection technology.

[0428] In actual application, the network side can configure the SRS with MBS service as the granularity for the terminal, and the SRS with MBS service as the granularity is valid or uniformly allocated within a certain area. The configuration information of SRS includes:

[0429] Information of the corresponding MBS service.

[0430] The MBS service information includes at least one of the following:

[0431] TMGI corresponding to MBS services;

[0432] The multicast session identifier corresponding to the MBS service;

[0433] Multicast QoS flow identifier corresponding to the MBS service;

[0434] MRB identifier corresponding to the MBS service;

[0435] Multicast IP address corresponding to MBS service;

[0436] G-RNTI corresponding to MBS services;

[0437] MBS group identifier;

[0438] Terminal information;

[0439] MBS area information;

[0440] List of cells to be applied;

[0441] The list of base stations used by the application;

[0442] Resource information of SRS;

[0443] SRS related logical channel information.

[0444] Among them, the definition of SRS configuration information is applicable to other parts of the embodiments of this application.

[0445] In addition, the terminal receiving the MBS service will periodically and / or event-based send the SRS corresponding to the MBS service (for example, the SRS uniformly allocated by the first network node and the second network node) to the network side; for example, if MBS service 1 corresponds to SRS1, the terminal receiving MBS service 1 will periodically and / or event-based send SRS1 to the network side, so that the network side can determine whether to trigger the establishment of a session related to the MBS service and / or a shared tunnel corresponding to the MBS service based on whether the SRS corresponding to the MBS service is received; for example, if the first network node receives the SRS1 sent by the terminal, it will trigger the establishment of a session related to MBS service 1 and / or a shared tunnel corresponding to MBS service 1; if it is found that the SRS1 is no longer received for a period of time, the session related to MBS service 1 and / or the shared tunnel corresponding to the MBS service 1 will be deleted, deactivated, or stopped.

[0446] In actual application, the network side can configure an SRS with MBS group as the granularity for the terminal, and the SRS with MBS group as the granularity is effective or uniformly allocated within a certain area (for example, uniformly allocated by the first network node and the second network node), wherein the MBS group is a terminal group that receives the same one or more MBS services. In addition, the terminals in the MBS group will periodically and / or event-based send the SRS corresponding to the MBS group to the network side; for example, at least one terminal in MBS group 1, where MBS group 1 is a terminal group that receives the same MBS service 1 and MBS service 2, will periodically and / or event-based send SRS1 to the network side. In this way, the network side can determine whether to trigger the establishment of a session related to the MBS service and / or a shared tunnel corresponding to the MBS service based on whether the SRS with the MBS group as the granularity is received. For example, if the first network node receives the SRS1 sent by the terminal, it will trigger the establishment of a session corresponding to the MBS service 1 and MBS service 2 and / or a shared tunnel corresponding to the MBS service 1 and MBS service 2; if it is found that the SRS1 is no longer received for a period of time, the session related to MBS service 1 and MBS service 2 and / or the shared tunnel corresponding to MBS service 1 and MBS service 2 will be deleted, deactivated, or stopped.

[0447] Accordingly, the embodiment of the present application also provides a method for processing a multicast service, which is applied to a first network node, such as Figure 2 As shown, the method includes:

[0448] Step 201: receiving a first request sent by a terminal in an idle state or an inactive state; the first request is used to request resource information for receiving at least one multicast service; the terminal in an idle state or an inactive state can receive the requested at least one multicast service in a second cell;

[0449] Step 202: Send resource information for receiving at least one multicast service to the terminal.

[0450] In one embodiment, when the multicast session and / or shared tunnel corresponding to at least one multicast service requested in the second cell has been established, resource information for receiving at least one multicast service is sent to the terminal, that is, resource information for receiving at least one multicast service is directly sent to the terminal.

[0451] Among them, the first network node can know whether there are other terminals receiving the at least one requested multicast service based on the relevant information of the at least one requested multicast service (the information carried in the first request), thereby being able to know whether the multicast session and / or shared tunnel corresponding to the at least one requested multicast service has been established; specifically, when there are other terminals receiving the at least one requested multicast service, it means that the multicast session and / or shared tunnel corresponding to the at least one requested multicast service has been established; when no other terminal is receiving the at least one requested multicast service, it means that the multicast session and / or shared tunnel corresponding to the at least one requested multicast service has not been established.

[0452] When the multicast session and / or shared tunnel corresponding to at least one requested multicast service in the second cell is not established, the second network node needs to establish a multicast session and / or shared tunnel corresponding to at least one requested multicast service with the core network in order to obtain resource information for receiving at least one requested multicast service.

[0453] That is to say, by sending a first request, the terminal can confirm to the first network node whether a multicast session and / or group tunnel corresponding to the multicast service exists. If so, the first network node will inform the terminal of the corresponding sending resource information; if not, a tunnel establishment request will be initiated to the core network.

[0454] Based on this, in one embodiment, the method may further include:

[0455] When a multicast session and / or a shared tunnel corresponding to at least one multicast service requested in the second cell is not established, sending first information to the terminal, wherein the first information instructs the terminal to initiate a request to establish a multicast session of the requested multicast service to the network side;

[0456] or,

[0457] When a multicast session and / or a shared tunnel corresponding to at least one multicast service requested in the second cell is not established, sending second information to the terminal, wherein the second information instructs the terminal to send NAS configuration information of the multicast service received in the first cell and stored by the terminal;

[0458] or,

[0459] When a multicast session and / or a shared tunnel corresponding to at least one multicast service requested in the second cell is not established, initiating a process of acquiring relevant configuration information of the multicast service received by the terminal in the first cell from the second network node where the first cell is located, that is, performing a tunnel transfer process;

[0460] or,

[0461] Sending reply information to the terminal indicating that at least one requested multicast service does not exist.

[0462] In one embodiment, the method may further include:

[0463] A second request sent by the terminal is received, where the second request is used to request to establish a multicast session corresponding to at least one multicast service requested to be received.

[0464] Specifically, the receiving the second request sent by the terminal includes:

[0465] A multicast session establishment request message for at least one requested multicast service is received from the terminal.

[0466] In response to the above information sent by the first network node, the second request carries the NAS configuration information of the multicast service received in the first cell and / or the first cell information saved by the terminal.

[0467] In actual application, after receiving the second request, the first network node interacts with the core network to establish a multicast session and / or shared tunnel corresponding to the at least one requested multicast service. When the first network node obtains the first cell information, the NAS configuration information of the multicast service received in the first cell saved by the terminal, and the relevant configuration information of the multicast service received by the terminal in the first cell, the multicast session and / or shared tunnel can be established using this information, so that the multicast session and / or shared tunnel can be quickly established.

[0468] In one embodiment, the first network node broadcasts a system message; the system message includes configuration information of a first resource; the first resource is shared by at least two terminals;

[0469] The first network node receives a first request sent by the terminal on a first resource.

[0470] Accordingly, the present application also provides a method for processing a multicast service, which is applied to a second network node and includes:

[0471] The receiving terminal sends third information when the receiving terminal is in an idle state or an inactive state; the third information is used to indicate at least one of the following information:

[0472] The terminal leaves a shared tunnel of at least one multicast service;

[0473] The terminal stops receiving at least one multicast service;

[0474] The terminal stops receiving at least one multicast service in the first cell;

[0475] The terminal leaves the first cell;

[0476] The terminal will enter or has entered the second cell;

[0477] The terminal stops receiving at least one multicast service at a first time point;

[0478] The terminal stops receiving at least one multicast service within a first time range;

[0479] The terminal enters or has entered the second cell at a second time point;

[0480] The terminal enters or has entered the second cell within a second time range; wherein,

[0481] When the terminal is in an idle state or an inactive state, the identifier of the terminal is retained in a first list; the first list contains at least one terminal identifier of a shared tunnel using at least one multicast service, or the first list contains at least one terminal identifier for establishing at least one multicast session, or the first list contains at least one terminal identifier for establishing a QoS flow of at least one multicast session, or the first list contains at least one terminal identifier for establishing at least one MRB.

[0482] In actual application, when the terminal enters an idle state (specifically, idle mode 1 (expressed as IDLE mode 1 in English)), the core network not only saves the TA information and registration information of the terminal, but also saves the relevant parameters of the QoS flow of the terminal and the N3 tunnel information. Only the Uu air interface resources are released, but the base station side maintains a list of terminals using the shared tunnel corresponding to the multicast TMGI information, and retains the UE ID in the list of terminals using the shared tunnel corresponding to the corresponding multicast TMGI information;

[0483] If the UE enters the INACTIVE state, the core network and the base station will continue to maintain the context of the terminal. The base station side can also maintain a list of terminals using the shared tunnel corresponding to the multicast TMGI information, and keep the UE ID in the list of terminals using the shared tunnel corresponding to the multicast TMGI information.

[0484] If the MBS session is released, that is, the multicast service session is released, the N3 tunnel information and the radio bearer resources corresponding to the MBS QoS flow will also be released.

[0485] In one embodiment, the second network node receives third information sent by the terminal through message 1, message A or message 3 of random access.

[0486] The method for processing multicast services provided in the embodiment of the present application is that when a terminal is in an idle state or an inactive state, it changes from a first cell to a second cell; the terminal sends a first request to a first network node where the second cell is located; the first request is used to request resource information for receiving at least one multicast service; and the resource information for receiving at least one multicast service sent by the first network node is received. In the scheme provided in the embodiment of the present application, when a terminal in an idle state or an inactive state changes from one cell to another cell, it needs to perform signaling interaction with another cell to obtain resources for the multicast service of interest to itself, thereby ensuring that the terminal can receive the multicast service of interest to itself in the changed cell.

[0487] It can be seen from the above description that in the above scheme, no matter what the circumstances, the terminal obtains the resource information of at least one multicast service from the network side, which can be understood as passively obtaining the resource information of at least one multicast service. In actual application, the terminal can also actively obtain the resource information of at least one multicast service, that is, the terminal actively detects whether the multicast session corresponding to the at least one multicast service requested in the second cell and / or the shared tunnel corresponding to the at least one multicast service requested has been established. If it has been established and the system message carries the resource information, the resource information is obtained from the system message. If it has been established and the system message does not carry the resource information or has not been established, the resource information is requested from the first network node where the second cell is located.

[0488] Based on this, the embodiment of the present application also provides a method for processing a multicast service, which is applied to a terminal, such as Figure 3 As shown, the method includes:

[0489] Step 301: When the terminal is in an idle state or an inactive state, the terminal changes from a first cell to a second cell;

[0490] Step 302: Detect whether a multicast session corresponding to at least one requested multicast service and / or a shared tunnel corresponding to at least one requested multicast service in the second cell has been established, and perform corresponding operations according to the detection result.

[0491] The performing of corresponding operations according to the detection result includes one of the following operations:

[0492] Sending a third request to the first network node where the second cell is located; the third request is used to request receiving resource information of at least one multicast service;

[0493] Resource information for receiving at least one multicast service is acquired from a system message.

[0494] More specifically, when it is detected that a multicast session corresponding to at least one multicast service requested in the second cell and / or a shared tunnel corresponding to at least one multicast service requested has been established, and the system message does not carry resource information of at least one multicast service, requesting resource information for receiving at least one multicast service from the first network node, that is, sending a third request;

[0495] When it is detected that the multicast session corresponding to the at least one requested multicast service and / or the shared tunnel corresponding to the at least one requested multicast service in the second cell is not established, initiating a request message for establishing the multicast session corresponding to the at least one requested multicast service and / or the shared tunnel corresponding to the at least one requested multicast service to the first network node, that is, sending a third request;

[0496] When it is detected that a multicast session corresponding to at least one multicast service requested in the second cell and / or a shared tunnel corresponding to at least one multicast service requested has been established, and the system message carries resource information of at least one multicast service, obtaining resource information of at least one multicast service from the system message; receiving at least one multicast service using the resource information for receiving at least one multicast service in the system message;

[0497] When it is detected that the multicast session corresponding to at least one multicast service requested in the second cell and / or the shared tunnel corresponding to at least one multicast service requested has been established, and the system message carries the group common part of the resource information of at least one multicast service, the group common part of the resource information for receiving the at least one multicast service is obtained from the system message, and then a request for the UE-specific part of the resource information for receiving the at least one multicast service is initiated to the first network node, that is, a third request is sent, and at this time the first network node sends the UE-specific part of the resource information to the terminal.

[0498] Specifically, the third request may carry at least one of the following information:

[0499] The TMGI corresponding to at least one multicast service requested to be received;

[0500] a multicast session identifier corresponding to at least one multicast service requested to be received;

[0501] a QoS flow identifier corresponding to at least one multicast service requested to be received;

[0502] An MRB identifier corresponding to at least one multicast service requested to be received;

[0503] A multicast IP address corresponding to at least one multicast service requested to be received;

[0504] The G-RNTI corresponding to at least one multicast service requested to be received;

[0505] identification information of the terminal;

[0506] First cell information;

[0507] The NAS configuration information of the multicast service received in the first cell and stored by the terminal.

[0508] here, Figure 3 The scheme shown is Figure 1 The difference of the scheme shown is that: the terminal actively detects whether the multicast session corresponding to at least one multicast service requested in the second cell and / or the shared tunnel corresponding to at least one multicast service requested have been established; if they have been established and the system message carries resource information, the resource information is obtained from the system message; if they have been established and the system message does not carry resource information or has not been established, the resource information is requested from the first network node where the second cell is located.

[0509] Of course, in the above solution, the terminal and the second network node also need to interact; the manner of interaction has been described in detail above and will not be repeated here.

[0510] It should be noted that: Figure 3 More specific operations of the terminal and the first network node in the illustrated solution have been described in detail above and will not be repeated here.

[0511] The method for processing multicast services provided in the embodiment of the present application is that when the terminal is in an idle state or an inactive state, it changes from a first cell to a second cell; the terminal detects whether a multicast session corresponding to at least one multicast service requested in the second cell and / or a shared tunnel corresponding to at least one multicast service requested has been established, and sends a third request to the first network node where the second cell is located according to the detection result; the third request is used to request resource information for receiving at least one multicast service; or obtain resource information for receiving at least one multicast service from a system message. The solution provided in the embodiment of the present application is that when a terminal in an idle state or an inactive state changes from one cell to another cell, it interacts with another cell through signaling or parses system messages to obtain resources for the multicast service of interest, thereby ensuring that the terminal can receive the multicast service of interest in the changed cell.

[0512] The terminal receives at least one multicast service in a connected state. When the at least one multicast service data stops being sent and continues for a period of time, the terminal enters an idle state or an inactive state. When the at least one multicast service has data again, how to page (also understood as notification) the terminal to start receiving the multicast service (i.e., starting or activating the multicast session) is also a problem that needs to be solved urgently; when the at least one multicast service data is being sent, how to page (also understood as notification) the terminal to stop receiving the multicast service (i.e., stopping or deactivating the multicast session) is also a problem that needs to be solved urgently.

[0513] Based on this, the embodiment of the present application also provides a method for processing a multicast service, which is applied to a third network node (specifically, a base station) and a fourth network node (specifically, a core network), such as Figure 4 As shown, the method includes:

[0514] Step 401: After the terminal enters an idle state or an inactive state, the fourth network node receives data of the at least one multicast service sent down, or does not receive data of the at least one multicast service for a period of time;

[0515] Step 402: The fourth network node generates a first paging message for at least one received multicast service;

[0516] Step 403: The fourth network node sends the first paging message to the third network node;

[0517] Step 404: After receiving the first paging message, the third network node uses the first paging message to generate a second paging message and sends the second paging message to the terminal; the second paging message is for at least one multicast service.

[0518] In step 401, a period of time can be understood as a first period of time. Here, the first period of time can be set as needed.

[0519] In the example of the present application, the paging message may also be referred to as a notification message, or as a group paging message (G-Paging).

[0520] In step 404, the third network node performs air interface transmission related processing on the first paging message to obtain a second paging message. Therefore, the second paging message may also be an air interface paging message. That is, all paging messages received by the terminal are air interface paging messages.

[0521] The second paging message includes at least one of the following:

[0522] an identifier of at least one multicast service;

[0523] an identifier of at least one multicast session;

[0524] At least one IP address corresponding to a multicast service;

[0525] A bitmap indicating the identifier of the multicast service configured in the network;

[0526] A bitmap indicating the identifier of the multicast session configured in the network;

[0527] MBS area information for paging;

[0528] The state of the terminal being paged for receiving multicast services, for example, connected state, idle state or deactivated state;

[0529] The state of the paged terminal after receiving the multicast service, for example, connected state, idle state or deactivated state;

[0530] Group-level temporary mobile subscriber identity (TMSI, Temporary Mobile Subscriber Identity);

[0531] a start time for sending data of the at least one multicast service or multicast session;

[0532] The sending stop time of the data of the at least one multicast service or multicast session;

[0533] Stop receiving indication, if this indication appears, it means stopping or deactivating the reception of the corresponding multicast service;

[0534] A start receiving indication, if the indication appears, it means starting or activating the reception of the corresponding multicast service;

[0535] a stop or start receiving indication, if the indication is set to 1 or true, it indicates starting or activating the reception of the corresponding multicast service, if the indication is 0 or false, it indicates stopping or deactivating the reception of the corresponding multicast service; or if the indication is set to 1 or true, it indicates stopping or deactivating the reception of the corresponding multicast service, if the indication is set to 0 or false, it indicates starting or activating the reception of the corresponding multicast service;

[0536] Part or all of the QoS information corresponding to the service that triggers the initiation of the paging or notification message, such as at least one of the delay requirement, reliability and bandwidth requirement;

[0537] Information on sending resources corresponding to the service that triggers the initiation of paging or notification messages;

[0538] Data packets that trigger services such as paging or notification messages;

[0539] Indicates whether there are subsequent data packets.

[0540] The terminal may use the information about the state of the paged terminal after receiving the multicast service to decide whether to save the RRC connection or initiate the RRC connection after receiving the multicast service.

[0541] The partial or complete QoS information corresponding to the service that triggers the initiation of the paging or notification message is used by the terminal to determine the priority or preemption level of reception when a conflict occurs between the reception of the notification message and other signaling or data transmission and reception.

[0542] The MBS area information may be understood with reference to the above description.

[0543] The information of the sending resources corresponding to the service that triggers the initiation of the paging or notification message is used by the terminal to quickly obtain the information of the sending resources corresponding to the service that triggers the initiation of the paging or notification message, thereby reducing the delay of data reception.

[0544] The function of the data packet of the service that triggers the initiation of the paging or notification message is to enable the terminal to receive the data packet of the service that triggers the initiation of the notification message as soon as possible, thereby reducing the signaling overhead of the RRC link establishment and reducing the delay of data reception.

[0545] In actual application, in step 402, after the terminal enters an idle state or an inactive state, the fourth network node receives the data of the at least one multicast service and generates a second paging message corresponding to the first paging message, which can be called a paging message for paging to the terminal to start receiving the multicast service, and can also be called a paging message for activating or starting the MBS data; the second paging message corresponding to the first paging message generated when the data of the at least one multicast service is not received for a period of time can be called a paging message for paging to the terminal to start stopping receiving the at least one multicast service, and can also be called a paging message for deactivating or stopping the MBS data. These two paging messages can be two independent messages or one message.

[0546] The fourth network node sending the first paging message to the third network node includes:

[0547] The fourth network node determines the TA and / or RANA of the paged terminal receiving the at least one multicast service, and sends the first paging message to the corresponding third network node;

[0548] and / or,

[0549] The fourth network node determines the MBS area of ​​the paged terminal receiving the multicast service, and sends the first paging message to the corresponding third network node.

[0550] There is at least one third network node that sends the first paging message.

[0551] In one embodiment, the second paging message is scrambled using the G-RNTI corresponding to the at least one multicast service.

[0552] Among them, when the terminal enters the idle state (specifically, it can be idle state mode 1), the core network not only saves the terminal's TA information and registration information, but also saves the relevant parameters of the terminal's QoS flow and N3 tunnel information. Only the Uu air interface resources are released, but the base station side will maintain a list of terminals using the shared tunnel corresponding to the multicast TMGI information, and retain the UE ID in the list of terminals using the shared tunnel corresponding to the corresponding multicast TMGI information.

[0553] Based on this, in one embodiment, when the terminal is in an idle state or an inactive state, the identifier of the terminal is retained in a second list; the second list contains at least one terminal identifier of a shared tunnel using a first multicast service, or the second list contains at least one terminal identifier for establishing at least one multicast session, or the second list contains at least one terminal identifier for establishing a QoS flow of at least one multicast session, or the second list contains at least one terminal identifier for establishing at least one MRB.

[0554] If the terminal enters the INACTIVE state, the core network and the base station will continue to maintain the context of the terminal.

[0555] The third network node sends down the period value of G-Paging so that the terminal can determine the PO (which can be called G-PO) and PF (which can be called G-PF) of G-Paging. Specifically, the third network node can send down the period value of G-Paging in a broadcast message.

[0556] Based on this, in one embodiment, the method may further include:

[0557] broadcast message; the message carries a period of the second paging message.

[0558] Here, the third network node further determines G-PF and G-PO by using an identifier related to the multicast service, so as to send the second paging message; wherein the identifier related to the multicast service includes at least one of the following:

[0559] TMGI corresponding to the multicast service;

[0560] The multicast session identifier corresponding to the multicast service;

[0561] Multicast QoS flow identifier corresponding to the multicast service;

[0562] MRB identifier corresponding to the multicast service;

[0563] G-RNTI corresponding to the multicast service;

[0564] IP address corresponding to the multicast service;

[0565] TMSI corresponding to the multicast service.

[0566] In actual application, in order to avoid too much concentration of terminals in a paging message time slot, the third network node can further determine the G-PF and G-PO using the UE granularity identifier or the offset of the network configuration.

[0567] In actual application, if the network side detects that the paging message fails to be sent (ie, no response from the terminal is received), it falls back to the traditional UE-granularity paging message or the UE-granularity Radio Access Network (RAN) paging message.

[0568] Here, if the network side detects that some terminals fail to receive the paging message, it may send a traditional UE-granularity paging message or a UE-granularity RAN paging message to the receiving terminals.

[0569] Accordingly, an embodiment of the present application further provides a method for processing a multicast service, which is applied to a terminal and includes:

[0570] A second paging message is monitored and received on the PO and / or the PF; the second paging message is for the first multicast service.

[0571] In one embodiment, after the terminal receives the second paging message, the second paging message may be sent or broadcast to other terminals in an MBS group; wherein the MBS group may be negotiated between terminals through communication means such as sidelink, Bluetooth, or WiFi. The specific confirmation strategy may be determined based on factors such as information quality, terminal location and / or received service characteristics, and the embodiment of the present application does not limit this. The determination of the MBS group may also be configured by the network and notified to a specific terminal or all terminals in the MBS group.

[0572] If a terminal detects or receives at least two of the following messages at the same time period or at the same time point:

[0573] Paging messages for system information updates;

[0574] Paging message for mobile terminated data;

[0575] Paging message for activation or opening of MBS data;

[0576] A paging message for deactivation or stop of MBS data;

[0577] The terminal may receive the message according to any of the following rules, that is, receive the paging message according to any of the following priority strategies (also referred to as receiving priority order):

[0578] The paging message used for system message update has the highest priority, followed by the paging message for mobile terminated data, then the paging message for activation or opening of MBS data, and finally the paging message for deactivation or stopping of MBS data; that is, the order of receiving priority from high to low is: paging message for system message update, paging message for mobile terminated data, paging message for activation or opening of MBS data, and paging message for deactivation or stopping of MBS data.

[0579] Then the paging message for updating at least one type of system message among MIB, SIB1, ETWS and PWS has the highest priority, followed by the paging message for mobile terminated data, then the paging message for activating or starting MBS data, then the paging message for updating other system messages other than MIB, SIB1, ETWS and PWS, and finally the paging message or notification message for deactivating or stopping MBS data; that is, the order of receiving priority from high to low is: paging message for updating the first type of system message, paging message for mobile terminated data, paging message for activating or starting MBS data, paging message for updating non-first type of system message, paging message for deactivating or stopping MBS data; the first type of system message includes at least one of the following: MIB, SIB1, ETWS and PWS;

[0580] The paging message for updating at least one of the system messages of MIB, SIB1, ETWS, and PWS has the highest priority, followed by the paging message for mobile terminated data and the paging message or notification message for activating or starting MBS data. The priority order is determined according to the priority of the services corresponding to the two paging messages, followed by the paging message for updating other system messages other than MIB, SIB1, ETWS, and PWS, and finally the paging message or notification message for deactivating or stopping MBS data. The order of receiving priority from high to low is: paging message for updating the first type of system messages, paging message for mobile terminated data and paging message for activating or starting MBS data, paging message for updating non-first type of system messages, and paging message for deactivating or stopping MBS data.

[0581] The terminal receives a broadcast message; the message carries a period of the second paging message;

[0582] The terminal determines the PO and PF using the period.

[0583] Similar to the third network node, the terminal also uses the identifier related to the multicast service to determine the G-PF and the G-PO.

[0584] Here, in actual application, in order to avoid too much concentration of terminals in one paging message time slot, the terminal can further determine the G-PF and G-PO by using the identifier of UE granularity or the offset configured by the network.

[0585] The embodiment of the present application provides a method for processing multicast services, wherein a third network node receives a first paging message for at least one multicast service sent by a fourth network node; the first paging message is used to generate a second paging message, and the second paging message is sent; the terminal detects the second paging message for the at least one multicast service in PO and / or PF, thereby implementing paging for the multicast service, specifically implementing paging for the multicast service after the terminal enters an idle state or an inactive state, and also implementing deactivation or stop paging for the multicast service.

[0586] The present application is further described in detail below in conjunction with application examples.

[0587] In this application embodiment, several cells are set, which support the UE to receive MBS services in these cells in idle or inactive state, and the network does not need to be informed when changing from one cell to another, that is, these cells form an MBS area. Optionally, the network configures a sounding reference (SRS) with MBS group or MBS service as the granularity for the UE.

[0588] The UE joins a multicast service through NAS information, hereinafter referred to as multicast service 1. The reliability requirement of multicast service 1 is not too high. If there is no other dedicated service at this time, the UE enters an idle state or an inactive state and receives data of multicast service 1.

[0589] Among them, although the UE enters the IDLE mode1 state, the core network not only saves the UE's TA information and registration information, but also saves the relevant parameters of the UE's QoS flow and N3 tunnel information. Only the Uu air interface resources are released, but the base station side will maintain a list of UEs using the shared tunnel corresponding to the TMGI information of multicast service 1, and retain the UE ID in the list of UEs using the shared tunnel corresponding to the TMGI information of multicast service 1.

[0590] If the UE enters the INACTIVE state, the core network and the base station will continue to maintain the context of the UE.

[0591] like Figure 5 As shown in FIG. 1 , the UE reselects from cell 1 to cell 2 due to reasons such as signal quality, and there is signaling interaction between the UE and cell 2, including:

[0592] Continue to be in the idle state or inactive state, send a tunnel establishment request message (which may carry TMGI information) to the base station 2 where the cell 2 is located, or temporarily enter the connected state and send a tunnel establishment request message to the cell 2;

[0593] After receiving the request, base station area 2 confirms whether there is a group tunnel corresponding to multicast service 1. If so, the corresponding sending resource information is notified to the UE; if not, a tunnel establishment request is initiated to the core network. Among them, base station 2 determines whether there are other UEs for multicast service 1. If so, it means that there is a group tunnel corresponding to multicast service 1, and pushes relevant information to the UE, that is, sends resource information, that is, receives resource information of multicast service 1. If there are no other UEs for multicast service 1, it means that the group tunnel corresponding to multicast service 1 does not exist, and sends a tunnel establishment request message (which can carry TMGI information) to the core network node to establish the group tunnel for multicast service 1, and returns relevant information to the UE after establishment.

[0594] When the UE reselects from cell 1 to cell 2 due to reasons such as signal quality, there is also signaling interaction between the UE and cell 1, including:

[0595] Send a tunnel leave request (which can also be understood as tunnel leave information, carrying TMGI information) to cell 1. This information can be sent in message 1, message A or message 3 of random access without the UE entering the connected state, or can be sent in message 1, message A or message 3 of random access by temporarily entering the connected state;

[0596] When base station 1 where cell 1 is located receives the information, if there are other UEs in base station 1 receiving multicast service 1, the information of the UE is deleted from the list of multicast UEs of multicast service 1, and the shared tunnel remains unchanged; if there are no other UEs in base station 1 receiving the multicast service, the list of multicast UEs of multicast service 1 is cleared, and the shared tunnel information is deleted; at the same time, the shared tunnel deletion information is sent to the core network.

[0597] Base station 1 and base station 2 can also perform a tunnel transfer process.

[0598] In order to implement the method of the embodiment of the present application, the embodiment of the present application also provides a multicast service processing device, which is set on the terminal, such as Figure 6 As shown, the device comprises:

[0599] A changing unit 601, configured to change from a first cell to a second cell when the terminal is in an idle state or an inactive state;

[0600] A first sending unit 602 is configured to send a first request to a first network node where the second cell is located; the first request is used to request to receive resource information of at least one multicast service;

[0601] The first receiving unit 603 is configured to receive resource information for receiving at least one multicast service sent by the first network node.

[0602] In one embodiment, the first sending unit 602 is further configured to send a second request to the first network node when one of the following conditions is met, wherein the second request is used to request to establish a multicast session corresponding to at least one multicast service requested to be received:

[0603] The first receiving unit 603 receives reply information sent by the first network node indicating that at least one requested multicast service does not exist;

[0604] The first receiving unit 603 receives first information sent by the first network node, where the first information instructs the terminal to initiate a request to establish a multicast session corresponding to at least one requested multicast service to the network side;

[0605] The first receiving unit 603 receives second information sent by the first network node, where the second information instructs the terminal to send non-access stratum NAS configuration information of a multicast service received in the first cell and stored by the terminal.

[0606] In one embodiment, the first sending unit 602 is used to send a multicast session establishment request message of at least one requested multicast service to the first network node.

[0607] In one embodiment, the first sending unit 602 is used to detect that a multicast session corresponding to at least one multicast service requested in the second cell and / or a shared tunnel corresponding to at least one multicast service requested is not established, and send a first request to the first network node where the second cell is located.

[0608] In one embodiment, the first sending unit 602 is used to:

[0609] Detecting from the system message of the second cell whether there is control information of at least one multicast service requested to be received;

[0610] When control information of the at least one requested multicast service exists, determining that a multicast session corresponding to the at least one requested multicast service and / or a shared tunnel corresponding to the at least one requested multicast service in the second cell has been established;

[0611] When control information of the at least one requested multicast service does not exist, it is determined that a multicast session corresponding to the at least one requested multicast service and / or a shared tunnel corresponding to the at least one requested multicast service in the second cell are not established.

[0612] In one embodiment, the first receiving unit 603 is configured to:

[0613] Resource information for receiving at least one multicast service sent by the first network node is received through RRC signaling and / or NAS information.

[0614] In one embodiment, the terminal enters a connected state from an idle state or an inactive state, and the first sending unit 602 sends a first request to the second cell;

[0615] After receiving the resource information for receiving at least one multicast service sent by the first network node, the idle state or the inactive state is entered again.

[0616] In one embodiment, the first receiving unit 603 is further configured to receive a system message;

[0617] The first sending unit 602 is configured to obtain configuration information of a first resource from the system message; the first resource is shared by at least two terminals; and send a first request to the first network node on the first resource.

[0618] In one embodiment, the changing unit 601 is used to:

[0619] receiving fourth information when in the first cell; the fourth information represents a multicast service being sent by at least one neighboring cell;

[0620] Using the fourth information, perform at least one of the following operations to change from the first cell to the second cell:

[0621] Cell selection;

[0622] Cell reselection;

[0623] Community reconstruction.

[0624] In one embodiment, the first sending unit 602 is further configured to send third information to the second network node where the first cell is located when the terminal is in an idle state or an inactive state; the third information is used to indicate at least one of the following information:

[0625] The terminal leaves the shared tunnel of the requested at least one multicast service;

[0626] The terminal stops receiving the at least one requested multicast service;

[0627] The terminal stops receiving the requested at least one multicast service in the first cell;

[0628] The terminal leaves the first cell;

[0629] The terminal will enter or has entered the second cell;

[0630] The terminal stops receiving the at least one requested multicast service at a first time point;

[0631] The terminal stops receiving the at least one requested multicast service within a first time range;

[0632] The terminal enters or has entered the second cell at a second time point;

[0633] The terminal enters or has entered the second cell within a second time range.

[0634] In one embodiment, the first sending unit 602 is configured to send third information to the second network node via message 1, message A or message 3 of random access.

[0635] In one embodiment, the first sending unit 602 is configured to:

[0636] When the second cell and the first cell do not belong to the same MBS area, the first request is sent to the second network node.

[0637] In one embodiment, the first receiving unit 603 is further configured to directly receive the multicast service by using the resource information of the multicast service receiving resource obtained in the first cell when the second cell and the first cell belong to the same MBS area.

[0638] In actual application, the changing unit 601 and the first sending unit 602 can be implemented by a processor in a multicast service processing device in combination with a communication interface; the first receiving unit 603 can be implemented by a communication interface in the multicast service processing device.

[0639] In order to implement the method on the first network node side of the embodiment of the present application, the embodiment of the present application also provides a multicast service processing device, which is arranged on the first network node, such as Figure 7 As shown, the device comprises:

[0640] The second receiving unit 701 is used to receive a first request sent by a terminal in an idle state or an inactive state; the first request is used to request to receive resource information of at least one multicast service; the terminal in the idle state or the inactive state can receive the requested at least one multicast service in the second cell;

[0641] The second sending unit 702 is configured to send resource information for receiving at least one multicast service to the terminal.

[0642] In one embodiment, the second sending unit 702 is used to:

[0643] When a multicast session and / or a shared tunnel corresponding to at least one multicast service requested in the second cell has been established, resource information for receiving at least one multicast service is sent to the terminal.

[0644] In one embodiment, the second sending unit 702 is further configured to:

[0645] When a multicast session and / or a shared tunnel corresponding to at least one multicast service requested in the second cell is not established, sending first information to the terminal, wherein the first information instructs the terminal to initiate a request to establish a multicast session of the requested multicast service to the network side;

[0646] or,

[0647] When a multicast session and / or a shared tunnel corresponding to at least one multicast service requested in the second cell is not established, sending second information to the terminal, wherein the second information instructs the terminal to send NAS configuration information of the multicast service received in the first cell and stored by the terminal;

[0648] or,

[0649] When a multicast session and / or a shared tunnel corresponding to at least one multicast service requested in the second cell is not established, initiating a process of acquiring relevant configuration information of the multicast service received by the terminal in the first cell from a second network node where the first cell is located;

[0650] or,

[0651] When the multicast session and / or shared tunnel corresponding to the at least one multicast service requested in the second cell is not established, reply information indicating that the at least one multicast service requested does not exist is sent to the terminal.

[0652] In one embodiment, the second receiving unit 701 is further configured to receive a second request sent by the terminal, where the second request is used to request to establish a multicast session corresponding to at least one multicast service requested to be received.

[0653] In one embodiment, the second receiving unit 701 is configured to receive a multicast session establishment request message for at least one requested multicast service sent by the terminal.

[0654] In one embodiment, the second sending unit 702 is further used to broadcast a system message; the system message includes configuration information of the first resource; the first resource is shared by at least two terminals;

[0655] The second receiving unit 701 is configured to receive a first request sent by the terminal on a first resource.

[0656] In actual application, the second sending unit 702 can be implemented by a processor in a multicast service processing device in combination with a communication interface; the second receiving unit 701 can be implemented by a communication interface in the multicast service processing device.

[0657] In order to implement the method on the second network node side of the embodiment of the present application, the embodiment of the present application also provides a multicast service processing device, which is arranged on the second network node, such as Figure 8 As shown, the device comprises:

[0658] The third receiving unit 801 is configured to receive third information sent when the terminal is in an idle state or an inactive state; the third information is used to indicate at least one of the following information:

[0659] The terminal leaves a shared tunnel of at least one multicast service;

[0660] The terminal stops receiving at least one multicast service;

[0661] The terminal stops receiving at least one multicast service in the first cell;

[0662] The terminal leaves the first cell;

[0663] The terminal will enter or has entered the second cell;

[0664] The terminal stops receiving at least one multicast service at a first time point;

[0665] The terminal stops receiving at least one multicast service within a first time range;

[0666] The terminal enters or has entered the second cell at a second time point;

[0667] The terminal enters or has entered the second cell within a second time range; wherein,

[0668] When the terminal is in an idle state or an inactive state, the identifier of the terminal is retained in a first list; the first list contains at least one terminal identifier of a shared tunnel using at least one multicast service, or the first list contains at least one terminal identifier for establishing at least one multicast session, or the first list contains at least one terminal identifier for establishing a QoS flow of at least one multicast session, or the first list contains at least one terminal identifier for establishing at least one MRB.

[0669] In one embodiment, the third receiving unit 801 is used to receive third information sent by the terminal through message 1, message A or message 3 of random access.

[0670] In one embodiment, if Figure 8 As shown, the device may also include:

[0671] The fourth sending unit 802 is configured to release the shared tunnel and send shared tunnel deletion information to the core network when a multicast service has no terminals.

[0672] In actual application, the third receiving unit 801 can be implemented by a communication interface in the multicast service processing device, and the fourth sending unit 802 can be implemented by a processor in the multicast service processing device in combination with the communication interface.

[0673] In order to implement the method on the third network node side of the embodiment of the present application, the embodiment of the present application also provides a multicast service processing device, which is set on the third network node, such as Fig. 9 As shown, the device comprises:

[0674] The fourth receiving unit 901 is configured to receive a first paging message for at least one multicast service sent by a fourth network node;

[0675] A generating unit 902 is configured to generate a second paging message using the first paging message; the second paging message is for at least one multicast service;

[0676] The third sending unit 903 is configured to send the second paging message.

[0677] In one embodiment, the device may further include:

[0678] The determining unit is used to determine the PO and the PF by using the identifier related to the multicast service.

[0679] The third sending unit 903 is further used to broadcast a message; the message carries the period of the second paging message.

[0680] In actual application, the fourth receiving unit 901 and the third sending unit 903 may be implemented by a communication interface in the multicast service processing device; the generating unit 902 and the determining unit may be implemented by a processor in the multicast service processing device.

[0681] In order to implement another method on the terminal side of the embodiment of the present application, the embodiment of the present application also provides a multicast service processing device, which is set on the terminal, such as Fig.10 As shown, the device comprises:

[0682] The paging unit 1001 is used to monitor and receive a second paging message on the PO and / or PF; the second paging message is for at least one multicast service.

[0683] In one embodiment, if Fig.10 As shown, the device comprises:

[0684] The fifth receiving unit 1002 is configured to receive a broadcast message; the message carries a period of the second paging message;

[0685] The paging unit 1001 is further configured to determine the PO and PF using the period.

[0686] In one embodiment, the paging unit 1001 is further configured to simultaneously detect or receive at least two of the following messages in the same time period or at the same time point:

[0687] Paging messages for system information updates;

[0688] Paging message for mobile terminated data;

[0689] Paging message for activation or opening of MBS data;

[0690] A paging message for deactivation or stop of MBS data;

[0691] Reception of paging messages is performed in one of the following reception priority orders:

[0692] The order of receiving priority from high to low is: paging message for system message update, paging message for mobile terminated data, paging message for activation or opening of MBS data, paging message for deactivation or stopping of MBS data;

[0693] The order of receiving priority from high to low is: paging message for updating the first type of system message, paging message for mobile terminated data, paging message for activating or starting MBS data, paging message for updating non-first type of system message, paging message for deactivating or stopping MBS data; the first type of system message includes at least one of the following: MIB, SIB1, ETWS, PWS;

[0694] The order of receiving priority from high to low is: paging message for updating first-category system messages, paging message for mobile terminated data and paging message for activating or starting MBS data, paging message for updating non-first-category system messages, and paging message for deactivating or stopping MBS data; the first-category system message includes at least one of the following: MIB, SIB1, ETWS, PWS; the priority of the paging message for mobile terminated data and the paging message for activating or starting MBS data is determined according to the service priority of one.

[0695] In one embodiment, the paging unit 1001 is further configured to determine the PO and PF using an identifier associated with the multicast service.

[0696] In actual application, the paging unit 1001 can be implemented by a processor in a multicast service processing device in combination with a communication interface; the fifth receiving unit 1002 can be implemented by a communication interface in the multicast service processing device.

[0697] It should be noted that: the multicast service processing device provided in the above embodiment only uses the division of the above program modules as an example to illustrate when processing the multicast service. In actual applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device is divided into different program modules to complete all or part of the processing described above. In addition, the multicast service processing device provided in the above embodiment and the multicast service processing method embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.

[0698] Based on the hardware implementation of the above program modules, and in order to implement the method on the terminal side of the embodiment of the present application, the embodiment of the present application also provides a terminal, such as Fig.11 As shown, the terminal 1100 includes:

[0699] The first communication interface 1101 is capable of exchanging information with a network node;

[0700] A first processor 1102, connected to the first communication interface 1101, to implement information interaction with a network node, and configured to execute the method provided by one or more technical solutions on the terminal side when running a computer program;

[0701] A first memory 1103 , on which the computer program is stored.

[0702] Specifically, in implementing Figure 1 In the process of the method shown, the first processor 1102 is used to change from the first cell to the second cell when the terminal is in an idle state or an inactive state; the first communication interface 1101 is used to send a first request to a first network node where the second cell is located; the first request is used to request to receive resource information for at least one multicast service; and receive resource information for receiving at least one multicast service sent by the first network node.

[0703] In one embodiment, the first communication interface 1101 is further configured to send a second request to the first network node when one of the following conditions is met, wherein the second request is configured to request establishment of a multicast session corresponding to at least one multicast service requested to be received:

[0704] receiving a reply message sent by the first network node indicating that at least one requested multicast service does not exist;

[0705] receiving first information sent by the first network node, wherein the first information instructs the terminal to initiate a request to establish a multicast session corresponding to at least one requested multicast service to the network side;

[0706] Second information sent by the first network node is received, where the second information instructs the terminal to send non-access layer NAS configuration information of the multicast service received in the first cell and stored by the terminal.

[0707] In one embodiment, the first communication interface 1101 is used to send a multicast session establishment request message of at least one requested multicast service to the first network node.

[0708] In one embodiment, the first communication interface 1101 is used for the first processor 1102 to detect that a multicast session corresponding to at least one multicast service requested in the second cell and / or a shared tunnel corresponding to at least one multicast service requested is not established, and to send a first request to the first network node where the second cell is located.

[0709] In one embodiment, the first processor 1102 is configured to:

[0710] Detecting from the system message of the second cell whether there is control information of at least one multicast service requested to be received;

[0711] When control information of the at least one requested multicast service exists, determining that a multicast session corresponding to the at least one requested multicast service and / or a shared tunnel corresponding to the at least one requested multicast service in the second cell has been established;

[0712] When control information of the at least one requested multicast service does not exist, it is determined that a multicast session corresponding to the at least one requested multicast service and / or a shared tunnel corresponding to the at least one requested multicast service in the second cell are not established.

[0713] In one embodiment, the first communication interface 1101 is used to:

[0714] Resource information for receiving at least one multicast service sent by the first network node is received through RRC signaling and / or NAS information.

[0715] In one embodiment, the terminal enters a connected state from an idle state or an inactive state, and the first communication interface 1101 sends a first request to the second cell;

[0716] After receiving the resource information for receiving at least one multicast service sent by the first network node, the idle state or the inactive state is entered again.

[0717] In one embodiment, the first communication interface 1101 is further used to receive system messages;

[0718] The first processor 1102 is used to obtain configuration information of a first resource from the system message; the first resource is shared by at least two terminals; and the first communication interface 1101 sends a first request to the first network node on the first resource.

[0719] In one embodiment, the first processor 1102 is configured to:

[0720] When in the first cell, receiving fourth information through the first communication interface 1101; the fourth information represents a multicast service being sent by at least one neighboring cell;

[0721] Using the fourth information, perform at least one of the following operations to change from the first cell to the second cell:

[0722] Cell selection;

[0723] Cell reselection;

[0724] Community reconstruction.

[0725] In one embodiment, the first communication interface 1101 is further used to send third information to the second network node where the first cell is located when the terminal is in an idle state or an inactive state; the third information is used to indicate at least one of the following information:

[0726] The terminal leaves the shared tunnel of the requested at least one multicast service;

[0727] The terminal stops receiving the at least one requested multicast service;

[0728] The terminal stops receiving the requested at least one multicast service in the first cell;

[0729] The terminal leaves the first cell;

[0730] The terminal will enter or has entered the second cell;

[0731] The terminal stops receiving the at least one requested multicast service at a first time point;

[0732] The terminal stops receiving the at least one requested multicast service within a first time range;

[0733] The terminal enters or has entered the second cell at a second time point;

[0734] The terminal enters or has entered the second cell within a second time range.

[0735] In one embodiment, the first communication interface 1101 is used to send third information to the second network node through message 1, message A or message 3 of random access.

[0736] In one embodiment, the first communication interface 1101 is used to:

[0737] When the second cell and the first cell do not belong to the same MBS area, the first request is sent to the second network node.

[0738] In one embodiment, when the second cell and the first cell belong to the same MBS area, the first communication interface 1101 directly uses the resource information of the multicast service receiving resources obtained in the first cell to receive the multicast service.

[0739] In realization Figure 3 In the method described, the first processor 1102 is used to change from the first cell to the second cell when the terminal is in an idle state or an inactive state; and detect whether a multicast session corresponding to at least one multicast service requested in the second cell and / or a shared tunnel corresponding to at least one multicast service requested have been established, and perform corresponding operations based on the detection results.

[0740] The performing of corresponding operations according to the detection result includes one of the following operations:

[0741] Sending a third request to the first network node where the second cell is located through the first communication interface 1101; the third request is used to request to receive resource information of at least one multicast service;

[0742] Resource information for receiving at least one multicast service is acquired from a system message. Figure 3 Other functions of the first processor 1102 and the first communication interface 1101 in the method shown can be referred to Figure 1 The functional understanding of the method shown will not be repeated here.

[0743] In the process of implementing another method, the first processor 1102 is used to monitor and receive a second paging message on the PO and / or PF through the first communication 1001 interface; the second paging message is for at least one multicast service.

[0744] In one embodiment, the first communication 1001 is used to receive a broadcast message; the message carries a period of the second paging message;

[0745] The first processor 1102 is further configured to determine the PO and PF using the cycle.

[0746] In one embodiment, the first processor 1102 is further configured to simultaneously detect or receive at least two of the following messages in the same time period or at the same time point:

[0747] Paging messages for system information updates;

[0748] Use mobile terminated data paging messages;

[0749] Paging message for activation or opening of MBS data;

[0750] A paging message for deactivation or stop of MBS data;

[0751] Reception of paging messages is performed in one of the following reception priority orders:

[0752] The order of receiving priority from high to low is: paging message for system message update, paging message for mobile terminated data, paging message for activation or opening of MBS data, paging message for deactivation or stopping of MBS data;

[0753] The order of receiving priority from high to low is: paging message for updating the first type of system message, paging message for mobile terminated data, paging message for activating or starting MBS data, paging message for updating non-first type of system message, paging message for deactivating or stopping MBS data; the first type of system message includes at least one of the following: MIB, SIB1, ETWS, PWS;

[0754] The order of receiving priority from high to low is: paging message for updating first-category system messages, paging message for mobile terminated data and paging message for activating or starting MBS data, paging message for updating non-first-category system messages, and paging message for deactivating or stopping MBS data; the first-category system message includes at least one of the following: MIB, SIB1, ETWS, PWS; the priority of the paging message for mobile terminated data and the paging message for activating or starting MBS data is determined according to the service priority of one.

[0755] In one embodiment, the first processor 1102 is further configured to determine the PO and the PF using an identifier associated with the multicast service.

[0756] It should be noted that the specific processing process of the first processor 1102 and the first communication interface 1101 can be understood by referring to the above method.

[0757] Of course, in actual application, the various components in the terminal 1100 are coupled together through the bus system 1104. It can be understood that the bus system 1104 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 1104 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Fig.11 Various buses are labeled as bus system 1004 .

[0758] The first memory 1103 in the embodiment of the present application is used to store various types of data to support the operation of the terminal 1100. Examples of such data include: any computer program used to operate on the terminal 1100.

[0759] The method disclosed in the above embodiment of the present application can be applied to the first processor 1102, or implemented by the first processor 1102. The first processor 1102 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by an integrated logic circuit of the hardware in the first processor 1102 or an instruction in the form of software. The above-mentioned first processor 1102 may be a general-purpose processor, a digital signal processor (DSP, Digital Signal Processor), or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The first processor 1102 can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiment of the present application, it can be directly embodied as a hardware decoding processor to execute, or it can be executed by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium, which is located in the first memory 1103, and the first processor 1102 reads the information in the first memory 1103, and completes the steps of the above method in combination with its hardware.

[0760] In an exemplary embodiment, terminal 1100 may be implemented by one or more application specific integrated circuits (ASIC), DSP, programmable logic device (PLD), complex programmable logic device (CPLD), field programmable gate array (FPGA), general processor, controller, microcontroller (MCU), microprocessor, or other electronic components to execute the aforementioned method.

[0761] Based on the hardware implementation of the above program module, and in order to implement the method on the first network node side of the embodiment of the present application, the embodiment of the present application also provides a first network node, such as Fig.12 As shown, the first network node 1200 includes:

[0762] The second communication interface 1201 is capable of exchanging information with the terminal and the second network node;

[0763] The second processor 1202 is connected to the second communication interface 1201 to implement information interaction with the terminal and the second network node, and is used to execute the method provided by one or more technical solutions on the first network node side when running the computer program;

[0764] A second memory 1203 , on which the computer program is stored.

[0765] Specifically, the second communication interface 1201 is used to receive a first request sent when the terminal is in an idle state or an inactive state; the first request is used to request resource information for receiving at least one multicast service; the terminal in an idle state or an inactive state can receive at least one requested multicast service in the second cell; and resource information for receiving at least one multicast service is sent to the terminal.

[0766] In one embodiment, the second communication interface 1201 is used to:

[0767] When the second processor 1202 determines that a multicast session and / or a shared tunnel corresponding to at least one multicast service requested in the second cell has been established, resource information for receiving at least one multicast service is sent to the terminal.

[0768] In one embodiment, the second communication interface 1201 is further used for:

[0769] When the second processor 1202 determines that a multicast session and / or a shared tunnel corresponding to at least one multicast service requested in the second cell is not established, sending first information to the terminal, where the first information instructs the terminal to initiate a request to establish a multicast session of the requested multicast service to the network side;

[0770] or,

[0771] When the second processor 1202 determines that a multicast session and / or a shared tunnel corresponding to at least one multicast service requested in the second cell is not established, sending second information to the terminal, where the second information instructs the terminal to send NAS configuration information of the multicast service received in the first cell saved by the terminal;

[0772] or,

[0773] When the second processor 1202 determines that a multicast session and / or a shared tunnel corresponding to at least one multicast service requested in the second cell is not established, the second processor 1202 initiates a process of acquiring relevant configuration information of the multicast service received by the terminal in the first cell from the second network node where the first cell is located;

[0774] or,

[0775] Sending reply information to the terminal indicating that at least one requested multicast service does not exist.

[0776] In one embodiment, the second communication interface 1201 is further used to receive a second request sent by the terminal, where the second request is used to request to establish a multicast session corresponding to at least one multicast service requested to be received.

[0777] In one embodiment, the second communication interface 1201 is used to receive a multicast session establishment request message of at least one requested multicast service sent by the terminal.

[0778] In one embodiment, the second communication interface 1201 is further used to broadcast a system message; the system message includes configuration information of the first resource; the first resource is shared by at least two terminals;

[0779] The second communication interface 1201 is configured to receive a first request sent by the terminal on a first resource.

[0780] It should be noted that the specific processing process of the second communication interface 1201 and the second processor 1202 can be understood by referring to the above method.

[0781] Of course, in actual application, the various components in the first network node 1200 are coupled together through the bus system 1204. It can be understood that the bus system 1204 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 1204 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Fig.12 Various buses are labeled as bus system 1204.

[0782] The second memory 1203 in the embodiment of the present application is used to store various types of data to support the operation of the first network node 1200. Examples of such data include: any computer program used to operate on the first network node 1200.

[0783] The method disclosed in the above embodiment of the present application can be applied to the second processor 1202, or implemented by the second processor 1202. The second processor 1202 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the hardware integrated logic circuit or software instructions in the second processor 1202. The above-mentioned second processor 1202 may be a general-purpose processor, DSP, or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The second processor 1202 can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiment of the present application, it can be directly embodied as a hardware decoding processor to execute, or it can be executed by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium, which is located in the second memory 1203, and the second processor 1202 reads the information in the second memory 1203 and completes the steps of the above method in combination with its hardware.

[0784] In an exemplary embodiment, the first network node 1200 may be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general purpose processors, controllers, MCUs, Microprocessors, or other electronic components to perform the aforementioned methods.

[0785] Based on the hardware implementation of the above program module, and in order to implement the method of the second network node side of the embodiment of the present application, the embodiment of the present application also provides a second network node, such as Fig.13 As shown, the second network node 1300 includes:

[0786] The third communication interface 1301 is capable of exchanging information with the terminal and the first network node;

[0787] The third processor 1302 is connected to the third communication interface 1301 to implement information interaction with the terminal and the first network node, and is used to execute the method provided by one or more technical solutions on the second network node side when running the computer program;

[0788] A third memory 1303 , on which the computer program is stored.

[0789] Specifically, the third communication interface 1301 is used to receive third information sent when the terminal is in an idle state or an inactive state; the third information is used to indicate at least one of the following information:

[0790] The terminal leaves a shared tunnel of at least one multicast service;

[0791] The terminal stops receiving at least one multicast service;

[0792] The terminal stops receiving at least one multicast service in the first cell;

[0793] The terminal leaves the first cell;

[0794] The terminal will enter or has entered the second cell;

[0795] The terminal stops receiving at least one multicast service at a first time point;

[0796] The terminal stops receiving at least one multicast service within a first time range;

[0797] The terminal enters or has entered the second cell at a second time point;

[0798] The terminal enters or has entered the second cell within a second time range; wherein,

[0799] When the terminal is in an idle state or an inactive state, the identifier of the terminal is retained in a first list; the first list contains at least one terminal identifier of a shared tunnel using at least one multicast service, or the first list contains at least one terminal identifier for establishing at least one multicast session, or the first list contains at least one terminal identifier for establishing a QoS flow of at least one multicast session, or the first list contains at least one terminal identifier for establishing at least one MRB.

[0800] In one embodiment, the third communication interface 1301 is used to receive third information sent by the terminal through message 1, message A or message 3 of random access.

[0801] Of course, in actual application, the various components in the second network node 1300 are coupled together through the bus system 1304. It can be understood that the bus system 1304 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 1304 also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, Fig.13 Various buses are labeled as bus system 1304 .

[0802] The third memory 1303 in the embodiment of the present application is used to store various types of data to support the operation of the second network node 1300. Examples of such data include: any computer program used to operate on the second network node 1300.

[0803] The method disclosed in the above embodiment of the present application can be applied to the third processor 1302, or implemented by the third processor 1302. The third processor 1302 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware or software instructions in the third processor 1302. The third processor 1302 mentioned above can be a general-purpose processor, a DSP, or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The third processor 1302 can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor can be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiment of the present application, it can be directly embodied as a hardware decoding processor to execute, or it can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium, which is located in the third memory 1303. The third processor 1302 reads the information in the third memory 1303 and completes the steps of the above method in combination with its hardware.

[0804] In an exemplary embodiment, the second network node 1300 may be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general purpose processors, controllers, MCUs, Microprocessors, or other electronic components to perform the aforementioned methods.

[0805] Based on the hardware implementation of the above program module, and in order to implement the method on the third network node side of the embodiment of the present application, the embodiment of the present application also provides a third network node, such as Fig.14 As shown, the third network node 1400 includes:

[0806] The fourth communication interface 1401 is capable of exchanging information with the terminal and the fourth network node;

[0807] a fourth processor 1402, connected to the fourth communication interface 1401, to implement information interaction with the terminal and the fourth network node, and configured to execute the method provided by one or more technical solutions on the network device side when running the computer program;

[0808] A fourth memory 1403 , on which the computer program is stored.

[0809] Specifically, the fourth communication interface 1401 is used to receive a first paging message for at least one multicast service sent by a fourth network node;

[0810] The fourth processor 1402 is configured to generate a second paging message using the first paging message; the second paging message is for at least one multicast service;

[0811] The fourth communication interface 1401 is further used to send the second paging message.

[0812] In one embodiment, the fourth communication interface 1401 is also used to broadcast a message; the message carries the period of the second paging message.

[0813] In one embodiment, the fourth processor 1402 is configured to determine the PO and the PF using an identifier associated with the multicast service.

[0814] Of course, in actual application, the various components in the third network node 1400 are coupled together through the bus system 1404. It can be understood that the bus system 1404 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 1404 also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, Fig.14 Various buses are labeled as bus system 1404.

[0815] The fourth memory 1403 in the embodiment of the present application is used to store various types of data to support the operation of the third network node 1400. Examples of such data include: any computer program used to operate on the third network node 1400.

[0816] The method disclosed in the above embodiment of the present application can be applied to the fourth processor 1402, or implemented by the fourth processor 1402. The fourth processor 1402 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by an integrated logic circuit of the hardware in the fourth processor 1402 or an instruction in the form of software. The above-mentioned fourth processor 1402 may be a general-purpose processor, a DSP, or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The fourth processor 1402 can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiment of the present application, it can be directly embodied as a hardware decoding processor to execute, or it can be executed by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium, which is located in the fourth memory 1403, and the fourth processor 1402 reads the information in the fourth memory 1403 and completes the steps of the above method in combination with its hardware.

[0817] In an exemplary embodiment, the third network node 1400 may be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general processors, controllers, MCUs, Microprocessors, or other electronic components to perform the aforementioned methods.

[0818] It can be understood that the memory (first memory 1103, second memory 1203, third memory 1303, fourth memory 1403) of the embodiment of the present application can be a volatile memory or a non-volatile memory, and can also 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), a magnetic random access memory (FRAM), a flash memory, a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM); the magnetic surface memory can be a disk memory or a tape memory. The volatile memory can be a random access memory (RAM), which is used as an external cache.By way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), synchronous static random access memory (SSRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), direct memory bus random access memory (DRRAM). The memory described in the embodiments of the present application is intended to include but is not limited to these and any other suitable types of memory.

[0819] To implement the method of the embodiment of the present application, the embodiment of the present application also provides a multicast service processing system, the system includes: a terminal, a first network node and a second network node; or, the system includes: a terminal, a third network node and a fourth network node.

[0820] Here, it should be noted that: the specific processing procedures of the terminal, the first network node, the second network node, the third network node and the fourth network node have been described in detail above and will not be repeated here.

[0821] In an exemplary embodiment, the embodiment of the present application further provides a storage medium, that is, a computer storage medium, specifically a computer-readable storage medium, for example, including a first memory 1103 storing a computer program, the computer program can be executed by the first processor 1102 of the terminal 1100 to complete the steps of the terminal side method, for example, including a second memory 1203 storing a computer program, the computer program can be executed by the second processor 1202 of the first network node 1200 to complete the steps of the first network node side method, for example, including a third memory 1303 storing a computer program, the computer program can be executed by the third processor 1302 of the second network node 1300 to complete the steps of the second network node side method, for example, including a fourth memory 1403 storing a computer program, the computer program can be executed by the fourth processor 1402 of the third network node 1400 to complete the steps of the third network node side method. The computer-readable storage medium can be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disk, or CD-ROM.

[0822] It should be noted that: "first", "second", etc. are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0823] In addition, the technical solutions described in the embodiments of the present application can be combined arbitrarily without conflict.

[0824] The above description is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application.

Claims

1. A method for processing a multicast service, characterized in that: Applied to terminals, including: The terminal changes from the first cell to the second cell when in an idle state or an inactive state; Sending a first request to a first network node where the second cell is located; the first request is used to request receiving resource information of at least one multicast service; receiving resource information for receiving at least one multicast service sent by the first network node; wherein, The sending a first request to a first network node where the second cell is located includes: Receive system messages; Acquire configuration information of a first resource from the system message; the first resource is shared by at least two terminals; When the terminal is in an idle state or an inactive state, sending a first request to the first network node on the first resource; The method further comprises: When the terminal is in an idle state or an inactive state, third information is sent to the second network node where the first cell is located; the third information is used to indicate at least one of the following information: The terminal leaves the shared tunnel of at least one requested multicast service; The terminal stops receiving at least one requested multicast service; The terminal stops receiving the at least one requested multicast service in the first cell; The terminal leaves the first cell; The terminal will enter or has entered the second cell; The terminal stops receiving at least one requested multicast service at a first time point; The terminal stops receiving at least one requested multicast service within a first time range; The terminal enters or has entered the second cell at a second time point; The terminal enters or has entered the second cell within a second time range.

2. The method according to claim 1, characterized in that The first request carries at least one of the following information: A temporary mobile group identifier TMGI corresponding to at least one multicast service requested to be received; a multicast session identifier corresponding to at least one multicast service requested to be received; a multicast quality of service QoS flow identifier corresponding to at least one multicast service requested to be received; a multicast radio bearer MRB identifier corresponding to at least one multicast service requested to be received; A multicast IP address corresponding to at least one multicast service requested to be received; A group radio network temporary identifier G-RNTI corresponding to at least one multicast service requested to be received; identification information of the terminal; First cell information; or, The first request is a sounding reference signal SRS with a multicast broadcast service MBS service as the granularity and / or with a MBS group as the granularity.

3. The method according to claim 1, characterized in that: The method further comprises: When one of the following conditions is met, a second request is sent to the first network node, where the second request is used to request to establish a multicast session corresponding to at least one multicast service requested to be received: receiving a reply message sent by the first network node indicating that at least one requested multicast service does not exist; receiving first information sent by the first network node, wherein the first information instructs the terminal to initiate a request to establish a multicast session corresponding to at least one requested multicast service to the network side; Second information sent by the first network node is received, where the second information instructs the terminal to send non-access layer NAS configuration information of the multicast service received in the first cell and stored by the terminal.

4. The method according to claim 3, characterized in that The sending a second request to the first network node where the second cell is located includes: Sending a multicast session establishment request message of at least one requested multicast service to the first network node; Alternatively, the second request carries the NAS configuration information of the multicast service received in the first cell and / or the first cell information saved by the terminal.

5. The method according to claim 1, characterized in that The sending a first request to a first network node where the second cell is located includes: It is detected that a multicast session corresponding to at least one requested multicast service and / or a shared tunnel corresponding to at least one requested multicast service in the second cell are not established, and a first request is sent to a first network node where the second cell is located.

6. The method according to claim 5, characterized in that Detecting whether a multicast session corresponding to at least one multicast service requested in the second cell and / or a shared tunnel corresponding to at least one multicast service requested is established includes: Detecting from the system message of the second cell whether there is control information of at least one multicast service requested to be received; When the control information of the at least one requested multicast service exists, determining that a multicast session corresponding to the at least one requested multicast service and / or a shared tunnel corresponding to the at least one requested multicast service in the second cell has been established; or When control information of the at least one requested multicast service does not exist, it is determined that a multicast session corresponding to the at least one requested multicast service and / or a shared tunnel corresponding to the at least one requested multicast service in the second cell are not established.

7. The method according to claim 1, characterized in that The resource information includes at least one of the following information: The TMGI corresponding to each one or more multicast services of receiving at least one multicast service; The session identifier corresponding to each one or more multicast services of receiving at least one multicast service; The G-RNTI corresponding to each one or more multicast services of receiving at least one multicast service; At least one of time domain information, frequency domain information and spatial domain information corresponding to each one or more multicast services of the received at least one multicast service; The receiving scheduling information corresponding to each one or more multicast services of at least one multicast service; The receiving of the configuration information of the wireless side corresponding to each one or more multicast services of the at least one multicast service; Multicast service list.

8. The method according to claim 7, characterized in that The multicast service list includes at least one of the following: TMGI corresponding to each multicast service or services; A session identifier corresponding to each one or more multicast services; G-RNTI corresponding to each multicast service or services; The correspondence between point-to-multipoint configuration information and multicast services; The mapping relationship between multicast services and logical channels; Priority information of multicast services.

9. The method according to claim 8, characterized in that The priority information of the multicast service includes at least one of the following: Priority information corresponding to multicast services; Priority information of the logical channel corresponding to the multicast service; The priority information of the semi-static scheduling SPS corresponding to the multicast service; Priority information of the newly transmitted data and / or retransmitted data corresponding to the multicast service relative to the newly transmitted data and / or retransmitted data of the unicast service; Preemption priority information of new transmission data and / or retransmission data corresponding to the multicast service relative to the new transmission data and / or retransmission data of the unicast service; Priority information of data corresponding to the multicast service relative to the measurement interval; The priority of the data corresponding to the multicast service relative to the downlink media access control control element MAC CE; A mapping relationship between a multicast service and at least one of a multicast or broadcast control channel MCCH and a multicast or broadcast service channel MTCH; The mapping relationship between multicast services and the radio network temporary identifier RNTI related to multicast; Shared tunnel information used for sending or receiving multicast services; IP multicast address information used for sending or receiving multicast services; The media type of the multicast service; MBS area information corresponding to the second cell.

10. The method according to claim 1, characterized in that The receiving resource information for receiving at least one multicast service sent by the first network node includes: Resource information for receiving at least one multicast service sent by the first network node is received through radio resource control RRC signaling and / or NAS information.

11. The method according to claim 1, characterized in that The terminal enters a connected state from an idle state or an inactive state, and sends a first request to the second cell; After receiving the resource information for receiving at least one multicast service sent by the first network node, the idle state or the inactive state is entered again.

12. The method according to any one of claims 1 to 11, characterized in that: The changing from the first cell to the second cell includes: receiving fourth information when in the first cell; the fourth information represents a multicast service being sent by at least one neighboring cell; Using the fourth information, perform at least one of the following operations to change from the first cell to the second cell: Cell selection; Cell reselection; Community reconstruction.

13. The method according to claim 1, characterized in that The sending third information to the second network node where the first cell is located includes: The third information is sent to the second network node through message 1, message A or message 3 of random access.

14. The method according to any one of claims 1 to 11, characterized in that When the second cell and the first cell do not belong to the same MBS area, sending the first request to the second network node; When the second cell and the first cell belong to the same MBS area, the multicast service is received directly by using the resource information of the multicast service receiving resources obtained in the first cell.

15. The method according to claim 14, characterized in that The MBS area includes at least one of the following characteristics: The MBS area includes at least one cell and at least one of the MBS service types sent between the cells is the same; The MBS area includes at least one cell and the MBS service types sent between the cells are the same; The time domain resources of MBS services sent by cells within the MBS area are the same; The frequency domain resources of MBS services transmitted by cells within the MBS area are the same; The RNTI used by different cells in the MBS area to activate MBS services or to scramble the signaling for the paging terminal to enter the connected state to receive MBS services is the same; The RNTI used for signaling scrambling of MBS services in different cells within the MBS area is the same; Time synchronization between different cells within the MBS area; The cells within the MBS area send cell-specific synchronization signal blocks SSB and / or channel state information reference signals CSI-RS, and also send SSB and / or CSI-RS with the MBS area as the granularity; The cells within the MBS area send cell-specific SSBs and / or CSI-RSs, and also send SSBs and / or CSI-RSs with a granularity of specific MBS services within the MBS area; In addition to sending the cell-specific SSB, the cells within the MBS area also send the same demodulation reference signal DMRS within the MBS area with the specific MBS service within the MBS area as the granularity.

16. The method according to claim 14, characterized in that The MBS area includes at least one of the following characteristics: When the terminal is in idle or inactive state, it receives MBS services in a cell within the MBS area and does not need to inform the network when changing from one cell to another; The terminal and multiple cells and / or base stations in the MBS area can receive at least one same MBS service in multiple cells through carrier aggregation and / or multi-connection.

17. A method for processing a multicast service, characterized in that: The method is applied to a first network node where a second cell is located, comprising: A first request sent by a receiving terminal when the receiving terminal is in an idle state or an inactive state; the first request is used to request resource information for receiving at least one multicast service; the terminal in the idle state or the inactive state can receive the requested at least one multicast service in the second cell; Sending resource information for receiving at least one multicast service to the terminal; wherein, The first request sent when the receiving terminal is in an idle state or an inactive state includes: Broadcasting a system message; the system message includes configuration information of a first resource; the first resource is shared by at least two terminals; A first request sent on a first resource when the terminal is in an idle state or an inactive state is received; the terminal includes a terminal that changes from a first cell to a second cell when in an idle state or an inactive state.

18. The method according to claim 17, characterized in that When a multicast session and / or a shared tunnel corresponding to at least one multicast service requested in the second cell has been established, resource information for receiving at least one multicast service is sent to the terminal.

19. The method according to claim 17, characterized in that The method further comprises: When a multicast session and / or a shared tunnel corresponding to at least one multicast service requested in the second cell is not established, sending first information to the terminal, wherein the first information instructs the terminal to initiate a request to establish a multicast session of the requested multicast service to the network side; or, When a multicast session and / or a shared tunnel corresponding to at least one multicast service requested in the second cell is not established, sending second information to the terminal, wherein the second information instructs the terminal to send NAS configuration information of the multicast service received in the first cell and stored by the terminal; or, When a multicast session and / or a shared tunnel corresponding to at least one multicast service requested in the second cell is not established, initiating a process of acquiring relevant configuration information of the multicast service received by the terminal in the first cell from a second network node where the first cell is located; or, When the multicast session and / or shared tunnel corresponding to the at least one multicast service requested in the second cell is not established, reply information indicating that the at least one multicast service requested does not exist is sent to the terminal.

20. The method according to claim 19, characterized in that The method further comprises: A second request sent by the terminal is received, where the second request is used to request to establish a multicast session corresponding to at least one multicast service requested to be received.

21. The method according to claim 20, characterized in that The receiving a second request sent by the terminal includes: receiving a multicast session establishment request message of at least one requested multicast service sent by the terminal; or, The second request carries the NAS configuration information of the multicast service received in the first cell and / or the first cell information saved by the terminal.

22. A method for processing a multicast service, characterized in that: The method is applied to a second network node where a first cell is located, comprising: receiving third information sent by a terminal in an idle state or an inactive state; the terminal includes a terminal that changes from the first cell to the second cell when in an idle state or an inactive state; the third information is used to indicate at least one of the following information: The terminal leaves a shared tunnel of at least one multicast service; The terminal stops receiving at least one multicast service; The terminal stops receiving at least one multicast service in the first cell; The terminal leaves the first cell; The terminal will enter or has entered the second cell; The terminal stops receiving at least one multicast service at a first time point; The terminal stops receiving at least one multicast service within a first time range; The terminal enters or has entered the second cell at a second time point; The terminal enters or has entered the second cell within a second time range; In the case where the first list contains the identifier of the terminal and the identifiers of other terminals, the identifier of the terminal is deleted from the first list; the first list contains at least one terminal identifier of a shared tunnel using at least one multicast service, or the first list contains at least one terminal identifier for establishing at least one multicast session, or the first list contains at least one terminal identifier for establishing a QoS flow of at least one multicast session, or the first list contains at least one terminal identifier for establishing at least one MRB; or, in the case where the first list only contains the identifier of the terminal, the first list is cleared, the shared tunnel is released, and shared tunnel deletion information is sent to the core network.

23. The method according to claim 22, characterized in that The receiving terminal sends third information through message 1, message A or message 3 of random access.

24. A multicast service processing device, characterized in that: include: A changing unit, used for changing from a first cell to a second cell when the terminal is in an idle state or an inactive state; A first sending unit, configured to send a first request to a first network node where the second cell is located; The first request is used to request to receive resource information of at least one multicast service; The first receiving unit is configured to receive resource information for receiving at least one multicast service sent by the first network node; wherein: The first receiving unit is further used to receive a system message; The first sending unit is further configured to obtain configuration information of a first resource from the system message; the first resource is shared by at least two terminals; and the terminal sends a first request to the first network node on the first resource when the terminal is in an idle state or an inactive state; The first sending unit is further configured to send third information to the second network node where the first cell is located when the terminal is in an idle state or an inactive state; the third information is used to indicate at least one of the following information: The terminal leaves the shared tunnel of at least one requested multicast service; The terminal stops receiving at least one requested multicast service; The terminal stops receiving the at least one requested multicast service in the first cell; The terminal leaves the first cell; The terminal will enter or has entered the second cell; The terminal stops receiving at least one requested multicast service at a first time point; The terminal stops receiving at least one requested multicast service within a first time range; The terminal enters or has entered the second cell at a second time point; The terminal enters or has entered the second cell within a second time range.

25. A device for processing a multicast service, characterized in that: The first network node configured in the second cell includes: A second receiving unit is used to receive a first request sent by a terminal in an idle state or an inactive state; the first request is used to request to receive resource information of at least one multicast service; the terminal in the idle state or the inactive state can receive the requested at least one multicast service in the second cell; The second sending unit is used to send resource information for receiving at least one multicast service to the terminal; wherein: The second sending unit is further used to broadcast a system message; the system message includes configuration information of a first resource; the first resource is shared by at least two terminals; The second receiving unit is further used to receive a first request sent on a first resource when the terminal is in an idle state or an inactive state; the terminal includes a terminal that changes from a first cell to a second cell when in an idle state or an inactive state.

26. A multicast service processing device, characterized in that: The second network node set at the first cell includes: A third receiving unit is configured to receive third information sent when the terminal is in an idle state or an inactive state; the terminal includes a terminal that changes from the first cell to the second cell when in an idle state or an inactive state; and the third information is used to indicate at least one of the following information: The terminal leaves a shared tunnel of at least one multicast service; The terminal stops receiving at least one multicast service; The terminal stops receiving at least one multicast service in the first cell; The terminal leaves the first cell; The terminal will enter or has entered the second cell; The terminal stops receiving at least one multicast service at a first time point; The terminal stops receiving at least one multicast service within a first time range; The terminal enters or has entered the second cell at a second time point; The terminal enters or has entered the second cell within a second time range; wherein, The fourth sending unit is used to clear the first list, release the shared tunnel, and send shared tunnel deletion information to the core network when the first list only contains the identifier of the terminal; the first list contains at least one terminal identifier of a shared tunnel using at least one multicast service, or the first list contains at least one terminal identifier for establishing at least one multicast session, or the first list contains at least one terminal identifier for establishing a QoS flow of at least one multicast session, or the first list contains at least one terminal identifier for establishing at least one MRB; or, the fourth sending unit is used to delete the identifier of the terminal from the first list when the first list contains the identifier of the terminal and identifiers of other terminals.

27. A terminal, characterized in that: include: A first processor and a first communication interface; wherein, The first processor is used to change from the first cell to the second cell when the terminal is in an idle state or an inactive state; the first communication interface is used to send a first request to a first network node where the second cell is located; the first request is used to request to receive resource information of at least one multicast service; and receive resource information of receiving at least one multicast service sent by the first network node; wherein, The first communication interface is further used to receive a system message; obtain configuration information of a first resource from the system message; the first resource is shared by at least two terminals; when the terminal is in an idle state or an inactive state, the terminal sends a first request to the first network node on the first resource; The first communication interface is further used to send third information to the second network node where the first cell is located when the terminal is in an idle state or an inactive state; the third information is used to indicate at least one of the following information: The terminal leaves the shared tunnel of at least one requested multicast service; The terminal stops receiving at least one requested multicast service; The terminal stops receiving the at least one requested multicast service in the first cell; The terminal leaves the first cell; The terminal will enter or has entered the second cell; The terminal stops receiving at least one requested multicast service at a first time point; The terminal stops receiving at least one requested multicast service within a first time range; The terminal enters or has entered the second cell at a second time point; The terminal enters or has entered the second cell within a second time range.

28. A first network node, characterized in that: include: A second processor and a second communication interface; wherein, The second communication interface is used to receive a first request sent when the terminal is in an idle state or an inactive state; the first request is used to request resource information for receiving at least one multicast service; the terminal in the idle state or the inactive state can receive the requested at least one multicast service in the second cell; and send resource information for receiving at least one multicast service to the terminal; wherein, The second communication interface is also used to broadcast system messages; the system message includes configuration information of a first resource; the first resource is shared by at least two terminals; a first request sent on the first resource when the terminal is in an idle state or an inactive state is received; the terminal includes a terminal that changes from a first cell to a second cell when in an idle state or an inactive state; the first network node includes a network node where the second cell is located.

29. A second network node, characterized in that: include: A third processor and a third communication interface; wherein, The third communication interface is used to receive third information sent when the terminal is in an idle state or an inactive state; the terminal includes a terminal that changes from the first cell to the second cell when in an idle state or an inactive state; the third information is used to indicate at least one of the following information: The terminal leaves a shared tunnel of at least one multicast service; The terminal stops receiving at least one multicast service; The terminal stops receiving at least one multicast service in the first cell; The terminal leaves the first cell; The terminal will enter or has entered the second cell; The terminal stops receiving at least one multicast service at a first time point; The terminal stops receiving at least one multicast service within a first time range; The terminal enters or has entered the second cell at a second time point; The terminal enters or has entered the second cell within a second time range; wherein, In the case where the first list only contains the identifier of the terminal, the first list is cleared, the shared tunnel is released, and the shared tunnel deletion information is sent to the core network; the first list contains at least one terminal identifier of a shared tunnel using at least one multicast service, or the first list contains at least one terminal identifier for establishing at least one multicast session, or the first list contains at least one terminal identifier for establishing a QoS flow of at least one multicast session, or the first list contains at least one terminal identifier for establishing at least one MRB; or, in the case where the first list contains the identifier of the terminal and the identifiers of other terminals, the identifier of the terminal is deleted from the first list; the second network node includes the network node where the first cell is located.

30. A terminal, characterized in that: include: a first processor and a first memory for storing a computer program executable on the processor, Wherein, when the first processor is used to run the computer program, the steps of the method described in any one of claims 1 to 16 are executed.

31. A first network node, characterized in that: include: a second processor and a second memory for storing a computer program executable on the processor, Wherein, when the second processor is used to run the computer program, it executes the steps of the method described in any one of claims 17 to 21.

32. A second network node, characterized in that: include: a third processor and a third memory for storing a computer program executable on the processor, Wherein, the third processor is used to execute the steps of the method described in claim 22 or 23 when running the computer program.

33. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, it implements the steps of the method described in any one of claims 1 to 16, or implements the steps of the method described in any one of claims 17 to 21, or implements the steps of the method described in claim 22 or 23.

Images