Communication method and device

Abstract

Embodiments of the present invention disclose a communication method and apparatus, including: establishing a first radio bearer for a first terminal device, the first radio bearer being used to transmit a first service; allocating a first RNTI and a second RNTI to the first terminal device, the first RNTI being used to schedule the service to the first terminal device, and the second RNTI being used to schedule the first service to a group of terminal devices including the first terminal device; and using the first RNTI and the second RNTI to schedule data packets of the first service to the first terminal device over the first radio bearer. Implementing embodiments of the present invention can improve communication efficiency.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of communication technology, and in particular to a communication method and device. Background Art

[0002] Multicast technology is a point-to-multipoint communication technology. Currently, when transmitting a multicast service, the same group radio network temporary identity (G-RNTI) can be used for transmission for terminal devices in the same cell. However, if a terminal device experiences poor signal reception, it will need to establish a unicast bearer to receive the service. However, the transition between multicast and unicast can cause interruptions, preventing the terminal device from receiving information and reducing communication efficiency. Summary of the Invention

[0003] The embodiment of the present invention discloses a communication method and device for improving communication efficiency.

[0004] The first aspect discloses a communication method, which establishes a first radio bearer for transmitting a first service for a first terminal device, allocates a first radio network temporary identity (RNTI) and a second RNTI to the first terminal device, and uses the first RNTI and the second RNTI to schedule data packets of the first service to the first terminal device on the first radio bearer. The first RNTI is used to schedule the service to the first terminal device, and the second RNTI is used to schedule the first service to a group of terminal devices including the first terminal device. Since the terminal device is simultaneously allocated an RNTI for scheduling unicast services and an RNTI for scheduling multicast services for scheduling data from the same radio bearer, the terminal device will not cause a change in the radio bearer when switching between multicast and unicast, and therefore, no interruption will occur, thereby improving communication efficiency.

[0005] As a possible implementation, a service establishment request message is received from a core network device, and the service establishment request message carries public information indicating that the first service is a multicast service.

[0006] As a possible implementation manner, the public information may be service information of a multicast service or address information.

[0007] As a possible implementation method, the first wireless bearer can be associated with the first public data channel. The first public data channel is used to transmit the data of the first service with the core network device, so that when multiple terminal devices receive the first service, the core network device can transmit the data of the first service through the first public data channel without establishing dedicated data channels for different terminal devices, thereby avoiding the repeated sending of the same data on multiple dedicated data channels.

[0008] As a possible implementation method, the second RNTI can be used to schedule data packets of the first service to the first terminal device on the first radio bearer, feedback information indicating failure to transmit the data packets of the first service is received from the first terminal device, and the first RNTI can be used to retransmit the data packets of the first service to the first terminal device on the first radio bearer. The second RNTI can be used to transmit new data, and the first RNTI can be used to retransmit data that failed to be transmitted. It can be seen that the retransmission of data that failed to be transmitted does not affect the transmission of new data on the second RNTI, thereby improving communication efficiency.

[0009] As a possible implementation, an association relationship between a first process and a second process can be sent to the first terminal device, where the first process is a process for initially transmitting data packets for the first service, and the second process is a process for retransmitting data packets for the first service. Based on the association relationship, newly transmitted or retransmitted data using different RNTIs can be associated so that the received data can be correctly processed, thereby improving data processing efficiency.

[0010] As a possible implementation method, indication information may be sent to the first terminal device, where the indication information may indicate that the second RNTI is used to schedule the first service, so that the first terminal device can quickly determine which service the second RNTI is used to transmit.

[0011] As a possible implementation method, the data packet of the first service may include a logical channel identifier, which is used to indicate that the data packet transmitted by the second RNTI is a data packet of the first service. It can be seen that no additional transmission information is required, and the service corresponding to the data packet can be determined only through the data packet, thereby saving resources.

[0012] As a possible implementation method, first configuration information can be sent to the first terminal device, and the first configuration information is used to instruct the first terminal device to detect the second RNTI according to the first configuration information, so that the terminal device can quickly detect the second RNTI according to the configuration information, thereby improving communication efficiency.

[0013] As a possible implementation manner, the first configuration information may include one or more of bandwidth part (BWP) information corresponding to the second RNTI, control resource set (CORESET) information corresponding to the second RNTI, and search space information corresponding to the second RNTI.

[0014] As a possible implementation method, indication information for indicating the number of receiving terminal devices of the first service and / or configuration information of the RNTI used by the first service can be sent to the resource management module, second configuration information including configuration information of the second RNTI corresponding to the first service from the resource management module is received, and the second configuration information is sent to the first terminal device. It can be seen that the resource management module can be used to enable the terminal devices transmitting the first service in the terminal devices corresponding to multiple cells or multiple access network devices to use the same RNTI or the same second configuration information, so that multicast transmission within an area uses the same resources, thereby enhancing the quality of the received signal and reducing service interruption caused by mobility.

[0015] As a possible implementation, an association relationship between a first terminal device and data of a first service may be received from a core network device. The first terminal device is any terminal device in the group of terminal devices. The association relationship may include at least one of the following: an association relationship between an identifier of a quality of service (QoS) flow of the first terminal device and an identifier of a public QoS flow, the public QoS flow being used to transmit data of the first service; an association relationship between an identifier of the QoS flow of the first terminal device and an identifier of the QoS flow of the second terminal device, the QoS flow of the second terminal device being used to transmit data of the first service, the second terminal device being a terminal device other than the first terminal device in the group of terminal devices; an association relationship between an identifier of the QoS flow of the first terminal device and index information of the data of the first service. It can be seen that the association relationship can be used to determine which terminal devices receive data of the first service so that the same second RNTI can be allocated to these terminal devices.

[0016] As one possible implementation, a session establishment request message is received from a core network device for establishing a QoS flow for a first terminal device. The session establishment request message is used to indicate that the QoS flow of the first terminal device is used to carry data for a multicast service. This indicates that the service carried by the QoS flow of the first terminal device can be determined as a multicast service through the session establishment request message, thereby improving the efficiency of determining the service type.

[0017] The second aspect discloses a communication device that can establish a first wireless bearer for transmitting a first service with an access network device, receive a first RNTI and a second RNTI from the access network device, and use the first RNTI and the second RNTI to receive data packets of the first service scheduled by the access network device on the first wireless bearer. The first RNTI is used to receive services scheduled from the access network device to the terminal device, and the second RNTI is used to receive the first service scheduled from the access network device to a group of terminal devices including the terminal device. Since the terminal device can use the RNTI for scheduling unicast services and the RNTI for scheduling multicast services at the same time to receive services from the same wireless bearer, the terminal device will not cause a change in the wireless bearer when switching between multicast and unicast, and therefore, no interruption will occur, thereby improving communication efficiency.

[0018] As a possible implementation, a data packet of the first service scheduled by the access network device can be received on the first radio bearer using the second RNTI, feedback information indicating a transmission failure of the data packet of the first service can be sent to the access network device, and data packets of the first service retransmitted by the access network device can be received on the first radio bearer using the first RNTI. The second RNTI can be used to transmit new data, and the first RNTI can be used to retransmit data that failed to be transmitted. This shows that retransmission of failed data does not affect the transmission of new data on the second RNTI, thereby improving communication efficiency.

[0019] As a possible implementation, an association relationship between a first process and a second process from an access network device may be received. Based on the association relationship, a data packet of a first service retransmitted from the access network device may be received on a first radio bearer using a first RNTI. The first process is a process for initially transmitting data packets for the first service, and the second process is a process for retransmitting data packets for the first service. Data newly transmitted or retransmitted using different RNTIs may be associated based on the association relationship to enable correct processing of the received data, thereby improving data processing efficiency.

[0020] As a possible implementation method, a first indication information can be received from an access network device, and a second RNTI can be determined based on the first indication information to be used for scheduling the first service, so that the first terminal device can quickly determine which service the second RNTI is used to transmit.

[0021] As a possible implementation method, the data packet transmitted by the second RNTI can be determined as the data packet of the first service based on the logical channel identifier included in the data packet of the first service. It can be seen that no additional transmission information is required, and the service corresponding to the data packet can be determined only through the data packet, thereby saving resources.

[0022] As a possible implementation method, configuration information from the access network device can be received, and data packets of the first service from the access network device can be detected from the second RNTI on the first wireless bearer according to the configuration information, so that the terminal device can quickly detect the second RNTI according to the configuration information, thereby improving communication efficiency.

[0023] As a possible implementation manner, the first configuration information may include one or more of BWP information corresponding to the second RNTI, CORESET information corresponding to the second RNTI, and search space information corresponding to the second RNTI.

[0024] As a possible implementation method, a second indication information can be received from an access network device, and the first wireless bearer can be determined as the wireless bearer used to transmit the first service based on the second indication information, so that the terminal device can quickly determine which service is transmitted by the first wireless bearer based on the second indication information, thereby improving communication efficiency.

[0025] As a possible implementation method, the first RNTI can be used to receive the first data packet of the first service from the access network device, and the second RNTI can be used to receive the second data packet of the first service from the access network device, and then the first data packet and the second data packet can be merged into the first wireless bearer. It can be seen that the first RNTI and the second RNTI can jointly transmit different data packets of the same service and then merge them, which can improve data transmission efficiency.

[0026] As a possible implementation method, when the first data packet and the second data packet are data packets of the media access control address (MAC) layer, the radio link control (RLC) protocol data unit (PDU) included in the first data packet and the second data packet can be merged into the first radio bearer at the RLC layer. When the first data packet and the second data packet are data packets of the RLC layer, the packet data convergence protocol (PDCP) PDU included in the first data packet and the second data packet can be merged into the first radio bearer at the PDCP layer.

[0027] As a possible implementation manner, the RLC PDU included in the first data packet and the RLC PDU included in the second data packet may be sorted and / or deduplicated.

[0028] As a possible implementation manner, the PDCP PDU included in the first data packet and the PDCP PDU included in the second data packet may be sorted and / or deduplicated.

[0029] The third aspect discloses a communication device, which includes a module for executing the communication method disclosed in the first aspect or any possible implementation of the first aspect, or includes a module for executing the communication method disclosed in the second aspect or any possible implementation of the second aspect.

[0030] A fourth aspect discloses a communication device, which may be an access network device or a chip within the access network device. The communication device includes a processor, a memory, an input interface, and an output interface. The input interface is configured to receive information from a communication device other than the communication device, and the output interface is configured to output information to the communication device other than the communication device. When the processor executes a computer program stored in the memory, the processor performs the communication method disclosed in the first aspect or any possible implementation of the first aspect.

[0031] A fifth aspect discloses a communication device, which may be a terminal device or a chip within a terminal device. The communication device includes a processor, a memory, an input interface, and an output interface. The input interface is used to receive information from another communication device outside the communication device, and the output interface is used to output information to another communication device outside the communication device. When the processor executes a computer program stored in the memory, the processor performs the communication method disclosed in the second aspect or any possible implementation of the second aspect.

[0032] The sixth aspect discloses a computer-readable storage medium having a computer program stored thereon. When the computer program is run, the communication method disclosed in the first aspect or any possible implementation of the first aspect is implemented, or the communication method disclosed in the second aspect or any possible implementation of the second aspect is implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 This is a schematic diagram of a network architecture disclosed in an embodiment of the present invention;

[0034] Figure 2 is a schematic diagram of implementing multicast transmission through SC-PTM disclosed in an embodiment of the present invention;

[0035] Figure 3 This is a schematic diagram of an SC-PTM channel configuration disclosed in an embodiment of the present invention;

[0036] Figure 4 This is a flow chart of a communication method disclosed in an embodiment of the present invention;

[0037] Figure 5 This is a schematic diagram of data merging disclosed in an embodiment of the present invention;

[0038] Figure 6 This is a schematic diagram of merging data into the RLC layer for processing disclosed in an embodiment of the present invention;

[0039] Figure 7 This is a schematic diagram of allocating a C-RNTI and a G-RNTI to a terminal device disclosed in an embodiment of the present invention;

[0040] Figure 8 This is another schematic diagram of allocating a C-RNTI and a G-RNTI to a terminal device disclosed in an embodiment of the present invention;

[0041] Figure 9 This is a flow chart of another communication method disclosed in an embodiment of the present invention;

[0042] Figure 10 This is a schematic diagram of a method of scheduling data using G-RNTI disclosed in an embodiment of the present invention;

[0043] Figure 11 This is a flow chart of another communication method disclosed in an embodiment of the present invention;

[0044] Figure 12 It is a structural diagram of a communication device disclosed in an embodiment of the present invention;

[0045] Figure 13 is a schematic structural diagram of another communication device disclosed in an embodiment of the present invention;

[0046] Figure 14 is a structural diagram of another communication device disclosed in an embodiment of the present invention;

[0047] Figure 15 is a structural diagram of another communication device disclosed in an embodiment of the present invention;

[0048] Figure 16 This is a flow chart of another communication method disclosed in an embodiment of the present invention;

[0049] Figure 17 This is a flow chart of another communication method disclosed in an embodiment of the present invention. DETAILED DESCRIPTION

[0050] The embodiments of the present invention disclose a communication method and apparatus for improving communication efficiency, which are described in detail below.

[0051] In order to better understand the communication method and device disclosed in the embodiment of the present invention, the network architecture used in the embodiment of the present invention is described below. Figure 1 , Figure 1 This is a schematic diagram of a network architecture disclosed in an embodiment of the present invention. Figure 1As shown, the network architecture may include a terminal device 101, an access network device 102, and a core network device 103. The terminal device 101 and the access network device 102, as well as the access network device 102 and the core network device 103, may be connected via a network. The core network device 103 is configured to send information to the access network device 102 and receive information from the access network device 102. The access network device 102 is configured to send information to the terminal device 101 and the core network device 103 and receive information from the terminal device 101 and the core network device 103. The terminal device 101 is configured to send information to the access network device 102 and receive information from the access network device 102.

[0052] The terminal device 101 may be user equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, or a user device. The access terminal may be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal in a future 5G network, or a terminal in a future evolved public land mobile network (PLMN), etc.

[0053] The access network device 102 can be a device used to communicate with the terminal device 101. It can be a base transceiver station (BTS) in the global system for mobile communication (GSM) or code division multiple access (CDMA), a base station (nodeB, NB) in a wideband code division multiple access (WCDMA) system, an evolutionary base station (eNB or eNodeB) in a long term evolution (LTE) system, a terminal that serves as an access network device in device to device (D2D) communication, a relay station, an access point, a vehicle-mounted device, a transmitting point, a wearable device, a network side device in a future 5G network, or an access network device in a future evolved PLMN, or any device that performs network functions.

[0054] The core network device 103 may correspond to different devices in different systems. For example, in 3G, it may correspond to a serving GPRS support node (SGSN) and / or a gateway GPRS support node (GGSN) of the general packet radio service (GPRS); in 4G, it may correspond to a mobility management entity (MME) and / or a serving gateway (S-GW); and in 5G, it may correspond to an access and mobility management function (AMF), a session management function (SMF), or a user plane function (UPF).

[0055] In order to better understand the communication method and apparatus disclosed in the embodiment of the present invention, the application scenario of the embodiment of the present invention is described below. Single cell point to multipoint (SC-PTM) is a technology for implementing multicast transmission. Figure 2 , Figure 2FIG. 1 is a schematic diagram of a multicast transmission method implemented by SC-PTM according to an embodiment of the present invention. Figure 2 As shown in Figure 1, in SC-PTM technology, a cell can schedule service data to multiple terminal devices simultaneously through the G-RNTI. Each G-RNTI can be associated with a multimedia broadcast multicast service (MBMS). Therefore, within a region, only cells containing terminal devices need to send data, while cells without terminal devices do not need to send data, thus saving air interface resources.

[0056] In SC-PTM technology, the physical downlink shared channel (PDSCH) can be used to transmit multicast services. Different from the PDSCH that carries unicast data, the PDSCH that carries multicast data can be called a multicast PDSCH. In SC-PTM technology, the access network equipment can send downlink control information (DCI) carried on the physical downlink control channel (PDCCH) to a group of terminal devices in a cell. After receiving the DCI, this group of terminal devices can receive the multicast PDSCH according to the scheduling information included in the DCI.

[0057] See also Figure 3 , Figure 3 This is a schematic diagram of an SC-PTM channel configuration disclosed in an embodiment of the present invention. Figure 3 As shown in Figure 1, SC-PTM is configured with a single-cell MBMS point-to-multipoint control channel (SC-MCCH) and a single-cell MBMS traffic control channel (SC-MTCH). The SC-MCCH is used to transmit control information, including SC-MTCH configuration information, such as the G-RNTI corresponding to the SC-MTCH and discontinuous reception (DRX) parameters. The SC-MCCH is used to transmit data in a periodic manner.

[0058] SC-MCCH configuration information can be transmitted via a broadcast channel. This information is used to configure SC-MCCH reception parameters, including the MCCH modification period, repetition period, and transmission duration. The SC-MCCH is transmitted using the PDCSH, and its corresponding PDCCH is scrambled using the single cell RNTI (SC-RNTI). The SC-RNTI value is fixed by the protocol and does not need to be configured during broadcasting.

[0059] The configuration information of SC-MTCH can be transmitted via SC-MCCH. The configuration information of SC-MTCH may include the configuration information of multicast services. The configuration information of each service may include the temporary multicast group identifier (TMGI) of the service, the corresponding G-RNTI, DRX parameters, and the neighboring cell information for sending the configuration information of this service. SC-MTCH is also carried on PDSCH, and its corresponding PDCCH is scrambled with G-RNTI.

[0060] For multicast service transmission, such as SC-PTM, multicast services are sent one-to-many, and access network equipment sends them blindly, regardless of the reception quality of the specific terminal device. If the reception quality of a terminal device is poor, a unicast bearer needs to be established to transmit this service. As a result, service continuity is not guaranteed well, thereby reducing communication efficiency.

[0061] based on Figure 1 The network architecture shown is shown in Figure 4 , Figure 4 This is a flow chart of a communication method disclosed in an embodiment of the present invention. Figure 4 As shown, the communication method may include the following steps.

[0062] 401. The access network device establishes a first radio bearer with the first terminal device.

[0063] In the case where there is a first service that needs to be transmitted to the first terminal device in the access network device, the access network device can establish a first radio bearer between the access network device and the first terminal device. After receiving the quality of service (QoS) parameters of the first service sent by the core network device, the access network device can establish a first radio bearer for the first service according to the requirements of the QoS parameters, and then send the parameters of the first radio bearer to the first terminal device. The first radio bearer is a bearer for transmitting the first service between the access network device and the first terminal device. Specifically, the parameters of the first radio bearer may include one or more of the following:

[0064] (1) radio bearer information, where the radio bearer information may include an identifier of a first radio bearer;

[0065] (2) PDCP layer configuration parameters, which may include PDCP sequence number length, encryption parameters, header compression parameters, etc.

[0066] (3) RLC layer configuration parameters. The RLC layer configuration parameters may include the logical channel number, RLC sequence number length, RLC mode, etc. The RLC mode may be the acknowledge mode (AM), the unacknowledge mode (UM), or the transparent mode (TM);

[0067] (4) MAC layer configuration parameters.

[0068] 402. The access network device sends a first RNTI to the first terminal device.

[0069] The access network device can allocate a first RNTI for the first terminal device and send the first RNTI to the first terminal device. The first RNTI can schedule services to the first terminal device, that is, the first RNTI can only schedule services for the first terminal device and cannot schedule services for other terminal devices. The scheduled services can be all services of the first terminal device, or the scheduling signaling of the first terminal, that is, the services and signaling transmitted between the access network device and the first terminal device can be scheduled through the first RNTI. The first RNTI can be a cell radio network temporary identifier (C-RNTI), or it can be another RNTI that can schedule unicast services. Among them, step 401 and step 402 can be executed serially or in parallel. The first RNTI may have been allocated before step 401, such as the first RNTI can be allocated during the process of the first terminal device accessing the current cell, or it can be allocated during the process of the first terminal device switching from other cells to the current cell. The first RNTI can also be allocated at the same time or after executing step 401.

[0070] 403. The access network device sends a second RNTI to the first terminal device.

[0071] The access network device may allocate a second RNTI to the first terminal device and send the second RNTI to the first terminal device. When the first service is a multicast service, the access network device may also allocate a second RNTI to the first terminal device while or after executing step 401. The second RNTI may schedule the first service to a group of terminal devices including the first terminal device. That is, the second RNTI may not only schedule the first service for the first terminal device, but also schedule the first service for other terminal devices, that is, the second RNTI is used to schedule multicast services. The second RNTI may be a G-RNTI or another RNTI that can schedule multicast services.

[0072] Among them, step 403 and step 402 can be executed simultaneously or separately. For example, in a handover scenario, when the source access network device requests to switch the terminal device to the target access network device, the target access network device allocates wireless bearer parameters to the terminal device, and simultaneously allocates a first RNTI and a second RNTI and sends them to the terminal device through the source access network device. When the terminal device initially accesses the access network device, the access network device first allocates the first RNTI to the terminal device, and then allocates the second RNTI when the first service establishment for the terminal device is received.

[0073] 404. The access network device uses the first RNTI and the second RNTI to schedule data packets of the first service to the first terminal device on the first radio bearer.

[0074] After the access network device establishes a first radio bearer for the first terminal device and sends the first RNTI and the second RNTI to the first terminal device, the access network device can use the first RNTI and the second RNTI to schedule data packets for the first service to the first terminal device, and the data packets for the first service are transmitted via the first radio bearer. Correspondingly, the first terminal device can use the first RNTI and the second RNTI to receive data packets for the first service scheduled by the access network device and process the data packets for the first service using configuration parameters related to the first radio bearer.

[0075] The access network device may use the first RNTI and the second RNTI to simultaneously schedule data packets of the first service to the first terminal device on the first radio bearer, that is, the access network device uses the first RNTI to schedule data packets of the first service to the first terminal device on the first radio bearer, and simultaneously uses the second RNTI to schedule data packets of the first service to the first terminal device on the first radio bearer. Accordingly, the first terminal device may use the first RNTI and the second RNTI to simultaneously receive data packets of the first service scheduled by the access network device on the first radio bearer, that is, the first terminal device uses the first RNTI to receive data packets of the first service scheduled by the access network device on the first radio bearer, and simultaneously the first terminal device may use the second RNTI to receive data packets of the first service scheduled by the access network device on the first radio bearer. The data packets of the first service scheduled by the first RNTI and the second RNTI may be the same, that is, all data packets of the first service, or they may be different, that is, the data packets scheduled by the first RNTI and the second RNTI may be partially the same or completely different. For example, the first RNTI schedules part of the data packets of the first service, and the second RNTI schedules the remaining data packets of the first service.

[0076] Alternatively, the access network device may first use the second RNTI to schedule the data packet of the first service to the first terminal device on the first radio bearer, and the first terminal device may use the second RNTI to receive the data packet of the first service scheduled by the access network device on the first radio bearer. The first terminal device then determines whether the data packet of the first service is successfully transmitted. If it is determined that the data packet transmission of the first service fails, the first terminal device sends feedback information indicating that the data packet transmission of the first service fails to the access network device. After the access network device receives the feedback information indicating that the data packet transmission of the first service fails from the first terminal device, the access network device retransmits the data packet of the first service to the first terminal device on the first radio bearer using the first RNTI. If the first terminal device determines that the data packet transmission of the first service is successful, the first terminal device sends feedback information indicating that the data packet transmission of the first service is successful to the access network device. The access network device receives the feedback information indicating that the data packet transmission of the first service is successful from the first terminal device, and ends the transmission of the data packet of the first service.

[0077] Specifically, for the same service, the choice of using G-RNTI scheduling or C-RNTI scheduling can be based on the following principles: C-RNTI is used when only one terminal device receives the same service, and G-RNTI is used when multiple terminal devices receive the same service; the RNTI that generates the largest throughput is used. For example, C-RNTI can schedule 1000 bits (bit) and 2000 bits of data for terminal device 1 and terminal device 2 respectively, while G-RNTI can only schedule 200 bits of data for terminal device 1 and terminal device 2 at a time. At this time, C-RNTI is used to schedule terminal device 1 and terminal device 2 respectively; if a terminal device fails to use G-RNTI scheduling continuously, C-RNTI scheduling can be used instead.

[0078] Specifically, the first terminal device may use the first RNTI to receive a first data packet of the first service from the access network device, and use the second RNTI to receive a second data packet of the first service from the access network device, and then merge the first data packet and the second data packet onto the first radio bearer. For example, the first data packet and the second data packet are data packets of the MAC layer, and the first terminal device may merge the RLC PDU included in the first data packet and the second data packet onto the first radio bearer at the RLC layer, that is, sort and / or deduplicate the RLC PDU included in the first data packet and the RLC PDU included in the second data packet. Alternatively, the first data packet and the second data packet are data packets of the RLC layer, and the first terminal device merges the PDCP PDU included in the first data packet and the second data packet onto the first radio bearer at the PDCP layer, that is, sort and / or deduplicate the PDCP PDU included in the first data packet and the PDCP PDU included in the second data packet. Deduplication means deleting duplicate data.

[0079] See also Figure 5 , Figure 5 This is a data merging diagram disclosed in an embodiment of the present invention. Figure 5 As shown, after the access network device transmits the data of each terminal device through the PDCP layer and the RLC layer, it can use the C-RNTI and G-RNTI to transmit the data to the terminal device through the MAC layer and the physical (PHY) layer in sequence. The terminal device uses the C-RNTI and G-RNTI to receive data through the PHY layer and the MAC layer in sequence, and then merges the data received using the C-RNTI and G-RNTI into a unicast bearer at the RLC layer and / or the PDCP layer for processing.

[0080] See also Figure 6 , Figure 6 FIG. 1 is a schematic diagram of merging data into the RLC layer for processing disclosed in an embodiment of the present invention. Figure 6As shown, terminal device 1 uses C-RNTI1 to receive multicast services with logical channel (LCH) identified as LCH1 and unicast services with LCH identified as LCH2, terminal device 1 and terminal device 2 use G-RNTI to receive multicast services with LCH identified as LCH1, and after terminal device 1 receives multicast services with LCH identified as LCH1 using C-RNTI1 and receives multicast services with LCH identified as LCH1 using G-RNTI, these data are merged and processed at the RLC layer.

[0081] See also Figure 7 , Figure 7 Schematic diagram of allocating C-RNTI and G-RNTI to terminal equipment disclosed in an embodiment of the present invention. Figure 7 As shown in the figure, the dotted line represents the control plane connection, and the solid line represents the user data transmission path. All three terminal devices are connected to the access network equipment. Each terminal device is configured with a C-RNTI and a data radio bearer (DRB) for unicast bearer. The DRB is also associated with a G-RNTI. G-RNTI and C-RNTI scheduling enable dynamic conversion between unicast and multicast. Figure 7 In this scenario, three terminal devices receive the same service. Each terminal device has a unicast bearer, which is a channel for receiving data based on the C-RNTI. The access network device also configures the same G-RNTI for all three terminal devices. When using C-RNTI scheduling, the access network device can schedule the same data to each of the three terminal devices, using unicast scheduling. When using G-RNTI scheduling, the access network device schedules a single copy of the data for all three terminal devices to receive.

[0082] See also Figure 8 , Figure 8 FIG. 1 is another schematic diagram of allocating C-RNTI and G-RNTI to a terminal device according to an embodiment of the present invention. Figure 8 As shown in the figure, in 5G, service data is transmitted between the new radio core (NGC) network equipment and the access network equipment. Two terminal devices correspond to different C-RNTIs, and two terminal devices correspond to the same G-RNTI. C-RNTI is used for the terminal device to receive scheduling information for a single terminal device. C-RNTI can be used to schedule signaling or data transmission for a single user. G-RNTI is used to schedule multiple terminal devices to receive the same service at the same time. For the same service, if C-RNTI scheduling is used, only the terminal device configured with the C-RNTI can receive it. If G-RNTI scheduling is used, multiple terminal devices can receive it.

[0083] based on Figure 1 The network architecture shown is shown in Figure 9 , Figure 9 FIG. 1 is a flow chart of another communication method disclosed in an embodiment of the present invention. Figure 9 As shown, the communication method may include the following steps.

[0084] 901. The core network device sends a service establishment request message to the access network device.

[0085] When there is a first service that needs to be transmitted, the core network device may send a service establishment request message to the access network device. The service establishment request message may be carried in an initial context establishment message, a protocol data unit (PDU) session establishment message, a context modification message, or other messages. The first service is a multicast service.

[0086] In one case, the service establishment request message may carry public information for indicating that the first service is a multicast service, that is, when the service establishment request message carries public information, the service to be established by the service establishment request message is a multicast service, and when the service establishment request message does not carry public information, the service to be established by the service establishment request message is a unicast service. The public information may be service information of a multicast service, and the service information may be TMGI, or other service information that can represent a multicast service. The public information may also be address information of a multicast service, and the access network device may join the multicast group corresponding to the address information to receive the first service. The correspondence between public information and services may be a correspondence between a service quality of service (QoS) flow and public information. The correspondence between QoS flows and public information may be as shown in Table 1:

[0087] Business Information Public Information QoS flow 1, QoS flow 2 Service 1 / multicast group address information 1 QoS Flow 3 Service 2 / multicast group address information 2 QoS Flow 4 none

[0088] Table 1: Correspondence between QoS flows and public information

[0089] Multiple QoS flows of a terminal device may correspond to multiple public information, as shown in Table 1. The public information corresponding to QoS flow 1 and QoS flow 2 is service 1 or multicast group address information 1, and the public information corresponding to QoS flow 3 is service 2 or multicast group address information 2. QoS flow 1, QoS flow 2, and QoS flow 3 all have corresponding public information. Therefore, the services corresponding to QoS flow 1, QoS flow 2, and QoS flow 3 are multicast services. Service 1 and service 2 are service information of multicast services, and multicast group address information 1 and multicast group address information 2 are address information of multicast services. Some QoS flows may have no public information. As shown in Table 1, QoS flow 4 has no public information, indicating that the content of QoS flow 4 will not be the same as that of other terminal devices, that is, the service corresponding to QoS flow 4 is a unicast service. Optionally, the service information in Table 1 may also be the identifier (ID) of the DRB, that is, the QoS flow in Table 1 may be replaced with the ID of the DRB.

[0090] In another case, the service establishment request message may directly indicate that the first service is a multicast service. That is, if the service establishment request message indicates that the service to be established by the service establishment request message is a multicast service, the service to be established by the service establishment request message is a multicast service; if the service establishment request message does not indicate that the service to be established by the service establishment request message is a multicast service, the service to be established by the service establishment request message is a unicast service.

[0091] Optionally, if there are multiple access network devices connected to the core network device, and multiple access network devices have established bearers for the same service, in order to ensure that the terminal device can continuously receive the service when moving between different access network devices, it is necessary to ensure that the core network device uses the same data packet number when sending the same service to multiple access network devices. The data packet number can be a GPRS tunneling protocol (GTP) number, or it can be another number with equivalent function. For example, access network device 1 and access network device 2 are both connected to the core network device, and UE1 and UE2 in access network device 1 receive service 1 at the same time, and UE3 and UE4 in access network device 2 receive service 1 at the same time. If UE1 moves from access network device 1 to access network device 2, UE1 will execute a switch to access network device 2, and UE1's service data will be forwarded to access network device 2. Access network device 2 may assign the same G-RNTI to UE1, UE3 and UE4 for unified scheduling. To determine which data UE1 has already transmitted, access network device 2 can determine the order of the data packets transmitted by UE3 and UE4 based on the packet number of the forwarded data packet of UE1. This can ensure that the transmission progress of UE1, UE3, and UE4 is aligned before transmission. Since the same packet number is used between access network devices, after UE1 switches to access network device 2, it can determine the difference between UE1's transmission progress and the transmission progress of UE3 and UE4 currently served by access network device 2 based on the packet number. For UEs served by the same access network device, if a common transport bearer is not used, the packet number can also be used to determine whether the content of the data packets transmitted to the UEs is the same. For example, if UE1 and UE2 each have dedicated data channels between the core network device and access network device 1, the packet numbers transmitted on the two dedicated data channels can be used to determine which data packets of the two UEs have the same content. The G-RNTI can then be used to schedule the same data packets to the two UEs simultaneously.

[0092] Optionally, before step 901, a connection for receiving the first service may be established between the terminal device, the core network device, and the application server. The connection for receiving the first service includes a PDU session between the terminal device and the core network device, and a data channel between the core network device and the application server. Before the terminal device and the application server interact, the application server needs to be informed that the terminal device needs to receive data for the first service. The application server may trigger a PDU session modification process, which mainly includes the following steps:

[0093] (1) The application server provides identification information related to the first service to the core network device, where the identification information is used by the core network device to identify the first service as downlink data corresponding to a multicast service;

[0094] Specifically, the application server provides identification information of the first service to a policy control function (PCF) network element in the core network. After receiving the identification information of the first service from the application server, the PCF network element in the core network can initiate a PDU session modification process and provide the identification information of the first service to an SMF network element in the core network. The SMF network element in the core network establishes transmission resources for the first service based on the identification information of the first service. The transmission resources can be service QoS flows.

[0095] (2) The core network device sends a service establishment request message to the access network device. The service establishment request message may include one or more of service information, common information of the multicast service, and information indicating that the first service is a multicast service.

[0096] 902. The access network device establishes a first wireless bearer with the first terminal device.

[0097] After the access network device receives the service establishment request message from the core network device, it indicates that there is a first service that needs to be transmitted between the access network device and the first terminal device, and a first radio bearer can be established between the access network device and the first terminal device. For a detailed description, please refer to step 401.

[0098] Since the first service is a multicast service, the first service may be scheduled to multiple terminal devices through G-RNTI. Therefore, the first radio bearer established by the access network device for the first terminal device does not start encryption. Since different terminal devices have different encryption keys, once encrypted, after the first service is scheduled to multiple terminal devices, only one terminal device among the multiple terminal devices can correctly decrypt the first service, and the other terminal devices cannot decrypt the first service, so that multicast transmission of the multicast service cannot be achieved. Alternatively, in order to improve security, when the access network device establishes the first radio bearer for the first terminal device, it can configure the first radio bearer to use a public key. The public key is a key used by multiple terminal devices receiving the first service. Multiple terminal devices use the public key for decryption when receiving the first service through the first radio bearer. In this way, when the access network device schedules the first terminal device, it can use the public key for scheduling regardless of whether it uses the first RNTI or the second RNTI. Regardless of which RNTI the terminal device uses for reception, it can use the same public key for decryption. The public key can be configured by the network device, for example, it can be configured to the terminal device by the access network device or the core network device through the encrypted signaling channel, or it can be derived by the terminal device based on the relevant information of the first service. The relevant information of the first service can be the service identifier of the first service, or it can be the wireless bearer identifier of the first service, or it can be the second RNTI, or it can be other information related to the first service. For example, the second RNTI corresponding to the first service is 62348, and the terminal device can mask the second RNTI and the first sequence to obtain the second sequence, and can use the second sequence as the secret key. The first sequence can be configured to the terminal device by the network device, or it can be a fixed sequence.

[0099] 903. The access network device associates the first radio bearer with the first public data channel.

[0100] This step is optional. The access network device uses the first wireless bearer and the first public data channel to save the overhead of transmitting the first service data between the core network and the access network device. When multiple terminal devices receive the first service, the public data channel is used to avoid repeated transmission of the first service data to multiple terminal devices. Without this step, the access network device still establishes a dedicated data channel with the core network device. In this way, when all terminal devices receive the first service, there is a different dedicated data channel between the access network device and the core network device for each terminal device. The data of the first service can be sent to the access network device on these dedicated channels.

[0101] After the access network device determines that the first service is a multicast service based on the service establishment request message, it associates the first radio bearer with the first public data channel. The first public data channel is a public data channel between the access network device and the core network device for transmitting data for the first service. After the access network device receives data for the first service from the core network device via the first public data channel, it transmits the received data for the first service to the first terminal device over the first radio bearer. The first public data channel can serve all terminal devices receiving the first service.

[0102] The first public data channel can be triggered and established by the access network device, or it can be triggered and established by the core network device. In the case where the first public data channel is triggered and established by the access network device, after the access network device receives the service establishment request message, it can return the downlink address information for receiving the first service to the core network device, and the address corresponding to the downlink address information is used to receive one or more QoS flows corresponding to the first service. In the case of using this method to establish the first public data channel, the public information is the service information of the multicast service. The access network device can also trigger the establishment of the first public data channel using the Internet Protocol (IP) multicast protocol. For example, the access network device sends a multicast group join request to the core network device in order to receive the data of the multicast group. After the multicast group joins successfully, it can be considered that the first public data channel is successfully established, and the access network device will receive the data corresponding to the first service from the core network device.

[0103] In the case where the first public data channel is triggered by the core network device, the core network device can initiate a public data channel establishment request carrying a service identifier to the access network device. After the access network device confirms the establishment, the public data channel is successfully established.

[0104] The first public data channel may have been established before, and here only the first radio bearer is associated with the first public data channel. For example, after the access network device associates the first radio bearer with the first public data channel, after the access network device receives a service establishment request message for other terminal devices, if the service establishment request message is a service establishment request message for establishing the first service, the first public data channel can be directly used without establishing it. For another example, the access network device has established a public data channel for public information 1 (or service 1 or multicast group address information 1), and directly associates the public channel with the service. The first public data channel may also not have been established before, and it is established and associated at this time. The establishment process can refer to the above description.

[0105] 904. The access network device sends a first RNTI to the first terminal device.

[0106] Among them, step 904 is the same as step 402. Please refer to step 402 for detailed description, and it will not be repeated here.

[0107] 905. The access network device sends a second RNTI to the first terminal device.

[0108] Among them, step 905 is the same as step 403. Please refer to step 403 for detailed description, which will not be repeated here.

[0109] 906. The access network device sends configuration information to the first terminal device.

[0110] The access network device may send configuration information to the first terminal device at the same time or after allocating the second RNTI to the first terminal device. The configuration information may include one or more of the bandwidth part (BWP) information corresponding to the second RNTI, the control resource set (CORESET) information corresponding to the second RNTI, and the search space information corresponding to the second RNTI. The COREST information indicates the time-frequency resources where the G-RNTI PDCCH is located.

[0111] BWP can be considered as part of the bandwidth of a cell. Each terminal device can be configured to work on several BWPs, but only one BWP is active at any one time. The main parameters of BPW may include bandwidth, frequency position, subcarrier space (SCS), cyclic prefix (CP) length, CORSET-related configuration information, and PDSCH-related configuration information. For a cell, there will be at least one initial BWP, and all public information such as broadcasts and paging are sent on the initial BWP. After the terminal device enters the connected state, the access network device can configure some dedicated BPWs for the terminal device. The first terminal device can determine the SCS, frequency domain position, CP length, etc. corresponding to the BPW based on the BPW.

[0112] The configuration information may also include the PDSCH scrambling sequence of the first service, so that the first terminal device can use the PDSCH scrambling sequence for descrambling when descrambling the PDSCH of the first service. The configuration information may also include the DRX parameters of the G-RNTI, so that the first terminal device can use the DRX parameters to perform G-RNTI detection. The configuration signal may also include a demodulation reference signal, so that the first terminal device can use the demodulation reference signal to demodulate the PDSCH scheduled by the G-RNTI. The configuration information may also include a rate matching reference signal, so that the first terminal device can exclude the position corresponding to the demodulation reference signal when receiving the PDSCH scheduled by the G-RNTI.

[0113] Optionally, the access network device may send indication information to the first terminal device, and the indication information may indicate that the second RNTI is used to schedule the first service. The indication information may be sent by the access network device to the first terminal device alone, or may be included in the above configuration information and sent together. The indication information may be the association information between G-RNTI and the service, such as the relationship between G-RNTI and LCH, the relationship between G-RNTI and DRB, the relationship between G-RNTI and the service identifier, etc. The indication information may also be the service information associated with DRB. For example, if the network sets DRB1 to be associated with a multicast service, the terminal device may consider that G-RNTI is used to receive data from the DRB1.

[0114] The configuration information may also include service information associated with the second RNTI, such as logical channel identifier, TMGI, DRB ID, etc., so that the first terminal device can determine which service the service scheduled using the second RNTI belongs to based on this information. In this way, the data sent using G-RNTI does not need to carry the logical channel identifier.

[0115] 907. The access network device uses the first RNTI and the second RNTI to schedule data packets of the first service to the first terminal device on the first radio bearer.

[0116] Among them, step 907 is similar to step 404. Please refer to step 404 for detailed description, and it will not be repeated here.

[0117] Specifically, after the first terminal device receives the configuration information from the access network device, it can detect the data packet of the first service from the access network device from the second RNTI on the first wireless bearer according to the configuration information.

[0118] When the access network device does not send indication information to the first terminal device to indicate that the second RNTI is used to schedule the first service, the data packet of the first service may include a logical channel identifier, and the logical channel identifier may indicate that the data packet transmitted by the second RNTI is a data packet of the first service.

[0119] In the case where the access network device uses G-RNTI to schedule services, terminal device 1 feeds back NACK, and the access network device can use C-RNTI for retransmission scheduling. In this way, G-RNTI can continue to schedule new data, ensuring that terminal device 1 and other terminal devices that correctly receive data can continue to receive new data. Terminal device 1 that does not receive data correctly can use C-RNTI for retransmission reception, which ensures the retransmission of data of terminal device 1 without affecting the reception of new data of other terminal devices. When using the hybrid automatic repeat request (HARQ) mechanism for data retransmission, it is necessary to ensure that the new transmission and retransmission use the same HARQ process. However, when using G-RNTI for new transmission, it is difficult to ensure that the same HARQ process is used when using C-RNTI for retransmission, because G-RNTI is shared by multiple terminal devices, and the process number scheduled by G-RNTI is consistent among multiple terminal devices. For example, if G-RNTI schedules process 8, all terminal devices using this G-RNTI will use process 8. If a data packet scheduled by G-RNTI is retransmitted for terminal device 1, process 8 cannot be used, and a new process needs to be replaced, such as process 6. However, after the process is replaced, the terminal device cannot determine whether the replaced process 6 is used to schedule the retransmission of process 8. Therefore, the access network device needs to notify the terminal device of the relationship between process 6 and process 8, so as to notify the terminal device that process 6 is currently retransmitting for process 8. Therefore, when the initial transmission of a data packet for the first service uses the second RNTI, while the retransmission of the data packet for the first service uses the first RNTI, the access network device can send the first terminal device an association between the first process and the second process, where the first process is the process used for initial transmission of the data packet for the first service, and the second process is the process used for retransmission of the data packet for the first service. The access network device can configure the association between the first and second processes through RRC. For example, an association between process 6 and process 8 can be configured, where process 6 is configured to retransmit data from process 8. When scheduling process 6, a scheduling command, such as a DCI, can indicate to the terminal device that the current retransmission of process 6 is for the associated process. In this case, the DCI can use one bit to indicate that the current retransmission is for the associated process. Alternatively, when scheduling the second process, the access network device can indicate in the scheduling command that the current process retransmission is associated with process 8. For example, when scheduling process 6, the scheduling command can indicate that the current process retransmission is associated with process 8. In this case, the scheduling command needs to add three bits to indicate this. The association relationship between the first process and the second process may be sent by the access network device to the first terminal device in the above configuration information, or may be sent to the first terminal device when the data packet of the first service needs to be retransmitted subsequently.

[0120] When the access network device uses G-RNTI scheduling, it is necessary to ensure that multiple data packets start from the same data position. Figure 10 , Figure 10 This is a schematic diagram of a method of scheduling data using G-RNTI disclosed in an embodiment of the present invention. Figure 10 As shown in the figure, three data packets, Data 1, Data 2, and Data 3, are currently being sent to the access network device. Initially, Terminal 1 and Terminal 2 each use their respective C-RNTIs for scheduling. Terminal 1 and Terminal 2 have already transmitted Data 1 and part of Data 2, but the remaining portion of Data 2 is different. Now, after G-RNTI is activated, G-RNTI scheduling begins with Data 3. The remaining portion of Data 2 requires Terminal 1 and Terminal 2 to continue scheduling using their respective C-RNTIs.

[0121] based on Figure 1 The network architecture shown is shown in Figure 11 , Figure 11 This is a flow chart of another communication method disclosed in an embodiment of the present invention. Figure 11 As shown, the communication method may include the following steps.

[0122] 1101. The access network device sends indication information for indicating the number of receiving terminal devices of the first service and / or first configuration information of the RNTI used by the first service to the resource management module.

[0123] The access network device can send indication information for indicating the number of receiving terminal devices of the first service to the resource management module in real time or periodically. The access network device can also determine in real time or periodically based on the number of receiving the first service in the cell covered by the access network device, to use the second RNTI to schedule the first service in the first cell, and then send the first configuration information to the resource management module. The first configuration information may include one or more of the BWP information corresponding to the second RNTI, the CORESET information corresponding to the second RNTI, the search space information corresponding to the second RNTI, the PDSCH scrambling sequence of the first service, the demodulation reference signal, the DRX parameters of the G-RNTI, and the rate matching reference signal. The resource management module can be an independent device or integrated in the access network device. The resource management module is mainly used to coordinate the G-RNTI and / or scheduling resources used between multiple cells or multiple access network devices.

[0124] 1102. The resource management module sends second configuration information corresponding to the first service to the access network device.

[0125] After receiving indication information from the access network device indicating the number of receiving terminal devices for the first service, the resource management module may determine, based on the indication information, that multiple cells may use the second RNTI to schedule the first service, and may send second configuration information corresponding to the first service to the access network device. The second configuration information includes configuration information of the second RNTI.

[0126] After receiving the first configuration information from multiple access network devices, the resource management module unifies the second RNTIs used by the multiple cells when the services of the multiple cells are the first services, and then sends the second configuration information corresponding to the first service to the access network device. The second configuration information includes configuration information of the transmission resources of the unified second RNTI. The transmission resources may include one or more of the BWP information corresponding to the second RNTI, the CORESET information corresponding to the second RNTI, the search space information corresponding to the second RNTI, the PDSCH scrambling sequence of the first service, the demodulation reference signal, the DRX parameters of the G-RNTI, and the rate matching reference signal. For example, the second RNTI and transmission resources of the second cell can be modified according to the second RNTI and transmission resources of the first cell so that the two cells use the same second RNTI and resources.

[0127] When the same second RNTI and transmission resources are used to transmit the same service between multiple cells, the air interface resources form the same signal, which can form a signal superposition effect when transmitted in multiple cells, thereby enhancing the reception effect of the first service.

[0128] 1103. The core network device sends a service establishment request message to the access network device.

[0129] Among them, step 1103 is the same as step 901. Please refer to step 901 for detailed description, and it will not be repeated here.

[0130] 1104. The access network device establishes a first wireless bearer with the first terminal device.

[0131] Among them, step 1104 is the same as step 902. Please refer to step 902 for detailed description, and it will not be repeated here.

[0132] 1105. The access network device associates the first radio bearer with the first public data channel.

[0133] Among them, step 1105 is the same as step 903. Please refer to step 903 for detailed description, which will not be repeated here.

[0134] 1106. The access network device sends a first RNTI to the first terminal device.

[0135] Among them, step 1106 is the same as step 402. Please refer to step 402 for detailed description, and it will not be repeated here.

[0136] 1107. The access network device sends a second RNTI to the first terminal device.

[0137] Step 1107 is the same as step 403. For detailed description, please refer to step 303, which will not be repeated here. In addition, the second RNTI may be allocated by the access network device according to the second configuration information.

[0138] 1108. The access network device sends configuration information including second configuration information to the first terminal device.

[0139] Among them, step 1108 is similar to step 906. Please refer to step 906 for detailed description, and it will not be repeated here.

[0140] 1109. The access network device uses the first RNTI and the second RNTI to schedule data packets of the first service to the first terminal device on the first radio bearer.

[0141] Among them, step 1109 is the same as step 907. Please refer to step 907 for detailed description, which will not be repeated here.

[0142] based on Figure 1 The network architecture shown is shown in Figure 16 , Figure 16 This is a flow chart of another communication method disclosed in an embodiment of the present invention. Figure 16 As shown, the communication method may include the following steps.

[0143] 1601. The core network device sends the association relationship between the first terminal device and the data of the first service to the access network device.

[0144] When data of a first service to be transmitted by a first terminal device exists, the core network device may send an association relationship between the first terminal device and the data of the first service to the access network device. The first service may be a multicast service, and the core network device may be an SMF network element. The first terminal device may be any terminal device in a group of terminal devices used to transmit the multicast service (i.e., the first service).

[0145] The core network device may receive a PDU session establishment / modification request from the first terminal device, and then establish a first QoS flow for the first terminal device to receive data of the first service. The core network device may then send an association relationship between the first terminal device and the data of the first service to the access network device.

[0146] The core network device may receive a message from the application server for establishing a QoS flow for a first terminal device to receive data of a first service, and then establish a first QoS flow for the first terminal device to receive data of the first service. The core network device may then send an association between the first terminal device and the data of the first service to the access network device.

[0147] The association relationship between the first terminal device and the data of the first service may include the association relationship between the identifier of the first QoS flow of the first terminal device and the identifier of the public QoS flow, where the public QoS flow is a QoS flow for transmitting the data of the first service, and the first QoS flow of the first terminal device is a QoS flow for the first terminal device to receive the data of the first service. The association relationship between the identifier of the first QoS flow of a group of terminal devices and the identifier of the public QoS flow can be referred to Table 2, where each row represents the association relationship between the identifier of the first QoS flow of a terminal device and the identifier of the public QoS flow. As shown in Table 2, UE1,

[0148] Terminal device identification Identifier of the first QoS flow of the terminal device Identification of public QoS flows UE1 QFI_1-1 QFI-C1 UE2 QFI_1-2 QFI-C1 UE3 QFI_1-3 QFI-C1 … … …

[0149] Table 2 Association between the identifier of the first QoS flow of a group of terminal devices and the identifier of the common QoS flow

[0150] UE2 and UE3 are identifiers of terminal devices, QFI_1-1 is the identifier of the first QoS flow of the terminal device corresponding to UE1, QFI_1-2 is the identifier of the first QoS flow of the terminal device corresponding to UE2, QFI_1-3 is the identifier of the first QoS flow of the terminal device corresponding to UE3, and QFI-C1 is the identifier of the public QoS flow used to transmit the data of the first service. The association relationship between the identifier of the first QoS flow of the terminal device and the identifier of the public QoS flow can also be referred to Table 3. As shown in Table 3, the identifier QFI-C1 of a public QoS flow corresponds to the identifiers QFI_1-1, QFI_1-2 and QFI_1-3 of the first QoS flows of three terminal devices. Optionally, the association relationship between the first terminal device and the data of the first service may also include the tunnel identification information corresponding to the first QoS flow of the first terminal device, and / or the tunnel identification information corresponding to the public QoS flow. Among them, the tunnel identification information can be the core network side tunnel information, and / or, the access network side tunnel information. Optionally, the association relationship between the first terminal device and the data of the first service may further include session identification information corresponding to the first QoS flow of the first terminal device, and / or session identification information corresponding to the public QoS flow.

[0151]

[0152] Table 3 Association between the identifier of the first QoS flow of a group of terminal devices and the identifier of the common QoS flow

[0153] The association relationship between the first terminal device and the data of the first service may include an association relationship between the identifier of the first QoS flow of the first terminal device and the identifier of the first QoS flow of the second terminal device. The first QoS flow of the first terminal device is a QoS flow used by the first terminal device to receive data of the first service, and the first QoS flow of the second terminal device is used to transmit data of the first service. The second terminal device is any terminal device in the group of terminal devices other than the first terminal device. The association relationship between the identifier of the first QoS flow of the first terminal device and the identifier of the first QoS flow of the second terminal device can be referred to in Tables 4 and 5. As shown in Table 4, UE1, UE2, and UE3 are terminal device identifiers, QFI_1-1 is the identifier of the first QoS flow of the terminal device corresponding to UE1, QFI_1-2 is the identifier of the first QoS flow of the terminal device corresponding to UE2, and QFI_1-3 is the identifier of the first QoS flow of the terminal device corresponding to UE3. It can be seen that the identifier QFI_1-2 of the first QoS flow of the terminal device corresponding to UE2 is associated with the identifier QFI_1-1 of the first QoS flow of the terminal device corresponding to UE1 and the identifier QFI_1-3 of the first QoS flow of the terminal device corresponding to UE3. As shown in Table 5, the identifier QFI_1-2 of the QoS flow of the terminal device corresponding to UE2 is associated with the identifier QFI_1-1 of the QoS flow of the terminal device corresponding to UE1 and the identifier QFI_1-3 of the QoS flow of the terminal device corresponding to UE3. Optionally, the association relationship between the first terminal device and the data of the first service may also include the tunnel identification information corresponding to the first QoS flow of the first terminal device, and / or the tunnel identification information corresponding to the first QoS flow of the second terminal device. The tunnel identification information may be the core network side tunnel information, and / or the access network side tunnel information. Optionally, the association relationship between the first terminal device and the data of the first service may also include the session identification information corresponding to the first QoS flow of the first terminal device, and / or the session identification information corresponding to the first QoS flow of the second terminal device.

[0154] Terminal device identification Identifier of the first QoS flow of the terminal device UE1 QFI_1-1QFI_1-2 UE2 QFI_1-2QFI_1-2 (optional) UE3 QFI_1-3QFI_1-2 … …

[0155] Table 4 Association between identifiers of the first QoS flow of the terminal device

[0156] Identifier of the first QoS flow of the second terminal device Identifier of the first QoS flow of other terminal devices QFI_1-2 QFI_1-1QFI_1-2(optional)QFI_1-3 … …

[0157] Table 5 Association between identifiers of the first QoS flow of the terminal device

[0158] The association relationship between the first terminal device and the data of the first service may include an association relationship between the identifier of the first QoS flow of the first terminal device and the index information of the data of the first service. The first QoS flow of the first terminal device may be used by the first terminal device to receive the data of the first service. The index information of the data of the first service is used to indicate that the transmitted data is the data of the first service, or is the same type of data. The index information of the data of the first service may be an index value, content identifier, reference value, or group identifier of the data of the first service. Index information of the same type or format should be used for different services. Taking the index value of the data of the first service as an example to illustrate the association relationship between the identifier of the first QoS flow of the first terminal device and the index information of the data of the first service, please refer to Table 6 and Table 7. As shown in Table 6, UE1, UE2, and UE3 are the identifiers of the terminal devices, QFI_1-1 is the identifier of the first QoS flow of the terminal device corresponding to UE1, Index1 is the index value of the data of the first service, QFI_1-2 is the identifier of the first QoS flow of the terminal device corresponding to UE2, and QFI_1-3 is the identifier of the QoS flow of the terminal device corresponding to UE3. As shown in Table 7, the index value Index1 of the data of the first service corresponds to the identifier QFI_1-1 of the first QoS flow of the terminal device corresponding to UE1, the identifier QFI_1-2 of the first QoS flow of the terminal device corresponding to UE2, and the identifier QFI_1-3 of the first QoS flow of the terminal device corresponding to UE3. Optionally, the association relationship between the first terminal device and the data of the first service may also include tunnel identification information corresponding to the first QoS flow of the first terminal device, wherein the tunnel identification information may be core network side tunnel information, and / or access network side tunnel information. Optionally, the association relationship between the first terminal device and the data of the first service may also include session identification information corresponding to the first terminal device and the first service.

[0159] Terminal device identification The identifier of the first QoS flow of the terminal device + the index value of the data of the first service UE1 QFI_1-1 Index1 UE2 QFI_1-2 Index1 UE3 QFI_1-3 Index1 … …

[0160] Table 6: Association between the identifier of the first QoS flow of the terminal device and the index information of the data of the first service

[0161] Index value of the first service data Identification of the QoS flow of the terminal device Index1 QFI_1-1 QFI_1-2 (optional) QFI_1-3 … …

[0162] Table 7 Association between the identifier of the QoS flow of the terminal device and the index information of the data of the first service

[0163] The access network device may obtain, from the core network device, an association relationship between the first terminal device and the data of the first service. Furthermore, based on the association relationship between the first terminal device and the data of the first service, a set of association relationships between the terminal device and the data of the first service may be generated, for use by the access network device in scheduling data packets for the first service. The access network device may also directly obtain an association relationship between the set of terminal devices and the data of the first service from the core network device. For details, see Tables 2-7.

[0164] In one implementation, the association relationship between the first terminal device and the data of the first service may include an association relationship between the identifier of the second QoS flow of the first terminal device and the identifier of the second QoS flow of at least one other terminal device in the group of terminal devices, the second QoS flow of at least one other terminal device in the group of terminal devices is used to receive the data of the first service, and the second QoS flow of the first terminal device can be used for the first terminal device to receive the data of the first service. The association relationship between the identifier of the second QoS flow of the first terminal device and the identifier of the second QoS flow of at least one other terminal device in the group of terminal devices can be referred to Tables 8-11. As shown in Table 8, UE1 is the identifier of the first terminal device, and QFI_2-1 is the identifier of the second QoS flow of the first terminal device. As shown in Table 9, UE2 is the identifier of the second terminal device, and there is an association relationship between the identifier QFI_2-2 of the second QoS flow of the second terminal device and the identifier QFI_2-1 of the second QoS flow of the first terminal device. As shown in Table 10, UE3 is the identifier of the third terminal device, and there is an association relationship between the identifier QFI_2-3 of the second QoS flow of the third terminal device, the identifier QFI_2-1 of the second QoS flow of the first terminal device, and the identifier QFI_2-2 of the second QoS flow of the second terminal device. As shown in Table 11, UE4 is the identifier of the fourth terminal device, and there is an association relationship between the identifier QFI_2-4 of the second QoS flow of the fourth terminal device, the identifier QFI_2-1 of the second QoS flow of the first terminal device, the identifier QFI_2-2 of the second QoS flow of the second terminal device, and the identifier QFI_2-3 of the second QoS flow of the third terminal device. The first terminal device, the second terminal device, the third terminal device, and the fourth terminal device are terminal devices in a group of terminal devices. Optionally, the association relationship between the identifier of the second QoS flow of the first terminal device and the identifier of the second QoS flow of at least one other terminal device in the group of terminal devices may also include the tunnel identification information corresponding to the second QoS flow of the first terminal, and / or the tunnel identification information corresponding to the second QoS flow of at least one other terminal device in the group of terminal devices. The tunnel identification information may be core network side tunnel information and / or access network side tunnel information. Optionally, the association relationship between the identifier of the second QoS flow of the first terminal device and the identifier of the second QoS flow of at least one other terminal device in the group of terminal devices may further include session identification information corresponding to the first terminal device and the first service.

[0165] Identification of the first terminal device Identifier of the second QoS flow of the first terminal device UE1 QFI_2-1

[0166] Table 8 Identification of the second QoS flow of the first terminal device

[0167] The identifier of the second terminal device Identification of the second QoS flow of the first terminal device and the second terminal device UE2 QFI_2-2 QFI_2-1

[0168] Table 9 Association between the identifiers of the second QoS flow of the first terminal device and the second terminal device

[0169]

[0170] Table 10: Association between the identifiers of the second QoS flows of the first terminal device, the second terminal device, and the third terminal device

[0171]

[0172] Table 11: Associations between identifiers of the second QoS flows of the first terminal device, the second terminal device, the third terminal device, and the fourth terminal device

[0173] The association relationship between the first terminal device and the data of the first service can be carried in the N2 session management information sent to the access network device by the SMF network element through the AMF network element, or it can be placed in the message or container sent by other SMFs to the access network device.

[0174] 1602. The access network device establishes a first wireless bearer with the first terminal device.

[0175] After the access network device receives the association relationship between the first terminal device and the data of the first service from the core network device, it indicates that data of the first service that needs to be transmitted exists between the access network device and the first terminal device, and a first radio bearer can be established with the first terminal device. For a specific description, please refer to step 902. The association relationship between the first terminal device and the data of the first service may be sent by the core network device via a PDU session resource setup request.

[0176] 1603. The access network device associates the first radio bearer with the QoS flow used to transmit data of the first service.

[0177] After the access network device establishes the first wireless bearer with the first terminal device, it can determine that the data of the first service received from the QoS flow used to transmit the data of the first service needs to be transmitted on the first wireless bearer based on the association relationship obtained from the core network, and the QoS flow used to transmit the data of the first service transmits the data of the first service. Among them, the QoS flow used to transmit the data of the first service can be the public QoS flow in step 1601 or the first QoS flow of the second terminal device. In the case that the association information contains index information corresponding to the data of the first service, the access network device can select one from the first QoS flows in the group of terminal devices for transmission. Among them, step 1603 is an optional step.

[0178] 1604. The access network device sends a first RNTI to the first terminal device.

[0179] For a detailed description, please refer to step 904, which will not be repeated here.

[0180] 1605. The access network device sends a second RNTI to the first terminal device.

[0181] The access network device sends the second RNTI to the first terminal device according to the association relationship. Please refer to step 905 for a detailed description, which will not be repeated here.

[0182] 1606. The access network device sends configuration information to the first terminal device.

[0183] For a detailed description, please refer to step 906 , which will not be repeated here.

[0184] 1607. The access network device uses the first RNTI and the second RNTI to schedule data packets of the first service to the first terminal device on the first radio bearer.

[0185] For a detailed description, please refer to step 907, which will not be repeated here.

[0186] based on Figure 1 The network architecture shown is shown in Figure 17 , Figure 17 This is a flow chart of another communication method disclosed in an embodiment of the present invention. Figure 17 As shown, the communication method may include the following steps.

[0187] 1701. A core network device sends a session establishment request message for establishing a first QoS flow of a first terminal to an access network device.

[0188] If there is data of a first service that needs to be transmitted, the core network device may send a session establishment request message to the access network device to establish a first QoS flow for the first terminal. The session establishment request message may be carried in an initial context establishment message, a PDU session establishment message, a context modification message, or other messages. The session establishment request message may indicate that the first QoS flow of the first terminal device carries data of a multicast service.

[0189] In one case, the session establishment request message may carry indication information for indicating that the first QoS flow of the first terminal device carries data for a multicast service. That is, when the session establishment request message carries indication information for indicating that the first QoS flow of the first terminal device carries data for a multicast service, the session establishment request message will establish the first QoS flow carrying data for the multicast service; and when the session establishment request message does not carry indication information for indicating that the first QoS flow of the first terminal device carries data for a multicast service, the session establishment request message will establish the first QoS flow carrying data for a unicast service.

[0190] In another case, the session establishment request message may directly indicate that the first QoS flow of the first terminal device carries data for a multicast service. That is, if the session establishment request message indicates that the first QoS flow of the first terminal device carries data for a multicast service, the session establishment request message will establish the first QoS flow that carries data for the multicast service; if the session establishment request message does not indicate that the first QoS flow carries data for a multicast service, the session establishment request message will establish the first QoS flow that carries data for a unicast service.

[0191] Optionally, before the core network device sends a session establishment request message for establishing a first QoS flow for the first terminal device to the access network device, it may receive a session establishment request from the first terminal device for establishing a first QoS flow for receiving data of the first service.

[0192] Optionally, the session establishment request message may also carry address information for the access network device to receive data for the first service, such as the IP address of the access network device, tunnel identification information, N3 tunnel identification information of a terminal device in the group of terminal devices, or a common N3 tunnel identification information of the access network device. This address information is used by the access network device to establish the first QoS flow for the first terminal device. For further details, refer to step 901.

[0193] 1702. The access network device establishes a first wireless bearer with the first terminal device.

[0194] After the access network device receives a session establishment request message from the core network device for establishing a first QoS flow for the first terminal device, it indicates that the data to be transmitted between the access network device and the first terminal device is multicast service data, and the multicast service data is first service data. Therefore, a first radio bearer can be established with the first terminal device. For a detailed description, see step 902.

[0195] Because the data being transmitted is a multicast service, the multicast service data may be dispatched to multiple terminal devices via the G-RNTI. Therefore, the access network device may not initiate encryption on the first radio bearer established for the first terminal device. Because different terminal devices use different encryption keys, once encrypted, after the multicast service data is dispatched to multiple terminal devices, only one of the multiple terminal devices can correctly decrypt the multicast data, while the other terminal devices cannot decrypt the multicast data, making it impossible to implement multicast transmission of the multicast service data.

[0196] 1703. The access network device associates the first radio bearer with a first QoS flow for transmitting data of the first service.

[0197] After establishing a first radio bearer with the first terminal device, the access network device may associate the first radio bearer with a first QoS flow used to transmit data for the first service. This can reduce data overhead for transmitting the first service between the core network device and the access network device. When multiple terminal devices receive data for the first service, using a single N3 QoS flow can prevent multiple terminal devices from repeatedly sending data for the first service to the same access network device. This N3 QoS flow can be a common QoS flow or the first QoS flow of a terminal device in the group. The first QoS flow used to transmit data for the first service can be the common QoS flow described in step 1601 or the first QoS flow of the second terminal device. If the association information includes index information corresponding to the data for the first service, the access network device can select one of the first QoS flows from the group of terminal devices for transmission. If this step is not performed, the access network device can still establish a dedicated data channel with the core network device. In this way, when a terminal device receives data for the first service, a different dedicated data channel exists between the access network device and the core network device, and for each terminal device. Data for the first service can be transmitted to the access network device via these dedicated channels. Step 1703 is optional.

[0198] 1704. The access network device sends a first RNTI to the first terminal device.

[0199] For a detailed description, please refer to step 904, which will not be repeated here.

[0200] 1705. The access network device sends a second RNTI to the first terminal device.

[0201] The access network device sends the second RNTI to the first terminal device according to the association relationship. Please refer to step 905 for a detailed description, which will not be repeated here.

[0202] 1706. The access network device sends configuration information to the first terminal device.

[0203] For a detailed description, please refer to step 906 , which will not be repeated here.

[0204] 1707. The access network device uses the first RNTI and the second RNTI to schedule data packets of the first service to the first terminal device on the first radio bearer.

[0205] For a detailed description, please refer to step 907, which will not be repeated here.

[0206] based on Figure 1 The network architecture shown is shown in Figure 12 , Figure 12 1 is a schematic diagram of the structure of a communication device disclosed in an embodiment of the present invention. The communication device may be an access network device or a chip in the access network device. Figure 12 As shown, the communication device may include:

[0207] An establishing unit 1201 is configured to establish a first radio bearer for a first terminal device, where the first radio bearer is used to transmit a first service;

[0208] An allocating unit 1202 is configured to allocate a first RNTI and a second RNTI to a first terminal device, where the first RNTI is used to schedule a service to the first terminal device, and the second RNTI is used to schedule the first service to a group of terminal devices including the first terminal device;

[0209] The sending unit 1203 is used to use the first RNTI and the second RNTI to schedule data packets of the first service to the first terminal device on the first radio bearer.

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

[0211] The receiving unit 1204 is configured to receive a service establishment request message from a core network device, where the service establishment request message carries public information indicating that the first service is a multicast service.

[0212] In one embodiment, the public information is service information or address information of a multicast service.

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

[0214] The associating unit 1205 is configured to associate the first radio bearer with a first public data channel, where the first public data channel is used to transmit data of the first service with the core network device.

[0215] In one embodiment, the sending unit 1203 is specifically configured to:

[0216] Scheduling a data packet of the first service to the first terminal device on the first radio bearer using the second RNTI;

[0217] receiving feedback information from the first terminal device indicating that data packet transmission of the first service has failed;

[0218] The data packet of the first service is retransmitted to the first terminal device on the first radio bearer using the first RNTI.

[0219] In one embodiment, the sending unit 1203 is further used to send the association relationship between the first process and the second process to the first terminal device, where the first process is the process for initially transmitting data packets of the first service, and the second process is the process for retransmitting data packets of the first service.

[0220] In one embodiment, the sending unit 1203 is further used to send indication information to the first terminal device, where the indication information is used to indicate that the second RNTI is used to schedule the first service.

[0221] In one embodiment, the data packet of the first service includes a logical channel identifier, and the logical channel identifier is used to indicate that the data packet transmitted by the second RNTI is the data packet of the first service.

[0222] In one embodiment, the sending unit 1203 is further used to send first configuration information to the first terminal device, where the first configuration information is used to instruct the first terminal device to detect the second RNTI according to the first configuration information.

[0223] In one embodiment, the first configuration information includes one or more of the following:

[0224] BWP information corresponding to the second RNTI;

[0225] CORESET information corresponding to the second RNTI; and

[0226] Search space information corresponding to the second RNTI.

[0227] In one embodiment, the sending unit 1203 is further configured to send, to the resource management module, indication information indicating the number of receiving terminal devices of the first service and / or configuration information of the RNTI used by the first service;

[0228] The receiving unit 1204 is further configured to receive second configuration information corresponding to the first service from the resource management module, where the second configuration information includes configuration information of the second RNTI;

[0229] The sending unit 1203 is further used to send second configuration information to the first terminal device.

[0230] A more detailed description of the establishing unit 1201, allocating unit 1202, sending unit 1203, receiving unit 1204 and associating unit 1205 can be directly obtained by referring to the relevant description of the access network device in the above method embodiment, which is not repeated here.

[0231] based on Figure 1 The network architecture shown is shown in Figure 13 , Figure 13 FIG. 1 is a schematic diagram of another communication device disclosed in an embodiment of the present invention. The communication device may be a terminal device or a chip in the terminal device. Figure 13 As shown, the communication device may include:

[0232] An establishing unit 1301 is configured to establish a first radio bearer with an access network device, where the first radio bearer is used to transmit a first service;

[0233] The receiving unit 1302 is configured to receive a first RNTI and a second RNTI from an access network device, where the first RNTI is used to receive a service scheduled from the access network device to a terminal device, and the second RNTI is used to receive a first service scheduled from the access network device to a group of terminal devices including the terminal device;

[0234] The receiving unit 1302 is further configured to receive, on the first radio bearer, a data packet of a first service scheduled by the access network device using the first RNTI and the second RNTI.

[0235] In one embodiment, the receiving unit 1302 uses the first RNTI and the second RNTI to receive, on the first radio bearer, a data packet of the first service scheduled by the access network device, including:

[0236] receiving, on the first radio bearer, a data packet of the first service scheduled by the access network device using the second RNTI;

[0237] Sending feedback information indicating a failure in transmission of a data packet of the first service to the access network device;

[0238] A data packet of a first service retransmitted from an access network device is received on a first radio bearer using the first RNTI.

[0239] In one embodiment, the receiving unit 1302 is further configured to receive an association relationship between a first process and a second process from an access network device, where the first process is a process for initially transmitting a data packet of the first service, and the second process is a process for retransmitting a data packet of the first service;

[0240] The receiving unit 1302 uses the first RNTI to receive, on the first radio bearer, a data packet of the first service retransmitted from the access network device, including:

[0241] The data packet of the first service retransmitted from the access network device is received on the first radio bearer using the first RNTI according to the association relationship.

[0242] In one embodiment, the communication device may further include a determining unit 1303, wherein:

[0243] In one case, the receiving unit 1302 is further configured to receive first indication information from the access network device, and the determining unit 1303 is configured to determine, based on the first indication information, the second RNTI for scheduling the first service;

[0244] In another case, the determining unit 1303 is configured to determine, according to a logical channel identifier included in a data packet of the first service, that the data packet transmitted by the second RNTI is a data packet of the first service.

[0245] In one embodiment, the receiving unit 1302 is further configured to receive configuration information from an access network device;

[0246] The receiving unit 1302 uses the second RNTI to receive, on the first radio bearer, a data packet of the first service scheduled by the access network device, including:

[0247] According to the configuration information, a data packet of the first service from the access network device is detected from the second RNTI on the first radio bearer.

[0248] In one embodiment, the configuration information includes one or more of the following:

[0249] BWP information corresponding to the second RNTI;

[0250] CORESET information corresponding to the second RNTI; and

[0251] Search space information corresponding to the second RNTI.

[0252] In one embodiment, the receiving unit 1302 is further configured to receive second indication information from the access network device;

[0253] The determining unit 1303 is further configured to determine, according to the second indication information, that the first radio bearer is a radio bearer for transmitting the first service.

[0254] In one embodiment, the receiving unit 1302 uses the first RNTI and the second RNTI to receive a data packet of the first service from the access network device on the first radio bearer, including:

[0255] receiving a first data packet of a first service from an access network device using a first RNTI;

[0256] receiving a second data packet of the first service from the access network device using the second RNTI;

[0257] The first data packet and the second data packet are combined into the first radio bearer.

[0258] In one embodiment, the receiving unit 1302 merging the first data packet and the second data packet into the first radio bearer includes:

[0259] In a case where the first data packet and the second data packet are data packets of the MAC layer, merging the RLC PDUs included in the first data packet and the second data packet onto the first radio bearer at the RLC layer; or

[0260] In a case where the first data packet and the second data packet are data packets of the RLC layer, the PDCP PDUs included in the first data packet and the second data packet are merged into the first radio bearer at the PDCP layer.

[0261] In one embodiment, the receiving unit 1302 merging the RLC PDUs included in the first data packet and the second data packet onto the first radio bearer at the RLC layer includes:

[0262] The RLC PDU included in the first data packet and the RLC PDU included in the second data packet are sorted and / or deduplicated.

[0263] In one embodiment, the receiving unit 1302 merging the RLC PDUs included in the first data packet and the second data packet onto the first radio bearer at the RLC layer includes:

[0264] The RLC PDU included in the first data packet and the RLC PDU included in the second data packet are sorted and / or deduplicated.

[0265] A more detailed description of the establishing unit 1301, the receiving unit 1302 and the determining unit 1303 can be directly obtained by referring to the relevant description of the terminal device in the above method embodiment, and will not be repeated here.

[0266] based on Figure 1 The network architecture shown is shown in Figure 14 , Figure 14 This is a structural diagram of another communication device disclosed in an embodiment of the present invention. Figure 14 As shown, the communication device may include a processor 1401, a memory 1402, an input interface 1403, an output interface 1404, and a bus 1405. The memory 1402 may be independent or connected to the processor 1401 via the bus 1405. The memory 1402 may also be integrated with the processor 1401. The bus 1405 is used to connect these components.

[0267] In one embodiment, the communication device may be an access network device or a chip within the access network device, wherein:

[0268] A set of computer programs is stored in the memory 1402. The processor 1401 is configured to call the computer programs stored in the memory 1402 to perform the following operations:

[0269] Establishing a first radio bearer for the first terminal device, where the first radio bearer is used to transmit a first service;

[0270] Allocate a first RNTI and a second RNTI to the first terminal device, where the first RNTI is used to schedule a service to the first terminal device, and the second RNTI is used to schedule the first service to a group of terminal devices including the first terminal device;

[0271] The output interface 1404 is configured to schedule data packets of the first service to the first terminal device on the first radio bearer using the first RNTI and the second RNTI.

[0272] In one embodiment, the input interface 1403 is used to receive a service establishment request message from a core network device, where the service establishment request message carries public information indicating that the first service is a multicast service.

[0273] In one embodiment, the public information is service information or address information of a multicast service.

[0274] In one embodiment, the processor 1401 is further configured to call a computer program stored in the memory 1402 to perform the following operations:

[0275] The first radio bearer is associated with a first public data channel, where the first public data channel is used to transmit data of the first service with the core network device.

[0276] In one embodiment, the output interface 1404 uses the first RNTI and the second RNTI to schedule a data packet of the first service to the first terminal device on the first radio bearer, including:

[0277] The output interface 1404 schedules a data packet of the first service to the first terminal device on the first radio bearer using the second RNTI;

[0278] The input interface 1403 receives feedback information from the first terminal device indicating that the data packet transmission of the first service has failed;

[0279] The output interface 1404 uses the first RNTI to retransmit the data packet of the first service to the first terminal device on the first radio bearer.

[0280] In one embodiment, the output interface 1404 is further used to send the association relationship between the first process and the second process to the first terminal device, where the first process is the process for initially transmitting data packets of the first service, and the second process is the process for retransmitting data packets of the first service.

[0281] In one embodiment, the output interface 1404 is further used to send indication information to the first terminal device, where the indication information is used to indicate that the second RNTI is used to schedule the first service.

[0282] In one embodiment, the data packet of the first service includes a logical channel identifier, and the logical channel identifier is used to indicate that the data packet transmitted by the second RNTI is the data packet of the first service.

[0283] In one embodiment, the output interface 1404 is further used to send first configuration information to the first terminal device, where the first configuration information is used to instruct the first terminal device to detect the second RNTI according to the first configuration information.

[0284] In one embodiment, the first configuration information includes one or more of the following:

[0285] BWP information corresponding to the second RNTI;

[0286] CORESET information corresponding to the second RNTI; and

[0287] Search space information corresponding to the second RNTI.

[0288] In one embodiment, the output interface 1404 is further configured to send, to the resource management module, indication information indicating the number of receiving terminal devices of the first service and / or configuration information of the RNTI used by the first service;

[0289] The input interface 1403 is further configured to receive second configuration information corresponding to the first service from the resource management module, where the second configuration information includes configuration information of the second RNTI;

[0290] The output interface 1404 is further configured to send the second configuration information to the first terminal device.

[0291] Among them, step 401, step 902-step 903 and step 1104-step 1105 can be executed by the processor 1401 and memory 1402 in the access network device; the steps of receiving the service establishment request message in step 901 and step 1103, and the step of receiving the second configuration information in step 1102 can be executed by the input interface 1403 in the access network device; steps 402-step 404, step 904-step 907 and step 1106-step 1109 can be executed by the output interface 1404 in the access network device.

[0292] Among them, the establishment unit 1201, the allocation unit 1202 and the association unit 1205 can be implemented by the processor 1401 and the memory 1402 in the access network device, the receiving unit 1204 can be implemented by the input interface 1403 in the access network device, and the sending unit 1203 can be implemented by the output interface 1404 in the access network device.

[0293] The above-mentioned access network device can also be used to execute various methods executed by the access network device in the aforementioned method embodiments, which will not be described in detail.

[0294] In another embodiment, the communication device may be a terminal device or a chip within the terminal device, wherein:

[0295] A set of computer programs is stored in the memory 1402. The processor 1401 is configured to call the computer programs stored in the memory 1402 to perform the following operations:

[0296] Establishing a first radio bearer with an access network device, where the first radio bearer is used to transmit a first service;

[0297] An input interface 1403 is configured to receive a first RNTI and a second RNTI from an access network device, wherein the first RNTI is used to receive a service scheduled from the access network device to the terminal device, and the second RNTI is used to receive a first service scheduled from the access network device to a group of terminal devices including the terminal device;

[0298] The input interface 1403 is further configured to receive, on the first radio bearer, a data packet of the first service scheduled by the access network device using the first RNTI and the second RNTI.

[0299] In one embodiment, the input interface 1403 uses the first RNTI and the second RNTI to receive, on the first radio bearer, a data packet of the first service scheduled by the access network device, including:

[0300] The input interface 1403 receives a data packet of the first service scheduled by the access network device on the first radio bearer using the second RNTI;

[0301] The output interface 1404 sends feedback information indicating a failure in transmission of a data packet of the first service to the access network device;

[0302] The input interface 1403 receives, on the first radio bearer, a data packet of the first service retransmitted from the access network device using the first RNTI.

[0303] In one embodiment, the input interface 1403 is further configured to receive an association relationship between a first process and a second process from an access network device, where the first process is a process for initially transmitting a data packet of the first service, and the second process is a process for retransmitting a data packet of the first service;

[0304] The input interface 1403 uses the first RNTI to receive, on the first radio bearer, a data packet of the first service retransmitted from the access network device, including:

[0305] The data packet of the first service retransmitted from the access network device is received on the first radio bearer using the first RNTI according to the association relationship.

[0306] In one embodiment, the input interface 1403 is further configured to receive first indication information from the access network device;

[0307] The processor 1401 is further configured to call the computer program stored in the memory 1402 to perform the following operations:

[0308] A second RNTI is determined according to the first indication information for scheduling the first service.

[0309] In one embodiment, the processor 1401 is further configured to call a computer program stored in the memory 1402 to perform the following operations:

[0310] Determine, according to the logical channel identifier included in the data packet of the first service, that the data packet transmitted by the second RNTI is the data packet of the first service.

[0311] In one embodiment, the input interface 1403 is further configured to receive configuration information from an access network device;

[0312] The input interface 1403 uses the second RNTI to receive a data packet of the first service scheduled by the access network device on the first radio bearer, including:

[0313] According to the configuration information, a data packet of the first service from the access network device is detected from the second RNTI on the first radio bearer.

[0314] In one embodiment, the configuration information includes one or more of the following:

[0315] BWP information corresponding to the second RNTI;

[0316] CORESET information corresponding to the second RNTI; and

[0317] Search space information corresponding to the second RNTI.

[0318] In one embodiment, the input interface 1403 is further configured to receive second indication information from the access network device;

[0319] The processor 1401 is further configured to call the computer program stored in the memory 1402 to perform the following operations:

[0320] The first radio bearer is determined as a radio bearer for transmitting the first service according to the second indication information.

[0321] In one embodiment, the input interface 1403 uses the first RNTI and the second RNTI to receive a data packet of the first service from the access network device on the first radio bearer, including:

[0322] The input interface 1403 receives a first data packet of a first service from an access network device using a first RNTI;

[0323] The input interface 1403 receives a second data packet of the first service from the access network device using the second RNTI;

[0324] The processor 1401 merges the first data packet and the second data packet into the first radio bearer.

[0325] In one embodiment, the processor 1401 merging the first data packet and the second data packet into the first radio bearer includes:

[0326] In a case where the first data packet and the second data packet are data packets of the MAC layer, merging the RLC PDUs included in the first data packet and the second data packet onto the first radio bearer at the RLC layer; or

[0327] In a case where the first data packet and the second data packet are data packets of the RLC layer, the PDCP PDUs included in the first data packet and the second data packet are merged into the first radio bearer at the PDCP layer.

[0328] In one embodiment, the processor 1401 merging the RLC PDUs included in the first data packet and the second data packet onto the first radio bearer at the RLC layer includes:

[0329] The RLC PDU included in the first data packet and the RLC PDU included in the second data packet are sorted and / or deduplicated.

[0330] In one embodiment, the processor 1401 merging the PDCP PDUs included in the first data packet and the second data packet onto the first radio bearer at the PDCP layer includes:

[0331] The PDCP PDU included in the first data packet and the PDCP PDU included in the second data packet are sorted and / or deduplicated.

[0332] Among them, the steps of receiving the first RNTI in steps 402, 904 and 1106, the steps of receiving the second RNTI in steps 403, 905 and 1107, the steps of receiving the data packet of the first service in steps 404, 907 and 1109, and the steps of receiving configuration information in steps 906 and 1108 can be executed by the input interface 1303 in the terminal device.

[0333] The establishing unit 1301 and the determining unit 1303 may be implemented by the processor 1401 and the memory 1402 in the terminal device, and the receiving unit 1302 may be implemented by the input interface 1403 in the terminal device.

[0334] The above-mentioned terminal device can also be used to execute various methods executed by the terminal device in the aforementioned method embodiment, which will not be repeated here.

[0335] based on Figure 1 The network architecture shown is shown in Figure 15 , Figure 15 This is a structural diagram of another communication device disclosed in an embodiment of the present invention. Figure 15 As shown, the communication device may include an input interface 1501, a logic circuit 1502 and an output interface 1503. The input interface 1501 and the output interface 1503 are connected through the logic circuit 1502. The input interface 1501 is used to receive information from other communication devices, and the output interface 1503 is used to output, schedule or send information to other communication devices. The logic circuit 1502 is used to perform operations other than the operations of the input interface 1501 and the output interface 1503, such as implementing the functions implemented by the processor 1401 in the above embodiment. The communication device can be an access network device or a chip in an access network device, or it can be a terminal device or a chip in a terminal device. For a more detailed description of the input interface 1501, the logic circuit 1502 and the output interface 1503, please refer directly to the above Figure 4 、 Figure 9 and Figure 11 The relevant descriptions of the access network device or the terminal device in the method embodiment shown are directly obtained and are not repeated here.

[0336] The embodiment of the present invention also discloses a computer-readable storage medium having a computer program stored thereon. When the computer program is executed, the following steps are implemented: Figure 4 、 Figure 9 and Figure 11 The communication method shown.

[0337] The specific implementation methods described above further illustrate the purpose, technical solutions and beneficial effects of this application. It should be understood that the above description is only the specific implementation methods of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent replacements, improvements, etc. made on the basis of the technical solutions of this application should be included in the scope of protection of this application.

Claims

1. A communication method, characterized in that: include: Establishing a first radio bearer for a first terminal device, where the first radio bearer is used to transmit a first service; The first service is a multicast service; Allocate a first radio network temporary identifier (RNTI) and a second RNTI to the first terminal device, where the first RNTI is used to schedule a service to the first terminal device, and the second RNTI is used to schedule the first service to a group of terminal devices including the first terminal device; The first RNTI being used to schedule a service to the first terminal device includes: the first RNTI being used to schedule a non-retransmission data packet of the first service to the first terminal device; Use the first RNTI and the second RNTI to schedule data packets of the first service to the first terminal device on the first radio bearer.

2. The method according to claim 1, characterized in that The method further comprises: A service establishment request message is received from a core network device, where the service establishment request message carries public information indicating that the first service is a multicast service.

3. The method according to claim 2, characterized in that The public information is service information or address information of the multicast service.

4. The method according to claim 2 or 3, characterized in that The method further comprises: The first radio bearer is associated with a first public data channel, where the first public data channel is used to transmit data of the first service with the core network device.

5. The method according to any one of claims 1 to 3, characterized in that The using the first RNTI and the second RNTI to schedule the data packet of the first service to the first terminal device on the first radio bearer includes: Scheduling a data packet of the first service to the first terminal device on the first radio bearer using the second RNTI; receiving feedback information from the first terminal device indicating that the data packet transmission has failed; Use the first RNTI to retransmit the data packet of the first service to the first terminal device on the first radio bearer.

6. The method according to claim 5, characterized in that The method further comprises: An association relationship between a first process and a second process is sent to the first terminal device, where the first process is a process for initially transmitting the data packet, and the second process is a process for retransmitting the data packet.

7. The method according to any one of claims 1 to 3, characterized in that The method further comprises: Send indication information to the first terminal device, where the indication information is used to indicate that the second RNTI is used to schedule the first service.

8. The method according to any one of claims 1 to 3, characterized in that The data packet includes a logical channel identifier, and the logical channel identifier is used to indicate that the data packet transmitted by the second RNTI is a data packet of the first service.

9. The method according to any one of claims 1 to 3, characterized in that The method further comprises: Send first configuration information to the first terminal device, where the first configuration information is used to instruct the first terminal device to detect the second RNTI according to the first configuration information.

10. The method according to claim 9, characterized in that The first configuration information includes one or more of the following: Bandwidth part BWP information corresponding to the second RNTI; Control resource set CORESET information corresponding to the second RNTI; and Search space information corresponding to the second RNTI.

11. The method according to any one of claims 1 to 3, characterized in that The method further comprises: Sending, to the resource management module, indication information for indicating the number of receiving terminal devices of the first service and / or configuration information of the RNTI used by the first service; receiving second configuration information corresponding to the first service from the resource management module, where the second configuration information includes configuration information of the second RNTI; Send the second configuration information to the first terminal device.

12. A communication method, characterized in that: include: Establishing a first radio bearer with an access network device, where the first radio bearer is used to transmit a first service; The first service is a multicast service; Receiving a first RNTI and a second RNTI from the access network device, where the first RNTI is used to receive a service scheduled from the access network device to a terminal device, and the second RNTI is used to receive the first service scheduled from the access network device to a group of terminal devices including the terminal device; The first RNTI is used to receive a service scheduled from the access network device to the terminal device, including: the first RNTI is used to receive a non-retransmitted data packet of a first service scheduled from the access network device to the terminal device; The first RNTI and the second RNTI are used to receive data packets of the first service scheduled by the access network device on the first radio bearer.

13. The method according to claim 12, characterized in that The receiving, on the first radio bearer, a data packet of the first service scheduled by the access network device using the first RNTI and the second RNTI includes: Using the second RNTI to receive, on the first radio bearer, a data packet of the first service scheduled by the access network device; Sending feedback information indicating a failure in transmission of the data packet to the access network device; The first RNTI is used to receive, on the first radio bearer, a data packet of the first service retransmitted from the access network device.

14. The method according to claim 13, characterized in that The method further comprises: receiving an association relationship between a first process and a second process from the access network device, where the first process is a process for initially transmitting the data packet, and the second process is a process for retransmitting the data packet; The receiving, on the first radio bearer, the data packet of the first service retransmitted from the access network device using the first RNTI includes: The first RNTI is used according to the association relationship to receive, on the first radio bearer, a data packet of the first service retransmitted from the access network device.

15. The method according to any one of claims 12 to 14, characterized in that: The method further comprises: receiving first indication information from the access network device; Determine, according to the first indication information, that the second RNTI is used to schedule the first service.

16. The method according to any one of claims 12 to 14, characterized in that: The method further comprises: Determine, according to the logical channel identifier included in the data packet, that the data packet transmitted by the second RNTI is a data packet of the first service.

17. The method according to claim 13 or 14, characterized in that The method further comprises: Receiving configuration information from the access network device; The receiving, on the first radio bearer, a data packet of the first service scheduled by the access network device using the second RNTI includes: Detecting, on the first radio bearer according to the configuration information, data packets of the first service from the access network device from the second RNTI.

18. The method according to claim 17, characterized in that The configuration information includes one or more of the following: BWP information corresponding to the second RNTI; CORESET information corresponding to the second RNTI; and Search space information corresponding to the second RNTI.

19. The method according to any one of claims 12 to 14, characterized in that: The method further comprises: receiving second indication information from the access network device; Determine, according to the second indication information, that the first radio bearer is a radio bearer used to transmit the first service.

20. The method according to claim 12, wherein The receiving, on the first radio bearer, a data packet of the first service from the access network device using the first RNTI and the second RNTI includes: receiving a first data packet of the first service from the access network device using the first RNTI; receiving a second data packet of the first service from the access network device using the second RNTI; The first data packet and the second data packet are merged into the first radio bearer.

21. The method according to claim 20, characterized in that The merging of the first data packet and the second data packet into the first radio bearer includes: In a case where the first data packet and the second data packet are data packets at the Media Access Control (MAC) layer, merging the Radio Link Control (RLC) Protocol Data Units (PDUs) included in the first data packet and the second data packet onto the first radio bearer at the RLC layer; or In a case where the first data packet and the second data packet are data packets of the RLC layer, the Packet Data Convergence Protocol (PDCP) PDUs included in the first data packet and the second data packet are merged into the first radio bearer at the PDCP layer.

22. The method according to claim 21, characterized in that The merging the RLC PDUs included in the first data packet and the second data packet onto the first radio bearer at the RLC layer includes: The RLC PDU included in the first data packet and the RLC PDU included in the second data packet are sorted and / or deduplicated.

23. The method according to claim 21, characterized in that The merging of the PDCP PDUs included in the first data packet and the second data packet onto the first radio bearer at the PDCP layer includes: The PDCP PDU included in the first data packet and the PDCP PDU included in the second data packet are sorted and / or deduplicated.

24. A communication device, characterized in that: include: An establishing unit, configured to establish a first radio bearer for a first terminal device, where the first radio bearer is used to transmit a first service; The first service is a multicast service; an allocating unit, configured to allocate a first RNTI and a second RNTI to the first terminal device, where the first RNTI is used to schedule a service to the first terminal device, and the second RNTI is used to schedule the first service to a group of terminal devices including the first terminal device; The first RNTI being used to schedule a service to the first terminal device includes: the first RNTI being used to schedule a non-retransmission data packet of the first service to the first terminal device; A sending unit is used to use the first RNTI and the second RNTI to schedule data packets of the first service to the first terminal device on the first radio bearer.

25. The device according to claim 24, characterized in that The device further comprises: The receiving unit is used to receive a service establishment request message from a core network device, where the service establishment request message carries public information indicating that the first service is a multicast service.

26. The device according to claim 25, characterized in that The public information is service information or address information of the multicast service.

27. The device according to claim 25 or 26, characterized in that The device further comprises: An associating unit is used to associate the first radio bearer with a first public data channel, where the first public data channel is used to transmit data of the first service with the core network device.

28. The device according to any one of claims 24 to 26, characterized in that The sending unit is specifically configured to: Scheduling a data packet of the first service to the first terminal device on the first radio bearer using the second RNTI; receiving feedback information from the first terminal device indicating that the data packet transmission has failed; Use the first RNTI to retransmit the data packet of the first service to the first terminal device on the first radio bearer.

29. The device according to claim 28, characterized in that The sending unit is further used to send an association relationship between a first process and a second process to the first terminal device, where the first process is a process used to initially transmit the data packet, and the second process is a process used to retransmit the data packet.

30. The device according to any one of claims 24 to 26, characterized in that The sending unit is further used to send indication information to the first terminal device, where the indication information is used to indicate that the second RNTI is used to schedule the first service.

31. The device according to any one of claims 24 to 26, characterized in that The data packet includes a logical channel identifier, and the logical channel identifier is used to indicate that the data packet transmitted by the second RNTI is a data packet of the first service.

32. The device according to any one of claims 24 to 26, characterized in that The sending unit is further used to send first configuration information to the first terminal device, where the first configuration information is used to instruct the first terminal device to detect the second RNTI according to the first configuration information.

33. The device according to claim 32, characterized in that The first configuration information includes one or more of the following: BWP information corresponding to the second RNTI; CORESET information corresponding to the second RNTI; and Search space information corresponding to the second RNTI.

34. The device according to claim 25 or 26, characterized in that The sending unit is further used to send indication information for indicating the number of receiving terminal devices of the first service and / or configuration information of the RNTI used by the first service to the resource management module; The receiving unit is further configured to receive second configuration information corresponding to the first service from the resource management module, where the second configuration information includes configuration information of the second RNTI; The sending unit is further used to send the second configuration information to the first terminal device.

35. A communication device, characterized in that: include: An establishing unit, configured to establish a first radio bearer with an access network device, where the first radio bearer is used to transmit a first service; The first service is a multicast service; A receiving unit, configured to receive a first RNTI and a second RNTI from the access network device, wherein the first RNTI is used to receive a service scheduled from the access network device to a terminal device, and the second RNTI is used to receive the first service scheduled from the access network device to a group of terminal devices including the terminal device; The first RNTI is used to receive a service scheduled from the access network device to the terminal device, including: the first RNTI is used to receive a non-retransmitted data packet of a first service scheduled from the access network device to the terminal device; The receiving unit is further configured to receive, on the first radio bearer, a data packet of the first service scheduled by the access network device using the first RNTI and the second RNTI.

36. The device according to claim 35, characterized in that The receiving unit receiving, on the first radio bearer, a data packet of the first service scheduled by the access network device using the first RNTI and the second RNTI includes: Using the second RNTI to receive, on the first radio bearer, a data packet of the first service scheduled by the access network device; Sending feedback information indicating a failure in transmission of the data packet to the access network device; The first RNTI is used to receive, on the first radio bearer, a data packet of the first service retransmitted from the access network device.

37. The device according to claim 36, characterized in that The receiving unit is further configured to receive an association relationship between a first process and a second process from the access network device, where the first process is a process for initially transmitting the data packet, and the second process is a process for retransmitting the data packet; The receiving unit receiving, on the first radio bearer, the data packet of the first service retransmitted from the access network device using the first RNTI includes: The first RNTI is used according to the association relationship to receive, on the first radio bearer, a data packet of the first service retransmitted from the access network device.

38. The device according to any one of claims 35 to 37, characterized in that The receiving unit is further configured to receive first indication information from the access network device; The device further comprises: A first determining unit is configured to determine, according to the first indication information, that the second RNTI is used for scheduling the first service.

39. The device according to any one of claims 35 to 37, characterized in that The device further comprises: The second determining unit is configured to determine, according to the logical channel identifier included in the data packet, that the data packet transmitted by the second RNTI is a data packet of the first service.

40. The device according to claim 36 or 37, characterized in that The receiving unit is further configured to receive configuration information from the access network device; The receiving unit receiving, on the first radio bearer, a data packet of the first service scheduled by the access network device using the second RNTI includes: Detecting, on the first radio bearer according to the configuration information, data packets of the first service from the access network device from the second RNTI.

41. The device according to claim 40, characterized in that The configuration information includes one or more of the following: BWP information corresponding to the second RNTI; CORESET information corresponding to the second RNTI; and Search space information corresponding to the second RNTI.

42. The device according to any one of claims 35 to 37, characterized in that The receiving unit is further configured to receive second indication information from the access network device; The device further comprises: The third determining unit is configured to determine, according to the second indication information, that the first radio bearer is a radio bearer for transmitting the first service.

43. The device according to claim 35, characterized in that The receiving unit receiving, on the first radio bearer, a data packet of the first service from the access network device using the first RNTI and the second RNTI includes: receiving a first data packet of the first service from the access network device using the first RNTI; receiving a second data packet of the first service from the access network device using the second RNTI; The first data packet and the second data packet are merged into the first radio bearer.

44. The device according to claim 43, characterized in that The receiving unit merging the first data packet and the second data packet into the first radio bearer includes: In a case where the first data packet and the second data packet are data packets of the MAC layer, merging the RLC PDUs included in the first data packet and the second data packet onto the first radio bearer at the RLC layer; or In a case where the first data packet and the second data packet are data packets of the RLC layer, the PDCP PDUs included in the first data packet and the second data packet are merged into the first radio bearer at the PDCP layer.

45. The device according to claim 44, characterized in that The receiving unit merging the RLC PDUs included in the first data packet and the second data packet onto the first radio bearer at the RLC layer includes: The RLC PDU included in the first data packet and the RLC PDU included in the second data packet are sorted and / or deduplicated.

46. ​​The device according to claim 44, characterized in that The receiving unit merging the PDCP PDUs included in the first data packet and the second data packet onto the first radio bearer at the PDCP layer includes: The PDCP PDU included in the first data packet and the PDCP PDU included in the second data packet are sorted and / or deduplicated.

47. A communication device, characterized in that It includes a processor, a memory, an input interface and an output interface, the input interface is used to receive information from other communication devices outside the communication device, the output interface is used to output information to other communication devices outside the communication device, and the processor calls the computer program stored in the memory to implement the method described in any one of claims 1-23.

48. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed, the method according to any one of claims 1 to 23 is implemented.

Images