Communication method and communication device

Abstract

The invention provides a communication method and a communication device, and relates to the technical field of communication. In the method, a relay UE can determine whether to forward a paging message to a remote terminal device according to a first indication message sent by the remote UE and a second indication message carried in the paging message sent by an access network device, if the first indication message is the same as the second indication message, the paging message is determined to be forwarded, and if the second indication message is not the same as the second indication message, the paging message is determined not to be forwarded. The first indication message is used for indicating a first service, the second indication message is used for indicating a second service, and both the first service and the second service comprise multicast services. In this way, the relay terminal device can accurately forward the paging message sent by the access network device to the corresponding remote terminal device, so that the access network device can accurately page the corresponding remote terminal device.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and more specifically, to a communication method and a communication device. Background Art

[0002] UE-to-Network Relay (U2N Relay) is a technology that uses relay terminal equipment to assist remote terminal equipment to communicate with access network equipment. The relay terminal equipment and remote terminal equipment communicate through the sidelink (SL), and the relay terminal equipment and access network equipment communicate through the air interface.

[0003] For unicast service transmission, the relay terminal device can forward the paging information of the access network device to the corresponding remote terminal device. The remote terminal device can switch from an idle state (IDLE) or an inactive state (INACTIVE) to a connected state (CONNECT) based on the paging information and perform unicast service transmission with the access network device.

[0004] For multicast / broadcast services (MBS) transmission, the relay terminal device may not be able to forward the paging information of the access network device to the corresponding remote terminal device, and the access network device cannot accurately page the corresponding remote terminal device. Summary of the invention

[0005] The present application provides a communication method and a communication device, which can support an access network device to accurately page a corresponding remote terminal device.

[0006] In a first aspect, a communication method is provided, which is applied to a first terminal device, and the method includes: receiving a first indication message from a second terminal device, the first indication message being used to indicate a first service, the first service being a service between the second terminal device and an access network device, and the first service including a multicast service; receiving a paging message from the access network device, the paging message including a second indication message, the second indication message being used to indicate a second service, the second service being a service between the second terminal device and the access network device, and the second service including a multicast service; and sending the paging message to the second terminal device according to the first indication message and the second indication message.

[0007] Optionally, the first terminal device determines to send the paging message to the second terminal device based on the first indication message and the second indication message.

[0008] In the above scheme, the first terminal device can determine whether to forward the paging message to the second terminal device according to the first indication message sent by the second terminal device and the second indication message carried in the paging message sent by the access network device. If they are the same, it is determined to be forwarded; if they are not the same, it is determined not to be forwarded. In this way, the first terminal device can accurately forward the paging message from the access network device to the corresponding second terminal device, and the access network device can also accurately page the corresponding second terminal device.

[0009] In a possible implementation manner, the method further includes: sending a first indication message to the access network device.

[0010] When the access network device wants to page the second terminal device, the access network device can carry the first indication message in the paging message, and the first terminal device can accurately forward the paging message from the access network device to the corresponding second terminal device.

[0011] In a possible implementation, the method further includes: sending capability information of the first terminal device to the second terminal device, where the capability information of the first terminal device is used to indicate that the first terminal device supports multicast service transmission.

[0012] In this way, the second terminal device can determine that the first terminal device supports multicast service transmission.

[0013] Optionally, the capability information of the first terminal device may also be used to indicate that the first terminal device does not support multicast service transmission.

[0014] In some implementations of the first aspect, the method further includes: receiving a request message from the second terminal device, where the request message is used to request a capability message of the first terminal device.

[0015] In this way, the first terminal device can send a capability message of the first terminal device to the second terminal device according to the request of the second terminal device.

[0016] In a possible implementation, the request information includes capability information of the second terminal device, where the capability information of the second terminal device is used to indicate that the second terminal device supports multicast service transmission.

[0017] In this way, the first terminal device can determine whether the second terminal device supports multicast service transmission.

[0018] Optionally, the capability information of the second terminal device may also be used to indicate that the first terminal device does not support multicast service transmission.

[0019] In one possible implementation, the method also includes: receiving a first message from an access network device, the first message including a first data packet and a first parameter, the first parameter being used to indicate a first multicast wireless bearer or a first logical channel, the first logical channel belonging to a first interface, the first interface being a communication interface between a first terminal device and an access network device, and the first data packet belonging to a second service; and sending a second message to a second terminal device according to the first parameter, the second message including the first data packet.

[0020] By carrying the first parameter in the first message, the first terminal device can determine to send the first data packet to the second terminal device according to the first parameter, thereby ensuring correct transmission of the second service data.

[0021] In a possible implementation, the method also includes: receiving a configuration message from an access network device, the configuration message including at least one of the following: a first mapping relationship, a second mapping relationship, and a third mapping relationship, the first mapping relationship is used to associate the second terminal device with the first channel, the second mapping relationship is used to associate the first channel with the first multicast wireless bearer, the third mapping relationship is used to associate the second channel with the first multicast wireless bearer, the first data packet is received by the first terminal device through the first channel at the first interface; the first data packet is sent by the first terminal device through the second channel at the second interface, the second interface is a communication interface between the first terminal device and the second terminal device, and the first multicast wireless bearer is used to carry the second service.

[0022] Through the at least one mapping relationship carried in the above configuration message, the first terminal device can forward the first data packet based on the at least one mapping relationship.

[0023] In a possible implementation manner, the first parameter is an identifier of a first logical channel, and the first logical channel is associated with the first channel.

[0024] In this way, the use of the sidelink relay adaptation protocol (SRAP) on the first interface can be avoided, and both the normal forwarding of the second service data and the correct reception of the second service data by the first terminal device can be ensured.

[0025] In a possible implementation manner, sending the second message to the second terminal device according to the first parameter includes: determining that the first data packet corresponds to the second terminal device according to the first mapping relationship and the first parameter.

[0026] In this way, the first terminal device can determine that the recipient of the first data packet is the second terminal device.

[0027] In a possible implementation, the sending of the second message to the second terminal device according to the first parameter includes: determining an identifier of the first multicast radio bearer according to an identifier of the first logical channel and a second mapping relationship.

[0028] In this way, the first terminal device can determine the identifier of the multicast radio bearer corresponding to the first data packet.

[0029] In a possible implementation manner, sending the second message to the second terminal device according to the first parameter includes: determining the second channel according to the identifier of the first multicast radio bearer and the third mapping relationship.

[0030] In this way, the first terminal device can determine the specific channel for sending the first data packet to the second terminal device.

[0031] In a possible implementation manner, sending the second message to the second terminal device according to the first parameter includes: sending the second message to the second terminal device through a second channel, wherein the second message also includes an identifier of the first multicast radio bearer.

[0032] By sending the identifier of the first multicast radio bearer to the second terminal device, the second terminal device can forward the first data packet to the corresponding protocol entity according to the identifier of the first multicast radio bearer.

[0033] In a possible implementation manner, the method further includes: sending an identifier of a second logical channel to the access network device, where the identifier of the second logical channel is used to identify the second logical channel, and the second logical channel belongs to the second interface.

[0034] In this way, the access network device can determine the association between the second logical channel and the second channel.

[0035] In a possible implementation manner, the method further includes: sending the third mapping relationship to the second terminal device.

[0036] In this way, the second terminal device can determine the identifier of the first multicast radio bearer corresponding to the first data packet according to the third mapping relationship and the identifier of the second channel, and then forward the first data packet to the corresponding protocol entity according to the identifier of the first multicast radio bearer.

[0037] In one possible implementation, the first message also includes an identifier of the second terminal device, the first parameter is an identifier of the first multicast wireless bearer, and the second message is sent to the second terminal device according to the first parameter, including: sending the second message to the second terminal device through a second channel, the second message also includes the identifier of the first multicast wireless bearer, and the second message does not include the identifier of the second terminal device.

[0038] By sending the identifier of the first multicast radio bearer to the second terminal device, the second terminal device can forward the first data packet to the corresponding protocol entity according to the identifier of the first multicast radio bearer.

[0039] In a possible implementation manner, the first message further includes a third indication message, where the third indication message is used to indicate that the radio bearer identifier corresponding to the first data packet is a multicast radio bearer identifier.

[0040] In this way, the first terminal device can determine, based on the third indication message, whether the type of the radio bearer identifier corresponding to the first data packet is a multicast radio bearer identifier or a data radio bearer identifier.

[0041] In a possible implementation, the configuration message also includes a fourth indication message, which is used to indicate the configuration of a first protocol entity and a second protocol entity, the first protocol entity is used for the first terminal device to transmit the first data packet in a point-to-point mode on the second interface, and the second protocol entity is used for the first terminal device to transmit the first data packet in a point-to-multipoint mode on the second interface.

[0042] In this way, the first terminal device can establish two protocol entities according to the fourth indication message, so as to support the transmission of the first data packet in point-to-point mode and point-to-multipoint mode.

[0043] According to a second aspect, a communication method is provided, comprising: receiving a first message from an access network device, the first message comprising a first data packet and a first parameter, the first parameter being used to indicate a first multicast wireless bearer or a first logical channel, the first logical channel belonging to a first interface, the first interface being a communication interface between a first terminal device and the access network device, the first data packet belonging to a second service; and sending a second message to a second terminal device according to the first parameter, the second message comprising the first data packet.

[0044] In a possible implementation, the method also includes: receiving a configuration message from an access network device, the configuration message including at least one of the following: a first mapping relationship, a second mapping relationship, and a third mapping relationship, the first mapping relationship is used to associate the second terminal device with the first channel, the second mapping relationship is used to associate the first channel with the first multicast wireless bearer, the third mapping relationship is used to associate the second channel with the first multicast wireless bearer, the first data packet is received by the first terminal device through the first channel at the first interface; the first data packet is sent by the first terminal device through the second channel at the second interface, the second interface is a communication interface between the first terminal device and the second terminal device, and the first multicast wireless bearer is used to carry the second service.

[0045] In a possible implementation manner, the first parameter is an identifier of a first logical channel, and the first logical channel is associated with the first channel.

[0046] In a possible implementation manner, sending the second message to the second terminal device according to the first parameter includes: determining that the first data packet corresponds to the second terminal device according to the first mapping relationship and the first parameter.

[0047] In a possible implementation, the sending of the second message to the second terminal device according to the first parameter includes: determining an identifier of the first multicast radio bearer according to an identifier of the first logical channel and a second mapping relationship.

[0048] In a possible implementation manner, sending a second message to a second terminal device according to the first parameter includes: determining a second channel according to an identifier of the first multicast radio bearer and a third mapping relationship.

[0049] In a possible implementation, sending the second message to the second terminal device according to the first parameter includes: sending the second message to the second terminal device through a second channel, the second message also including an identifier of the first multicast radio bearer.

[0050] In a possible implementation manner, the method further includes: sending an identifier of a second logical channel to the access network device, where the identifier of the second logical channel is used to identify the second logical channel, and the second logical channel belongs to the second interface.

[0051] In a possible implementation manner, the method further includes: sending the third mapping relationship to the second terminal device.

[0052] In one possible implementation, the first message also includes an identifier of the second terminal device, the first parameter is an identifier of the first multicast wireless bearer, and sending a fourth message to the second terminal device according to the first parameter includes: sending the second message to the second terminal device through the second channel, the second message also includes the identifier of the first multicast wireless bearer, and the second message does not include the identifier of the second terminal device.

[0053] In a possible implementation manner, the first message further includes a first indication message, where the first indication message is used to indicate that the radio bearer identifier corresponding to the first data packet is a multicast radio bearer identifier.

[0054] In one possible implementation, the configuration message also includes a second indication message, and the second indication message is used to indicate the configuration of a first protocol entity and a second protocol entity, the first protocol entity is used for the first terminal device to transmit the first data packet in a point-to-point mode on the second interface, and the second protocol entity is used for the first terminal device to transmit the first data packet in a point-to-multipoint mode on the second interface.

[0055] For the description of the beneficial effects of the second aspect and any one of the solutions described in the second aspect, reference can be made to the description of the beneficial effects of the first aspect and any one of the solutions described in the first aspect, and no further details will be given.

[0056] According to a third aspect, a communication method is provided, which is applied to a first terminal device, and the method includes: receiving a first indication message from a second terminal device, the first indication message being used to indicate a first service, the first service being a service between the second terminal device and an access network device, and the first service including a multicast service; receiving a paging message from the access network device, the paging message including a second indication message being used to indicate a second service, the second service being a service between the second terminal device and the access network device, and the second service including a multicast service; and sending the paging message to the second terminal device according to the first indication message and the second indication message.

[0057] Optionally, the first terminal device determines to send the paging message to the second terminal device based on the first indication message and the second indication message.

[0058] In a possible implementation manner, the method further includes: sending a first indication message to the access network device.

[0059] In a possible implementation, the method further includes: sending capability information of the first terminal device to the second terminal device, where the capability information of the first terminal device is used to indicate that the first terminal device supports multicast service transmission.

[0060] In a possible implementation manner, the method further includes: receiving a request message from the second terminal device, where the request message is used to request a capability message of the first terminal device.

[0061] In a possible implementation, the request information includes capability information of the second terminal device, where the capability information of the second terminal device is used to indicate that the second terminal device supports multicast service transmission.

[0062] For the description of the beneficial effects of the third aspect and any one of the solutions described in the third aspect, reference can be made to the description of the beneficial effects of the first aspect and any one of the solutions described in the first aspect, and no further details will be given.

[0063] In a fourth aspect, a communication method is provided, which is applied to a second terminal device, and the method includes: sending a first indication message to a first terminal device, the first indication message is used to indicate a first service, and the first service includes a multicast service; receiving a paging message from the first terminal device, the paging message includes a second indication message, and the second indication message is used to indicate a second service, and the second service includes a multicast service.

[0064] In the above scheme, the first indication message sent by the second terminal device to the first terminal device can be used by the first terminal device to determine whether it is necessary to forward the paging message from the access network device to the second terminal device. In this way, the first terminal device can accurately forward the paging message from the access network device to the corresponding second terminal device, and the access network device can also accurately page the corresponding second terminal device.

[0065] In a possible implementation, the method further includes: sending a request message to the first terminal device, the request message being used to request a capability message of the first terminal device, the capability message of the first terminal device being used to indicate that the first terminal device supports multicast service transmission; and receiving capability information of the first terminal device.

[0066] In this way, the second terminal device can obtain the capability information of the first terminal device, and then determine that the first terminal device supports multicast service transmission.

[0067] In a possible implementation, the request message includes a capability message of the second terminal device, and the capability message of the second terminal device is used to indicate that the first terminal device supports multicast service transmission.

[0068] In this way, this can enable the first terminal device to determine that the second terminal device supports multicast service transmission.

[0069] In one possible implementation, the method also includes: receiving a first mapping relationship from a first terminal device, or receiving a first mapping relationship from an access network device, the first mapping relationship being used to associate a first channel with a first multicast wireless bearer, a first data packet being sent by the first terminal device through a first channel at a first interface, the first interface being a communication interface between the first terminal device and the second terminal device, the first multicast wireless bearer being used to carry the second service, and the first data packet belonging to the second service.

[0070] In this way, the second terminal device can determine the identifier of the multicast radio bearer corresponding to the first data packet according to the above mapping relationship, and then forward the first data packet to a suitable protocol entity for processing according to the identifier of the multicast radio bearer corresponding to the first data packet.

[0071] In a possible implementation manner, the method further includes: receiving a first message from a first terminal device, where the first message includes a first data packet and does not include an identifier of the second terminal device.

[0072] In this way, the second terminal device can obtain the first data packet and realize multicast service transmission between the second terminal device and the access network device.

[0073] In a possible implementation, the method further includes: receiving a first message from a first terminal device, the first message including a first data packet and an identifier of a first multicast radio bearer, and the first message not including an identifier of a second terminal device.

[0074] In this way, the second terminal device can forward the first data packet to the corresponding protocol entity according to the identifier of the first multicast radio bearer.

[0075] In a possible implementation, the method also includes: receiving a third indication message from an access network device, the third indication message being used to indicate configuration of a first protocol entity and a second protocol entity, the first protocol entity being used for the second terminal device to transmit a first data packet in a point-to-point mode on a first interface, and the second protocol entity being used for the second terminal device to transmit a first data packet in a point-to-multipoint mode on the first interface.

[0076] In this way, the second terminal device can establish two protocol entities according to the third indication message, so as to support the transmission of the first data packet in the point-to-point mode and the point-to-multipoint mode.

[0077] In a fifth aspect, a communication method is provided, which is applied to a second terminal device, and the method includes: sending a first indication message to a first terminal device, the first indication message is used to indicate a first service, and the first service includes a multicast service; receiving a paging message from the first terminal device, the paging message includes a second indication message, and the second indication message is used to indicate a second service, and the second service includes a multicast service.

[0078] In a possible implementation, the method further includes: sending a request message to the first terminal device, the request message being used to request a capability message of the first terminal device, the capability message of the first terminal device being used to indicate that the first terminal device supports multicast service transmission; and receiving capability information of the first terminal device.

[0079] In a possible implementation, the request message includes a capability message of the second terminal device, and the capability message of the second terminal device is used to indicate that the first terminal device supports multicast service transmission.

[0080] For the description of the beneficial effects of the fifth aspect and any one of the schemes in the fifth aspect, reference can be made to the description of the beneficial effects of the fourth aspect and any one of the schemes in the fourth aspect, and no further details will be given.

[0081] In a sixth aspect, a communication method is provided, which is applied to a second terminal device, and the method includes: receiving a first mapping relationship from a first terminal device, or receiving a first mapping relationship from an access network device, the first mapping relationship being used to associate a first channel with a first multicast wireless bearer, a first data packet being received by the second terminal device through a first channel at a first interface, the first interface being a communication interface between the first terminal device and the second terminal device, the first multicast wireless bearer being used to carry the second service, and the first data packet belonging to the second service.

[0082] In a possible implementation manner, the method further includes: receiving a first message from a first terminal device, where the first message includes a first data packet and does not include an identifier of the second terminal device.

[0083] In a possible implementation, the method further includes: receiving a first message from a first terminal device, the first message including a first data packet and an identifier of a first multicast radio bearer, and the first message not including an identifier of a second terminal device.

[0084] In a possible implementation, the method also includes: receiving an indication message from an access network device, the indication message being used to indicate configuration of a first protocol entity and a second protocol entity, the first protocol entity being used for the second terminal device to transmit the first data packet in a point-to-point mode on the first interface, and the second protocol entity being used for the second terminal device to transmit the first data packet in a point-to-multipoint mode on the first interface.

[0085] For the description of the beneficial effects of the sixth aspect and any one of the schemes in the sixth aspect, reference can be made to the description of the beneficial effects of the fourth aspect and any one of the schemes in the fourth aspect, and no further details will be given.

[0086] In the seventh aspect, a communication method is provided, which is applied to an access network device, and the method includes: receiving a first indication message from a first terminal device, the first indication message is used to indicate a first service, and the first service includes a multicast service; sending a paging message to the first terminal device, the paging message includes a second identifier, and the second indication message is used to indicate a second service, and the second service includes a multicast service.

[0087] In one possible implementation, the method also includes: sending a first message to a first terminal device, the first message including a first data packet and a first parameter, the first parameter being used to identify a first multicast wireless bearer or a first logical channel, the first logical channel belonging to a first interface, the first interface being a communication interface between the first terminal device and an access network device, and the first data packet belonging to the second service.

[0088] In a possible implementation, the method also includes: sending a first configuration message to the first terminal device, the first configuration message including at least one of the following: a first mapping relationship, a second mapping relationship, and a third mapping relationship, the first mapping relationship is used to associate the second terminal device with the first channel, the second mapping relationship is used to associate the first channel with the first multicast wireless bearer, the third mapping relationship is used to associate the second channel with the first multicast wireless bearer, the first data packet is sent by the access network device through the first channel on the first interface; the first data packet is sent by the first terminal device through the second channel on the second interface, the second interface is a communication interface between the first terminal device and the second terminal device, and the first multicast wireless bearer is used to carry the second service.

[0089] In a possible implementation manner, the first parameter is an identifier of a first logical channel, and the first logical channel is associated with the first channel.

[0090] In a possible implementation, the method further includes: receiving an identifier of a second logical channel from the first terminal device, where the identifier of the second logical channel is used to identify a second logical channel, and the second logical channel belongs to the second interface.

[0091] In a possible implementation manner, the first parameter is an identifier of the first multicast radio bearer.

[0092] In a possible implementation manner, the first message further includes third indication information, where the third indication information is used to indicate that the radio bearer identifier corresponding to the first data packet is a multicast radio bearer identifier.

[0093] In a possible implementation, the first configuration message also includes a fourth indication message, and the fourth indication message is used to indicate the configuration of a first protocol entity and a second protocol entity, the first protocol entity is used for the first terminal device to transmit the first data packet in a point-to-point mode on the second interface, and the second protocol entity is used for the first terminal device to transmit the first data packet in a point-to-multipoint mode on the second interface.

[0094] In one possible implementation, the method also includes: sending a second configuration message to a second terminal device, the second configuration message including a third mapping relationship, the third mapping relationship being used to associate a second channel with a first multicast wireless bearer, a first data packet being sent by the first terminal device through a second channel at a second interface, the second interface being a communication interface between the first terminal device and the second terminal device, and the first data packet belonging to the second service.

[0095] In a possible implementation, the second configuration message also includes a fifth indication message, and the fifth indication message is used to indicate the configuration of a first protocol entity and a second protocol entity, the first protocol entity is used for the second terminal device to transmit the first data packet in point-to-point mode on the second interface, and the second protocol entity is used for the first terminal device to transmit the first data packet in point-to-multipoint mode on the second interface.

[0096] For the description of the beneficial effects of the seventh aspect and any one of the solutions described in the seventh aspect, reference can be made to the description of the beneficial effects of the first aspect and any one of the solutions described in the first aspect, and no further details will be given.

[0097] In an eighth aspect, a communication method is provided, which is applied to an access network device, and the method includes: sending a first message to a first terminal device, the first message including a first data packet and a first parameter, the first parameter being used to identify a first multicast wireless bearer or a first logical channel, the first logical channel belonging to a first interface, the first interface being a communication interface between the first terminal device and the access network device, and the first data packet belonging to the second service.

[0098] In a possible implementation, the method also includes: sending a first configuration message to the first terminal device, the first configuration message including at least one of the following: a first mapping relationship, a second mapping relationship, and a third mapping relationship, the first mapping relationship is used to associate the second terminal device with the first channel, the second mapping relationship is used to associate the first channel with the first multicast wireless bearer, the third mapping relationship is used to associate the second channel with the first multicast wireless bearer, the first data packet is sent by the access network device through the first channel on the first interface; the first data packet is sent by the first terminal device through the second channel on the second interface, the second interface is the communication interface between the first terminal device and the second terminal device, and the first multicast wireless bearer is used to carry the second service.

[0099] In a possible implementation manner, the first parameter is an identifier of a first logical channel, and the first logical channel is associated with the first channel.

[0100] In a possible implementation, the method further includes: receiving an identifier of a second logical channel from the first terminal device, where the identifier of the second logical channel is used to identify a second logical channel, and the second logical channel belongs to the second interface.

[0101] In a possible implementation manner, the first parameter is an identifier of the first multicast radio bearer.

[0102] In a possible implementation manner, the first message further includes first indication information, where the first indication information is used to indicate that the radio bearer identifier corresponding to the first data packet is a multicast radio bearer identifier.

[0103] In certain implementations of the eighth aspect, the first configuration message also includes a second indication message, where the second indication message is used to indicate the configuration of a first protocol entity and a second protocol entity, where the first protocol entity is used for the first terminal device to transmit the first data packet in point-to-point mode on the second interface, and the second protocol entity is used for the first terminal device to transmit the first data packet in point-to-multipoint mode on the second interface.

[0104] In one possible implementation, the method also includes: sending a second configuration message to a second terminal device, the second configuration message including a third mapping relationship, the third mapping relationship being used to associate a second channel with a first multicast wireless bearer, the first data packet being sent by the first terminal device through a second channel at a second interface, the second interface being a communication interface between the first terminal device and the second terminal device, and the first data packet belonging to the second service.

[0105] In a possible implementation, the second configuration message also includes a third indication message, and the third indication message is used to indicate the configuration of a third protocol entity and a fourth protocol entity. The third protocol entity is used for the second terminal device to transmit the first data packet in point-to-point mode on the second interface, and the fourth protocol entity is used for the second terminal device to transmit the first data packet in point-to-multipoint mode on the second interface.

[0106] For the description of the beneficial effects of the eighth aspect and any one of the solutions described in the eighth aspect, reference can be made to the description of the beneficial effects of the first aspect and any one of the solutions described in the first aspect, and no further details will be given.

[0107] In a ninth aspect, a communication device is provided, which is used to execute the method provided in any one of the first to eighth aspects. Specifically, the communication device may include a unit and / or module for executing the method provided in any one of the above implementations of the first to eighth aspects.

[0108] In one implementation, the communication device is a device (such as a first terminal device, or a second terminal device, or an access network device, etc.). When the communication device is a device, the transceiver unit may be a transceiver, or an input / output interface; the processing unit may be at least one processor. Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0109] In another implementation, the communication device is a chip, a chip system or a circuit used in a device (such as a first terminal device, or a second terminal device, or an access network device, etc.). When the communication device is a chip, a chip system or a circuit used in a device, the transceiver unit may be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit on the chip, the chip system or the circuit; the processing unit may be at least one processor, a processing circuit or a logic circuit, etc.

[0110] In a tenth aspect, a communication device is provided, comprising: a memory for storing programs; and at least one processor for executing computer programs or instructions stored in the memory to execute a method provided in any one of the above-mentioned implementations of the first to eighth aspects.

[0111] In one implementation, the communication apparatus is a device (a first terminal device, or a second terminal device, or an access network device, etc.).

[0112] In another implementation, the apparatus is a chip, a chip system or a circuit used in a device (a first terminal device, or a second terminal device, or an access network device, etc.).

[0113] In an eleventh aspect, the present application provides a processor for executing the methods provided in the above aspects.

[0114] For the operations such as sending and acquiring / receiving involved in the processor, unless otherwise specified, or unless they conflict with their actual function or internal logic in the relevant description, they can be understood as operations such as processor output, reception, input, etc., or as sending and receiving operations performed by the radio frequency circuit and antenna, and this application does not limit this.

[0115] In a twelfth aspect, a computer-readable storage medium is provided, which stores a program code for execution by a device, and the program code includes instructions for executing the method provided by any one of the above-mentioned implementations of the first to eighth aspects.

[0116] In a thirteenth aspect, a computer program product comprising instructions is provided. When the computer program product is run on a computer, the computer executes the method provided by any one of the above-mentioned implementations of the first to eighth aspects.

[0117] In a fourteenth aspect, a chip system is provided, which includes a processor for calling and executing computer instructions from a memory so that a device equipped with the chip system executes a method provided in any one of the above-mentioned implementations of the first to eighth aspects.

[0118] Optionally, the chip system may further include an input / output interface, and the processor may read instructions stored in the memory through the input / output interface.

[0119] Optionally, as an implementation method, the chip system also includes a memory, in which a computer program or instructions are stored, and the processor is used to execute the computer program or instructions stored in the memory. When the computer program or instructions are executed, the processor is used to execute the method provided in any one of the above-mentioned implementation methods of the first aspect to the eighth aspect.

[0120] In the fifteenth aspect, a communication system is provided, including a first terminal device and a second terminal device, the first terminal device is used to execute the method provided by any one of the above-mentioned implementation modes of the first to third aspects, and the second terminal device is used to execute the method provided by any one of the implementation modes of the fourth to sixth aspects.

[0121] Optionally, the communication system may further include an access network device, and the access network device is used to execute the method provided by any one of the implementation modes of the seventh and eighth aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0122] Figure 1 It is a schematic diagram of a communication system 100 to which an embodiment of the present application is applicable.

[0123] Figure 2 It is a schematic diagram of the interaction flow of the communication method 200 according to an embodiment of the present application.

[0124] Figure 3 It is a schematic diagram of the interaction flow of the communication method 300 according to an embodiment of the present application.

[0125] Figure 4 It is a schematic diagram of the protocol architecture 400 of an embodiment of the present application.

[0126] Figure 5 It is a schematic diagram of the interaction flow of the communication method 500 according to an embodiment of the present application.

[0127] Figure 6 It is a schematic diagram of the interaction flow of the communication method 600 according to an embodiment of the present application.

[0128] Figure 7 It is a schematic diagram of the protocol architecture 700 of an embodiment of the present application.

[0129] Figure 8 It is a schematic diagram of the interaction process of the communication method 800 according to an embodiment of the present application.

[0130] Fig. 9 It is a schematic diagram of the protocol architecture 900 of an embodiment of the present application.

[0131] Fig.10It is a schematic diagram of the interaction flow of the communication method 1000 according to an embodiment of the present application.

[0132] Fig.11 It is a schematic diagram of the configuration relationship 1100 of an embodiment of the present application.

[0133] Fig.12 It is a schematic diagram of the protocol architecture 1200 of an embodiment of the present application.

[0134] Fig.13 It is a schematic diagram of the interaction flow of the communication method 1300 according to an embodiment of the present application.

[0135] Fig.14 It is a schematic diagram of the configuration relationship 1400 of an embodiment of the present application.

[0136] Fig.15 It is a schematic block diagram of a communication device 1500 according to an embodiment of the present application.

[0137] Fig.16 It is a schematic block diagram of a communication device 1600 according to an embodiment of the present application.

[0138] Fig.17 It is a schematic block diagram of a communication device 1700 according to an embodiment of the present application.

[0139] Fig.18 It is a schematic block diagram of a communication device 1800 according to an embodiment of the present application.

[0140] Fig.19 It is a schematic block diagram of a communication device 1900 according to an embodiment of the present application. DETAILED DESCRIPTION

[0141] In order to facilitate understanding of the embodiments of the present application, the following points are first explained.

[0142] 1. Unless otherwise specified, “plurality” means two or more.

[0143] 2. Unless otherwise specified or there is no logical conflict, the terms and / or descriptions between different embodiments of the present application are consistent and can be referenced to each other. The technical features in different embodiments can be combined to form new embodiments based on their internal logical relationships.

[0144] 3. The various digital numbers involved in this application are only used for the convenience of description and are not used to limit the scope of protection of this application. The size of the serial numbers involved in this application does not mean the order of execution. The execution order of each process should be determined by its function and internal logic. For example, the terms "first", "second", "third", "fourth" and other various terminology labels (if any) in the specification and claims and drawings of this application are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. Among them, the data used in this way can be interchangeable where appropriate, so that the embodiments described here can be implemented in an order other than what is illustrated or described here.

[0145] At the same time, any embodiment or design described in the present application as "exemplary" or "for example" should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a concrete manner for ease of understanding.

[0146] 4. The terms "comprise", "include", "have" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or apparatus comprising a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such process, method, product or apparatus.

[0147] 5. In this application, "used to indicate" can be understood as "enable", and "enable" can include direct enablement and indirect enablement. When describing that a certain information is used to enable A, it can include that the information directly enables A or indirectly enables A, and it does not mean that the information must carry A.

[0148] The information enabled by the information is called information to be enabled. In the specific implementation process, there are many ways to enable the information to be enabled, such as but not limited to, the information to be enabled can be directly enabled, such as the information to be enabled itself or the index of the information to be enabled. The information to be enabled can also be indirectly enabled by enabling other information, wherein there is an association relationship between the other information and the information to be enabled. It is also possible to enable only a part of the information to be enabled, while the other parts of the information to be enabled are known or agreed in advance. For example, the enabling of specific information can also be achieved by means of the arrangement order of each piece of information agreed in advance (such as specified by the protocol), thereby reducing the enabling overhead to a certain extent. At the same time, the common parts of each piece of information can also be identified and enabled uniformly to reduce the enabling overhead caused by enabling the same information separately.

[0149] 6. In this application, "pre-configuration" may include pre-definition, such as protocol definition. Among them, "pre-definition" can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including each network element), and this application does not limit its specific implementation method.

[0150] 7. The term "storage" or "saving" as used in this application may refer to saving in one or more memories. The one or more memories may be provided separately or integrated in an encoder or decoder, a processor, or a communication device. The one or more memories may also be partially provided separately and partially integrated in a decoder, a processor, or a communication device. The type of memory may be any form of storage medium, without limitation.

[0151] 8. The “protocol” involved in this application may refer to a standard protocol in the field of communications, for example, it may include the fourth generation (4G) network, the fifth generation (5G) network protocol, the new radio (NR) protocol, the 5.5G network protocol, the sixth generation (6G) network protocol and related protocols used in future communication systems, and this application does not limit this.

[0152] 9. The dotted arrows or boxes in the schematic diagrams of the drawings in the specification of this application represent optional steps or optional modules.

[0153] 10. Unless otherwise specified, “ / ” indicates that the objects associated with each other are in an “or” relationship. For example, A / B can represent A or B. The “and / or” in this application is only a description of the association relationship between the associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural.

[0154] First, a communication system to which the embodiments of the present application are applicable is described.

[0155] Figure 1 1 is a schematic diagram of a communication system 100 applicable to an embodiment of the present application. Figure 1 As shown, the communication system 100 includes: an access network device, a first terminal device and a second terminal device. The first terminal device is used to assist the second terminal device to communicate with the access network device, for example, to assist the second terminal device to transmit services with the access network device, such as unicast services and multicast services. The first terminal device may also be a relay terminal device, and the second terminal device may also be a remote terminal device.

[0156] Optionally, the communication system 100 may further include a plurality of first terminal devices. In other words, the communication system 100 may support a plurality of relay terminal devices to assist the communication between the remote terminal device and the access network device.

[0157] In the communication system 100, the first terminal device communicates with the second terminal device via the SL (eg, via the PC5 interface), and the first terminal device communicates with the access network device via the air interface (eg, via the Uu interface).

[0158] The above-mentioned first terminal device and second terminal device (hereinafter collectively referred to as terminal devices) are a device with wireless transceiver functions, which may refer to user equipment (UE), access terminal, subscriber unit, user station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication equipment, user agent or user device. The terminal device 120 may also be a satellite phone, a cellular phone, a smart phone, a wireless data card, a wireless modem, a machine type communication device, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a customer-premises equipment (CPE), a smart point of sale (POS) machine, a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a communication device carried on a high-altitude aircraft, a wearable device, a drone, a robot, a terminal in device-to-device communication (D2D), a terminal in vehicle-to-everything (V2X), a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self-driving, a remote medical device, or a wireless terminal in medical equipment. This application does not limit the wireless terminals in medical, smart grid, transportation safety, smart city, smart home, or terminal devices in communication networks evolved after 5G.

[0159] The communication device for realizing the function of the terminal device can be a terminal device, or a device that can support the terminal device to realize the function, such as a chip system. The device can be installed in the terminal device or used in combination with the terminal device. In the present application, the chip system can be composed of a chip, or it can include a chip and other discrete devices.

[0160] Access network equipment is a device with wireless transceiver functions, which is used to communicate with terminal equipment. Access network equipment can be a node in the radio access network (RAN), which can be called a base station or a RAN node. It can be an evolved Node B (eNB or eNodeB) of long term evolution (LTE); or a base station of a 5G network such as gNodeB (gNB) or a base station in a public land mobile network (PLMN) evolved after 5G, a broadband network service gateway (BNG), an aggregation switch or the 3rd generation partnership project (3GPP) access equipment, etc.

[0161] The above-mentioned RAN can be configured as a RAN defined by the 3GPP protocol, an open radio access network (O-RAN) or a cloud radio access network (C-RAN), etc. The network device 110 can also include various forms of base stations, such as: macro base stations, micro base stations (also called small stations), relay stations, transmission points (transmitting and receiving points, TRP), transmission points (transmitting points, TP), mobile switching centers, and devices that assume the function of base stations in device-to-device (D2D), vehicle-to-everything (V2X), machine-to-machine (M2M) communications, network devices in non-terrestrial networks (NTN), etc., without specific limitation.

[0162] The access network equipment may also include network elements or modules that implement some functions of the base station, for example, one or more of the following: a centralized unit (CU), a distributed unit (DU), or a radio unit (RU). Optionally, the CU can be further separated into a CU-control plane (CP) and a CU-user plane (UP). The functions of the CU and DU can be implemented by different network elements, or simultaneously by the baseband unit (BBU) of the base station. The function of the RU can be implemented by the radio frequency equipment of the base station. For example, the radio frequency equipment of the base station may be a remote radio unit (RRU), a pico remote radio unit (pRRU), an active antenna unit (AAU), or other units, modules or devices with radio frequency processing functions. The communication interface protocol between the BBU and the radio frequency equipment can be a common public radio interface (CPRI) interface protocol, an enhanced common public radio interface (eCPRI) interface protocol, or a fronthaul interface protocol between the DU and the RU in the O-RAN system, etc., without limitation.

[0163] In different systems, CU (or CU-CP and CU-UP), DU or RU may have different names, and those skilled in the art may understand their meanings. For example, in the O-RAN system, CU may be called O-CU (open CU), DU may be called O-DU, CU-CP may be called O-CU-CP, CU-UP may be called O-CU-UP, and RU may be called O-RU. For the convenience of description, the embodiments of the present application are described using CU, CU-CP, CU-UP, DU and RU as examples. Any of the CU (or CU-CP, CU-UP), DU and RU in the embodiments of the present application may be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0164] The communication device for implementing the function of the access network device may be an access network device, or may be a device capable of supporting the access network device to implement the function, such as a chip system. The device may be installed in the access network device or used in conjunction with the access network device. The chip system in the embodiment of the present application may be composed of a chip, or may include a chip and other discrete devices.

[0165] The communication system 100 can also be the following systems: long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, universal mobile telecommunication system (UMTS), 5G system, 6G system, intersatellite communication and satellite communication and other NTN systems. Among them, the satellite communication system includes a satellite base station and a terminal device. The satellite base station provides communication services for the terminal device. The satellite base station can also communicate with the ground base station. The satellite can be used as a base station or as a terminal device. Among them, the satellite can refer to non-ground base stations or non-ground equipment such as drones, hot air balloons, low-orbit satellites, medium-orbit satellites, and high-orbit satellites.

[0166] The communication system 100 may also be a ground cellular communication system, a high altitude platform station (HAPS) communication system, a V2X system, an integrated access and backhaul (IAB) system, and a reconfigurable intelligent surface (RIS) communication system, etc., without limitation.

[0167] As described in the background technology, for unicast services, the relay terminal device can forward the paging information of the access network device to the appropriate remote terminal device. For example, the relay terminal device compares the UE ID carried in the paging information sent by the access network device with the paging ID sent by the remote terminal device to the relay terminal device to see if they match. If they match, the relay terminal device forwards the paging information to the remote terminal device. For multicast services, since the paging message sent by the access network device does not carry the UE ID, the relay terminal device cannot forward the paging information of the access network device to the appropriate remote terminal device, thereby affecting the multicast service transmission between the remote terminal device and the network device.

[0168] In view of this, the present application provides a communication method and a communication device, which can support an access network device to accurately page a remote terminal device.

[0169] For ease of understanding and explanation, the following describes the communication method of the embodiment of the present application by taking the interaction between the first terminal device, the second terminal device and the access network device as an example, but this should not constitute any limitation on the execution subject of the communication method of the embodiment of the present application. For example, the first terminal device can be replaced by a component configured in the first terminal device (such as a circuit, a chip or a chip system, etc.), the second terminal device can be replaced by a component configured in the second terminal device (such as a circuit, a chip or a chip system, etc.), and the access network device can be replaced by a component configured in the access network device (such as a circuit, a chip or a chip system, etc.).

[0170] Figure 2 2 is a schematic diagram of the interaction flow of the communication method 200 of the embodiment of the present application. Figure 2 As shown, the method 200 includes:

[0171] S210. The second terminal device sends an indication message 1 to the first terminal device. The indication message 1 is used to indicate service 1, and service 1 includes a multicast service.

[0172] Correspondingly, the first terminal device receives indication message 1.

[0173] Optionally, in a possible example, the second terminal device may send an indication message 1 to the first terminal device via a RemoteUEInformationSidelink message. In this way, it may be compatible with existing standards.

[0174] Optionally, a possible example is that service 1 includes a multicast service, which may include: service 1 is a multicast service, or service 1 includes services including multicast services. An example of a multicast service is a multicast / broadcast services (MBS) session, or a service similar to an MBS session, which is not a unicast service, and is not limited. Service 1 is a service between the second terminal device and the access network device, for example, the access network device needs to send data of service 1 to the second terminal device.

[0175] Optionally, a possible example is that indication message 1 is used to indicate service 1, and may also include: indication message 1 is used to indicate the type of service 1, or indication message 1 is used to indicate the service or service type that the second terminal device is interested in, or identification 1 is used to indicate the service or service type that the second terminal device is interested in, and the above-mentioned service or service type is related to the multicast service.

[0176] Optionally, in a possible example, service 1 may also be a multicast session that the second terminal device needs to join, is interested in joining, or expects to join. Therefore, indication message 1 may be used to indicate that the second terminal device needs to join, is interested in joining, or expects to join a multicast session.

[0177] Optionally, a possible implementation method indicates that message 1 is a temporary mobile group identity (TMGI) or an identifier similar to TMGI. The first terminal device can determine service 1 based on TMGI or an identifier similar to TMGI. Among them, TMGI can be used to identify a multicast session, which consists of a PLMN identifier and a service identifier (service ID). For further description of TMGI, please refer to the description of the existing standard, which will not be repeated here.

[0178] Optionally, the first terminal device may also send an indication message 1 to the access network device. For example, the first terminal device sends a SidelinkUEInformationNR message to the access network device, and the SidelinkUEInformationNR message includes the indication message 1. In this way, when the access network device wants to page the second terminal device, the access network device may carry the indication message 1 in the paging message 1, and the first terminal device may accurately forward the paging message 1 from the access network device to the corresponding second terminal device.

[0179] Optionally, the above-mentioned indication message 1 can be understood as identification 1, and identification 1 is used to indicate service 1.

[0180] S220. The access network device sends a paging message 1 to the first terminal device. The paging message 1 includes an indication message 2. The indication message 2 is used to indicate a service 2. The service 2 includes a multicast service.

[0181] Correspondingly, the first terminal device receives the paging message 1. For the description of the indication message 2, reference can be made to the description of the indication message 1, which will not be repeated here.

[0182] Optionally, the above-mentioned indication message 2 can be understood as identification 2, and identification 2 is used to indicate service 2.

[0183] Optionally, a possible implementation method, in which the access network device sends a paging message 1 to the first terminal device, may include: the access network device sends the paging message 1 to the first terminal device by broadcasting, or, when the first terminal device is in a connected state, the access network device sends the paging message 1 to the first terminal device by dedicated signaling, which is not limited to this.

[0184] S230. The first terminal device sends a paging message 1 to the second terminal device according to the indication message 1 and the indication message 2.

[0185] Correspondingly, the second terminal device receives paging message 1.

[0186] Optionally, the first terminal device may determine, based on indication message 1 and indication message 2, that paging message 1 needs to be sent to the second terminal device.

[0187] The first terminal device can determine whether to forward paging message 1 to the second terminal device by comparing whether indication message 1 is the same as indication message 2. In one example, if indication message 1 is the same as indication message 2, it is determined to forward paging message 1 to the second terminal device; in another example, if indication message 1 is different from indication message 2, it is determined not to forward paging message 1 to the second terminal device.

[0188] Optionally, in a possible implementation, the first terminal device may forward the paging message 1 to the second terminal device via the UuMessageTransferSidelink message. Accordingly, the second terminal device receives and parses the UuMessageTransferSidelink message to obtain the paging message 1, and switches from the idle state or the inactive state to the connected state based on the paging message 1, and starts the multicast service transmission between the access network device and the access network device.

[0189] Optionally, in a possible implementation, the first terminal device may send a paging message 1 to multiple second terminal devices in a multicast manner, and the multiple second terminal devices may be devices that have joined the same multicast session.

[0190] In the above scheme, the first terminal device can determine whether to forward the paging message 1 to the second terminal device according to the indication message 1 sent by the second terminal device and the indication message 2 carried in the paging message 1 sent by the access network device. If they are the same, it is determined to be forwarded; if they are not the same, it is determined not to be forwarded. In this way, the first terminal device can accurately forward the paging message from the access network device to the corresponding second terminal device, and the access network device can also accurately page the corresponding second terminal device.

[0191] Optionally, in a possible implementation, method 200 may further include:

[0192] S203. The second terminal device sends a request message 1 to the first terminal device, where the request message 1 is used to request capability information of the first terminal device.

[0193] Correspondingly, the first terminal device receives the request message 1. The capability information of the first terminal device can be used to indicate whether the first terminal device supports multicast service transmission. In this way, the second terminal device can determine that the first terminal device supports multicast service transmission.

[0194] Optionally, the request message 1 may also include capability information of the second terminal device, and the capability information of the second terminal device may be used to indicate that the second terminal device supports multicast service transmission. In this way, the first terminal device may determine that the second terminal device supports multicast service transmission.

[0195] Optionally, the capability information of the first terminal device may also be used to indicate that the first terminal device does not support multicast service transmission.

[0196] Optionally, the capability information of the second terminal device may also be used to indicate that the second terminal device does not support multicast service transmission.

[0197] When the second terminal device can send the request message 1 to the first terminal device, it can indicate that the second terminal device supports the multicast service. Therefore, the request message 1 may not include the capability information of the second terminal device.

[0198] In one example, the request message 1 may be a UECapabilityEnquirySidelink message, or the request message 1 may be in a UECapabilityEnquirySidelink message, and the UECapabilityEnquirySidelink message may also include capability information of the second terminal device, so as to be compatible with existing standards.

[0199] Optionally, in a possible implementation, method 200 may further include:

[0200] S206. The first terminal device sends capability information of the first terminal device to the second terminal device.

[0201] Correspondingly, the second terminal device receives the capability information of the first terminal device. In this way, the first terminal device can send the capability message of the first terminal device to the second terminal device according to the request of the second terminal device.

[0202] For ease of description, the following description uses the example of the capability information of the first terminal device being used to indicate that the first terminal device supports multicast service transmission. However, the capability information of the first terminal device can also be used to indicate that the first terminal device does not support multicast service transmission.

[0203] Optionally, the first terminal device may indicate whether the first terminal device supports multicast services by whether the information sent to the second terminal device includes the capability information of the first terminal device. For example, if the information sent by the first terminal device to the second terminal device (the specific type of information is not limited, and it can be any information) does not include the capability information of the first terminal device, it indicates that the first terminal device does not support multicast services; for example, if the information sent by the first terminal device to the second terminal device includes the capability information of the first terminal device, it indicates that the first terminal device supports multicast services.

[0204] Optionally, the first terminal device may send an indication message to the second terminal device, and the indication message is used to indicate whether the first terminal device supports the multicast service. For example, the indication message uses one or more bits, and the bit value is 1, which indicates that the first terminal device supports the multicast service, and the bit value is 0, which indicates that the first terminal device does not support the multicast service, and vice versa, which is not limited.

[0205] In summary, the present application does not limit the specific manner in which the first terminal device sends the capability information of the first terminal device to the second terminal device.

[0206] In a possible example, the capability information of the first terminal device is located in the UECapabilityInformationSidelink message, so as to be compatible with the existing standards.

[0207] When the first terminal device and the second terminal device do not exchange their respective capability information, the first terminal device may not support multicast service transmission, and the second terminal device cannot determine whether the first terminal device supports multicast service transmission. If the first terminal device does not support multicast service transmission, it cannot identify identification 1, the first terminal device can ignore identification 1, and the second terminal device cannot receive paging messages. Accordingly, the second terminal device can perform subsequent actions, including: switching to a new cell, discovering and selecting other first terminal devices, etc.

[0208] Optionally, in a possible implementation, method 200 may further include:

[0209] S209. The access network device sends capability information of the access network device to the first terminal device.

[0210] Correspondingly, the first terminal device receives capability information of the access network device, where the capability information of the access network device is used to indicate whether the access network device supports multicast service transmission.

[0211] In one example, the access network device carries the capability information of the access network device in a broadcast system message.

[0212] In one example, the access network device carries the capability information of the access network device in dedicated signaling, and the dedicated signaling may be a radio resource control (RRC) reconfiguration message, which is not limited.

[0213] When the access network device does not support multicast service transmission, this application supports the following processing:

[0214] For the second terminal device in the idle state, the core network (CN) initiates a separate paging to the second terminal device. For example, the CN sends a paging message (the paging message is a message of the NG interface) to the access network device, the access network device broadcasts the paging message (the paging message is a message of the Uu interface) through the air interface, and the first terminal device forwards the paging message according to the UE ID carried in the paging message. If the UE ID matches the paging ID indicated by the second terminal device, the paging message is forwarded to the second terminal device.

[0215] For the second terminal device in an inactive state, the access network device initiates a separate paging for the second terminal device. For example, the access network device broadcasts a paging message through an air interface, and the first terminal device forwards the paging message according to the UEID carried in the paging message.

[0216] If the UE ID matches the paging ID indicated by the second terminal device, the paging message is forwarded to the second terminal device.

[0217] Through the above technical solution, the second terminal device in an idle state or an inactive state can obtain the service information multicast by the access network device, thereby entering a connected state to receive the multicast service data from the access network device.

[0218] Combined with the following Figure 3 Describes that the second terminal device obtains data of the multicast service sent by the access network device. Figure 3 The scheme may be independent of Figure 2 The scheme described, Figure 3 The scheme described can also be used with Figure 2 The above schemes are combined and combined into a new scheme, which is uniformly described here and will not be described again below.

[0219] Figure 3 3 is a schematic diagram of the interaction flow of the communication method 300 of the embodiment of the present application. Figure 3 As shown, the method 300 includes:

[0220] S310. The access network device sends message 1 to the first terminal device. Message 1 includes data packet 1 and parameter 1. Parameter 1 is used to indicate multicast radio bearer 1 or logical channel 1.

[0221] Correspondingly, the first terminal device receives message 1 and is able to obtain data packet 1 and parameter 1 according to message 1.

[0222] In one example, logical channel 1 belongs to interface 1, which is a communication interface between the first terminal device and the access network device. In other words, interface 1 is a Uu interface. Multicast radio bearer 1 is used to carry service 2, and data packet 1 belongs to service 2. Therefore, multicast radio bearer 1 can be used to carry the transmission of data packet 1.

[0223] Optionally, in a possible implementation, parameter 1 can be used by the first terminal device to determine that data packet 1 corresponds to the second terminal device. In other words, parameter 1 can be used by the first terminal device to determine that the recipient of data packet 1 is the second terminal device, and the first terminal device determines to send data packet 1 to the second terminal device based on parameter 1.

[0224] Optionally, in a possible implementation, the first terminal device may also determine the PC5 (radiolink control, RLC) channel according to parameter 1, and may determine that the data packet 1 corresponds to the second terminal device according to the identifier of the second terminal device, as can be seen in Figure 8 Description.

[0225] Optionally, in a possible implementation, when parameter 1 is used to indicate multicast radio bearer 1, parameter 1 may be an identifier of multicast radio bearer 1, which is used to identify multicast radio bearer 1. When parameter 1 is used to indicate logical channel 1, parameter 1 may be an identifier of logical channel 1, which is used to identify logical channel 1. In this way, it is possible to avoid using SRAP on interface 1, and both ensure that service 2 data is forwarded normally and that the first terminal device can correctly receive service 2 data.

[0226] S320. The first terminal device determines to send message 2 to the second terminal device according to parameter 1, where message 2 includes data packet 1.

[0227] For a description of S320, see Figures 4 to 9 , I won’t say much here.

[0228] By carrying parameter 1 in message 1, the first terminal device can send data packet 1 to the second terminal device according to parameter 1, thereby ensuring the correct transmission of service 2 data.

[0229] The following will combine Figures 4 to 14 right Figure 3 The scheme shown is further described.

[0230] For ease of description, the following describes three scenarios respectively from the perspectives of using a point to point (PTP) mode, a point to multipoint (PTM) mode, and a PTP mode and a PTM mode.

[0231] 1. PTM Model

[0232] Figure 4 4 is a schematic diagram of a protocol architecture 400 of an embodiment of the present application. The protocol architecture 400 is applicable to the PTM mode. Figure 4 As shown, the protocol architecture 400 includes:

[0233] Access network equipment: packet data convergence protocol (PDCP) layer, RLC layer, media access control (MAC) layer and physical (PHY) layer. The PTM mode is used between the PDCP layer and the RLC layer for multicast service transmission.

[0234] First terminal device: RLC layer, MAC layer, and PHY layer on the Uu interface, RLC layer, MAC layer, and PHY layer on the PC5 interface, the RLC layer, MAC layer, and PHY layer on the Uu interface are respectively connected to the RLC layer, MAC layer, and PHY layer of the access network device, and the RLC layer, MAC layer, and PHY layer on the PC5 interface are respectively connected to the RLC layer, MAC layer, and PHY layer of the second terminal device.

[0235] Second terminal device: RLC layer, MAC layer and PHY layer on PC5 interface, the RLC layer, MAC layer and PHY layer on PC5 interface are respectively connected to the RLC layer, MAC layer and PHY layer of the second terminal device.

[0236] Optionally, the first terminal device and the second terminal device may also both include an SRAP layer, the main function of the SRAP layer is to multiplex and demultiplex bearers, that is, to support different bearers to be multiplexed into one bearer or to split one bearer into different bearers, and to distinguish data of different remote terminal devices. The SRAP layer in the protocol stack at both ends of the PC5 interface is called PC5-SRAP, and the SRAP layer in the protocol stack at both ends of the Uu interface is called Uu-SRAP.

[0237] It should be noted that the functions of the various layers described in the protocol architecture 400 can be found in the definitions of existing standards and will not be repeated here.

[0238] When the access network device adopts the CU-DU separation architecture, the above-listed layers can be divided in a variety of ways, for example, the PDCP layer is located in the CU, the RLC layer, the MAC layer and the PHY layer are located in the DU, etc., but other division methods are not limited.

[0239] It should be noted that Figure 4 The content shown is understood as an example only, and other layers may also be included. When other layers are included, the division method of other layers is not limited, and they may be divided into CU or DU, which is not limited.

[0240] When the access network device is a device in the O-RAN system, the access network device in the O-RAN system adopts a CU-DU separation architecture. This application does not limit the division method of the above layers. Some layers may be in the DU and other layers may be in the CU. The specific division method is not limited, and it can be adapted according to future evolution standards. A unified explanation is given here and no further details will be given later.

[0241] The following will describe the communication method 500 and the communication method 600 of the embodiments of the present application based on the protocol architecture 400.

[0242] Figure 5 FIG. 5 is a schematic diagram of the interaction flow of the communication method 500 according to an embodiment of the present application. Figure 5 As shown, the method 500 includes:

[0243] S501. The access network device sends a configuration message 1 to the first terminal device.

[0244] Accordingly, the first terminal device receives the configuration message 1. The configuration message 1 can be used to configure the first terminal device to forward the service 2. In other words, the configuration message 1 can be used to configure the first terminal device to forward the data packet 1 to the second terminal device.

[0245] It should be uniformly explained that when the access network device adopts the CU-DU separation architecture, the CU and DU can be responsible for different functions respectively. For example, in one possible implementation, the CU is used for information processing and generation, and the DU is responsible for sending and receiving information, but it is not strictly limited and is only described as an example. For example, the CU generates a configuration message 1, and the DU sends a configuration message 1 to the first terminal device, etc., which are uniformly explained here and will not be repeated below.

[0246] Optionally, in a possible implementation manner, the configuration message 1 may include at least one of the following:

[0247] Mapping relationship 1, mapping relationship 2, and mapping relationship 3.

[0248] Mapping relationship 1 can be used to associate the second terminal device with channel 1, mapping relationship 2 can be used to associate channel 1 with multicast radio bearer 1, and mapping relationship 3 can be used to associate multicast radio bearer 1 with channel 2. By configuring at least one mapping relationship carried in message 1, the first terminal device can forward data packet 1 based on at least one of the above mapping relationships.

[0249] As an example, data packet 1 may be sent by the access network device through channel 1 at interface 1.

[0250] In one example, data packet 1 may be sent by the first terminal device through channel 2 at the second interface 2, where interface 2 is a communication interface between the first terminal device and the second terminal device, in other words, interface 2 is a PC5 interface.

[0251] Optionally, in a possible implementation, mapping relationship 1 includes the identifier of the second terminal device and the identifier of channel 1; mapping relationship 2 includes the identifier of channel 1 and the identifier of multicast wireless bearer 1; and mapping relationship 3 includes the identifier of multicast wireless bearer 1 and the identifier of channel 2.

[0252] Optionally, in a possible implementation, mapping relationship 1 may also include: the identifier of the second terminal device, the identifier of channel 1, and the identifier of logical channel 1; or, mapping relationship 1 may also include: the identifier of the second terminal device and the identifier of logical channel 1; or, mapping relationship 1 may also include: the identifier of the second terminal device and the identifier of channel 1.

[0253] Optionally, when mapping relationship 1 includes the identifier of the second terminal device and the identifier of channel 1, configuration message 1 may also include the correspondence between the identifier of logical channel 1 and the identifier of channel 1. Optionally, the correspondence between the identifier of logical channel 1 and the identifier of channel 1 may not be carried in configuration message 1, and may be determined by the first terminal device itself. In other words, the access network device may indicate the identifier of the second terminal device and the identifier of channel 1 to the first terminal device, and the first terminal device may determine the correspondence between the identifier of the second terminal device and the identifier of logical channel 1 based on the correspondence between logical channel 1 and channel 1.

[0254] Optionally, the first terminal device may send the corresponding relationship between the identifier of logical channel 1 and the identifier of channel 1 to the access network device. After acquiring the corresponding relationship between logical channel 1 and channel 1, the access network device sends the identifier of the second terminal device, the identifier of channel 1, and the identifier of logical channel 1 to the first terminal device, or may only send the identifier of the second terminal device and the identifier of logical channel 1 to the first terminal device, which is not limited.

[0255] Optionally, mapping relationship 1 can also be that channel 1 corresponds to multiple second terminal devices, that is, the multicast service data transmitted on channel 1 is sent to multiple second terminal devices connected to the first terminal device, or the multicast service data transmitted on channel 1 is sent to a second terminal device connected to the first terminal device, which is not limited to this.

[0256] Optionally, in a possible implementation, channel 1 is a Uu RLC channel and channel 2 is a PC5 RLC channel, so as to be compatible with the current standard.

[0257] Optionally, the configuration message 1 may further include an identifier of the second terminal device, which is used to identify the second terminal device.

[0258] Optionally, the configuration message 1 may also include a group radio network temporary identifier (G-RNTI), which can be used for transmission scheduling in the PTM mode. For further description of the G-RNTI, please refer to the existing standards and will not be repeated here.

[0259] Optionally, the access network device can send a configuration message 2 to the second terminal device through the first terminal device, and the configuration message 2 includes multicast configuration information. The second terminal device can establish or reconfigure a corresponding PDCP entity according to the multicast configuration information in the configuration message 2, and the PDCP entity can be used by the second terminal device to perform corresponding processing on the received data packets.

[0260] S502. The access network device sends message 1 to the first terminal device.

[0261] Accordingly, the first terminal device receives message 1.

[0262] For the description of message 1, please refer to the description of S310 and will not be repeated here.

[0263] Parameter 1 included in message 1 is the identifier of logical channel 1, and logical channel 1 is associated with channel 1. In this way, it is possible to avoid using SRAP on interface 1, which can ensure that service 2 data is forwarded normally and that the first terminal device can correctly receive service 2 data.

[0264] S503. The first terminal device determines, based on the identifier of the logical channel 1 and the mapping relationship 1, that the data packet 1 corresponds to the second terminal device.

[0265] For example, the identifier of logical channel 1 is used to identify logical channel 1, and logical channel 1 is associated with channel 1. The first terminal device can determine that data packet 1 transmitted on channel 1 corresponds to the second terminal device according to mapping relationship 1 and the identifier of logical channel 1. In this way, the first terminal device can determine that the recipient of data packet 1 is the second terminal device.

[0266] When mapping relationship 1 includes the identifier of the second terminal device and the identifier of channel 1, the first terminal device can determine the identifier of channel 1 based on the correspondence between logical channel 1 and channel 1 and the identifier of logical channel 1, and determine the identifier of the second terminal device based on mapping relationship 1.

[0267] S504. The first terminal device determines the identifier of multicast radio bearer 1 according to the identifier of logical channel 1 and mapping relationship 2.

[0268] For example, the first terminal device can determine the identifier of logical channel 1 through parameter 1, and obtain the identifier of multicast radio bearer 1 in combination with mapping relationship 2, and the identifier of multicast radio bearer 1 is used to identify multicast radio bearer 1. In this way, the first terminal device can determine the identifier of the multicast radio bearer corresponding to data packet 1.

[0269] S505. The first terminal device determines channel 2 according to the identifier of multicast radio bearer 1 and mapping relationship 3.

[0270] For example, the first terminal device can determine channel 2 through the identifier of multicast radio bearer 1 and mapping relationship 2. In other words, the first terminal device can determine the identifier of channel 2 through mapping relationship 2 and the identifier of multicast radio bearer 1, and can determine channel 2 through the identifier of channel 2. In this way, the first terminal device can determine the specific channel for sending data packet 1 to the second terminal device.

[0271] S506. The first terminal device sends message 2 to the second terminal device through channel 2. Message 2 also includes the identifier of multicast radio bearer 1.

[0272] Accordingly, the second terminal device receives message 2 through channel 2, and obtains the identifier of multicast radio bearer 1 through message 2. By sending the identifier of multicast radio bearer 1 to the second terminal device, the second terminal device can forward data packet 1 to the corresponding protocol entity according to the identifier of multicast radio bearer 1.

[0273] Optionally, the message 2 may further include an identifier of the second terminal device.

[0274] It should be noted that message 1 does not include a SRAP header, and message 2 includes a SRAP header, which includes an identifier of multicast radio bearer 1.

[0275] Through the above technical solution, the present application supports the first terminal device to forward the data packet to a suitable second terminal device.

[0276] Figure 6 600 is a schematic diagram of the interaction process of the communication method 600 of the embodiment of the present application. Figure 6 As shown, the method 600 includes:

[0277] S601. The access network device sends a configuration message 1 to the first terminal device.

[0278] Correspondingly, the first terminal device receives the configuration message 1.

[0279] For the description of S601, please refer to the description of S501, which will not be repeated here.

[0280] S602. The first terminal device sends mapping relationship 3 to the second terminal device.

[0281] Accordingly, the second terminal device receives mapping relationship 3. Thus, the second terminal device can determine the identifier of multicast radio bearer 1 corresponding to data packet 1 according to mapping relationship 3 and the identifier of channel 2, and then forward data packet 1 to the corresponding protocol entity according to the identifier of multicast radio bearer 1.

[0282] Optionally, in a possible implementation, mapping relationship 3 is configured by an access network device. In other words, the access network device may send mapping relationship 3 to the second terminal device through the first terminal device.

[0283] For example, the first terminal device sends an identifier of logical channel 2 corresponding to channel 2 to the access network device, and logical channel 2 belongs to interface 2. Exemplarily, the first terminal device sends sidelink UE information (SidelinkUEInformation, SUI) to the access network device, and the SUI includes the correspondence between channel 2 and logical channel 2.

[0284] Optionally, in a possible implementation, the SUI includes an identifier of channel 2 and an identifier of logical channel 2. In this way, the access network device can determine the association between logical channel 2 and channel 2.

[0285] Optionally, in a possible implementation, the SUI includes an identifier of multicast radio bearer 1 and an identifier of logical channel 2. In this way, the access network device can determine that channel 2 is associated with or corresponds to logical channel 2.

[0286] Further, after the access network device obtains the identifier of the logical channel 2, the access network device configures the mapping relationship 3, and sends the mapping relationship 3 to the second terminal device through the first terminal device. The mapping relationship 3 sent by the access network device to the second terminal device through the first terminal device can be carried on Figure 5In the configuration message 2 shown.

[0287] In a possible implementation, mapping relationship 3 is configured by the first terminal device. For example, after the first terminal device determines the identifier of logical channel 2 corresponding to channel 2, it can send the corresponding relationship between logical channel 2 and channel 2 to the second terminal device, there is a corresponding relationship between channel 2 and multicast wireless bearer 1, logical channel 2 is associated with channel 2, and the second terminal device can obtain mapping relationship 3.

[0288] S603. The access network device sends message 1 to the first terminal device.

[0289] Accordingly, the first terminal device receives message 1.

[0290] The description of S603 can refer to the description of S502, which will not be repeated here. Parameter 1 is the identifier of logical channel 1.

[0291] S604. The first terminal device determines, based on the identifier of the logical channel 1 and the mapping relationship 1, that the data packet 1 corresponds to the second terminal device.

[0292] For the description of S604, please refer to the description of S503, which will not be repeated here.

[0293] S605. The first terminal device determines the identifier of multicast radio bearer 1 according to the identifier of logical channel 1 and mapping relationship 2.

[0294] For the description of S605, please refer to the description of S504, which will not be repeated here.

[0295] S606. The first terminal device determines channel 2 according to the identifier of multicast radio bearer 1 and mapping relationship 3.

[0296] For the description of S606, please refer to the description of S505, which will not be repeated here.

[0297] S607. The first terminal device sends message 2 to the second terminal device through channel 2.

[0298] Correspondingly, the second terminal device receives message 2 via channel 2.

[0299] Specifically, the second terminal device can determine the identifier of the multicast radio bearer 1 according to the mapping relationship 3 and the channel 2, and submit the data packet 1 to the corresponding PDCP entity for processing according to the identifier of the multicast radio bearer 1.

[0300] Optionally, after receiving message 1, the first terminal device may send message 2 to the second terminal device via multicast.

[0301] For example, the multicast process is:

[0302] The upper layer (e.g., V2X layer, application layer) determines a group and indicates a same group L2 ID to the access stratum (AS) of each second terminal device in the group. After the first terminal device receives the configuration message 1, the upper layer of the first terminal device determines a group L2 ID and indicates it to the AS layer of the first terminal device. The first terminal device uses the group L2 ID as the destination L2 ID for multicast.

[0303] It should be noted that the message 1 does not include the SRAP header, and the second message 2 may not include the SRAP header.

[0304] Through the above technical solution, the present application supports the first terminal device to forward the data packet to a suitable second terminal device.

[0305] 2. PTP Mode

[0306] Figure 7 Schematic diagram of the protocol architecture 700 of the embodiment of the present application. The protocol architecture 700 is applicable to the PTP mode. Figure 7 As shown, the protocol architecture 700 includes:

[0307] Access network equipment: PDCP layer, SRAP layer, RLC layer, MAC layer and PHY layer. The PTP mode is used between the PDCP layer and the RLC layer for multicast service data transmission.

[0308] First terminal device: SRAP layer, RLC layer, MAC layer and PHY layer on Uu interface, SRAP layer, RLC layer, MAC layer and PHY layer on PC5 interface, the SRAP layer, RLC layer, MAC layer and PHY layer on Uu interface are respectively connected to the SRAP layer, RLC layer, MAC layer and PHY layer of the access network device, and the SRAP layer, RLC layer, MAC layer and PHY layer on PC5 interface are respectively connected to the SRAP layer, RLC layer, MAC layer and PHY layer of the second terminal device.

[0309] Second terminal device: PDCP layer, SRAP layer, RLC layer, MAC layer and PHY layer on PC5 interface, the SRAP layer, RLC layer, MAC layer and PHY layer on PC5 interface are respectively connected to the SRAP layer, RLC layer, MAC layer and PHY layer of the second terminal device.

[0310] It should be noted that the functions of the various layers described in the protocol architecture 700 can be found in the definitions of existing standards and will not be repeated here.

[0311] It should be noted that when the access network device adopts the CU-DU separation architecture, the PDCP layer is located in the CU, and the SRAP layer, RLC layer, MAC layer and PHY layer are located in the DU.

[0312] The following will describe the communication method 800 of an embodiment of the present application based on the protocol architecture 700.

[0313] Figure 8 800 is a schematic diagram of the interaction process of the communication method 800 of the embodiment of the present application. Figure 8 As shown, method 800 includes:

[0314] S801. The access network device sends a configuration message 1 to the first terminal device.

[0315] Correspondingly, the first terminal device receives the configuration message 1.

[0316] In a possible implementation, the configuration message 1 includes the mapping relationship 3 and the identifier of the second terminal device, and the identifier of the second terminal device is used to indicate that the recipient of the data packet 1 is the second terminal device.

[0317] Since the identifier of the multicast radio bearer (MBS radio bearer, MRB) and the identifier of the data radio bearer (date radiobearer, DRB) may be the same, forwarding errors may occur in the first terminal device. For example, MRB1 corresponds to PC5 RLC channel 1, and DRB1 corresponds to PC5 RLC channel 2. After the first terminal device receives the data packet carrying RB ID1, it cannot determine whether to use PC5RLC channel 1 or PC5RLC channel 2 to forward it.

[0318] For this problem, this application supports the following methods:

[0319] 1) DRB and MRB cannot be mapped to the same RLC channel. In this way, the access network equipment needs to ensure that DRB and MRB are mapped to different Uu RLC channels and PC5 RLC channels.

[0320] 2) No restriction is made, and the indication message 3 is carried in the SRAP layer, which is used to indicate whether the radio bearer identifier corresponding to the data packet 1 is MRB or DRB.

[0321] For ease of description, the following description is given by taking the carrying indication message 3 as an example.

[0322] S802. The access network device sends message 1 to the first terminal device.

[0323] Correspondingly, the first terminal device receives message 1. Parameter 1 in message 1 is the identifier of multicast radio bearer 1.

[0324] The message 1 also includes an identifier of the second terminal device, which is used to indicate that the data packet 1 corresponds to the second terminal device.

[0325] In one possible implementation, message 1 also includes an indication message 3, which is used to indicate that the radio bearer identifier corresponding to data packet 1 is a multicast radio bearer identifier. In this way, the first terminal device can determine, based on indication message 3, whether the type of the radio bearer identifier corresponding to data packet 1 is a multicast radio bearer identifier or a data radio bearer identifier.

[0326] S803: The first terminal device determines, based on the identifier of the second terminal device, that data packet 1 corresponds to the second terminal device.

[0327] S804. The first terminal device determines channel 2 according to mapping relationship 3 and the identifier of multicast radio bearer 1.

[0328] For the description of S804, please refer to S505 and will not be repeated here.

[0329] S805. The first terminal device sends message 2 to the second terminal device through channel 2. Message 2 includes the identifier of multicast radio bearer 1, but does not include the identifier of the second terminal device.

[0330] Correspondingly, the second terminal device receives message 2 via channel 2.

[0331] Since data packet 1 is unidirectionally transmitted, message 2 may not include the identifier of the second terminal device. By sending the identifier of multicast radio bearer 1 to the second terminal device, the second terminal device may forward data packet 1 to the corresponding protocol entity according to the identifier of multicast radio bearer 1.

[0332] For the description of S805, please refer to the description of S506, which will not be repeated here.

[0333] It should be noted that the first terminal device can determine that the radio bearer identifier corresponding to the data packet 1 is a multicast radio bearer identifier through the indication message 3 carried in the message 1.

[0334] Optionally, the first terminal device can also determine that the radio bearer identifier corresponding to the data packet 1 is a multicast radio bearer identifier through the identifier of the logical channel 1 carried in the message 1. For example, the identifier 1 of the logical channel 1 corresponds to DRB1, and the identifier 2 of the logical channel 1 corresponds to MRB1. When the first terminal device receives the identifier 2 of the logical channel 1 carried in the message 1, it can determine that the radio bearer identifier corresponding to the data packet 1 is a multicast radio bearer identifier.

[0335] Optionally, after the second terminal device receives message 2, the second terminal device can determine that the radio bearer identifier corresponding to data packet 1 is a multicast radio bearer identifier through the identifier of the logical channel 2 corresponding to message 2. For example, identifier 1 of logical channel 2 corresponds to DRB1, and identifier 2 of logical channel 2 corresponds to MRB1. When the second terminal device receives identifier 2 of logical channel 2 carried in message 2, it can determine that the radio bearer identifier corresponding to data packet 1 is a multicast radio bearer identifier.

[0336] Optionally, message 2 may further include indication message 4, which is used to indicate that the radio bearer identifier corresponding to data packet 1 is a multicast radio bearer identifier. Thus, the second terminal device may determine, based on indication message 4, that the radio bearer identifier corresponding to data packet 1 is a multicast radio bearer identifier.

[0337] Through the above technical solution, the present application supports the first terminal device to forward the data packet to a suitable second terminal device.

[0338] 3. PTM mode and PTP mode

[0339] Fig. 9 900 is a schematic diagram of a protocol architecture 900 of an embodiment of the present application. The protocol architecture 900 is applicable to the first terminal device using both the PTP mode and the PTM mode on the PC5 interface. Fig. 9 As shown, the protocol architecture 900 includes:

[0340] Access network equipment: PDCP layer, RLC layer corresponding to PTM mode, MAC layer and PHY layer, SRAP layer, RLC layer, MAC layer and PHY layer corresponding to PTP mode.

[0341] First terminal device: the SRAP layer, RLC layer, MAC layer and PHY layer corresponding to the PTP mode on the Uu interface, and the RLC layer, MAC layer and PHY layer corresponding to the PTM mode on the Uu interface; the SRAP layer, RLC layer, MAC layer and PHY layer corresponding to the PTP mode on the PC5 interface, and the SRAP layer (this is optional), RLC layer, MAC layer and PHY layer corresponding to the PTM mode on the PC5 interface.

[0342] Second terminal device: PDCP layer, SRAP layer corresponding to PTP mode on PC5 interface, RLC layer, MAC layer and PHY layer, SRAP layer corresponding to PTM mode on PC5 interface (this is optional), RLC layer, MAC layer and PHY layer.

[0343] It should be noted that the functions of the various layers described in the protocol architecture 900 can be found in the definitions of existing standards and will not be repeated here.

[0344] The following will describe the communication method 1000 of an embodiment of the present application based on the protocol architecture 900.

[0345] Fig.10 1 is a schematic diagram of the interaction flow of the communication method 1000 of the embodiment of the present application. Fig.10 As shown, method 1000 includes:

[0346] S1001. An access network device sends a configuration message 1 to a first terminal device, and sends a configuration message 2 to a second terminal device.

[0347] Correspondingly, the first terminal device receives configuration message 1, and the second terminal device receives configuration message 2.

[0348] Configuration message 1 can be used to configure the first terminal device to forward the first data packet. Configuration message 2 can be used to configure the second terminal device to process the first data packet.

[0349] In a possible implementation manner, the configuration message 1 includes at least one of the following items: G-RNTI, indication information 5 and SRAP configuration 1.

[0350] In one example, the indication message 5 is a PTM transmission indication, which is used to instruct the access network device to transmit the data packet 1 through the PTM mode.

[0351] In one example, SRAP configuration 1 includes mapping relationship 1-mapping relationship 3, or SRAP configuration 1 includes mapping relationship 3, which is related to the mode in which the first terminal device sends data packet 1. For the description of both, please refer to the above text.

[0352] In a possible implementation, the configuration message 2 includes the indication message 6 and the multicast configuration information. The second terminal device can establish or reconfigure the corresponding PDCP entity according to the multicast configuration information in the configuration message 2, and the PDCP entity can be used by the second terminal device to process the received data packets accordingly.

[0353] In one example, the indication message 6 is a PTM transmission indication, which is used to instruct the first terminal device to transmit the data packet 1 via the PTM mode.

[0354] For ease of description, it is taken as an example that a first terminal device serves a second terminal device, and there are two multicast radio bearers, namely: MRB1 and MRB2.

[0355] Exemplarily, configuration message 1 includes: G-RNTI, CellGroupConfig and SL-L2RelayUE-Config.

[0356] 1) CellGroupConfig includes a Uu RLC channel configuration list, which includes three configurations, namely: {Uu LCID1, Uu RLC channel ID1, PTM indication}, {Uu LCID2, Uu RLC channel ID2}, {UuLCID3, Uu RLC channel ID3, PTM indication}. Among them, {Uu LCID1, Uu RLC channel ID1, PTM indication} and {UuLCID2, Uu RLC channel ID2} can correspond to MRB1 at the same time, and {Uu LCID2, Uu RLC channel ID2} and {Uu LCID3, Uu RLC channel ID3, PTM indication} can correspond to MRB2 at the same time.

[0357] 2) SL-L2RelayUE-Config includes the SRAP configuration corresponding to the second terminal device, the SRAP configuration includes a mapping relationship list, and the mapping relationship list includes 4 sets of configurations, namely: {MRB ID1, Uu RLC channel ID1, PC5 RLC channel ID1},

[0358] {MRB ID1, Uu RLC channel ID2, PC5 RLC channel ID2}, {MRB ID2, Uu RLC channel ID2, PC5

[0359] RLC channel ID3}, {MRB ID2, Uu RLC channel ID3, PC5 RLC channel ID4}.

[0360] For a description of the above configuration, see Fig.11 .

[0361] Fig.11 1100 is a schematic diagram of a configuration relationship 1100 of an embodiment of the present application. Fig.11 As shown, MRB1 is mapped to Uu RLC channel 1 and Uu RLC channel 2, MRB2 is mapped to Uu RLC channel 2 and Uu RLC channel 3, MRB1 is mapped to PC5 RLC channel 1 and PC5 RLC channel 2, and MRB2 is mapped to PC5 RLC channel 3 and PC5 RLC channel 4.

[0362] For example, the access network device sends data packet 1 through Uu RLC channel 1 in PTM mode, and the access network device sends data packet 1 through Uu RLC channel 2 in PTP mode, and the first terminal device receives two identical data packets 1 through Uu RLC channel 1 and UuRLC channel 2. The first terminal device can send data packet 1 through PC5 RLC channel 1 in PTM mode, and the first terminal device can send data packet 1 through PC5 RLC channel 2 in PTP mode.

[0363] Further, the first terminal device establishes a protocol entity 1 ( Fig. 9 The first terminal device in the PTP mode corresponds to the SRAP layer, RLC layer, MAC layer and PHY layer) and protocol entity 2 ( Fig. 9 The first terminal device corresponds to the SRAP layer, RLC layer, MAC layer and PHY layer of the PTM mode, protocol entity 1 is used for the first terminal device to transmit data packet 1 at interface 2 using the PTP mode, and protocol entity 2 is used for the first terminal device to transmit data packet 1 at interface 2 using the PTM mode.

[0364] Exemplarily, configuration message 2 includes a PC5 RLC channel configuration list, which includes four configurations, namely: {PC5 LCID1, PC5 RLC channel ID1, PTM indication}, {PC5 LCID2, PC5 RLC channel ID2}, {PC5 LCID3, PC5RLC channel ID3}, {PC5 LCID4, PC5 RLC channel ID4, PTM indication}. Among them, {PC5 LCID1, PC5 RLC channel ID1, PTM indication} and {PC5 LCID2, PC5 RLC channel ID2} can correspond to MRB1 at the same time, and {PC5 LCID3, PC5 RLC channel ID3} and {PC5LCID4, PC5 RLC channel ID4, PTM indication} can correspond to MRB2 at the same time.

[0365] For example, the first terminal device sends data packet 1 through PC5 RLC channel 1 in PTM mode, and the first terminal device sends data packet 1 through PC5 RLC channel 2 in PTP mode. The second terminal device receives two data packets 1 through PC5 RLC channel 1 and PC5 RLC channel 2, respectively. The second terminal device processes data packet 1 through protocol entity 3 and protocol entity 4, respectively.

[0366] Further, the second terminal device establishes a protocol entity 3 according to the configuration message 2 ( Fig. 9 The second terminal device in the PTP mode corresponds to the SRAP layer, RLC layer, MAC layer and PHY layer) and protocol entity 4 ( Fig. 9 The second terminal device corresponds to the SRAP layer, RLC layer, MAC layer and PHY layer of the PTM mode), the protocol entity 3 is used for the second terminal device to transmit data packet 1 using the PTP mode at interface 2, and the protocol entity 4 is used for the second terminal device to transmit data packet 1 using the PTM mode at interface 2.

[0367] S1002. The access network device sends data packet 1 to the first terminal device.

[0368] Correspondingly, the first terminal device receives data packet 1. After receiving data packet 1, the first terminal device submits the data packet 1 to the protocol entity on the PC5 interface for processing according to the MRB identifier corresponding to the data packet 1.

[0369] If the access network device configures both PTM mode transmission and PTP mode transmission for data packet 1, when sending data packet 1, the access network device can dynamically decide to send data packet 1 through PTM mode and / or PTP mode. That is, for a data packet, the access network device can send it only through the RLC entity configured in PTM mode, or only through the RLC entity configured in PTP mode, or through the RLC entity configured in PTM mode and the RLC entity configured in PTP mode.

[0370] If the access network device transmits data packet 1 via PTM mode and PTP mode simultaneously, the first terminal device receives data packet 1 via PTP mode and PTM mode respectively, and receives two data packets 1.

[0371] If the access network device transmits data packet 1 via PTM mode, the first terminal device receives data packet 1 via PTM mode and receives one data packet 1. If the access network device transmits data packet 1 via PTP mode, the first terminal device receives data packet 1 via PTP mode and receives one data packet 1. S1003. The first terminal device sends data packet 1 to the second terminal device.

[0372] Correspondingly, the second terminal device receives data packet 1.

[0373] When the first terminal device receives data packet 1 through PTP mode and PTM mode respectively, the first terminal device sends two data packets 1 to the second terminal device through PTP mode and PTM mode respectively, and the second terminal device receives two data packets 1 through PTP mode and PTM mode respectively; when the first terminal device receives data packet 1 through PTM mode, the first terminal device sends a data packet 1 to the second terminal device through PTM mode, and the second terminal device receives data packet 1 through PTM mode; when the first terminal device receives data packet 1 through PTP mode, the first terminal device sends a data packet 1 to the second terminal device through PTP mode, and the second terminal device receives data packet 1 through PTP mode.

[0374] For a description of S1003, see Figure 5-Figure 8 The description is not repeated here.

[0375] Furthermore, the second terminal device may forward data packet 1 to a corresponding PDCP entity for processing according to the identifier of the multicast wireless bearer of data packet 1.

[0376] Since the access network device can use PTM mode and PTM mode to transmit data packet 1 at the same time, the second terminal device will receive two data packets 1. After being processed by the protocol entity on the PC5 interface of the second terminal device, the two data packets 1 will be submitted to the same PDCP entity. The PDCP layer of the second terminal device needs to perform data packet deduplication processing.

[0377] Through the above-mentioned technical solution, the present application supports the access network equipment to be configured with PTP mode and PTM mode at the same time, the first terminal device can correctly forward the multicast service data packets transmitted in PTP mode and PTM mode to the corresponding second terminal device, and the second terminal device can identify the multicast wireless bearer corresponding to the data packet, thereby correctly delivering it to the PDCP entity, thereby ensuring the normal transmission of the multicast service.

[0378] Fig.12 1 is a schematic diagram of a protocol architecture 1200 of an embodiment of the present application. The protocol architecture 1200 is applicable to a first terminal device that does not distinguish between a PTP mode and a PTM mode on a PC5 interface. Fig.12 As shown, the protocol architecture 1200 includes:

[0379] Access network equipment: PDCP layer, RLC layer, MAC layer and PHY layer corresponding to PTM mode, SRAP layer, RLC layer, MAC layer and PHY layer corresponding to PTP mode.

[0380] First terminal device: SRAP layer, RLC layer, MAC layer and PHY layer corresponding to PTP mode on Uu interface; RLC layer, MAC layer and PHY layer corresponding to PTM mode on Uu interface; SRAP layer, RLC layer, MAC layer and PHY layer on PC5 interface.

[0381] Second terminal device: PDCP layer, SRAP layer, RLC layer, MAC layer and PHY layer on the PC5 interface.

[0382] It should be noted that the functions of the various layers described in the protocol architecture 1200 can be found in the definitions of existing standards and will not be repeated here.

[0383] The following will describe the communication method 1300 of an embodiment of the present application based on the protocol architecture 1200.

[0384] S1301. The access network device sends a configuration message 1 to a first terminal device, and the access network device sends a configuration message 2 to a second terminal device.

[0385] Correspondingly, the first terminal device receives configuration message 1, and the second terminal device receives configuration message 2.

[0386] For a description of S1301, see Fig.10The description of S1001 in will not be repeated here.

[0387] For ease of description, it is taken as an example that a first terminal device serves a second terminal device, and there are two multicast radio bearers, namely: MRB1 and MRB2.

[0388] Exemplarily, configuration message 1 includes: G-RNTI, CellGroupConfig and SL-L2RelayUE-Config.

[0389] 1) CellGroupConfig includes a Uu RLC channel configuration list, which includes three configurations, namely: {Uu LCID1, Uu RLC channel ID1, PTM indication}, {Uu LCID2, Uu RLC channel ID2}, {UuLCID3, Uu RLC channel ID3, PTM indication}. Among them, {Uu LCID1, Uu RLC channel ID1, PTM indication} and {UuLCID2, Uu RLC channel ID2} can correspond to MRB1 at the same time, and {Uu LCID2, Uu RLC channel ID2} and {Uu LCID3, Uu RLC channel ID3, PTM indication} can correspond to MRB2 at the same time.

[0390] 2) SL-L2RelayUE-Config includes the SRAP configuration corresponding to the second terminal device, the SRAP configuration includes a mapping relationship list, and the mapping relationship list includes 4 sets of configurations, namely: {MRB ID1, Uu RLC channel ID1, PC5 RLC channel ID1},

[0391] {MRB ID1, Uu RLC channel ID2, PC5 RLC channel ID1}, {MRB ID2, Uu RLC channel ID2, PC5

[0392] RLC channel ID2}, {MRB ID2, Uu RLC channel ID3, PC5 RLC channel ID2}.

[0393] For a description of the above configuration, see Fig.14 .

[0394] Fig.14 1400 is a schematic diagram of a configuration relationship of an embodiment of the present application. Fig.14 As shown, MRB1 is mapped to Uu RLC channel 1 and Uu RLC channel 2, MRB2 is mapped to Uu RLC channel 2 and Uu RLC channel 3, MRB1 is mapped to PC5 RLC channel 1, and MRB2 is mapped to PC5 RLC channel 2.

[0395] For example, the access network device sends data packet 1 through Uu RLC channel 1 in PTM mode, and the access network device sends data packet 1 through Uu RLC channel 2 in PTP mode. Accordingly, the first terminal device receives two identical data packets 1 through Uu RLC channel 1 and Uu RLC channel 2. Further, the first terminal device can send data packet 1 through PC5 RLC channel 1.

[0396] Further, the first terminal device establishes a protocol entity 5 ( Fig.12 The first terminal device in the SRAP layer, RLC layer, MAC layer and PHY layer on the PC5 interface, the protocol entity 5 is used for the first terminal device to transmit the data packet 1 on the interface 2.

[0397] Exemplarily, configuration message 2 includes a PC5 RLC channel configuration list, which includes 2 configurations, namely: {PC5 LCID1, PC5 RLC channel ID1} and {PC5 LCID2, PC5 RLC channel ID2}. Among them, {PC5 LCID1, PC5RLC channel ID1} can correspond to MRB1, and {PC5 LCID2, PC5 RLC channel ID2} can correspond to MRB2.

[0398] For example, the first terminal device sends data packet 1 through PC5 RLC channel 1, and the second terminal device receives data packet 1 through PC5 RLC channel 1. The second terminal device processes data packet 1 through protocol entity 6.

[0399] Further, the second terminal device establishes a protocol entity 6 ( Fig.12 The second terminal device corresponds to the SRAP layer, RLC layer, MAC layer and PHY layer of the PTP mode, and the protocol entity 6 is used by the second terminal device to transmit the data packet 1 at the interface 2.

[0400] S1302. The access network device sends data packet 1 to the first terminal device.

[0401] Accordingly, the first terminal device receives two data packets 1 .

[0402] For the description of S1302, please refer to the description of S1002, which will not be repeated here. S1303: The first terminal device sends a data packet 1 to the second terminal device.

[0403] Correspondingly, the second terminal device receives data packet 1.

[0404] When the first terminal device receives data packet 1 through PTP mode and PTM mode respectively, the first terminal device sends a data packet 1 to the second terminal device, and the second terminal device receives a data packet 1; when the first terminal device receives data packet 1 through PTM mode, the first terminal device sends a data packet 1 to the second terminal device through PTM mode, and the second terminal device receives data packet 1 through PTM mode; when the first terminal device receives data packet 1 through PTP mode, the first terminal device sends a data packet 1 to the second terminal device through PTP mode, and the second terminal device receives data packet 1 through PTP mode.

[0405] When the access network device transmits data packet 1 in both PTM mode and PTP mode, the first terminal device receives two data packets 1. After being processed by the protocol entity on the Uu interface, the two data packets 1 are delivered to the same PC5 SRAP entity. The first terminal device may perform data packet deduplication processing at the SRAP layer, or may not do so and send two data packets 1 to the second terminal device. There is no limitation on this. For a description of S1303, see Figure 5-Figure 8 The description is not repeated here.

[0406] Furthermore, the second terminal device forwards data packet 1 to a corresponding PDCP entity for processing according to the identifier of the multicast radio bearer of data packet 1.

[0407] Through the above-mentioned technical solution, the present application supports the access network equipment to be configured with PTP mode and PTM mode at the same time, the first terminal device can correctly forward the multicast service data packets transmitted in PTP mode and PTM mode to the corresponding second terminal device, and the second terminal device can identify the multicast wireless bearer corresponding to the data packet, thereby correctly delivering it to the PDCP entity, thereby ensuring the normal transmission of the multicast service.

[0408] Finally, the device embodiment of the embodiment of the present application is introduced.

[0409] In order to implement the functions in the method provided in the present application, the first terminal device, the second terminal device and the access network device may include hardware structures and / or software modules, and implement the above functions in the form of hardware structures, software modules, or hardware structures plus software modules. Whether one of the above functions is executed in the form of hardware structures, software modules, or hardware structures plus software modules depends on the specific application and design constraints of the technical solution.

[0410] Fig.151 is a schematic block diagram of a communication device 1500 of an embodiment of the present application. The communication device 1500 includes a processor 1510 and a communication interface 1520, and the processor 1510 and the communication interface 1520 can be connected to each other via a bus 1530. The communication device 1500 can be a first terminal device, a second terminal device, or an access network device.

[0411] Optionally, the communication device 1500 may further include a memory 1540. The memory 1540 includes, but is not limited to, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), or a portable read-only memory (CD-ROM), and the memory 1540 is used for related instructions and data.

[0412] The processor 1510 may be one or more central processing units (CPUs). When the processor 1510 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.

[0413] When the communication apparatus 1500 is a first terminal device, exemplarily, the processor 1510 is used to perform the following operations: receive an indication message 1 and a paging message 1; send a paging message 1 to a second terminal device according to the indication message 1 and the indication message 2, etc.

[0414] When the communication apparatus 1500 is a second terminal device, illustratively, the processor 1510 is configured to perform the following operations: sending an indication message 1 and receiving a paging message 1, etc.

[0415] When the communication device 1500 is an access network device, exemplarily, the processor 1510 is used to perform the following operations: receiving an indication message 1; sending a paging message 1, etc.

[0416] The above contents are only exemplary descriptions. When the communication device 1500 is a first terminal device / a second terminal device / an access network device, it will be responsible for executing the methods or steps related to the first terminal device / a second terminal device / an access network device in the above method embodiments.

[0417] The above description is only an exemplary description. For specific content, please refer to the content shown in the above method embodiment. Fig.15 The implementation of each operation in can also refer to Figure 2-Figure 14 The corresponding description of the method embodiment shown.

[0418] Fig.16 1 is a schematic block diagram of a communication device 1600 of an embodiment of the present application. The communication device 1600 may be a first terminal device / a second terminal device / an access network device, or may be a chip or module in the first terminal device / a second terminal device / an access network device, for implementing the method involved in the above embodiment. The communication device 1600 includes a transceiver unit 1610 and a processing unit 1620. The transceiver unit 1610 and the processing unit 1620 are exemplarily introduced below.

[0419] The transceiver unit 1610 may include a transmitting unit and a receiving unit. The transmitting unit is used to perform a transmitting action of the communication device, and the receiving unit is used to perform a receiving action of the communication device. For ease of description, the embodiment of the present application combines the transmitting unit and the receiving unit into one transceiver unit. A unified description is given here, and no further description is given later.

[0420] When the communication device 1600 is a first terminal device, illustratively, the transceiver unit 1610 is used to receive an indication message 1 and a paging message 1, etc. The processing unit 1620 is used to send a paging message 1, etc. to a second terminal device according to the indication message 1 and the indication message 2.

[0421] When the communication device 1600 is a second terminal device, illustratively, the transceiver unit 1610 is used to send an indication message 1 and receive a paging message 1; the processing unit 1620 can be used to process a received data packet 1, etc.

[0422] When the communication device 1600 is an access network device, illustratively, the transceiver unit 1610 is used to receive an indication message 1 and send a paging message 1, etc. The processing unit 1620 is used to determine the above-mentioned mapping relationship, etc.

[0423] The above contents are only exemplary descriptions. When the communication device 1600 is a first terminal device / a second terminal device / an access network device, it will be responsible for executing the methods or steps related to the first terminal device / a second terminal device / an access network device in the above method embodiments.

[0424] Optionally, the communication device 1600 further includes a storage unit 1630, and the storage unit 1630 is used to store a program or code for executing the aforementioned method.

[0425] Fig.15 and Fig.16 The device embodiment shown is used to implement Figure 2-Figure 14 The content described. Fig.15 and Fig.16 The specific execution steps and methods of the device shown can refer to the contents described in the aforementioned method embodiment.

[0426] Fig.171 is a schematic block diagram of a communication device 1700 of an embodiment of the present application. The communication device 1700 is used to implement the functions of a first terminal device / a second terminal device / an access network device. The communication device 1700 may be a chip in the first terminal device / a second terminal device / an access network device.

[0427] The communication device 1700 includes: an input / output interface 1720 and a processor 1710. The input / output interface 1720 may be an input / output circuit. The processor 1710 may be a signal processor, a chip, or other integrated circuit that can implement the method of the present application. The input / output interface 1720 is used for inputting or outputting signals or data.

[0428] For example, when the communication device 1700 is a first terminal device, the input / output interface 1720 is used to receive an indication message 1 and a paging message 1. The processor 1710 is used to send a paging message 1 to a second terminal device according to the indication message 1 and the indication message 2. The processor 1710 is also used to execute some or all of the steps of any method provided in the present application.

[0429] For example, the communication device 1700 is a second terminal device, and the input / output interface 1720 is used to send an indication message 1 and receive a paging message 1. In addition, the processor 1710 is also used to execute part or all of the steps of any method provided in the present application.

[0430] In one possible implementation, the processor 1710 implements the functions implemented by the network device or the terminal device by executing instructions stored in the memory.

[0431] Optionally, the communication device 1700 also includes a memory.

[0432] Optionally, the processor and memory are integrated together.

[0433] Optionally, the memory is outside the communication device 1700 .

[0434] In a possible implementation, the processor 1710 may be a logic circuit, and the processor 1710 inputs / outputs messages or signals through the input / output interface 1720. The logic circuit may be a signal processor, a chip, or other integrated circuit that can implement the method of the embodiment of the present application.

[0435] The above description of the communication device 1700 is only an exemplary description. The communication device 1700 can be used to execute the method described in the above embodiment. The specific content can be found in the description of the above method embodiment, which will not be repeated here.

[0436] Fig.181 is a schematic block diagram of a communication device 1800 according to an embodiment of the present application. The communication device 1800 may be an access network device or a chip in the access network device. The communication device 1800 is used to execute Figure 2-Figure 14 The operations in the method embodiment shown are performed by the access network device.

[0437] When the communication device 1800 is an access network device, for example, it is a base station. Fig.18 A simplified schematic diagram of the base station structure is shown. The base station includes module 1810, module 1820 and module 1830. Module 1810 is mainly used for baseband processing, controlling the base station, etc.; module 1810 is usually the control center of the base station, which can be generally referred to as a processor, and is used to control the base station to perform the processing operations on the network device side in the above method embodiment. Module 1820 is mainly used to store computer program code and data. Module 1830 is mainly used for receiving and transmitting radio frequency signals and converting radio frequency signals into baseband signals; module 1830 can generally be referred to as a transceiver module, a transceiver, a transceiver circuit, or a transceiver, etc. The transceiver module of module 1830, which can also be referred to as a transceiver or a transceiver, etc., includes an antenna 1833 and a radio frequency circuit ( Fig.18 Not shown), wherein the RF circuit is mainly used for RF processing. Optionally, the device for implementing the receiving function in module 1830 can be regarded as a receiver, and the device for implementing the transmitting function can be regarded as a transmitter, that is, module 1830 includes a receiver 1832 and a transmitter 1831. The receiver can also be called a receiving module, a receiver, or a receiving circuit, etc., and the transmitter can be called a transmitting module, a transmitter, or a transmitting circuit, etc.

[0438] Module 1810 and module 1820 may include one or more single boards, each of which may include one or more processors and one or more memories. The processor is used to read and execute the program in the memory to realize the baseband processing function and the control of the base station. If there are multiple single boards, each single board can be interconnected to enhance the processing capability. As an optional implementation, multiple single boards may share one or more processors, or multiple single boards may share one or more memories, or multiple single boards may share one or more processors at the same time.

[0439] For example, in one implementation, the transceiver module of module 1830 is used to perform Figure 2-Figure 14 In the embodiment shown, the access network device performs the related processes of sending and receiving. The processor of module 1810 is used to perform Figure 2-Figure 14 The illustrated embodiment is a process related to processing performed by the access network device.

[0440] In another implementation, the processor of module 1810 is used to execute Figure 2-Figure 14 The illustrated embodiment is a process related to the processing performed by the communication device.

[0441] In another implementation, the transceiver module of module 1830 is used to execute Figure 2-Figure 14 The illustrated embodiment shows a process related to transmission and reception performed by a communication device.

[0442] It should be understood that Fig.18 This is only an example and not a limitation. The access network device including the processor, memory and transceiver may not rely on Figures 15 to 17 The structure shown.

[0443] When the communication device 1800 is a chip, the chip includes a transceiver, a memory and a processor. The transceiver may be an input / output circuit or a communication interface; the processor may be a processor, a microprocessor or an integrated circuit integrated on the chip. The sending operation of the access network device in the above method embodiment may be understood as the output of the chip, and the receiving operation of the access network device in the above method embodiment may be understood as the input of the chip.

[0444] Fig.19 1 is a schematic block diagram of a communication device 1900 of an embodiment of the present application. The communication device 1900 may be a first terminal device / a second terminal device, a processor or a chip of the first terminal device / a second terminal device. The communication device 1900 may be used to perform the operations performed by the first terminal device / a second terminal device or a communication device in the above method embodiment.

[0445] When the communication device 1900 is a first terminal device / a second terminal device, Fig.19 FIG. 1 shows a simplified schematic diagram of the structure of a terminal device. Fig.19 As shown, the terminal device includes a processor, a memory, and a transceiver. The memory can store computer program codes, and the transceiver includes a transmitter 1931, a receiver 1932, and a radio frequency circuit ( Fig.19 Not shown), antenna 1933 and input / output device ( Fig.19 not shown).

[0446] The processor is mainly used to process communication protocols and communication data, as well as to control terminal devices, execute software programs, process software program data, etc. The memory is mainly used to store software programs and data. The radio frequency circuit is mainly used for converting baseband signals and radio frequency signals and processing radio frequency signals. The antenna is mainly used to send and receive radio frequency signals in the form of electromagnetic waves. Input and output devices. For example, touch screens, display screens, keyboards, etc. are mainly used to receive data input by users and output data to users. It should be noted that some types of terminal devices may not have input and output devices.

[0447] When data needs to be sent, the processor performs baseband processing on the data to be sent and outputs the baseband signal to the RF circuit. The RF circuit performs RF processing on the baseband signal and then sends the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the terminal device, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor. The processor converts the baseband signal into data and processes the data. For ease of explanation, Fig.19 Only one memory, processor and transceiver are shown. In an actual terminal device product, there may be one or more processors and one or more memories. The memory may also be referred to as a storage medium or a storage device. The memory may be set independently of the processor or integrated with the processor, and the embodiments of the present application do not limit this.

[0448] In the embodiment of the present application, the antenna and the radio frequency circuit with transceiver functions can be regarded as the transceiver module of the terminal device, and the processor with processing function can be regarded as the processing module of the terminal device.

[0449] like Fig.19 As shown, the terminal device includes a processor 1910, a memory 1920 and a transceiver 1930. The processor 1910 can be called a processing unit, a processing board, a processing module, a processing device, etc., and the transceiver 1930 can be called a transceiver unit, a transceiver, a transceiver device, etc.

[0450] Optionally, the device for implementing the receiving function in the transceiver 1930 may be regarded as a receiving module, and the device for implementing the transmitting function in the transceiver 1930 may be regarded as a transmitting module, that is, the transceiver 1930 includes a receiver and a transmitter. A transceiver may sometimes be referred to as a transceiver, a transceiver module, or a transceiver circuit, etc. A receiver may sometimes be referred to as a receiver, a receiving module, or a receiving circuit, etc. A transmitter may sometimes be referred to as a transmitter, a transmitting module, or a transmitting circuit, etc.

[0451] For example, in one implementation, the processor 1910 is used to execute Figure 2-Figure 14 In the embodiment shown, the first terminal device / the second terminal device performs the processing action, and the transceiver 1930 is used to perform Figure 2-Figure 14 The sending and receiving actions of the first terminal device / the second terminal device.

[0452] For example, in one implementation, the processor 1910 is used to execute Figure 2-Figure 14 In the embodiment shown, the first terminal device / the second terminal device performs the processing action, and the transceiver 1930 is used to perform Figure 2-Figure 14 The sending and receiving actions of the first terminal device / the second terminal device.

[0453] It should be understood that Fig.19This is only an example and not a limitation. The terminal device including the transceiver module and the processing module may not rely on Figures 15 to 17 The structure shown.

[0454] When the communication device 1900 is a chip, the chip includes a processor, a memory and a transceiver. The transceiver may be an input / output circuit or a communication interface; the processor may be a processing module or a microprocessor or an integrated circuit integrated on the chip. The sending operation of the terminal device in the above method embodiment may be understood as the output of the chip, and the receiving operation of the terminal device in the above method embodiment may be understood as the input of the chip.

[0455] The present application also provides a chip, including a processor, for calling and executing instructions stored in a memory from the memory, so that a communication device equipped with the chip executes the methods in the above examples.

[0456] The present application also provides another chip, including: an input interface, an output interface, and a processor, wherein the input interface, the output interface, and the processor are connected via an internal connection path, and the processor is used to execute the code in the memory, and when the code is executed, the processor is used to execute the method in each of the above examples. Optionally, the chip also includes a memory, and the memory is used to store computer programs or codes.

[0457] The present application also provides a processor, which is coupled to a memory and is used to execute the methods and functions involving a network device or a terminal device in any of the above-mentioned embodiments.

[0458] In another embodiment of the present application, a computer program product including instructions is provided. When the computer program product is run on a computer, the method of the above embodiment is implemented.

[0459] The present application also provides a computer program. When the computer program is executed in a computer, the method of the above embodiment is implemented.

[0460] In another embodiment of the present application, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a computer, the method described in the above embodiment is implemented.

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

[0462] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0463] In several embodiments provided in the present application, the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0465] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

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

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

Claims

1. A communication method, characterized in that: Applied to the first terminal device, including: receiving a first indication message from a second terminal device, where the first indication message is used to indicate a first service, where the first service is a service between the second terminal device and an access network device, and where the first service includes a multicast service; receiving a paging message from the access network device, the paging message including a second indication message, the second indication message being used to indicate a second service, the second service being a service between the second terminal device and the access network device, and the second service including a multicast service; Send the paging message to the second terminal device according to the first indication message and the second indication message.

2. The method according to claim 1, characterized in that The method further comprises: receiving a first message from the access network device, the first message including a first data packet and a first parameter, the first parameter being used to indicate a first multicast radio bearer or a first logical channel, the first logical channel belonging to a first interface, the first interface being a communication interface between the first terminal device and the access network device, and the first data packet belonging to the second service; A second message is sent to the second terminal device according to the first parameter, where the second message includes the first data packet.

3. The method according to claim 2, characterized in that The method further comprises: Receive a configuration message from the access network device, where the configuration message includes at least one of the following: The first mapping relationship, the second mapping relationship and the third mapping relationship, The first mapping relationship is used to associate the second terminal device with the first channel, The second mapping relationship is used to associate the first channel with the first multicast radio bearer, The third mapping relationship is used to associate the second channel with the first multicast radio bearer, The first data packet is received by the first terminal device at the first interface through the first channel; The first data packet is sent by the first terminal device through the second channel at the second interface, where the second interface is a communication interface between the first terminal device and the second terminal device. The first multicast radio bearer is used to carry the second service.

4. The method according to claim 3, characterized in that The first parameter is an identifier of the first logical channel, and the first logical channel is associated with the first channel.

5. The method according to claim 4, characterized in that The sending a second message to the second terminal device according to the first parameter includes: According to the first mapping relationship and the identifier of the first logical channel, it is determined that the first data packet corresponds to the second terminal device.

6. The method according to claim 4 or 5, characterized in that: The sending a second message to the second terminal device according to the first parameter includes: The identifier of the first multicast radio bearer is determined according to the identifier of the first logical channel and the second mapping relationship.

7. The method according to claim 6, characterized in that The sending a second message to the second terminal device according to the first parameter includes: The second channel is determined according to the identifier of the first multicast radio bearer and the third mapping relationship.

8. The method according to claim 7, characterized in that The sending a second message to the second terminal device according to the first parameter includes: The second message is sent to the second terminal device via the second channel, wherein the second message also includes an identifier of the first multicast radio bearer.

9. The method according to any one of claims 4 to 8, characterized in that The method further comprises: An identifier of a second logical channel is sent to the access network device, where the identifier of the second logical channel is used to identify a second logical channel, and the second logical channel belongs to the second interface.

10. The method according to any one of claims 4 to 9, characterized in that The method further comprises: Send the third mapping relationship to the second terminal device.

11. The method according to any one of claims 1 to 10, characterized in that The method further comprises: Send the first indication message to the access network device.

12. The method according to any one of claims 1 to 11, characterized in that The method further comprises: The capability information of the first terminal device is sent to the second terminal device, where the capability information of the first terminal device is used to indicate that the first terminal device supports multicast service transmission.

13. The method according to claim 12, characterized in that The method further comprises: A request message is received from the second terminal device, where the request message is used to request a capability message of the first terminal device.

14. The method according to claim 13, characterized in that The request information includes capability information of the second terminal device, and the capability information of the second terminal device is used to indicate that the second terminal device supports multicast service transmission.

15. A communication method, characterized in that: Applied to the second terminal device, including: Sending a first indication message to a first terminal device, where the first indication message is used to indicate a first service, where the first service includes a multicast service; A paging message is received from the first terminal device, wherein the paging message includes a second indication message, and the second indication message is used to indicate a second service, wherein the second service includes a multicast service.

16. The method according to claim 15, characterized in that The method further comprises: Sending a request message to the first terminal device, where the request message is used to request a capability message of the first terminal device, where the capability message of the first terminal device is used to indicate that the first terminal device supports multicast service transmission; Receive capability information of the first terminal device.

17. The method according to claim 16, characterized in that The request message includes a capability message of the second terminal device, and the capability message of the second terminal device is used to indicate that the first terminal device supports multicast service transmission.

18. The method according to any one of claims 15 to 17, characterized in that The method further comprises: receiving a first mapping relationship from the first terminal device, or receiving a first mapping relationship from an access network device, The first mapping relationship is used to associate the first channel with the first multicast radio bearer, A first data packet is received by the second terminal device through the first channel at a first interface, the first interface is a communication interface between the first terminal device and the second terminal device, the first multicast wireless bearer is used to carry the second service, and the first data packet belongs to the second service.

19. The method according to claim 18, characterized in that The method further comprises: A first message is received from the first terminal device, where the first message includes the first data packet and does not include an identifier of the second terminal device.

20. A communication method, characterized in that: Applied to access network equipment, including: receiving a first indication message from a first terminal device, where the first indication message is used to indicate a first service, where the first service includes a multicast service; A paging message is sent to the first terminal device, wherein the paging message includes a second indication message, and the second indication message is used to indicate a second service, wherein the second service includes a multicast service.

21. The method according to claim 20, characterized in that The method further comprises: A first message is sent to the first terminal device, the first message includes a first data packet and a first parameter, the first parameter is used to indicate a first multicast wireless bearer or a first logical channel, the first logical channel belongs to a first interface, the first interface is a communication interface between the first terminal device and the access network device, and the first data packet belongs to the second service.

22. The method according to claim 21, characterized in that The method further comprises: Sending a first configuration message to the first terminal device, where the first configuration message includes at least one of the following: The first mapping relationship, the second mapping relationship and the third mapping relationship, The first mapping relationship is used to associate the second terminal device with the first channel, The second mapping relationship is used to associate the first channel with the first multicast radio bearer, The third mapping relationship is used to associate the second channel with the first multicast radio bearer, The first data packet is sent by the access network device through the first channel on the first interface; The first data packet is sent by the first terminal device through the second channel on the second interface, and the second interface is a communication interface between the first terminal device and the second terminal device. The first multicast radio bearer is used to carry the second service.

23. The method according to claim 22, characterized in that The first parameter is an identifier of the first logical channel, and the first logical channel is associated with the first channel.

24. The method according to claim 22 or 23, characterized in that The method further comprises: Receive an identifier of a second logical channel from the first terminal device, where the identifier of the second logical channel is used to identify the second logical channel, and the second logical channel belongs to the second interface.

25. A communication device, characterized in that: The communication device comprises means for performing the method according to any one of claims 1 to 24.

26. A communication device, characterized in that: include: A processor, configured to execute computer instructions stored in the memory, so that the communication device performs the method according to any one of claims 1 to 24.

27. A computer-readable storage medium, characterized in that: Used to store a computer program, the computer program comprising instructions for implementing the method according to any one of claims 1 to 24.

28. A computer program product, characterized in that The computer program product comprises computer program code, When the computer program code is executed by a communication unit, a processing unit or a transceiver, or a processor of a communication device, the communication device is caused to perform the method according to any one of claims 1 to 24.

29. A chip system, characterized in that: It includes a processor for calling and running a computer program from a memory, so that a device equipped with the chip system executes the method described in any one of claims 1 to 24.

30. A communication system, characterized in that: include: a first terminal device and a second terminal device; The first terminal device is used to perform the method according to any one of claims 1 to 14; The second terminal device is used to execute the method according to any one of claims 15 to 19.

Images