A method and device for wireless communication

Abstract

The present application discloses a method and device for wireless communication, including sending a first message, the first message is used to indicate a first session set of a first service, the first session set includes at least one session; receiving a second message, the second message indicates a first unicast bearer; receiving first data through the first unicast bearer; wherein the first data belongs to a session in the first session set of the first service; the first service is a multicast broadcast service; the first message is used to determine that the first data is sent through the first unicast bearer. The present application improves resource utilization and reduces power consumption by determining the first session set.

Description

Technical Field

[0001] The present application relates to a transmission method and device in a wireless communication system, and in particular to a transmission method and device for improving system efficiency, optimizing resource utilization, reducing service interruption, avoiding resource waste, saving power, enhancing service continuity, and improving reliability in wireless communication. Background Art

[0002] In the future, the application scenarios of wireless communication systems will become more and more diversified, and different application scenarios will put forward different performance requirements for the system. In order to meet the different performance requirements of various application scenarios, the 3GPP (3rd Generation Partner Project) RAN (Radio Access Network) #72 plenary meeting decided to study the new radio (NR) (or Fifth Generation, 5G) technology, and the NR WI (Work Item) was passed at the 3GPP RAN #75 plenary meeting, and the standardization work on NR began.

[0003] In communication, both LTE (Long Term Evolution) and 5G NR involve accurate reception of reliable information, optimized energy efficiency, determination of information validity, flexible resource allocation, scalable system structure, efficient non-access layer information processing, low service interruption and drop rate, and support for low power consumption. This is of great significance to the normal communication between base stations and user equipment, the reasonable scheduling of resources, and the balancing of system loads. It can be said to be the cornerstone of high throughput, meeting the communication needs of various services, improving spectrum utilization, and improving service quality. It is indispensable for eMBB (ehanced Mobile BroadBand), URLLC (Ultra Reliable Low Latency Communication) and eMTC (enhanced Machine Type Communication). At the same time, in IIoT (Industrial Internet of Things), V2X (Vehicular to X), device to device, unlicensed spectrum communication, user communication quality monitoring, network planning optimization, NTN (Non Territerial Network), TN (Territial Network), dual connectivity systems, a mixture of the above communication modes, wireless resource management and multi-antenna codebook selection, signaling design, neighbor management, service management, and beamforming, there are extensive demands. Information transmission methods are divided into 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 power saving. At the same time, compatibility between different versions of different systems also needs to be considered during system design. Summary of the invention

[0005] In various communication scenarios, especially in wireless networks supporting the new generation of broadcast multicast services (MBS), it involves configuring wireless bearers for users for specific services. The configured wireless bearers can be unicast bearers or non-unicast bearers (i.e., point-to-multipoint transmission or point-to-point transmission). They can be non-unicast bearers in one cell, or unicast bearers can be configured in one cell. They can be configured as unicast bearers at certain times or non-unicast bearers at other times. This can greatly increase the flexibility of the network and the flexibility of resource allocation, and also help save system resources. This is an important technical content of 5G broadcast multicast. However, such configuration will encounter a series of problems, namely, when to configure what kind of wireless bearer and how to configure it, when users move between different cells, if the type of wireless bearer is different, how to choose, how to switch to reduce data interruption; similar problems also exist in a cell, how to configure unicast bearers. Non-unicast bearers, including broadcast or multicast bearers, can be targeted at a cell, a small area, or a large area. There are many users in the area, so it is difficult for such bearers to take care of each user. The service cell does not even know which users are receiving or interested in receiving services, because there is no accurate context information about these users receiving such services. Therefore, it is difficult to optimize and involve each specific user like unicast bearers. Improper processing may very likely cause interruption and loss of data reception. In addition, the establishment or data transmission method of unicast bearers is very different from multicast. It is difficult for users to make independent decisions, and network processing requires users to provide sufficient auxiliary information, otherwise it will cause resource waste and users are forced to receive unnecessary data. This auxiliary information may include user conditions, user reception conditions, user interests, user resource usage, service requirements and service transmission conditions for different services and different bearers, etc.

[0006] With regard to the above-mentioned problems, this application provides a solution.

[0007] It should be noted that, in the absence of conflict, the embodiments and features in any node of the present application can be applied to any other node. In the absence of conflict, the embodiments and features in the embodiments of the present application can be arbitrarily combined with each other.

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

[0009] Sending a first message, where the first message is used to indicate a first session set of a first service, where the first session set includes at least one session;

[0010] receiving a second message indicating a first unicast bearer; and receiving first data through the first unicast bearer;

[0011] The first data belongs to a session in the first session set of the first service; the first service is a multicast broadcast service; and the first message is used to determine that the first data is sent through the first unicast bearer.

[0012] As an embodiment, the problems to be solved by the present application include: when it is necessary to determine the type of wireless bearer used to transmit services such as broadcast and multicast, or to switch between non-unicast bearers and unicast bearers, especially when switching from non-unicast bearers to unicast bearers, since non-unicast bearers and unicast bearers are very different, the configuration mode, service capabilities, resource allocation, bearer management, user management, establishment and release, etc. may be different. In order to correctly implement the algorithm and make decisions, it is necessary to accurately grasp the information of the user's reception status, and configure resources and select bearers based on this information. In particular, it is necessary to avoid users receiving a part of the service that they are not interested in. That is, if the user is interested in the service itself, but is not interested in part of it or has already received it, it is necessary to avoid receiving or repeatedly receiving it. The present application solves the above problems by sending a first message to indicate the first session set of the first service.

[0013] As an embodiment, the benefits of the above method include: by indicating the first session set of the first service, the serving cell can correctly determine whether to use unicast transmission and whether to transmit data, and can also determine whether the data to be transmitted is required by the user. Therefore, it is beneficial to save resources, reduce user power consumption, and improve service quality.

[0014] Specifically, according to one aspect of the present invention, the first message indicates a third session set, the third session set includes sessions of the first service that are not of interest, and the third session set is used to determine the first session set; the first session set only includes sessions other than the third session set.

[0015] Specifically, according to one aspect of the present invention, first signaling is received, where the first signaling includes a second session set of the first service;

[0016] When the intersection of the second session set and the third session set is not empty, sending the first message as a response to receiving the first signaling.

[0017] Specifically, according to one aspect of the present invention, the first message is used to indicate a first segment identity set of a first session, the first session belongs to a first session set, each identity in the first segment identity set corresponds to a segment of the first session, and the first session includes N segments, where N is a positive integer; wherein the first segment identity set includes M identities, M is a positive integer not greater than N, and the first data belongs to a segment corresponding to an identity in the first segment identity set.

[0018] Specifically, according to one aspect of the present invention, a third message is sent, and the third message is used to indicate that the user is no longer interested in the session of the first service.

[0019] Specifically, according to one aspect of the present invention, the first message includes a recommended mode of an RLC entity for a radio bearer that carries the first service.

[0020] Specifically, according to one aspect of the present invention, a first reception quality is determined, where the first reception quality is the reception quality of the first service, and the first reception quality being lower than a first threshold is used to trigger sending the first message.

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

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

[0023] Specifically, according to one aspect of the present application, the first node is a relay.

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

[0025] Specifically, according to one aspect of the present application, the first node is an aircraft.

[0026] The present application discloses a method in a second node used for wireless communication, comprising:

[0027] receiving a first message, wherein the first message is used to indicate a first session set of a first service, wherein the first session set includes at least one session;

[0028] sending a second message indicating a first unicast bearer; and receiving first data through the first unicast bearer;

[0029] The first data belongs to a session in the first session set of the first service; the first service is a multicast broadcast service; and the first message is used to determine that the first data is sent through the first unicast bearer.

[0030] Specifically, according to one aspect of the present invention, the first message indicates a third session set, the third session set includes sessions of the first service that are not of interest, and the third session set is used to determine the first session set; the first session set only includes sessions other than the third session set.

[0031] Specifically, according to one aspect of the present invention, a first signaling is sent, where the first signaling includes a second session set of the first service;

[0032] When the intersection of the second session set and the third session set is not empty, the first message is sent as a response to receiving the first signaling.

[0033] Specifically, according to one aspect of the present invention, the first message is used to indicate a first segment identity set of a first session, the first session belongs to a first session set, each identity in the first segment identity set corresponds to a segment of the first session, and the first session includes N segments, where N is a positive integer; wherein the first segment identity set includes M identities, M is a positive integer not greater than N, and the first data belongs to a segment corresponding to an identity in the first segment identity set.

[0034] Specifically, according to one aspect of the present invention, a third message is received, where the third message is used to indicate that the user is no longer interested in the session of the first service.

[0035] Specifically, according to one aspect of the present invention, the first message includes a recommended mode of an RLC entity for a radio bearer that carries the first service.

[0036] Specifically, according to one aspect of the present invention, the sender of the first message determines a first reception quality, where the first reception quality is the reception quality of the first service, and the first reception quality being lower than a first threshold is used to trigger sending the first message.

[0037] Specifically, according to one aspect of the present application, the second node is a base station.

[0038] Specifically, according to one aspect of the present application, the second node is a relay.

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

[0040] Specifically, according to one aspect of the present application, the second node is an aircraft.

[0041] Specifically, according to one aspect of the present application, the second node is a group header.

[0042] Specifically, according to one aspect of the present application, the second node is a satellite.

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

[0044] A first transmitter sends a first message, where the first message is used to indicate a first session set of a first service, where the first session set includes at least one session;

[0045] A first receiver receives a second message indicating a first unicast bearer; and receives first data through the first unicast bearer;

[0046] The first data belongs to a session in the first session set of the first service; the first service is a multicast broadcast service; and the first message is used to determine that the first data is sent through the first unicast bearer.

[0047] The application discloses a second node used for wireless communication, comprising:

[0048] A second receiver receives a first message, wherein the first message is used to indicate a first session set of a first service, wherein the first session set includes at least one session;

[0049] A second transmitter sends a second message, where the second message indicates a first unicast bearer; and receives first data through the first unicast bearer;

[0050] The first data belongs to a session in the first session set of the first service; the first service is a multicast broadcast service; and the first message is used to determine that the first data is sent through the first unicast bearer.

[0051] As an embodiment, compared with the traditional solution, this application has the following advantages:

[0052] When a user just enters a new cell, or moves from a cell that transmits broadcast multicast services via non-unicast bearers to a cell that transmits broadcast multicast services via unicast bearers, or when a cell that transmits broadcast multicast services via non-unicast bearers is converted to unicast bearers to transmit the same services, or when unicast can better transmit services, a key issue will arise: whether a unicast point-to-point bearer should be established for a user, and whether a data packet should be transmitted in a point-to-point manner. For non-unicast bearer point-to-multipoint transmission, this is not a problem. The user can choose not to receive or not to establish the relevant bearer. These can be decided by the user, for example, the user is not interested for the time being; whether it is established or not, it will not affect the data transmission on the network side. However, for unicast, the user needs to establish the bearer and receive the data; if HARQ is used, ACK / NACK needs to be fed back, and if the RLC AM mode is configured, feedback status reports will also be involved. If the user does not do this, the entire wireless communication may be interrupted and forced to enter the idle state. When a user is interested in a certain service, but is not interested in part of the service or has already received the data of this part, it is necessary to avoid the user receiving or repeatedly receiving; this is also conducive to supporting arbitrary reception. This is not supported by current methods, because traditional non-unicast transmission does not need to be supported, and users can solve it themselves. The present application indicates the first service and the first session set of the first service through a first message indication, which can help the service cell determine a refined spectrum of interest, which is used to determine whether to establish a unicast bearer and whether to transmit related data. It is conducive to saving resources and power. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0054] Figure 1 A flowchart of sending a first message and receiving a second message according to an embodiment of the present application is shown;

[0055] Figure 2 A schematic diagram of a network architecture according to an embodiment of the present application is shown;

[0056] Figure 3 A schematic diagram showing an embodiment of a wireless protocol architecture of a user plane and a control plane according to an embodiment of the present application;

[0057] Figure 4 A schematic diagram showing a first communication device and a second communication device according to an embodiment of the present application is shown;

[0058] Figure 5A flow chart showing the transmission of a wireless signal according to an embodiment of the present application is shown;

[0059] Figure 6 A flow chart showing the transmission of a wireless signal according to an embodiment of the present application is shown;

[0060] Figure 7 A schematic diagram showing a first message according to an embodiment of the present application being used to determine that first data is sent through a first unicast bearer;

[0061] Figure 8 A schematic diagram of a first unicast bearer according to an embodiment of the present application is shown;

[0062] Fig. 9 A schematic diagram showing message and data transmission according to an embodiment of the present application is shown;

[0063] Fig.10 A schematic diagram showing that a first reception quality lower than a first threshold is used to trigger a first transmitter to send a first message according to an embodiment of the present application;

[0064] Fig.10a A schematic diagram of segmentation according to an embodiment of the present application is shown;

[0065] Fig.11 A schematic diagram illustrating a processing device in a first node according to an embodiment of the present application is illustrated;

[0066] Fig.12 The diagram illustrates a processing device used in a second node according to an embodiment of the present application. DETAILED DESCRIPTION

[0067] 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 in the present application and the features in the embodiments can be combined with each other arbitrarily.

[0068] Example 1

[0069] Embodiment 1 illustrates a flowchart of sending a first message and receiving a second message according to an embodiment of the present application, as shown in the attached Figure 1 Attached Figure 1 In the figure, each box represents a step. It should be emphasized that the order of the boxes in the figure does not represent the temporal relationship between the steps represented.

[0070] In Embodiment 1, the first node in the present application sends a first message in step 101; receives a second message in step 102;

[0071] wherein the first message is used to indicate a first session set of a first service, the first session set including at least one session; the second message indicates a first unicast bearer; first data is received through the first unicast bearer; wherein the first data belongs to a session in the first session set of the first service; the first service is a multicast broadcast service; the first message is used to determine that the first data is sent through the first unicast bearer.

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

[0073] As an embodiment, the first node is in an RRC (Radio Resource Control) connected state.

[0074] As an embodiment, the first node is in an RRC idle state or an RRC inactive state.

[0075] As an embodiment, the first message includes an RRC message.

[0076] As an embodiment, the first message includes a NAS message.

[0077] As an embodiment, the first message is an RRC message.

[0078] As an embodiment, the logical channel occupied by the first message includes DCCH.

[0079] As an embodiment, the logical channel occupied by the first message includes DTCH.

[0080] As an embodiment, the first message includes MBMSInterestIndication.

[0081] As an embodiment, the first message includes a part of the fields in MBMSInterestIndication.

[0082] As an embodiment, the first message includes RRCSetupRequest.

[0083] As an embodiment, the first message includes RRCResumeRequest.

[0084] As an embodiment, the first message includes RRCConnectionSetupRequest.

[0085] As an embodiment, the first message includes RRCConnectionResumeRequest.

[0086] As an embodiment, the second signaling includes ueAssistanceInformation.

[0087] As an embodiment, the first message includes a Service Request.

[0088] As an embodiment, the first service includes MBMS (Multimedia Broadcast Multicast Service) service.

[0089] As an embodiment, the first service includes an eMBMS (Enhanced Multimedia Broadcast Multicast Service) service.

[0090] As an embodiment, the first service includes MBS (Multicast Broadcast Service) service.

[0091] As an embodiment, the first service includes a Broadcast service.

[0092] As an embodiment, the first service includes a Multicast service.

[0093] As an embodiment, the first service includes a groupcast service.

[0094] As an embodiment, the first session set includes S sessions, where S is a positive integer.

[0095] As an embodiment, the first session set includes session.

[0096] As an embodiment, the first session set includes a download session.

[0097] As an embodiment, the first session set includes a streaming session.

[0098] As an embodiment, the first service includes a multicast or broadcast service for V2X.

[0099] As an embodiment, the first service includes a multicast or broadcast service based on NR.

[0100] As an embodiment, any session in the first session set is associated with a session context, and the session context includes parameters related to the session.

[0101] As a sub-embodiment of this embodiment, the session-related parameters include an IP address.

[0102] As a sub-embodiment of this embodiment, the session-related parameters include flute-tsi.

[0103] As a sub-embodiment of this embodiment, the session-related parameters include sessionId.

[0104] As a sub-embodiment of this embodiment, the session-related parameters include the session start time.

[0105] As a sub-embodiment of this embodiment, the session-related parameters include session termination time.

[0106] As a sub-embodiment of this embodiment, the session-related parameters include the duration of the session.

[0107] As a sub-embodiment of this embodiment, the session-related parameters include the number of bits or bytes of the session.

[0108] As a sub-embodiment of this embodiment, the session-related parameters include the QoS of the session.

[0109] As a sub-embodiment of this embodiment, the session-related parameters include the port number used by the session.

[0110] As a sub-embodiment of this embodiment, the session-related parameters include MBMS-Session-Identity.

[0111] As a sub-embodiment of this embodiment, the session-related parameters include MBS-Session-Identity.

[0112] As a sub-embodiment of this embodiment, the session-related parameters include MBMS-Session-Identity-Expiry.

[0113] As a sub-embodiment of this embodiment, the session-related parameters include MBS-Session-Identity-Expiry.

[0114] As a sub-embodiment of this embodiment, the node that owns the one session context includes the first node.

[0115] As a sub-embodiment of this embodiment, the node having the one session context includes a serving cell of the first node.

[0116] As a sub-embodiment of this embodiment, the node that owns the one session context includes a network that provides the first service.

[0117] As a sub-embodiment of this embodiment, the first message carries some parameters of a session context associated with a session in the first session set.

[0118] As a sub-embodiment of this embodiment, the second message carries some parameters of a session context associated with a session in the first session set.

[0119] As a sub-embodiment of this embodiment, the network to which the first node accesses indicates partial parameters of a session context associated with a session in the first session set.

[0120] As a sub-embodiment of this embodiment, the session context includes a context; the session context includes a set of parameters related to the session.

[0121] As a sub-embodiment of this embodiment, any session in the first session set has a corresponding session context.

[0122] As an embodiment, the first message indicates the identity of the first service, and the identity of the first service identifies the first service.

[0123] As an embodiment, the first message includes a TMGI, and the TMGI indicates the first service.

[0124] As an embodiment, the first node receives first service signaling, the first service signaling includes a first index, the first index corresponds to the first service, and the first message indicates the first index.

[0125] As an embodiment, the first session set uniquely determines the session of the first service within the PLMN range.

[0126] As an embodiment, the second message includes SIB.

[0127] As an embodiment, the second message includes RRCReconfiguration.

[0128] As an embodiment, the second message includes RRCConnectionReconfiguration.

[0129] As an embodiment, the second message includes RRCConnectionSetup.

[0130] As an embodiment, the second message includes RRCSetup.

[0131] As an embodiment, the second message includes RRCResume.

[0132] As an embodiment, the second message includes RRCConnectionResume.

[0133] As an embodiment, the second message includes DCI.

[0134] As an embodiment, the second message includes MAC CE (Medium Access Control Control Element).

[0135] As an embodiment, the physical channel occupied by the second message includes PDSCH.

[0136] As an embodiment, the physical channel occupied by the second message includes PDCCH.

[0137] As an embodiment, the physical channel occupied by the second message includes PSSCH.

[0138] As an embodiment, the physical channel occupied by the second message includes PSCCH.

[0139] As an embodiment, the physical channel occupied by the second message includes PSFCH.

[0140] As an embodiment, the first unicast bearer includes DRB.

[0141] As an embodiment, the first unicast bearer includes a unicast bearer.

[0142] As an embodiment, the first unicast bearer includes an MRB transmitted in a PTP (Point to point) manner.

[0143] As an embodiment, the first unicast bearer includes a multicast bearer transmitted in a PTP (Point to point) manner.

[0144] As an embodiment, the first unicast bearer is a wireless bearer.

[0145] As an embodiment, the first unicast bearer is an RLC bearer.

[0146] As an embodiment, the first unicast bearer includes an RLC bearer.

[0147] As an embodiment, the first unicast bearer is a SL-RB.

[0148] As an embodiment, the first unicast bearer is a PTP branch in a multicast bearer.

[0149] As a sub-embodiment of this embodiment, the PTP branch includes leg.

[0150] As a sub-embodiment of this embodiment, the PTP branch includes link.

[0151] As a sub-embodiment of this embodiment, the PTP branch includes branch.

[0152] As an embodiment, the first unicast bearer is a PTP transmission in a multicast bearer.

[0153] As an embodiment, the PDCCP that schedules the data carried by the first unicast is scrambled using the C-RNTI of the first node.

[0154] As an embodiment, the DCI that schedules the data carried by the first unicast is scrambled using the C-RNTI of the first node.

[0155] As an embodiment, the DCI scheduling the first data is scrambled using the C-RNTI of the first node.

[0156] As an embodiment, the first data is sent using the first unicast bearer.

[0157] As an embodiment, the first data is transmitted in a point-to-point manner.

[0158] As an embodiment, the first data is a MAC PDU, and the link layer identity included in the DST field of the header of the MAC PDU identifies the first node.

[0159] As an embodiment, the first data is data above the MAC layer, and the link layer identity included in the DST field of the header of the MAC PDU carrying the first data identifies the first node.

[0160] As an embodiment, the first data includes PDCP PDU.

[0161] As an embodiment, the first data includes PDCP SDU.

[0162] As an embodiment, the first data includes RLC PDU.

[0163] As an embodiment, the first data includes MAC PDU.

[0164] As an embodiment, the first data includes data of the QoS flow of the first service.

[0165] As an embodiment, the first data includes higher-layer data of the first service.

[0166] As an embodiment, the sentence "the first data belongs to a session in the first session set of the first service" includes the following meanings: the first data is data of the first service; the first data is data of a session in the first session set of the first service; the QoS flow of the first data belongs to the first MBS session, and the first MBS session is the MBS session of the first service; the first MBSsession is a multicast broadcast service session established by the core network; the first MBS session is different from the sessions included in the first session set; the first MBS session is the same as the session included in the first session set; the first data is associated with a first TMGI; the first TMGI identifies the first service; the first data uses the first unicast bearer, and the first unicast bearer is associated with the first service; the first service is sent using the first unicast bearer; the first data is associated with a first session identity, the first session identity identifies a first session, and the first session belongs to the first session set of the first service; the first unicast bearer is associated with the first session; the sender of the first data indicates, through explicit signaling, that the first data is associated with the first TMGI; the sender of the first data indicates, through explicit signaling, that the first data is associated with the first session identity; the sender of the first data indicates, through explicit signaling, that the first unicast bearer is associated with the first TMGI; indicating that the first unicast bearer is associated with the first session identity; the explicit signaling includes RRC signaling; the explicit signaling includes DCI.

[0167] As an embodiment, the serving cell of the first node explicitly indicates information of the first service, including information of sessions in the first session set, through signaling; the information of the first service is used to determine the first session set of the first service.

[0168] As a sub-embodiment of this embodiment, the signaling passed by the service cell of the first node includes a user service description (USD, User Service Description).

[0169] As an embodiment, the user service description (USD, User Service Description) pre-stored in the first node includes information of the first service.

[0170] As an embodiment, the second message includes a SCPTMConfiguration message.

[0171] As an embodiment, the multicast group joined by the first node through the joining process determines that the session of the first service is sent through the first unicast bearer.

[0172] As an embodiment, the first service is a multicast bearer service included in the multicast group that the first node joins through a joining process.

[0173] As an embodiment, the first service is a broadcast service registered by the first node through NAS (Non-Access Stratum).

[0174] As an embodiment, the first service is a multicast service registered by the first node through NAS (Non-Access Stratum).

[0175] As an embodiment, the first service is a broadcast service subscribed by the first node.

[0176] As an embodiment, the first service is a multicast service subscribed by the first node.

[0177] As an embodiment, the first service is a broadcast or multicast service in which the first node is interested.

[0178] As an embodiment, the first session set of the first service includes sessions of the first service in which the first node is interested.

[0179] As an embodiment, the first message indicates that the first node is not interested in sessions other than the first session set of the first service.

[0180] As an embodiment, the first message indicates that the first node is not interested in sessions other than the first session set of the first service and is received via PTP.

[0181] As an embodiment, the first unicast bearer uses RLC UM.

[0182] As an embodiment, the first unicast bearer uses RLC AM.

[0183] As an embodiment, the sending of the first message is used to trigger the PDCP entity of the first unicast bearer of the first node to send a PDCP status report.

[0184] As an embodiment, the sending of the first message is used to trigger the RLC entity corresponding to the first unicast bearer of the first node to send an RLC status report.

[0185] As an embodiment, the sending of the first message is used to trigger the RLC entity corresponding to the first unicast bearer of the first node to send polling.

[0186] Example 2

[0187] Embodiment 2 illustrates a schematic diagram of a network architecture according to the present application, as shown in the attached Figure 2 shown.

[0188] Attached Figure 2A diagram of a network architecture 200 for 5G NR, LTE (Long-Term Evolution) and LTE-A (Long-Term Evolution Advanced) systems is illustrated. The 5G NR or LTE network architecture 200 may be referred to as 5GS (5G System) / EPS (Evolved Packet System) 200 or some other suitable terminology. The 5GS / EPS 200 may include one or more UEs (User Equipment) 201, NG-RAN (Next Generation Radio Access Network) 202, 5GC (5G Core Network) / EPC (Evolved Packet Core) 210, HSS (Home Subscriber Server) / UDM (Unified Data Management) 220, and Internet services 230. The 5GS / EPS may be interconnected with other access networks, but these entities / interfaces are not shown for simplicity. As shown, 5GS / EPS provides packet-switched services, however, those skilled in the art will readily appreciate that the various concepts presented throughout this application can be extended to networks providing circuit-switched services or other cellular networks. NG-RAN includes NR Node B (gNB) 203 and other gNBs 204. gNB 203 provides user and control plane protocol terminations toward UE 201. gNB 203 can be connected to other gNBs 204 via an Xn interface (e.g., backhaul). gNB 203 may also be referred to as a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP (transmitting receiving node), or some other suitable term. gNB 203 provides an access point to 5GC / EPC 210 for UE 201. Examples of UE 201 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radios, non-terrestrial base station communications, satellite mobile communications, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, drones, aircraft, narrowband Internet of Things devices, machine type communication devices, land vehicles, cars, wearable devices, or any other similar functional devices. 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 term.gNB203 is connected to 5GC / EPC210 via the S1 / NG interface. 5GC / EPC210 includes MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MME / AMF / SMF214, S-GW (Service Gateway) / UPF (User Plane Function) 212, and P-GW (Packet Data Network Gateway) / UPF213. MME / AMF / SMF211 is the control node that handles signaling between UE201 and 5GC / EPC210. ​​In general, MME / AMF / SMF211 provides bearer and connection management. All user IP (Internet Protocol) packets are transmitted through S-GW / UPF212, which itself is connected to P-GW / UPF213. P-GW provides UE IP address allocation and other functions. P-GW / UPF213 is connected to Internet service 230. Internet service 230 includes operator-corresponding Internet protocol services, which may specifically include Internet, Intranet, IMS (IP Multimedia Subsystem) and packet-switched streaming services.

[0189] As an embodiment, the UE201 corresponds to the first node in the present application.

[0190] As an embodiment, the UE 201 supports transmission in a non-terrestrial network (NTN).

[0191] As an embodiment, the UE201 supports transmission in a network with a large delay difference.

[0192] As an embodiment, the UE 201 supports V2X transmission.

[0193] As an embodiment, the UE 201 supports MBS transmission.

[0194] As an embodiment, the UE 201 supports MBMS transmission.

[0195] As an embodiment, the gNB203 corresponds to the second node in this application.

[0196] As an embodiment, the gNB203 supports transmission in a non-terrestrial network (NTN).

[0197] As an embodiment, the gNB203 supports transmission in a network with large latency difference.

[0198] As an embodiment, the gNB203 supports V2X transmission.

[0199] As an embodiment, the gNB203 supports MBS transmission.

[0200] As an embodiment, the gNB203 supports MBMS transmission.

[0201] Example 3

[0202] Embodiment 3 shows a schematic diagram of an embodiment of a wireless protocol architecture of a user plane and a control plane according to the present application, as shown in the attached Figure 3 shown. Figure 3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300, Figure 3The radio protocol architecture of the control plane 300 for a first node (UE, satellite or aircraft in gNB or NTN) and a second node (satellite or aircraft in gNB, UE or NTN), or between two UEs is shown in 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 as PHY301 in this article. Layer 2 (L2 layer) 305 is above PHY301 and is responsible for the link between the first node and the second node and the two UEs through PHY301. 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 nodes. 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 layer) in the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and configuring the lower layers using RRC signaling between the second node and the first node. The radio protocol architecture of the user plane 350 includes layer 1 (L1 layer) and layer 2 (L2 layer). The radio protocol architecture for the first node and the second node in the user plane 350 is substantially the same as the corresponding layers and sublayers in the control plane 300 for 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, but the PDCP sublayer 354 also provides header compression for upper layer data packets to reduce radio transmission overhead. The L2 layer 355 in the user plane 350 also includes a SDAP (Service Data Adaptation Protocol) sublayer 356, which is responsible for mapping between QoS flows and data radio bearers (DRBs) to support the diversity of services.Although not shown, the first node may have several upper layers above the L2 layer 355. Also included are a network layer (e.g., IP layer) terminated at the P-GW on the network side and an application layer terminated at the other end of the connection (e.g., remote UE, server, etc.).

[0203] As an example, Figure 3 The wireless protocol architecture in is applicable to the first node in this application.

[0204] As an example, Figure 3 The wireless protocol architecture in is applicable to the second node in this application.

[0205] As an embodiment, the first message in the present application is generated by the PHY301 or PHY351 or MAC302 or MAC352 or RRC306.

[0206] As an embodiment, the second message in the present application is generated in the PHY301 or PHY351 or MAC302 or MAC352 or RRC306 or non-access stratum (NAS).

[0207] As an embodiment, the first signaling in the present application is generated in the RRC306 or the non-access stratum (NAS).

[0208] As an embodiment, the third message in the present application is generated in the PHY301 or PHY351 or MAC302 or MAC352 or RRC306 or non-access stratum (NAS).

[0209] As an embodiment, the first data in the present application is generated at a layer or application layer above the PHY351 or MAC352 or RLC353 or the SDAP356 or PDCP354 or L2 layer 355 .

[0210] Example 4

[0211] Embodiment 4 shows a schematic diagram of a first communication device and a second communication device according to the present application, as shown in the attached figure. Figure 4 shown. 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.

[0212] 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, a multi-antenna transmit processor 457, a multi-antenna receive processor 458, a transmitter / receiver 454 and an antenna 452.

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

[0214] In transmission from the second communication device 410 to the first communication device 450, at the second communication device 410, upper layer data packets from the core network are provided to the controller / processor 475. The controller / processor 475 implements the functionality of the L2 layer. In 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 L1 layer (i.e., the 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), M-quadrature amplitude modulation (M-QAM)). The multi-antenna transmit processor 471 performs digital spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing 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 domain and / or frequency domain, and then uses an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain multi-carrier symbol stream. The multi-antenna transmit processor 471 then performs a transmit analog precoding / beamforming operation on the time-domain multi-carrier 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.

[0215] In the 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 through 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 and provides it to the receiving processor 456. The receiving processor 456 and the multi-antenna receiving processor 458 implement various signal processing functions of the L1 layer. The multi-antenna receiving processor 458 performs a receiving analog precoding / beamforming operation on the baseband multi-carrier symbol stream from the receiver 454. The receiving processor 456 uses a fast Fourier transform (FFT) to convert the baseband multi-carrier symbol stream after the receiving analog precoding / beamforming operation from the time domain to the frequency domain. In the frequency domain, the physical layer data signal and the reference signal are demultiplexed by the receiving processor 456, wherein the reference signal will be used for channel estimation, and the data signal is recovered after multi-antenna detection in the multi-antenna receiving processor 458 to any spatial stream destined for the first communication device 450. The symbols on each spatial stream are demodulated and recovered in the receiving processor 456, and soft decisions are generated. The receiving 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 codes and data. The memory 460 may be referred to as a computer-readable medium. In the transmission from the second communication device 410 to the second communication device 450, the controller / processor 459 provides multiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover the 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 L3 for L3 processing.

[0216] In the transmission from the first communication device 450 to the second communication device 410, at the first communication device 450, a data source 467 is used 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 function 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, and implements L2 layer functions for user plane and control plane. The controller / processor 459 is also responsible for the retransmission of lost packets and signaling to the second communication device 410. The transmit processor 468 performs modulation mapping and channel coding processing, and the multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing. Then, the transmit processor 468 modulates the generated spatial stream into a multi-carrier / single-carrier symbol stream, which is then provided to different antennas 452 via the transmitter 454 after analog precoding / beamforming operations in the multi-antenna transmit processor 457. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a radio frequency symbol stream, and then provides it to the antenna 452.

[0217] In the transmission from the first communication device 450 to the second communication device 410, the function at the second communication device 410 is similar to the reception function at the first communication device 450 described in the transmission from the second communication device 410 to the first communication device 450. Each receiver 418 receives a radio frequency signal through its corresponding antenna 420, converts the received radio frequency signal into a baseband signal, and provides the baseband signal to the multi-antenna reception processor 472 and the reception processor 470. The reception processor 470 and the multi-antenna reception processor 472 jointly implement the functions of the L1 layer. The controller / processor 475 implements the L2 layer functions. The controller / processor 475 can be associated with a memory 476 storing program codes and data. The memory 476 can be referred to as a computer-readable medium. In the transmission from the first communication device 450 to the second communication device 410, the controller / processor 475 provides multiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover the upper layer data packets from the UE 450. Upper layer packets from controller / processor 475 may be provided to the core network.

[0218] As an embodiment, the first communication device 450 apparatus 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 apparatus at least: sends a first message, the first message is used to indicate a first session set of a first service, the first session set includes at least one session; receives a second message, the second message indicates a first unicast bearer; receives first data through the first unicast bearer; wherein the first data belongs to a session in the first session set of the first service; the first service is a multicast broadcast service; the first message is used to determine that the first data is sent through the first unicast bearer.

[0219] As an embodiment, the first communication device 450 includes: a memory storing a computer-readable instruction program, wherein the computer-readable instruction program generates actions when executed by at least one processor, and the actions include: sending a first message, wherein the first message is used to indicate a first session set of a first service, and the first session set includes at least one session; receiving a second message, wherein the second message indicates a first unicast bearer; receiving first data through the first unicast bearer; wherein the first data belongs to a session in the first session set of the first service; the first service is a multicast broadcast service; and the first message is used to determine that the first data is sent through the first unicast bearer.

[0220] As an embodiment, the second communication device 410 device includes: at least one processor and at least one memory, the at least one memory includes 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. The second communication device 410 device at least: receives a first message, the first message is used to indicate a first session set of a first service, the first session set includes at least one session; sends a second message, the second message indicates a first unicast bearer; receives first data through the first unicast bearer; wherein the first data belongs to a session in the first session set of the first service; the first service is a multicast broadcast service; the first message is used to determine that the first data is sent through the first unicast bearer.

[0221] As an embodiment, the second communication device 410 apparatus includes: a memory storing a computer-readable instruction program, wherein the computer-readable instruction program generates actions when executed by at least one processor, and the actions include: receiving a first message, wherein the first message is used to indicate a first session set of a first service, wherein the first session set includes at least one session; sending a second message, wherein the second message indicates a first unicast bearer; receiving first data through the first unicast bearer; wherein the first data belongs to a session in the first session set of the first service; the first service is a multicast broadcast service; and the first message is used to determine that the first data is sent through the first unicast bearer.

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

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

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

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

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

[0227] As an embodiment, the second communication device 410 is a relay.

[0228] As an embodiment, the second communication device 410 is a UE.

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

[0230] As an embodiment, the receiver 456 (including the antenna 460), the receiving processor 452 and the controller / processor 490 are used to receive the first data in the present application.

[0231] As an embodiment, the receiver 456 (including the antenna 460), the receiving processor 452 and the controller / processor 490 are used to receive the second message in the present application.

[0232] As an embodiment, the receiver 456 (including the antenna 460), the receiving processor 452 and the controller / processor 490 are used to receive the first signaling in the present application.

[0233] As an embodiment, the transmitter 456 (including the antenna 460), the transmission processor 455 and the controller / processor 490 are used to send the first message in the present application.

[0234] As an embodiment, the transmitter 456 (including the antenna 460), the transmit processor 455 and the controller / processor 490 are used to send the third message in the present application.

[0235] As an embodiment, the transmitter 416 (including the antenna 420), the transmit processor 412 and the controller / processor 440 are used to send the second information in the present application.

[0236] As an embodiment, the transmitter 416 (including the antenna 420), the transmission processor 412 and the controller / processor 440 are used to send the first signaling in the present application.

[0237] As an embodiment, the transmitter 416 (including the antenna 420), the transmission processor 412 and the controller / processor 440 are used to send the first data in the present application.

[0238] As an embodiment, the receiver 416 (including the antenna 420), the receiving processor 412 and the controller / processor 440 are used to receive the first message in the present application.

[0239] As an embodiment, the receiver 416 (including the antenna 420), the receiving processor 412 and the controller / processor 440 are used to receive the third message in the present application.

[0240] Example 5

[0241] Embodiment 5 illustrates a wireless signal transmission flow chart according to an embodiment of the present application, as shown in the attached Figure 5 Attached Figure 5 In the example, U01 corresponds to the first node of the present application, and N02 corresponds to the second 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, wherein the steps in F51 and F52 are optional.

[0242] for First node U01 , receiving the first signaling in step S5101; sending the first message in step S5102; receiving the second message in step S5103; receiving the first data in step S5104; and sending the third message in step S5105.

[0243] for Second node N02, sending a first signaling in step S5201; receiving a first message in step S5202; sending a second message in step S5203; sending first data in step S5204; receiving a third message in step S5205.

[0244] In embodiment 5, the first message is used to indicate a first session set of a first service, the first session set including at least one session; the second message indicates a first unicast bearer; the first node U01 receives first data through the first unicast bearer;

[0245] The first data belongs to a session in the first session set of the first service; the first service is a multicast broadcast service; and the first message is used to determine that the first data is sent through the first unicast bearer.

[0246] As an embodiment, the second node N02 is a service cell of the first node U01.

[0247] As an embodiment, the second node N02 is a relay of the first node U01.

[0248] As an embodiment, the second node N02 is the PCell of the first node U01.

[0249] As an embodiment, the second node N02 is the PSCell of the first node U01.

[0250] As an embodiment, the second node N02 is the MCG of the first node U01.

[0251] As an embodiment, the second node N02 is the SCG of the first node U01.

[0252] As an embodiment, the second node N02 is the target cell of the first node U01.

[0253] As an embodiment, the second node N02 is the source cell of the first node U01.

[0254] As an embodiment, the first session set includes sessions of the first service of interest.

[0255] As an embodiment, the first data is multicast broadcast service data; the multicast broadcast service includes MBS.

[0256] As an embodiment, the first unicast bearer is a point-to-point transmission bearer.

[0257] As an embodiment, the first data belongs to a first MBS session, and the first MBS session is established by a core network.

[0258] As an embodiment, the first data is transmitted from the core network to the service cell N02 of the first node through a shared tunnel.

[0259] As an embodiment, the first session set is stored in the UE context or UE MBS contex of the first node U01 by the serving cell of the first node.

[0260] As an embodiment, the second message indicates establishing the first unicast bearer.

[0261] As an embodiment, the second message indicates to add the first unicast bearer.

[0262] As an embodiment, the second message indicates to modify the first unicast bearer.

[0263] As a sub-embodiment of this embodiment, the second message indicates that the QoS flow of the first data is mapped to the first unicast bearer.

[0264] As an embodiment, the second message indicates resuming the first unicast bearer.

[0265] As an embodiment, the second message indicates activation of the first unicast bearer.

[0266] As an embodiment, the first message is used to determine establishment of the first unicast bearer.

[0267] As an embodiment, the first message is used to trigger establishment of the first unicast bearer.

[0268] As an embodiment, the first signaling includes a second session set of the first service.

[0269] As an embodiment, when the intersection of the second session set and the third session set is not empty, the first node U01 sends the first message as a response to receiving the first signaling.

[0270] As an embodiment, the first signaling includes SIB (System Information Block).

[0271] As an embodiment, the logical channel occupied by the first signaling includes MCCH.

[0272] As an embodiment, the logical channel occupied by the first signaling includes SC-MCCH.

[0273] As an embodiment, the logical channel occupied by the first signaling includes MTCH.

[0274] As an embodiment, the logical channel occupied by the first signaling includes SC-MTCH.

[0275] As an embodiment, the first signaling is sent via broadcast or multicast.

[0276] As an embodiment, the first signaling is sent via unicast.

[0277] As an embodiment, the first signaling indicates a sending method of the first service, and the sending method includes PTM or PTP.

[0278] As an embodiment, the first signaling indicates that a method for sending data of the second session set of the first service includes PTP.

[0279] As an embodiment, the first signaling indicates that a sending method of the second session set of the first service includes PTP.

[0280] As an embodiment, the first signaling indicates that the sending mode of at least one session in the second session set of the first service includes PTP.

[0281] As an embodiment, the second session set of the first service includes sessions that are being sent; and the second session set of the first service includes sessions that are about to be sent.

[0282] As an embodiment, when a transmission mode of a session in the first session set of the first service changes, the first node sends the first message.

[0283] As a sub-embodiment of this embodiment, the transmission mode is changed from PTM to PTP.

[0284] As an embodiment, the second session set includes at least one session.

[0285] As an embodiment, the first signaling indicates a second session identity set, and any session identity in the second session identity set determines a session.

[0286] As an embodiment, the second session set includes sessions of the first service in which the first node is interested.

[0287] As an embodiment, the second session set includes sessions of the first service in which the first node is not interested.

[0288] As an embodiment, the first message is used to trigger the sending of the second message.

[0289] As an embodiment, the first signaling includes SIB1.

[0290] As an embodiment, the first signaling includes SIB14.

[0291] As an embodiment, the first signaling includes SIB15.

[0292] As an embodiment, the first signaling includes SIB16.

[0293] As an embodiment, the first signaling includes SIB17.

[0294] As an embodiment, the first signaling includes SIB18.

[0295] As an embodiment, the first signaling includes SIB19.

[0296] As an embodiment, the first signaling includes SIB20.

[0297] As an embodiment, the first signaling includes a SCPTMConfiguration message.

[0298] As an embodiment, the first signaling includes an RRCReconfiguration message.

[0299] As an embodiment, the first signaling includes an RRCConnectionReconfiguration message.

[0300] As an embodiment, when the intersection of the second session set and the third session set is not empty, the first node U01 sends the first message.

[0301] As an embodiment, when the first node U01 needs to use the first unicast bearer or PTP to receive the session in the first session set of the first service, the first node U01 sends the first message.

[0302] As an embodiment, when the first signaling indicates that the sending mode of the sessions in the first session set of the first service is converted from PTM to PTP, the first node U01 sends the first message.

[0303] As an embodiment, the first data is data forwarded by the second node N02.

[0304] As an embodiment, the first message is used to determine establishment of the first unicast bearer.

[0305] As an embodiment, the first message is used to trigger establishment of the first unicast bearer.

[0306] As an embodiment, in response to receiving the first message, the second node N02 sends the second message.

[0307] As an embodiment, when the first message is received, the first unicast bearer has not been established, and the second message indicates to establish the first unicast bearer.

[0308] As an embodiment, when the first message is received, the first unicast bearer has been established, but the QoS flow to which the first data belongs has not yet been mapped to the wireless bearer, and the second message indicates that the QoS flow to which the first data belongs is mapped to the first unicast bearer.

[0309] As a sub-embodiment of this embodiment, the second message includes RRCReconfiguration.

[0310] As an embodiment, when the first message is received, the first unicast bearer has been established, and the second message indicates that data of the first unicast bearer is received via PTP.

[0311] As an embodiment, the second message indicates enabling PTP transmission of the first unicast bearer.

[0312] As an embodiment, the reception of the second message triggers the first node U01 to establish an RLC entity for PTP transmission of the first unicast bearer.

[0313] As an embodiment, the reception of the second message triggers the first node U01 to establish a MAC entity for PTP transmission of the first unicast bearer.

[0314] As an embodiment, the first message indicates a third session set, the third session set includes sessions of the first service that are not of interest, the third session set is used to determine the first session set; the first session set only includes sessions other than the third session set.

[0315] As an embodiment, the first session set includes all sessions of interest for the first service.

[0316] As an embodiment, the first session set includes all sessions of the first service other than the third session set.

[0317] As an embodiment, the first session set includes sessions of the first service other than the third session set.

[0318] As an embodiment, all sessions of the first service other than the third session set are determined to belong to the first session set.

[0319] As an embodiment, the first message includes the third session set, and the third session set implicitly determines the first session set.

[0320] As an embodiment, the sessions in the second session set that do not include the third session set belong to the first session set.

[0321] As an embodiment, the third session set and the first session set are both subsets of the second session set.

[0322] As an embodiment, the first message indicates the third index set, the indexes in the third index set correspond one-to-one to the sessions in the third session set, the first signaling indicates the second index set, the indexes in the second index set correspond one-to-one to the sessions in the second session set, and the third index set is a subset of the second index set.

[0323] As an embodiment, the first message implicitly indicates the first session set.

[0324] As an embodiment, the first message implicitly indicates the third session set.

[0325] As an embodiment, the first message indicates a third session identity set, and the session identities in the third session identity set correspond one-to-one to the sessions in the third session set.

[0326] As an embodiment, the first data does not belong to any session in the third session set.

[0327] As an embodiment, when the intersection of the second session set and the third session set is not empty, the first message is sent as a response to receiving the first signaling.

[0328] As an embodiment, when the intersection of the second session set and the third session set is empty, the first node U01 is not triggered to send a message indicating the first session set of the first service.

[0329] As an embodiment, the advantage of the above method is that the first node sends the first message only when it finds that the serving cell is going to transmit a session that it is not interested in through PTP, thereby saving wireless resources.

[0330] As an embodiment, the first message includes a recommended mode of the RLC entity of the radio bearer used to carry the first service.

[0331] As an embodiment, the first message may recommend using AM as the RLC mode.

[0332] As an embodiment, the first message recommends using UM as the RLC mode.

[0333] As an embodiment, the first message includes a recommendation to use UM as the RLC mode when using PTP to transmit a session in the first session set of the first service.

[0334] As an embodiment, the first message includes a recommendation to use HARQ or not to use HARQ.

[0335] As an embodiment, the first message includes recommending the use of HARQ or not using HARQ when using PTP to transmit the first service.

[0336] As an embodiment, the first message includes recommending the use of HARQ or not using HARQ when using PTP to transmit a session in the first session set of the first service.

[0337] As an embodiment, the second message indicates the first unicast bearer according to the configuration recommended by the first message.

[0338] As an embodiment, the second message configures the first unicast bearer according to the configuration recommended by the first message.

[0339] As an embodiment, when PTP is used to transmit the first service, the second message configures the RLC entity corresponding to the first unicast bearer to use UM mode.

[0340] As an embodiment, when PTP is used to transmit the first service, the second message configures the MAC corresponding to the first unicast bearer not to use HARQ.

[0341] As an embodiment, the benefits of the above method include: when the MBS service is transmitted using the PTP mode, the user does not need to be forced to receive the service.

[0342] As an embodiment, the third message is used to indicate that the user is no longer interested in the session of the first service.

[0343] As an embodiment, the third message indicates a fourth session set of the first service, the fourth session set includes at least one session, and the fourth session set is orthogonal to the first session set.

[0344] As an embodiment, the third message is used to suspend or release the first unicast bearer.

[0345] As an embodiment, the third message is used to terminate the transmission of data of the first service through the first unicast bearer.

[0346] As an embodiment, the third message is sent after the first message.

[0347] As an embodiment, when the fourth session set includes the second session set, the second node N02 abandons transmitting data of the first service.

[0348] As an embodiment, when the fourth session set includes the second session set, the second node N02 suspends or releases the first unicast bearer.

[0349] As an embodiment, when the fourth session set includes the second session set, the second node N02 stops transmitting data of the first service.

[0350] As an embodiment, in response to receiving the third message, the second node N02 sends a second signaling, where the second signaling is used to instruct the first service to stop being sent via the PTP mode.

[0351] As an embodiment, in response to receiving the third message, the second node N02 sends a second signaling, where the second signaling is used to instruct the session of the first service to stop being sent in a PTP manner.

[0352] As an embodiment, in response to receiving the third message, the second node N02 sends a second signaling, where the second signaling is used to instruct the session indicated by the fourth session set of the first service to stop sending in a PTP manner.

[0353] As an embodiment, the first node is switched from a first source cell to the second node N02, the first source cell sends the first service in a PTM manner; the second node N02 sends the first service in a PTP manner.

[0354] As a sub-embodiment of this embodiment, the first message and the measurement report are multiplexed in the same RRC message.

[0355] As a sub-embodiment of this embodiment, the first message includes RRCReconfigurationComplete.

[0356] As a sub-embodiment of this embodiment, the RRCReconfigurationComplete message carries the first message.

[0357] As a sub-embodiment of this embodiment, the RRCReconfigurationComplete message is the first message.

[0358] As an embodiment, the RRCReconfigurationComplete message carries the first message.

[0359] As an embodiment, the second node N02 forwards the first session set of the first service to a target cell.

[0360] As a sub-embodiment of this embodiment, the target cell is a target cell to which the first node U01 switches.

[0361] As an embodiment, the first node U01 sends an initial message before sending the first message, and the initial message is used to indicate the initial session set of the first service, the initial session set includes at least one session, and the initial session set includes the session of the first service of interest.

[0362] As a sub-embodiment of this embodiment, the intersection of the first session set and the initial session set is empty.

[0363] As an embodiment, the sessions included in the first session set are all sessions of the first service that the first node is interested in; the first node is interested in the sessions in the first session subset.

[0364] As an embodiment, the sentence “the first node is interested in the sessions in the first session subset” includes the following meaning: data in the first session subset is being received.

[0365] As an embodiment, the sentence "the first node is interested in the sessions in the first session subset" includes the following meaning: being interested in receiving data in the first session subset in a PTP manner.

[0366] As an embodiment, the sentence "the first node is interested in the sessions in the first session subset" includes the following meaning: data in the first session subset can only be received in PTP mode.

[0367] As an embodiment, the sentence "the first node is interested in the sessions in the first session subset" includes the following meaning: data in the first session subset can be received in a PTP manner.

[0368] As an embodiment, the sentence “the first node is interested in sessions in the first session subset” includes the following meaning: subscribing to sessions in the first session subset.

[0369] As an embodiment, the sentence "the first node is interested in the sessions in the first session subset" includes the following meaning: joining the multicast group used to carry data in the first session subset.

[0370] As an embodiment, the sentence “the first node is interested in the sessions in the first session subset” includes the following meaning: the user indicates interest in the services in the first session subset.

[0371] As an embodiment, the sentence "the first node is interested in the sessions in the first session subset" includes the following meaning: for any session in the first session subset, the first node has single-cell point-to-multipoint capability, and the first node is receiving or interested in receiving through SC-MRB or MRB, and the session of the first service in the first session subset is in progress or is about to start, and one or more service area identifiers of the first service in the first session subset are included in the multicast-related SIB of the PCell.

[0372] As an embodiment, the sentence "the first node is interested in the sessions in the first session subset" includes the following meaning: for any session in the first session subset, the first node has single-cell point-to-multipoint capability, and the first node is receiving or interested in receiving through SC-MRB or MRB, and the session of the first service in the first session subset is in progress or is about to start, and one or more service area identifiers of the first service in the first session subset are included in the multicast-related SIB of the PCell and the multicast-related SIB is sent on the frequency of interest.

[0373] As an embodiment, when the target cell is configured with PTP to transmit the sessions in the first session set, and the current cell only provides PTM to transmit the sessions in the first session set, and the first node U01 is configured with conditional switching (CHO) or conditional reconfiguration, conditional switching (CHO) or conditional reconfiguration is triggered.

[0374] As a sub-embodiment of this embodiment, the target cell is the first node N02.

[0375] As an embodiment, when the target cell is configured with PTP to transmit the sessions in the first session set, and the current cell only provides PTM to transmit the sessions in the first session set, and the first node U01 is configured with conditional switching (CHO) or conditional reconfiguration, conditional switching (CHO) or conditional reconfiguration is executed.

[0376] As a sub-embodiment of this embodiment, the target cell is the first node N02.

[0377] Example 6

[0378] Embodiment 6 illustrates a wireless signal transmission flow chart according to an embodiment of the present application, as shown in the attached Figure 6 Attached Figure 6 In the example, U11 corresponds to the first node of the present application, and N12 corresponds to the second 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. Example 6 is based on Example 5. For the steps required in Example 6 but not shown in detail, reference can be made to Example 5.

[0379] for First node U11 , receiving the second data in step S6101; receiving the first signaling in step S6102; sending the first message in step S6103; sending the third message in step S6104;

[0380] for Second node N12 , sending the second data in step S6201; sending the first signaling in step S6202; receiving the first message in step S6203; receiving the third message in step S6204.

[0381] As an embodiment, the second node N12 is a service cell of the first node U11.

[0382] As an embodiment, the second node N12 is a relay node of the first node U11.

[0383] As an embodiment, the first service is a non-unicast service.

[0384] As an embodiment, the first service is a broadcast service.

[0385] As an embodiment, the first service is a multicast service.

[0386] As an embodiment, the second data belongs to the first service.

[0387] As an embodiment, the second data is a MAC PDU, and the link layer identity included in the DST field of the header of the MAC PDU identifies a multicast group.

[0388] As an embodiment, the second data is data above the MAC layer, and the link layer identity included in the DST field of the header of the MAC PDU carrying the first data identifies a multicast group.

[0389] As an embodiment, the second data includes PDCP PDU.

[0390] As an embodiment, the second data includes PDCP SDU.

[0391] As an embodiment, the second data includes RLC PDU.

[0392] As an embodiment, the second data includes a MAC PDU.

[0393] As an embodiment, the second data includes data of the QoS flow of the first service.

[0394] As an embodiment, the second data includes higher-layer data of the first service.

[0395] As an embodiment, the second data is sent in a PTM manner.

[0396] As an embodiment, the second data belongs to a session in the first session set of the first service.

[0397] As an embodiment, the second data belongs to a session outside the first session set of the first service.

[0398] As an embodiment, the first signaling indicates that the first service is sent in a PTP manner.

[0399] As an embodiment, the first signaling indicates that the sessions in the second session set of the first service are sent in a PTP manner.

[0400] As an embodiment, the first signaling indicates that the transmission mode of the sessions in the second session set of the first service is switched from PTM to PTP.

[0401] As an embodiment, the first signaling is sent in a broadcast manner.

[0402] As an embodiment, the first signaling is sent in a unicast manner.

[0403] As an embodiment, when the first signaling does not explicitly indicate the session of the first service, by default, the second session set is determined to include all sessions of the first service.

[0404] As an embodiment, when the first signaling does not explicitly indicate the session of the first service, by default, the second session set is determined to include all sessions of the first service that are about to be transmitted.

[0405] As an embodiment, when the first message does not explicitly indicate the session of the first service, by default, the first session set is determined to include all sessions of the first service.

[0406] As an embodiment, when the first message does not explicitly indicate the session of the first service, by default, the first session set is determined to include all sessions of the first service that are about to be transmitted.

[0407] As an embodiment, the third message has the same domain as the first message.

[0408] Example 7

[0409] Embodiment 7 illustrates a schematic diagram of a first message according to an embodiment of the present application being used to determine that first data is sent through a first unicast bearer, as shown in the attached figure. Figure 7 shown.

[0410] As an embodiment, the second node is the service cell of the first node.

[0411] As an embodiment, the second node is a relay node of the first node.

[0412] As an embodiment, when the first data belongs to a session in the first session set of the first session indicated by the first message, the first data is sent through a first unicast bearer.

[0413] As an embodiment, when the first signaling indicates that the transmission mode of the first service includes PTP, when the first data belongs to a session in the first session set of the first session indicated by the first message, the first data is sent through a first unicast bearer.

[0414] As an embodiment, when the first data belongs to a session in the first session set of the first session indicated by the first message, the first data stops being sent through the first unicast bearer.

[0415] As an embodiment, the second node checks each data packet of the first service, and the data packet is sent only if it belongs to a session in the first session set of the first session indicated by the first message, and the first data is one of the data packets.

[0416] As an embodiment, the first data includes all data belonging to the first session set.

[0417] As an embodiment, when the first data belongs to a session in the first session set of the first session indicated by the first message, and the first unicast bearer has not been established or configured, the second node instructs to establish or configure the first unicast bearer.

[0418] As an embodiment, the second node discards data that does not belong to the first session set.

[0419] As a sub-embodiment of this embodiment, the discarded data belongs to PDCP PDU.

[0420] As a sub-embodiment of this embodiment, the discarded data belongs to PDCP SDU.

[0421] As a sub-embodiment of this embodiment, the discarded data belongs to RLC PDU.

[0422] As a sub-embodiment of this embodiment, the discarded data belongs to MAC PDU.

[0423] As an embodiment, before sending the first data, the second node instructs the first node to rebuild the first unicast bearer.

[0424] As an embodiment, before sending the first data, the second node instructs the first node to rebuild the RLC entity corresponding to the first unicast bearer.

[0425] As an embodiment, when the third session set included in the first message includes the second session set, the second node stops sending data of the first service through the first unicast bearer.

[0426] As an embodiment, when the third message indicates that the second node is no longer interested in the third session of the first service, the second node stops sending data of the third session of the first service through the first unicast bearer, and the third session belongs to the first session set.

[0427] As an embodiment, when the third message indicates that all sessions in the first session set of the first service are no longer of interest, the second node stops sending the first service data through the first unicast bearer.

[0428] As a sub-embodiment of this embodiment, the second node instructs the release of the first unicast bearer.

[0429] As a sub-embodiment of this embodiment, the first node releases the first unicast bearer.

[0430] As a sub-embodiment of this embodiment, the first node suspends the first unicast bearer.

[0431] As an embodiment, the third message includes the third session set.

[0432] As an embodiment, the first message indicates that the first node expects to receive data of sessions in the first session set of the first service in a PTP manner.

[0433] As an embodiment, when the first unicast bearer is in a suspended state, the first data triggers the recovery of the first unicast bearer.

[0434] Example 8

[0435] Embodiment 8 illustrates a schematic diagram of a first unicast bearer according to an embodiment of the present application, as shown in the attached figure. Figure 8 Attached Figure 8 The dotted line in represents the protocol entity involved in the first radio bearer.

[0436] The first unicast bearer may be a DRB, which is independent of the radio bearer that transmits data in a PTM manner; Figure 8 Another possible implementation is shown, where the first unicast bearer and the radio bearer for PTM transmission data share some protocol entities; further, within a service cell, PTP transmission and PTM transmission can exist simultaneously.

[0437] In the attached Figure 8In (a), the data of the first service is transmitted using a PDCP entity, PDCP-1; the PDCP-1 entity sends the generated PDCP PDU to two RLC entities respectively, where RLC-1 is responsible for PTM transmission; RLC-2 is responsible for PTP transmission; RLC-1 and RLC-2 can use the same transmission mode or different transmission modes, for example, one uses AM and the other uses UM; the RLC PDU generated by RLC-1 and the PDU generated by RLC-2 are sent to their respective MAC entities, MAC-1 and MAC-2, and the data processed by the MAC layer are then sent to the physical layer respectively. In (a), the protocol entities included or associated with the first unicast bearer include the PDCP-1 entity, the RLC-2 entity, the MAC-2 entity and the physical layer entity. The first PTM bearer is a wireless bearer that uses PTM to transmit the data of the first service, and the protocol entities included or associated with the first PTM bearer include the PDCP-1 entity, the RLC-1 entity, the MAC-1 entity and the physical layer entity.

[0438] As an embodiment, the first PTM bearer and the first unicast bearer are simultaneously configured with a service cell.

[0439] As an embodiment, the MAC PDUs generated by MAC-1 and MAC-2 occupy the same physical channel.

[0440] As an embodiment, both MAC-1 and MAC-2 support HARQ.

[0441] As an embodiment, the first PTM bearer and the first unicast bearer exist simultaneously.

[0442] As an embodiment, the first PTM bearer transmits the same PDCP SDU as the first unicast bearer.

[0443] As an embodiment, the first PTM bearer and the first unicast bearer are both active.

[0444] As an embodiment, one of the first PTM bearer and the first unicast bearer is in an active state, and the other is in a suspended state.

[0445] As an embodiment, the first PTM bearer and the first unicast bearer use the same bearer identity.

[0446] As an embodiment, the first PTM bearer and the first unicast bearer use different transmission mode identities or indexes or identifiers.

[0447] As an embodiment, the first PTM bearer and the first unicast bearer use different configuration indexes.

[0448] As an embodiment, the PDCP PDU sent by the PDCP-1 entity of the first PTM bearer and the first unicast bearer to RLC-1 and RLC-2 is the same.

[0449] As an embodiment, the PDCP PDU sent by the PDCP-1 entity of the first PTM bearer and the first unicast bearer to RLC-1 and RLC-2 uses different encryption keys.

[0450] As an embodiment, the PDCP PDU sent by the PDCP-1 entity of the first PTM bearer and the first unicast bearer includes a first field, and the first field indicates the context of the security algorithm adopted by the PDCP PDU.

[0451] As an embodiment, the PDCP PDU sent by the PDCP-1 entity of the first PTM bearer and the first unicast bearer includes a first field, and the first field indicates the key identity of the security algorithm adopted by the PDCP PDU.

[0452] As a sub-embodiment of this embodiment, a value of the first field of the PDCP PDU carried by the first PTM is different from a value of the first field of the PDCP PDU carried by the first unicast.

[0453] As an embodiment, the first unicast bearer is a service provided to a higher layer for transmitting data in a PTP manner.

[0454] As an embodiment, the RLC status report received by the RLC entity responsible for PTP transmission is used to determine whether the RLC entity responsible for PTM transmission retransmits data.

[0455] As an embodiment, the RLC status report is only received by the RLC entity responsible for the PTP transmission.

[0456] As an embodiment, the RLC status report is only processed by the RLC entity responsible for PTP transmission.

[0457] As an embodiment, PDCP-1 sends PDCP PDU to only one entity in RLC-1 or RLC-2.

[0458] As a sub-embodiment of this embodiment, both the first PTM bearer and the first unicast bearer are in active state.

[0459] As an embodiment, the advantage of the above method is that data transmission is more flexible, PDCP can retransmit data as needed, and the retransmitted data can be sent only through PTM or PTP.

[0460] As an embodiment, when the serving cell instructs one of the first PTM bearer and the first unicast bearer to suspend or stop transmitting data, the first node sends a PDCP status report.

[0461] As an embodiment, when the serving cell instructs one of the first PTM bearer and the first unicast bearer to suspend or stop transmitting data, the first node sends an RLC status report.

[0462] As an embodiment, when the serving cell indicates that the transmission mode of the data of the first service switches between PTM and PTP, the first node sends an RLC status report.

[0463] As a sub-embodiment of this embodiment, the serving cell indicates through the first signaling that the transmission mode of the data of the first service is switched between PTM and PTP.

[0464] As an embodiment, when the serving cell indicates that the transmission mode of the data of the first service switches between PTM and PTP, the first node sends a PDCP status report.

[0465] As a sub-embodiment of this embodiment, the serving cell indicates through the first signaling that the transmission mode of the data of the first service is switched between PTM and PTP.

[0466] As an embodiment, when RLC-1 is reconfigured to transmit a service other than the first service or a session other than a current session of the first service, PDCP-1 is reestablished.

[0467] As an embodiment, when RLC-1 is reconfigured to transmit a service other than the first service or a session other than a current session of the first service, RLC-1 is reestablished.

[0468] As an embodiment, RLC-1 receives an RLC status report, which triggers PDCP-1 to retransmit the unreceived PDCP SDU determined by the RLC status report received by RLC-1.

[0469] As an embodiment, RLC-2 receives an RLC status report, which triggers PDCP-1 to retransmit the unreceived PDCP SDU determined by the RLC status report received by RLC-2.

[0470] In the attached Figure 8In (b), the data of the first service is transmitted using a PDCP entity, PDCP-2; the PDCP-2 entity sends the generated PDCP PDU to an RLC entity, RLC-3; RLC-3 sends the generated RLC PDU to two MAC entities, MAC-3 and MAC-4 respectively, and the data processed by the MAC layer is then sent to the physical layer respectively. Among them, MAC-3 is responsible for PTM transmission, and MAC-4 is responsible for PTP transmission. In (b), the protocol entities included or associated with the first unicast bearer include a PDCP-2 entity, an RLC-3 entity, a MAC-4 entity and a physical layer entity. The first PTM bearer is a wireless bearer that transmits the data of the first service using PTM, and the protocol entities included or associated with the first PTM bearer include a PDCP-2 entity, an RLC-3 entity, a MAC-3 entity and a physical layer entity.

[0471] As an embodiment, the RLC PDU sent by RLC-3 to MAC-3 and MAC-4 is the same.

[0472] As an embodiment, the RLC PDUs sent by RLC-3 to MAC-3 and MAC-4 are different.

[0473] As an embodiment, the RLC PDU sent by RLC-3 to MAC-3 and MAC-4 has an independent segmentation method.

[0474] As an embodiment, the MAC PDUs generated by MAC-3 and MAC-4 use the same logical channel identity.

[0475] As an embodiment, the MAC PDUs generated by MAC-3 and MAC-4 use different logical channel identities.

[0476] As an embodiment, the MAC PDU generated by MAC-3 and MAC-4 uses different identity transmission modes; the transmission modes include PTM and PTP.

[0477] As an embodiment, the MAC PDUs generated by MAC-3 and MAC-4 occupy the same physical channel.

[0478] As an embodiment, both MAC-3 and MAC-4 support HARQ.

[0479] As an embodiment, MAC-3 does not use HARQ; MAC-4 uses HARQ.

[0480] As an embodiment, the header of the MAC PDU sent by MAC-4 includes a link layer identity indicated by a DST field identifying the first node.

[0481] As an embodiment, the first data belongs to an attached Figure 8 The data of the first business.

[0482] As an embodiment, the first data includes Figure 8 The data of the first business.

[0483] As an embodiment, when RLC-3 is reconfigured to transmit services other than the first service or sessions other than the current session of the first service, PDCP-2 is reestablished.

[0484] As an embodiment, when RLC-3 is reconfigured to transmit a service other than the first service or a session other than a current session of the first service, RLC-3 is reestablished.

[0485] As an embodiment, the RLC status report received by RLC-3 is used to trigger PDCP-2 to retransmit the unreceived PDCP SDUs determined by the RLC status report received by RLC-3.

[0486] Example 9

[0487] Embodiment 9 illustrates a schematic diagram of message and data transmission according to an embodiment of the present application, as shown in the attached Fig. 9 Attached Fig. 9 Node A in corresponds to the first node of this application.

[0488] As an embodiment, node B and node C form the second node of this application; the node B is the CU (Central Unit) of the service cell of the node A, and the node B is the DU (Distributed Unit) of the service cell of the node A; the node B receives the first message; the node B sends the second message; the node B sends the first signaling, and the node B receives the third message; the node C sends the first data; the first unicast bearer is the user-plane wireless bearer from the node C to the node A; the first message indicates that the node A wishes to receive the session in the first session set of the first service sent by the node C in a PTP manner; the first message includes the identity of the node C; the second message indicates the transmission mode of the first service sent by the node C; the second message includes the identity of the node C.

[0489] As an embodiment, the second node of the present application is a cell group, Fig. 9 The Node B in the cell group is the PCell of the cell group; Fig. 9Node C in the Scell ​​is the Scell ​​of the cell group; the node B receives the first message; the node B sends the second message; the node B sends the first signaling, and the node B receives the third message; the node C sends the first data; the first unicast bearer is the user-plane wireless bearer from the node C to the node A; the first message indicates that the node A wishes to receive the session in the first session set of the first service sent by the node C in a PTP manner; the first message includes the identity of the node C; the second message indicates the transmission mode of the first service sent by the node C; the second message includes the identity of the node C; the second message includes the configuration of the node C; the second message is used to configure the node C; when a wireless link failure is detected, the node A abandons suspending the first unicast bearer.

[0490] As an example, Fig. 9 Node B in the example is the serving cell of Node A; Fig. 9 Node C in the embodiment is a relay; Node C forwards the first data through the first unicast bearer; Node A is a remote UE; when Node C receives data from Node B, and the received data does not belong to a session in the first session set, Node C abandons sending the data; Node C uses Layer 2 to forward the first data, or Node C uses Layer 3 to forward the first data.

[0491] As a sub-embodiment of this embodiment, the node A directly indicates the first session set of the first service to the node B, or the node A indicates the first session set of the first service to the node B through the node C.

[0492] As a sub-embodiment of this embodiment, the node A only sends the first message to the node C.

[0493] As a sub-embodiment of this embodiment, the node A only sends the first session set of the first service to the node C; and does not send the first session set of the first service to the node B.

[0494] As a sub-embodiment of this embodiment, the node A only sends the first session set of the first service to the node B; and does not send the first session set of the first service to the node C.

[0495] As a sub-embodiment of this embodiment, the node A sends the first session set of the first service to the node C; and also sends the first session set of the first service to the node B.

[0496] Example 10

[0497] Embodiment 10 illustrates a schematic diagram of a first reception quality lower than a first threshold being used to trigger a first transmitter to send a first message according to an embodiment of the present application, wherein the first transmitter is a transmitter of the first node, as shown in the attached Fig.10 shown.

[0498] As an embodiment, the first node receives a first reference signal, the first node performs a first measurement on the first reference signal, and a result of the first measurement is a first reception quality.

[0499] As a sub-embodiment of this embodiment, the first reference signal includes a CSI-RS.

[0500] As a sub-embodiment of this embodiment, the first reference signal includes an SS / PBCH block.

[0501] As a sub-embodiment of this embodiment, the first reference signal includes SSB.

[0502] As a sub-embodiment of this embodiment, the first reference signal includes a DM-RS.

[0503] As a sub-embodiment of this embodiment, the first reference signal includes a CRS.

[0504] As a sub-embodiment of this embodiment, the first measurement includes measuring RSRP.

[0505] As a sub-embodiment of this embodiment, the first measurement includes measuring RSRQ.

[0506] As a sub-embodiment of this embodiment, the first measurement includes measuring RSSI.

[0507] As a sub-embodiment of this embodiment, the first measurement includes measuring SNR.

[0508] As a sub-embodiment of this embodiment, the first reception quality includes an RSRP value.

[0509] As a sub-embodiment of this embodiment, the first reception quality includes an RSRQ value.

[0510] As a sub-embodiment of this embodiment, the first reception quality includes an RSSI value.

[0511] As a sub-embodiment of this embodiment, the first reception quality includes an SNR value.

[0512] As a sub-embodiment of this embodiment, the first reception quality includes an estimated BLER.

[0513] As a sub-embodiment of this embodiment, the first reception quality includes an estimated BER.

[0514] As a sub-embodiment of this embodiment, the first threshold includes a real number.

[0515] As a sub-embodiment of this embodiment, the unit of the first threshold is dB.

[0516] As a sub-embodiment of this embodiment, the first service is sent in PTM mode, and the first reception quality is lower than the first threshold, and the first node sends the first message; the first message is used to trigger the session in the first session set of the first service to be sent in PTP mode.

[0517] As an embodiment, the first node receives the first service in a PTM manner, the first node performs a second measurement on data of the first service, and a result of the second measurement is a first reception quality.

[0518] As a sub-embodiment of this embodiment, the PTM mode of receiving the first service includes using a multicast bearer, and the multicast bearer includes MRB or SC-MRB.

[0519] As a sub-embodiment of this embodiment, the second measurement includes measuring BLER.

[0520] As a sub-embodiment of this embodiment, the second measurement includes measuring BER.

[0521] As a sub-embodiment of this embodiment, the second measurement includes measuring a packet error rate.

[0522] As a sub-embodiment of this embodiment, the second measurement includes measuring FER.

[0523] As a sub-embodiment of this embodiment, the second measurement includes measuring delay.

[0524] As a sub-embodiment of this embodiment, the second measurement includes measuring the number of packets that meet the delay requirement.

[0525] As a sub-embodiment of this embodiment, the second measurement includes measuring a packet loss rate.

[0526] As a sub-embodiment of this embodiment, the second measurement includes measuring the number of RLC retransmissions.

[0527] As a sub-embodiment of this embodiment, the second measurement includes measuring the RLC retransmission rate.

[0528] As a sub-embodiment of this embodiment, the second measurement includes measuring the number of HARQ times.

[0529] As a sub-embodiment of this embodiment, the second measurement includes measuring a HARQ retransmission rate.

[0530] As a sub-embodiment of this embodiment, the second measurement includes measuring delay jitter.

[0531] As a sub-embodiment of this embodiment, the second measurement includes layer 2 measurement.

[0532] As a sub-embodiment of this embodiment, the first reception quality includes BLER.

[0533] As a sub-embodiment of this embodiment, the first reception quality includes BER.

[0534] As a sub-embodiment of this embodiment, the first reception quality includes a packet error rate.

[0535] As a sub-embodiment of this embodiment, the first reception quality includes FER.

[0536] As a sub-embodiment of this embodiment, the first reception quality includes delay.

[0537] As a sub-embodiment of this embodiment, the first reception quality includes the number of packets that meet the delay requirement.

[0538] As a sub-embodiment of this embodiment, the first reception quality includes a packet loss rate.

[0539] As a sub-embodiment of this embodiment, the first reception quality includes the number of RLC retransmissions.

[0540] As a sub-embodiment of this embodiment, the first reception quality includes an RLC retransmission rate.

[0541] As a sub-embodiment of this embodiment, the first reception quality includes the number of HARQ times.

[0542] As a sub-embodiment of this embodiment, the first reception quality includes a HARQ retransmission rate.

[0543] As a sub-embodiment of this embodiment, the first reception quality includes delay jitter.

[0544] As a sub-embodiment of this embodiment, the first reception quality includes a result of layer 2 measurement.

[0545] Example 10a

[0546] Embodiment 10a illustrates a schematic diagram of a segment according to an embodiment of the present application, as shown in the attached Fig.10a As shown; attached Fig.10a Each rectangular box in represents a segment, and there are M segments in total, where M is a positive integer.

[0547] As an embodiment, the first message is used to indicate a first segment identity set of a first session, the first session belongs to a first session set, each identity in the first segment identity set corresponds to a segment of the first session, and the first session includes N segments, where N is a positive integer; wherein the first segment identity set includes M identities, M is a positive integer not greater than N, and the first data belongs to a segment corresponding to an identity in the first segment identity set.

[0548] As an embodiment, M is equal to N.

[0549] As an embodiment, M is less than N.

[0550] As an embodiment, the first segment set includes and only includes M segments corresponding to the M identities included in the first segment identity set.

[0551] As an embodiment, the segment is a segment.

[0552] As an embodiment, the segment is a section.

[0553] As an example, Fig.10a The lengths of each segment in can be equal or unequal.

[0554] As an embodiment, N is equal to 1.

[0555] As an embodiment, N is greater than 1.

[0556] As an embodiment, the first segment identity set includes Timestamp.

[0557] As a sub-embodiment of this embodiment, each segment in the first segment set is determined by a time period, and the start and end time of the time period is determined by the Timestamp.

[0558] As an embodiment, the first segment identity set includes volume.

[0559] As a sub-embodiment of this embodiment, each segment in the first segment set is determined by a volume interval, and the volume interval is determined by the volume included in the first segment identity set.

[0560] As a sub-embodiment of this embodiment, the volume includes bits or bytes.

[0561] As a sub-embodiment of this embodiment, the volume includes files.

[0562] As a sub-embodiment of this embodiment, the volume includes chapters.

[0563] As a sub-embodiment of this embodiment, the volume includes natural paragraphs.

[0564] As a sub-embodiment of this embodiment, the volume includes a clip number.

[0565] As a sub-embodiment of this embodiment, the volume includes a section.

[0566] As a sub-embodiment of this embodiment, the volume is a data volume.

[0567] As an embodiment, the first segment identity set includes percentages.

[0568] As a sub-embodiment of this embodiment, each segment in the first segment set is determined by a percentage interval, and the percentage interval is determined by a percentage included in the first segment identity set.

[0569] As an embodiment, the first segment identity set includes bit or byte values.

[0570] As a sub-embodiment of this embodiment, each segment in the first segment set is determined by a bit or byte interval, and the bit or byte interval is determined by the bit or byte value included in the first segment identity set.

[0571] As an embodiment, the first segment identity set includes the SN of the PDCP or higher layer PDU.

[0572] As a sub-embodiment of this embodiment, each segment in the first segment set is determined by an SN interval of a PDCP or higher layer PDU, and the SN interval of the PDCP or higher layer PDU is determined by the SN of the PDCP or higher layer PDU included in the first segment identity set.

[0573] As an embodiment, the first data belongs to the segment corresponding to the identity included in the first segment identity set.

[0574] As an embodiment, the first data belongs to a segment in the first segment set.

[0575] As an embodiment, when the third data belongs to the first session but does not belong to a segment in the first segment set, the second node abandons sending the third data.

[0576] As an embodiment, the first message is used to indicate that the first node is interested in receiving data of segments in the first set of segments.

[0577] As an embodiment, the first message is used to indicate that the first node is not interested in receiving data of segments outside the first set of segments of the first session of the first service.

[0578] As an embodiment, the first message is used to indicate that the first node is interested in receiving data of segments in the first segment set in a PTP manner.

[0579] As an embodiment, the first message is used to indicate that the first node is interested in receiving data of segments in the first segment set through a first radio bearer.

[0580] Embodiment 11

[0581] Embodiment 11 illustrates a structural block diagram of a processing device used in a first node according to an embodiment of the present application; Fig.11 As shown in the attached Fig.11 In the embodiment 11, the processing device 1100 in the first node includes a first receiver 1101 and a first transmitter 1102.

[0582] A first transmitter 1102 sends a first message, where the first message is used to indicate a first session set of a first service, where the first session set includes at least one session;

[0583] The first receiver 1101 receives a second message indicating a first unicast bearer; and receives first data through the first unicast bearer.

[0584] The first data belongs to a session in the first session set of the first service; the first service is a multicast broadcast service; and the first message is used to determine that the first data is sent through the first unicast bearer.

[0585] As an embodiment, the first message indicates a third session set, the third session set includes sessions of the first service that are not of interest, the third session set is used to determine the first session set; the first session set only includes sessions other than the third session set.

[0586] As an embodiment, the first receiver 1101 receives first signaling, where the first signaling includes a second session set of the first service.

[0587] When the intersection of the second session set and the third session set is not empty, the first transmitter 1102 sends the first message in response to receiving the first signaling.

[0588] As an embodiment, the first message is used to indicate a first segment identity set of a first session, the first session belongs to a first session set, each identity in the first segment identity set corresponds to a segment of the first session, and the first session includes N segments, where N is a positive integer; wherein the first segment identity set includes M identities, M is a positive integer not greater than N, and the first data belongs to a segment corresponding to an identity in the first segment identity set.

[0589] As an embodiment, the first transmitter 1102 sends a third message, where the third message is used to indicate that the user is no longer interested in the session of the first service.

[0590] As an embodiment, the first message includes a recommended mode of an RLC entity for a radio bearer that carries the first service.

[0591] As an embodiment, the first receiver 1101 determines a first reception quality, where the first reception quality is the reception quality of the first service, and the first reception quality is lower than a first threshold and is used for triggering, and the first transmitter 1102 sends the first message.

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

[0593] As an embodiment, the first node is a terminal supporting a large delay difference.

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

[0595] As an embodiment, the first node is an aircraft.

[0596] As an embodiment, the first node is a vehicle-mounted terminal.

[0597] As an embodiment, the first node is a relay.

[0598] As an embodiment, the first node is a vessel.

[0599] As an embodiment, the first node is an Internet of Things terminal.

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

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

[0602] As an embodiment, the first receiver 1101 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.

[0603] As an embodiment, the first transmitter 1102 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 Embodiment 4.

[0604] Example 12

[0605] Embodiment 12 illustrates a structural block diagram of a processing device used in a second node according to an embodiment of the present application; Fig.12 As shown in the attached Fig.12 In the embodiment 12, the processing device 1200 in the second node includes a second transmitter 1201 and a second receiver 1202.

[0606] A second receiver 1202 receives a first message, where the first message is used to indicate a first session set of a first service, where the first session set includes at least one session;

[0607] The second transmitter 1201 sends a second message, where the second message indicates a first unicast bearer; and receives first data through the first unicast bearer;

[0608] The first data belongs to a session in the first session set of the first service; the first service is a multicast broadcast service; and the first message is used to determine that the first data is sent through the first unicast bearer.

[0609] As an embodiment, the first message indicates a third session set, the third session set includes sessions of the first service that are not of interest, the third session set is used to determine the first session set; the first session set only includes sessions other than the third session set.

[0610] As an embodiment, the second transmitter 1201 sends a first signaling, where the first signaling includes a second session set of the first service;

[0611] When the intersection of the second session set and the third session set is not empty, the first message is sent as a response to receiving the first signaling.

[0612] As an embodiment, the first message is used to indicate a first segment identity set of a first session, the first session belongs to a first session set, each identity in the first segment identity set corresponds to a segment of the first session, and the first session includes N segments, where N is a positive integer; wherein the first segment identity set includes M identities, M is a positive integer not greater than N, and the first data belongs to a segment corresponding to an identity in the first segment identity set.

[0613] As an embodiment, the second receiver 1202 receives a third message, where the third message is used to indicate that the user is no longer interested in the session of the first service.

[0614] As an embodiment, the first message includes a recommended mode of an RLC entity for a radio bearer that carries the first service.

[0615] As an embodiment, the sender of the first message determines a first reception quality, where the first reception quality is the reception quality of the first service, and the first reception quality being lower than a first threshold is used to trigger sending the first message.

[0616] As an embodiment, the second node is a base station.

[0617] As an embodiment, the second node is a satellite.

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

[0619] As an embodiment, the second node is a gateway.

[0620] As an embodiment, the second node is a base station supporting a large delay difference.

[0621] As an embodiment, the second transmitter 1201 includes at least one of the antenna 420, transmitter 418, transmit processor 416, multi-antenna transmit processor 471, controller / processor 475, and memory 476 in Embodiment 4.

[0622] As an embodiment, the second receiver 1202 includes at least one of the antenna 420, the receiver 418, the receiving processor 470, the multi-antenna receiving processor 472, the controller / processor 475, and the memory 476 in Embodiment 4.

[0623] A person of ordinary skill in the art can understand that all or part of the steps in the above method can be completed by instructing the 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 function module, and the present application is not limited to any specific form of software and hardware combination. 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, tablet computers, notebooks, vehicle-mounted communication equipment, wireless sensors, Internet cards, Internet of Things terminals, RFID terminals, NB-IoT terminals, MTC (Machine Type Communication, machine type communication) terminals, eMTC (enhanced MTC, enhanced MTC) terminals, data cards, Internet cards, vehicle-mounted communication equipment, low-cost mobile phones, low-cost tablet computers, satellite communication equipment, ship communication equipment, NTN user equipment and other wireless communication equipment. 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), NTN base stations, satellite equipment, flight platform equipment and other wireless communication equipment.

[0624] The above is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A first node for wireless communication, wherein: include: A first transmitter sends a first message, where the first message is used to indicate a first session set of a first service, where the first session set includes at least one session; A first receiver receives a second message, where the second message indicates a first unicast bearer; receiving first data through the first unicast bearer; The first transmitter sends a third message, where the third message is used to indicate that the user is no longer interested in the session of the first service; Among them, the first data belongs to a session in the first session set of the first service; the first service is a multicast broadcast service; the first message is used to determine that the first data is sent through the first unicast bearer; the first message indicates a third session set, the third session set includes sessions of the first service that are not of interest, and the third session set is used to determine the first session set; the first session set only includes sessions outside the third session set; the first message implicitly indicates the third session set.

2. The first node according to claim 1, characterized in that: The first unicast bearer is a PTP branch in a multicast bearer.

3. The first node according to claim 1 or 2, characterized in that: include: The first receiver receives a first signaling, where the first signaling includes a second session set of the first service; The first transmitter, when the intersection of the second session set and the third session set is not empty, sends the first message as a response to receiving the first signaling.

4. The first node according to any one of claims 1 to 3, characterized in that: The first message is used to indicate a first segment identity set of a first session, the first session belongs to the first session set, each identity in the first segment identity set corresponds to a segment of the first session, and the first session includes N segments, where N is a positive integer; The first segment identity set includes M identities, where M is a positive integer not greater than N, and the first data belongs to a segment corresponding to an identity in the first segment identity set.

5. The first node according to any one of claims 1 to 3, characterized in that: The sending of the first message is triggered by a change in the transmission mode of the session in the first session set of the first service.

6. The first node according to claim 1, characterized in that: The first message includes a recommended mode of an RLC entity for a radio bearer carrying the first service.

7. The first node according to any one of claims 1 to 6, characterized in that: The second message and the first data are both received from a second node.

8. The first node according to claim 1, characterized in that: The user service description (USD, User Service Description) pre-stored in the first node includes information of the first service; the first service is a broadcast service registered by the first node through NAS (Non-Access Stratum); the first message includes TMGI, and the TMGI indicates the first service; the first unicast bearer includes MRB transmitted in PTP (Point to point) mode.

9. The first node according to claim 1, characterized in that: The first message implicitly indicates the first session set.

10. A second node for wireless communication, wherein: include: A second receiver receives a first message, where the first message is used to indicate a first session set of a first service, where the first session set includes at least one session; A second transmitter sends a second message, where the second message indicates the first unicast bearer; Sending first data through the first unicast bearer; The second receiver receives a third message, where the third message is used to indicate that the second receiver is no longer interested in the session of the first service; Among them, the first data belongs to a session in the first session set of the first service; the first service is a multicast broadcast service; the first message is used to determine that the first data is sent through the first unicast bearer; the first message indicates a third session set, the third session set includes sessions of the first service that are not of interest, and the third session set is used to determine the first session set; the first session set only includes sessions outside the third session set; the first message implicitly indicates the third session set.

11. The second node according to claim 10, characterized in that: The first unicast bearer is a PTP branch in a multicast bearer.

12. The second node according to claim 10 or 11, characterized in that: include: The second transmitter sends a first signaling, where the first signaling includes a second session set of the first service; The intersection of the second session set and the third session set is not empty, and the first signaling is used to trigger the sending of the first message.

13. The second node according to any one of claims 10 to 12, characterized in that: The first message is used to indicate a first segment identity set of a first session, the first session belongs to the first session set, each identity in the first segment identity set corresponds to a segment of the first session, and the first session includes N segments, where N is a positive integer; The first segment identity set includes M identities, where M is a positive integer not greater than N, and the first data belongs to a segment corresponding to an identity in the first segment identity set.

14. The second node according to any one of claims 10 to 13, characterized in that: The sending of the first message is triggered by a change in the transmission mode of the session in the first session set of the first service.

15. The second node according to any one of claims 10 to 14, characterized in that: The first message includes a recommended mode of an RLC entity for a radio bearer for carrying the first service; the first message implicitly indicates the first session set.

16. The second node according to any one of claims 10 to 15, characterized in that: The first message includes a TMGI, where the TMGI indicates the first service; the first unicast bearer includes an MRB transmitted in a PTP (Point to point) manner.

17. The second node according to any one of claims 10 to 16, characterized in that: The first message implicitly indicates the first session set.

18. A method in a first node for wireless communication, wherein: include: Sending a first message, where the first message is used to indicate a first session set of a first service, where the first session set includes at least one session; receiving a second message, wherein the second message indicates a first unicast bearer; receiving first data through the first unicast bearer; Sending a third message, the third message is used to indicate that the session of the first business is no longer interested; Among them, the first data belongs to a session in the first session set of the first service; the first service is a multicast broadcast service; the first message is used to determine that the first data is sent through the first unicast bearer; the first message indicates a third session set, the third session set includes sessions of the first service that are not of interest, and the third session set is used to determine the first session set; the first session set only includes sessions outside the third session set; the first message implicitly indicates the third session set.

19. The method in the first node according to claim 18, characterized in that: The first unicast bearer is a PTP branch in a multicast bearer.

20. The method in the first node according to claim 18 or 19, characterized in that: include: receiving first signaling, where the first signaling includes a second session set of the first service; When the intersection of the second session set and the third session set is not empty, sending the first message as a response to receiving the first signaling.

21. The method in the first node according to any one of claims 18 to 20, characterized in that: The first message is used to indicate a first segment identity set of a first session, the first session belongs to the first session set, each identity in the first segment identity set corresponds to a segment of the first session, and the first session includes N segments, where N is a positive integer; The first segment identity set includes M identities, where M is a positive integer not greater than N, and the first data belongs to a segment corresponding to an identity in the first segment identity set.

22. The method in the first node according to any one of claims 18 to 21, characterized in that: The sending of the first message is triggered by a change in the transmission mode of the session in the first session set of the first service.

23. The method in the first node according to any one of claims 18 to 22, characterized in that: The first message includes a recommended mode of an RLC entity for a radio bearer for carrying the first service, and the first message implicitly indicates the first session set.

24. The method in the first node according to any one of claims 18 to 23, characterized in that: A first reception quality is determined, where the first reception quality is the reception quality of the first service, and the first reception quality being lower than a first threshold is used to trigger sending the first message.

25. The method in the first node according to claim 18, characterized in that: The user service description (USD, User Service Description) pre-stored in the first node includes information of the first service; the first service is a broadcast service registered by the first node through NAS (Non-Access Stratum); the first message includes TMGI, and the TMGI indicates the first service; the first unicast bearer includes MRB transmitted in PTP (Point to point) mode.

26. A method in a second node for wireless communication, wherein: include: receiving a first message, where the first message is used to indicate a first session set of a first service, where the first session set includes at least one session; sending a second message, where the second message indicates the first unicast bearer; receiving first data through the first unicast bearer; receiving a third message, wherein the third message is used to indicate that the user is no longer interested in the session of the first service; Among them, the first data belongs to a session in the first session set of the first service; the first service is a multicast broadcast service; the first message is used to determine that the first data is sent through the first unicast bearer; the first message indicates a third session set, the third session set includes sessions of the first service that are not of interest, and the third session set is used to determine the first session set; the first session set only includes sessions outside the third session set; the first message implicitly indicates the third session set.

27. The method in the second node according to claim 26, characterized in that: The first unicast bearer is a PTP branch in a multicast bearer.

28. The method in the second node according to claim 26 or 27, characterized in that: include: Sending a first signaling, where the first signaling includes a second session set of the first service; The intersection of the second session set and the third session set is not empty, and the first signaling is used to trigger the sending of the first message.

29. The method in the second node according to any one of claims 26 to 28, characterized in that: The first message is used to indicate a first segment identity set of a first session, the first session belongs to the first session set, each identity in the first segment identity set corresponds to a segment of the first session, and the first session includes N segments, where N is a positive integer; The first segment identity set includes M identities, where M is a positive integer not greater than N, and the first data belongs to a segment corresponding to an identity in the first segment identity set.

30. The method in the second node according to any one of claims 26 to 29, characterized in that: The sending of the first message is triggered by a change in the transmission mode of the session in the first session set of the first service.

31. The method in the second node according to any one of claims 26 to 30, characterized in that: The first message includes a recommended mode of an RLC entity for a radio bearer for carrying the first service; the first message implicitly indicates the first session set.

32. The method in the second node according to any one of claims 26 to 31, characterized in that: The first message includes a TMGI, where the TMGI indicates the first service; the first unicast bearer includes an MRB transmitted in a PTP (Point to point) manner.

Images