Communication method and communication apparatus

Abstract

A communication method and a communication apparatus, relating to the technical field of communications. In the method, on the basis of a first indication message sent by a remote terminal device (remote UE) and a second indication message carried in a paging message sent by an access network device, a relay terminal device (relay UE) can determine whether to forward the paging message to the remote terminal device; if the first indication message and the second indication message are the same, the relay terminal device determines to forward the paging message; and if the first indication message and the second indication message are different, the relay terminal device determines not to forward the paging message. The first indication message is used for indicating a first service, and the second indication message is used for indicating a second service, the first service and the second service each comprising a multicast service. 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

Communication method and communication device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on September 15, 2023, with application number 202311197076.3 and application name “Communication Method and Communication Device”, the entire contents of which are incorporated by reference into this application. Technical Field

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

[0003] UE-to-Network Relay (U2N Relay) is a technology that uses a relay terminal device to facilitate communication between a remote terminal device and access network equipment. The relay terminal device and the remote terminal device communicate via a sidelink (SL), while the relay terminal device and the access network equipment communicate over the air interface.

[0004] 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 the idle state (IDLE) or inactive state (INACTIVE) to the connected state (CONNECT) based on the paging information and perform unicast service transmission with the access network device.

[0005] For multicast / broadcast services (MBS) transmission, a relay terminal device may be unable to forward the paging information of an access network device to a corresponding remote terminal device, and the access network device may be unable to accurately page the corresponding remote terminal device.

[0006] Summary of the Invention

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

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

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

[0010] In the above solution, the first terminal device can determine whether to forward the paging message to the second terminal device based on the first indication message sent by the second terminal device and the second indication message included in the paging message sent by the access network device. If the indication messages are identical, the first terminal device determines to forward the paging message; if they are different, the first terminal device determines not to forward the paging message. 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.

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

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

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

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

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

[0016] In certain 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.

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

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

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

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

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

[0022] 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 based on the first parameter, thereby ensuring correct transmission of the second service data.

[0023] In one 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 being used to associate the second terminal device with the first channel, the second mapping relationship being used to associate the first channel with the first multicast wireless bearer, the third mapping relationship being used to associate the second channel with the first multicast wireless bearer, the first data packet being received by the first terminal device through the first channel at the first interface; the first data packet being sent by the first terminal device through the second channel at the second interface, the second interface being a communication interface between the first terminal device and the second terminal device, and the first multicast wireless bearer being used to carry the second service.

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

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

[0026] In this way, the use of the sidelink relay adaptation protocol (SRAP) on the first interface can be avoided, and the normal forwarding of the second service data can be guaranteed, and the first terminal device can be guaranteed to correctly receive the second service data.

[0027] In a possible implementation, 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.

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

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

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

[0031] In a possible implementation, 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.

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

[0033] 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, where the second message also includes an identifier of the first multicast radio bearer.

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

[0035] In a possible implementation, 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.

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

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

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

[0039] 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 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 includes the identifier of the first multicast wireless bearer, and the second message does not include the identifier of the second terminal device.

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

[0041] In a possible implementation, 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.

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

[0043] In one 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, where 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.

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

[0045] In 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 radio 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 comprising the first data packet.

[0046] In one 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 being used to associate the second terminal device with the first channel, the second mapping relationship being used to associate the first channel with the first multicast wireless bearer, the third mapping relationship being used to associate the second channel with the first multicast wireless bearer, the first data packet being received by the first terminal device through the first channel at the first interface; the first data packet being sent by the first terminal device through the second channel at the second interface, the second interface being a communication interface between the first terminal device and the second terminal device, and the first multicast wireless bearer being used to carry the second service.

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

[0048] In a possible implementation, 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.

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

[0050] In a possible implementation, 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.

[0051] 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 the second channel, where the second message also includes an identifier of the first multicast radio bearer.

[0052] In a possible implementation, 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.

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

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

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

[0056] 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 being 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 being used for the first terminal device to transmit the first data packet in point-to-multipoint mode on the second interface.

[0057] For the description of the beneficial effects of the second aspect and any one of the solutions described in the second aspect, please refer 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.

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

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

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

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

[0062] In a possible implementation, 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.

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

[0064] For the description of the beneficial effects of the third aspect and any one of the solutions described in the third aspect, please refer 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.

[0065] 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 the 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.

[0066] In the above solution, 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 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.

[0067] In one 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.

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

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

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

[0071] 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, the 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.

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

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

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

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

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

[0077] In one 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 the 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.

[0078] 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 point-to-point mode and point-to-multipoint mode.

[0079] 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 the 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.

[0080] In one 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.

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

[0082] For the description of the beneficial effects of the fifth aspect and any one of the schemes in the fifth aspect, please refer 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.

[0083] In the 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.

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

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

[0086] In one 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.

[0087] For the description of the beneficial effects of the sixth aspect and any one of the solutions in the sixth aspect, please refer to the description of the beneficial effects of the fourth aspect and any one of the solutions in the fourth aspect, and no further details will be given.

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

[0089] In one possible implementation, the method also includes: sending a first message to the 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.

[0090] In one 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 being used to associate the second terminal device with the first channel, the second mapping relationship being used to associate the first channel with the first multicast wireless bearer, the third mapping relationship being used to associate the second channel with the first multicast wireless bearer, the first data packet being sent by the access network device through the first channel on the first interface; the first data packet being sent by the first terminal device through the second channel on the second interface, the second interface being the communication interface between the first terminal device and the second terminal device, and the first multicast wireless bearer being used to carry the second service.

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

[0092] 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 the second logical channel, and the second logical channel belongs to the second interface.

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

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

[0095] In one possible implementation, the first configuration message also includes a fourth indication message, which is used to indicate the configuration of the first protocol entity and the second protocol entity, 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.

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

[0097] In one possible implementation, the second configuration message also includes a fifth indication message, which is used to indicate the 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 point-to-point mode on the second interface, and the second protocol entity being used for the first terminal device to transmit the first data packet in point-to-multipoint mode on the second interface.

[0098] For the description of the beneficial effects of the seventh aspect and any one of the solutions in the seventh aspect, please refer to the description of the beneficial effects of the first aspect and any one of the solutions in the first aspect, and no further details will be given.

[0099] In the 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.

[0100] In one 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 being used to associate the second terminal device with the first channel, the second mapping relationship being used to associate the first channel with the first multicast wireless bearer, the third mapping relationship being used to associate the second channel with the first multicast wireless bearer, the first data packet being sent by the access network device through the first channel on the first interface; the first data packet being sent by the first terminal device through the second channel on the second interface, the second interface being the communication interface between the first terminal device and the second terminal device, and the first multicast wireless bearer being used to carry the second service.

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

[0102] 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 the second logical channel, and the second logical channel belongs to the second interface.

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

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

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

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

[0107] In one possible implementation, the second configuration message also includes a third indication message, which 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.

[0108] For the description of the beneficial effects of the eighth aspect and any one of the solutions described in the eighth aspect, please refer 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.

[0109] 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 units and / or modules for executing the method provided in any one of the above implementations of the first to eighth aspects.

[0110] In one implementation, the communication device is a device (e.g., a first terminal device, a second terminal device, or an access network device). 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. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input / output interface may be an input / output circuit.

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

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

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

[0114] 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.).

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

[0116] For the operations such as sending and acquiring / receiving involved in the processor, unless otherwise specified, or if they do not conflict with their actual functions or internal logic in the relevant descriptions, they can be understood as processor output, reception, input and other operations, and can also be understood as sending and receiving operations performed by the radio frequency circuit and antenna. This application does not limit this.

[0117] In the 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 implementation methods of the first to eighth aspects.

[0118] In a thirteenth aspect, a computer program product comprising instructions is provided, which, when run on a computer, enables the computer to execute the method provided by any one of the above-mentioned implementations of the first to eighth aspects.

[0119] In the fourteenth aspect, a chip system is provided, which includes a processor, which is used to call and run computer instructions from a memory, so that a device equipped with the chip system executes the method provided in any one of the above-mentioned implementation methods of the first to eighth aspects.

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

[0121] Optionally, as an implementation method, the chip system also includes a memory, in which a computer program or instruction is stored, and the processor is used to execute the computer program or instruction stored on the memory. When the computer program or instruction is 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.

[0122] 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 methods of the first to third aspects, and the second terminal device is used to execute the method provided by any one of the implementation methods of the fourth to sixth aspects.

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

[0124] FIG1 is a schematic diagram of a communication system 100 to which an embodiment of the present application is applicable.

[0125] FIG2 is a schematic diagram of an interaction flow of a communication method 200 according to an embodiment of the present application.

[0126] FIG3 is a schematic diagram of an interaction flow of a communication method 300 according to an embodiment of the present application.

[0127] FIG4 is a schematic diagram of a protocol architecture 400 according to an embodiment of the present application.

[0128] FIG5 is a schematic diagram of an interaction flow of a communication method 500 according to an embodiment of the present application.

[0129] FIG6 is a schematic diagram of an interaction flow of a communication method 600 according to an embodiment of the present application.

[0130] FIG7 is a schematic diagram of a protocol architecture 700 according to an embodiment of the present application.

[0131] FIG8 is a schematic diagram of an interaction flow of a communication method 800 according to an embodiment of the present application.

[0132] FIG9 is a schematic diagram of a protocol architecture 900 according to an embodiment of the present application.

[0133] FIG10 is a schematic diagram of the interaction flow of a communication method 1000 according to an embodiment of the present application.

[0134] FIG11 is a schematic diagram of a configuration relationship 1100 according to an embodiment of the present application.

[0135] FIG12 is a schematic diagram of a protocol architecture 1200 according to an embodiment of the present application.

[0136] FIG13 is a schematic diagram of an interaction flow of a communication method 1300 according to an embodiment of the present application.

[0137] FIG14 is a schematic diagram of a configuration relationship 1400 according to an embodiment of the present application.

[0138] FIG15 is a schematic block diagram of a communication device 1500 according to an embodiment of the present application.

[0139] FIG16 is a schematic block diagram of a communication device 1600 according to an embodiment of the present application.

[0140] FIG17 is a schematic block diagram of a communication device 1700 according to an embodiment of the present application.

[0141] FIG18 is a schematic block diagram of a communication device 1800 according to an embodiment of the present application.

[0142] FIG19 is a schematic block diagram of a communication device 1900 according to an embodiment of the present application. DETAILED DESCRIPTION

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

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

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

[0146] 3. The various numerical 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 order of execution 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.

[0147] At the same time, any embodiment or design described in this 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 the relevant concepts in a concrete manner to facilitate understanding.

[0148] 4. The terms "comprise" and "have" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or apparatus that includes 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.

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

[0150] The information enabled by the information is called information to be enabled. In the specific implementation process, there are many ways to enable the enabled information, such as but not limited to, directly enabling the information to be 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, it is also possible to enable specific information with the help of the arrangement order of each piece of information agreed in advance (such as specified in the protocol), thereby reducing the enabling overhead to a certain extent. At the same time, it is also possible to identify the common parts of each piece of information and enable them uniformly to reduce the enabling overhead caused by enabling the same information separately.

[0151] 6. In this application, "pre-configuration" may include pre-definition, such as protocol definition. "Pre-definition" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., including each network element). This application does not limit the specific implementation method.

[0152] 7. "Storage" or "saving" as used in this application may refer to storage in one or more memories. The one or more memories may be provided separately or integrated into an encoder or decoder, a processor, or a communication device. The one or more memories may also be provided in part separately and in part integrated into a decoder, processor, or communication device. The type of memory may be any form of storage medium and is not limited thereto.

[0153] 8. The “protocol” referred to 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. This application does not limit this.

[0154] 9. The arrows or boxes indicated by dotted lines in the schematic diagrams in the accompanying drawings of this application specification represent optional steps or optional modules.

[0155] 10. Unless otherwise specified, “ / ” indicates that the objects associated with each other are in an “or” relationship. For example, A / B can mean A or B. “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 mean: A exists alone, A and B exist at the same time, and B exists alone. A and B can be singular or plural.

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

[0157] Figure 1 is a schematic diagram of a communication system 100 applicable to an embodiment of the present application. As shown in Figure 1 , 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 in communicating with the access network device. For example, it assists in the transmission of services between the second terminal device and the access network device, such as unicast 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.

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

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

[0160] 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 device, 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), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a communication device carried on a high-altitude aircraft, a wearable device, a drone, a robot, a terminal in device-to-device (D2D) communication, 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 similar device. 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.

[0161] The communication device used to implement the functions of the terminal device can be the terminal device, or it can be a device that can support the terminal device to implement the functions, such as a chip system. The device can be installed in the terminal device or used in conjunction with the terminal device. In this application, the chip system can be composed of a chip or include a chip and other discrete devices.

[0162] Access network equipment is a device with wireless transceiver functions used to communicate with terminal devices. 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 gateway (BNG), an aggregation switch or the 3rd generation partnership project (3GPP) access equipment, etc.

[0163] The 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). The network device 110 can also include various forms of base stations, such as macro base stations, micro base stations (also known as small stations), relay stations, transmission points (transmitting and receiving points, TRP), transmission points (transmitting points, TP), mobile switching centers, and devices that perform base station functions in device-to-device (D2D), vehicle-to-everything (V2X), and machine-to-machine (M2M) communications, network devices in non-terrestrial networks (NTN), etc., without specific limitation.

[0164] The access network equipment may also include network elements or modules that implement some functions of the base station, such as 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 functions 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 RU in the O-RAN system, etc., without limitation.

[0165] In different systems, CU (or CU-CP and CU-UP), DU or RU may have different names, and those skilled in the art can 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.

[0166] The communication device used to implement the functions of the access network device can be the access network device, or it can be a device that can support the access network device to implement the functions, such as a chip system. The device can be installed in the access network device or used in conjunction with the access network device. The chip system in the embodiments of the present application can be composed of a chip, or it can include a chip and other discrete devices.

[0167] The communication system 100 may 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, inter-satellite communication, satellite communication and other NTN systems. Among them, the satellite communication system includes a satellite base station and terminal equipment. The satellite base station provides communication services for the terminal equipment. 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.

[0168] The communication system 100 may also be a terrestrial 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.

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

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

[0171] For ease of understanding and explanation, the following describes the communication method of the embodiment of the present application using 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.).

[0172] FIG2 is a schematic diagram of an interaction flow of a communication method 200 according to an embodiment of the present application. As shown in FIG2 , the method 200 includes:

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

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

[0175] 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 can be compatible with existing standards.

[0176] Optionally, in one possible example, 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, as long as it is not a unicast service, and is not limited to this. 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 for service 1 to the second terminal device.

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

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

[0179] Optionally, in one possible implementation, indication 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 the TMGI or an identifier similar to TMGI. The TMGI can be used to identify a multicast session and is composed of a PLMN identifier and a service identifier (service ID). For further description of TMGI, please refer to the description of the existing standard and will not be repeated here.

[0180] Optionally, the first terminal device may also send an indication message 1 to the access network device. For example, the first terminal device may send a SidelinkUEInformationNR message to the access network device, where 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 include 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.

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

[0182] 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 service 2. Service 2 includes a multicast service.

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

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

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

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

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

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

[0189] The first terminal device can determine whether to forward paging message 1 to the second terminal device by comparing whether indication message 1 is identical to indication message 2. In one example, if indication message 1 is identical to indication message 2, then 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, then it is determined not to forward paging message 1 to the second terminal device.

[0190] Optionally, in one 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 multicast service transmission with the access network device.

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

[0192] In the above solution, the first terminal device can determine whether to forward paging message 1 to the second terminal device based on indication message 1 sent by the second terminal device and indication message 2 carried in paging message 1 sent by the access network device. If the indication messages are identical, the first terminal device determines to forward the paging message; if they are different, the first terminal device determines not to forward the paging message. 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.

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

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

[0195] Accordingly, 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.

[0196] Optionally, the request message 1 may further 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.

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

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

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

[0200] In one example, the request message 1 may be a UECapabilityEnquirySidelink message, or the request message 1 may be included in a UECapabilityEnquirySidelink message, and the UECapabilityEnquirySidelink message may further include capability information of the second terminal device, thereby achieving compatibility with existing standards.

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

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

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

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

[0205] Optionally, the first terminal device may indicate whether the first terminal device supports multicast services by determining 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.

[0206] Optionally, the first terminal device may send an indication message to the second terminal device, where 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, where a bit value of 1 indicates that the first terminal device supports the multicast service, and a bit value of 0 indicates that the first terminal device does not support the multicast service, and vice versa, without limitation.

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

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

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

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

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

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

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

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

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

[0216] For a second terminal device in the idle state, the core network (CN) initiates a separate paging call 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, which broadcasts the paging message (the paging message is a message of the Uu interface) over the air interface. The first terminal device forwards the paging message based on 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.

[0217] For a second terminal device in an inactive state, the access network device initiates a separate paging call to the second terminal device. For example, the access network device broadcasts a paging message over the air interface, and the first terminal device forwards the paging message based on 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.

[0218] Through the above technical solution, the second terminal device in the idle state or inactive state can obtain the service information multicast by the access network device, and thus enter the connected state to receive the multicast service data from the access network device.

[0219] The following describes how the second terminal device obtains data of the multicast service sent by the access network device in conjunction with Figure 3. The solution described in Figure 3 can be independent of the solution described in Figure 2, or it can be combined with the solution described in Figure 2 to form a new solution, which is described here as a whole and will not be further described below.

[0220] FIG3 is a schematic diagram of an interaction flow of a communication method 300 according to an embodiment of the present application. As shown in FIG3 , the method 300 includes:

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

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

[0223] In one example, logical channel 1 belongs to interface 1, which is the communication interface between the first terminal device and the access network device. In other words, interface 1 is the 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.

[0224] Optionally, in one 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.

[0225] Optionally, in a possible implementation, the first terminal device may also determine the PC5 (radio link control, RLC) channel according to parameter 1, and may determine that data packet 1 corresponds to the second terminal device according to the identifier of the second terminal device, as described in FIG8 .

[0226] Optionally, in one 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, the use of SRAP on interface 1 can be avoided, while ensuring that service 2 data is forwarded normally and that the first terminal device can correctly receive service 2 data.

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

[0228] For the description of S320 , please refer to FIG. 4 to FIG. 9 , and no further details are given here.

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

[0230] The solution shown in FIG3 will be further described below in conjunction with FIG4 to FIG14.

[0231] For ease of description, the following describes three scenarios: point to point (PTP) mode, point to multipoint (PTM) mode, and PTP mode and PTM mode.

[0232] 1. PTM Model

[0233] FIG4 is a schematic diagram of a protocol architecture 400 according to an embodiment of the present application. The protocol architecture 400 is applicable to the PTM mode. As shown in FIG4 , the protocol architecture 400 includes:

[0234] Access network equipment: Packet Data Convergence Protocol (PDCP), RLC, Media Access Control (MAC), and Physical (PHY) layers. The PTM mode is used between the PDCP and RLC layers for multicast service transmission.

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

[0236] Second terminal device: RLC layer, MAC layer and PHY layer on the PC5 interface, 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.

[0237] Optionally, both the first terminal device and the second terminal device may further include an SRAP layer. The SRAP layer primarily functions to multiplex and demultiplex bearers, namely, to support multiplexing different bearers onto a single bearer or splitting a single bearer into different bearers, and to distinguish data from 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.

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

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

[0240] It should be noted that the content shown in FIG4 is only understood as an example, and other layers may also be included. When other layers are included, the division method of other layers is not limited, and they can be divided into CUs or DUs, which is not limited.

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

[0242] The following describes the communication method 500 and the communication method 600 according to the embodiment of the present application based on the protocol architecture 400.

[0243] FIG5 is a schematic diagram of an interaction flow of a communication method 500 according to an embodiment of the present application. As shown in FIG5 , the method 500 includes:

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

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

[0246] It should be uniformly explained that when the access network device adopts a 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. However, this is not strictly limited and is described only as an example. For example, the CU generates configuration message 1, and the DU sends configuration message 1 to the first terminal device. This is uniformly explained here and will not be repeated below.

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

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

[0249] 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 the at least one mapping relationship mentioned above.

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

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

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

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

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

[0255] Optionally, the first terminal device may send the correspondence between the identifier of logical channel 1 and the identifier of channel 1 to the access network device. After obtaining the correspondence 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. It may also 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 to this.

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

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

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

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

[0260] 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 based on the multicast configuration information in the configuration message 2. The PDCP entity can be used by the second terminal device to perform corresponding processing on the received data packets.

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

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

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

[0264] 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, the use of SRAP on interface 1 can be avoided, which can ensure that service 2 data is forwarded normally and that the first terminal device can correctly receive service 2 data.

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

[0266] For example, the identifier of logical channel 1 is used to identify logical channel 1. 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 based on 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.

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

[0268] S504. The first terminal device determines the identifier of multicast radio bearer 1 based on the identifier of logical channel 1 and mapping relationship 2.

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

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

[0271] For example, the first terminal device can determine channel 2 using 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 using mapping relationship 2 and the identifier of multicast radio bearer 1, and can also determine channel 2 using the identifier of channel 2. In this way, the first terminal device can determine the specific channel on which to send data packet 1 to the second terminal device.

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

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

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

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

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

[0277] FIG6 is a schematic diagram of an interaction flow of a communication method 600 according to an embodiment of the present application. As shown in FIG6 , the method 600 includes:

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

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

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

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

[0282] Accordingly, the second terminal device receives mapping relationship 3. In this way, the second terminal device can determine the identifier of multicast radio bearer 1 corresponding to data packet 1 based on mapping relationship 3 and the identifier of channel 2, and then forward data packet 1 to the corresponding protocol entity based on the identifier of multicast radio bearer 1.

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

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

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

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

[0287] Furthermore, after the access network device obtains the identifier of logical channel 2, the access network device configures mapping relationship 3 and sends 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 in the configuration message 2 shown in Figure 5.

[0288] In one 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 radio bearer 1, and logical channel 2 is associated with channel 2. The second terminal device can then obtain mapping relationship 3.

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

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

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

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

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

[0294] S605. The first terminal device determines the identifier of multicast radio bearer 1 based on the identifier of logical channel 1 and mapping relationship 2.

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

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

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

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

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

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

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

[0302] For example, the multicast process is:

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

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

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

[0306] 2. PTP Mode

[0307] FIG7 is a schematic diagram of a protocol architecture 700 according to an embodiment of the present application. The protocol architecture 700 is applicable to the PTP mode. As shown in FIG7 , the protocol architecture 700 includes:

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

[0309] First terminal device: SRAP layer, RLC layer, MAC layer and PHY layer on the Uu interface, SRAP layer, RLC layer, MAC layer and PHY layer on the PC5 interface, the SRAP layer, RLC layer, MAC layer and PHY layer on the 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 the PC5 interface are respectively connected to the SRAP layer, RLC layer, MAC layer and PHY layer of the second terminal device.

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

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

[0312] It should be noted that when the access network equipment 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.

[0313] The following describes the communication method 800 of an embodiment of the present application based on the protocol architecture 700.

[0314] FIG8 is a schematic diagram of an interaction flow of a communication method 800 according to an embodiment of the present application. As shown in FIG8 , the method 800 includes:

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

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

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

[0318] Since the identifier of the multicast radio bearer (MBS radio bearer, MRB) and the identifier of the data radio bearer (data radio bearer, DRB) may be the same, it may cause forwarding errors in the first terminal device. For example, MRB1 corresponds to PC5RLC channel 1, and DRB1 corresponds to PC5RLC 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.

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

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

[0321] 2) No restriction is imposed, 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 an MRB or a DRB.

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

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

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

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

[0326] In one possible implementation, message 1 further 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.

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

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

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

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

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

[0332] Since data packet 1 is a unidirectional transmission, 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 can forward data packet 1 to the corresponding protocol entity according to the identifier of multicast radio bearer 1.

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

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

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

[0336] 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, the identifier 1 of the logical channel 2 corresponds to DRB1, and the identifier 2 of the logical channel 2 corresponds to MRB1. Then, when the second terminal device receives the identifier 2 of the 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.

[0337] Optionally, message 2 may further include an indication message 4, 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 second terminal device may determine that the radio bearer identifier corresponding to data packet 1 is a multicast radio bearer identifier based on indication message 4.

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

[0339] 3. PTM mode and PTP mode

[0340] FIG9 is a schematic diagram of a protocol architecture 900 according to an embodiment of the present application. The protocol architecture 900 is applicable to a first terminal device that uses both the PTP mode and the PTM mode on the PC5 interface. As shown in FIG9 , the protocol architecture 900 includes:

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

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

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

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

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

[0346] FIG10 is a schematic diagram of an interaction flow of a communication method 1000 according to an embodiment of the present application. As shown in FIG10 , the method 1000 includes:

[0347] S1001. The access network device sends configuration message 1 to the first terminal device, and sends configuration message 2 to the second terminal device.

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

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

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

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

[0352] 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 descriptions of both, please refer to the above text.

[0353] In one possible implementation, the configuration message 2 includes the indication message 6 and the 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 process the received data packets accordingly.

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

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

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

[0357] 1) CellGroupConfig includes a Uu RLC channel configuration list, which includes three configurations: {Uu LCID1, Uu RLC channel ID1, PTM indication}, {Uu LCID2, Uu RLC channel ID2}, and {Uu LCID3, Uu RLC channel ID3, PTM indication}. Among them, {Uu LCID1, Uu RLC channel ID1, PTM indication} and {Uu LCID2, Uu RLC channel ID2} can simultaneously correspond to MRB1, and {Uu LCID2, Uu RLC channel ID2} and {Uu LCID3, Uu RLC channel ID3, PTM indication} can simultaneously correspond to MRB2.

[0358] 2) SL-L2RelayUE-Config includes the SRAP configuration corresponding to the second terminal device. The SRAP configuration includes a mapping relationship list. The mapping relationship list includes 4 sets of configurations, namely: {MRB ID1, Uu RLC channel ID1, PC5RLC channel ID1}, {MRB ID1, Uu RLC channel ID2, PC5RLC channel ID2}, {MRB ID2, Uu RLC channel ID2, PC5RLC channel ID3}, {MRB ID2, Uu RLC channel ID3, PC5RLC channel ID4}.

[0359] For a description of the above configuration, please refer to FIG11 .

[0360] FIG11 is a schematic diagram of a configuration relationship 1100 according to an embodiment of the present application. As shown in FIG11 , 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.

[0361] 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. The first terminal device receives two identical data packets 1 through Uu RLC channel 1 and Uu RLC 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.

[0362] Furthermore, the first terminal device establishes protocol entity 1 (the first terminal device in Figure 9 corresponds to the SRAP layer, RLC layer, MAC layer and PHY layer of the PTP mode) and protocol entity 2 (the first terminal device in Figure 9 corresponds to the SRAP layer, RLC layer, MAC layer and PHY layer of the PTM mode) according to the configuration message 1. Protocol entity 1 is used for the first terminal device to transmit data packet 1 in PTP mode at interface 2, and protocol entity 2 is used for the first terminal device to transmit data packet 1 in PTM mode at interface 2.

[0363] Exemplarily, configuration message 2 includes a PC5RLC channel configuration list, which includes four configurations: {PC5LCID1, PC5RLC channel ID1, PTM indication}, {PC5LCID2, PC5RLC channel ID2}, {PC5LCID3, PC5RLC channel ID3}, and {PC5LCID4, PC5RLC channel ID4, PTM indication}. Among them, {PC5LCID1, PC5RLC channel ID1, PTM indication} and {PC5LCID2, PC5RLC channel ID2} can both correspond to MRB1, and {PC5LCID3, PC5RLC channel ID3} and {PC5LCID4, PC5RLC channel ID4, PTM indication} can both correspond to MRB2.

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

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

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

[0367] Accordingly, 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.

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

[0369] If the access network device transmits data packet 1 through PTM mode and PTP mode at the same time, the first terminal device receives data packet 1 through PTP mode and PTM mode respectively, and receives two data packets 1.

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

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

[0372] 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 one 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 one data packet 1 to the second terminal device through PTP mode, and the second terminal device receives data packet 1 through PTP mode.

[0373] For the description of S1003 , please refer to the description of FIG. 5 to FIG. 8 , which will not be repeated here.

[0374] Furthermore, the second terminal device can forward data packet 1 to the corresponding PDCP entity for processing based on the identifier of the multicast wireless bearer of data packet 1.

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

[0376] Through the above technical solution, this 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, and thus correctly deliver it to the PDCP entity, thereby ensuring the normal transmission of the multicast service.

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

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

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

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

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

[0382] The following describes the communication method 1300 of an embodiment of the present application based on the protocol architecture 1200.

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

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

[0385] For the description of S1301, please refer to the description of S1001 in Figure 10, which will not be repeated here.

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

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

[0388] 1) CellGroupConfig includes a Uu RLC channel configuration list, which includes three configurations: {Uu LCID1, Uu RLC channel ID1, PTM indication}, {Uu LCID2, Uu RLC channel ID2}, and {Uu LCID3, Uu RLC channel ID3, PTM indication}. Among them, {Uu LCID1, Uu RLC channel ID1, PTM indication} and {Uu LCID2, Uu RLC channel ID2} can simultaneously correspond to MRB1, and {Uu LCID2, Uu RLC channel ID2} and {Uu LCID3, Uu RLC channel ID3, PTM indication} can simultaneously correspond to MRB2.

[0389] 2) SL-L2RelayUE-Config includes the SRAP configuration corresponding to the second terminal device. The SRAP configuration includes a mapping relationship list. The mapping relationship list includes 4 sets of configurations, namely: {MRB ID1, Uu RLC channel ID1, PC5RLC channel ID1}, {MRB ID1, Uu RLC channel ID2, PC5RLC channel ID1}, {MRB ID2, Uu RLC channel ID2, PC5RLC channel ID2}, {MRB ID2, Uu RLC channel ID3, PC5RLC channel ID2}.

[0390] For a description of the above configuration, please refer to FIG14 .

[0391] FIG14 is a schematic diagram of a configuration relationship 1400 according to an embodiment of the present application. As shown in FIG14 , 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.

[0392] 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. Furthermore, the first terminal device can send data packet 1 through PC5 RLC channel 1.

[0393] Furthermore, the first terminal device establishes a protocol entity 5 (SRAP layer, RLC layer, MAC layer and PHY layer of the first terminal device on the PC5 interface in Figure 12) according to the configuration message 1, and the protocol entity 5 is used by the first terminal device to transmit data packet 1 on interface 2.

[0394] Exemplarily, configuration message 2 includes a PC5RLC channel configuration list, which includes two configurations: {PC5LCID1, PC5RLC channel ID1} and {PC5LCID2, PC5RLC channel ID2}. {PC5LCID1, PC5RLC channel ID1} may correspond to MRB1, and {PC5LCID2, PC5RLC channel ID2} may correspond to MRB2.

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

[0396] Furthermore, the second terminal device establishes a protocol entity 6 according to the configuration message 2 (the second terminal device in Figure 12 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 data packet 1 at interface 2.

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

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

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

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

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

[0402] When the access network device transmits data packet 1 using both PTM and PTP modes, 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 PC5SRAP entity. The first terminal device may perform data packet deduplication processing at the SRAP layer, or may not perform deduplication processing and send two data packets 1 to the second terminal device. For a description of S1303, refer to the description of Figures 5-8 and will not be repeated here.

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

[0404] Through the above technical solution, this 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, and thus correctly deliver it to the PDCP entity, thereby ensuring the normal transmission of the multicast service.

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

[0406] To implement the various functions of the method provided herein, the first terminal device, the second terminal device, and the access network device may each include hardware structures and / or software modules, and implement the aforementioned functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular one of the aforementioned functions is implemented in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.

[0407] Figure 15 is a schematic block diagram of a communication device 1500 according to an embodiment of the present application. Communication device 1500 includes a processor 1510 and a communication interface 1520, which may be interconnected via a bus 1530. Communication device 1500 may be a first terminal device, a second terminal device, or an access network device.

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

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

[0410] When the communication apparatus 1500 is a first terminal device, illustratively, the processor 1510 is configured 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.

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

[0412] When the communication apparatus 1500 is an access network device, illustratively, the processor 1510 is configured to perform the following operations: receive an indication message 1; send a paging message 1, etc.

[0413] When the communication device 1500 is a first terminal device / second terminal device / access network device, it will be responsible for executing the methods or steps related to the first terminal device / second terminal device / access network device in the aforementioned method embodiments.

[0414] The above description is merely exemplary. For details, please refer to the contents of the above method embodiments. The implementation of each operation in FIG15 may also correspond to the corresponding description of the method embodiments shown in FIG2 to FIG14.

[0415] Figure 16 is a schematic block diagram of a communication device 1600 according to an embodiment of the present application. Communication device 1600 may be a first terminal device, a second terminal device, or an access network device, or may be a chip or module within the first terminal device, the second terminal device, or the access network device, configured to implement the methods described in the above embodiments. Communication device 1600 includes a transceiver unit 1610 and a processing unit 1620. The following provides an exemplary description of transceiver unit 1610 and processing unit 1620.

[0416] The transceiver unit 1610 may include a transmitting unit and a receiving unit. The transmitting unit is configured to execute a transmitting operation of the communication device, and the receiving unit is configured to execute a receiving operation of the communication device. For ease of description, this embodiment of the application combines the transmitting unit and the receiving unit into a single transceiver unit. This is described here as a unified description and will not be repeated later.

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

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

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

[0420] When the communication device 1600 is a first terminal device / second terminal device / access network device, it will be responsible for executing the methods or steps related to the first terminal device / second terminal device / access network device in the aforementioned method embodiments.

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

[0422] The device embodiments shown in Figures 15 and 16 are used to implement the contents described in Figures 2 to 14. The specific execution steps and methods of the devices shown in Figures 15 and 16 can refer to the contents described in the above method embodiments.

[0423] Figure 17 is a schematic block diagram of a communication device 1700 according to 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, or an access network device. The communication device 1700 may be a chip in the first terminal device, the second terminal device, or the access network device.

[0424] Communication device 1700 includes an input / output interface 1720 and a processor 1710. Input / output interface 1720 may be an input / output circuit. Processor 1710 may be a signal processor, a chip, or other integrated circuit capable of implementing the method of the present application. Input / output interface 1720 is used for inputting or outputting signals or data.

[0425] For example, when communication device 1700 is a first terminal device, input / output interface 1720 is configured to receive indication message 1 and paging message 1. Processor 1710 is configured to send paging message 1 to a second terminal device based on indication message 1 and indication message 2. Processor 1710 is further configured to execute some or all of the steps of any method provided herein.

[0426] 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 this application.

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

[0428] Optionally, the communication device 1700 further includes a memory.

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

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

[0431] In one possible implementation, the processor 1710 may be a logic circuit that 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.

[0432] 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 embodiments. For specific content, please refer to the description of the above method embodiments, which will not be repeated here.

[0433] Figure 18 is a schematic block diagram of a communication device 1800 according to an embodiment of the present application. Communication device 1800 may be an access network device or a chip within the access network device. Communication device 1800 is configured to perform the operations performed by the access network device in the method embodiments shown in Figures 2-14.

[0434] When the communication device 1800 is an access network device, for example, a base station. Figure 18 shows a simplified schematic diagram of the base station structure. 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 usually be called 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 usually be called a transceiver module, a transceiver, a transceiver circuit, or a transceiver, etc. The transceiver module of module 1830 can also be called a transceiver or a transceiver, etc., which includes an antenna 1833 and a radio frequency circuit (not shown in Figure 18), wherein the radio frequency circuit is mainly used for radio frequency processing. Alternatively, the device for implementing the receiving function in module 1830 may be considered a receiver, and the device for implementing the transmitting function may be considered a transmitter, that is, module 1830 includes a receiver 1832 and a transmitter 1831. The receiver may also be referred to as a receiving module, a receiver, or a receiving circuit, and the transmitter may be referred to as a transmitting module, a transmitter, or a transmitting circuit.

[0435] Modules 1810 and 1820 may include one or more boards, each of which may include one or more processors and one or more memories. The processor is used to read and execute programs in the memory to implement baseband processing functions and control the base station. If multiple boards are present, the boards may be interconnected to enhance processing capabilities. As an optional implementation, multiple boards may share one or more processors, multiple boards may share one or more memories, or multiple boards may simultaneously share one or more processors.

[0436] For example, in one implementation, the transceiver module of module 1830 is used to execute the transceiver-related processes performed by the access network device in the embodiments shown in Figures 2 to 14. The processor of module 1810 is used to execute the processing-related processes performed by the access network device in the embodiments shown in Figures 2 to 14.

[0437] In another implementation, the processor of module 1810 is used to execute processes related to the processing performed by the communication device in the embodiments shown in Figures 2 to 14.

[0438] In another implementation, the transceiver module of module 1830 is used to execute the transceiver-related processes performed by the communication device in the embodiments shown in Figures 2 to 14.

[0439] It should be understood that FIG18 is merely an example and not a limitation, and the access network device including the processor, memory, and transceiver mentioned above may not rely on the structures shown in FIG15 to FIG17 .

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

[0441] Figure 19 is a schematic block diagram of a communication device 1900 according to an embodiment of the present application. Communication device 1900 may be a first terminal device / second terminal device, or a processor or chip of the first terminal device / second terminal device. Communication device 1900 may be used to perform the operations performed by the first terminal device / second terminal device or the communication device in the above-described method embodiments.

[0442] When communication device 1900 is a first terminal device or a second terminal device, Figure 19 shows a simplified schematic diagram of the terminal device structure. As shown in Figure 19, the terminal device includes a processor, a memory, and a transceiver. The memory can store computer program code, and the transceiver includes a transmitter 1931, a receiver 1932, a radio frequency circuit (not shown in Figure 19), an antenna 1933, and input / output devices (not shown in Figure 19).

[0443] The processor is primarily used to process communication protocols and communication data, control terminal devices, execute software programs, and process software program data. Memory is primarily used to store software programs and data. Radio frequency circuits are primarily used to convert baseband signals into radio frequency signals and process radio frequency signals. Antennas are primarily used to transmit and receive radio frequency signals in the form of electromagnetic waves. Input / output devices. For example, touch screens, displays, and keyboards are primarily used to receive user input and output data to the user. It should be noted that some types of terminal devices may not have input / output devices.

[0444] When data needs to be sent, the processor performs baseband processing on the data to be sent, and then 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, Figure 19 only shows one memory, processor, and transceiver. 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. This is not limited in the embodiments of the present application.

[0445] In the embodiment of the present application, the antenna and 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.

[0446] As shown in Figure 19, 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.

[0447] Alternatively, the device implementing the receiving function in transceiver 1930 may be considered a receiving module, and the device implementing the transmitting function in transceiver 1930 may be considered a transmitting module. That is, transceiver 1930 includes a receiver and a transmitter. A transceiver may also be sometimes referred to as a transceiver, a transceiver module, or a transceiver circuit. A receiver may also be sometimes referred to as a receiver, a receiving module, or a receiving circuit. A transmitter may also be sometimes referred to as a transmitter, a transmitting module, or a transmitting circuit.

[0448] For example, in one implementation, the processor 1910 is used to execute the processing actions of the first terminal device / second terminal device in the embodiments shown in Figures 2-14, and the transceiver 1930 is used to execute the transceiver actions of the first terminal device / second terminal device in Figures 2-14.

[0449] For example, in one implementation, the processor 1910 is used to execute the processing actions of the first terminal device / second terminal device in the embodiments shown in Figures 2-14, and the transceiver 1930 is used to execute the transceiver actions of the first terminal device / second terminal device in Figures 2-14.

[0450] It should be understood that FIG19 is merely an example and not a limitation, and the above-mentioned terminal device including the transceiver module and the processing module may not rely on the structures shown in FIG15 to FIG17.

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

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

[0453] The present application also provides another chip, comprising: 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 configured to execute code in a memory. When the code is executed, the processor is configured to execute the methods in the above examples. Optionally, the chip also includes a memory, which is configured to store computer programs or code.

[0454] The present application also provides a processor for coupling with a memory, and for executing the methods and functions involving a network device or a terminal device in any of the above embodiments.

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

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

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

[0458] Those skilled 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 beyond the scope of this application.

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

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

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

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

[0463] 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, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

[0464] The above is only a specific implementation of the embodiment of the present application, but the scope of protection of the embodiment of the present application is not limited to this. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the embodiment of the present application, and they should be included in the scope of protection of the embodiment of the present application. Therefore, the scope of protection of the embodiment of the present application should be based on the scope of protection 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