WO2021018213A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置 Download PDF

Info

Publication number
WO2021018213A1
WO2021018213A1 PCT/CN2020/105575 CN2020105575W WO2021018213A1 WO 2021018213 A1 WO2021018213 A1 WO 2021018213A1 CN 2020105575 W CN2020105575 W CN 2020105575W WO 2021018213 A1 WO2021018213 A1 WO 2021018213A1
Authority
WO
WIPO (PCT)
Prior art keywords
rnti
service
data packet
access network
network device
Prior art date
Application number
PCT/CN2020/105575
Other languages
English (en)
French (fr)
Inventor
李秉肇
官磊
李濛
杨艳梅
张万强
葛翠丽
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from CN201910866760.3A external-priority patent/CN112312575A/zh
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP20846975.9A priority Critical patent/EP3975649A4/en
Publication of WO2021018213A1 publication Critical patent/WO2021018213A1/zh
Priority to US17/568,097 priority patent/US20220124840A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers

Definitions

  • the embodiment of the present invention relates to the field of communication technology, and in particular to a communication method and device.
  • Multicast technology is a point-to-multipoint communication technology.
  • the same group radio network temporary identity G-RNTI
  • G-RNTI group radio network temporary identity
  • the terminal device needs to establish a unicast bearer so that it can receive the service through the unicast bearer, but the terminal device may switch between multicast and unicast. An interrupt is generated so that the terminal device cannot receive information, which reduces the communication efficiency.
  • the embodiment of the present invention discloses a communication method and device for improving communication efficiency.
  • a communication method which establishes a first radio bearer for transmitting a first service for a first terminal device, and assigns a first radio network temporary identity (RNTI) and a second radio network temporary identity to the first terminal device.
  • RNTI radio network temporary identity
  • the first RNTI is used to schedule a service to the first terminal device
  • the second RNTI is used to schedule the first service to a group of terminal devices including the first terminal device.
  • the terminal equipment Since the terminal equipment is allocated the RNTI for scheduling unicast services and the RNTI for scheduling multicast services at the same time for scheduling data from the same radio bearer, the terminal equipment will not cause wireless transmission when switching between multicast and unicast.
  • the bearer changes, so there is no interruption, which can improve communication efficiency.
  • a service establishment request message from a core network device is received, and the service establishment request message carries public information used to indicate that the first service is a multicast service. It can be seen that the service can be determined as a multicast service through public information, which can improve the efficiency of determining the service type.
  • the public information can be service information of a multicast service, or address information.
  • the first radio 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, and there is no need to separately establish dedicated data channels for different terminal devices, thereby avoiding repeated transmission of the same data on multiple dedicated data channels.
  • the second RNTI can be used to schedule the data packet of the first service to the first terminal device on the first radio bearer, and receive the data packet from the first terminal device that indicates that the transmission of the first service fails. Using the first RNTI to retransmit the data packet of the first service to the first terminal device on the first radio bearer.
  • the second RNTI can be used to newly transmit data, and the first RNTI can be used to retransmit the failed data. It can be seen that the retransmission of the failed data will not affect the transmission of new data on the second RNTI, thereby improving communication efficiency.
  • the association relationship between the first process and the second process can be sent to the first terminal device.
  • the first process is the process used to initially transmit the data packet of the first service
  • the second process is used The process of retransmitting the data packet of the first service.
  • the data newly transmitted or retransmitted using different RNTIs can be associated according to the association relationship, so that the received data can be processed correctly, and the data processing efficiency can be improved.
  • indication information may be sent to the first terminal device, and the indication information may indicate that the second RNTI is used for scheduling the first service, so that the first terminal device can quickly determine which service the second RNTI is used for transmission .
  • the data packet of the first service may include a logical channel identifier.
  • 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. It can be seen that no additional transmission information is required, and only The data packet can be used to determine the service corresponding to the data packet, which can save resources.
  • the first configuration information may be sent to the first terminal device.
  • 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 The second RNTI is detected, so that communication efficiency can be improved.
  • the first configuration information may include bandwidth part (BWP) information corresponding to the second RNTI, control resource set (CORESET) information corresponding to the second RNTI, and corresponding information to the second RNTI.
  • BWP bandwidth part
  • CORESET control resource set
  • 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 may be sent to the resource management module, and the first service from the resource management module may be received.
  • the second configuration information including the configuration information of the second RNTI corresponding to the service sends the second configuration information to the first terminal device.
  • the association relationship between the first terminal device and the data of the first service from the core network device may be received.
  • 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 (flow) of the first terminal device and an identifier of a public QoS flow, and the public QoS flow is used to transmit the first terminal device.
  • QoS quality of service
  • the association relationship between the QoS flow identification of the first terminal device and the QoS flow identification of the second terminal device, the QoS flow of the second terminal device is used to transmit the data of the first service
  • the second terminal device is A terminal device in the group of terminal devices other than the first terminal device; the association relationship between the identifier of the QoS flow of the first terminal device and the index information of the data of the first service. It can be seen that it is possible to determine which terminal devices receive the data of the first service through the association relationship, so that the same second RNTI can be allocated to these terminal devices.
  • a session establishment request message for establishing a QoS flow of the first terminal device is received from the core network device.
  • the session establishment request message is used to indicate that the QoS flow of the first terminal device is used to carry data of the multicast service. It can be seen 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, which can improve the efficiency of determining the service type.
  • a second aspect discloses a communication device that can establish a first radio 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 receives the data packet of the first service scheduled by the access network device on the first radio bearer.
  • the first RNTI is used to receive a service scheduled from an access network device to a terminal device
  • the second RNTI is used to receive a first service scheduled from an access network device to a group of terminal devices including the terminal device.
  • the terminal equipment can simultaneously use the RNTI for scheduling unicast services and the RNTI for scheduling multicast services to receive services from the same radio bearer, the terminal equipment will not change the radio bearer when switching between multicast and unicast. Therefore, there is no interruption, which can improve communication efficiency.
  • the second RNTI can be used to receive the data packet of the first service scheduled by the access network device on the first radio bearer, and send the data packet transmission indicating the first service to the access network device.
  • the first RNTI is used to receive the data packet of the first service retransmitted from the access network device on the first radio bearer.
  • the second RNTI can be used to newly transmit data, and the first RNTI can be used to retransmit the failed data. It can be seen that the retransmission of the failed data will not affect the transmission of new data on the second RNTI, thereby improving communication efficiency.
  • the association relationship between the first process and the second process from the access network device can be received, and the first RNTI is used according to the association relationship to receive the retransmission from the access network device on the first radio bearer
  • the first business data packet is a process for initially transmitting a data packet of the first service
  • the second process is a process for retransmitting a data packet of the first service.
  • the data newly transmitted or retransmitted using different RNTIs can be associated according to the association relationship, so that the received data can be processed correctly, and the data processing efficiency can be improved.
  • the first indication information from the access network device may be received, and the second RNTI may be determined to be used for scheduling the first service according to the first indication information, so that the first terminal device can quickly determine the second RNTI to use. Which service to transmit.
  • the data packet transmitted by the second RNTI can be determined as the data packet of the first service according to the logical channel identifier included in the data packet of the first service. It can be seen that there is no need to transmit additional information, and only need to pass the data packet. The business corresponding to the data packet can be determined, which can save resources.
  • the configuration information from the access network device can be received, and the data packet of the first service from the access network device can be detected from the second RNTI on the first radio bearer according to the configuration information, so that the terminal device The second RNTI can be quickly detected according to the configuration information, so that communication efficiency can be improved.
  • 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.
  • the second indication information from the access network device can be received, and the first radio bearer can be determined according to the second indication information as the radio bearer used to transmit the first service, so that the terminal device can follow the second indication
  • the information quickly determines which service is the service transmitted by the first radio bearer, thereby improving communication efficiency.
  • the first RNTI can be used to receive the first data packet of the first service from the access network device
  • the second RNTI can be used to receive the second data packet of the first service from the access network device. Combining the first data packet and the second data packet on the first radio 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 combining them can improve the data transmission efficiency.
  • the first data packet and the second data packet can be The included radio link control (RLC) protocol data unit (protocol data unit, PDU) is merged into the first radio bearer at the RLC layer, and the first data packet and the second data packet are data packets of the RLC layer
  • RLC radio link control
  • PDU protocol data unit
  • the Packet Data Convergence Protocol (PDCP) PDUs included in the first data packet and the second data packet may be merged onto the first radio bearer at the PDCP layer.
  • PDCP Packet Data Convergence Protocol
  • the RLC PDU included in the first data packet and the RLC PDU included in the second data packet may be sequenced and/or deduplicated.
  • the PDCP PDU included in the first data and the PDCP PDU included in the second data packet may be sorted and/or deduplicated.
  • a third aspect discloses a communication device that includes a module for executing the communication method disclosed in the first aspect or any possible implementation manner of the first aspect, or includes a module for executing the second aspect or the second aspect Any possible implementation of the module of the disclosed communication method.
  • a fourth aspect discloses a communication device, which may be an access network device or a chip in the access network 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 other communication devices other than the communication device, and the output interface is used to output information to other communication devices other than the communication device.
  • the processor executes the computer program stored in the memory, the processor is caused to execute the communication method disclosed in the first aspect or any possible implementation manner of the first aspect.
  • a fifth aspect discloses a communication device, which may be a terminal device or a chip in the 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 other communication devices other than the communication device, and the output interface is used to output information to other communication devices other than the communication device.
  • the processor executes the computer program stored in the memory, the processor is caused to execute the communication method disclosed in the second aspect or any possible implementation manner of the second aspect.
  • a sixth aspect discloses a computer-readable storage medium with a computer program stored on the computer-readable storage medium, and when the computer program runs, the communication as disclosed in the first aspect or any possible implementation manner of the first aspect is realized Method, or implement the communication method disclosed in the second aspect or any possible implementation manner of the second aspect.
  • Figure 1 is a schematic diagram of a network architecture disclosed in an embodiment of the present invention.
  • FIG. 2 is a schematic diagram of implementing multicast transmission through SC-PTM according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of an SC-PTM channel configuration disclosed in an embodiment of the present invention.
  • FIG. 4 is a schematic flowchart of a communication method disclosed in an embodiment of the present invention.
  • Fig. 5 is a schematic diagram of data merging disclosed in an embodiment of the present invention.
  • Fig. 6 is a schematic diagram of a process of merging data into an RLC layer disclosed in an embodiment of the present invention.
  • FIG. 7 is a schematic diagram of C-RNTI and G-RNTI allocated to terminal equipment according to an embodiment of the present invention.
  • FIG. 8 is another schematic diagram of assigning C-RNTI and G-RNTI to terminal equipment according to an embodiment of the present invention.
  • FIG. 9 is a schematic flowchart of another communication method disclosed in an embodiment of the present invention.
  • FIG. 10 is a schematic diagram of using G-RNTI to schedule data according to an embodiment of the present invention.
  • FIG. 11 is a schematic flowchart of another communication method disclosed in an embodiment of the present invention.
  • FIG. 12 is a schematic structural diagram of a communication device disclosed in an embodiment of the present invention.
  • FIG. 13 is a schematic structural diagram of another communication device disclosed in an embodiment of the present invention.
  • FIG. 14 is a schematic structural diagram of another communication device disclosed in an embodiment of the present invention.
  • 15 is a schematic structural diagram of another communication device disclosed in an embodiment of the present invention.
  • 16 is a schematic flowchart of another communication method disclosed in an embodiment of the present invention.
  • FIG. 17 is a schematic flowchart of another communication method disclosed in an embodiment of the present invention.
  • the embodiment of the present invention discloses a communication method and device for improving communication efficiency. Detailed descriptions are given below.
  • FIG. 1 is a schematic diagram of a network architecture disclosed in an embodiment of the present invention.
  • 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, and the access network device 102 and the core network device 103 may be connected through 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 used to send information to the terminal device 101 and the core network device 103, and to 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.
  • the terminal device 101 may be a user equipment (UE), an access terminal, a user unit, a user 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 can be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), with wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminals in the future 5G network or terminals in the future evolution of the public land mobile network (PLMN), etc. .
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • the access network device 102 may be a device used to communicate with the terminal device 101, and may be a base station (global system for mobile communication, GSM) or code division multiple access (CDMA).
  • base transmitter station, BTS can also be the base station (nodeB, NB) in the wideband code division multiple access (wideband code division multiple access, WCDMA) system, or the evolution in the long term evolution (LTE) system Type base station (evolutional node B, eNB or eNodeB), it can also be a terminal that functions as an access network device in device-to-device (D2D) communication, and it can also be a relay station, access point, in-vehicle device, and transmission point , Wearable devices and network side devices in the future 5G network or access network devices in the future evolved PLMN, or any device that undertakes network functions, etc.
  • GSM global system for mobile communication
  • CDMA code division multiple access
  • base transmitter station, BTS can also be the base station (nodeB,
  • the core network device 103 in different systems may correspond to different devices.
  • the service support node serving GPRS support node, SGSN
  • general packet radio service general packet radio service
  • gateway support node gateway support node (gateway GPRS Support Node, GGSN) of GPRS
  • MME mobility management entity
  • S-GW serving gateway
  • 5G it can correspond to access and mobility management function (AMF), session management function (session management function, SMF) or user plane function (UPF).
  • AMF access and mobility management function
  • SMF session management function
  • UPF user plane function
  • FIG. 2 is a schematic diagram of implementing multicast transmission through SC-PTM according to an embodiment of the present invention.
  • the cell can dispatch service data to multiple terminal devices simultaneously through G-RNTI, and each G-RNTI can be associated with a multimedia broadcast multicast service (MBMS) . Therefore, in an area, only cells containing terminal equipment need to send data, and cells not containing terminal equipment do not need to send data, thereby saving air interface resources.
  • MBMS multimedia broadcast multicast service
  • a physical downlink shared channel (physical downlink share 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.
  • an access network device can send downlink control information (downlink control information, DCI) carried on a 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.
  • DCI downlink control information
  • FIG. 3 is a schematic diagram of an SC-PTM channel configuration disclosed in an embodiment of the present invention.
  • SC-PTM is configured with single cell MBMS point-to-multipoint control channel (SC-MCCH) and single cell MBMS traffic control channel (single cell MBMS traffic control channel, SC-MTCH).
  • 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.
  • SC-MCCH is used to transmit data in a periodic manner.
  • the SC-MCCH configuration information can be transmitted through a broadcast channel.
  • the SC-MCCH configuration information is used to configure the receiving parameters of the SC-MCCH, which can include the MCCH modification period, repetition period, and transmission duration.
  • SC-MCCH uses PDCSH for transmission, and its corresponding PDCCH uses single cell RNTI (single cell RNTI, SC-RNTI) for scrambling.
  • the value of SC-RNTI is fixed by the protocol and does not need to be configured in the broadcast.
  • the configuration information of the SC-MTCH can be transmitted through the SC-MCCH.
  • the configuration information of the SC-MTCH may include the configuration information of the multicast service.
  • the configuration information of each service may include the temporary multicast group identifier (TMGI) of the service, the corresponding G-RNTI, DRX parameters, and neighbor cell information for sending the configuration information of the service.
  • TMGI temporary multicast group identifier
  • the SC-MTCH is also carried on the PDSCH, and the corresponding PDCCH is scrambled by G-RNTI.
  • the access network device For multicast service transmission, such as SC-PTM, since the multicast service is sent in one-to-many mode, the access network device sends blindly. Regardless of the receiving quality of the specific terminal device, the receiving quality of a certain terminal device is not In a good situation, a unicast bearer needs to be established, and the service is transmitted through the unicast bearer, so that the service continuity guarantee is not very good, thereby reducing the communication efficiency.
  • FIG. 4 is a schematic flowchart of a communication method disclosed in an embodiment of the present invention. As shown in Fig. 4, the communication method may include the following steps.
  • the access network device establishes a first radio bearer with the first terminal device.
  • the access network device may establish a first radio bearer with the first terminal device.
  • the access network device may, after receiving the quality of service (QoS) parameter of the first service sent by the core network device, establish a first radio bearer for the first service according to the requirements of the QoS parameter, and then transfer the first radio bearer to the first service.
  • the parameters of the radio bearer are sent to the first terminal device.
  • the first radio bearer is a bearer that transmits the first service between the access network device and the first terminal device.
  • the parameters of the first radio bearer may include one or more of the following:
  • Radio bearer information may include the identity of the first radio bearer
  • PDCP layer configuration parameters can include PDCP sequence number length, encryption parameters, header compression parameters, etc.
  • the RLC layer configuration parameters can include logical channel number, RLC sequence number length, RLC mode, etc.
  • the RLC mode can be acknowledged mode (AM) mode or unacknowledged mode, UM) mode, which can also be a transparent mode (TM) mode;
  • the access network device sends the first RNTI to the first terminal device.
  • the access network device can allocate the first RNTI to 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 be the first terminal device Dispatch services, not for other terminal equipment dispatch services.
  • the scheduled service 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 may be a cell radio network temporary identifier (C-RNTI), or may be another RNTI that can schedule unicast services.
  • step 401 and step 402 can be executed serially or in parallel.
  • the first RNTI may be allocated before step 401.
  • the first RNTI may be allocated during the process of the first terminal device accessing the current cell, or it may be the process of the first terminal device being handed over from another cell to the current cell. Allocated in.
  • the first RNTI may also be allocated at the same time or after step 401 is executed.
  • the access network device sends the second RNTI to the first terminal device.
  • the access network device may allocate the second RNTI to the first terminal device, and send the second RNTI to the first terminal device.
  • the access network device may also allocate a second RNTI to the first terminal device, and the second RNTI may send the second RNTI to a group including the first terminal device.
  • the terminal device schedules the first service, that is, the second RNTI can 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 the multicast service.
  • the second RNTI may be a G-RNTI, or other RNTI that can schedule multicast services.
  • step 403 and step 402 can be performed simultaneously or separately.
  • the target access network device allocates radio bearer parameters for the terminal device, and simultaneously allocates the first RNTI and the second RNTI and passes The source access network device sends to the terminal device.
  • the access network device first allocates the first RNTI to the terminal device, and then allocates the second RNTI when the first service for the terminal device is established afterwards.
  • the access network device 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.
  • the access network device After the access network device establishes the 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 to the first terminal device The data packet of the first service is transmitted through the first radio bearer.
  • the first terminal device can use the first RNTI and the second RNTI to receive the data packet of the first service scheduled from the access network device, and process the data packet of the first service through the configuration parameters related to the first radio bearer.
  • the access network device uses the first RNTI and the second RNTI to simultaneously schedule the 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 send the data packets of the first service on the first radio bearer.
  • the first terminal device schedules the data packet of the first service, and at the same time uses the second RNTI to schedule the data packet of the first service to the first terminal device on the first radio bearer.
  • the first terminal device can use the first RNTI and the second RNTI to simultaneously receive data packets from the first service scheduled by the access network device on the first radio bearer.
  • the radio bearer receives the data packet from the first service scheduled by the access network device, and the first terminal device can use the second RNTI to receive the data packet from 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 the data packets of the first service, or they may be different, that is, the first RNTI and the second RNTI scheduling data packets may be partially the same , It can be completely different.
  • the first RNTI schedules part of the data packets of the first service
  • the second RNTI schedules the remaining part of the data packets of the first service.
  • the access network device first uses the second RNTI to schedule the data packets of the first service to the first terminal device on the first radio bearer, and the first terminal device uses the second RNTI to receive data packets from the access network on the first radio bearer.
  • the data packet of the first service scheduled by the device After that, the first terminal device determines whether the transmission of the data packet of the first service is successful, and in the case of determining that the transmission of the data packet of the first service fails, the first terminal device sends a data packet indicating the first service to the access network device Feedback information of transmission failure.
  • the access network device After the access network device receives the feedback information from the first terminal device indicating the failure of transmission of the data packet of the first service, the access network device uses the first RNTI to retransmit the first terminal device on the first radio bearer. Business data package.
  • the first terminal device determines that the data packet of the first service is successfully transmitted, the first terminal device sends feedback information indicating that the data packet of the first service is successfully transmitted to the access network device, and the access network device receives
  • the feedback information of the first terminal device used to indicate the successful transmission of the data packet of the first service ends the transmission of the data packet of the first service.
  • C-RNTI scheduling or C-RNTI scheduling can be based on the following principles: C-RNTI is used when the same service is received by only one terminal device, and G-RNTI is used when the same service is received by multiple end devices. -RNTI; which RNTI scheduling generates the greater throughput, which RNTI is used.
  • C-RNTI can schedule 1000 bits (bit) and 2000 bits of data for terminal device 1 and terminal device 2 respectively, and G-RNTI can only be used once To schedule 200-bit data for terminal equipment 1 and terminal equipment 2, use C-RNTI for scheduling for terminal equipment 1 and terminal equipment 2 respectively; in the case of a terminal equipment using G-RNTI scheduling consecutive failures, you can switch to C-RNTI scheduling.
  • the first terminal device may use the first RNTI to receive the first data packet of the first service from the access network device, and use the second RNTI 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 are combined on the first radio bearer.
  • the first data packet and the second data packet are MAC layer data packets
  • the first terminal device may merge the RLC PDU included in the first data packet and the second data packet on the first radio bearer at the RLC layer, that is, the first The RLC PDU included in one data packet and the RLC PDU included in the second data packet are sequenced and/or deduplicated.
  • the first data packet and the second data packet are data packets of the RLC layer
  • the first terminal device combines the PDCP PDUs included in the first data packet and the second data packet onto the first radio bearer at the PDCP layer, that is, the first
  • the PDCP PDU included in the data and the PDCP PDU included in the second data packet are sequenced and/or deduplicated.
  • Deduplication means removing duplicate data.
  • FIG. 5 is a schematic diagram of data merging disclosed in an embodiment of the present invention.
  • the access network device passes the data of each terminal device through the PDCP layer and the RLC layer, it can use C-RNTI and G-RNTI to transmit the data to the MAC layer and the physical (physical, PHY) layer in turn.
  • Terminal Equipment The terminal device uses C-RNTI and G-RNTI to receive data through the PHY layer and the MAC layer in turn, and then combines the data received using C-RNTI and G-RNTI at the RLC layer and/or PDCP layer to the unicast bearer for processing .
  • FIG. 6 is a schematic diagram of a process of merging data into an RLC layer according to an embodiment of the present invention.
  • terminal device 1 uses C-RNTI1 to receive a multicast service with a logical channel (logic channel, LCH) identified as LCH1 and a unicast service with LCH identification as LCH2, and terminal device 1 and terminal device 2 use G-RNTI
  • LCH logic channel
  • terminal device 1 and terminal device 2 use G-RNTI
  • the terminal device 1 uses the C-RNTI1 to receive the multicast service with the LCH identifier as LCH1 and uses the G-RNTI to receive the multicast service with the LCH identifier as LCH1, and transfers these data to the RLC layer Perform merge processing.
  • FIG. 7 is a schematic diagram of assigning C-RNTI and G-RNTI to terminal equipment according to an embodiment of the present invention.
  • the dotted line represents the control plane connection
  • the solid line represents the transmission path of user data.
  • All three terminal devices are connected to the access network devices.
  • a C-RNTI and a data radio bearer (DRB) for unicast bearer are configured.
  • the DRB is also associated with a G- RNTI, through G-RNTI and C-RNTI scheduling to realize dynamic conversion between unicast and multicast.
  • three terminal devices receive the same service, and each terminal device has a unicast bearer, that is, a channel for receiving data based on C-RNTI.
  • the access network device also configures the same G-RNTI for the three terminal devices at the same time.
  • the access network device can schedule the same data to three terminal devices respectively, and unicast scheduling is used in this case.
  • the access network equipment schedules a copy of data and all three terminal equipment can receive it.
  • FIG. 8 is another schematic diagram of assigning C-RNTI and G-RNTI to terminal equipment disclosed in an embodiment of the present invention.
  • service data is transmitted between new radio core (NGC) network equipment and access network equipment.
  • the two terminal devices correspond to different C-RNTIs respectively, and the two terminal devices correspond to the same G-RNTI.
  • C-RNTI is used for terminal equipment to receive scheduling information for a single terminal device, and 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 adopted, only the terminal equipment configured with the C-RNTI can receive it, and if G-RNTI scheduling is adopted, multiple terminal devices can receive it.
  • FIG. 9 is a schematic flowchart of another communication method disclosed in an embodiment of the present invention. As shown in Fig. 9, the communication method may include the following steps.
  • the core network device sends a service establishment request message to the access network device.
  • 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 (protocol data unit, PDU) session establishment message, a context modification message, and other messages.
  • the first service is a multicast service.
  • the service establishment request message may carry public information used to indicate 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 multicast
  • the public information can be the service information of the multicast service
  • the service information can 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 the correspondence between service quality (quality of service, QoS) flow and public information.
  • the correspondence between QoS flow and public information can be as shown in Table 1:
  • Multiple QoS flows of a terminal device can correspond to multiple public information.
  • the public information corresponding to QoS flow 1 and QoS flow 2 is service 1 or multicast group address information 1
  • the public information corresponding to QoS flow 3 It is service 2 or multicast group address information 2.
  • QoS flow 1, QoS flow 2 and QoS flow 3 all have corresponding common 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 the service information of the multicast service
  • the multicast group address information 1 and the multicast group address information 2 are the address information of the multicast service.
  • Some QoS flows may have no public information.
  • QoS flow 4 has no public information, which means 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.
  • the service information in Table 1 may also be an identifier (identifier, ID) of the DRB, that is, the QoS flow in Table 1 may be replaced with the ID of the DRB.
  • the service establishment request message may directly indicate that the first service is a multicast service. That is, when 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, and the service establishment request message does not indicate that the service establishment request message is to be established. When the service is a multicast service, the service to be established by the service establishment request message is a unicast service.
  • 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 tunnelling protocol (GPRS tunnelling protocol, GTP) number, or other numbers with equivalent functions.
  • GTP GPRS tunnelling protocol
  • both access network equipment 1 and access network equipment 2 are connected to the core network equipment, UE1 and UE2 in access network equipment 1 receive service 1 at the same time, and UE3 and UE4 in access network equipment 2 receive service 1 at the same time.
  • the access network device 2 may allocate the same G-RNTI to UE1, UE3, and UE4 for unified scheduling. In order to determine which data UE1 has transmitted, the access network device 2 can determine the sequence relationship with the data packets of UE3 and UE4 according to the packet number of the data packet of UE1 being forwarded, and can first ensure that UE1, UE3 and UE4 are transmitted After the progress is aligned, transfer is performed.
  • the transmission progress of UE1 can be judged according to the data packet numbers and between UE3 and UE4 currently served by access network device 2. The difference in transfer progress.
  • the data packet number can also be used to determine whether the contents of the data packets transmitted to the UE are the same.
  • UE1 and UE2 have dedicated data channels between the core network device and the access network device 1. It can be determined which data packets of the two UEs have the same content according to the packet numbers transmitted by the two dedicated data channels.
  • G-RNTI can be used to schedule the same data packet to the two UEs at the same time.
  • 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.
  • the application server needs to know that the terminal device needs to receive the data of the first service, and the application server can trigger the PDU session modification process, which mainly includes the following steps:
  • the application server provides identification information related to the first service to the core network device, and the identification information is used by the core network device to identify that the first service is downlink data corresponding to the multicast service;
  • the application server provides the identification information of the first service to the policy control function (PCF) network element of the core network.
  • PCF policy control function
  • the PCF network element of the core network receives the identification information of the first service from the application server, it can initiate a PDU session modification process, and can provide the identification information of the first service to the SMF network element of the core network.
  • the SMF network element of the core network establishes a transmission resource for the first service according to the identification information of the first service, and the transmission resource may be a service QoS flow.
  • 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, public information of the multicast service, and information indicating that the first service is a multicast service.
  • the access network device establishes a first radio bearer with the first terminal device.
  • the access network device 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 the first wireless connection with the first terminal device can be established. Bearer. For specific description, refer to step 401.
  • 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 dispatched to multiple terminal devices, only one of the multiple terminal devices can correctly decrypt the first service, and other terminal devices cannot decrypt the first service. One service, so that the multicast transmission of the multicast service cannot be realized. Or, in order to improve security, when the access network device establishes the first radio bearer for the first terminal device, a public key can be used for the first radio bearer configuration, and the public key is shared by multiple terminal devices receiving the first service. Key.
  • Multiple terminal devices use the public key for decryption when receiving the first service through the first radio bearer.
  • the public key can be used for scheduling regardless of whether the first RNTI or the second RNTI is used.
  • the terminal equipment can use the same public key for decryption no matter which RNTI is used for reception.
  • the public key can be configured by the network device, for example, it can be configured by the access network device or the core network device to the terminal device through the encrypted signaling channel, or it can be derived by the terminal device based on the relevant information of the first service Yes, the related information of the first service may be the service identifier of the first service, the radio bearer identifier of the first service, the second RNTI, or other information related to the first service.
  • the second RNTI corresponding to the first service is 62348, and the terminal device may perform a mask operation on the second RNTI and the first sequence to obtain the second sequence, and the second sequence may be used as the secret key.
  • the first sequence may be configured by the network device to the terminal device, or may be a fixed sequence.
  • the access network device associates the first radio bearer with the first public data channel.
  • the access network device is the first radio bearer and the first public data channel in order to save the overhead of transmitting the first service data between the core network and the access network device.
  • the use of a common data channel prevents the first service data from being repeatedly sent to multiple terminal devices. Without this step, a dedicated data channel is still established between the access network equipment and the core network equipment. In this way, when the terminal equipment receives the first service, for each terminal equipment, there is a different dedicated data channel between the access network equipment and the core network equipment. Data channel. The data of the first service can be sent to the access network equipment on these dedicated channels.
  • the access network device After the access network device determines that the first service is a multicast service according to the service establishment request message, it associates the first radio bearer with the first public data channel.
  • the first public data channel is used for transmission between the access network device and the core network device.
  • the public data channel for the data of the first service.
  • the access network device After the access network device receives the data of the first service from the core network device through the first public data channel, the access network device transmits the received data of the first service to the first terminal device on the first radio bearer. send.
  • the first public data channel can serve all terminal devices that receive the first service.
  • the first public data channel may be established triggered by the access network device, or may be established triggered by the core network device.
  • the access network device triggers the establishment of the first public data channel
  • the public information is the service information of the multicast service.
  • the access network device triggering the establishment of the first public data channel can also be established 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 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.
  • IP Internet Protocol
  • the core network device may initiate a public data channel establishment request carrying the service identifier to the access network device, and the access network device confirms that the establishment of the public data channel is successful.
  • the first public data channel may be 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, the service establishment request message is used to establish the first service In the case of the service establishment request message, the first public data channel can be used directly without establishing. 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 be established before, and the establishment and association are performed at this time. For the establishment process, refer to the above description.
  • the access network device sends the first RNTI to the first terminal device.
  • step 904 is the same as step 402.
  • step 402 which will not be repeated here.
  • the access network device sends the second RNTI to the first terminal device.
  • step 905 is the same as step 403.
  • step 403 which will not be repeated here.
  • the access network device sends configuration information to the first terminal device.
  • the access network device may send configuration information to the first terminal device.
  • the 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.
  • BWP bandwidth part
  • CORESET control resource set
  • search space information corresponding to the second RNTI.
  • the COREST information indicates the time-frequency resource where the G-RNTI PDCCH is located.
  • 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 time.
  • the main parameters of BPW may include bandwidth, frequency location, subcarrier space (SCS), cyclic prefix (CP) length, CORSET-related configuration information, and PDSCH-related configuration information.
  • SCS subcarrier space
  • CP cyclic prefix
  • CORSET-related configuration information CORSET-related configuration information
  • PDSCH-related configuration information For a cell, there will be at least one initial (initial) BWP, and all public information such as broadcasts and paging are sent on the initial BWP.
  • the access network device can configure some dedicated BPW for the terminal device.
  • the first terminal device may determine the SCS, frequency domain position, CP length, etc. corresponding to the BPW according to the BPW.
  • the configuration information may also include the PDSCH scrambling sequence of the first service, so that the first terminal device may use the PDSCH scrambling sequence for descrambling when descrambling the PDSCH of the first service.
  • the configuration information may also include DRX parameters of G-RNTI, so that the first terminal device uses the DRX parameters to perform G-RNTI detection.
  • the configuration signal may also include a demodulation reference signal, so that the first terminal device uses the demodulation reference signal to perform G-RNTI scheduled PDSCH demodulation.
  • the configuration information may also include a rate matching reference signal, so that when the first terminal device receives the PDSCH scheduled by the G-RNTI, the position corresponding to the demodulation reference signal can be excluded.
  • 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 for scheduling the first service.
  • the instruction information may be separately sent by the access network device to the first terminal device, or may be included in the foregoing configuration information and sent together.
  • the indication information may be the association information between G-RNTI and service, such as the relationship between G-RNTI and LCH, the relationship between G-RNTI and DRB, the relationship between G-RNTI and service identity, and so on.
  • the indication information may also be service information associated with the DRB. For example, if the network sets that DRB1 is associated with a multicast service, the terminal device may consider that the G-RNTI is used to receive the data of the DRB1.
  • the configuration information may also include service information associated with the second RNTI, such as logical channel ID, 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, and thus use G-RNTI
  • the sent data does not need to carry the logical channel identifier.
  • the access network device 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.
  • step 907 is similar to step 404.
  • step 404 please refer to step 404, which will not be repeated here.
  • the first terminal device can detect the data packet of the first service from the access network device from the second RNTI on the first radio bearer according to the configuration information.
  • the data packet of the first service may include a logical channel identifier, and the logical channel identifier may indicate the second
  • the data packet transmitted by RNTI is the data packet of the first service.
  • the terminal equipment 1 feeds back the NACK, and the access network equipment can use the C-RNTI to perform retransmission scheduling.
  • the G-RNTI can continue to schedule new data to ensure that the terminal device 1 and other terminal devices that receive data correctly can continue to receive new data.
  • the terminal device 1 that has not received the data correctly can use the C-RNTI to perform the retransmission reception, which ensures the retransmission of the data of the terminal device 1 without affecting the reception of new data from other terminal devices.
  • HARQ hybrid automatic repeat request
  • G-RNTI schedules process No. 8, and all terminal equipment using this G-RNTI uses process 8. If terminal equipment 1 retransmits a data packet scheduled by G-RNTI, it cannot Use process 8 and you need to replace a process, such as process 6. However, after the process is replaced, the terminal device cannot determine that the replaced process No. 6 is used to schedule the retransmission of the No. 8 process. Therefore, the access network device needs to notify the terminal device of the relationship between the No.
  • the access network device can send the first process and the first RNTI to the first terminal device.
  • the first process is a process for initially transmitting a data packet of the first service
  • the second process is a process for retransmitting a data packet of the first service.
  • the access network device may configure the association relationship between the first process and the second process through RRC.
  • the association relationship between process 6 and process 8, that is, process 6 can be configured to retransmit data of process 8, and then when process 6 is scheduled, the terminal equipment can be indicated in the scheduling command, such as DCI
  • the retransmission of the current process No. 6 is a retransmission for the associated process.
  • the DCI can use 1 bit to indicate that the current retransmission is a retransmission for the associated process.
  • the access network device may also indicate in the scheduling command that the retransmission of the current process of the terminal device is associated with process No. 8.
  • the scheduling command can indicate that the retransmission of the current process of the terminal device is associated with process No. 8.
  • 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 sent to the first terminal device when the data packet of the first service needs to be retransmitted later. Of the first terminal device.
  • FIG. 10 is a schematic diagram of scheduling data using G-RNTI according to an embodiment of the present invention.
  • the service data currently sent to the access network device includes three data packets: data 1, data 2, and data 3.
  • terminal device 1 and terminal device 2 respectively use C-RNTI for scheduling. Both terminal device 1 and terminal device 2 have already transmitted part of data 1 and data 2, but the rest of data 2 is different.
  • G-RNTI needs to start scheduling from data 3, and the remaining part of data 2 requires terminal equipment 1 and terminal equipment 2 to continue scheduling using their respective C-RNTIs.
  • FIG. 11 is a schematic flowchart of another communication method disclosed in an embodiment of the present invention. As shown in FIG. 11, the communication method may include the following steps.
  • 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.
  • the access network device may 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 whether to use the second RNTI to schedule the first service in the first cell based on the number of received first services in the cell covered by the access network device in real time or periodically, and then send it to the resource management module
  • the first configuration information, the first configuration information may include BWP information corresponding to the second RNTI, CORESET information corresponding to the second RNTI, search space information corresponding to the second RNTI, PDSCH scrambling sequence of the first service, demodulation reference signal, One or more of G-RNTI DRX parameters, rate matching reference signals, etc.
  • 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 G-RNTI and/or scheduling resources used among multiple cells or multiple access network devices.
  • the resource management module sends second configuration information corresponding to the first service to the access network device.
  • the resource management module After the resource management module receives the indication information from the access network equipment for indicating the number of receiving terminal equipment for the first service, it can be determined according to the indication information that multiple cells can use the second RNTI to schedule the first service, and can provide access
  • the network device sends second configuration information corresponding to the first service.
  • the second configuration information includes configuration information of the second RNTI.
  • the resource management module After receiving the first configuration information from multiple access network devices, the resource management module unifies the second RNTI used by the multiple cells when the services of multiple cells are the first service, and then can access The network device sends second configuration information corresponding to the first service.
  • the second configuration information includes unified second RNTI transmission resource configuration information.
  • the transmission resource may include BWP information corresponding to the second RNTI, CORESET information corresponding to the second RNTI, search space information corresponding to the second RNTI, PDSCH scrambling sequence of the first service, demodulation reference signal, DRX parameters of G-RNTI , One or more of the rate matching reference signal, etc.
  • the second RNTI and transmission resources of the second cell may 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.
  • the same signal formed by the air interface resources can form a signal superimposition effect when multiple cells are transmitted, thereby enhancing the reception effect of the first service.
  • the core network device sends a service establishment request message to the access network device.
  • step 1103 is the same as step 901.
  • step 901 which will not be repeated here.
  • the access network device establishes a first radio bearer with the first terminal device.
  • step 1104 is the same as step 902.
  • step 902 which will not be repeated here.
  • the access network device associates the first radio bearer with the first public data channel.
  • step 1105 is the same as step 903.
  • step 903 which will not be repeated here.
  • the access network device sends the first RNTI to the first terminal device.
  • step 1106 is the same as step 402.
  • step 402 which will not be repeated here.
  • the access network device sends the second RNTI to the first terminal device.
  • step 1107 is the same as step 403.
  • the second RNTI may be allocated by the access network device according to the second configuration information.
  • the access network device sends configuration information including second configuration information to the first terminal device.
  • step 1108 is similar to step 906.
  • step 906 which will not be repeated here.
  • the access network device 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.
  • step 1109 is the same as step 907.
  • step 907 please refer to step 907, which will not be repeated here.
  • FIG. 16 is a schematic flowchart of another communication method disclosed in an embodiment of the present invention. As shown in FIG. 16, the communication method may include the following steps.
  • 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.
  • the core network device may send the association relationship between the first terminal device and the data of the first service to the access network device when there is the data of the first service to be sent by the first terminal device.
  • the first service may be a multicast service
  • 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 (that is, the first service).
  • the core network device may receive the PDU session establishment/modification request from the first terminal device, and then may establish the first QoS flow for the first terminal device to receive data of the first service. Then, the association relationship between the first terminal device and the data of the first service can be sent to the access network device.
  • the core network device may receive a message from the application server for establishing a QoS flow for the first terminal device to receive the data of the first service, and then may establish the first terminal device for the first terminal device to receive the data of the first service. QoS flow. Then, the association relationship between the first terminal device and the data of the first service can be sent to the access network device.
  • the association relationship between the first terminal device and the data of the first service may include the association relationship between the identity of the first QoS flow of the first terminal device and the identity of the public QoS flow, and the public QoS flow is used to transmit the first QoS flow.
  • the QoS flow of service data, the first QoS flow of the first terminal device is a QoS flow used by the first terminal device to receive the data of the first service. Refer to Table 2 for the association relationship between the identification of the first QoS flow of a group of terminal devices and the identification of the public QoS flow, where each row represents the relationship between the identification of the first QoS flow of a terminal device and the identification of the public QoS flow Relationship.
  • Identification of terminal equipment The identification of the first QoS flow of the terminal device Identification of public QoS flow UE1 QFI_1-1 QFI-C1 UE2 QFI_1-2 QFI-C1 UE3 QFI_1-3 QFI-C1 ... ... ... ...
  • 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
  • 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
  • QFI-C1 is the identifier of the public QoS flow used to transmit data of the first service.
  • the association relationship between the identification of the first QoS flow of the terminal device and the identification of the public QoS flow can also refer to Table 3.
  • the association relationship between the first terminal device and the data of the first service may further include tunnel identification information corresponding to the first QoS flow of the first terminal device, and/or tunnel identification information corresponding to the public QoS flow.
  • the tunnel identification information may be core network side tunnel information, and/or access network side tunnel information.
  • 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.
  • 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 first QoS flow of the second terminal device.
  • the first terminal device The first QoS flow is the QoS flow used by the first terminal device to receive the data of the first service
  • the first QoS flow of the second terminal device is used to transmit the data of the first service
  • the second terminal device is the group of terminal devices Any terminal device except the first terminal device.
  • UE1, UE2, and UE3 are the identities of the terminal devices
  • QFI_1-1 is the identity of the first QoS flow of the terminal device corresponding to UE1
  • QFI_1-2 is the identity of the first QoS flow of the terminal device corresponding to UE2
  • QFI_1-3 is the identification of the first QoS flow of the terminal device corresponding to UE3. It can be seen that the identification of the first QoS flow of the terminal device corresponding to UE2 is QFI_1-2 and the identification of the first QoS flow of the terminal device corresponding to UE1 QFI_1- There is an association relationship between the identifiers QFI_1-3 of the first QoS flow of the terminal devices corresponding to 1 and UE3.
  • the QoS flow identification QFI_1-2 of the terminal device corresponding to UE2 is associated with the QoS flow identification QFI_1-1 of the terminal device corresponding to UE1 and the QoS flow identification QFI_1-3 of the terminal device corresponding to UE3. relationship.
  • 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, and/or the first QoS flow of the second terminal device Corresponding tunnel identification information.
  • the tunnel identification information may be core network side tunnel information, and/or access network side tunnel information.
  • 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 first QoS flow corresponding to the second terminal device The session identification information.
  • Identification of terminal equipment The identification of the first QoS flow of the terminal device UE1 QFI_1-1 QFI_1-2 UE2 QFI_1-2 QFI_1-2 (optional) UE3 QFI_1-3 QFI_1-2 ... ... ...
  • the identity of the first QoS flow of the second terminal device Identification of the first QoS flow of other terminal equipment QFI_1-2 QFI_1-1 QFI_1-2 (optional) QFI_1-3 ... ...
  • 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 index information of the data of the first service.
  • the QoS flow can 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 the same type of data.
  • the index information of the data of the first service may be the 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.
  • UE1, UE2, and UE3 are the identities of the terminal devices
  • QFI_1-1 is the identity 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 UE2
  • QFI_1-3 is the identifier of the QoS flow of the terminal device corresponding to UE3.
  • the index value Index1 of the data of the first service corresponds to the first QoS flow identifier QFI_1-1 of the terminal device corresponding to UE1, the first QoS flow identifier QFI_1-2 of the terminal device corresponding to UE2, and UE3 corresponds to The identifier QFI_1-3 of the first QoS flow of the terminal device.
  • 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, where the tunnel identification information may be core network side tunnel information , And/or, access network side tunnel information.
  • 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 terminal device and the first service.
  • Identification of terminal equipment The identification 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 ... ...
  • Index value of the first business data Identification of the QoS flow of the terminal device Index1 QFI_1-1 QFI_1-2 (optional) QFI_1-3 ... ...
  • Table 7 The association relationship between the QoS flow identifier of the terminal device and the index information of the data of the first service
  • the access network device may obtain the association relationship between the first terminal device and the data of the first service from the core network device, and further, may generate a group of terminal devices according to the association relationship between the first terminal device and the data of the first service
  • the association relationship with the data of the first service is used for the access network device to schedule the data packets of the first service.
  • the access network device can also directly obtain the association relationship between a group of terminal devices and the data of the first service from the core network device. For details, refer to Table 2 to Table 7.
  • the association relationship between the first terminal device and the data of the first service may include the identifier of the second QoS flow of the first terminal device and the first terminal device of at least one other terminal device in the group of terminal devices.
  • the relationship between the two QoS flow identifiers, the second QoS flow of the other at least one 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 may be used for the first A terminal device receives 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 refer to Table 8 to Table 11.
  • UE1 is the identifier of the first terminal device
  • QFI_2-1 is the identifier of the second QoS flow of the first terminal device
  • 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.
  • UE3 is the identity of the third terminal device, the identity of the second QoS flow of the third terminal device QFI_2-3 and the identity of the second QoS flow of the first terminal device QFI_2-1 and the identity of the second terminal device
  • UE4 is the identity of the fourth terminal device, the identity of the second QoS flow of the fourth terminal device QFI_2-4 and the identity of the second QoS flow of the first terminal device QFI_2-1, the identity of the second 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.
  • 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 second QoS flow of the first terminal.
  • the tunnel identification information may be core network side tunnel information, and/or access network side tunnel information.
  • 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 first terminal device and the first terminal device. Session identification information corresponding to the service.
  • 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 by the SMF network element to the access network device through the AMF network element, or can be placed in other SMFs sent to the access network.
  • the message or container of the device can be carried in the N2 session management information sent by the SMF network element to the access network device through the AMF network element, or can be placed in other SMFs sent to the access network.
  • the access network device establishes a first radio bearer with the first terminal device.
  • the access network device 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 there is data of the first service that needs to be transmitted between the access network device and the first terminal device, The first radio bearer can be established with the first terminal device. For a specific description, 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 through a PDU session resource setup request (session resource setup request).
  • the access network device associates the first radio bearer with a QoS flow used to transmit data of the first service.
  • the access network device After the access network device has established the first radio bearer with the first terminal device, it may determine, according to the association relationship obtained from the core network, that it is necessary to transmit the QoS flow from the data used to transmit the first service on the first radio bearer
  • the data of the first service received on the QoS stream used to transmit the data of the first service is the data of the first service.
  • the QoS flow used to transmit the data of the first service may be the public QoS flow in step 1601 or the first QoS flow of the second terminal device.
  • the access network device may select one of the first QoS flows in the group of terminal devices for transmission. Among them, step 1603 is an optional step.
  • the access network device sends the first RNTI to the first terminal device.
  • step 904 please refer to step 904, which will not be repeated here.
  • the access network device sends the second RNTI to the first terminal device.
  • the access network device sends the second RNTI to the first terminal device according to the association relationship.
  • step 905 please refer to step 905, which will not be repeated here.
  • the access network device sends configuration information to the first terminal device.
  • step 906 please refer to step 906, which will not be repeated here.
  • the access network device 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.
  • step 907 please refer to step 907, which will not be repeated here.
  • FIG. 17 is a schematic flowchart of another communication method disclosed in an embodiment of the present invention. As shown in FIG. 17, the communication method may include the following steps.
  • the core network device sends a session establishment request message for establishing a first QoS flow of the first terminal to the access network device.
  • the core network device may send a session establishment request message for establishing the first QoS flow of the first terminal to the access network device.
  • the session establishment request message may be carried in messages such as an initial context establishment message, a PDU session establishment message, and a context modification message.
  • the session establishment request message may indicate that the first QoS flow of the first terminal device bears the data of the multicast service.
  • the session establishment request message may carry indication information used to indicate that the first QoS flow of the first terminal device carries data of the multicast service. That is, in the case of carrying indication information for indicating that the first QoS flow of the first terminal device carries the data of the multicast service, the session establishment request message is to establish the first QoS flow carrying the data of the multicast service. In the case of the indication information used to indicate that the first QoS flow of the first terminal device carries the data of the multicast service, the session establishment request message is to establish the first QoS flow carrying the data of the unicast service.
  • the session establishment request message may directly indicate that the first QoS flow of the first terminal device carries data of the multicast service. That is, in the case that the session establishment request message indicates that the first QoS flow of the first terminal device carries the data of the multicast service, the first QoS flow that carries the data of the multicast service to be established by the session establishment request message, in the session establishment request In the case that the message does not indicate that the first QoS flow carries the data of the multicast service, the session establishment request message is to establish the first QoS flow carrying the data of the unicast service.
  • the core network device may receive the data for establishing and receiving the first service from the first terminal device. Session establishment request for the first QoS flow.
  • the session establishment request message may also carry address information for the access network device to receive the data of the first service, such as the IP address of the access network device, tunnel identification information, and a certain terminal device in the group of terminal devices. N3 tunnel identification information or a public N3 tunnel identification information of the access network device.
  • the address information is used by the access network device to establish the first QoS flow of the first terminal device for the first terminal device. For other detailed descriptions, refer to step 901.
  • the access network device establishes a first radio bearer with the first terminal device.
  • the access network device After the access network device receives the session establishment request message for establishing the first QoS flow of the first terminal device from the core network device, it indicates that the data to be transmitted between the access network device and the first terminal device is a multicast service
  • the data of the multicast service is the data of the first service, and the first radio bearer with the first terminal device can be established.
  • the access network device After the access network device receives the session establishment request message for establishing the first QoS flow of the first terminal device from the core network device, it indicates that the data to be transmitted between the access network device and the first terminal device is a multicast service
  • the data of the multicast service is the data of the first service, and the first radio bearer with the first terminal device can be established.
  • the data of the multicast service may be scheduled to multiple terminal devices through G-RNTI. Therefore, the access network device may not start encryption for the first radio bearer established by the first terminal device. Since different terminal devices have different encryption keys, once the data of the multicast service is encrypted and dispatched to multiple terminal devices, only one of the multiple terminal devices can correctly decrypt the multicast data, and other terminal devices The multicast data cannot be decrypted, so that the multicast transmission of the data of the multicast service cannot be realized.
  • the access network device associates the first radio bearer with the first QoS flow used to transmit data of the first service.
  • the access network device After the access network device establishes the first radio bearer with the first terminal device, it can associate the first radio bearer with the first QoS flow used to transmit the data of the first service, which can save core network equipment and access network equipment.
  • the data overhead of the first service is transmitted between.
  • using one N3QoS flow can avoid multiple terminal devices from repeatedly sending the data of the first service to the same access network device.
  • the N3QoS flow may be a public QoS flow, or may be the first QoS flow of one terminal device in the group of terminal devices.
  • the first QoS flow used for transmitting the data of the first service may be the public QoS flow described in step 1601 or the first QoS flow of the second terminal device.
  • the access network device may select one of the first QoS flows of the group of terminal devices for transmission. Without this step, the access network device can still establish a dedicated data channel with the core network device. In this way, when the terminal device receives the data of the first service, for each terminal device, between the access network device and the core network device There are different dedicated data channels with terminal equipment. The data of the first service can be sent to the access network equipment on these dedicated channels. Among them, step 1703 is an optional step.
  • the access network device sends the first RNTI to the first terminal device.
  • step 904 please refer to step 904, which will not be repeated here.
  • the access network device sends the second RNTI to the first terminal device.
  • the access network device sends the second RNTI to the first terminal device according to the association relationship.
  • step 905 please refer to step 905, which will not be repeated here.
  • the access network device sends configuration information to the first terminal device.
  • step 906 please refer to step 906, which will not be repeated here.
  • the access network device 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.
  • step 907 please refer to step 907, which will not be repeated here.
  • FIG. 12 is a schematic structural diagram 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.
  • the communication device may include:
  • the establishment 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;
  • the allocation unit 1202 is configured to allocate a first RNTI and a second RNTI to a first terminal device, the first RNTI is used to schedule services to the first terminal device, and the second RNTI is used to schedule a group of terminal devices including the first terminal device First business
  • the sending unit 1203 is configured to use 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.
  • the communication device may further include:
  • 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 used to indicate that the first service is a multicast service.
  • the public information is service information or address information of a multicast service.
  • the communication device may further include:
  • the association unit 1205 is configured to associate the first radio bearer with the first public data channel, and the first public data channel is used to transmit data of the first service with the core network device.
  • the sending unit 1203 is specifically configured to:
  • the first RNTI is used to retransmit the data packet of the first service to the first terminal device on the first radio bearer.
  • the sending unit 1203 is further configured to send the association relationship between the first process and the second process to the first terminal device.
  • the first process is a process for initially transmitting data packets of the first service.
  • the second process is a process for retransmitting the data packet of the first service.
  • the sending unit 1203 is further configured to send indication information to the first terminal device, where the indication information is used to indicate that the second RNTI is used for scheduling the first service.
  • 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 a data packet of the first service.
  • the sending unit 1203 is further configured 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.
  • the first configuration information includes one or more of the following:
  • the sending unit 1203 is further configured 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 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;
  • the sending unit 1203 is further configured to send second configuration information to the first terminal device.
  • FIG. 13 is a schematic structural 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 a terminal device.
  • the communication device may include:
  • the establishment 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;
  • the receiving unit 1302 is configured to receive the first RNTI and the second RNTI from the access network device, the first RNTI is used to receive the service scheduled from the access network device to the terminal device, and the second RNTI is used to receive the service from the access network device The first service scheduled to a group of terminal devices including the terminal device;
  • the receiving unit 1302 is further configured to use the first RNTI and the second RNTI to receive a data packet of the first service scheduled by the access network device on the first radio bearer.
  • the receiving unit 1302 using the first RNTI and the second RNTI to receive a data packet from the first service scheduled by the access network device on the first radio bearer includes:
  • the receiving unit 1302 is further configured to receive the association relationship between the first process and the second process from the access network device, the first process is a process for initially transmitting data packets of the first service, The second process is a process for retransmitting the data packet of the first service;
  • the receiving unit 1302 using the first RNTI to receive the data packet of the first service retransmitted from the access network device on the first radio bearer includes:
  • the first RNTI is used to receive the data packet of the first service retransmitted from the access network device on the first radio bearer.
  • the communication device may further include a determining unit 1303, wherein:
  • 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 that the second RNTI is used for scheduling the first service according to the first indication information;
  • the determining unit 1303 is configured to determine that the data packet transmitted by the second RNTI is the data packet of the first service according to the logical channel identifier included in the data packet of the first service.
  • the receiving unit 1302 is further configured to receive configuration information from the access network device
  • the receiving unit 1302 using the second RNTI to receive the data packet of the first service scheduled from the access network device on the first radio bearer includes:
  • the data packet of the first service from the access network device is detected from the second RNTI on the first radio bearer according to the configuration information.
  • the configuration information includes one or more of the following:
  • the receiving unit 1302 is further configured to receive second indication information from the access network device
  • the determining unit 1303 is further configured to determine, according to the second indication information, that the first radio bearer is a radio bearer used to transmit the first service.
  • the receiving unit 1302 using the first RNTI and the second RNTI to receive the data packet of the first service from the access network device on the first radio bearer includes:
  • the first data packet and the second data packet are combined on the first radio bearer.
  • the receiving unit 1302 combining the first data packet and the second data packet onto the first radio bearer includes:
  • the RLC PDUs included in the first data packet and the second data packet are merged onto the first radio bearer at the RLC layer;
  • the PDCP PDUs included in the first data packet and the second data packet are combined onto the first radio bearer at the PDCP layer.
  • the receiving unit 1302 merging the RLC PDU 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 sequenced and/or duplicated.
  • the receiving unit 1302 merging the RLC PDU 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 sequenced and/or duplicated.
  • FIG. 14 is a schematic structural diagram of another communication device disclosed in an embodiment of the present invention.
  • 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 exist independently, and may be connected to the processor 1401 through the bus 1405.
  • the memory 1402 may also be integrated with the processor 1401. Among them, the bus 1405 is used to realize the connection between these components.
  • the communication device may be an access network device or a chip in the access network device, where:
  • a group of computer programs are stored in the memory 1402, and the processor 1401 is configured to call the computer programs stored in the memory 1402 to perform the following operations:
  • Allocate a first RNTI and a second RNTI to the first terminal device 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 output interface 1404 is configured 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.
  • the input interface 1403 is used to receive a service establishment request message from a core network device, and the service establishment request message carries public information used to indicate that the first service is a multicast service.
  • the public information is service information or address information of a multicast service.
  • the processor 1401 is further configured to call a computer program stored in the memory 1402 to perform the following operations:
  • the first radio bearer is associated with the first public data channel, and the first public data channel is used to transmit data of the first service with the core network device.
  • the output interface 1404 using 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 includes:
  • the output interface 1404 uses the second RNTI to schedule data packets of the first service to the first terminal device on the first radio bearer;
  • the input interface 1403 receives feedback information from the first terminal device for indicating that the data packet transmission of the first service fails;
  • 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.
  • the output interface 1404 is also used to send the association relationship between the first process and the second process to the first terminal device.
  • the first process is a process for initially transmitting data packets of the first service.
  • the second process is a process for retransmitting the data packet of the first service.
  • the output interface 1404 is also used to send indication information to the first terminal device, and the indication information is used to indicate that the second RNTI is used to schedule the first service.
  • 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 a data packet of the first service.
  • the output interface 1404 is also used to send first configuration information 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.
  • the first configuration information includes one or more of the following:
  • the output interface 1404 is also 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 input interface 1403 is also used 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 output interface 1404 is also used to send second configuration information to the first terminal device.
  • step 401, step 902-step 903, and step 1104-step 1105 can be executed by the processor 1401 and the memory 1402 in the access network device; the step of receiving the service establishment request message in step 901 and step 1103, step 1102
  • the step of receiving the second configuration information can be performed by the input interface 1403 in the access network device;
  • step 402-step 404, step 904-step 907, and step 1106-step 1109 can be performed by the output interface 1404 in the access network device.
  • 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
  • the sending unit 1203 It can be implemented by the output interface 1404 in the access network device.
  • the above-mentioned access network device may also be used to execute various methods executed by the access network device in the foregoing method embodiments, and details are not described herein again.
  • the communication device may be a terminal device or a chip in the terminal device, where:
  • a group of computer programs are stored in the memory 1402, and the processor 1401 is configured to call the computer programs stored in the memory 1402 to perform the following operations:
  • the input interface 1403 is used to receive the first RNTI and the second RNTI from the access network device, the first RNTI is used to receive the service scheduled from the access network device to the terminal device, and the second RNTI is used to receive the service from the access network device
  • the input interface 1403 is also configured to 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 radio bearer.
  • the input interface 1403 using the first RNTI and the second RNTI to receive a data packet from the first service scheduled by the access network device on the first radio bearer includes:
  • the input interface 1403 uses the second RNTI to receive a data packet from the first service scheduled by the access network device on the first radio bearer;
  • the output interface 1404 sends feedback information used to indicate failure of transmission of the data packet of the first service to the access network device;
  • the input interface 1403 uses the first RNTI to receive the data packet of the first service retransmitted from the access network device on the first radio bearer.
  • the input interface 1403 is also used to receive the association relationship between the first process and the second process from the access network device.
  • the first process is a process for initially transmitting data packets of the first service.
  • the second process is a process for retransmitting the data packet of the first service;
  • the input interface 1403 using the first RNTI to receive the data packet of the first service retransmitted from the access network device on the first radio bearer includes:
  • the first RNTI is used to receive the data packet of the first service retransmitted from the access network device on the first radio bearer.
  • the input interface 1403 is also used to receive first indication information from the access network device
  • the processor 1401 is further configured to call a computer program stored in the memory 1402 to perform the following operations:
  • the processor 1401 is further configured to call a computer program stored in the memory 1402 to perform the following operations:
  • the data packet transmitted by the second RNTI is determined to be the data packet of the first service according to the logical channel identifier included in the data packet of the first service.
  • the input interface 1403 is also used to receive configuration information from the access network device
  • the input interface 1403 using the second RNTI to receive the data packet of the first service scheduled from the access network device on the first radio bearer includes:
  • the data packet of the first service from the access network device is detected from the second RNTI on the first radio bearer according to the configuration information.
  • the configuration information includes one or more of the following:
  • the input interface 1403 is also used to receive second indication information from the access network device
  • the processor 1401 is further configured to call a computer program stored in the memory 1402 to perform the following operations:
  • the first radio bearer is a radio bearer used to transmit the first service.
  • the input interface 1403 using the first RNTI and the second RNTI to receive the data packet of the first service from the access network device on the first radio bearer includes:
  • the input interface 1403 uses the first RNTI to receive the first data packet of the first service from the access network device;
  • the input interface 1403 uses the second RNTI to receive the second data packet of the first service from the access network device;
  • the processor 1401 merges the first data packet and the second data packet onto the first radio bearer.
  • the processor 1401 combining the first data packet and the second data packet onto the first radio bearer includes:
  • the RLC PDUs included in the first data packet and the second data packet are merged onto the first radio bearer at the RLC layer;
  • the PDCP PDUs included in the first data packet and the second data packet are combined onto the first radio bearer at the PDCP layer.
  • the processor 1401 merging the RLC PDU 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 sequenced and/or duplicated.
  • the processor 1401 merging the PDCP PDU 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 and the PDCP PDU included in the second data packet are sequenced and/or duplicated.
  • step of receiving the first RNTI in step 402, step 904 and step 1106, the step of receiving the second RNTI in step 403, step 905 and step 1107, the step of receiving the data packet of the first service in step 404, step 907 and step 1109 The steps of receiving configuration information in step 906 and step 1108 can be performed by the input interface 1303 in the terminal device.
  • 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.
  • the foregoing terminal device may also be used to execute various methods executed by the terminal device in the foregoing method embodiments, and details are not described herein again.
  • FIG. 15 is a schematic structural diagram of another communication device disclosed in an embodiment of the present invention.
  • 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 a 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, for example, to implement the functions implemented by the processor 1401 in the foregoing embodiment.
  • the communication device can be an access network device or a chip in an access network device, or a terminal device or a chip in a terminal device.
  • the input interface 1501, the logic circuit 1502, and the output interface 1503 can be directly obtained by referring to the relevant description of the access network device or the terminal device in the method embodiments shown in FIG. 4, FIG. 9 and FIG. 11. , Do not repeat them here.
  • the embodiment of the present invention also discloses a computer-readable storage medium with a computer program stored on the computer-readable storage medium, and when the computer program runs, the communication method shown in FIG. 4, FIG. 9 and FIG. 11 is implemented.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明实施例公开一种通信方法及装置，包括：为第一终端设备建立第一无线承载，第一无线承载用于传输第一业务；为第一终端设备分配第一RNTI和第二RNTI，第一RNTI用于向第一终端设备调度业务，第二RNTI用于向包括第一终端设备的一组终端设备调度第一业务；使用第一RNTI和第二RNTI在第一无线承载上向第一终端设备调度第一业务的数据包。实施本发明实施例，可以提高通信效率。

Description

一种通信方法及装置
本申请要求于2019年07月31日提交中国专利局、申请号为201910704742.5、申请名称为“一种通信方法及装置”的中国专利申请的优先权，以及要求于2019年09月12日提交中国专利局、申请号为201910866760.3、申请名称为“一种通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明实施例涉及通信技术领域，尤其涉及一种通信方法及装置。
背景技术
多播技术是一种点到多点的通信技术。目前，在传输某一个多播业务时，针对同一小区的终端设备，可以使用同一个组无线网络临时标识(group radio network temporary identity，G-RNTI)进行传输。然而，在某个终端设备的接收信号不好的情况下，这个终端设备需要建立单播承载，以便可以通过单播承载来接收这个业务，但终端设备在多播与单播之间的转换可能产生中断，以致终端设备无法接收信息，降低了通信效率。
发明内容
本发明实施例公开了一种通信方法及装置，用于提高通信效率。
第一方面公开一种通信方法，为第一终端设备建立用于传输第一业务的第一无线承载，为第一终端设备分配第一无线网络临时标识(radio network temporary identity，RNTI)和第二RNTI，使用第一RNTI和第二RNTI在第一无线承载上向第一终端设备调度第一业务的数据包。第一RNTI用于向第一终端设备调度业务，第二RNTI用于向包括第一终端设备的一组终端设备调度第一业务。由于为终端设备同时分配了调度单播业务的RNTI和调度多播业务的RNTI用于调度来自同一无线承载的数据，因此，终端设备在多播与单播之间的转换时，不会导致无线承载变更，因此，不会产生中断，从而可以提高通信效率。
作为一种可能的实现方式，接收来自核心网设备的业务建立请求消息，业务建立请求消息携带用于指示第一业务为多播业务的公共信息。可见，可以通过公共信息确定业务为多播业务，可以提高业务类型的确定效率。
作为一种可能的实现方式，公共信息可以为多播业务的业务信息，也可以为地址信息。
作为一种可能的实现方式，可以关联第一无线承载与第一公共数据通道，第一公共数据通道用于与核心网设备传输第一业务的数据，以便多个终端设备都接收第一业务时，核心网设备可以通过第一公共数据通道传输第一业务的数据，而不需要为不同的终端设备分别建立专用数据通道，从而可以避免同一份数据在多个专用数据通道上重复发送。
作为一种可能的实现方式，可以使用第二RNTI在第一无线承载上向第一终端设备调度第一业务的数据包，接收来自第一终端设备的用于指示第一业务的数据包传输失败的反馈信息，使用第一RNTI在第一无线承载上向第一终端设备重传第一业务的数据包。可以使用第二RNTI新传数据，使用第一RNTI重传传输失败的数据，可见，传输失败的数据的重传并 不会影响第二RNTI上新数据的传输，从而可以提高通信效率。
作为一种可能的实现方式，可以向第一终端设备发送第一进程与第二进程之间的关联关系，第一进程为用于初传第一业务的数据包的进程，第二进程为用于重传第一业务的数据包的进程。可以根据关联关系将使用不同RNTI新传或重传的数据关联起来，以便能够对接收的数据进行正确处理，从而可以提高数据处理效率。
作为一种可能的实现方式，可以向第一终端设备发送指示信息，该指示信息可以指示第二RNTI用于调度第一业务，以便第一终端设备能够快速地确定第二RNTI用于传输哪个业务。
作为一种可能的实现方式，第一业务的数据包可以包括逻辑信道标识，逻辑信道标识用于指示第二RNTI传输的数据包为第一业务的数据包，可见，不需要额外传输信息，只需要通过数据包就可以确定数据包对应的业务，从而可以节约资源。
作为一种可能的实现方式，可以向第一终端设备发送第一配置信息，第一配置信息用于指示第一终端设备根据第一配置信息检测第二RNTI，以便终端设备可以根据配置信息快速地检测到第二RNTI，从而可以提高通信效率。
作为一种可能的实现方式，第一配置信息可以包括第二RNTI对应的带宽部分(bandwitch part，BWP)信息、第二RNTI对应的控制资源集(control resource set，CORESET)信息以及第二RNTI对应的搜索空间信息中的一种或多种。
作为一种可能的实现方式，可以向资源管理模块发送用于指示第一业务的接收终端设备的数量的指示信息和/或第一业务使用的RNTI的配置信息，接收来自资源管理模块的第一业务对应的包括第二RNTI的配置信息的第二配置信息，向第一终端设备发送第二配置信息。可见，可以通过资源管理模块使多个小区或多个接入网设备对应的终端设备中传输第一业务的终端设备使用同一个RNTI或者相同的第二配置信息，使得一个区域内多播传输采用相同的资源，增强接收信号质量，减少移动带来的业务中断。
作为一种可能的实施方式，可以接收来自核心网设备的第一终端设备与第一业务的数据之间的关联关系。第一终端设备为该一组终端设备中的任一终端设备。该关联关系可以包括以下中的至少一种：第一终端设备的服务质量(quality of service，QoS)流(flow)的标识与公共QoS流的标识之间的关联关系，公共QoS流用于传输第一业务的数据；第一终端设备的QoS流的标识与第二终端设备的QoS流的标识之间的关联关系，第二终端设备的QoS流用于传输第一业务的数据，第二终端设备为该一组终端设备中除第一终端设备之外的终端设备；第一终端设备的QoS流的标识与第一业务的数据的索引信息之间的关联关系。可见，可以通过关联关系确定哪些终端设备接收第一业务的数据，以便可以对这些终端设备分配同样的第二RNTI。
作为一种可能的实施方式，接收来自核心网设备的用于建立第一终端设备的QoS流的会话建立请求消息。会话建立请求消息用于指示第一终端设备的QoS流用于承载多播业务的数据。可见，可以通过会话建立请求消息确定第一终端设备的QoS流承载的业务为多播业务，可以提高业务类型的确定效率。
第二方面公开一种通信装置，可以建立与接入网设备之间的用于传输第一业务的第一 无线承载，接收来自接入网设备的第一RNTI和第二RNTI，使用第一RNTI和第二RNTI在第一无线承载上接收来自接入网设备调度的第一业务的数据包。第一RNTI用于接收来自接入网设备向终端设备调度的业务，第二RNTI用于接收来自接入网设备向包括终端设备的一组终端设备调度的第一业务。由于终端设备可同时使用调度单播业务的RNTI和调度多播业务的RNTI接收来自于同一无线承载的业务，因此，终端设备在多播与单播之间的转换时，不会导致无线承载变更，因此，不会产生中断，从而可以提高通信效率。
作为一种可能的实现方式，可以使用第二RNTI在第一无线承载上接收来自接入网设备调度的第一业务的数据包，向接入网设备发送用于指示第一业务的数据包传输失败的反馈信息，使用第一RNTI在第一无线承载上接收来自接入网设备重传的第一业务的数据包。可以使用第二RNTI新传数据，使用第一RNTI重传传输失败的数据，可见，传输失败的数据的重传并不会影响第二RNTI上新数据的传输，从而可以提高通信效率。
作为一种可能的实现方式，可以接收来自接入网设备的第一进程与第二进程之间的关联关系，根据关联关系使用第一RNTI在第一无线承载上接收来自接入网设备重传的第一业务的数据包。其中，第一进程为用于初传第一业务的数据包的进程，第二进程为用于重传第一业务的数据包的进程。可以根据关联关系将使用不同RNTI新传或重传的数据关联起来，以便能够对接收的数据进行正确处理，从而可以提高数据处理效率。
作为一种可能的实现方式，可以接收来自接入网设备的第一指示信息，根据第一指示信息确定第二RNTI用于调度第一业务，以便第一终端设备能够快速地确定第二RNTI用于传输哪个业务。
作为一种可能的实现方式，可以根据第一业务的数据包包括的逻辑信道标识确定第二RNTI传输的数据包为第一业务的数据包，可见，不需要额外传输信息，只需要通过数据包就可以确定数据包对应的业务，从而可以节约资源。
作为一种可能的实现方式，可以接收来自接入网设备的配置信息，根据配置信息在第一无线承载上从第二RNTI上检测来自接入网设备的第一业务的数据包，以便终端设备可以根据配置信息快速地检测到第二RNTI，从而可以提高通信效率。
作为一种可能的实现方式，第一配置信息可以包括第二RNTI对应的BWP信息、第二RNTI对应的CORESET信息以及第二RNTI对应的搜索空间信息中的一种或多种。
作为一种可能的实现方式，可以接收来自接入网设备的第二指示信息，根据第二指示信息确定第一无线承载为用于传输第一业务的无线承载，以便终端设备可以根据第二指示信息快速地确定第一无线承载传输的业务为哪个业务，从而可以提高通信效率。
作为一种可能的实现方式，可以使用第一RNTI接收来自接入网设备的第一业务的第一数据包，使用第二RNTI接收来自接入网设备的第一业务的第二数据包，之后将第一数据包和第二数据包合并到第一无线承载上，可见，可以由第一RNTI和第二RNTI共同传输同一业务的不同数据包，之后进行合并，可以提高数据传输效率。
作为一种可能的实现方式，在第一数据包和第二数据包为媒体访问控制(media Access control address，MAC)MAC层的数据包的情况下，可以将第一数据包和第二数据包包括的无线链路控制(radio link control，RLC)协议数据单元(protocol data unit，PDU)在RLC层合并到第一无线承载上，在第一数据包和第二数据包为RLC层的数据包的情况下，可以 将第一数据包和第二数据包包括的分组数据汇聚协议(packet data convergence protocol，PDCP)PDU在PDCP层合并到第一无线承载上。
作为一种可能的实现方式，可以将第一数据包包括的RLC PDU和第二数据包包括的RLC PDU进行排序和/或去重。
作为一种可能的实现方式，可以将第一数据包括的PDCP PDU和第二数据包包括的PDCP PDU进行排序和/或去重。
第三方面公开一种通信装置，该通信装置包括用于执行第一方面或第一方面的任一可能实现方式所公开的通信方法的模块，或者包括用于执行第二方面或第二方面的任一可能实现方式所公开的通信方法的模块。
第四方面公开一种通信装置，该通信装置可以是接入网设备或者接入网设备内的芯片。该通信装置包括处理器、存储器、输入接口和输出接口，输入接口用于接收来自该通信装置之外的其它通信装置的信息，输出接口用于向该通信装置之外的其它通信装置输出信息。当处理器执行存储器存储的计算机程序时，使得处理器执行第一方面或第一方面的任一可能实现方式所公开的通信方法。
第五方面公开一种通信装置，该通信装置可以是终端设备或者终端设备内的芯片。该通信装置包括处理器、存储器、输入接口和输出接口，输入接口用于接收来自该通信装置之外的其它通信装置的信息，输出接口用于向该通信装置之外的其它通信装置输出信息。当处理器执行存储器存储的计算机程序时，使得处理器执行第二方面或第二方面的任一可能实现方式所公开的通信方法。
第六方面公开一种计算机可读存储介质，该计算机可读存储介质上存储有计算机程序，当该计算机程序运行时，实现如第一方面或第一方面的任一可能实现方式所公开的通信方法，或者实现如第二方面或第二方面的任一可能实现方式所公开的通信方法。
附图说明
图1是本发明实施例公开的一种网络架构示意图；
图2是本发明实施例公开的一种通过SC-PTM实现多播传输的示意图；
图3是本发明实施例公开的一种SC-PTM信道配置示意图；
图4是本发明实施例公开的一种通信方法的流程示意图；
图5是本发明实施例公开的一种数据合并示意图；
图6是本发明实施例公开的一种将数据合并到RLC层处理的示意图；
图7是本发明实施例公开的一种为终端设备分配了C-RNTI和G-RNTI的示意图；
图8是本发明实施例公开的另一种为终端设备分配了C-RNTI和G-RNTI的示意图；
图9是本发明实施例公开的另一种通信方法的流程示意图；
图10是本发明实施例公开的一种采用G-RNTI调度数据的示意图；
图11是本发明实施例公开的又一种通信方法的流程示意图；
图12是本发明实施例公开的一种通信装置的结构示意图；
图13是本发明实施例公开的另一种通信装置的结构示意图；
图14是本发明实施例公开的又一种通信装置的结构示意图；
图15是本发明实施例公开的又一种通信装置的结构示意图；
图16是本发明实施例公开的又一种通信方法的流程示意图；
图17是本发明实施例公开的又一种通信方法的流程示意图。
具体实施方式
本发明实施例公开了一种通信方法及装置，用于提高通信效率。以下分别进行详细说明。
为了更好地理解本发明实施例公开的一种通信方法及装置，下面先对本发明实施例使用的网络架构进行描述。请参阅图1，图1是本发明实施例公开的一种网络架构示意图。如图1所示，该网络架构可以包括终端设备101、接入网设备102和核心网设备103。终端设备101与接入网设备102、接入网设备102与核心网设备103之间可以通过网络连接。核心网设备103，用于向接入网设备102发送信息，以及接收来自接入网设备102的信息。接入网设备102，用于向终端设备101和核心网设备103发送信息，以及接收来自终端设备101和核心网设备103的信息。终端设备101，用于向接入网设备102发送信息，以及接收来自接入网设备102的信息。
终端设备101可以为用户设备(user equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字处理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，未来5G网络中的终端或者未来演进的公共陆地移动网络(public land mobile network，PLMN)中的终端等。
接入网设备102可以是用于与终端设备101进行通信的设备，可以是全球移动通信系统(global system for mobile communication，GSM)或码分多址(code division multiple access，CDMA)中的基站(base transceiver station，BTS)，也可以是宽带码分多址(wideband code division multiple access，WCDMA)系统中的基站(nodeB，NB)，还可以是长期演进(long term evolution，LTE)系统中的演进型基站(evolutional node B，eNB或eNodeB)，还可以是设备对设备(device to device，D2D)通信中担任接入网设备功能的终端，还可以是中继站、接入点、车载设备、发射点、可穿戴设备以及未来5G网络中的网络侧设备或未来演进的PLMN中的接入网设备，或者任一承担网络功能的设备等。
不同系统中核心网设备103可以对应不同的设备。比如在3G中可以对应通用分组无线服务技术(general packet radio service，GPRS)的服务支持节点(serving GPRS support node，SGSN)和/或GPRS的网关支持节点(gateway GPRS Support Node，GGSN)，在4G中可以对应移动管理实体(mobility management entity，MME)和/或服务网关(serving gateway，S-GW)；在5G中可以对应接入移动管理功能(access and mobility management function，AMF)，会话管理功能(session management function，SMF)或者用户面功能(user plane  function，UPF)。
为了更好地理解本发明实施例公开的一种通信方法及装置，下面先对本发明实施例使用的应用场景进行描述。单小区点到多点(single cell point to multipoint，SC-PTM)是一种实现多播传输的技术。请参阅图2，图2是本发明实施例公开的一种通过SC-PTM实现多播传输的示意图。如图2所示，在SC-PTM技术中，小区可以通过G-RNTI同时向多个终端设备调度业务数据，每个G-RNTI可以关联一个多媒体广播多播业务(multimedia broadcast multicast service，MBMS)。因此，在一个区域内，只有包含终端设备的小区需要发送数据，不包含终端设备的小区不需要发送数据，从而可以节省空口资源。
在SC-PTM技术中，可以使用物理下行共享信道(physical downlink share channel，PDSCH)传输组播业务。区别于承载单播数据的PDSCH，承载组播数据的PDSCH可以称为组播PDSCH。在SC-PTM技术中，接入网设备可以向一个小区内的一组终端设备发送承载于物理下行控制信道(physical downlink control channel，PDCCH)的下行控制信息(downlink control information，DCI)。这组终端设备接收到DCI之后，可以根据该DCI包括的调度信息接收组播PDSCH。
请参阅图3，图3是本发明实施例公开的一种SC-PTM信道配置示意图。如图3所示，SC-PTM配置有单小区MBMS点到多点控制信道(single cell MBMS point-to-multipoint control channel，SC-MCCH)和单小区MBMS业务信道(single cell MBMS traffic control channel，SC-MTCH)。SC-MCCH，用于传输控制信息，包含SC-MTCH的配置信息，比如SC-MTCH对应的G-RNTI以及不连续接收模式(discontinuous reception，DRX)参数。SC-MCCH，用于以周期的方式传输数据。
SC-MCCH配置信息可以通过广播信道进行传输，SC-MCCH配置信息用以配置SC-MCCH的接收参数，可以包括MCCH的修改周期、重复周期、发送持续时间等。SC-MCCH采用PDCSH进行传输，其对应的PDCCH采用单小区RNTI(single cell RNTI，SC-RNTI)进行加扰。SC-RNTI的值由协议固定，不需要在广播中配置。
SC-MTCH的配置信息可以通过SC-MCCH传输。SC-MTCH的配置信息可以包括多播业务的配置信息。其中，每个业务的配置信息可以包括业务的临时多播组标识(temporary multicast group identifier，TMGI)、对应的G-RNTI、DRX参数以及发送此业务的配置信息的邻区信息。SC-MTCH也承载在PDSCH上，其对应PDCCH采用G-RNTI加扰。
对于多播业务传输，比如SC-PTM，由于多播业务发送时是一对多的发送，接入网设备是盲发送的，不管具体的终端设备的接收质量，在某个终端设备接收质量不好的情况下，需要建立单播承载，通过单播承载来传输这个业务，以致业务连续性保障不是太好，从而降低了通信效率。
基于图1所示的网络架构，请参阅图4，图4是本发明实施例公开的一种通信方法的流程示意图。如图4所示，该通信方法可以包括如下步骤。
401、接入网设备建立与第一终端设备之间的第一无线承载。
在接入网设备中存在需要向第一终端设备传输的第一业务的情况下，接入网设备可以 建立与第一终端设备之间的第一无线承载。接入网设备可以在接收到核心网设备发送的第一业务的服务质量(quality of service，QoS)参数之后，根据该QoS参数的要求为第一业务建立第一无线承载，之后可以将第一无线承载的参数发送给第一终端设备。第一无线承载为接入网设备与第一终端设备之间传输第一业务的承载。具体的，第一无线承载的参数可以包括下面的一种或多种：
(1)无线承载信息，无线承载信息可以包括第一无线承载的标识；
(2)PDCP层配置参数，PDCP层配置参数可以包括PDCP序号长度、加密参数、头压缩参数等；
(3)RLC层配置参数，RLC层配置参数可以包括逻辑信道号、RLC序号长度、RLC模式等，RLC模式可以为确认模式(acknowledge mode，AM)模式，也可以为非确认(un acknowledge mode，UM)模式，还可以为透明(transparent mode，TM)模式；
(4)MAC层配置参数。
402、接入网设备向第一终端设备发送第一RNTI。
接入网设备可以为第一终端设备分配第一RNTI，并将第一RNTI发送给第一终端设备，第一RNTI可以向第一终端设备调度业务，即第一RNTI只能为第一终端设备调度业务，不能为其它终端设备调度业务。调度的业务可以为第一终端设备的所有业务，也可以为第一终端的调度信令，即接入网设备与第一终端设备之间传输的业务和信令都可以通过第一RNTI进行调度。第一RNTI可以为小区无线网络临时标识(cell radio network temporary identifier，C-RNTI)，也可以为其它可以调度单播业务的RNTI。其中，步骤401与步骤402可以串行执行，也可以并行执行。第一RNTI可以是在步骤401之前就已经分配好的，如第一RNTI可以为在第一终端设备接入当前小区过程中分配的，也可以为第一终端设备由其它小区切换到当前小区过程中分配的。第一RNTI也可以是在执行步骤401的同时或之后分配的。
403、接入网设备向第一终端设备发送第二RNTI。
接入网设备可以为第一终端设备分配第二RNTI，并将第二RNTI发送给第一终端设备。在第一业务为多播业务的情况下，在执行步骤401的同时或之后，接入网设备还可以为第一终端设备分配第二RNTI，第二RNTI可以向包括第一终端设备的一组终端设备调度第一业务，即第二RNTI不仅可以为第一终端设备调度第一业务，也可以为其它终端设备调度第一业务，也即第二RNTI用于调度多播业务。第二RNTI可以为G-RNTI，也可以为其它可以调度多播业务的RNTI。
其中，步骤403与步骤402可以同时执行，也可以分开执行。例如，在切换场景中，当源接入网设备请求将终端设备切向目标接入网设备时，目标接入网设备为终端设备分配无线承载参数，同时分配第一RNTI和第二RNTI并通过源接入网设备发送给终端设备。而在终端设备初始接入接入网设备时，接入网设备先为终端设备分配第一RNTI，后续收到针对终端设备的第一业务建立时再分配第二RNTI。
404、接入网设备使用第一RNTI和第二RNTI在第一无线承载上向第一终端设备调度第一业务的数据包。
接入网设备为第一终端设备建立第一无线承载，以及向第一终端设备发送第一RNTI和第二RNTI之后，接入网设备可以使用第一RNTI和第二RNTI向第一终端设备调度第一业务 的数据包，第一业务的数据包通过第一无线承载传输。相应地，第一终端设备可以使用第一RNTI和第二RNTI接收来自接入网设备调度的第一业务的数据包，并通过第一无线承载相关的配置参数处理第一业务的数据包。
可以是接入网设备使用第一RNTI和第二RNTI在第一无线承载上同时向第一终端设备调度第一业务的数据包，即接入网设备使用第一RNTI在第一无线承载上向第一终端设备调度第一业务的数据包，同时使用第二RNTI在第一无线承载上向第一终端设备调度第一业务的数据包。相应地，第一终端设备可以使用第一RNTI和第二RNTI在第一无线承载上同时接收来自接入网设备调度的第一业务的数据包，即第一终端设备使用第一RNTI在第一无线承载上接收来自接入网设备调度的第一业务的数据包，同时第一终端设备可以使用第二RNTI在第一无线承载上接收来自接入网设备调度的第一业务的数据包。第一RNTI和第二RNTI调度的第一业务的数据包可以是相同的，即第一业务的所有数据包，也可以是不相同的，即第一RNTI和第二RNTI调度数据包可以部分相同，也可以完全不同。例如，第一RNTI调度第一业务的部分数据包，第二RNTI调度第一业务的剩余部分数据包。
也可以是接入网设备先使用第二RNTI在第一无线承载上向第一终端设备调度第一业务的数据包，第一终端设备使用第二RNTI在第一无线承载上接收来自接入网设备调度的第一业务的数据包。之后第一终端设备判断第一业务的数据包是否传输成功，在判断出第一业务的数据包传输失败的情况下，第一终端设备向接入网设备发送用于指示第一业务的数据包传输失败的反馈信息。接入网设备接收来自第一终端设备的用于指示第一业务的数据包传输失败的反馈信息之后，接入网设备使用第一RNTI在第一无线承载上向第一终端设备重传第一业务的数据包。在第一终端设备判断出第一业务的数据包传输成功的情况下，第一终端设备向接入网设备发送用于指示第一业务的数据包传输成功的反馈信息，接入网设备接收来自第一终端设备的用于指示第一业务的数据包传输成功的反馈信息，结束对第一业务的数据包的传输。
具体地，对于同一业务，选择使用G-RNTI调度还是选择使用C-RNTI调度可以基于以下原则进行：同一业务只有一个终端设备接收时采用C-RNTI，同一业务有多个端设备接收时采用G-RNTI；哪个RNTI调度产生的吞吐量大则采用哪个RNTI，比如采用C-RNTI可以分别为终端设备1和终端设备2分别调度1000比特(bit)和2000bit的数据，采用G-RNTI只能一次为终端设备1和终端设备2调度200bit的数据，此时采用C-RNTI分别为终端设备1和终端设备2进行调度；在一个终端设备使用G-RNTI调度连续失败的情况下，可以转而采用C-RNTI调度。
具体地，第一终端设备可以使用第一RNTI接收来自接入网设备的第一业务的第一数据包，使用第二RNTI接收来自接入网设备的第一业务的第二数据包，之后将第一数据包和第二数据包合并到第一无线承载上。例如，第一数据包和第二数据包为MAC层的数据包，第一终端设备可以将第一数据包和第二数据包包括的RLC PDU在RLC层合并到第一无线承载上，即将第一数据包包括的RLC PDU和第二数据包包括的RLC PDU进行排序和/或去重。或者，第一数据包和第二数据包为RLC层的数据包，第一终端设备将第一数据包和第二数据包包括的PDCP PDU在PDCP层合并到第一无线承载上，即将第一数据包括的PDCP PDU和第二数据包包括的PDCP PDU进行排序和/或去重。去重即删除重复的数据。
请参阅图5，图5是本发明实施例公开的一种数据合并示意图。如图5所示，接入网设备将每个终端设备的数据通过PDCP层和RLC层之后，可以将数据使用C-RNTI和G-RNTI依次通过MAC层和物理(physical，PHY)层传输给终端设备。终端设备使用C-RNTI和G-RNTI依次通过PHY层和MAC层接收到数据，之后将使用C-RNTI和G-RNTI接收的数据在RLC层和/或PDCP层合并到单播承载上进行处理。
请参阅图6，图6是本发明实施例公开的一种将数据合并到RLC层处理的示意图。如图6所示，终端设备1使用C-RNTI1接收逻辑信道(logic channel，LCH)标识为LCH1的多播业务和LCH标识为LCH2的单播业务，终端设备1和终端设备2使用G-RNTI接收LCH标识为LCH1的多播业务，终端设备1使用C-RNTI1接收到LCH标识为LCH1的多播业务以及使用G-RNTI接收到LCH标识为LCH1的多播业务之后，将这些数据在RLC层进行合并处理。
请参阅图7，图7是本发明实施例公开的一种为终端设备分配了C-RNTI和G-RNTI的示意图。如图7所示，虚线表示控制面连接，实线表示用户数据的发送路径。三个终端设备都与接入网设备均有连接，对于每个终端设备分别配置了C-RNTI和用于单播承载的数据无线承载(data radio bearer，DRB)，同时DRB还关联一个G-RNTI，通过G-RNTI和C-RNTI调度实现单播与多播之间的动态转换。图7中三个终端设备接收同一业务，每个终端设备都有单播承载，即基于C-RNTI接收数据的通道，接入网设备同时为三个终端设备还配置了相同的G-RNTI。在采用C-RNTI调度的情况下，接入网设备可以将同一数据分别调度给三个终端设备，此时是利用单播调度。在采用G-RNTI调度数据的情况下，接入网设备调度一份数据三个终端设备都能收到。
请参阅图8，图8是本发明实施例公开的另一种为终端设备分配了C-RNTI和G-RNTI的示意图。如图8所示，在5G中，新无线核心(new radio core，NGC)网设备与接入网设备之间传输业务的数据。两个终端设备分别对应不同的C-RNTI，两个终端设备对应同一个G-RNTI。C-RNTI用于终端设备接收针对单个终端设备的调度信息，C-RNTI可以用来调度针对单个用户信令或者数据传输。G-RNTI用来同时调度多个终端设备进行相同业务的接收。对于同一业务，如果采用C-RNTI调度则只有配置该C-RNTI的终端设备可以收到，如果采用G-RNTI调度则会有多个终端设备都可以收到。
基于图1所示的网络架构，请参阅图9，图9是本发明实施例公开的另一种通信方法的流程示意图。如图9所示，该通信方法可以包括以下步骤。
901、核心网设备向接入网设备发送业务建立请求消息。
在存在需要传输的第一业务的情况下，核心网设备可以向接入网设备发送业务建立请求消息。该业务建立请求消息可以携带在初始上下文建立消息、协议数据单元(protocol data unit，PDU)会话建立消息、上下文修改消息等消息中。第一业务为多播业务。
在一种情况下，业务建立请求消息可以携带用于指示第一业务为多播业务的公共信息，即在业务建立请求消息携带公共信息的情况下，业务建立请求消息要建立的业务为多播业务，在业务建立请求消息未携带公共信息的情况下，业务建立请求消息要建立的业务为单播业务。公共信息可以为多播业务的业务信息，业务信息可以为TMGI，也可以为其它可以 表示一个多播业务的业务信息。公共信息也可以为多播业务的地址信息，接入网设备可以加入该地址信息对应的多播组以接收第一业务。公共信息与业务之间的对应关系可以为业务服务质量(quality of service，QoS)流(flow)与公共信息之间的对应关系。QoS流与公共信息之间的对应关系可以如表1所示：
业务信息 公共信息
QoS流1，QoS流2 业务1/多播组地址信息1
QoS流3 业务2/多播组地址信息2
QoS流4 无
表1 QoS流与公共信息之间的对应关系
终端设备的多个QoS流可以与多个公共信息对应，如表1所示，QoS流1与QoS流2对应的公共信息为业务1或多播组地址信息1，QoS流3对应的公共信息为业务2或多播组地址信息2。QoS流1、QoS流2和QoS流3均有对应的公共信息，因此，QoS流1、QoS流2和QoS流3对应的业务为多播业务。业务1和业务2为多播业务的业务信息，多播组地址信息1和多播组地址信息2为多播业务的地址信息。有些QoS流可以是没有公共信息，如表1所示，QoS流4没有公共信息，表示QoS流4内容不会与其他终端设备的内容相同，即QoS流4对应的业务为单播业务。可选地，表1中的业务信息也可以为DRB的标识(identifier，ID)，即可以将表1中的QoS流替换为DRB的ID。
在另一种情况下，业务建立请求消息可以直接指示第一业务为多播业务。即在业务建立请求消息指示业务建立请求消息要建立的业务为多播业务的情况下，业务建立请求消息要建立的业务为多播业务，在业务建立请求消息未指示业务建立请求消息要建立的业务为多播业务的情况下，业务建立请求消息要建立的业务为单播业务。
可选地，如果有多个接入网设备和核心网设备连接，并且多个接入网设备都建立了针对相同业务的承载时，为了保证终端设备在不同接入网设备之间移动时业务能够连续接收，需要保证核心网设备向多个接入网设备发送相同的业务时采用相同的数据包编号。数据包编号可以为GPRS隧道协议(GPRS tunnelling protocol，GTP)编号，也可以为其它具有同等功能的编号。例如，接入网设备1和接入网设备2都和核心网设备连接，接入网设备1中有UE1和UE2同时接收业务1，接入网设备2中有UE3和UE4同时接收业务1。如果UE1从接入网设备1移动到接入网设备2，UE1会执行切换到接入网设备2，UE1的业务数据会被转发到接入网设备2。接入网设备2可能将UE1、UE3和UE4分配相同G-RNTI进行统一调度。为了确定UE1已经传输了哪些数据，接入网设备2可以根据被转发的UE1的数据包的数据包编号确定与UE3和UE4的数据包之间的先后关系，可以先保证UE1、UE3和UE4传输进度对齐之后再进行传输。由于接入网设备之间采用了相同的数据包编号，因此，UE1切换到接入网设备2之后可以根据数据包编号判断UE1的传输进度和接入网设备2当前服务的UE3，UE4之间传输进度的区别。对于同一接入网设备服务的UE，如果没有采用公共的传输承载，也可以利用数据包编号来判断传输给UE的数据包的内容是否相同。例如，UE1和UE2在核心网设备与接入网设备1之间都有专用的数据通道，可以根据两个专用的数据通道传输的数据包编号来判断这个两个UE哪些数据包的内容相同，进而可以采用G-RNTI同时调度相同的数据包给这两个UE。
可选地，在步骤901之前，终端设备、核心网设备和应用服务器之间可以建立用于接收 第一业务的连接。用于接收第一业务的连接包括终端设备与核心网设备之间的PDU会话，以及核心网设备与应用服务器之间的数据通道。终端设备和应用服务器进行交互之前，应用服务器需要获知终端设备需要接收第一业务的数据，应用服务器可以触发PDU会话修改流程，主要包括以下步骤：
(1)应用服务器向核心网设备提供第一业务相关的识别信息，该识别信息用于核心网设备识别第一业务为多播业务对应的下行数据；
具体地，应用服务器向核心网的策略控制功能(policy control function，PCF)网元提供第一业务的识别信息。核心网的PCF网元接收到来自应用服务器的第一业务的识别信息之后，可以发起PDU会话修改流程，可以向核心网的SMF网元提供第一业务的识别信息。核心网的SMF网元根据第一业务的识别信息为第一业务建立传输资源，传输资源可以为业务QoS流。
(2)核心网设备向接入网设备发送业务建立请求消息。业务建立请求消息可以包括业务信息、多播业务的公共信息和指示第一业务为多播业务的信息中的一项或多项。
902、接入网设备建立与第一终端设备之间的第一无线承载。
接入网设备接收到来自核心网设备的业务建立请求消息之后，表明接入网设备与第一终端设备之间存在需要传输的第一业务，可以建立与第一终端设备之间的第一无线承载。具体的描述可以参考步骤401。
由于第一业务为多播业务，第一业务可能通过G-RNTI调度给多个终端设备，因此，接入网设备为第一终端设备建立的第一无线承载不启动加密。由于不同的终端设备加密的密钥不同，一旦加密，将第一业务调度给多个终端设备后，多个终端设备中只有一个终端设备能够正确解密出第一业务，其它终端设备无法解密出第一业务，以致无法实现多播业务的多播传输。或者，为了提高安全性，接入网设备为第一终端设备建立的第一无线承载时可以为第一无线承载配置使用公用密钥，公用密钥为多个接收第一业务的终端设备共同使用的密钥。多个终端设备在通过第一无线承载接收第一业务时都使用公用密钥进行解密。这样接入网设备在对第一终端设备进行调度时，无论采用第一RNTI或者第二RNTI均可以采用该公用密钥进行调度。终端设备无论采用哪个RNTI进行接收，均可以采用相同的公用密钥进行解密。该公共密钥可以是网络设备配置的，例如，可以是接入网设备或者核心网设备通过加密后的信令通道配置给终端设备的，也可以是终端设备根据第一业务的相关信息推导得到的，第一业务的相关信息可以为第一业务的业务标识，也可以为第一业务的无线承载标识，还可以为第二RNTI，还可以为其它与第一业务有关的信息。例如，第一业务对应第二RNTI为62348，终端设备可以将该第二RNTI和第一序列进行掩码运算得到第二序列，可以采用第二序列作为秘钥。第一序列可以为网络设备配置给终端设备的，也可以为固定的序列。
903、接入网设备关联第一无线承载与第一公共数据通道。
此步骤为可选，接入网设备为第一无线承载与第一公共数据通道是为了节省核心网和接入网设备间传输第一业务数据开销，多个终端设备都接收第一业务时，采用公共数据通道避免了第一业务数据为多个终端设备重复发送。如果没有此步骤，接入网设备仍然和核心网设备之间建立专用数据通道，这样，终端设备都接收第一业务时，针对每个终端设备， 接入网设备和核心网设备间有不同专用数据通道。第一业务的数据可以在这些专用通道上发送给接入网设备。
接入网设备根据业务建立请求消息确定第一业务为多播业务之后，关联第一无线承载与第一公共数据通道，第一公共数据通道为接入网设备与核心网设备之间用于传输第一业务的数据的公共数据通道。接入网设备在通过第一公共数据通道接收到来自核心网设备的第一业务的数据之后，接入网设备会将接收的第一业务的数据在第一无线承载上向第一终端设备进行发送。第一公共数据通道可以为所有接收第一业务的终端设备服务。
第一公共数据通道可以是接入网设备触发建立的，也可以是核心网设备触发建立的。在第一公共数据通道是接入网设备触发建立的情况下，接入网设备接收到业务建立请求消息之后，可以为向核心网设备返回接收第一业务的下行地址信息，该下行地址信息对应的地址用于接收第一业务对应的一个或者多个QoS流。在采用此方法建立第一公共数据通道的情况下，公共信息为多播业务的业务信息。接入网设备触发建立第一公共数据通道也可以采用互联网协议(internet protocol，IP)组播协议进行建立，例如：接入网设备向核心网设备发送多播组加入请求，以便接收多播组的数据，多播组加入成功后，可以认为第一公共数据通道建立成功，接入网设备会从核心网设备接收到第一业务对应的数据。
在第一公共数据通道是核心网设备触发建立的情况下，核心网设备可以向接入网设备发起携带业务标识的公共数据通道建立请求，接入网设备确认建立后公共数据通道建立成功。
第一公共数据通道可以是之前已经建立好的，此处只是将第一无线承载与第一公共数据通道关联起来。例如，接入网设备关联第一无线承载与第一公共数据通道之后，在接入网设备接收到针对其他终端设备的业务建立请求消息之后，在该业务建立请求消息为用于建立第一业务的业务建立请求消息的情况下，可以直接利用第一公共数据通道而不需要建立。再例如，接入网设备已经为公共信息1(或者业务1或者多播组地址信息1)建立了公共数据通道，直接将该公共通道关联到该业务上。第一公共数据通道也可以之前未建立，此时进行建立以及关联的，建立的过程可以参考上面的描述。
904、接入网设备向第一终端设备发送第一RNTI。
其中，步骤904与步骤402相同，详细描述请参考步骤402，在此不加赘述。
905、接入网设备向第一终端设备发送第二RNTI。
其中，步骤905与步骤403相同，详细描述请参考步骤403，在此不加赘述。
906、接入网设备向第一终端设备发送配置信息。
接入网设备为第一终端设备分配第二RNTI同时或之后，可以向第一终端设备发送配置信息。配置信息可以包括第二RNTI对应的带宽部分(bandwidth part，BWP)信息、第二RNTI对应的控制资源集(control resource set，CORESET)信息以及第二RNTI对应的搜索空间信息中的一种或多种。COREST信息指示了G-RNTI PDCCH所在时频资源。
BWP可以认为是一个小区的部分带宽，每个终端设备可以配置工作在若干个BWP上，但任一时刻只有一个BWP是激活的。BPW的主要参数可以包括带宽、频率位置、子载波间隔(sub carrier space，SCS)、循环前缀(cyclic prefix，CP)长度、CORSET相关的配置信息以及PDSCH相关的配置信息。对于一个小区而言，会有至少一个初始(initial)BWP，所 有的广播，寻呼等公共信息都在初始BWP上发送。终端设备进入连接态后，接入网设备可以再为终端设备配置一些专用的BPW。第一终端设备可以根据BPW确定BPW对应的SCS、频域位置、CP长度等。
配置信息还可以包括第一业务的PDSCH加扰序列，以便第一终端设备在解扰第一业务的PDSCH时，可以采用该PDSCH加扰序列进行解扰。配置信息还可以包括G-RNTI的DRX参数，以便第一终端设备使用该DRX参数进行G-RNTI检测。配置信号还可以包括解调参考信号，以便第一终端设备使用该解调参考信号进行G-RNTI调度的PDSCH解调。配置信息还可以包括速率匹配参考信号，以便第一终端设备接收G-RNTI调度的PDSCH时可以排除掉该解调参考信号对应的位置。
可选地，接入网设备可以向第一终端设备发送指示信息，该指示信息可以指示第二RNTI用于调度第一业务。其中，该指示信息可以是接入网设备单独发送给第一终端设备的，也可以是包括在上述配置信息中一起发送的。该指示信息可以为G-RNTI与业务的关联信息，如G-RNTI与LCH的关系、G-RNTI与DRB的关系、G-RNTI与业务标识的关系等。该指示信息也可以为DRB关联的业务信息，如网络设定了DRB1是关联多播业务的，终端设备可以认为G-RNTI是用来接收该DRB1的数据的。
配置信息还可以包括第二RNTI关联的业务信息，如逻辑信道标识、TMGI、DRB ID等，以便第一终端设备可以根据这些信息确定使用第二RNTI调度的业务属于哪个业务，这样利用G-RNTI发送的数据不需要携带逻辑信道标识。
907、接入网设备使用第一RNTI和第二RNTI在第一无线承载上向第一终端设备调度第一业务的数据包。
其中，步骤907与步骤404相似，详细描述请参考步骤404，在此不加赘述。
具体地，第一终端设备接收到来自接入网设备的配置信息之后，可以根据配置信息在第一无线承载上从第二RNTI上检测来自接入网设备的第一业务的数据包。
在接入网设备未向第一终端设备发送用于指示第二RNTI用于调度第一业务的指示信息的情况下，第一业务的数据包可以包括逻辑信道标识，逻辑信道标识可以指示第二RNTI传输的数据包为第一业务的数据包。
在接入网设备采用G-RNTI调度业务的情况下，终端设备1反馈了NACK，接入网设备可以采用C-RNTI进行重传调度。这样G-RNTI可以继续调度新的数据，保证终端设备1与其他正确接收数据的终端设备可以继续接收新数据。而没有正确接收数据的终端设备1可以使用C-RNTI进行重传的接收，即保证了终端设备1的数据的重传，又不影响其他终端设备的新数据的接收。采用混合自动重传请求(hybrid automatic repeat request，HARQ)机制进行数据重传时需要保证新传和重传使用相同的HARQ进程。而采用G-RNTI新传在利用C-RNTI重传时很难保证采用同一HARQ进程，因为G-RNTI是多个终端设备公用的，采用G-RNTI调度的进程号在多个终端设备之间是一致的，比如G-RNTI调度8号进程，则所有使用该G-RNTI的终端设备都使用8号进程，如果针对终端设备1对G-RNTI调度的某个数据包进行重传，则不能使用8号进程，此时需要更换一个进程，比如6号进程。但更换进程后，终端设备无法判断更换后的6号进程是用来调度8号进程的重传，因此，需要接入网设备通知终端设备6号进程与进程8之间的关系，用以通知终端设备6号进程当前是针对8号进程的重传。 因此，在第一业务的数据包的初传使用第二RNTI，而第一业务的数据包的重传使用第一RNTI的情况下，接入网设备可以向第一终端设备发送第一进程与第二进程之间的关联关系，第一进程为用于初传第一业务的数据包的进程，第二进程为用于重传第一业务的数据包的进程。接入网设备可以通过RRC配置第一进程与第二进程之间的关联关系。例如，6号进程与8号进程之间的关联关系，即配置6号进程可用来重传8号进程的数据，然后在调度6号进程的时候，调度命令，如DCI，中可以指示终端设备当前6号进程的重传是针对关联进程的重传，此时，DCI可以通过1比特来指示当前重传是针对关联进程的重传。接入网设备也可以在调度第二进程时，可以在调度命令中指示终端设备当前进程的重传关联的是8号进程。例如，在调度6号进程的时候，调度命令中可以指示终端设备当前进程的重传关联的是8号进程，此时调度命令需要增加3个比特来指示。其中，第一进程与第二进程之间的关联关系可以是接入网设备在上述配置信息中发送给第一终端设备的，也可以是后续需要重传第一业务的数据包的时候发送给第一终端设备的。
接入网设备采用G-RNTI调度时，需要确保多个数据包从相同的数据位置开始。请参阅图10，图10是本发明实施例公开的一种采用G-RNTI调度数据的示意图。如图10所示，业务数据目前发送到接入网设备的有数据1、数据2和数据3共3个数据包。开始的时候终端设备1和终端设备2分别采用C-RNTI来调度，终端设备1和终端设备2都已经传输完数据1以及数据2的部分数据，但数据2剩余部分并不相同。此时启动G-RNTI后，G-RNTI需要从数据3开始调度，数据2剩余部分数据需要终端设备1和终端设备2采用各自C-RNTI继续调度。
基于图1所示的网络架构，请参阅图11，图11是本发明实施例公开的又一种通信方法的流程示意图。如图11所示，该通信方法可以包括以下步骤。
1101、接入网设备向资源管理模块发送用于指示第一业务的接收终端设备的数量的指示信息和/或第一业务使用的RNTI的第一配置信息。
接入网设备可以实时或周期性地向资源管理模块发送用于指示第一业务的接收终端设备的数量的指示信息。接入网设备也可以实时地或周期性地根据该接入网设备所覆盖的小区内接收第一业务的数量，确定第一小区内使用第二RNTI调度第一业务，之后向资源管理模块发送第一配置信息，第一配置信息可以包括第二RNTI对应的BWP信息、第二RNTI对应的CORESET信息、第二RNTI对应的搜索空间信息、第一业务的PDSCH加扰序列、解调参考信号、G-RNTI的DRX参数、速率匹配参考信号等中的一种或多种。资源管理模块可以为独立的设备，也可以集成在接入网设备中。资源管理模块主要用于协调多个小区或者多个接入网设备之间使用的G-RNTI和/或调度资源。
1102、资源管理模块向接入网设备发送第一业务对应的第二配置信息。
资源管理模块接收到来自接入网设备的用于指示第一业务的接收终端设备的数量的指示信息之后，根据指示信息可以确定多个小区可以使用第二RNTI调度第一业务，可以向接入网设备发送第一业务对应的第二配置信息。第二配置信息包括第二RNTI的配置信息。
资源管理模块接收到来自多个接入网设备的第一配置信息之后，在多个小区的业务为第一业务的情况下，将多个小区使用的第二RNTI进行统一，之后可以向接入网设备发送第一业务对应的第二配置信息。第二配置信息包括统一后的第二RNTI的传输资源的配置信息。 该传输资源可以包括第二RNTI对应的BWP信息、第二RNTI对应的CORESET信息、第二RNTI对应的搜索空间信息、第一业务的PDSCH加扰序列、解调参考信号、G-RNTI的DRX参数、速率匹配参考信号等中的一种或多种。例如，可以根据第一小区的第二RNTI和传输资源修改第二小区的第二RNTI和传输资源，以便两个小区采用相同的第二RNTI和资源。
在多个小区之间采用相同的第二RNTI和传输资源传输相同业务时，空口资源形成相同的信号在多个小区传输时可以形成信号叠加的效果，从而可以增强第一业务的接收效果。
1103、核心网设备向接入网设备发送业务建立请求消息。
其中，步骤1103与步骤901相同，详细描述请参考步骤901，在此不加赘述。
1104、接入网设备建立与第一终端设备之间的第一无线承载。
其中，步骤1104与步骤902相同，详细描述请参考步骤902，在此不加赘述。
1105、接入网设备关联第一无线承载与第一公共数据通道。
其中，步骤1105与步骤903相同，详细描述请参考步骤903，在此不加赘述。
1106、接入网设备向第一终端设备发送第一RNTI。
其中，步骤1106与步骤402相同，详细描述请参考步骤402，在此不加赘述。
1107、接入网设备向第一终端设备发送第二RNTI。
其中，步骤1107与步骤403同，详细描述请参考步骤303，在此不加赘述。此外，第二RNTI可以是接入网设备根据第二配置信息分配的。
1108、接入网设备向第一终端设备发送包括第二配置信息的配置信息。
其中，步骤1108与步骤906相似，详细描述请参考步骤906，在此不加赘述。
1109、接入网设备使用第一RNTI和第二RNTI在第一无线承载上向第一终端设备调度第一业务的数据包。
其中，步骤1109与步骤907相同，详细描述请参考步骤907，在此不加赘述。
基于图1所示的网络架构，请参阅图16，图16是本发明实施例公开的又一种通信方法的流程示意图。如图16所示，该通信方法可以包括以下步骤。
1601、核心网设备向接入网设备发送第一终端设备与第一业务的数据之间的关联关系。
核心网设备在存在第一终端设备的待发送的第一业务的数据的情况下，可以向接入网设备发送第一终端设备与第一业务的数据之间的关联关系。其中，第一业务可以为组播业务，核心网设备可以为SMF网元。其中，第一终端设备可以为用于传输该组播业务(即第一业务)的一组终端设备中的任一终端设备。
核心网设备可以接收来自第一终端设备的PDU会话建立/修改请求，之后可以为第一终端设备建立用于接收第一业务的数据的第一QoS流。之后可以向接入网设备发送第一终端设备与第一业务的数据之间的关联关系。
核心网设备可以接收来自应用服务器的用于为第一终端设备建立用于接收第一业务的数据的QoS流的消息，之后可以为第一终端设备建立用于接收第一业务的数据的第一QoS流。之后可以向接入网设备发送第一终端设备与第一业务的数据之间的关联关系。
第一终端设备与第一业务的数据之间的关联关系可以包含第一终端设备的第一QoS流的标识与公共QoS流的标识之间的关联关系，该公共QoS流为用于传输第一业务的数据的 QoS流，第一终端设备的第一QoS流为第一终端设备用于接收第一业务的数据的QoS流。一组终端设备的第一QoS流的标识与公共QoS流的标识之间的关联关系可以参考表2，其中，每一行表示一个终端设备的第一QoS流的标识与公共QoS流的标识之间的关联关系。
终端设备的标识 终端设备的第一QoS流的标识 公共QoS流的标识
UE1 QFI_1-1 QFI-C1
UE2 QFI_1-2 QFI-C1
UE3 QFI_1-3 QFI-C1
… … …
表2 一组终端设备的第一QoS流的标识与公共QoS流的标识之间的关联关系
如表2所示，UE1、UE2和UE3为终端设备的标识，QFI_1-1为UE1对应的终端设备的第一QoS流的标识，QFI_1-2为UE2对应的终端设备的第一QoS流的标识，QFI_1-3为UE3对应的终端设备的第一QoS流的标识，QFI-C1为用于传输第一业务的数据的公共QoS流的标识。终端设备的第一QoS流的标识与公共QoS流的标识之间的关联关系也可以参考表3。如表3所示，一个公共QoS流的标识QFI-C1对应三个终端设备的第一QoS流的标识QFI_1-1、QFI_1-2和QFI_1-3。可选地，第一终端设备与第一业务的数据之间的关联关系还可以包括第一终端设备的第一QoS流对应的隧道标识信息，和/或公共QoS流对应的隧道标识信息。其中，隧道标识信息可以是核心网侧隧道信息，和/或，接入网侧隧道信息。可选地，第一终端设备与第一业务的数据之间的关联关系还可以包括第一终端设备的第一QoS流对应的会话标识信息，和/或，公共QoS流对应的会话标识信息。
Figure PCTCN2020105575-appb-000001
表3 一组终端设备的第一QoS流的标识与公共QoS流的标识之间的关联关系
第一终端设备与第一业务的数据之间的关联关系可以包括第一终端设备的第一QoS流的标识与第二终端设备的第一QoS流的标识之间的关联关系，第一终端设备的第一QoS流为第一终端设备用于接收第一业务的数据的QoS流，第二终端设备的第一QoS流用于传输第一业务的数据，第二终端设备为该一组终端设备中除第一终端设备之外的任一终端设备。第一终端设备的第一QoS流的标识与第二终端设备的第一QoS流的标识之间的关联关系可以参考表4和表5。如表4所示，UE1、UE2和UE3为终端设备的标识，QFI_1-1为UE1对应的终端设备的第一QoS流的标识，QFI_1-2为UE2对应的终端设备的第一QoS流的标识，QFI_1-3为UE3对应的终端设备的第一QoS流的标识，可见，UE2对应的终端设备的第一QoS流的标识QFI_1-2与UE1对应的终端设备的第一QoS流的标识QFI_1-1和UE3对应的终端设备的第一QoS流的标识QFI_1-3均存在关联关系。如表5所示，UE2对应的终端设备的QoS流的标识QFI_1-2与UE1对应的终端设备的QoS流的标识QFI_1-1和UE3对应的终端设备的QoS流的标 识QFI_1-3均存在关联关系。可选地，第一终端设备与第一业务的数据之间的关联关系还可以包括第一终端设备的第一QoS流对应的隧道标识信息，和/或，第二终端设备的第一QoS流对应的隧道标识信息。其中，隧道标识信息可以是核心网侧隧道信息，和/或，接入网侧隧道信息。可选地，第一终端设备与第一业务的数据之间的关联关系还可以包括第一终端设备的第一QoS流对应的会话标识信息，和/或第二终端设备的第一QoS流对应的会话标识信息。
终端设备的标识 终端设备的第一QoS流的标识
UE1 QFI_1-1 QFI_1-2
UE2 QFI_1-2 QFI_1-2(可选)
UE3 QFI_1-3 QFI_1-2
… …
表4 终端设备的第一QoS流的标识之间的关联关系
第二终端设备的第一QoS流的标识 其它终端设备的第一QoS流的标识
QFI_1-2 QFI_1-1 QFI_1-2(可选) QFI_1-3
… …
表5终端设备的第一QoS流的标识之间的关联关系
第一终端设备与第一业务的数据之间的关联关系可以包含第一终端设备的第一QoS流的标识与第一业务的数据的索引信息之间的关联关系，第一终端设备的第一QoS流可以用于第一终端设备接收第一业务的数据。第一业务的数据的索引信息用于表示传输的数据是第一业务的数据，或者是同一种数据。第一业务的数据的索引信息可以是第一业务的数据的索引值、内容标识、参考值、或者组标识。对于不同的业务应该使用同一类型或同一格式(format)的索引信息。以第一业务的数据的索引值为例说明第一终端设备的第一QoS流的标识与第一业务的数据的索引信息之间的关联关系，可以参考表6和表7。如表6所示，UE1、UE2和UE3为终端设备的标识，QFI_1-1为UE1对应的终端设备的第一QoS流的标识，Index1为第一业务的数据的索引值，QFI_1-2为UE2对应的终端设备的第一QoS流的标识，QFI_1-3为UE3对应的终端设备的QoS流的标识。如表7所示，第一业务的数据的索引值Index1对应UE1对应的终端设备的第一QoS流的标识QFI_1-1、UE2对应的终端设备的第一QoS流的标识QFI_1-2以及UE3对应的终端设备的第一QoS流的标识QFI_1-3。可选地，第一终端设备与第一业务的数据之间的关联关系还可以包括第一终端设备的第一QoS流对应的隧道标识信息，其中，该隧道标识信息可以是核心网侧隧道信息，和/或，接入网侧隧道信息。可选地，第一终端设备与第一业务的数据之间的关联关系还可以包括第一终端设备与第一业务对应的会话标识信息。
终端设备的标识 终端设备的第一QoS流的标识+第一业务的数据的索引值
UE1 QFI_1-1 Index1
UE2 QFI_1-2 Index1
UE3 QFI_1-3 Index1
… …
表6 终端设备的第一QoS流的标识与第一业务的数据的索引信息之间的关联关系
第一业务的数据的索引值 终端设备的QoS流的标识
Index1 QFI_1-1 QFI_1-2(可选) QFI_1-3
… …
表7 终端设备的QoS流的标识与第一业务的数据的索引信息之间的关联关系
接入网设备可以从核心网设备获取第一终端设备与第一业务的数据之间的关联关系，进而，可以根据第一终端设备与第一业务的数据之间的关联关系生成一组终端设备和第一业务的数据的关联关系，用于接入网设备调度第一业务的数据包。接入网设备也可以直接从核心网设备获取一组终端设备和第一业务的数据的关联关系，具体内容可以参考表2-表7。
在一种实现方式中，第一终端设备与第一业务的数据之间的关联关系可以包含第一终端设备的第二QoS流的标识与该一组终端设备中的其他至少一个终端设备的第二QoS流的标识之间的关联关系，该一组终端设备中的其他至少一个终端设备的第二QoS流用于接收该第一业务的数据，第一终端设备的第二QoS流可以用于第一终端设备接收第一业务的数据。第一终端设备的第二QoS流的标识与该一组终端设备中的其他至少一个终端设备的第二QoS流的标识之间的关联关系可以参考表8-表11。如表8所示，UE1为第一终端设备的标识，QFI_2-1为第一终端设备的第二QoS流的标识。如表9所示，UE2为第二终端设备的标识，第二终端设备的第二QoS流的标识QFI_2-2与第一终端设备的第二QoS流的标识QFI_2-1之间存在关联关系。如表10所示，UE3为第三终端设备的标识，第三终端设备的第二QoS流的标识QFI_2-3与第一终端设备的第二QoS流的标识QFI_2-1和第二终端设备的第二QoS流的标识QFI_2-2之间存在关联关系。如表11所示，UE4为第四终端设备的标识，第四终端设备的第二QoS流的标识QFI_2-4与第一终端设备的第二QoS流的标识QFI_2-1、第二终端设备的第二QoS流的标识QFI_2-2和第三终端设备的第二QoS流的标识QFI_2-3之间存在关联关系。第一终端设备、第二终端设备、第三终端设备和第四终端设备为一组终端设备中的终端设备。可选地，第一终端设备的第二QoS流的标识与该一组终端设备中的其他至少一个终端设备的第二QoS流的标识之间的关联关系还可以包括该第一终端的第二QoS流对应的隧道标识信息，和/或和该一组终端设备中的其他至少一个终端设备的第二QoS流的对应的隧道标识信息。其中，隧道标识信息可以是核心网侧隧道信息，和/或，接入网侧隧道信息。可选地，第一终端设备的第二QoS流的标识与该一组终端设备中的其他至少一个终端设备的第二QoS流的标识之间的关联关系还可以包括第一终端设备与第一业务对应的会话标识信息。
第一终端设备的标识 第一终端设备的第二QoS流的标识
UE1 QFI_2-1
表8 第一终端设备的第二QoS流的标识
第二终端设备的标识 第一终端设备和第二终端设备的第二QoS流的标识
UE2 QFI_2-2 QFI_2-1
表9 第一终端设备与第二终端设备的第二QoS流的标识之间的关联关系
Figure PCTCN2020105575-appb-000002
表10 第一终端设备、第二终端设备和第三终端设备的第二QoS流的标识之间的关联关系
Figure PCTCN2020105575-appb-000003
表11 第一终端设备、第二终端设备、第三终端设备和第四终端设备的第二QoS流的标识之间的关联关系
第一终端设备与第一业务的数据之间的关联关系可以是携带在SMF网元通过AMF网元发送给接入网设备的N2会话管理信息中，也可以放在其它SMF发给接入网设备的消息或容器中。
1602、接入网设备建立与第一终端设备之间的第一无线承载。
接入网设备接收到来自核心网设备的第一终端设备与第一业务的数据之间的关联关系之后，表明接入网设备与第一终端设备之间存在需要传输的第一业务的数据，可以建立与第一终端设备之间的第一无线承载，具体的描述可以参考步骤902。其中，第一终端设备与第一业务的数据之间的关联关系可以是核心网设备通过PDU会话资源建立请求(session resource setup request)发送的。
1603、接入网设备关联第一无线承载与用于传输第一业务的数据的QoS流。
接入网设备建立完与第一终端设备之间的第一无线承载之后，可以根据从核心网获取的关联关系确定需要在第一无线承载上传输从用于传输第一业务的数据的QoS流上接收到的第一业务的数据，用于传输第一业务的数据的QoS流传输的是第一业务的数据。其中，用于传输第一业务的数据的QoS流可以是步骤1601中的公共QoS流或第二终端设备的第一QoS流。在关联信息包含第一业务的数据对应的索引信息的情况下，接入网设备可以从该一组终端设备中的第一QoS流中选择一个进行传输。其中，步骤1603为可选地步骤。
1604、接入网设备向第一终端设备发送第一RNTI。
其中，详细描述请参考步骤904，在此不加赘述。
1605、接入网设备向第一终端设备发送第二RNTI。
其中，接入网设备根据关联关系向第一终端设备发送第二RNTI。详细描述请参考步骤905，在此不加赘述。
1606、接入网设备向第一终端设备发送配置信息。
其中，详细描述请参考步骤906，在此不加赘述。
1607、接入网设备使用第一RNTI和第二RNTI在第一无线承载上向第一终端设备调度第一业务的数据包。
其中，详细描述请参考步907，在此不加赘述。
基于图1所示的网络架构，请参阅图17，图17是本发明实施例公开的又一种通信方法的 流程示意图。如图17所示，该通信方法可以包括以下步骤。
1701、核心网设备向接入网设备发送用于建立第一终端的第一QoS流的会话建立请求消息。
在存在需要传输的第一业务的数据的情况下，核心网设备可以向接入网设备发送用于建立第一终端的第一QoS流的会话建立请求消息。该会话建立请求消息可以携带在初始上下文建立消息、PDU会话建立消息、上下文修改消息等消息中。其中，该会话建立请求消息可以指示第一终端设备的第一QoS流承载多播业务的数据。
在一种情况下，该会话建立请求消息可以携带用于指示第一终端设备的第一QoS流承载多播业务的数据的指示信息。即在携带用于指示第一终端设备的第一QoS流承载多播业务的数据的指示信息的情况下，该会话建立请求消息要建立承载多播业务的数据的第一QoS流，在未携带用于指示第一终端设备的第一QoS流承载多播业务的数据的指示信息的情况下，该会话建立请求消息要建立承载单播业务的数据的第一QoS流。
在另一种情况下，该会话建立请求消息可以直接指示第一终端设备的第一QoS流承载多播业务的数据。即该会话建立请求消息指示第一终端设备的第一QoS流承载多播业务的数据情况下，该会话建立请求消息要建立的承载多播业务的数据的第一QoS流，在该会话建立请求消息未指示第一QoS流承载多播业务的数据的情况下，该会话建立请求消息要建立承载单播业务的数据的第一QoS流。
可选地，核心网设备向接入网设备发送用于建立第一终端设备的第一QoS流的会话建立请求消息之前，可以接收来自第一终端设备的用于建立接收第一业务的数据的第一QoS流的会话建立请求。
可选地，该会话建立请求消息还可以携带接入网设备接收第一业务的数据的地址信息，如接入网设备的IP地址、隧道标识信息、该一组终端设备中的某个终端设备的N3隧道标识信息或接入网设备的一个公共N3隧道标识信息。该地址信息用于接入网设备为第一终端设备建立第一终端设备的第一QoS流。其他详细描述参考步骤901。
1702、接入网设备建立与第一终端设备之间的第一无线承载。
接入网设备接收到来自核心网设备的用于建立第一终端设备的第一QoS流的会话建立请求消息之后，表明接入网设备与第一终端设备之间需要传输的数据为组播业务的数据，该组播业务的数据为第一业务的数据，可以建立与第一终端设备之间的第一无线承载。具体的描述可以参考步骤902。
由于传输的是组播业务的数据，该组播业务的数据可能通过G-RNTI调度给多个终端设备，因此，接入网设备可以为第一终端设备建立的第一无线承载不启动加密。由于不同的终端设备加密的密钥不同，一旦加密，将该组播业务的数据调度给多个终端设备后，多个终端设备中只有一个终端设备能够正确解密出该组播数据，其它终端设备无法解密出该组播数据，以致无法实现该组播业务的数据的组播传输。
1703、接入网设备关联第一无线承载与用于传输第一业务的数据的第一QoS流。
接入网设备建立与第一终端设备之间的第一无线承载之后，可以关联第一无线承载与用于传输第一业务的数据的第一QoS流，可以节省核心网设备与接入网设备之间传输第一业务的数据开销。多个终端设备都接收第一业务的数据时，采用一个N3QoS流可以避免多 个终端设备重复向同一个接入网设备发送第一业务的数据。该N3QoS流可以是公共QoS流，也可以是该一组终端设备中的一个终端设备的第一QoS流。其中，用于传输第一业务的数据的第一QoS流可以是步骤1601中描述的公共QoS流或第二终端设备的第一QoS流。在关联信息包含第一业务的数据对应的索引信息的情况下，接入网设备可以从该一组终端设备的第一QoS流中选择一个进行传输。如果没有此步骤，接入网设备仍然可以与核心网设备之间建立专用数据通道，这样，终端设备接收第一业务的数据时，针对每个终端设备，接入网设备与核心网设备之间有和终端设备有不同专用数据通道。第一业务的数据可以在这些专用通道上发送给接入网设备。其中，步骤1703为可选地的步骤。
1704、接入网设备向第一终端设备发送第一RNTI。
其中，详细描述请参考步骤904，在此不加赘述。
1705、接入网设备向第一终端设备发送第二RNTI。
其中，接入网设备根据关联关系向第一终端设备发送第二RNTI。详细描述请参考步骤905，在此不加赘述。
1706、接入网设备向第一终端设备发送配置信息。
其中，详细描述请参考步骤906，在此不加赘述。
1707、接入网设备使用第一RNTI和第二RNTI在第一无线承载上向第一终端设备调度第一业务的数据包。
其中，详细描述请参考步907，在此不加赘述。
基于图1所示的网络架构，请参阅图12，图12是本发明实施例公开的一种通信装置的结构示意图。其中，该通信装置可以为接入网设备或接入网设备中的芯片。如图12所示，该通信装置可以包括：
建立单元1201，用于为第一终端设备建立第一无线承载，第一无线承载用于传输第一业务；
分配单元1202，用于为第一终端设备分配第一RNTI和第二RNTI，第一RNTI用于向第一终端设备调度业务，第二RNTI用于向包括第一终端设备的一组终端设备调度第一业务；
发送单元1203，用于使用第一RNTI和第二RNTI在第一无线承载上向第一终端设备调度第一业务的数据包。
在一个实施例中，该通信装置还可以包括：
接收单元1204，用于接收来自核心网设备的业务建立请求消息，业务建立请求消息携带用于指示第一业务为多播业务的公共信息。
在一个实施例中，公共信息为多播业务的业务信息或地址信息。
在一个实施例中，该通信装置还可以包括：
关联单元1205，用于关联第一无线承载与第一公共数据通道，第一公共数据通道用于与核心网设备传输第一业务的数据。
在一个实施例中，发送单元1203具体用于：
使用第二RNTI在第一无线承载上向第一终端设备调度第一业务的数据包；
接收来自第一终端设备的用于指示第一业务的数据包传输失败的反馈信息；
使用第一RNTI在第一无线承载上向第一终端设备重传第一业务的数据包。
在一个实施例中，发送单元1203，还用于向第一终端设备发送第一进程与第二进程之间的关联关系，第一进程为用于初传第一业务的数据包的进程，第二进程为用于重传第一业务的数据包的进程。
在一个实施例中，发送单元1203，还用于向第一终端设备发送指示信息，该指示信息用于指示第二RNTI用于调度第一业务。
在一个实施例中，第一业务的数据包包括逻辑信道标识，逻辑信道标识用于指示第二RNTI传输的数据包为第一业务的数据包。
在一个实施例中，发送单元1203，还用于向第一终端设备发送第一配置信息，第一配置信息用于指示第一终端设备根据第一配置信息检测第二RNTI。
在一个实施例中，第一配置信息包括下面的一种或多种：
第二RNTI对应的BWP信息；
第二RNTI对应的CORESET信息；和
第二RNTI对应的搜索空间信息。
在一个实施例中，发送单元1203，还用于向资源管理模块发送用于指示第一业务的接收终端设备的数量的指示信息和/或第一业务使用的RNTI的配置信息；
接收单元1204，还用于接收来自资源管理模块的第一业务对应的第二配置信息，第二配置信息包括第二RNTI的配置信息；
发送单元1203，还用于向第一终端设备发送第二配置信息。
有关上述建立单元1201、分配单元1202、发送单元1203、接收单元1204和关联单元1205更详细的描述可以直接参考上述方法实施例中接入网设备的相关描述直接得到，这里不加赘述。
基于图1所示的网络架构，请参阅图13，图13是本发明实施例公开的另一种通信装置的结构示意图。其中，该通信装置可以为终端设备或终端设备中的芯片。如图13所示，该通信装置可以包括：
建立单元1301，用于建立与接入网设备之间的第一无线承载，第一无线承载用于传输第一业务；
接收单元1302，用于接收来自接入网设备的第一RNTI和第二RNTI，第一RNTI用于接收来自接入网设备向终端设备调度的业务，第二RNTI用于接收来自接入网设备向包括该终端设备的一组终端设备调度的第一业务；
接收单元1302，还用于使用第一RNTI和第二RNTI在第一无线承载上接收来自接入网设备调度的第一业务的数据包。
在一个实施例中，接收单元1302使用第一RNTI和第二RNTI在第一无线承载上接收来自接入网设备调度的第一业务的数据包包括：
使用第二RNTI在第一无线承载上接收来自接入网设备调度的第一业务的数据包；
向接入网设备发送用于指示第一业务的数据包传输失败的反馈信息；
使用第一RNTI在第一无线承载上接收来自接入网设备重传的第一业务的数据包。
在一个实施例中，接收单元1302，还用于接收来自接入网设备的第一进程与第二进程之间的关联关系，第一进程为用于初传第一业务的数据包的进程，第二进程为用于重传第一业务的数据包的进程；
接收单元1302使用第一RNTI在第一无线承载上接收来自接入网设备重传的第一业务的数据包包括：
根据关联关系使用第一RNTI在第一无线承载上接收来自接入网设备重传的第一业务的数据包。
在一个实施例中，该通信装置还可以包括确定单元1303，其中：
在一种情况下，接收单元1302，还用于接收来自接入网设备的第一指示信息，确定单元1303，用于根据第一指示信息确定第二RNTI用于调度第一业务；
在另一种情况下，确定单元1303，用于根据第一业务的数据包包括的逻辑信道标识确定第二RNTI传输的数据包为第一业务的数据包。
在一个实施例中，接收单元1302，还用于接收来自接入网设备的配置信息；
接收单元1302使用第二RNTI在第一无线承载上接收来自接入网设备调度的第一业务的数据包包括：
根据配置信息在第一无线承载上从第二RNTI上检测来自接入网设备的第一业务的数据包。
在一个实施例中，配置信息包括下面的一种或多种：
第二RNTI对应的BWP信息；
第二RNTI对应的CORESET信息；和
第二RNTI对应的搜索空间信息。
在一个实施例中，接收单元1302，还用于接收来自接入网设备的第二指示信息；
确定单元1303，还用于根据第二指示信息确定第一无线承载为用于传输第一业务的无线承载。
在一个实施例中，接收单元1302使用第一RNTI和第二RNTI在第一无线承载上接收来自接入网设备的第一业务的数据包包括：
使用第一RNTI接收来自接入网设备的第一业务的第一数据包；
使用第二RNTI接收来自接入网设备的第一业务的第二数据包；
将第一数据包和第二数据包合并到第一无线承载上。
在一个实施例中，接收单元1302将第一数据包和第二数据包合并到第一无线承载上包括：
在第一数据包和第二数据包为MAC层的数据包的情况下，将第一数据包和第二数据包包括的RLC PDU在RLC层合并到第一无线承载上；或者
在第一数据包和第二数据包为RLC层的数据包的情况下，将第一数据包和第二数据包包括的PDCP PDU在PDCP层合并到第一无线承载上。
在一个实施例中，接收单元1302将第一数据包和第二数据包包括的RLC PDU在RLC层合并到第一无线承载上包括：
将第一数据包包括的RLC PDU和第二数据包包括的RLC PDU进行排序和/或去重。
在一个实施例中，接收单元1302将第一数据包和第二数据包包括的RLC PDU在RLC层合并到第一无线承载上包括：
将第一数据包包括的RLC PDU和第二数据包包括的RLC PDU进行排序和/或去重。
有关上述建立单元1301、接收单元1302和确定单元1303更详细的描述可以直接参考上述方法实施例中终端设备的相关描述直接得到，这里不加赘述。
基于图1所示的网络架构，请参阅图14，图14是本发明实施例公开的又一种通信装置的结构示意图。如图14所示，该通信装置可以包括处理器1401、存储器1402、输入接口1403、输出接口1404和总线1405。存储器1402可以是独立存在的，可以通过总线1405与处理器1401相连接。存储器1402也可以和处理器1401集成在一起。其中，总线1405用于实现这些组件之间的连接。
在一个实施例中，该通信装置可以为接入网设备或接入网设备内的芯片，其中：
存储器1402中存储有一组计算机程序，处理器1401用于调用存储器1402中存储的计算机程序执行以下操作：
为第一终端设备建立第一无线承载，第一无线承载用于传输第一业务；
为第一终端设备分配第一RNTI和第二RNTI，第一RNTI用于向第一终端设备调度业务，第二RNTI用于向包括第一终端设备的一组终端设备调度第一业务；
输出接口1404，用于使用第一RNTI和第二RNTI在第一无线承载上向第一终端设备调度第一业务的数据包。
在一个实施例中，输入接口1403，用于接收来自核心网设备的业务建立请求消息，业务建立请求消息携带用于指示第一业务为多播业务的公共信息。
在一个实施例中，公共信息为多播业务的业务信息或地址信息。
在一个实施例中，处理器1401还用于调用存储器1402中存储的计算机程序执行以下操作：
关联第一无线承载与第一公共数据通道，第一公共数据通道用于与核心网设备传输第一业务的数据。
在一个实施例中，输出接口1404使用第一RNTI和第二RNTI在第一无线承载上向第一终端设备调度第一业务的数据包包括：
输出接口1404使用第二RNTI在第一无线承载上向第一终端设备调度第一业务的数据包；
输入接口1403接收来自第一终端设备的用于指示第一业务的数据包传输失败的反馈信息；
输出接口1404使用第一RNTI在第一无线承载上向第一终端设备重传第一业务的数据包。
在一个实施例中，输出接口1404，还用于向第一终端设备发送第一进程与第二进程之间的关联关系，第一进程为用于初传第一业务的数据包的进程，第二进程为用于重传第一业务的数据包的进程。
在一个实施例中，输出接口1404，还用于向第一终端设备发送指示信息，指示信息用 于指示第二RNTI用于调度第一业务。
在一个实施例中，第一业务的数据包包括逻辑信道标识，逻辑信道标识用于指示第二RNTI传输的数据包为第一业务的数据包。
在一个实施例中，输出接口1404，还用于向第一终端设备发送第一配置信息，第一配置信息用于指示第一终端设备根据第一配置信息检测第二RNTI。
在一个实施例中，第一配置信息包括下面的一种或多种：
第二RNTI对应的BWP信息；
第二RNTI对应的CORESET信息；和
第二RNTI对应的搜索空间信息。
在一个实施例中，输出接口1404，还用于向资源管理模块发送用于指示第一业务的接收终端设备的数量的指示信息和/或第一业务使用的RNTI的配置信息；
输入接口1403，还用于接收来自资源管理模块的第一业务对应的第二配置信息，第二配置信息包括第二RNTI的配置信息；
输出接口1404，还用于向第一终端设备发送第二配置信息。
其中，步骤401、步骤902-步骤903以及步骤1104-步骤1105可以由接入网设备中的处理器1401和存储器1402来执行；步骤901和步骤1103中的接收业务建立请求消息的步骤，步骤1102中接收第二配置信息的步骤可以由接入网设备中的输入接口1403来执行；步骤402-步骤404、步骤904-步骤907以及步骤1106-步骤1109可以由接入网设备中的输出接口1404来执行。
其中，建立单元1201、分配单元1202和关联单元1205可以由接入网设备中的处理器1401和存储器1402来实现，接收单元1204可以由接入网设备中的输入接口1403来实现，发送单元1203可以由接入网设备中的输出接口1404来实现。
上述接入网设备还可以用于执行前述方法实施例中接入网设备执行的各种方法，不再赘述。
在另一个实施例中，该通信装置可以为终端设备或终端设备内的芯片，其中：
存储器1402中存储有一组计算机程序，处理器1401用于调用存储器1402中存储的计算机程序执行以下操作：
建立与接入网设备之间的第一无线承载，第一无线承载用于传输第一业务；
输入接口1403，用于接收来自接入网设备的第一RNTI和第二RNTI，第一RNTI用于接收来自接入网设备向终端设备调度的业务，第二RNTI用于接收来自接入网设备向包括终端设备的一组终端设备调度的第一业务；
输入接口1403，还用于使用第一RNTI和第二RNTI在第一无线承载上接收来自接入网设备调度的第一业务的数据包。
在一个实施例中，输入接口1403使用第一RNTI和第二RNTI在第一无线承载上接收来自接入网设备调度的第一业务的数据包包括：
输入接口1403使用第二RNTI在第一无线承载上接收来自接入网设备调度的第一业务的数据包；
输出接口1404向接入网设备发送用于指示第一业务的数据包传输失败的反馈信息；
输入接口1403使用第一RNTI在第一无线承载上接收来自接入网设备重传的第一业务的数据包。
在一个实施例中，输入接口1403，还用于接收来自接入网设备的第一进程与第二进程之间的关联关系，第一进程为用于初传第一业务的数据包的进程，第二进程为用于重传第一业务的数据包的进程；
输入接口1403使用第一RNTI在第一无线承载上接收来自接入网设备重传的第一业务的数据包包括：
根据关联关系使用第一RNTI在第一无线承载上接收来自接入网设备重传的第一业务的数据包。
在一个实施例中，输入接口1403，还用于接收来自接入网设备的第一指示信息；
处理器1401还用于调用存储器1402中存储的计算机程序执行以下操作：
根据第一指示信息确定第二RNTI用于调度第一业务。
在一个实施例中，处理器1401还用于调用存储器1402中存储的计算机程序执行以下操作：
根据第一业务的数据包包括的逻辑信道标识确定第二RNTI传输的数据包为第一业务的数据包。
在一个实施例中，输入接口1403，还用于接收来自接入网设备的配置信息；
输入接口1403使用第二RNTI在第一无线承载上接收来自接入网设备调度的第一业务的数据包包括：
根据配置信息在第一无线承载上从第二RNTI上检测来自接入网设备的第一业务的数据包。
在一个实施例中，配置信息包括下面的一种或多种：
第二RNTI对应的BWP信息；
第二RNTI对应的CORESET信息；和
第二RNTI对应的搜索空间信息。
在一个实施例中，输入接口1403，还用于接收来自接入网设备的第二指示信息；
处理器1401还用于调用存储器1402中存储的计算机程序执行以下操作：
根据第二指示信息确定第一无线承载为用于传输第一业务的无线承载。
在一个实施例中，输入接口1403使用第一RNTI和第二RNTI在第一无线承载上接收来自接入网设备的第一业务的数据包包括：
输入接口1403使用第一RNTI接收来自接入网设备的第一业务的第一数据包；
输入接口1403使用第二RNTI接收来自接入网设备的第一业务的第二数据包；
处理器1401将第一数据包和第二数据包合并到第一无线承载上。
在一个实施例中，处理器1401将第一数据包和第二数据包合并到第一无线承载上包括：
在第一数据包和第二数据包为MAC层的数据包的情况下，将第一数据包和第二数据包包括的RLC PDU在RLC层合并到第一无线承载上；或者
在第一数据包和第二数据包为RLC层的数据包的情况下，将第一数据包和第二数据包包括的PDCP PDU在PDCP层合并到第一无线承载上。
在一个实施例中，处理器1401将第一数据包和第二数据包包括的RLC PDU在RLC层合并到第一无线承载上包括：
将第一数据包包括的RLC PDU和第二数据包包括的RLC PDU进行排序和/或去重。
在一个实施例中，处理器1401将第一数据包和第二数据包包括的PDCP PDU在PDCP层合并到第一无线承载上包括：
将第一数据包括的PDCP PDU和第二数据包包括的PDCP PDU进行排序和/或去重。
其中，步骤402、步骤904以及步骤1106中接收第一RNTI的步骤，步骤403、步骤905以及步骤1107中接收第二RNTI的步骤，步骤404、步骤907以及步骤1109中接收第一业务的数据包的步骤，步骤906和步骤1108中接收配置信息的步骤可以由终端设备中的输入接口1303来执行。
其中，建立单元1301和确定单元1303可以由终端设备中的处理器1401和存储器1402来实现，接收单元1302可以由终端设备中的输入接口1403来实现。
上述终端设备还可以用于执行前述方法实施例中终端设备执行的各种方法，不再赘述。
基于图1所示的网络架构，请参阅图15，图15是本发明实施例公开的又一种通信装置的结构示意图。如图15所示，该通信装置可以包括输入接口1501、逻辑电路1502和输出接口1503。输入接口1501与输出接口1503通过逻辑电路1502相连接。其中，输入接口1501用于接收来自其它通信装置的信息，输出接口1503用于向其它通信装置输出、调度或者发送信息。逻辑电路1502用于执行除输入接口1501与输出接口1503的操作之外的操作，例如实现上述实施例中处理器1401实现的功能。其中，该通信装置可以为接入网设备或接入网设备内的芯片，也可以为终端设备或终端设备内的芯片。其中，有关输入接口1501、逻辑电路1502和输出接口1503更详细的的描述可以直接参考上述图4、图9和图11所示的方法实施例中接入网设备或终端设备的相关描述直接得到，这里不加赘述。
本发明实施例还公开了一种计算机可读存储介质，该计算机可读存储介质上存储有计算机程序，该计算机程序运行时，实现如图4、图9和图11所示的通信方法。
以上所述的具体实施方式，对本申请的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本申请的具体实施方式而已，并不用于限定本申请的保护范围，凡在本申请的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本申请的保护范围之内。

Claims (48)

  1. 一种通信方法，其特征在于，包括：
    为第一终端设备建立第一无线承载，所述第一无线承载用于传输第一业务；
    为所述第一终端设备分配第一无线网络临时标识RNTI和第二RNTI，所述第一RNTI用于向所述第一终端设备调度业务，所述第二RNTI用于向包括所述第一终端设备的一组终端设备调度所述第一业务；
    使用所述第一RNTI和所述第二RNTI在所述第一无线承载上向所述第一终端设备调度所述第一业务的数据包。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    接收来自核心网设备的业务建立请求消息，所述业务建立请求消息携带用于指示所述第一业务为多播业务的公共信息。
  3. 根据权利要求2所述的方法，其特征在于，所述公共信息为多播业务的业务信息或地址信息。
  4. 根据权利要求2或3所述的方法，其特征在于，所述方法还包括：
    关联所述第一无线承载与第一公共数据通道，所述第一公共数据通道用于与所述核心网设备传输所述第一业务的数据。
  5. 根据权利要求1-4任一项所述的方法，其特征在于，所述使用所述第一RNTI和所述第二RNTI在所述第一无线承载上向所述第一终端设备调度所述第一业务的数据包包括：
    使用所述第二RNTI在所述第一无线承载上向所述第一终端设备调度所述第一业务的数据包；
    接收来自所述第一终端设备的用于指示所述数据包传输失败的反馈信息；
    使用所述第一RNTI在所述第一无线承载上向所述第一终端设备重传所述第一业务的数据包。
  6. 根据权利要求5所述的方法，其特征在于，所述方法还包括：
    向所述第一终端设备发送第一进程与第二进程之间的关联关系，所述第一进程为用于初传所述数据包的进程，所述第二进程为用于重传所述数据包的进程。
  7. 根据权利要求1-6任一项所述的方法，其特征在于，所述方法还包括：
    向所述第一终端设备发送指示信息，所述指示信息用于指示所述第二RNTI用于调度所述第一业务。
  8. 根据权利要求1-6任一项所述的方法，其特征在于，所述数据包包括逻辑信道标识，所述逻辑信道标识用于指示所述第二RNTI传输的数据包为所述第一业务的数据包。
  9. 根据权利要求1-8任一项所述的方法，其特征在于，所述方法还包括：
    向所述第一终端设备发送第一配置信息，所述第一配置信息用于指示所述第一终端设备根据所述第一配置信息检测所述第二RNTI。
  10. 根据权利要求9所述的方法，其特征在于，所述第一配置信息包括下面的一种或多种：
    所述第二RNTI对应的带宽部分BWP信息；
    所述第二RNTI对应的控制资源集CORESET信息；和
    所述第二RNTI对应的搜索空间信息。
  11. 根据权利要求1-10任一项所述的方法，其特征在于，所述方法还包括：
    向资源管理模块发送用于指示所述第一业务的接收终端设备的数量的指示信息和/或所述第一业务使用的RNTI的配置信息；
    接收来自所述资源管理模块的所述第一业务对应的第二配置信息，所述第二配置信息包括所述第二RNTI的配置信息；
    向所述第一终端设备发送所述第二配置信息。
  12. 一种通信方法，其特征在于，包括：
    建立与接入网设备之间的第一无线承载，所述第一无线承载用于传输第一业务；
    接收来自所述接入网设备的第一RNTI和第二RNTI，所述第一RNTI用于接收来自所述接入网设备向终端设备调度的业务，所述第二RNTI用于接收来自所述接入网设备向包括所述终端设备的一组终端设备调度的所述第一业务；
    使用所述第一RNTI和所述第二RNTI在所述第一无线承载上接收来自所述接入网设备调度的所述第一业务的数据包。
  13. 根据权利要求12所述的方法，其特征在于，所述使用所述第一RNTI和所述第二RNTI在所述第一无线承载上接收来自所述接入网设备调度的所述第一业务的数据包包括：
    使用所述第二RNTI在所述第一无线承载上接收来自所述接入网设备调度的所述第一业务的数据包；
    向所述接入网设备发送用于指示所述数据包传输失败的反馈信息；
    使用所述第一RNTI在所述第一无线承载上接收来自所述接入网设备重传的所述第一业务的数据包。
  14. 根据权利要求12或13所述的方法，其特征在于，所述方法还包括：
    接收来自所述接入网设备的第一进程与第二进程之间的关联关系，所述第一进程为用于初传所述数据包的进程，所述第二进程为用于重传所述数据包的进程；
    所述使用所述第一RNTI在所述第一无线承载上接收来自所述接入网设备重传的所述第一业务的数据包包括：
    根据所述关联关系使用所述第一RNTI在所述第一无线承载上接收来自所述接入网设备重传的所述第一业务的数据包。
  15. 根据权利要求12-14任一项所述的方法，其特征在于，所述方法还包括：
    接收来自所述接入网设备的第一指示信息；
    根据所述第一指示信息确定所述第二RNTI用于调度所述第一业务。
  16. 根据权利要求12-14任一项所述的方法，其特征在于，所述方法还包括：
    根据所述数据包包括的逻辑信道标识确定所述第二RNTI传输的数据包为所述第一业务的数据包。
  17. 根据权利要求13-16任一项所述的方法，其特征在于，所述方法还包括：
    接收来自所述接入网设备的配置信息；
    所述使用所述第二RNTI在所述第一无线承载上接收来自所述接入网设备调度的所述第一业务的数据包包括：
    根据所述配置信息在所述第一无线承载上从所述第二RNTI上检测来自所述接入网设备的所述第一业务的数据包。
  18. 根据权利要求17所述的方法，其特征在于，所述配置信息包括下面的一种或多种：
    所述第二RNTI对应的BWP信息；
    所述第二RNTI对应的CORESET信息；和
    所述第二RNTI对应的搜索空间信息。
  19. 根据权利要求12-18任一项所述的方法，其特征在于，所述方法还包括：
    接收来自所述接入网设备的第二指示信息；
    根据所述第二指示信息确定所述第一无线承载为用于传输所述第一业务的无线承载。
  20. 根据权利要求12所述的方法，其特征在于，所述使用所述第一RNTI和所述第二RNTI在所述第一无线承载上接收来自所述接入网设备的所述第一业务的数据包包括：
    使用所述第一RNTI接收来自所述接入网设备的所述第一业务的第一数据包；
    使用所述第二RNTI接收来自所述接入网设备的所述第一业务的第二数据包；
    将所述第一数据包和所述第二数据包合并到所述第一无线承载上。
  21. 根据权利要求20所述的方法，其特征在于，所述将所述第一数据包和所述第二数据包合并到所述第一无线承载上包括：
    在所述第一数据包和所述第二数据包为媒体访问控制地址MAC层的数据包的情况下，将所述第一数据包和所述第二数据包包括的无线链路控制RLC协议数据单元PDU在RLC层合并到所述第一无线承载上；或者
    在所述第一数据包和所述第二数据包为RLC层的数据包的情况下，将所述第一数据包和所述第二数据包包括的分组数据汇聚协议PDCP PDU在PDCP层合并到所述第一无线承载上。
  22. 根据权利要求21所述的方法，其特征在于，所述将所述第一数据包和所述第二数据包包括的RLC PDU在RLC层合并到所述第一无线承载上包括：
    将所述第一数据包包括的RLC PDU和所述第二数据包包括的RLC PDU进行排序和/或去重。
  23. 根据权利要求21所述的方法，其特征在于，所述将所述第一数据包和所述第二数据包包括的PDCP PDU在PDCP层合并到所述第一无线承载上包括：
    将所述第一数据包括的PDCP PDU和所述第二数据包包括的PDCP PDU进行排序和/或去重。
  24. 一种通信装置，其特征在于，包括：
    建立单元，用于为第一终端设备建立第一无线承载，所述第一无线承载用于传输第一业务；
    分配单元，用于为所述第一终端设备分配第一RNTI和第二RNTI，所述第一RNTI用于向所述第一终端设备调度业务，所述第二RNTI用于向包括所述第一终端设备的一组终端设 备调度所述第一业务；
    发送单元，用于使用所述第一RNTI和所述第二RNTI在所述第一无线承载上向所述第一终端设备调度所述第一业务的数据包。
  25. 根据权利要求24所述的装置，其特征在于，所述装置还包括：
    接收单元，用于接收来自核心网设备的业务建立请求消息，所述业务建立请求消息携带用于指示所述第一业务为多播业务的公共信息。
  26. 根据权利要求25所述的装置，其特征在于，所述公共信息为多播业务的业务信息或地址信息。
  27. 根据权利要求25或26所述的装置，其特征在于，所述装置还包括：
    关联单元，用于关联所述第一无线承载与第一公共数据通道，所述第一公共数据通道用于与所述核心网设备传输所述第一业务的数据。
  28. 根据权利要求24-27任一项所述的装置，其特征在于，所述发送单元具体用于：
    使用所述第二RNTI在所述第一无线承载上向所述第一终端设备调度所述第一业务的数据包；
    接收来自所述第一终端设备的用于指示所述数据包传输失败的反馈信息；
    使用所述第一RNTI在所述第一无线承载上向所述第一终端设备重传所述第一业务的数据包。
  29. 根据权利要求28所述的装置，其特征在于，所述发送单元，还用于向所述第一终端设备发送第一进程与第二进程之间的关联关系，所述第一进程为用于初传所述数据包的进程，所述第二进程为用于重传所述数据包的进程。
  30. 根据权利要求24-29任一项所述的装置，其特征在于，所述发送单元，还用于向所述第一终端设备发送指示信息，所述指示信息用于指示所述第二RNTI用于调度所述第一业务。
  31. 根据权利要求24-29任一项所述的装置，其特征在于，所述数据包包括逻辑信道标识，所述逻辑信道标识用于指示所述第二RNTI传输的数据包为所述第一业务的数据包。
  32. 根据权利要求24-31任一项所述的装置，其特征在于，所述发送单元，还用于向所述第一终端设备发送第一配置信息，所述第一配置信息用于指示所述第一终端设备根据所述第一配置信息检测所述第二RNTI。
  33. 根据权利要求32所述的装置，其特征在于，所述第一配置信息包括下面的一种或多种：
    所述第二RNTI对应的BWP信息；
    所述第二RNTI对应的CORESET信息；和
    所述第二RNTI对应的搜索空间信息。
  34. 根据权利要求24-33任一项所述的装置，其特征在于，所述发送单元，还用于向资源管理模块发送用于指示所述第一业务的接收终端设备的数量的指示信息和/或所述第一业务使用的RNTI的配置信息；
    所述接收单元，还用于接收来自所述资源管理模块的所述第一业务对应的第二配置信息，所述第二配置信息包括所述第二RNTI的配置信息；
    所述发送单元，还用于向所述第一终端设备发送所述第二配置信息。
  35. 一种通信装置，其特征在于，包括：
    建立单元，用于建立与接入网设备之间的第一无线承载，所述第一无线承载用于传输第一业务；
    接收单元，用于接收来自所述接入网设备的第一RNTI和第二RNTI，所述第一RNTI用于接收来自所述接入网设备向终端设备调度的业务，所述第二RNTI用于接收来自所述接入网设备向包括所述终端设备的一组终端设备调度的所述第一业务；
    所述接收单元，还用于使用所述第一RNTI和所述第二RNTI在所述第一无线承载上接收来自所述接入网设备调度的所述第一业务的数据包。
  36. 根据权利要求35所述的装置，其特征在于，所述接收单元使用所述第一RNTI和所述第二RNTI在所述第一无线承载上接收来自所述接入网设备调度的所述第一业务的数据包包括：
    使用所述第二RNTI在所述第一无线承载上接收来自所述接入网设备调度的所述第一业务的数据包；
    向所述接入网设备发送用于指示所述数据包传输失败的反馈信息；
    使用所述第一RNTI在所述第一无线承载上接收来自所述接入网设备重传的所述第一业务的数据包。
  37. 根据权利要求35或36所述的装置，其特征在于，所述接收单元，还用于接收来自所述接入网设备的第一进程与第二进程之间的关联关系，所述第一进程为用于初传所述数据包的进程，所述第二进程为用于重传所述数据包的进程；
    所述接收单元使用所述第一RNTI在所述第一无线承载上接收来自所述接入网设备重传的所述第一业务的数据包包括：
    根据所述关联关系使用所述第一RNTI在所述第一无线承载上接收来自所述接入网设备重传的所述第一业务的数据包。
  38. 根据权利要求35-37任一项所述的装置，其特征在于，所述接收单元，还用于接收来自所述接入网设备的第一指示信息；
    所述装置还包括：
    第一确定单元，用于根据所述第一指示信息确定所述第二RNTI用于调度所述第一业务。
  39. 根据权利要求35-37任一项所述的装置，其特征在于，所述装置还包括：
    第二确定单元，用于根据所述数据包包括的逻辑信道标识确定所述第二RNTI传输的数据包为所述第一业务的数据包。
  40. 根据权利要求35-39任一项所述的装置，其特征在于，所述接收单元，还用于接收来自所述接入网设备的配置信息；
    所述接收单元使用所述第二RNTI在所述第一无线承载上接收来自所述接入网设备调度的所述第一业务的数据包包括：
    根据所述配置信息在所述第一无线承载上从所述第二RNTI上检测来自所述接入网设备的所述第一业务的数据包。
  41. 根据权利要求40所述的装置，其特征在于，所述配置信息包括下面的一种或多种：
    所述第二RNTI对应的BWP信息；
    所述第二RNTI对应的CORESET信息；和
    所述第二RNTI对应的搜索空间信息。
  42. 根据权利要求35-41任一项所述的装置，其特征在于，所述接收单元，还用于接收来自所述接入网设备的第二指示信息；
    所述装置还包括：
    第三确定单元，用于根据所述第二指示信息确定所述第一无线承载为用于传输所述第一业务的无线承载。
  43. 根据权利要求35所述的装置，其特征在于，所述接收单元使用所述第一RNTI和所述第二RNTI在所述第一无线承载上接收来自所述接入网设备的所述第一业务的数据包包括：
    使用所述第一RNTI接收来自所述接入网设备的所述第一业务的第一数据包；
    使用所述第二RNTI接收来自所述接入网设备的所述第一业务的第二数据包；
    将所述第一数据包和所述第二数据包合并到所述第一无线承载上。
  44. 根据权利要求43所述的装置，其特征在于，所述接收单元将所述第一数据包和所述第二数据包合并到所述第一无线承载上包括：
    在所述第一数据包和所述第二数据包为MAC层的数据包的情况下，将所述第一数据包和所述第二数据包包括的RLC PDU在RLC层合并到所述第一无线承载上；或者
    在所述第一数据包和所述第二数据包为RLC层的数据包的情况下，将所述第一数据包和所述第二数据包包括的PDCP PDU在PDCP层合并到所述第一无线承载上。
  45. 根据权利要求44所述的装置，其特征在于，所述接收单元将所述第一数据包和所述第二数据包包括的RLC PDU在RLC层合并到所述第一无线承载上包括：
    将所述第一数据包包括的RLC PDU和所述第二数据包包括的RLC PDU进行排序和/或去重。
  46. 根据权利要求44所述的装置，其特征在于，所述接收单元将所述第一数据包和所述第二数据包包括的PDCP PDU在PDCP层合并到所述第一无线承载上包括：
    将所述第一数据包括的PDCP PDU和所述第二数据包包括的PDCP PDU进行排序和/或去重。
  47. 一种通信装置，其特征在于，包括处理器、存储器、输入接口和输出接口，所述输入接口用于接收来自所述通信装置之外的其它通信装置的信息，所述输出接口用于向所述通信装置之外的其它通信装置输出信息，所述处理器调用所述存储器中存储的计算机程序实现如权利要求1-23任一项所述的方法。
  48. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有计算机程序，当所述计算机程序被运行时，实现如权利要求1-23任一项所述的方法。
PCT/CN2020/105575 2019-07-31 2020-07-29 一种通信方法及装置 WO2021018213A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20846975.9A EP3975649A4 (en) 2019-07-31 2020-07-29 Communication method and apparatus
US17/568,097 US20220124840A1 (en) 2019-07-31 2022-01-04 Communication method and apparatus

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201910704742 2019-07-31
CN201910704742.5 2019-07-31
CN201910866760.3 2019-09-12
CN201910866760.3A CN112312575A (zh) 2019-07-31 2019-09-12 一种通信方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/568,097 Continuation US20220124840A1 (en) 2019-07-31 2022-01-04 Communication method and apparatus

Publications (1)

Publication Number Publication Date
WO2021018213A1 true WO2021018213A1 (zh) 2021-02-04

Family

ID=74228823

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/105575 WO2021018213A1 (zh) 2019-07-31 2020-07-29 一种通信方法及装置

Country Status (3)

Country Link
US (1) US20220124840A1 (zh)
EP (1) EP3975649A4 (zh)
WO (1) WO2021018213A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022240184A1 (ko) * 2021-05-11 2022-11-17 엘지전자 주식회사 무선 통신 시스템에서 그룹 공통 전송을 위한 harq 기반 송수신 방법 및 장치

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103491643A (zh) * 2012-06-12 2014-01-01 电信科学技术研究院 组通信连接的建立方法和设备
CN105900355A (zh) * 2014-01-08 2016-08-24 高通股份有限公司 小型区域mbsfn增强
US20180343694A1 (en) * 2017-05-23 2018-11-29 Nec Corporation Base station, terminal apparatus, method
CN109429188A (zh) * 2017-08-21 2019-03-05 成都鼎桥通信技术有限公司 基于Btrunc的集群用户测量GAP规避方法及设备
CN109982266A (zh) * 2017-12-28 2019-07-05 华为技术有限公司 一种通信方法、及相关产品

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
NZ588002A (en) * 2008-03-19 2013-09-27 Ericsson Telefon Ab L M Improved uplink scheduling in a cellular system
US9277533B2 (en) * 2012-05-17 2016-03-01 Vid Scale, Inc. Scalable video coding over simultaneous unicast/multicast LTE DL shared channel
WO2016119198A1 (en) * 2015-01-30 2016-08-04 Qualcomm Incorporated Support of transmission mode and impact on pdcch blind decodes of ptm (point-to-multipoint) transmission
CN105992158B (zh) * 2015-02-13 2020-09-08 中兴通讯股份有限公司 单小区多媒体广播多播业务mbms的调度方法及装置
EP3270623A4 (en) * 2015-04-10 2018-04-11 Kyocera Corporation Network device, user terminal, and base station
WO2016163548A1 (ja) * 2015-04-10 2016-10-13 京セラ株式会社 基地局及びユーザ端末

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103491643A (zh) * 2012-06-12 2014-01-01 电信科学技术研究院 组通信连接的建立方法和设备
CN105900355A (zh) * 2014-01-08 2016-08-24 高通股份有限公司 小型区域mbsfn增强
US20180343694A1 (en) * 2017-05-23 2018-11-29 Nec Corporation Base station, terminal apparatus, method
CN109429188A (zh) * 2017-08-21 2019-03-05 成都鼎桥通信技术有限公司 基于Btrunc的集群用户测量GAP规避方法及设备
CN109982266A (zh) * 2017-12-28 2019-07-05 华为技术有限公司 一种通信方法、及相关产品

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3975649A4

Also Published As

Publication number Publication date
EP3975649A4 (en) 2022-06-29
US20220124840A1 (en) 2022-04-21
EP3975649A1 (en) 2022-03-30

Similar Documents

Publication Publication Date Title
CN113853808B (zh) 一种多播传输控制方法以及相关设备
US20230422346A1 (en) Multicast service receiving method, multicast service configuration method, terminal, and network side device
WO2019057072A1 (zh) 数据传输的方法及装置
CN112312575A (zh) 一种通信方法及装置
WO2021164400A1 (zh) 数据流传输方法、终端和网络侧设备
US20230262533A1 (en) Communication control method
US20230091236A1 (en) Communication control method and user equipment
WO2022239690A1 (ja) 通信制御方法及びユーザ装置
JP7549077B2 (ja) 通信制御方法、ユーザ装置及びプロセッサ
WO2021018213A1 (zh) 一种通信方法及装置
WO2022006888A1 (zh) 一种mbs业务的接收方法及装置、终端设备
WO2022198415A1 (zh) 提高mbs业务可靠性的方法及装置、终端设备、网络设备
WO2009132255A2 (en) Method and system for resolving inter-mbs-zone performance issues using mbs service groups
KR101268580B1 (ko) 멀티미디어 브로드캐스트 멀티캐스트 서비스 제공 방법 및 그 장치
JP7506227B2 (ja) 基地局、方法及びシステム
JP7571174B2 (ja) 通信制御方法、ユーザ装置、プロセッサ及び基地局
JP7425259B2 (ja) 通信制御方法及び基地局
US20230188950A1 (en) Communication control method
JP7508634B2 (ja) 通信制御方法、基地局、ユーザ装置及びプロセッサ
JP7508576B2 (ja) 通信制御方法
WO2024034564A1 (ja) 通信方法、集約ユニット、及び分散ユニット
WO2022006882A1 (zh) Mbs业务的传输方法及装置、网络设备、终端设备
WO2022165720A1 (zh) 提高mbs业务可靠性的方法及装置、终端设备、网络设备
WO2024162424A1 (ja) 通信方法
WO2023097613A1 (zh) 一种信息确定方法及装置、终端设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20846975

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020846975

Country of ref document: EP

Effective date: 20211222

NENP Non-entry into the national phase

Ref country code: DE