Method for multicast service and small data transmission in wireless communication, and device

Abstract

The present application discloses a method for a multicast service and small data transmission in wireless communication, and a device. The method comprises: receiving first signaling, the first signaling being configured for small data transmission in an RRC inactive state, and the first signaling being configured to receive a multicast service in the RRC inactive state; and in the RRC inactive state, in response to any condition in a first condition set being satisfied, sending first information, the sending first information depending on whether the small data transmission is being performed. The present application allows for better reception of a multicast service and ensures the continuity of multicast service reception.

Description

A method and device for multicast services and small data transmission in wireless communications Technical Field

[0001] The present application relates to a method and apparatus for multicast services and small data transmission in a wireless communication system, and relates to receiving multicast services and small data transmission in an RRC inactive state, and in particular to simultaneously receiving multicast services and performing small data transmission. Background Art

[0002] The application scenarios of future wireless communication systems will become increasingly diverse, and different scenarios will place varying performance requirements on the systems. To meet these diverse performance demands, the 3GPP (3rd Generation Partner Project) RAN (Radio Access Network) plenary meeting #72 decided to conduct research on New Radio (NR) (or Fifth Generation, 5G). The NR Work Item (WI) was approved at the 3GPP RAN plenary meeting #75, initiating standardization work on NR.

[0003] In communications, both LTE (Long Term Evolution) and 5G NR require reliable and accurate information reception, optimized energy efficiency, determination of information validity, flexible resource allocation, scalable system architecture, efficient non-access layer information processing, low service interruption and call drop rates, and support for low power consumption. These requirements are crucial for normal communication between base stations and user devices, rational resource scheduling, and system load balancing. They are the cornerstone for achieving high throughput, meeting the communication needs of various services, improving spectrum utilization, and enhancing service quality. They are indispensable for eMBB (enhanced Mobile Broadband), URLLC (Ultra Reliable Low Latency Communication), and eMTC (enhanced Machine Type Communication). At the same time, there are extensive demands in IIoT (Industrial Internet of Things), V2X (Vehicular to X), device-to-device communication, unlicensed spectrum communication, user communication quality monitoring, network planning and optimization, TN (Territory Network), dual connectivity systems, wireless resource management and multi-antenna codebook selection, signaling design, neighboring cell management, service management, and beamforming. Information is sent in two ways: broadcast and unicast. Both transmission methods are essential for 5G systems because they are very helpful in meeting the above requirements.

[0004] As the scenarios and complexity of the system continue to increase, higher requirements are placed on reducing interruption rates, reducing latency, enhancing reliability, enhancing system stability, business flexibility, and saving power. At the same time, compatibility between different system versions also needs to be considered during system design.

[0005] The meanings of the concepts, terms, and abbreviations in this application may refer to the 3GPP standards, including but not limited to:

[0006] https: / / www.3gpp.org / ftp / Specs / archive / 21_series / 21.905 / 21905-h10.zip

[0007] https: / / www.3gpp.org / ftp / Specs / archive / 38_series / 38.300 / 38300-h10.zip

[0008] https: / / www.3gpp.org / ftp / Specs / archive / 38_series / 38.331 / 38331-h10.zip

[0009] https: / / www.3gpp.org / ftp / Specs / archive / 38_series / 38.133 / 38133-h10.zip

[0010] https: / / www.3gpp.org / ftp / Specs / archive / 38_series / 38.304 / 38304-h10.zip

[0011] https: / / www.3gpp.org / ftp / Specs / archive / 32_series / 32.422 / 32422-h10.zip

[0012] https: / / www.3gpp.org / ftp / Specs / archive / 37_series / 37.320 / 37320-h10.zip

[0013] Summary of the Invention

[0014] Researchers found that in a non-RRC connected state, when receiving or needing to receive multicast services, how to select an appropriate control channel to send uplink information based on whether small data transmission is in progress is a problem that needs to be solved.

[0015] In response to the above-mentioned problems, this application provides a solution.

[0016] It should be noted that, in the absence of conflict, the embodiments and features of any node in this application can be applied to any other node. In the absence of conflict, the embodiments and features of the embodiments of this application can be combined with each other in any way. At the same time, the method proposed in this application can also be used to solve other problems in communications, such as NR evolution and problems in 6G systems.

[0017] As an embodiment, the interpretation of terminology in this application refers to the definition of 3GPP specification protocol TS38 series.

[0018] As an example, the interpretation of the terms in this application refers to the definitions of the TS37 series of specification protocols of 3GPP.

[0019] The present application discloses a method in a first node for wireless communication, comprising:

[0020] receiving a first signaling, wherein the first signaling is configured to transmit small data in an RRC inactive state; and receiving a multicast service in an RRC inactive state;

[0021] In the RRC inactive state, sending first information as a response to any condition in the first condition set being met; the sending of the first information depends on whether small data transmission is in progress;

[0022] Among them, the first condition set includes receiving a first system information block that triggers multicast service reception, the configuration of at least one active multicast service session joined by the first node is unavailable, the serving cell does not provide at least one active multicast service session joined by the first node to the RRC inactive state, and the measurement of the serving cell is lower than at least one of the given thresholds for at least one active multicast service session joined by the first node; the sending of the first information depends on whether small data transmission is in progress, including: when small data transmission is in progress, sending the first information through a dedicated control channel; when small data transmission is not in progress, sending the first information through a common control channel, wherein the first information includes an RRC connection recovery request.

[0023] As an embodiment, the problem to be solved by the present application includes: in a non-RRC connected state, when receiving or needing to receive a multicast service, how to select an appropriate control channel to send the first information according to whether a small data transmission is in progress.

[0024] As an embodiment, the above method has the following advantages: saving signaling overhead, having good flexibility, ensuring reception of multicast services, and avoiding conflicts between sending the first information and transmitting small data.

[0025] Specifically, according to one aspect of the present application, the first information is used to request reception of a multicast service in an RRC connected state.

[0026] Specifically, according to one aspect of the present application, when small data transmission is in progress, the first information includes UE auxiliary information.

[0027] Specifically, according to one aspect of the present application, when small data transmission is not in progress, any condition in the first condition set is met to trigger the initiation of the RRC connection recovery process.

[0028] Specifically, according to one aspect of the present application, the configuration of at least one active multicast service session joined by the first node is unavailable, which means that the configuration of at least one active multicast service session joined by the first node is unavailable in the cell after cell selection or reselection; the service cell does not provide at least one active multicast service session joined by the first node to the RRC inactive state, which means that the cell after cell selection or reselection does not provide at least one active multicast service session joined by the first node to the RRC inactive state.

[0029] Specifically, according to one aspect of the present application, when small data transmission is in progress, the first information is sent via SRB1; when no small data transmission is in progress, the first information is sent via SRB0.

[0030] Specifically, according to one aspect of the present application, when small data transmission is in progress, the first information occupies only one bit in the UE auxiliary information.

[0031] Specifically, according to one aspect of the present application, the first node enters an RRC inactive state along with the execution of the first signaling.

[0032] Specifically, according to one aspect of the present application, second information is sent, where the second information indicates the arrival of at least one of data and signaling mapped to a radio bearer other than a radio bearer configured for small data transmission; the second information is sent via a dedicated control channel;

[0033] Among them, small data transmission is ongoing.

[0034] Specifically, according to one aspect of the present application, the first condition set includes: being unable to simultaneously receive multiple active multicast service sessions joined by the first node.

[0035] Specifically, according to one aspect of the present application, the first condition set includes: failure to obtain MCCH.

[0036] Specifically, according to one aspect of the present application, the first node is an Internet of Things terminal.

[0037] Specifically, according to one aspect of the present application, the first node is user equipment.

[0038] Specifically, according to one aspect of the present application, the first node is an access network device.

[0039] Specifically, according to one aspect of the present application, the first node is a vehicle-mounted terminal.

[0040] Specifically, according to one aspect of the present application, the first node is a mobile phone.

[0041] The present application discloses a first node used for wireless communication, comprising:

[0042] A first receiver receives a first signaling, wherein the first signaling is configured to transmit small data in an RRC inactive state; the first signaling is configured to receive a multicast service in the RRC inactive state;

[0043] The first transmitter, in an RRC inactive state, sends first information in response to any condition in a first condition set being met; the sending of the first information depends on whether small data transmission is in progress;

[0044] Among them, the first condition set includes receiving a first system information block that triggers multicast service reception, the configuration of at least one active multicast service session joined by the first node is unavailable, the serving cell does not provide at least one active multicast service session joined by the first node to the RRC inactive state, and the measurement of the serving cell is lower than at least one of the given thresholds for at least one active multicast service session joined by the first node; the sending of the first information depends on whether small data transmission is in progress, including: when small data transmission is in progress, sending the first information through a dedicated control channel; when small data transmission is not in progress, sending the first information through a common control channel, wherein the first information includes an RRC connection recovery request.

[0045] As an example, compared with traditional solutions, this application has the following advantages:

[0046] It can better support receiving multicast services and performing small data transmission in the RRC inactive state.

[0047] The sending of the first information triggered by or for receiving a multicast service uses a more appropriate control channel; generally speaking, a dedicated control channel has better security and lower latency; a public control channel is simpler, has fewer prerequisites, and is available at any time.

[0048] Using a dedicated control channel has lower signaling overhead, for example, only one bit may be used for indication.

[0049] This helps ensure continuous reception of multicast services. For example, when the channel quality deteriorates, the RRC connected state can be entered as quickly as possible to continue receiving multicast services.

[0050] It saves more power and can better support receiving multicast services and small data transmission in the RRC inactive state. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] Other features, objects and advantages of the present application will become more apparent upon reading the detailed description of non-limiting embodiments with reference to the following drawings:

[0052] FIG1 shows a flowchart of executing first signaling and sending first information according to an embodiment of the present application;

[0053] FIG2 shows a schematic diagram of a network architecture according to an embodiment of the present application;

[0054] FIG3 is a schematic diagram showing an embodiment of a radio protocol architecture of a user plane and a control plane according to an embodiment of the present application;

[0055] FIG4 shows a schematic diagram of a first communication device and a second communication device according to an embodiment of the present application;

[0056] FIG5 shows a flowchart of wireless signal transmission according to an embodiment of the present application;

[0057] FIG6 is a schematic diagram showing a method in which first information is used to request reception of a multicast service in an RRC connected state according to an embodiment of the present application;

[0058] FIG7 is a schematic diagram showing the arrival of at least one of data and signaling mapped to a radio bearer other than a radio bearer configured for small data transmission according to an embodiment of the present application;

[0059] FIG8 illustrates a schematic diagram of a processing device used in a first node according to an embodiment of the present application.

[0060] Implementation Method

[0061] The technical solution of the present application will be further described in detail below in conjunction with the accompanying drawings. It should be noted that, unless there is a conflict, the embodiments and features in the embodiments of the present application can be combined with each other in any way.

[0062] Example 1

[0063] Example 1 illustrates a flowchart of executing first signaling and sending first information according to an embodiment of the present application, as shown in Figure 1. In Figure 1, each box represents a step, and it is particularly important to emphasize that the order of the boxes in the figure does not represent the temporal sequence between the steps represented.

[0064] In embodiment 1, the first node in the present application receives first signaling in step 101; sends first information in step 102;

[0065] Among them, the first signaling configuration is small data transmission in the RRC inactive state; the first signaling configuration is to receive multicast services in the RRC inactive state; in the RRC inactive state, any condition in the first condition set is met to trigger the sending of the first information; the sending of the first information depends on whether small data transmission is in progress; the first condition set includes receiving a first system information block that triggers multicast service reception, the configuration of at least one active multicast service session joined by the first node is unavailable, the serving cell does not provide at least one active multicast service session joined by the first node to the RRC inactive state, and the measurement of the serving cell is lower than at least one of the given thresholds for at least one active multicast service session joined by the first node; the sending of the first information depends on whether small data transmission is in progress, including: when small data transmission is in progress, sending the first information through a dedicated control channel; when small data transmission is not in progress, sending the first information through a common control channel, wherein the first information includes an RRC connection recovery request.

[0066] As an embodiment, the first node is a UE (User Equipment).

[0067] As an embodiment, any parameter in the present application may be either configured by the network or generated by the first node according to an internal algorithm, such as random.

[0068] As an example, the value of any parameter in this application, including but not limited to the value of a timer and the value of a counter, is limited unless otherwise stated.

[0069] As a sub-embodiment of this embodiment, the upper limit of the value of any parameter in this application is 1024 times of 65536.

[0070] As a sub-embodiment of this embodiment, the upper limit of the value of any parameter in this application is 65536 or 65535.

[0071] As a sub-embodiment of this embodiment, the upper limit of the value of any parameter in this application is 1024.

[0072] As a sub-embodiment of this embodiment, the upper limit of the value of any parameter in this application is 640 or 320.

[0073] As an embodiment, the present application is directed to NR.

[0074] As an embodiment, the present application is directed to wireless communication networks after NR.

[0075] As an embodiment, the serving cell refers to the cell where the UE is camped. Performing a cell search includes the UE searching for a suitable cell in the selected PLMN (Public Land Mobile Network) or SNPN (Stand-alone Non-Public Network), selecting the suitable cell to provide available services, and monitoring the control channel of the suitable cell. This process is defined as camping on a cell; that is, a camped cell is the serving cell of the UE relative to the UE. Camping on a cell in the RRC idle state or RRC inactive state has the following benefits: it allows the UE to receive system messages from the PLMN or SNPN; after registration, if the UE wishes to establish an RRC connection or continue a suspended RRC connection, it can do so by performing initial access on the control channel of the camped cell; the network can page the UE; and it allows the UE to receive ETWS (Earthquake and Tsunami Warning System) and CMAS (Commercial Mobile Alert System) notifications.

[0076] As an embodiment, for a UE in an RRC connected state that is not configured with CA / DC (carrier aggregation / dual connectivity), there is only one serving cell including a primary cell. For a UE in an RRC connected state that is configured with CA / DC (carrier aggregation / dual connectivity), the serving cell is used to indicate a set of cells including a special cell (SpCell) and all cells from the cell. The primary cell (Primary Cell) is an MCG (Master Cell Group) cell that operates on the primary frequency, and the UE performs an initial connection establishment process or initiates connection reconstruction on the primary cell. For dual-connection operation, the special cell refers to the PCell (Primary Cell) of the MCG or the PSCell (Primary SCG Cell) of the SCG (Secondary Cell Group); if it is not a dual-connection operation, the special cell refers to the PCell.

[0077] As an embodiment, the operating frequency of the SCell (Secondary Cell) is a secondary frequency.

[0078] As an example, the individual contents of an information element are referred to as fields.

[0079] As an embodiment, MR-DC (Multi-Radio Dual Connectivity) refers to dual connectivity of E-UTRA and NR nodes, or dual connectivity between two NR nodes.

[0080] As an embodiment, in MR-DC, the wireless access node that provides the control plane connection to the core network is a master node, which can be a master eNB, a master ng-eNB, or a master gNB.

[0081] As an embodiment, MCG refers to a group of serving cells associated with a master node in MR-DC, including SpCells, and may also, optionally, include one or more SCells.

[0082] As an embodiment, PCell is the SpCell of MCG.

[0083] As an embodiment, the PSCell is the SpCell of the SCG.

[0084] As an embodiment, in MR-DC, the radio access node that does not provide a control plane connection to the core network and provides additional resources to the UE is a slave node. The slave node can be an en-gNB, a slave ng-eNB, or a slave gNB.

[0085] As an embodiment, in MR-DC, a group of serving cells associated with a slave node is a SCG (secondary cell group), which includes a SpCell and, optionally, one or more SCells.

[0086] As an embodiment, the SpCell is a PCell or the SpCell is a PSCell.

[0087] As an embodiment, in the RRC inactive state, DC is not used.

[0088] As an example, in the RRC inactive state, CA is typically not used.

[0089] As an embodiment, the RRC information block refers to an information block (information element) in an RRC message.

[0090] As an embodiment, SSB may be referred to as SS\PBCH, or SS block.

[0091] As an embodiment, L1 is Layer-1 or physical layer.

[0092] As an embodiment, the present application is directed to NR and NR evolved networks, such as 6G networks.

[0093] As an embodiment, an RRC information block may include one or more RRC information blocks.

[0094] As an embodiment, an RRC information block may not include any RRC information block, but only include at least one parameter.

[0095] As an embodiment, the radio bearer includes at least a signaling radio bearer and a data radio bearer.

[0096] As an embodiment, a radio bearer is a service or service interface provided by the PDCP layer to a higher layer.

[0097] As a sub-embodiment of this embodiment, the higher layer includes one of the RRC layer, NAS, and SDAP layer.

[0098] As an embodiment, the signaling radio bearer is a service or service interface provided by PDCP to a higher layer.

[0099] As a sub-embodiment of this embodiment, the higher layer includes the RRC layer, at least the former in the NAS.

[0100] As an embodiment, the data radio bearer is a service or an interface of services provided by PDCP to a higher layer.

[0101] As a sub-embodiment of this embodiment, the higher layer includes an SDAP layer, at least the former in NAS.

[0102] As an embodiment, after the first node establishes an RRC connection with the network, the first node enters an RRC connection state.

[0103] As a sub-embodiment of this embodiment, the network is a radio access network (RAN).

[0104] As an embodiment, when the first node does not establish an RRC connection with the network, the first node is in an RRC idle state.

[0105] As a sub-embodiment of this embodiment, the network is a radio access network (RAN).

[0106] As an embodiment, when the RRC connection established between the first node and the network is suspended, the first node enters an RRC inactive state.

[0107] As a sub-embodiment of this embodiment, the network is a radio access network (RAN).

[0108] As an embodiment, the first node supports different functions in different RRC states.

[0109] As an embodiment, the first node only supports very limited functions in the non-RRC connected state.

[0110] As an embodiment, the non-RRC connected state is or includes an RRC idle state.

[0111] As an embodiment, the non-RRC connected state is or includes an RRC inactive state.

[0112] As an embodiment, in the RRC idle state, the supported features include: DRX (Discontinuous reception) specific to the first node configured by a higher layer.

[0113] As an embodiment, in the RRC idle state, the supported features include: at a lower layer, the first node can be configured with DRX for PTM (point to multi point) transmission broadcast by MBS (multicast broadcast service).

[0114] As an embodiment, in the RRC idle state, the supported features include: mobility based on network configuration.

[0115] As an embodiment, in the RRC idle state, the supported features include: monitoring paging, listening to short messages scrambled by P-RNTI (paging radio network temporary identity), performing neighbor cell measurements and cell reselection, obtaining system information, sending system information requests, recording available measurements, performing idle or inactive state measurements, and obtaining MCCH (MBS Control channel) change notifications.

[0116] As an embodiment, in the RRC inactive state, the supported features include: DRX (Discontinuous reception) specific to the first node configured by a higher layer.

[0117] As an embodiment, in the RRC inactive state, the supported features include: at a lower layer, the first node can be configured with DRX for PTM (point to multi point) transmission of MBS (multicast broadcast service) broadcast.

[0118] As an embodiment, in the RRC inactive state, the supported features include: mobility based on network configuration.

[0119] As an embodiment, in the RRC inactive state, the supported features include: storing UE inactive AS (access stratum) context.

[0120] As an embodiment, in the RRC inactive state, the supported features include: configuring a RAN-based notification area.

[0121] As an embodiment, in the RRC inactive state, supported features include: transmitting data and / or signaling using a radio bearer configured with SDT (small data transmission).

[0122] As an embodiment, in the RRC inactive state, the supported features include: monitoring paging, listening to P-RNTI encrypted short messages, performing neighbor cell measurements and cell reselection, obtaining system information, sending system information requests, recording available measurements, performing idle or inactive state measurements, and obtaining MCCH (MBS Control channel) change notifications.

[0123] As an embodiment, in the RRC inactive state, the supported features include: monitoring the control channel during the SDT process.

[0124] As an embodiment, in the RRC inactive state, the supported features include: sending an SRS (sounding reference signal) for positioning during the SDT process.

[0125] As an embodiment, in the RRC connected state, the supported features include: storing AS context.

[0126] As an embodiment, in the RRC connected state, the supported features include: sending and receiving unicast data.

[0127] As an embodiment, in the RRC connected state, the supported features include: receiving MBS data.

[0128] As an embodiment, in the RRC connected state, the supported features include: configuring the first node-specific DRX by a higher layer.

[0129] As an embodiment, in the RRC connected state, the supported features include: at a lower layer, the first node may be configured with DRX for PTM transmission of MBS broadcast.

[0130] As an embodiment, in the RRC connected state, the supported features include: if CA is supported, using one or more SCells.

[0131] As an embodiment, in the RRC connected state, the supported features include: if DC is supported, using SCG.

[0132] As an embodiment, in the RRC connected state, the supported features include: network-controlled mobility.

[0133] As an embodiment, in the RRC connected state, the supported features include: monitoring the short message scrambled by the P-RNTI, and monitoring the control channel associated with the shared control channel.

[0134] As an embodiment, in the RRC connected state, the supported features include: providing channel quality information.

[0135] As an embodiment, in the RRC connected state, the supported features include: performing neighboring cell measurement and reporting.

[0136] As an embodiment, in the RRC connected state, the supported features include: obtaining system information.

[0137] As an embodiment, in the RRC connected state, the supported features include: performing intermediate MDT measurements and reporting available location information.

[0138] As an embodiment, in the RRC connected state, the supported features include: obtaining MCCH change notification to receive MBS broadcast.

[0139] As an embodiment, the first signaling indicates the given threshold for at least one active multicast service session joined by the first node.

[0140] As an embodiment, the multicast service is or includes an MBS (multicast broadcast service) service.

[0141] As an embodiment, the multicast service is a multicast MBS service.

[0142] As an embodiment, the multicast service includes data from the application layer.

[0143] As an embodiment, typical applications of the multicast service include streaming media.

[0144] As an embodiment, the multicast service is transmitted in PTM (point to multipoint) mode.

[0145] As an embodiment, the multicast service and the broadcast service are different. In this field, the terminal can receive the broadcast service in any RRC state including the RRC idle state, but can only receive the multicast service in the RRC inactive state or the RRC connected state. This shows that the transmission method and control means of the broadcast service and the multicast service are completely different.

[0146] As an embodiment, the network may not know which users receive the broadcast service, but whether the terminal can receive the multicast service is controlled by the network.

[0147] As an embodiment, the multicast service is sent via an MRB (MBS Radio Bearer).

[0148] As an embodiment, the small data transmission is sent via a DRB (data radio bearer) and / or an SRB (signaling radio bearer).

[0149] As an embodiment, the first signaling is actively sent by the network.

[0150] As an embodiment, the first signaling is actively sent by the network according to, for example, load conditions, whether the first node has other services to receive, and an active MBS service session to which the first node joins.

[0151] As an embodiment, the first signaling is RRC signaling.

[0152] As an embodiment, the first signaling indicates the release of the RRC connection.

[0153] As an embodiment, the first signaling is RRCRelease signaling.

[0154] As an embodiment, the first signaling uses encryption and integrity protection.

[0155] As an embodiment, the first signaling is sent using SRB1 (signaling radio bearer 1).

[0156] As an embodiment, upon receiving the first signaling, the first node suspends only the RB configured for small data transmission and the MRB used for transmitting the active multicast service session to which the first node joins.

[0157] As an embodiment, the first condition set includes receiving a first system information block that triggers multicast service reception, the configuration of at least one active multicast service session joined by the first node is unavailable, the serving cell does not provide at least one active multicast service session joined by the first node to the RRC inactive state, and the measurement of the serving cell is lower than a given threshold for at least one active multicast service session joined by the first node.

[0158] As an embodiment, the measurement of the serving cell includes RSRP.

[0159] As an embodiment, the measurement of the serving cell includes RSRQ.

[0160] As an embodiment, how the first node joins a multicast service or a multicast service session is prior art in the art.

[0161] As an embodiment, the network indicates whether the multicast service session is active.

[0162] As an embodiment, the serving cell is a cell that receives multicast services.

[0163] As an embodiment, the serving cell is a resident cell.

[0164] As an embodiment, the serving cell is the current cell.

[0165] As an embodiment, in the RRC inactive state, the first node has only one serving cell.

[0166] As an embodiment, in the RRC inactive state, the first node only receives the multicast service of one serving cell.

[0167] As an embodiment, the first signaling is downlink signaling.

[0168] As an embodiment, receiving the first signaling in the RRC connection state means: using DCCH (dedicated Control channel) to receive the first signaling.

[0169] As an embodiment, in the RRC idle state, control signaling can only be received using CCCH (common control channel) or BCCH (broadcast control channel).

[0170] As an embodiment, small data transmission (SDT) is a specific technology in this field, which means a specific transmission method and control mode.

[0171] As an embodiment, the first signaling configuration of small data transmission in the RRC inactive state includes: configuring a DRB that allows the use of SDT.

[0172] As an embodiment, the first signaling configuration of small data transmission in the RRC inactive state includes: configuring whether to allow the use of SRB2 (signaling radio bearer 2) in small data transmission.

[0173] As an embodiment, the first signaling configuration of small data transmission in the RRC inactive state includes: configuring an uplink grant (configured grant) for small data transmission.

[0174] As a sub-embodiment of this embodiment, the configuration of downlink and / or uplink BWP (bandwidth part) is included.

[0175] As a sub-embodiment of this embodiment, a CS-RNTI is included for uplink grant transmission.

[0176] As a sub-embodiment of this embodiment, a threshold for determining whether to use the small data transmission granted by the uplink is included.

[0177] As a sub-embodiment of this embodiment, a timing advance check configuration is included.

[0178] As a sub-embodiment of this embodiment, timing advance information is included.

[0179] As a sub-embodiment of this embodiment, it includes identification of a logical channel used for small data transmission.

[0180] As an embodiment, the first signaling configuration of small data transmission in the RRC inactive state includes: indicating whether to continue header compression.

[0181] As a sub-embodiment of this embodiment, the indication of whether to continue header compression refers to whether the PDCP entity configured for the radio bearer of small data transmission continues or resets the header compression protocol when the PDCP is re-established in small data transmission.

[0182] As an embodiment, the sdt-config field of the first signaling is configured for small data transmission in the RRC inactive state.

[0183] As an embodiment, the first signaling configuration for receiving multicast services in an RRC inactive state includes: configuring an inactive PTM.

[0184] As an embodiment, the first signaling configuration for receiving the multicast service in the RRC inactive state includes: configuring an MCCH (mbs control channel, MBS control channel) in the inactive state.

[0185] As an embodiment, the first signaling configuration for receiving multicast services in the RRC inactive state includes: indicating an MBS session information list.

[0186] As an embodiment, the first signaling configuration for receiving multicast services in the RRC inactive state includes: indicating an MBS neighbor list.

[0187] As an embodiment, the first signaling configuration for receiving multicast services in the RRC inactive state includes: configuring DRX for PTM.

[0188] As an embodiment, the first signaling configuration for receiving multicast services in the RRC inactive state includes: configuring MTCH (MBS traffic channel).

[0189] As an embodiment, the first signaling configuration for receiving the multicast service in the RRC inactive state includes: configuring a PDSCH (physical downlink shared channel) carrying the MTCH.

[0190] As an embodiment, the first signaling configuration for receiving multicast services in the RRC inactive state includes: configuring the SSB mapping window of MTCH.

[0191] As an embodiment, the first signaling configuration for receiving multicast services in the RRC inactive state includes: configuring a given threshold for at least one active multicast service session joined by the first node.

[0192] As an embodiment, the given threshold for each active multicast service session joined by the first node is the same.

[0193] As a sub-embodiment of this embodiment, the given threshold is applicable to each active multicast service session joined by the first node.

[0194] As an embodiment, the given threshold for the active multicast service session joined by the first node includes at least one of RSRP (Reference Signal Receiving Power) and RSRQ (Reference Signal Receiving Quality).

[0195] As an embodiment, the presence of multicastConfigInactive in the first signaling indicates that the first node is configured to receive multicast services in an RRC inactive state.

[0196] As an embodiment, any condition in the first condition set being met will trigger the sending of the first information.

[0197] As an embodiment, whether small data transmission is in progress refers to whether the process of small data transmission is in progress.

[0198] As an embodiment, the small data transmission starts from the initiation of the SDT and ends at the end of the SDT.

[0199] As an embodiment, when small data transmission is in progress, the network does not need to page the first node.

[0200] As an embodiment, the first condition set does not include receiving a paging call.

[0201] As an embodiment, the first condition set includes receiving a first system information block that triggers multicast service reception.

[0202] As an embodiment, the first system information block is SIB1 (System Information Block 1).

[0203] As an embodiment, the received first system information block for triggering multicast service reception includes: the received SIB1 unscheduled second system information block.

[0204] As an embodiment, the received first system information block for triggering multicast service reception includes: a SIB1 unscheduled second system information block received after cell selection or cell reselection.

[0205] As an embodiment, the received first system information block for triggering multicast service reception includes: SIB1 of the cell after cell selection or cell reselection does not schedule the second system information block.

[0206] As an embodiment, the second system information block includes the configuration of the multicast MCCH and / or MTCH required to be acquired in order to receive the MBS in the RRC inactive state.

[0207] As an embodiment, the second system information block is SIB22.

[0208] As an embodiment, the second system information block is SIB23.

[0209] As an embodiment, the second system information block is SIB24.

[0210] As an embodiment, the second system information block is SIB25.

[0211] As an embodiment, the second system information block is SIB26.

[0212] As an embodiment, the first condition set includes: the first system information block schedules the second system information block, the first system information block indicates that the broadcast status of the second system information block is not broadcast, and the first node fails to successfully request the second system information block.

[0213] As a sub-embodiment of this embodiment, the meaning of this embodiment is or includes: the first system information block obtained after cell selection or cell reselection schedules the second system information block, the first system information block indicates that the broadcast status of the second system information block is not broadcast, and the first node fails to successfully request the second system information block.

[0214] As a sub-embodiment of this embodiment, the meaning of this embodiment is or includes: failing to successfully obtain the second system information block within a given time.

[0215] As a sub-embodiment of this embodiment, the meaning of this embodiment is or includes: the first system information block indicates the given time.

[0216] As an embodiment, the first condition set includes that configuration of at least one active multicast service session joined by the first node is unavailable.

[0217] As an embodiment, the unavailability of the configuration of at least one active multicast service session joined by the first node includes: failure to obtain the configuration of at least one active multicast service session joined by the first node.

[0218] As a sub-embodiment of this embodiment, for example, the received system information block does not include the configuration of at least one active multicast service session joined by the first node.

[0219] As an embodiment, the unavailable configuration of at least one active multicast service session joined by the first node includes: the acquired configuration for the multicast service does not include the configuration of at least one active multicast service session joined by the first node.

[0220] As an embodiment, the unavailable configuration of at least one active multicast service session joined by the first node includes: the acquired configuration for the multicast service does not support the at least one active multicast service session joined by the first node.

[0221] As an embodiment, the configuration for the multicast service includes MBSMulticastConfiguration.

[0222] As an embodiment, the first node obtains the configuration for the multicast service by receiving a system information block.

[0223] As an embodiment, the first node obtains the configuration for the multicast service by receiving MCCH.

[0224] As an embodiment, the multicast service is MBS.

[0225] As an embodiment, the multicast service is multicast transmission of MBS.

[0226] As an embodiment, the multicast service session is an MBS session.

[0227] As an embodiment, MBS is a downlink service.

[0228] As an embodiment, the first condition set includes that the serving cell does not provide at least one active multicast service session joined by the first node to the RRC inactive state.

[0229] As an embodiment, the serving cell does not provide at least one active multicast service session for the first node to join to the RRC inactive state, including: the cell indicated by the first signaling that provides at least one active multicast service session for the first node to join does not include the cell selected after performing cell selection or cell reselection.

[0230] As an embodiment, the serving cell does not provide at least one active multicast service session joined by the first node to the RRC inactive state, including: the serving cell after cell selection or cell reselection does not provide at least one active multicast service session joined by the first node to the RRC inactive state.

[0231] As an embodiment, the serving cell does not provide at least one active multicast service session that the first node joins in the RRC inactive state, including: the serving cell does not support providing at least one active multicast service session that the first node joins in the RRC inactive state.

[0232] As an embodiment, the serving cell does not provide at least one active multicast service session joined by the first node in the RRC inactive state, including: the serving cell does not support receiving at least one active multicast service session joined by the first node in the RRC inactive state.

[0233] As an embodiment, the first condition set includes that a measurement of a serving cell is lower than a given threshold for at least one active multicast service session joined by the first node.

[0234] As an embodiment, the measurement of the serving cell being lower than a given threshold for at least one active multicast service session to which the first node joins includes: the measurement of the serving cell after cell selection or cell reselection being lower than a given threshold for at least one active multicast service session to which the first node joins.

[0235] As an embodiment, the measurement of the serving cell being lower than a given threshold for at least one active multicast service session joined by the first node includes: the measurement of the serving cell is at least one of RSRP and RSRQ of the serving cell.

[0236] As an embodiment, the measurement of the serving cell is lower than a given threshold for at least one active multicast service session to which the first node joins, which means that the measurement of the serving cell is lower than a given threshold for at least one active multicast service session to which the first node joins when the at least one multicast service session to which the first node joins is in an active state.

[0237] As an embodiment, the measurement of the service cell is lower than a given threshold for at least one active multicast service session joined by the first node, including: when all multicast service sessions joined by the first node are not in an active state, the first node does not detect whether the measurement of the service cell is lower than a given threshold for at least one active multicast service session joined by the first node.

[0238] As an embodiment, the benefits of the above method include: avoiding unnecessary RRC connection recovery, reducing signaling overhead, and saving more power.

[0239] As an embodiment, the detection of whether the first node's measurement of the serving cell is lower than a given threshold for at least one active multicast service session joined by the first node can occur after cell selection or cell reselection, or can occur during the process of receiving multicast services.

[0240] As an embodiment, the measurement of the serving cell being lower than a given threshold for at least one active multicast service session joined by the first node includes: the measurement of the serving cell is a channel quality of the serving cell.

[0241] As an embodiment, the first condition set includes: being unable to simultaneously receive multiple active multicast service sessions joined by the first node.

[0242] As a sub-embodiment of this embodiment, the benefits of this method include: being able to receive all active multicast service sessions that are joined as much as possible.

[0243] As an embodiment, the first condition set includes: failure to obtain MCCH.

[0244] As a sub-embodiment of this embodiment, the benefits of this method include: being able to continue to receive active multicast service sessions when MCCH acquisition fails.

[0245] As an embodiment, the first condition set includes: selecting an L2 U2N (UE to Network) relay.

[0246] As an embodiment, the first condition set includes: selecting an L2 U2N relay UE.

[0247] As a sub-embodiment of this embodiment, the benefits of this method include: avoiding the situation where a UE cannot receive an active multicast service session when an L2 U2N relay UE is selected.

[0248] As an embodiment, the sending of the first information depends on whether small data transmission is in progress, which means that: when small data transmission is in progress, the first information is sent through a dedicated control channel; when small data transmission is not in progress, the first information is sent through a public control channel, wherein the first information includes an RRC connection recovery request.

[0249] As an embodiment, sending the first information through a dedicated control channel includes: sending the first information using a dedicated control channel.

[0250] As an embodiment, sending the first information through a dedicated control channel includes: the first information occupies a dedicated control channel to send the first information.

[0251] As an embodiment, the first information is or belongs to an RRC message.

[0252] As an embodiment, the first information is or belongs to a domain or field in an RRC message.

[0253] As an embodiment, the first information is carried by a domain or field in an RRC message.

[0254] As an embodiment, when small data transmission is in progress, the first information is carried by a field in the RRC message.

[0255] As an embodiment, when small data transmission is not in progress, the first information is an RRC message.

[0256] As an embodiment, the dedicated control channel is a DCCH (dedicated control channel).

[0257] As an embodiment, the dedicated control channel is a logical channel.

[0258] As an embodiment, the benefits of sending the first information through a dedicated control channel include: better security, lower signaling overhead, lower transmission delay, and greater reliability.

[0259] As an embodiment, sending the first information through a common control channel includes: sending the first information using a common control channel.

[0260] As an embodiment, sending the first information through a public control channel includes: the first information occupies the public control channel to send the first information.

[0261] As an embodiment, the common control channel is CCCH (common control channel) or CCCH1 (common control channel 1).

[0262] As an embodiment, the common control channel is a logical channel.

[0263] As an embodiment, the benefits of sending the first information through a public control channel include: fewer restrictions on sending, greater flexibility, and the ability to send at any time.

[0264] As an embodiment, the RRC connection recovery request is an RRC message.

[0265] As an embodiment, the RRC connection resumption request is RRCResumeRequest.

[0266] As an embodiment, the RRC connection resumption request is RRCConnectionResumeRequest.

[0267] As an embodiment, the RRC connection resumption request is RRCResumeReq.

[0268] As an embodiment, the RRC connection recovery request is used to restore the RRC connection.

[0269] As an embodiment, the first node joins at least one multicast service.

[0270] As an embodiment, the first node joins at least one multicast service session.

[0271] As an embodiment, the first node joins at least one active multicast service session.

[0272] As an embodiment, the first information is used to request reception of a multicast service in an RRC connected state.

[0273] As an embodiment, the first information is used to explicitly request reception of multicast services in the RRC connected state.

[0274] As an embodiment, the first information is used to implicitly request reception of multicast services in the RRC connected state.

[0275] As an embodiment, when small data transmission is in progress, the first information includes UE assistance information.

[0276] As an embodiment, when small data transmission is in progress, the first information includes a partial field in the UE assistance information.

[0277] As an embodiment, the UE assistance information is an RRC message.

[0278] As an embodiment, the UE auxiliary information is an uplink message.

[0279] As an embodiment, the UE assistance information is UEAssistanceInformation.

[0280] As an embodiment, the UE assistance information includes assistance information provided by the UE.

[0281] As an embodiment, the UE assistance information is always sent using a dedicated control channel.

[0282] As an embodiment, the UE auxiliary information is sent using SRB1.

[0283] As an embodiment, in the RRC inactive state, the UE assistance information is always sent using SRB1.

[0284] As an embodiment, the UE auxiliary information is not sent using SRB0.

[0285] As an embodiment, when small data transmission is in progress, the first information occupies only one bit in the UE assistance information.

[0286] As an embodiment, when small data transmission is in progress, the first information is one bit of UE assistance information.

[0287] As an embodiment, the benefits of the above method include: saving signaling overhead.

[0288] As an embodiment, when small data transmission is in progress, the first information is mbsIndication in UE assistance information.

[0289] As an embodiment, when small data transmission is in progress, the first information is mbsRequestIndication in UE assistance information.

[0290] As an embodiment, when small data transmission is in progress, the first information is nonSDT-mbsIndication in UE assistance information.

[0291] As an embodiment, when small data transmission is in progress, the first information is mbsRequest in UE assistance information.

[0292] As an embodiment, when small data transmission is in progress, the first information is an indication in UE assistance information.

[0293] As an embodiment, when small data transmission is in progress, the first information is the nonSDT-DataIndication in the UE assistance information.

[0294] As an embodiment, when small data transmission is not in progress, any one condition in the first condition set is met to trigger the initiation of the RRC connection recovery process.

[0295] As a sub-embodiment of this embodiment, the first information is or includes an RRC message in the RRC connection recovery process.

[0296] As a sub-embodiment of this embodiment, the first information includes an RRC recovery request message in the RRC connection recovery process.

[0297] As a sub-embodiment of this embodiment, the RRC connection recovery process initiated is for MBS reception.

[0298] As an embodiment, when small data transmission is in progress, the first information is sent via SRB1; when small data transmission is not in progress, the first information is sent via SRB0.

[0299] As an embodiment, although the SRB1 and the SRB0 are both signaling radio bearers, their functions are completely different.

[0300] As an embodiment, the SRB0 is for an RRC message using CCCH and / or CCCH1.

[0301] As an embodiment, the configuration of SRB0 is fixed.

[0302] As an embodiment, the SRB0 does not use encryption and integrity protection.

[0303] As an embodiment, SRB1 is used for RRC messages and NAS messages using the DCCH logical channel.

[0304] As a sub-embodiment of this embodiment, the NAS message transmitted on SRB1 is generally a NAS message before SRB2 is established.

[0305] As an example, SRB1 generally uses encryption and integrity protection.

[0306] As an embodiment, SRB1 is network configured.

[0307] Example 2

[0308] Example 2 illustrates a schematic diagram of a network architecture according to the present application, as shown in FIG2 .

[0309] FIG2 illustrates a diagram of a network architecture 200 for 5G NR, LTE (Long-Term Evolution), and LTE-A (Long-Term Evolution Advanced) systems. The 5G NR or LTE network architecture 200 may be referred to as a 5G System (5GS) / EPS (Evolved Packet System) 200 or some other suitable terminology. The 5GS / EPS 200 may include one or more UEs (User Equipment) 201, an NG-RAN (Next Generation Radio Access Network) 202, a 5G Core Network (5GC) / EPC (Evolved Packet Core) 210, a Home Subscriber Server (HSS) / UDM (Unified Data Management) 220, and Internet services 230. The 5GS / EPS may interconnect with other access networks, but these entities / interfaces are not shown for simplicity. As shown, the 5GS / EPS provides packet-switched services, but those skilled in the art will readily appreciate that the various concepts presented throughout this disclosure can be extended to networks providing circuit-switched services or other cellular networks. The NG-RAN includes an NR Node B (gNB) 203 and other gNBs 204. The gNB 203 provides user and control plane protocol termination towards the UE 201. The gNB 203 can be connected to other gNBs 204 via an Xn interface (e.g., backhaul). The gNB 203 may also be referred to as a base station, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), TRP (transmitter receive node), or some other appropriate terminology. The gNB 203 provides an access point to the 5GC / EPC 210 for the UE 201. Examples of UE 201 include a cellular phone, a smartphone, a Session Initiation Protocol (SIP) phone, a laptop computer, a personal digital assistant (PDA), a satellite radio, non-terrestrial base station communications, satellite mobile communications, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a drone, an aircraft, a narrowband Internet of Things device, a machine type communication device, a land vehicle, an automobile, a wearable device, or any other similarly functional device. Those skilled in the art may also refer to UE 201 as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.The gNB 203 connects to the 5GC / EPC 210 via the S1 / NG interface. The 5GC / EPC 210 includes the MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MMEs / AMFs / SMFs 214, the S-GW (Service Gateway) / UPF (User Plane Function) 212, and the P-GW (Packet Data Network Gateway) / UPF 213. The MME / AMF / SMF 211 is the control node that handles signaling between the UE 201 and the 5GC / EPC 210. Generally, the MME / AMF / SMF 211 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the S-GW / UPF 212, which itself is connected to the P-GW / UPF 213. The P-GW provides UE IP address allocation and other functions. The P-GW / UPF 213 is connected to the Internet Services 230. The Internet Services 230 includes the operator's corresponding Internet Protocol services, which may include the Internet, Intranet, IMS (IP Multimedia Subsystem), and packet-switched streaming services.

[0310] As an embodiment, the first node in this application is UE201.

[0311] As an embodiment, the base station of the second node in this application is gNB203.

[0312] As an embodiment, the wireless link from the UE201 to the NR node B is an uplink.

[0313] As an embodiment, the wireless link from the NR Node B to the UE 201 is a downlink.

[0314] As an embodiment, the UE 201 includes a mobile phone.

[0315] As an embodiment, the UE 201 is a vehicle including a car.

[0316] As an embodiment, the gNB203 is a macrocellular base station.

[0317] As an embodiment, the gNB203 is a micro cell base station.

[0318] As an embodiment, the gNB203 is a pico cell base station.

[0319] As an embodiment, the gNB203 is a flying platform device.

[0320] As an embodiment, the gNB203 is a satellite device.

[0321] Example 3

[0322] Embodiment 3 illustrates a schematic diagram of an embodiment of a radio protocol architecture for a user plane and a control plane according to the present application, as shown in FIG3 . FIG3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300. FIG3 illustrates the radio protocol architecture of the control plane 300 for a first node (UE, gNB) and a second node (gNB, UE), or between two UEs, using three layers: Layer 1, Layer 2, and Layer 3. Layer 1 (L1 layer) is the lowest layer and implements various PHY (physical layer) signal processing functions. The L1 layer will be referred to herein as PHY 301. Layer 2 (L2 layer) 305 is above PHY 301 and is responsible for the link between the first and second nodes, as well as between two UEs, via PHY 301. The L2 layer 305 includes a MAC (Medium Access Control) sublayer 302, an RLC (Radio Link Control) sublayer 303, and a PDCP (Packet Data Convergence Protocol) sublayer 304, which terminate at the second node. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security by encrypting data packets, and provides support for inter-zone mobility of the first node between the second node. The RLC sublayer 303 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out-of-order reception due to HARQ. The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating various radio resources (e.g., resource blocks) in a cell between the first nodes. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control) sublayer 306 in Layer 3 (L3) of the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and configuring lower layers using RRC signaling between the second node and the first node. The PC5-S (PC5 Signaling Protocol) sublayer 307 is responsible for processing the signaling protocol of the PC5 interface. The radio protocol architecture of the user plane 350 includes Layer 1 (L1) and Layer 2 (L2). The radio protocol architecture for the first and second nodes in the user plane 350 is generally the same as the corresponding layers and sublayers in the control plane 300, including the physical layer 351, the PDCP sublayer 354 in the L2 layer 355, the RLC sublayer 353 in the L2 layer 355, and the MAC sublayer 352 in the L2 layer 355. However, the PDCP sublayer 354 also provides header compression for upper layer packets to reduce radio transmission overhead.The L2 layer 355 in the user plane 350 also includes the SDAP (Service Data Adaptation Protocol) sublayer 356, which is responsible for mapping QoS flows and data radio bearers (DRBs) to support service diversity. SRBs can be considered services or interfaces provided by the PDCP layer to higher layers, such as the RRC layer. In the NR system, SRBs include SRB1, SRB2, and SRB3, each used to transmit different types of control signaling. SRBs are bearers between the UE and the access network, used to transmit control signaling, including RRC signaling, between the UE and the access network. SRB1 is of special significance to the UE. After each UE establishes an RRC connection, it will have SRB1 for transmitting RRC signaling. Most signaling is transmitted over SRB1. If SRB1 is interrupted or unavailable, the UE must perform RRC re-establishment. SRB2 is generally used only to transmit NAS signaling or security-related signaling. The UE does not need to configure SRB3. Except for emergency services, the UE must establish an RRC connection with the network for subsequent communication. Although not shown, the first node may have several upper layers above the L2 layer 355. This includes a network layer (e.g., an IP layer) that terminates at the P-GW on the network side and an application layer that terminates at the other end of the connection (e.g., a remote UE, a server, etc.).

[0323] As an embodiment, the wireless protocol architecture in FIG3 is applicable to the first node in this application.

[0324] As an embodiment, the wireless protocol architecture in FIG3 is applicable to the second node in this application.

[0325] As an embodiment, the first signaling in this application is generated in RRC306.

[0326] As an embodiment, the first information in this application is generated in RRC306.

[0327] As an embodiment, the second information in this application is generated in RRC306.

[0328] As an embodiment, the first system information block in the present application is generated in RRC306.

[0329] As an embodiment, the second system information block in the present application is generated in RRC306.

[0330] As an embodiment, the signaling on the MCCH in this application is generated in RRC306.

[0331] Example 4

[0332] Embodiment 4 shows a schematic diagram of a first communication device and a second communication device according to an embodiment of the present application, as shown in Figure 4. Figure 4 is a block diagram of a first communication device 450 and a second communication device 410 communicating with each other in an access network.

[0333] The first communication device 450 includes a controller / processor 459, a memory 460, a data source 467, a transmit processor 468, a receive processor 456, and optionally may also include a multi-antenna transmit processor 457, a multi-antenna receive processor 458, a transmitter / receiver 454 and an antenna 452.

[0334] The second communication device 410 includes a controller / processor 475 , a memory 476 , a receive processor 470 , a transmit processor 416 , and optionally may also include a multi-antenna receive processor 472 , a multi-antenna transmit processor 471 , a transmitter / receiver 418 and an antenna 420 .

[0335] During transmission from the second communication device 410 to the first communication device 450, upper layer data packets from the core network are provided to the controller / processor 475 at the second communication device 410. The controller / processor 475 implements Layer 2 (L2) functionality. During transmission from the second communication device 410 to the first communication device 450, the controller / processor 475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation to the first communication device 450 based on various priority metrics. The controller / processor 475 is also responsible for retransmission of lost packets and signaling to the first communication device 450. The transmit processor 416 and the multi-antenna transmit processor 471 implement various signal processing functions for the Layer 1 (i.e., physical layer). The transmit processor 416 implements coding and interleaving to facilitate forward error correction (FEC) at the second communication device 410, as well as mapping of signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), and M-quadrature amplitude modulation (M-QAM)). The multi-antenna transmit processor 471 performs digital spatial precoding, including codebook-based and non-codebook-based precoding, and beamforming on the coded and modulated symbols to generate one or more spatial streams. The transmit processor 416 then maps each spatial stream to a subcarrier, multiplexes it with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then uses an inverse fast Fourier transform (IFFT) to generate a physical channel carrying the time-domain multicarrier symbol stream. The multi-antenna transmit processor 471 then performs transmit analog precoding / beamforming operations on the time-domain multicarrier symbol stream. Each transmitter 418 converts the baseband multi-carrier symbol stream provided by the multi-antenna transmit processor 471 into a radio frequency stream, and then provides it to a different antenna 420.

[0336] During transmission from the second communication device 410 to the first communication device 450, at the first communication device 450, each receiver 454 receives a signal via its corresponding antenna 452. Each receiver 454 recovers the information modulated onto the RF carrier and converts the RF stream into a baseband multi-carrier symbol stream, which is provided to the receive processor 456. The receive processor 456 and the multi-antenna receive processor 458 implement various L1 signal processing functions. The multi-antenna receive processor 458 performs receive analog precoding / beamforming operations on the baseband multi-carrier symbol stream from the receiver 454. The receive processor 456 converts the baseband multi-carrier symbol stream, after the receive analog precoding / beamforming operations, from the time domain to the frequency domain using a fast Fourier transform (FFT). In the frequency domain, the receive processor 456 demultiplexes the physical layer data signal and reference signal, where the reference signal is used for channel estimation. The data signal undergoes multi-antenna detection in the multi-antenna receive processor 458 to recover any spatial streams destined for the first communication device 450. The symbols on each spatial stream are demodulated and recovered in the receive processor 456, and soft decisions are generated. The receive processor 456 then decodes and deinterleaves the soft decisions to recover the upper layer data and control signals transmitted by the second communication device 410 on the physical channel. The upper layer data and control signals are then provided to the controller / processor 459. The controller / processor 459 implements the functions of the L2 layer. The controller / processor 459 may be associated with a memory 460 that stores program code and data. The memory 460 may be referred to as a computer-readable medium. During transmission from the second communication device 410 to the second communication device 450, the controller / processor 459 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover upper layer data packets from the core network. The upper layer data packets are then provided to all protocol layers above the L2 layer. Various control signals may also be provided to the L3 layer for L3 processing.

[0337] During transmission from the first communication device 450 to the second communication device 410, a data source 467 is used at the first communication device 450 to provide upper layer data packets to the controller / processor 459. The data source 467 represents all protocol layers above the L2 layer. Similar to the transmission functionality at the second communication device 410 described in the transmission from the second communication device 410 to the first communication device 450, the controller / processor 459 implements header compression, encryption, packet segmentation and reordering, and multiplexing between logical and transport channels based on radio resource allocation, implementing L2 layer functions for the user plane and control plane. The controller / processor 459 is also responsible for retransmission of lost packets and signaling to the second communication device 410. The transmit processor 468 performs modulation mapping and channel coding, while the multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based and non-codebook-based precoding, and beamforming. The transmit processor 468 then modulates the resulting spatial stream into a multi-carrier / single-carrier symbol stream. After analog precoding and beamforming operations in the multi-antenna transmit processor 457, the stream is provided to different antennas 452 via the transmitter 454. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a RF symbol stream before providing it to the antenna 452.

[0338] During transmission from the first communications device 450 to the second communications device 410, the functionality at the second communications device 410 is similar to the reception functionality at the first communications device 450 described for transmission from the second communications device 410 to the first communications device 450. Each receiver 418 receives RF signals via its corresponding antenna 420, converts the received RF signals into baseband signals, and provides the baseband signals to a multi-antenna receive processor 472 and a receive processor 470. The receive processor 470 and the multi-antenna receive processor 472 collectively implement L1 layer functionality. A controller / processor 475 implements L2 layer functionality. The controller / processor 475 may be associated with a memory 476 storing program codes and data. The memory 476 may be referred to as a computer-readable medium. During transmission from the first communications device 450 to the second communications device 410, the controller / processor 475 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover upper layer data packets from the UE 450. Upper layer packets from controller / processor 475 may be provided to the core network.

[0339] As an embodiment, the first communication device 450 device includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor, and the first communication device 450 device at least: receives a first signaling, the first signaling is configured to transmit small data in an RRC inactive state; the first signaling is configured to receive a multicast service in an RRC inactive state; in the RRC inactive state, as a response to any condition in a first condition set being met, sends a first message; the sending of the first message depends on whether small data transmission is in progress; wherein the first condition set includes The method includes receiving a first system information block that triggers multicast service reception, the configuration of at least one active multicast service session joined by the first node is unavailable, the serving cell does not provide at least one active multicast service session joined by the first node to the RRC inactive state, and the measurement of the serving cell is lower than at least one of the given thresholds for at least one active multicast service session joined by the first node; the sending of the first information depends on whether small data transmission is in progress, including: when small data transmission is in progress, sending the first information through a dedicated control channel; when small data transmission is not in progress, sending the first information through a common control channel, wherein the first information includes an RRC connection recovery request.

[0340] As an embodiment, the first communication device 450 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generating an action when executed by at least one processor, the action including: receiving a first signaling, the first signaling configuring a small data transmission in an RRC inactive state; the first signaling configuring receiving a multicast service in an RRC inactive state; in the RRC inactive state, sending a first information in response to any condition in a first condition set being met; the sending of the first information depends on whether the small data transmission is in progress; wherein the first condition set includes receiving a first system information block that triggers multicast service reception, the configuration of at least one active multicast service session joined by the first node is unavailable, the serving cell does not provide the at least one active multicast service session joined by the first node to the RRC inactive state, and the measurement of the serving cell is lower than at least one of the given thresholds for the at least one active multicast service session joined by the first node; the sending of the first information depends on whether the small data transmission is in progress, including: when the small data transmission is in progress, sending the first information through a dedicated control channel; when the small data transmission is not in progress, sending the first information through a common control channel, wherein the first information includes an RRC connection recovery request.

[0341] As an embodiment, the first communication device 450 corresponds to the first node in this application.

[0342] As an embodiment, the second communication device 410 corresponds to the second node in this application.

[0343] As an embodiment, the first communication device 450 is a UE.

[0344] As an embodiment, the first communication device 450 is a vehicle-mounted terminal.

[0345] As an embodiment, the first communication device 450 is a mobile phone.

[0346] As an embodiment, the second communication device 450 is a relay.

[0347] As an embodiment, the second communication device 410 is a satellite.

[0348] As an embodiment, the second communication device 410 is an aircraft.

[0349] As an embodiment, the second communication device 410 is a base station.

[0350] As an embodiment, the receiver 454 (including the antenna 452 ), the receiving processor 456 and the controller / processor 459 are used to receive the first signaling in this application.

[0351] As an embodiment, the receiver 454 (including the antenna 452 ), the receiving processor 456 and the controller / processor 459 are used to receive the first system information block in this application.

[0352] As an embodiment, the receiver 454 (including the antenna 452 ), the receiving processor 456 and the controller / processor 459 are used to receive the second system information block in the present application.

[0353] As an embodiment, the receiver 454 (including the antenna 452), the receiving processor 456 and the controller / processor 459 are used to receive the MCCH in this application.

[0354] As an embodiment, the transmitter 454 (including the antenna 452), the transmit processor 468 and the controller / processor 459 are used to transmit the first information in the present application.

[0355] As an embodiment, the transmitter 454 (including the antenna 452), the transmit processor 468 and the controller / processor 459 are used to transmit the second information in the present application.

[0356] Example 5

[0357] Example 5 illustrates a wireless signal transmission flow chart according to an embodiment of the present application, as shown in Figure 5. In Figure 5, U01 corresponds to the first node of the present application. It is particularly noted that the order in this example does not limit the signal transmission order and implementation order in the present application, and the steps in F51 are optional.

[0358] For the first node U01, the first signaling is received in step S5101; the first information is sent in step S5102; and the second information is sent in step S5103.

[0359] For the second node U02, the first signaling is sent in step S5201; the first information is received in step S5202; and the second information is received in step S5203.

[0360] In embodiment 5, the first signaling configuration is for small data transmission in an RRC inactive state; the first signaling configuration is for receiving multicast services in an RRC inactive state; the sending of the first information depends on whether small data transmission is in progress; any condition in the first condition set is met to trigger the sending of the first information; the first condition set includes receiving a first system information block that triggers multicast service reception, the configuration of at least one active multicast service session joined by the first node is unavailable, the serving cell does not provide at least one active multicast service session joined by the first node to the RRC inactive state, and the measurement of the serving cell is lower than at least one of the given thresholds for at least one active multicast service session joined by the first node; the sending of the first information depends on whether small data transmission is in progress, including: when small data transmission is in progress, sending the first information through a dedicated control channel; when small data transmission is not in progress, sending the first information through a common control channel, wherein the first information includes an RRC connection recovery request.

[0361] As an embodiment, the first node U01 sends the first information in an RRC inactive state.

[0362] As an embodiment, the first node U01 receives the first signaling in an RRC connected state.

[0363] As an embodiment, the second node U02 is the base station corresponding to the SpCell of the first node U01.

[0364] As an embodiment, the second node U02 is the PCell of the first node U01 or the base station to which the PCell of the first node U01 belongs.

[0365] As an embodiment, the second node U02 is the PCell when the first node U01 is in the RRC connected state or the base station to which the PCell when the first node U01 is in the RRC connected state belongs.

[0366] As an embodiment, Figure 5 shows that the sender of the first signaling and the receiver of the first information are both the second node U02, but the method proposed in this application is also applicable to the scenario where the sender of the first signaling and the receiver of the first information are different.

[0367] As a sub-embodiment of this embodiment, when the first node U01 has moved to another cell after receiving the first signaling, that is, cell selection or cell reselection occurs, the recipient of the first information is the other cell.

[0368] As a sub-embodiment of this embodiment, similarly, the method proposed in this application is also applicable to scenarios where the sender of the first signaling is different from the receiver of the second signaling.

[0369] As an embodiment, step S5101 precedes step S5102.

[0370] As an embodiment, there is no obvious order relationship between step S5102 and step S5103.

[0371] As an embodiment, step S5101 precedes step S5103.

[0372] As an embodiment, the first node U01 is in different RRC states when receiving the first signaling and sending the first information.

[0373] As an embodiment, the first node U01 receives at least the same active multicast service session before entering the RRC inactive state and after entering the RRC inactive state.

[0374] As an embodiment, the first node U01 does not receive any active multicast service session before entering the RRC inactive state.

[0375] As an embodiment, the execution of the first signaling includes performing cell selection.

[0376] As an embodiment, after performing cell selection or cell reselection, the first node U01 needs to read first system information, where the first system information schedules second system information, and the second system information indicates the configuration for receiving multicast services in an RRC inactive state.

[0377] As an embodiment, the first node U01 needs to read information on the MCCH after performing cell selection or cell reselection.

[0378] As an embodiment, the first node U01 is in an RRC inactive state and wants to receive a multicast service.

[0379] As a sub-embodiment of this embodiment, when the first information is sent.

[0380] As a sub-embodiment of this embodiment, before the first information is sent.

[0381] As an embodiment, the first node U01 is in an RRC inactive state and wants to receive a multicast service session.

[0382] As a sub-embodiment of this embodiment, when the first information is sent.

[0383] As a sub-embodiment of this embodiment, before the first information is sent.

[0384] As an embodiment, in the RRC inactive state, the first node U01 has at least one active multicast service session.

[0385] As a sub-embodiment of this embodiment, when the first information is sent.

[0386] As a sub-embodiment of this embodiment, before the first information is sent.

[0387] As an embodiment, in the RRC inactive state, at least one multicast service session of the first node U01 is active or becomes active.

[0388] As a sub-embodiment of this embodiment, when the first information is sent.

[0389] As a sub-embodiment of this embodiment, before the first information is sent.

[0390] As an embodiment, in the RRC inactive state, at least one multicast service session of the first node U01 is about to become active.

[0391] As a sub-embodiment of this embodiment, when the first information is sent.

[0392] As a sub-embodiment of this embodiment, before the first information is sent.

[0393] As an embodiment, in the RRC inactive state, at least one multicast service session of the first node U01 starts or is about to start.

[0394] As a sub-embodiment of this embodiment, when the first information is sent.

[0395] As a sub-embodiment of this embodiment, before the first information is sent.

[0396] As an embodiment, the first node U01 is in an RRC inactive state and is receiving at least one multicast service session.

[0397] As a sub-embodiment of this embodiment, when the first information is sent.

[0398] As a sub-embodiment of this embodiment, before the first information is sent.

[0399] As an embodiment, before receiving the first signaling, the first node U01 sends a first indication indicating whether to prefer receiving multicast services in the RRC inactive state.

[0400] As an embodiment, before receiving the first signaling, the first node U01 sends a first indication indicating a preference for receiving multicast services in an RRC inactive state.

[0401] As an embodiment, the first information triggers RRC recovery signaling.

[0402] As an embodiment, the first information triggers the second node U02 to send RRC recovery signaling.

[0403] As an embodiment, the network or the second node U02 determines whether to send RRC recovery signaling based on the first information.

[0404] As an embodiment, the RRC recovery signaling instructs the first node U01 to enter the RRC connected state.

[0405] As an embodiment, the RRC recovery signaling is configured to receive multicast services in the RRC connected state.

[0406] As an embodiment, the second information indicates the arrival of at least one of data and signaling mapped to a radio bearer other than a radio bearer configured for small data transmission.

[0407] As a sub-embodiment of this embodiment, small data transmission is in progress.

[0408] As an embodiment, the second information is sent via a dedicated control channel.

[0409] As a sub-embodiment of this embodiment, small data transmission is in progress.

[0410] As a sub-embodiment of this embodiment, the dedicated control channel is DCCH.

[0411] As an embodiment, the period during which the small data transmission is in progress corresponds to the running period of the timer T319a.

[0412] As an embodiment, the second information is sent via UE auxiliary information.

[0413] As an embodiment, when small data transmission is in progress, the first information and the second information are transmitted by the UE using different fields in the UE assistance information.

[0414] As an embodiment, when small data transmission is in progress, the first node U01 may send the first information and the second information through UE assistance information.

[0415] As an embodiment, the first information and the second information are used to determine whether to send RRC recovery signaling.

[0416] As an embodiment, at least one of the data and signaling mapped to a radio bearer other than a radio bearer configured for small data transmission is uplink.

[0417] As an embodiment, the first information and the second information occupy different fields in the UE auxiliary information.

[0418] As an embodiment, the first node U01 enters an RRC inactive state along with the execution of the first signaling.

[0419] As a sub-embodiment of this embodiment, the meaning of this embodiment is: the first signaling triggers the first node U01 to enter the RRC inactive state.

[0420] As a sub-embodiment of this embodiment, the meaning of this embodiment is that the execution of the first signaling includes entering the RRC inactive state.

[0421] Example 6

[0422] Embodiment 6 illustrates a schematic diagram of a method in which the first information according to an embodiment of the present application is used to request reception of a multicast service in an RRC connected state, as shown in FIG6 .

[0423] As an embodiment, the meaning that the first information is used to request to receive multicast services in the RRC connection state includes: the first information is used to trigger the network to instruct the first node to restore the RRC connection, and after the RRC connection is restored, the first node enters the RRC connection state.

[0424] As an embodiment, the meaning that the first information is used to request to receive multicast services in the RRC connection state includes: the first information is used to trigger the network to instruct the first node to restore the RRC connection, the signaling for restoring the RRC connection includes the configuration of receiving multicast services in the RRC connection state, and the first node enters the RRC connection state.

[0425] As an embodiment, the meaning that the first information is used to trigger the network to instruct the first node to restore the RRC connection includes: the network can instruct the first node to restore the RRC connection after receiving the first information.

[0426] As an embodiment, the network instructs the first node to resume the RRC connection by sending RRC resumption signaling.

[0427] As an embodiment, the network saves the context in which the first node is configured to receive multicast services, so the network can determine which multicast services the first node needs to continue to receive in the RRC connected state.

[0428] As a sub-embodiment of this embodiment, the network refers to an access network.

[0429] As an embodiment, the network may obtain from the core network which multicast service sessions the first node has joined, so that the network may determine which multicast services the first node needs to continue to receive in the RRC connected state.

[0430] As a sub-embodiment of this embodiment, the network refers to an access network.

[0431] As an embodiment, the meaning that the first information is used to request receiving multicast services in the RRC connection state includes: the first information is sent in order to receive multicast services in the RRC connection state.

[0432] As an embodiment, when small data transmission is not performed, the first information includes an RRC recovery request, and the RRC recovery request triggers RRC recovery signaling.

[0433] As an embodiment, when small data transmission is not performed, the first information includes an RRC recovery request, the RRC recovery request triggers RRC recovery signaling, and after receiving the RRC recovery signaling, the first node enters the RRC connection state.

[0434] As an embodiment, the RRC recovery signaling includes configuration for receiving multicast services in the RRC connected state.

[0435] As an embodiment, when small data transmission is in progress, the first information is sent via UE assistance information, and the first information is used to trigger the network to instruct the first node to resume the RRC connection.

[0436] As an embodiment, the first information is sent in order to continue receiving the multicast service.

[0437] As an embodiment, the meaning that the first information is used to request reception of multicast services in the RRC connected state includes: the first information includes an RRC recovery request, and the RRC recovery process initiated by the RRC recovery request is for reception of multicast services.

[0438] As a sub-embodiment of this embodiment, small data transmission is not in progress.

[0439] As an embodiment, when small data transmission is in progress, sending the first information helps the network to instruct the first node to resume the RRC connection, thereby receiving the multicast service in the RRC connection state.

[0440] Example 7

[0441] Embodiment 7 illustrates a schematic diagram of the second information indicating the arrival of at least one of data and signaling mapped to a radio bearer other than a radio bearer configured for small data transmission according to an embodiment of the present application, as shown in FIG7 .

[0442] As an embodiment, the arrival of data at the first node refers to that higher-layer data and signaling of the first node arrive at the access layer.

[0443] As an embodiment, the arrival of data at the first node means that there is uplink data and signaling to be sent.

[0444] As an embodiment, the first radio bearer is any radio bearer other than a radio bearer configured for small data transmission.

[0445] As an embodiment, the first radio bearer is not any radio bearer configured for small data transmission.

[0446] As an embodiment, at least one of the data and signaling mapped to a radio bearer other than a radio bearer configured for small data transmission is at least one of the data and signaling mapped to the first radio bearer.

[0447] As an embodiment, the mapping of data and signaling to which radio bearer is performed by network configuration or a predetermined method.

[0448] As an embodiment, the data or signaling mapped to the first radio bearer cannot be sent through the small data transmission process.

[0449] As a sub-embodiment of this embodiment, unless there is a new configuration.

[0450] As an embodiment, when the first wireless bearer is a data wireless bearer, the arrival of at least one of the data and signaling mapped to a wireless bearer other than the wireless bearer configured for small data transmission refers to the arrival of data mapped to a wireless bearer other than the wireless bearer configured for small data transmission.

[0451] As an embodiment, when the first wireless bearer is a signaling wireless bearer, the arrival of at least one of the data and signaling mapped to a wireless bearer other than the wireless bearer configured for small data transmission refers to the arrival of signaling mapped to a wireless bearer other than the wireless bearer configured for small data transmission.

[0452] As an embodiment, the second information explicitly indicates the arrival of at least one of data and signaling mapped to a radio bearer other than a radio bearer configured for small data transmission.

[0453] As an embodiment, after receiving the second information, the network may configure resources for transmitting at least one of data and signaling mapped to a radio bearer other than a radio bearer configured for small data transmission.

[0454] As an embodiment, receiving multicast services in the RRC connected state is more conducive to ensuring reception quality. For example, a PTP (point to point) transmission method can be used, a richer retransmission mechanism can be used, and more resources can be allocated.

[0455] As an embodiment, receiving multicast services in the RRC inactive state is more power-saving.

[0456] Example 8

[0457] Embodiment 8 illustrates a structural block diagram of a processing device in a first node according to an embodiment of the present application, as shown in FIG8 . In FIG8 , the processing device 800 in the first node includes a first receiver 801 and a first transmitter 802 .

[0458] In embodiment 8, a first receiver 801 receives a first signaling, wherein the first signaling configures small data transmission in an RRC inactive state; the first signaling configures receiving a multicast service in an RRC inactive state;

[0459] The first transmitter 802, in an RRC inactive state, sends first information in response to any condition in a first condition set being met; the sending of the first information depends on whether small data transmission is in progress;

[0460] Among them, the first condition set includes receiving a first system information block that triggers multicast service reception, the configuration of at least one active multicast service session joined by the first node is unavailable, the serving cell does not provide at least one active multicast service session joined by the first node to the RRC inactive state, and the measurement of the serving cell is lower than at least one of the given thresholds for at least one active multicast service session joined by the first node; the sending of the first information depends on whether small data transmission is in progress, including: when small data transmission is in progress, sending the first information through a dedicated control channel; when small data transmission is not in progress, sending the first information through a common control channel, wherein the first information includes an RRC connection recovery request.

[0461] As an embodiment, the first information is used to request reception of a multicast service in an RRC connected state.

[0462] As an embodiment, when small data transmission is in progress, the first information includes UE assistance information.

[0463] As an embodiment, when small data transmission is not in progress, any one condition in the first condition set is met to trigger the initiation of the RRC connection recovery process.

[0464] As an embodiment, the configuration of at least one active multicast service session joined by the first node is unavailable, which means that the configuration of at least one active multicast service session joined by the first node is unavailable in the cell after cell selection or reselection; the serving cell does not provide at least one active multicast service session joined by the first node to the RRC inactive state, which means that the cell after cell selection or reselection does not provide at least one active multicast service session joined by the first node to the RRC inactive state.

[0465] As an embodiment, when small data transmission is in progress, the first information is sent via SRB1; when small data transmission is not in progress, the first information is sent via SRB0.

[0466] As an embodiment, when small data transmission is in progress, the first information occupies only one bit in the UE assistance information.

[0467] As an embodiment, the first node enters an RRC inactive state along with the execution of the first signaling.

[0468] As an embodiment, second information is sent, where the second information indicates arrival of at least one of data and signaling mapped to a radio bearer other than a radio bearer configured for small data transmission; the second information is sent via a dedicated control channel;

[0469] Among them, small data transmission is ongoing.

[0470] As an embodiment, the first condition set includes: being unable to simultaneously receive multiple active multicast service sessions joined by the first node.

[0471] As an embodiment, the first condition set includes: failure to obtain MCCH.

[0472] As an embodiment, the first condition set includes: L2 U2N relay UE selection occurs.

[0473] As an embodiment, the first condition set includes: expiration of a first timer.

[0474] As an embodiment, the first node is a user equipment (UE).

[0475] As an embodiment, the first node is a terminal that supports a large delay difference.

[0476] As an embodiment, the first node is a terminal supporting NTN.

[0477] As an embodiment, the first node is an aircraft or a ship.

[0478] As an embodiment, the first node is a mobile phone or a vehicle-mounted terminal.

[0479] As an embodiment, the first node is a terminal supporting MUSIM.

[0480] As an embodiment, the first node is an Internet of Things terminal or an industrial Internet of Things terminal.

[0481] As an embodiment, the first node is a device that supports low-latency and high-reliability transmission.

[0482] As an embodiment, the first receiver 801 includes at least one of the antenna 452, receiver 454, receiving processor 456, multi-antenna receiving processor 458, controller / processor 459, memory 460, or data source 467 in Example 4.

[0483] As an embodiment, the first transmitter 802 includes at least one of the antenna 452, transmitter 454, transmit processor 468, multi-antenna transmit processor 457, controller / processor 459, memory 460, or data source 467 in Example 4.

[0484] Those skilled in the art will appreciate that all or part of the steps in the above method can be completed by instructing relevant hardware through a program, and the program can be stored in a computer-readable storage medium, such as a read-only memory, a hard disk or an optical disk. Optionally, all or part of the steps in the above embodiment can also be implemented using one or more integrated circuits. Accordingly, each module unit in the above embodiment can be implemented in the form of hardware or in the form of a software functional module. The present application is not limited to any specific form of combination of software and hardware. The user equipment, terminal and UE in the present application include but are not limited to drones, communication modules on drones, remote-controlled aircraft, aircraft, small aircraft, mobile phones, tablets, notebooks, vehicle-mounted communication equipment, wireless sensors, network cards, Internet of Things terminals, RFID terminals, NB-IoT terminals, MTC (Machine Type Communication) terminals, eMTC (enhanced MTC) terminals, data cards, network cards, vehicle-mounted communication equipment, low-cost mobile phones, low-cost tablets, satellite communication equipment, ship communication equipment, NTN user equipment and other wireless communication devices. The base stations or system equipment in this application include but are not limited to macrocell base stations, microcell base stations, home base stations, relay base stations, gNB (NR node B) NR node B, TRP (Transmitter Receiver Point, sending and receiving nodes), NTN base stations, satellite equipment, flight platform equipment and other wireless communication equipment.

[0485] The present invention may be implemented in other specific forms without departing from its core or essential characteristics. Therefore, the presently disclosed embodiments should be considered in all respects as illustrative and not restrictive. The scope of the invention is determined by the appended claims, not the foregoing description, and all modifications that come within the meaning and range of equivalents are intended to be embraced therein.

Claims

1. A first node used for multicast services and small data transmission, wherein: include: A first receiver receives a first signaling, wherein the first signaling configures small data transmission in an RRC inactive state; The first signaling configuration receives a multicast service in an RRC inactive state; The first transmitter, in an RRC inactive state, sends first information as a response to any condition in a first condition set being met; the sending of the first information depends on whether a small data transmission is in progress; The first condition set includes receiving a first system information block that triggers multicast service reception, the configuration of at least one active multicast service session joined by the first node is unavailable, the serving cell does not provide at least one active multicast service session joined by the first node to the RRC inactive state, and the measurement of the serving cell is lower than at least one of the given thresholds for at least one active multicast service session joined by the first node; the sending of the first information depends on whether small data transmission is in progress, including: when small data transmission is in progress, sending the first information through a dedicated control channel; when small data transmission is not in progress, sending the first information through a common control channel, wherein the first information includes an RRC connection recovery request.

2. The first node according to claim 1, characterized in that: The first information is used to request to receive a multicast service in an RRC connected state.

3. The first node according to claim 1 or 2, characterized in that: When small data transmission is in progress, the first information includes UE assistance information.

4. The first node according to any one of claims 1 to 3, characterized in that: When small data transmission is not in progress, any condition in the first condition set is met to trigger the initiation of the RRC connection recovery process.

5. The first node according to any one of claims 1 to 4, characterized in that: The configuration of at least one active multicast service session joined by the first node is unavailable, which means that the configuration of at least one active multicast service session joined by the first node is unavailable in the cell after cell selection or reselection; the serving cell does not provide at least one active multicast service session joined by the first node to the RRC inactive state, which means that the cell after cell selection or reselection does not provide at least one active multicast service session joined by the first node to the RRC inactive state.

6. The first node according to any one of claims 1 to 5, characterized in that: When small data transmission is in progress, the first information is sent via SRB1; when small data transmission is not in progress, the first information is sent via SRB0.

7. The first node according to any one of claims 1 to 6, characterized in that: When small data transmission is in progress, the first information occupies only one bit in the UE assistance information.

8. The first node according to any one of claims 1 to 7, characterized in that: The first node, along with the execution of the first signaling, enters an RRC inactive state.

9. The first node according to any one of claims 1 to 8, characterized in that: include: The first transmitter sends second information, wherein the second information indicates the arrival of at least one of data and signaling mapped to a radio bearer other than a radio bearer configured for small data transmission; the second information is sent via a dedicated control channel; Among them, small data transmission is ongoing.

10. A method in a first node for multicast services and small data transmission, wherein: include: Receiving first signaling, wherein the first signaling configures small data transmission in an RRC inactive state; The first signaling configuration receives a multicast service in an RRC inactive state; In the RRC inactive state, as a response to any condition in the first condition set being met, sending the first information; the sending of the first information depends on whether the small data transmission is in progress; The first condition set includes receiving a first system information block that triggers multicast service reception, the configuration of at least one active multicast service session joined by the first node is unavailable, the serving cell does not provide at least one active multicast service session joined by the first node to the RRC inactive state, and the measurement of the serving cell is lower than at least one of the given thresholds for at least one active multicast service session joined by the first node; the sending of the first information depends on whether small data transmission is in progress, including: when small data transmission is in progress, sending the first information through a dedicated control channel; when small data transmission is not in progress, sending the first information through a common control channel, wherein the first information includes an RRC connection recovery request.

Images