Data transmission method, device, and system

The data transmission method in 3GPP networks addresses the issue of incomplete multicast data delivery by triggering communication connections for terminals in idle or inactive states, ensuring all terminals receive the data without loss.

JP7596506B2Active Publication Date: 2024-12-09HUAWEI TECH CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
JP2023504424
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2020-07-23
Filing Date
2021-07-23
Publication Date
2024-12-09
Estimated Expiration
2041-07-23

AI Technical Summary

Technical Problem

In 3GPP networks, terminals in idle or inactive states cannot receive multicast service data due to severed communication connections with the access network device, leading to incomplete delivery of multicast service data to all terminals in a group.

Method used

A data transmission method involving session management network elements sending notification information to user plane network elements when multicast service data arrives, triggering the establishment of communication connections with terminals in preset states, ensuring all terminals receive the data without loss.

Benefits of technology

Ensures that all terminals in a multicast group receive multicast service data by establishing communication connections with terminals in idle or inactive states, preventing data loss and ensuring complete delivery.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007596506000001
    Figure 0007596506000001
  • Figure 0007596506000002
    Figure 0007596506000002
  • Figure 0007596506000003
    Figure 0007596506000003
Patent Text Reader

Abstract

The present application discloses a data transmission method, apparatus, and system for solving a problem in which a terminal in a preset state within a multicast group cannot receive multicast service data. The method is applied when at least one terminal in a preset state exists in a multicast group corresponding to a first multicast service. The method includes: a session management network element notifying a user plane network element to transmit notification information to the session management network element when data of the first multicast service arrives at the user plane network element; and the session management network element triggering establishment of a communication connection between the terminal in the preset state and an access network device after receiving the notification information, and notifying the user plane network element to transmit data of the first multicast service after the establishment of the communication connection is completed. Alternatively, after receiving the data of the first multicast service, the access network device buffers the data of the first multicast service, pages the terminal in the preset state, and transmits the buffered data of the first multicast service after the establishment of the communication connection between the terminal and the access network device is completed.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] TECHNICAL FIELD Embodiments of the present application relate to the field of communication technology, and in particular to a data transmission method, apparatus and system. [Background technology]

[0002] In 3rd generation partnership project (3GPP) networks, there is a requirement that a network side device transmits multicast service data to multiple terminals (e.g., terminals in a multicast group) over the same communication connection, i.e., a point-to-multipoint data transmission requirement.

[0003] To meet this requirement, in the prior art, the multicast service data sent to the multiple terminals share the same user plane function (UPF) and downlink tunnel between the UPF and the access network device. The downlink tunnel may be any downlink tunnel among the multiple downlink tunnels corresponding to the multiple terminals, and the downlink tunnel information for identifying the downlink tunnel is stored in the UPF. After the application server sends the multicast service data to the UPF, the UPF can send the multicast service data to the access network device through the downlink tunnel based on the locally stored downlink tunnel information, and the access network device sends the multicast service data to the multiple terminals.

[0004] However, in the communication process, the terminal may be in a connected state, an idle state, or an inactive state. When a terminal having a multicast service requirement is in an idle state or an inactive state, the communication connection between the terminal and the access network device is disconnected, and the terminal cannot receive the multicast service data transmitted by the access network device. As a result, it cannot be guaranteed that all terminals in the multicast group receive the multicast service data. Summary of the Invention [Means for solving the problem]

[0005] The embodiments of the present application provide a data transmission method, apparatus and system to solve the problem that a terminal in an idle or inactive state cannot receive multicast service data.

[0006] In order to achieve the aforementioned objectives, the following technical solutions are used in the embodiments of this application.

[0007] According to a first aspect of an embodiment of the present application, a data transmission method is provided, the method including: transmitting first information by a session management network element to a user plane network element when there is at least one terminal in a preset state in a multicast group corresponding to a first multicast service, the first information being used by the user plane network element to transmit notification information to the session management network element when data of the first multicast service arrives at the user plane network element; receiving notification information from the user plane network element by the session management network element, the notification information indicating that data of the first multicast service has arrived at the user plane network element; and transmitting second information to a mobility management network element based on the notification information, the second information being for triggering establishment of a communication connection between the first terminal and a first access network device, the first terminal belonging to at least one terminal in the preset state.

[0008] The preset states include an idle state, an inactive state, or a state in which there is no communication connection to the access network device for transmitting data of the first multicast service.

[0009] Based on the method according to the first aspect, when there is at least one terminal in a preset state in a multicast group corresponding to a multicast service, the session management network element can send first information to a user plane network element to instruct the user plane network element to send notification information to the session management network element when data of the first multicast service arrives at the user plane network element, and subsequently trigger the establishment of a communication connection between the terminal in the preset state and the access network device when the data of the first multicast service arrives at the user plane network element. In this way, after the establishment of the communication connection is completed, the data of the first multicast service is transmitted to the terminals in the multicast group via the communication connection between the access network device and the terminal. This avoids the problem that the terminal cannot receive the multicast service data when the communication connection between the terminal and the access network device for transmitting the multicast service data is disconnected because the terminal is in a preset state, and ensures that all terminals in the multicast group can receive the multicast service data without loss.

[0010] In a possible design, for at least one terminal in the preset state, e.g., another terminal belonging to the second terminal, the second information is further for triggering establishment of a communication connection between the second terminal and the second access network device. Based on the possible design, in order to reduce signaling overhead, establishment of communication connections between multiple terminals and the access network device may be triggered by using one piece of information.

[0011] In a possible design, the first information includes first identification information for identifying data of the first multicast service. Based on this possible design, the identification information indicating the data of the first multicast service is carried in the first information to explicitly instruct the user plane network element to send notification information to the session management network element when the data of the first multicast service arrives at the user plane network element, and the user plane network element does not need to indirectly decide to send notification information to the session management network element based on the first information, thereby simplifying the system design.

[0012] In a possible design, the method further includes a step of sending, by the session management network element, third information to a user plane network element when all terminals in a multicast group corresponding to the first multicast service have a communication connection to the access network device, the third information being for informing the user plane network element to send data of the first multicast service, thereby ensuring that all terminals in the multicast group receive the multicast service data without loss.

[0013] In a possible design, the method further includes a step of transmitting, by the session management network element, third information to the user plane network element when all terminals of the at least one terminal in the preset state have a communication connection to the access network device, the third information being for informing the user plane network element to transmit data of the first multicast service, thereby at least ensuring that the multicast service data is received via the communication connection when establishment of the communication connection between all terminals in the preset state and the access network device is completed.

[0014] In a possible design, after the step of transmitting the second information to the mobility management network element, the method further includes a step of transmitting, by the session management network element, third information to the user plane network element based on a first preset waiting duration, the third information being for notifying the user plane network element to transmit data of the first multicast service. Based on the possible design, a waiting duration for the session management network element to transmit the third information to the user plane network element can be designed in advance. After the waiting duration expires, the third information is transmitted to the user plane network element, thereby simplifying the system design.

[0015] In a possible design, the third information includes second identification information for identifying data of the first multicast service. Based on the possible design, the identification information for identifying data of the first multicast service is carried in the third information and explicitly indicated to the user plane network element, so that the user plane network element directly knows the data to be transmitted of the first multicast service based on the identification information, and the user plane network element does not need to indirectly determine the data to be transmitted of the first multicast service. This simplifies the design complexity of the user plane network element.

[0016] In a possible design, the method further includes receiving, by the session management network element, fourth information from the mobility management network element and for deactivating user plane transmission resources of the first terminal, and determining that the first terminal is in a preset state based on the fourth information. Based on a possible design, when the terminal is in the preset state, the information for deactivating the user plane transmission resources may be further transmitted to the session management network element, so that the session management network element knows that the terminal corresponding to the user plane transmission resources is in the preset state, thereby simplifying the system design.

[0017] According to a second aspect, the present application provides a communication device. The communication device may be a session management network element, or a chip or system-on-chip in the session management network element. The communication device may implement the functions performed by the communication device according to the first aspect, or a possible design of the first aspect. The functions may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions. For example, the communication device may include a transmitting unit and a receiving unit.

[0018] The sending unit is configured to send first information to the user plane network element when there is at least one terminal in a preset state in a multicast group corresponding to the first multicast service, and the first information is used by the user plane network element to send notification information to the session management network element when data of the first multicast service arrives at the user plane network element.

[0019] The receiving unit is configured to receive notification information from the user plane network element, where the notification information indicates that data of the first multicast service has arrived at the user plane network element.

[0020] The sending unit is further configured to send second information to the mobility management network element based on the notification information, the second information being for triggering establishment of a communication connection between the first terminal and the first access network device, the first terminal belonging to at least one terminal in a preset state.

[0021] The preset states include an idle state, an inactive state, or a state in which there is no communication connection to the access network device for transmitting data of the first multicast service. For specific implementation forms of each unit of the communication device, please refer to the operation function of the session management network element in the data transmission method according to the first aspect or any one of the possible designs of the first aspect. Details will not be described again here. The provided communication device can achieve the same beneficial effects as the first aspect or any one of the possible designs of the first aspect.

[0022] According to a third aspect, there is provided a communications device, the communications device including a processor and a memory, the memory configured to store computer-executable instructions, and wherein, when the communications device is operated, the processor executes the computer-executable instructions stored in the memory, such that the communications device performs a data transmission method according to the first aspect or any one of the possible designs of the first aspect.

[0023] According to a fourth aspect, there is provided a computer readable storage medium storing instructions which, when executed on a computer, enable the computer to perform a data transmission method according to the first aspect or any one of its possible designs.

[0024] According to a fifth aspect, there is provided a computer program product comprising instructions which, when run on a computer, enable the computer to perform a data transmission method according to the first aspect or any one of the possible designs of the first aspect.

[0025] According to a sixth aspect, a communication device is provided. The communication device may be a chip system, and the chip system may include a processor and a communication interface configured to support the communication device in implementing the functionality according to the first aspect or any one of the possible designs of the first aspect. For example, the processor transmits first information to a user plane network element via the communication interface when there is at least one terminal in a preset state in a multicast group corresponding to a first multicast service, the first information being used by the user plane network element to transmit notification information to a session management network element when data of the first multicast service arrives at the user plane network element, receives notification information from the user plane network element, the notification information indicating that data of the first multicast service has arrived at the user plane network element, transmits second information to a mobility management network element based on the notification information, the second information being for triggering establishment of a communication connection between the first terminal and the first access network device, the first terminal belonging to at least one terminal in the preset state. In a possible design, the chip system further includes a memory. The memory is configured to store program instructions and data required for the communication device. A chip system may include a chip, or may include a chip and other individual components.

[0026] For the technical effects achieved by any one of the designs of the third to sixth aspects, please refer to the technical effects achieved by the first aspect or any one of the possible designs of the first aspect. Details will not be described again.

[0027] According to a seventh aspect, an embodiment of the present application provides another data transmission method. The method may include the steps of: receiving, by a user plane network element, first information from a session management network element, the first information being used by the user plane network element to send notification information to the session management network element when data of a first multicast service arrives at the user plane network element; and after receiving the data of the first multicast service, sending notification information to the session management network element based on the first information, the notification information indicating that data of the first multicast service has arrived at the user plane network element. In this way, after receiving the notification message, the session management network element triggers the establishment of a communication connection between the terminal in the preset state and the access network device. This ensures that the terminal in the preset state receives the data of the first multicast service without loss via the communication connection.

[0028] Based on the method according to the seventh aspect, when there is at least one terminal in a preset state in a multicast group corresponding to a multicast service, the user plane network element, under the instruction of the session management network element, can notify the session management network element when data arrives at the user plane network element, so that the session management network element triggers the establishment of a communication connection between the terminal in the preset state and the access network device. In this way, after the establishment of the communication connection is completed, the data of the first multicast service is transmitted to the terminals in the multicast group via the communication connection between the access network device and the terminal. This avoids the problem that the terminal cannot receive the multicast service data when the communication connection between the terminal and the access network device for transmitting the multicast service data is disconnected because the terminal is in a preset state, and ensures that all terminals in the multicast group can receive the multicast service data without loss.

[0029] In a possible design, the method further includes: after receiving the data of the first multicast service, the user plane network element buffers the data of the first multicast service, so that the buffered data of the first multicast service is subsequently transmitted after the establishment of the communication connection is completed. In this way, when the data of the first multicast service arrives at the user plane network element, the data is stored through buffering, to avoid the problem that the terminal in the preset state misses (or cannot receive) the data of the first multicast service delivered during this period.

[0030] In a possible design, the first information includes first identification information for identifying data of the first multicast service. In other words, the user plane network element is explicitly instructed to monitor whether data of the first multicast service has arrived by using the identification information, and to notify the session management network element when the data of the first multicast service has arrived. This simplifies the system design.

[0031] In a possible design, the method further includes receiving, by the user plane network element, third information from the session management network element for informing the user plane network element to transmit data of the first multicast service, and transmitting the data of the first multicast service based on the third information. In other words, after the establishment of the communication connection is completed, the user plane network element delivers the multicast service data when the session management network element notifies the user plane network element to deliver the data of the first multicast service, thereby avoiding failure of transmission of the multicast service data.

[0032] In a possible design, the third information includes second identification information for identifying the data of the first multicast service. In other words, the user plane network element is explicitly instructed to deliver the data of the first multicast service by using the identification information. This simplifies the system design.

[0033] According to an eighth aspect, there is provided a communication device. The communication device may be a user plane network element, or a chip or system-on-chip in the user plane network element. The communication device may implement functions performed by the user plane network element according to the seventh aspect, or possible designs of the seventh aspect. The functions may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions. For example, the communication device may include a receiving unit and a transmitting unit.

[0034] The receiving unit is configured to receive first information from the session management network element, the first information being used by the user plane network element to send notification information to the session management network element when data of the first multicast service arrives at the user plane network element, and to receive the data of the first multicast service.

[0035] The sending unit is configured to send notification information to the session management network element based on the first information, where the notification information indicates that data of the first multicast service has arrived at the user plane network element.

[0036] For a specific implementation form of the communication device, please refer to the operation function of the user plane network element in the data transmission method according to the seventh aspect or any one of the possible designs of the seventh aspect. The seventh aspect or any one of the possible designs of the seventh aspect may be correspondingly implemented by a receiving unit and a transmitting unit included in the communication device.

[0037] According to a ninth aspect, there is provided a communications device, the communications device including a processor and a memory, the memory configured to store computer-executable instructions, and when the communications device is operated, the processor executes the computer-executable instructions stored in the memory, such that the communications device performs the data transmission method according to the seventh aspect or any one of the possible designs of the seventh aspect.

[0038] According to a tenth aspect, there is provided a computer readable storage medium storing instructions which, when executed on a computer, enable the computer to perform a data transmission method according to the seventh aspect or any one of the possible designs of the seventh aspect.

[0039] According to an eleventh aspect, there is provided a computer program product comprising instructions, which when executed on a computer, enable the computer to perform a data transmission method according to the seventh aspect or any one of the possible designs of the seventh aspect.

[0040] According to a twelfth aspect, a chip system is provided. The chip system includes a processor and a communication interface configured to support a communication device in implementing functions in the aforementioned aspects. For example, the processor receives first information from a session management network element via the communication interface, the first information being used by the user plane network element to send notification information to the session management network element when data of a first multicast service arrives at the user plane network element, receives data of the first multicast service, and sends notification information to the session management network element based on the first information, the notification information indicating that data of the first multicast service has arrived at the user plane network element. In a possible design, the chip system further includes a memory. The memory is configured to store program instructions and data required for the communication device. The chip system may include a chip, or may include a chip and another discrete component.

[0041] For the technical effects achieved by any one of the designs of the ninth to twelfth aspects, please refer to the technical effects achieved by the seventh aspect or any one of the possible designs of the seventh aspect. Details will not be described again.

[0042] According to a thirteenth aspect, a data transmission method is further provided. The method includes the steps of receiving, by a mobility management network element, second information from a session management network element, the second information for triggering establishment of a communication connection between a first terminal and a first access network device, and transmitting fifth information to the first access network device based on the second information, the fifth information being used by the first access network device to establish a communication connection to the first terminal. Based on the method according to the thirteenth aspect, the mobility management network element can transmit the second information to the first access network device when triggered by the session management network element, so that the first access network device establishes a communication connection between the first access network device and the first terminal, and the first access network device transmits data of the first multicast service to the first terminal via the communication connection, thereby ensuring that the first terminal receives the data of the first multicast service without loss.

[0043] In a possible design, the mobility management network element receives first indication information from the first access network device, the first indication information indicating that the establishment of the communication connection between the first terminal and the first access network device is completed, and transmits second indication information to the session management network element based on the first indication information, the second indication information indicating that the establishment of the communication connection between the first terminal and the first access network device is completed. In other words, when the mobility management network element receives the communication connection establishment completion information transmitted by the access network device, it transmits the indication information to the session management network element, so that the session management network element knows the specific terminal in the multicast group to which the communication connection is established, thereby simplifying the system design.

[0044] In a possible design, the second information is further for triggering establishment of a communication connection between the second terminal and the second access network device, and the method further includes the mobility management network element sending sixth information to the second access network device based on the second information, the sixth information being used by the second access network device to establish the communication connection to the second terminal. In other words, establishment of multiple communication connections is triggered by using one second information to reduce signaling overhead.

[0045] In a possible design, the method further includes the mobility management network element receiving third indication information from the second access network device, the third indication information indicating that the establishment of the communication connection between the second terminal and the second access network device is completed, and sending fourth indication information to the session management network element based on the third indication information, the fourth indication information indicating that the establishment of the communication connection between the second terminal and the second access network device is completed. Similarly, for a communication connection establishment completion indication sent by another access network device, the mobility management network element sends indication information to the session management network element immediately after receiving the communication connection establishment completion indication sent by the access network device, so that the session management network element knows the specific terminal in the multicast group to which the communication connection is established, thereby simplifying the system design.

[0046] In a possible design, the mobility management network element sends fifth indication information to the session management network element based on the second preset waiting duration, and the fifth indication information indicates that the establishment of all communication connections that the session management network element triggers the mobility management network element to establish has been completed. Specifically, a preset waiting duration is set for the mobility management network element. When the preset waiting duration expires, the session management network element is notified that the establishment of the communication connections has been completed, and ensures that the establishment of as many communication connections as possible is completed within the preset waiting duration. This avoids the problem that, due to different communication connection establishment speeds of different terminals served by different access network devices, when an access network device that first completes the establishment of a communication connection triggers data distribution of a multicast service, packet loss is caused for terminals served by another access network device with a slower communication connection establishment.

[0047] In a possible design, before the step of sending the fifth information to the first access network device by the mobility management network element when the first terminal is in an idle state, the method further includes the steps of sending a paging message to the first access network device by the mobility management network element, the paging message being for paging the first terminal, and receiving a service request message from the first terminal by the mobility management network element. In other words, when the terminal is in a CM connected state, the fifth information for establishing a communication connection is sent to the access network device, thereby ensuring the accuracy of the communication connection establishment.

[0048] It should be understood that, in order to reduce signaling overhead, after receiving notification information indicating that the user plane network element has received data of the first multicast service, the session management network element may instruct the mobility management network element to a terminal to join the multicast group by using a signaling message, so that the mobility management network element pages the terminal in an idle state to receive the data of the first multicast service. Specifically, the mobility management network element receives a user equipment list UE list of a multicast group from the session management network element, the multicast group corresponds to the first multicast service, the UE list indicates the terminal to join the multicast group, and the mobility management network element determines a terminal in an idle state among the terminals indicated by the UE list, and sends a paging message to the terminal in an idle state. In other words, in order to reduce signaling overhead, paging of multiple terminals is triggered by using one signaling message.

[0049] In a possible design, the UE list is carried in the second information, and the second information may further include a multicast group identification. In this way, the mobility management network element knows the specific multicast group to which the terminal is paged. The paging message carrying the multicast group identification is sent to the terminal in the idle state. In this way, upon receiving the paging message carrying the multicast group identification, the terminal in the idle state can know whether the terminal needs to initiate a service request procedure.

[0050] In a possible design, the terminals in idle state include a first terminal and a second terminal, and the step of sending, by the mobility management network element, a paging message to the terminals in idle state includes sending, by the mobility management network element, the paging message in a first paging area, where the paging message includes an identification information of a multicast group, and the first paging area includes a registration area of ​​the first terminal and a registration area of ​​the second terminal. In this way, multiple terminals can be paged in a group paging manner to reduce paging signaling overhead.

[0051] In a possible design, the method further includes receiving, by the mobility management network element, a service request message from the first terminal, and / or receiving, by the mobility management network element, a service request message from the second terminal.

[0052] In a possible design, the first paging area further includes a registration area of ​​terminals other than the first terminal and the second terminal in the UE list. Alternatively, the first paging area further includes a registration area of ​​terminals in an idle state other than the first terminal and the second terminal in the UE list. In this way, group paging can be initiated in the registration areas of more terminals, so that more terminals are paged to receive data of the first multicast service.

[0053] According to a fourteenth aspect, the present application provides a communication device. The communication device may be a mobility management network element, or may be a chip or a system-on-chip in the mobility management network element. The communication device may implement functions performed by the mobility management network element according to the thirteenth aspect or any one of the possible designs of the thirteenth aspect. The functions may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions. For example, the communication device may include a receiving unit, a transmitting unit, and a processing unit.

[0054] In a possible design, the receiving unit is configured to receive second information from the session management network element, the second information being for triggering establishment of a communication connection between the first terminal and the first access network device, the communication connection being for transmitting data of the first multicast service.

[0055] The transmitting unit is configured to transmit fifth information to the first access network device based on the second information, the fifth information being used by the first access network device to establish a communication connection to the first terminal.

[0056] In another possible design, the receiving unit is configured to receive a user equipment list (UE list) of a multicast group from the session management network element, the multicast group corresponding to a first multicast service, and the UE list indicating terminals to join the multicast group. The processing unit is configured to determine terminals in an idle state among the terminals indicated by the UE list. The sending unit is configured to send a paging message to the terminals in the idle state.

[0057] For a specific implementation form of the communication device, please refer to the operation function of the mobility management network element in the data transmission method according to the thirteenth aspect or any one of the possible designs of the thirteenth aspect. The method according to the thirteenth aspect or any one of the possible designs of the thirteenth aspect may be correspondingly implemented by an obtaining unit and a transmitting unit included in the communication device.

[0058] According to a fifteenth aspect, there is provided a communications device, the communications device including a processor and a memory, the memory configured to store computer-executable instructions, and when the communications device is operated, the processor executes the computer-executable instructions stored in the memory, such that the communications device performs a data transmission method according to the thirteenth aspect or any one of the possible designs of the thirteenth aspect.

[0059] According to a sixteenth aspect, there is provided a computer readable storage medium storing instructions which, when executed on a computer, enable the computer to perform a data transmission method according to the thirteenth aspect or any one of the possible designs of the thirteenth aspect.

[0060] According to a seventeenth aspect, there is provided a computer program product comprising instructions, which when executed on a computer, enable the computer to perform a data transmission method according to the thirteenth aspect or any one of the possible designs of the thirteenth aspect.

[0061] According to an eighteenth aspect, a chip system is provided. The chip system includes a processor and a communication interface configured to support a communication device in implementing functions in the aforementioned aspects. For example, the processor receives second information from a session management network element via the communication interface, the second information being for triggering establishment of a communication connection between a first terminal and a first access network device, and transmits fifth information to the first access network device based on the second information, the fifth information being used by the first access network device to establish a communication connection to the first terminal. In a possible design, the chip system further includes a memory. The memory is configured to store program instructions and data required for the communication device. The chip system may include a chip, or may include a chip and another discrete component.

[0062] For the technical effects achieved by any one of the fifteenth to eighteenth aspects, please refer to the technical effects achieved by the thirteenth aspect or any one of the possible designs of the thirteenth aspect. Details will not be described again.

[0063] According to a nineteenth aspect, there is further provided a data transmission method, comprising the steps of: receiving, by a first access network device, data of a first multicast service, and, if there is at least one terminal in a multicast group served by the first access network device and corresponding to the first multicast service in a preset state, buffering, by the first access network device, the data of the first multicast service, and sending a paging message to page the first terminal, the first terminal belonging to at least one terminal served by the first access network device and in a preset state, the preset state comprising an idle state, an inactive state, or a state in which there is no communication connection to the access network device for transmitting the data of the first multicast service.

[0064] Based on the method according to the nineteenth aspect, when a terminal served by the first access network device is in an unconnected state, the first access network device first buffers the received data of the first multicast service and initiates paging to the terminal, so that the multicast service data is delivered when the terminal is paged and transitions to a connected state, thereby ensuring that the terminal receives the multicast service data without loss.

[0065] In a possible design, the method further includes receiving, by the first access network device, a first RRC message from the first terminal, the first RRC message requesting to establish a communication connection between the first terminal and the first access network device, obtaining fifth information from a mobility management network element based on the first RRC message, the fifth information being for establishing the communication connection between the first terminal and the first access network device, and transmitting seventh information to the first terminal based on the fifth information, the seventh information indicating a related configuration of the communication connection between the first terminal and the first access network device. In other words, the fifth information is obtained when a request to establish the communication connection is received from the first terminal, and air interface resource configuration, etc. is performed for the terminal based on the fifth information, and the configuration is indicated to the terminal. This simplifies the system design when the establishment of the communication connection is completed.

[0066] In a possible design, the method further includes: transmitting, by the first access network device, the buffered data of the first multicast service when there is no terminal in the preset state in the multicast group served by the first access network device and corresponding to the first multicast service, or transmitting, by the first access network device, the buffered data of the first multicast service based on a third preset waiting duration. In other words, the buffered multicast service data is transmitted when the communication connection corresponding to all terminals served by the first access network device is completed or when the preset waiting duration expires, thereby ensuring that as many terminals as possible receive the multicast service data.

[0067] In a possible design, the first RRC message is a service request message or an RRC resume request message. In other words, the above application scenario is applied when the first terminal is in an idle state or a non-connected state. The application scenario is flexible and diverse, and has good adaptability.

[0068] In a possible design, the step of transmitting a paging message to the first terminal by the first access network device includes transmitting the paging message to the first terminal on a first channel by the first access network device, the first channel including any one of a unicast channel between the first access network device and the first terminal, a common channel, or a dedicated channel of a multicast group corresponding to the first multicast service. In other words, the paging message can be transmitted on any one of a plurality of channels. This is flexible and has good adaptability.

[0069] According to a twentieth aspect, the present application provides a communication device. The communication device may be a first access network device, or a chip or system-on-chip in the first access network device. The communication device may implement the functions performed by the first access network device according to the nineteenth aspect or any one of the possible designs of the nineteenth aspect. The functions may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions. For example, the communication device may include a receiving unit, a processing unit, and a transmitting unit.

[0070] The receiving unit is configured to receive data of a first multicast service.

[0071] The processing unit is configured to buffer data of the first multicast service when there is at least one terminal served by the first access network device in a multicast group that is in a preset state and corresponds to the first multicast service.

[0072] The sending unit is configured to send a paging message for paging a first terminal, the first terminal being in a preset state and belonging to at least one terminal served by the first access network device.

[0073] For a specific implementation form of the communication device, please refer to the operation function of the first access network device in the data transmission method according to the 19th aspect or any one of the possible designs of the 19th aspect. The method according to the 19th aspect or any one of the possible designs of the 19th aspect may be correspondingly implemented by an obtaining unit and a transmitting unit included in the communication device.

[0074] According to a twenty-first aspect, there is provided a communications device, the communications device including a processor and a memory, the memory configured to store computer-executable instructions, and when the communications device is operated, the processor executes the computer-executable instructions stored in the memory, such that the communications device performs a data transmission method according to the nineteenth aspect or any one of the possible designs of the nineteenth aspect.

[0075] According to a twenty-second aspect, there is provided a computer-readable storage medium storing instructions which, when executed on a computer, enable the computer to perform a data transmission method according to the nineteenth aspect or any one of the possible designs of the nineteenth aspect.

[0076] According to a twenty-third aspect there is provided a computer program product comprising instructions, which when run on a computer enable the computer to perform a data transmission method according to the nineteenth aspect or any one of the possible designs of the nineteenth aspect.

[0077] According to a twenty-fourth aspect, a chip system is provided. The chip system includes a processor and a communication interface configured to support a communication device in implementing functions in the aforementioned aspects. For example, the processor receives data of a first multicast service via the communication interface, and if there is at least one terminal that is in a preset state and is served by the first access network device in a multicast group corresponding to the first multicast service, buffers the data of the first multicast service and sends a paging message to page the first terminal, the first terminal being in the preset state and belonging to at least one terminal served by the first access network device. In a possible design, the chip system further includes a memory. The memory is configured to store program instructions and data required for the communication device. The chip system may include a chip, or may include a chip and another discrete component.

[0078] For the technical effects achieved by any one of the designs of the 21st to 24th aspects, please refer to the technical effects achieved by the 19th aspect or any one of the possible designs of the 19th aspect. The details will not be described again.

[0079] According to a twenty-fifth aspect of an embodiment of the present application, a data transmission method is provided. The method includes the steps of: receiving, by a session management network element, fourth information from a mobility management network element, the fourth information being for deactivating a user plane transmission resource of a first terminal; and transmitting second information to the mobility management network element based on the fourth information, the second information being for establishing a communication connection between the first terminal and a first access network device. In other words, when the user plane resource of the first terminal is deactivated, the second information for establishing the communication connection is transmitted to the mobility management network element, so that the mobility management network element configures the air interface resource of the terminal based on the second information. This ensures that the terminal receives the multicast service data without loss based on the air interface resource configured for the terminal.

[0080] In a possible design, the step of sending the second information to the mobility management network element by the session management network element includes the steps of sending a subscription request by the session management network element to the mobility management network element, the subscription request being for requesting to subscribe to a first event, the first event being a first terminal transitioning from a preset state to a connected state, receiving event notification information from the mobility management network element by the session management network element, the event notification information being for notifying the first event, and sending the second information by the session management network element to the mobility management network element based on the event notification information. In other words, the second information is sent via a subscription process, thereby simplifying the system design.

[0081] According to a twenty-sixth aspect, the present application provides a communication device. The communication device may be a session management network element, or a chip or system-on-chip in the session management network element. The communication device may implement the functions performed by the communication device according to the twenty-fifth aspect, or a possible design of the twenty-fifth aspect. The functions may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions. For example, the communication device may include a receiving unit and a transmitting unit.

[0082] The receiving unit is configured to receive fourth information from the mobility management network element and for deactivating user plane transmission resources of the first terminal.

[0083] The sending unit is configured to send second information to the mobility management network element based on the fourth information, the second information being for establishing a communication connection between the first terminal and the first access network device.

[0084] For specific implementation forms of each unit of the communication device, please refer to the operation function of the session management network element in the data transmission method according to the 25th aspect or any one of the possible designs of the 25th aspect. Details will not be described again here. The provided communication device can achieve the same beneficial effects as the 25th aspect or any one of the possible designs of the 25th aspect.

[0085] According to a twenty-seventh aspect, there is provided a communications device, the communications device including a processor and a memory. The memory is configured to store computer-executable instructions. When the communications device is operated, the processor executes the computer-executable instructions stored in the memory, such that the communications device performs a data transmission method according to the twenty-fifth aspect or any one of the possible designs of the twenty-fifth aspect.

[0086] According to a twenty-eighth aspect, there is provided a computer readable storage medium storing instructions which, when executed on a computer, enable the computer to perform a data transmission method according to the twenty-fifth aspect or any one of the possible designs of the twenty-fifth aspect.

[0087] According to a 29th aspect there is provided a computer program product comprising instructions, which when run on a computer enable the computer to perform a data transmission method according to the 25th aspect or any one of the possible designs of the 25th aspect.

[0088] According to a 30th aspect, a communication device is provided. The communication device may be a chip system, and the chip system may include a processor and a communication interface configured to support the communication device in implementing the functionality according to the 25th aspect or any one of the possible designs of the 25th aspect. For example, the processor receives, via the communication interface, fourth information from a mobility management network element and for deactivating user plane transmission resources of the first terminal, and transmits second information to the mobility management network element based on the fourth information, the second information for establishing a communication connection between the first terminal and the first access network device. In a possible design, the chip system further includes a memory. The memory is configured to store program instructions and data required for the communication device. The chip system may include a chip, or may include a chip and another discrete component.

[0089] For the technical effects achieved by any one of the designs of the 27th to 30th aspects, please refer to the technical effects achieved by the 25th aspect or any one of the possible designs of the 25th aspect. Details will not be described again.

[0090] According to a thirty-first aspect, there is provided a communication system, which may include a communication device or chip system according to any one of the second to sixth aspects, a communication device or chip system according to any one of the eighth to twelfth aspects, and a communication device or chip system according to any one of the fourteenth to eighteenth aspects.

[0091] Alternatively, the communication system may include a communication device or chip system according to any one of the twentieth to twenty-fourth aspects and a communication device or chip system according to any one of the twenty-sixth to thirtieth aspects. [Brief description of the drawings]

[0092] [Figure 1a] FIG. 1 is a schematic diagram of a "pseudo broadcast" scheme. [Figure 1b] FIG. 2 is a schematic diagram of another "pseudo broadcast" scheme. [Figure 1c] FIG. 2 is a schematic diagram of another "pseudo broadcast" scheme. [Diagram 2] 1 is a schematic flow chart of an access network release; [Figure 3a] FIG. 1 is a schematic diagram of the architecture of a communication system. [Figure 3b] 1 is a schematic diagram of the architecture of a 5G communication system. [Figure 4] 1 is a schematic configuration diagram of a communication device 400 according to an embodiment of the present application. [Diagram 5] 2 is a flowchart of a data transmission method according to an embodiment of the present application; [Figure 6a] 2 is a flowchart of a data transmission method according to an embodiment of the present application; [Figure 6b] 2 is a flowchart of a data transmission method according to an embodiment of the present application; [Figure 7] 4 is a flowchart of another data transmission method according to an embodiment of the present application. [Figure 8a] 4 is a flowchart of another data transmission method according to an embodiment of the present application. [Figure 8b] 4 is a flowchart of another data transmission method according to an embodiment of the present application. [Figure 9] 1 is a schematic configuration diagram of a communication device 90 according to an embodiment of the present application. [Figure 10] 1 is a schematic configuration diagram of a communication device 100 according to an embodiment of the present application. [Figure 11] 1 is a schematic configuration diagram of a communication device 110 according to an embodiment of the present application. [Figure 12] 1 is a schematic configuration diagram of a communication device 120 according to an embodiment of the present application. [Figure 13] 1 is a schematic configuration diagram of a communication system according to an embodiment of the present application. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0093] In a communication system, in a scenario where a network side device transmits multicast service data of a multicast service to multiple terminals (e.g., multiple terminals in the same multicast group), in order to improve resource utilization, the multicast service data is transmitted in a "pseudo broadcast" manner. The "pseudo broadcast" manner may mean that the multicast service data transmitted to multiple terminals are combined in the UPF and / or the access network device.

[0094] For example, Figure 1a is a schematic diagram showing that the multicast service data transmitted to multiple terminals are combined in the UPF and the access network device. As shown in Figure 1a, after combining the received multicast service data transmitted to multiple terminals into one multicast service data, the UPF transmits the multicast service data to the access network device through a communication connection. After receiving the multicast service data, the access network device encodes the multicast service data by using a group radio network temporary identifier (RNTI), and then broadcasts the multicast service data to multiple terminals. The UPF does not need to transmit multiple multicast service data to the access network device through multiple communication connections, and the access network device does not need to transmit multiple multicast service data to multiple terminals through multiple communication connections. This improves resource utilization.

[0095] As another example, Figure 1b is a schematic diagram showing that the multicast service data transmitted to multiple terminals are combined in an access network device. As shown in Figure 1b, the UPF transmits multiple multicast service data transmitted to multiple terminals to the access network device. After receiving the multiple multicast service data, the access network device combines the multiple multicast service data into one multicast service data, encodes the combined multicast service data by using a group RNTI, and then broadcasts the combined multicast service data to multiple terminals. The access network device does not need to transmit the multiple multicast service data to multiple terminals through multiple communication connections. This improves resource utilization.

[0096] In the pseudo-broadcast scheme shown in FIG. 1a, the communication connection for transmitting the multicast service data between the UPF and the access network device may be a communication connection corresponding to a unicast protocol data unit (PDU) session of any terminal in the multicast group. For example, as shown in FIG. 1c, there are three terminals in the multicast group, terminal 1, terminal 2, and terminal 3. Each terminal establishes a PDU session, and the PDU sessions of all terminals correspond to the same UPF, and one PDU session includes a communication connection between the UPF and the access network device and a communication connection between the access network device and the terminal. Before the multicast service data is transmitted to the three terminals, one PDU session may be pre-selected from the PDU sessions of the three terminals, for example, the PDU session of terminal 2 shown in FIG. 1c. After receiving the multicast service data sent by the application server, the UPF maps the multicast service data to a quality of service flow (QoS flow, QF) corresponding to the PDU session of the terminal 2, determines downlink tunnel information of the access network device corresponding to the PDU session, and sends the multicast service data mapped to the QF to the access network device according to the downlink tunnel information of the access network device. The access network device sends the received multicast service data to the three terminals, thereby improving resource utilization.

[0097] It should be noted that the communication connection in the embodiment of the present application may alternatively be described as a downlink transmission tunnel. The PDU session of the terminal may be replaced by a unicast PDU session of the terminal. The downlink tunnel information of the access network device may be for establishing a communication connection between the UPF and the access network device. The downlink tunnel information of the access network device may include an internet protocol (IP) address of the access network device and / or a tunnel endpoint identifier (TEID) of the access network device. After the establishment of the PDU session of the terminal is completed, the session management network element can store in the UPF the downlink tunnel information of the access network device corresponding to the PDU session of the terminal and a quality of service flow identifier (QoS flow identifier, QFI) of the PDU session, so that the UPF transmits the multicast service data mapped to the QF to the access network device indicated by the downlink tunnel information based on the correspondence between the downlink tunnel information of the access network device and the QFI.

[0098] In the scheme shown in FIG. 1a, when a terminal corresponding to the selected PDU session, for example, terminal 2, is in a preset state (for example, idle state or inactive state), the selected PDU session is released, and the UPF can disconnect from the access network device and delete the downlink tunnel information of the access network device from the local storage of the UPF. In this case, if the UPF still needs to transmit multicast service data by using the PDU session, when it finds that the downlink tunnel information of the access network device corresponding to the QF corresponding to the multicast service data does not exist locally, the UPF can trigger the access network device or the core network device to start paging the terminal. After the paging is successful, the downlink tunnel information of the access network device is configured on the UPF, so that the UPF again transmits the multicast service data to the access network device based on the downlink tunnel information of the access network device, and the access network device transmits the multicast service data to the multiple terminals. However, in this scheme, among the multiple terminals, only the terminal that has been successfully paged and another terminal in a radio resource control (RRC) connected state can receive the multicast service data. A terminal having a multicast service data requirement but in a preset state cannot receive the multicast service data because its communication connection to the access network device is disconnected. This cannot meet the requirement of receiving the multicast service data by all terminals in a "pseudo broadcast" manner. Similarly, in the manner shown in FIG. 1b, if a terminal in a multicast group has a multicast service data requirement but in a preset state, such a terminal cannot receive the multicast service data because its communication connection to the access network device is disconnected.This cannot meet the requirement that the multicast service data be received by all terminals in the multicast group in a "pseudo broadcast" manner.

[0099] For example, as shown in FIG. 1c, it is assumed that terminal 2 and terminal 3 are in an idle state, terminal 1 is in an RRC connected state, the selected PDU session of terminal 2 is for transmitting multicast service data, and the downlink tunnel information of the access network device corresponding to the PDU session of terminal 2 is deleted from the UPF. In this case, if the UPF still needs to transmit the multicast service data by using the PDU session of terminal 2, the UPF pages terminal 2. After terminal 2 is successfully paged, the downlink tunnel information of the access network device corresponding to the PDU session of terminal 2 is reconfigured on the UPF. The UPF transmits the multicast service data to the access network device based on the downlink tunnel information of the access network device, and the access network device transmits the data to terminal 1 and terminal 2. Since terminal 3 is in an idle state, the communication connection between terminal 3 and the access network device is disconnected. As a result, terminal 3 cannot receive the multicast service data.

[0100] In order to solve the technical problem, in the present application, when there is at least one terminal in a preset state (e.g., idle state or inactive state) in the multicast group, the session management network element instructs the user plane network element to send notification information to the session management network element when data of the first multicast service arrives at the user plane network element, and triggers paging of the terminal in the preset state when the session management network element receives the notification information. In this way, when there is no terminal among the terminals in the preset state or there is no terminal in the preset state among all terminals in the multicast group, the user plane network element is instructed to transmit the data of the first multicast service. Alternatively, when a terminal included in the multicast group and corresponding to the first access network device is in the preset state, after receiving the data of the first multicast service, the first access network device first buffers the data of the first multicast service. In addition, the first access network device pages the terminal in the preset state and triggers the terminal to establish a communication connection to the first access network device, and delivers the buffered data of the first multicast service if there is no terminal in the preset state in the multicast group. This ensures that all terminals in the multicast group receive the data of the first multicast service.

[0101] The preset states described in the present application may include any one of an idle state, an inactive state, or a state in which there is no communication connection to the access network device for transmitting data of the first multicast service, and may further include a state in which there is no communication connection between the access network device and the user plane network element for transmitting data of the first multicast service, etc. The absence of a communication connection to the access network device for transmitting data of the multicast service may be understood as the context information of the multicast session corresponding to the first multicast service being released / deleted / removed at the access network device side. The absence of a communication connection between the access network device and the user plane network element for transmitting data of the first multicast service may be understood as the user plane network element releasing a transmission tunnel corresponding to the multicast session, for example deleting the tunnel information stored locally at the access network device, or deleting / removing / releasing the locally stored N4 context corresponding to the first multicast service.

[0102] The connected state described in this application may be replaced with a non-idle state. For a core network device (e.g., a mobility management network element or a session management network element), the connected state may include a radio resource control (RRC) connected state and a connection management (CM) connected state, or the connected state may include an inactive state and a CM connected state. For an access network device, the connected state may include an RRC connected state.

[0103] The RRC connected state may mean that there is an RRC connection between the terminal and the access network device, and the CM connected state may mean that there is a non-access stratum (NAS) signaling connection between the terminal and the core network device (e.g., a mobility management network element) and an N2 connection between the access network device and the core network device. In the RRC connected state and the CM connected state, both the access network device and the core network device store the context of the terminal. The access network device knows that the terminal is within the coverage area of ​​the access network device or within the management range of the access network device. The core network device knows which access network device can be used for locating or detecting the terminal. In the connected state, the terminal can perform downlink data and / or uplink data transmission with the access network device.

[0104] The idle state may mean that there is no RRC connection between the terminal and the access network device. The idle state may be referred to as an RRC_idle state. In the idle state, the access network device does not store the terminal's context, there is no NAS signaling connection between the terminal and a core network device (e.g., a mobility management network element), there is no N2 connection between the access network device and a core network device (e.g., a mobility management network element), and the core network device stores the terminal's context. The access network device does not know whether the terminal is within the coverage area of ​​the access network device. The core network device does not know which access network device's coverage area or management range the terminal is within, and the access network device does not know which access network device can be used for locating or detecting the terminal.

[0105] The inactive state may be referred to as an RRC_inactive state. The inactive state may mean that there is no RRC connection between the terminal and the access network device. In the inactive state, there is no NAS signaling connection between the terminal and the core network device (e.g., mobility management network element), and there is an N2 connection between the access network device and the core network device (e.g., mobility management network element). The access network device stores the context of the terminal, and the core network device can store the context of the terminal. The access network device does not know the particular cell in which the terminal camps within the coverage area of ​​the access network device, or whether the terminal is within the management range of the access network device. The core network device knows which access network device's coverage area or management range the terminal is within, and the core network device knows which access network device can be used for locating or detecting the terminal.

[0106] The three states of RRC_connected, RRC_idle, and RRC_inactive may be transitioned to each other. After the terminal selects a cell to be accessed and before the terminal accesses the access network device corresponding to the cell, the terminal can successfully establish an RRC connection to the access network device through an RRC establishment process, access the cell, enter the RRC_connected state, and trigger the establishment of a CM connection between the access network device and the mobility management network element. In the RRC_connected state, if the terminal has no data transmission requirements for a long time, the access network device may transition the state of the terminal from the RRC_connected state to the RRC_idle state or the RRC_inactive state through an RRC release process. For example, as shown in FIG. 2, the access network device does not receive uplink data or downlink data of the terminal within a specified period of time. In this case, the access network device decides to release the context of the terminal. The access network device sends a user equipment (UE) context release request to the mobility management network element to request the terminal context to be released. The mobility management network element receives the UE context release request and sends a UE context release command to the access network device. The access network device receives the UE context release command and sends an RRC release message to the terminal to request the terminal to release the RRC connection. After receiving the RRC release message, the terminal disconnects the RRC connection from the access network device and enters the RRC_idle state from the RRC_connected state or the RRC_inactive state. The access network device sends a UE context release complete message to the mobility management network element, and the mobility management network element receives the UE context release complete message.Further optionally, if the terminal currently has an active user plane context, the mobility management network element notifies the corresponding session management network element to deactivate user plane transmission resources. After the above procedures are performed, the mobility management network element considers the terminal to be in CM idle state.

[0107] In addition, in the method shown in FIG. 2, when the terminal establishes a PDU session, a process of deactivating / releasing the user plane transmission resources of the terminal is further included to improve resource utilization. For example, the UE context release complete message sent by the access network device to the mobility management network element carries the ID of the PDU session of the terminal. After receiving the UE context release complete message sent by the access network device, the mobility management network element sends a PDU session deactivation indication to the session management network element that manages the PDU session. After receiving the PDU session deactivation indication, the session management network element deletes the correspondence between the terminal's data and the QF and the correspondence between the QF and the downlink tunnel information, and notifies the user plane network element to release the user plane transmission resources. For the process shown in FIG. 2, please refer to the prior art. Details will not be described further.

[0108] In the RRC_idle state, the terminal may transition the state of the terminal from the RRC_idle state to the RRC_connected state by using an RRC establishment process. For example, the access network device may send a paging message to the terminal. After receiving the paging message and determining that the terminal is being paged, the terminal is triggered to start the RRC establishment process to attempt to establish an RRC connection to the access network device and enter the RRC_connected state. If the RRC connection is successfully established, the terminal enters the RRC_connected state. If the RRC connection fails to be established, the terminal continues to stay in the RRC_idle state. When the terminal is in the RRC_inactive state, the terminal may attempt to resume the RRC connection to the access network device via an RRC resume process after receiving a paging message from the access network device and determining that the terminal is being paged to enter the RRC_connected state. For example, the terminal may send an RRC resume request message to the access network device, and after receiving the RRC resume request message, the access network device may send an RRC establishment message or an RRC resume message to the terminal, so that the state of the terminal may be transitioned to the RRC_connected state. When the terminal is in the RRC_inactive state, the access network device may transition the state of the terminal from the RRC_inactive state to the RRC_idle state through an RRC release process. For example, the access network device may send an RRC release message to the terminal, so that the state of the terminal is transitioned from the RRC_inactive state to the RRC_idle state, or the access network device may send an RRC reject message to the terminal, so that the terminal continues to remain in the RRC_inactive state.

[0109] It should be noted that the terminal context stored in the access network device is different from the terminal context stored in the core network device. The terminal context stored in the access network device is related to the data transmission of the terminal. The terminal context stored in the access network device may include the terminal's identity and a quality of service profile (QoS profile). The terminal context stored in the core network device is a context related to the terminal's mobility and registration, for example, the terminal context stored in the core network device may include the terminal's identity, the terminal's location information, the terminal's registration area, the terminal's current CM connection state, etc. The terminal's identity can identify the terminal. The terminal's identity may be any one of the terminal's internet protocol (IP) address, the terminal's media access control (MAC) address, the terminal's international mobile subscriber identity (IMSI), or the terminal's PDU session identifier. Alternatively, the terminal's identity may be other information that can identify the terminal in a future communication standard, for example, a session management context identifier (SM context ID). This is not limited.

[0110] The following describes the technical solutions of the embodiments of the present application with reference to the accompanying drawings of the embodiments of the present application.

[0111] The data transmission method provided in the embodiment of the present application may be applied to the communication system shown in Figure 3a. As shown in Figure 3a, the communication system may include a plurality of terminals, a mobility management network element, a session management network element, an access network device, and a user plane network element. In addition, the communication system shown in Figure 3a may further include a data network (DN), and the DN may include an application server (AS). The following describes the network elements or devices in the architecture shown in Figure 3a.

[0112] The terminal may be a device configured to implement wireless communication functions, such as a terminal, or a chip that can be used in a terminal. The terminal may be a UE, an access terminal, a terminal unit, a terminal station, a mobile station, a mobile console, a remote station, a remote terminal, a mobile device, a wireless communication device, a terminal agent, a terminal device, etc. in a 5G network or a future evolved communication system. The access terminal may be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld or computing device with wireless communication capabilities, another processing device, an in-vehicle device, or a wearable device connected to a wireless modem, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, an industrial control wireless terminal, a self driving wireless terminal, a remote medical wireless terminal, a smart grid wireless terminal, a transportation safety wireless terminal, a smart city wireless terminal, or a smart home wireless terminal, etc. The terminal may be mobile or fixed.

[0113] The access network device is mainly configured to implement functions such as physical layer functions, resource scheduling and management, and terminal access control and mobility management. The access network device may be a device supporting wired access or a device supporting wireless access. For example, the access network device may be an access network (AN) / radio access network (RAN), where the AN / RAN includes multiple 5G-AN / 5G-RAN nodes. The 5G-AN / 5G-RAN node may be an access point (AP), a node B (NB), an enhanced node B (eNB), a next generation node B (NR nodeB, gNB), a transmission reception point (TRP), a transmission point (TP), another access node, etc.

[0114] The mobility management network element is mainly responsible for terminal access authentication, mobility management, signaling exchange between functional network elements, etc., and manages, for example, user registration status, user connection status, user registration and network access, tracking area updates, user authentication during cell handover, and key security.

[0115] The session management network element is primarily configured to implement session management functions such as establishing, releasing, and modifying user plane transmission logical channels, e.g., PDU sessions.

[0116] The user plane network element may be used as an anchor on a user plane transmission logical channel and is configured to complete functions such as routing and forwarding of user plane data. For example, the user plane network element establishes a channel (i.e., a user plane transmission logical channel) between the user plane network element and a terminal, forwards data packets between the terminal and the DN on the channel, and is responsible for data packet filtering, data forwarding, rate control, and generating charging information for the terminal.

[0117] A DN is an operator network that can provide a data transmission service to a user, for example, an operator network that can provide an internet protocol (IP) multimedia service (IMS) to a user. An AS may be located in the DN, and an application server may provide a data transmission service to the user.

[0118] Please note that Fig. 3a is just an exemplary diagram of the architecture. In addition to the functional units shown in Fig. 3a, the system may further include another functional network element, for example, an operation and management (O&M) network element. This is not limited in the embodiment of the present application. In addition, the names of the devices in Fig. 3a are not limited. In addition to the names shown in Fig. 3a, the devices may have other names. For example, the names are replaced with the names of network elements with the same or similar functions. This is not limited.

[0119] The system shown in Figure 3a may be a 3rd generation partnership project (3GPP) communication system, such as a 4th generation (4G) communication system, a long term evolution (LTE) system, a 5th generation (5G) communication system, a new radio (NR) system, a next generation communication system, or a non-3GPP communication system, without being limited thereto.

[0120] For example, the communication system shown in Figure 3a is a 5G communication system shown in Figure 3b. As shown in Figure 3b, a network element or entity corresponding to a session management network element may be a session management function (SMF) in a 5G communication system, a network element or entity corresponding to a user plane network element may be a user plane function (UPF) in a 5G communication system, a network element or entity corresponding to an access network device may be a radio access network (RAN) in a 5G communication system, and a network element or entity corresponding to a mobility management network element may be an access and mobility management function (AMF) in a 5G communication system.

[0121] Optionally, the session management network element and the mobility management network element in the embodiment of the present application may also be called a communication device, and may be a general-purpose device or a dedicated device, which is not particularly limited in the embodiment of the present application.

[0122] Optionally, the relevant functions of the mobility management network element, the user plane network element, or the access network device in the embodiment of the present application may be implemented by one device, may be implemented jointly by multiple devices, or may be implemented by one or more function modules in one device. This is not particularly limited in the embodiment of the present application. It can be understood that the aforementioned functions may be network elements in a hardware device, software functions that operate on dedicated hardware, a combination of hardware and software, or virtualization functions instantiated on a platform (e.g., a cloud platform).

[0123] During specific implementation, each device (such as a session management network element, a user plane network element, a mobility management network element, or an access network device) shown in FIG. 3a may use the configuration structure shown in FIG. 4 or may include the components shown in FIG. 4. FIG. 4 is a schematic configuration diagram of a communication device 400 according to an embodiment of the present application. The communication device 400 may include a processor 401 and a memory 404. In addition, the communication device 400 may further include a communication line 402 and a communication interface 403. The processor 401, the memory 404, and the communication interface 403 may be connected to each other via the communication line 402.

[0124] The processor 401 may be a central processing unit (CPU), a general purpose processor, a network processor (NP), a digital signal processing (DSP), a microprocessor, a microcontroller, a programmable logic device (PLD), or any combination thereof. The processor 401 may alternatively be another device having processing capabilities, such as a circuit, a component, or a software module, without limitation.

[0125] The communication lines 402 are configured to transmit information between components included in the communication device 400 .

[0126] The communication interface 403 is configured to communicate with another device or another communication network. The other communication network may be an Ethernet, a radio access network (RAN), or a wireless local area network (WLAN), etc. The communication interface 403 may be a module, a circuit, a transceiver, or any device capable of implementing communication.

[0127] The memory 404 is configured to store instructions, which may be a computer program.

[0128] Memory 404 may be, without limitation, read-only memory (ROM) or another type of static storage device capable of storing static information and / or instructions, random access memory (RAM) or another type of dynamic storage device capable of storing information and / or instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other compact disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, and Blu-ray disc optical discs), magnetic disc storage media, or another magnetic storage device.

[0129] It should be noted that the memory 404 may exist separately from the processor 401 or may be integrated with the processor 401. The memory 404 may be configured to store instructions, program code, some data, etc. The memory 404 may be located inside the communication device 400 or may be located outside the communication device 400. This is not a limitation.

[0130] The processor 401 is configured to execute instructions stored in the memory 404 to implement the data transmission methods provided in the following embodiments of the present application. For example, if the communication device 400 is a session management network element, or a chip or system-on-chip in the session management network element, the processor 401 executes instructions stored in the memory 404 to implement the steps performed by the session management network element in the following embodiments of the present application. As another example, if the communication device 400 is a mobility management network element, or a chip or system-on-chip in the mobility management network element, the processor 401 can execute instructions stored in the memory 404 to implement the steps performed by the mobility management network element in the following embodiments of the present application.

[0131] In one example, the processor 401 may include one or more CPUs, such as CPU0 and CPU1 of FIG.

[0132] In an optional implementation, the communication device 400 includes multiple processors. For example, the communication device may further include a processor 407 in addition to the processor 401 of FIG.

[0133] In an optional implementation, the communication apparatus 400 further includes an output device 405 and an input device 406. For example, the input device 406 is a keyboard, a mouse, a microphone, a joystick, or another device, and the output device 405 is a display, a speaker, or another device.

[0134] It should be noted that the communication device 400 may be a desktop computer, a portable computer, a network server, a mobile phone, a tablet computer, a wireless terminal, an embedded device, a chip system, or a device having a structure similar to that of Figure 4. In addition, the configuration structure shown in Figure 4 does not constitute a limitation for the communication device. In addition to the components shown in Figure 4, the communication device may include more or less components than those shown in the figure, or some components may be combined, or different component arrangements may be used.

[0135] In this embodiment of the application, the chip system may include the chip, or may include the chip and other discrete components.

[0136] In addition, operations, terms, etc. in the embodiments of the present application may be cross-referenced. This is not limited. In the embodiments of the present application, the names of messages exchanged between devices, the names of parameters in messages, etc. are merely examples. Other names may be used instead in a specific implementation. This is not limited.

[0137] In the following, the communication system shown in FIG. 3a is used as an example to describe the data transmission method provided in the embodiment of the present application. The network element in the following embodiment may have the components shown in FIG. 4. Details are not described again. It should be noted that in the embodiment of the present application, the names of messages exchanged between devices, the names of parameters in the messages, etc. are merely examples. Other names may be used alternatively in a specific implementation. For example, multicast in the embodiment of the present application may be replaced with terms such as broadcast, groupcast, and multicast / broadcast. "Determining" in the embodiment of the present application may be understood as creating or generating, and "including" in the embodiment of the present application may be understood as "carrying", etc. Details are not particularly limited in the embodiment of the present application.

[0138] 5 shows a data transmission method according to an embodiment of the present application. As shown in FIG. 5, the method may include the following steps:

[0139] Step 501: A session management network element sends first information to a user plane network element when there is at least one terminal in a preset state in a multicast group corresponding to a first multicast service.

[0140] The session management network element may be a session management network element that manages a multicast session corresponding to the first multicast service, for example, a multicast session management network element. Alternatively, the session management network element may be a session management network element that manages a PDU session (for example, a unicast session) of the terminal, for example, a unicast session management network element. The user plane network element may be an anchor of the first multicast service, or the user plane network element may not be an anchor of the first multicast service. The user plane network element may be a user plane network element configured to connect the access network device to the anchor of the first multicast service, for example, a user plane network element that corresponds to the PDU session, i.e., the anchor of the unicast service. A communication connection is established between the user plane network element and the access network device, and a communication connection is established between the user plane network element and the anchor of the first multicast service.

[0141] The presence of at least one terminal in a preset state in a multicast group corresponding to a first multicast service may alternatively be described as a terminal corresponding to at least one member in the multicast group corresponding to the first multicast service being in a preset state, and the member may be a user using the terminal, i.e., a user of the terminal. The first multicast service may be a service for multiple terminals. For example, the first multicast service may be a television program, a file transfer service, an intragroup audio or video communication, or a broadcast service in a vehicle platoon. The multiple terminals to which the first multicast service is directed may join a group. The group may be referred to as a multicast group corresponding to the first multicast service. All terminals in the multicast group may be authorized to receive data of the multicast service, or may receive data of the multicast service without authorization. That is, the multicast group corresponding to the first multicast service may be a combination of multiple terminals receiving data of the first multicast service. For example, the multicast group may be a vehicle platoon receiving commands sent by the same command center, a user group receiving the same television program, etc.

[0142] For example, before step 501, multiple terminals may join the multicast group in the manner shown in FIG. 1a or FIG. 1b, and the multiple terminals share the same user plane network element. For example, each of the multiple terminals may establish a PDU session of the terminal. The session management network element may select a PDU session from the PDU sessions established by the multiple terminals, or establish a dedicated channel of the multicast group, map the data of the first multicast service to a QF corresponding to the selected PDU session or the dedicated channel of the multicast group, and locally store the context information of the multicast group, and the context information of the multicast group may include the identification information of the multiple terminals participating in the multicast group, and the corresponding relationship between the identification information of the user plane network element and the identification information of the first multicast service, and correspondingly configure the mapping relationship between the QF and the first multicast service for the user plane network element. In this way, after receiving the data of the first multicast service, the user plane network element transmits the data of the first multicast service to the multiple terminals by using the QF. For the detailed process of the terminals establishing a PDU session and joining the multicast group, please refer to the prior art. Details will not be described further.

[0143] The relevant descriptions of the preset state, the idle state, and the inactive state have been described above, and the details will not be described again. The session management network element can determine that there is at least one terminal in a preset state in a multicast group corresponding to a first multicast service by using the following embodiment 1 or embodiment 2. In the following, the two schemes of embodiment 1 and embodiment 2 are described by using an example in which the first terminal is in a preset state.

[0144] Example 1: A mobility management network element determines that an RRC connection between a first terminal and an access network device is disconnected, and therefore cannot transmit data to the first terminal. The mobility management network element transmits fourth information to a session management network element for deactivating a user plane transmission resource of the first terminal. The fourth information may carry identification information of a PDU session of the first terminal, for example, may carry an ID of a PDU session of the first terminal. The session management network element receives the fourth information and determines that the first terminal served by the mobility management network element is in a preset state based on the fourth information.

[0145] The fourth information may be called a deactivate indication or another name, without being limited thereto. For example, the mobility management network element may include the fourth information in a Nsmf_PDU session_update SMContext request and send the request to the session management network element.

[0146] When the session management network element is a multicast session management network element, the mobility management network element sending the fourth information to the session management network element may include: the mobility management network element sending information indicating a multicast group corresponding to the first multicast service (e.g., identification information of a multicast group) and the fourth information to the first network element. The first network element receives the information indicating a multicast group corresponding to the first multicast service and the fourth information, and sends a subscription message carrying the fourth information to a session management network element that manages a multicast session corresponding to the multicast group. The first network element is a unicast session management network element corresponding to the first terminal, or another intermediate network element configured to forward the fourth information. This is not limited to this.

[0147] Furthermore, after determining that the first terminal is in the preset state, the session management network element may record the terminal in the preset state in a context of the multicast group corresponding to the first multicast service, at the granularity of the terminal. For example, the session management network element may correspondingly set flag information for the identity of the terminal in the context of the multicast group corresponding to the first multicast service, where the flag information indicates that the terminal identified by the identity is in the preset state.

[0148] Example 2: The mobility management network element determines that the RRC connection between the first terminal and the access network device served by the mobility management network element is disconnected, so that the mobility management network element cannot transmit data to the first terminal. The mobility management network element sends an event exposure notification message (Namf_EventExposure Notify) to the session management network element, indicating that there is at least one terminal in a preset state in the multicast group served by the mobility management network element and corresponding to the first multicast service. The session management network element receives the event exposure notification message, and determines that there is at least one terminal in a preset state in the multicast group corresponding to the first multicast service based on the event exposure notification message.

[0149] When the session management network element is a multicast session management network element, the mobility management network element sending the event publish notification message to the session management network element may include: the mobility management network element sending information indicating a multicast group corresponding to the first multicast service (e.g., identification information of the multicast group) and the event publish notification message to the first network element. The first network element receives the information indicating the multicast group corresponding to the first multicast service and the event publish notification message, and sends the event publish notification message to a session management network element that manages a multicast session corresponding to the multicast group. The first network element is a unicast session management network element corresponding to the first terminal, or another intermediate network element configured to forward the event publish notification message. This is not limited to this.

[0150] It should be noted that after the first network element receives the event publishing notification message or the fourth information sent by the mobility management network element, the first network element can send another type of message, for example, a request message or a subscription message, to the session management network element. The content indicated by the other type of message is the same as the content indicated by the event publishing notification message or the fourth information. This is not limited in this embodiment of the present application.

[0151] Furthermore, after the session management network element receives the event publishing notification message and determines that there is at least one terminal in the preset state in the multicast group corresponding to the first multicast service, the session management network element can record that there is at least one terminal in the preset state in the multicast group at the granularity of the multicast group. For example, the session management network element correspondingly sets flag information for the context of the multicast group corresponding to the first multicast service, and the flag information indicates that there is at least one terminal in the preset state in the multicast group. In this case, the session management network element does not need to know the specific terminal in the preset state.

[0152] Furthermore, the session management network element can locally store a correspondence between the identification information of the mobility management network element and the identification information of the first multicast service, so as to indicate that a terminal in a preset state is served by the mobility management network element in a multicast group corresponding to the first multicast service. When the session management network element receives an event publishing notification message via the first network element, the session management network element can further locally store the identification information of the first network element and the identification information of the first multicast service, and the first network element can locally store the correspondence between the identification information of the mobility management network element and the identification information of the first multicast service.

[0153] The mobility management network element may determine that the first terminal disconnects its RRC connection to the access network device in the following manner: the access network device or the mobility management network element triggers the AN release procedure shown in FIG. 2, so that the first terminal disconnects its RRC connection to the access network device. After the first terminal is in the RRC_idle or RRC_inactive state, the access network device sends a UE context release complete message carrying the identification information of the first terminal to the mobility management network element. After receiving the UE context release complete message, the mobility management network element determines that the first terminal disconnects its RRC connection to the access network device. Alternatively, when the access network device determines that the first terminal has disconnected its RRC connection to the access network device and is in an RRC_idle state or an RRC_inactive state, or the access network device determines to release the context of the first terminal or to release the RRC connection of the first terminal, the access network device sends a UE context release request message or a UE notification message to the mobility management network element. After receiving the UE context release request message or the UE notification message, the mobility management network element determines that the first terminal disconnects its RRC connection to the access network device.

[0154] The first information may include a first identification information. The first information may be for sending notification information to the session management network element when data of the first multicast service arrives at the user plane network element, or may instruct the user plane network element to buffer or drop the data of the first multicast service. For example, after receiving information instructing to deactivate user plane transmission resources of terminals in a multicast group corresponding to the first multicast service for the first time, or after receiving an event publishing notification message sent by the mobility management network element for the first time, the session management network element may obtain an identification information of the user plane network element from the context of the multicast group, and send the first information to the user plane network element based on the identification information of the user plane network element.

[0155] In this embodiment of the present application, the session management network element sending the first information to the user plane network element may be understood as follows: the arrival of data of the first multicast service at the user plane network element is an event. The session management network element sends a configuration, an instruction, or a processing rule corresponding to the event to the user plane network element, so that the user plane network element triggers a report or notification of the event based on the configuration, the instruction, or the processing rule delivered by the session management network element. Alternatively, the session management network element sending the first information to the user plane network element may be understood as follows: the session management network element subscribes to a service provided by the user plane network element. For example, the session management network element sends subscription information for subscribing to the event that data of the first multicast service arrives at the user plane network element to the user plane network element, and the subscription information includes a service type (or a trigger condition). When a service type (or trigger condition) is met, the user plane network element sends notification information to the session management network element.

[0156] Specifically, the session management network element sending the first information to the user plane network element may include: the session management network element sending, to the user plane network element, a user plane connection establishment request message (e.g., a packet forwarding control protocol (PFCP) Session Establishment Request), a user plane connection establishment modification message (e.g., a PFCP Session Modification Request), an N4 Session Establishment Request, or an N4 Session Modification Request message, including processing rules, instructions, configuration, or subscription information t, when data of the first multicast service arrives at the user plane network element. The user plane network element sends a report or notification to the session management network element based on the processing rules, instructions, configuration, or subscription information when data of the first multicast service arrives at the user plane network element, for example, sending a User Plane Connection Report Request (e.g., PFCP Session Report Request), an N4 Session Report Request, or a Downlink Data Notification carrying the notification information.

[0157] The first identification information may be for identifying data of the first multicast service, and the first identification information may be replaced with the identification information of the first multicast service. In this embodiment of the present application, the first identification information or the identification information of the first multicast service may include one or more of a temporary mobile group identifier (TMGI) of a multicast group corresponding to the first multicast service, an internet protocol (IP) address of an application server (e.g., an AF providing data of the first multicast service), a service identifier (service ID) of the first multicast service, packet filter information of data of the first multicast service, or a service data flow (SDF) identification rule of data of the first multicast service.

[0158] Step 502: A user plane network element receives first information and receives data of a first multicast service.

[0159] For example, the user plane network element is an anchor of the first multicast service. If the session management network element is a multicast session management network element that manages a multicast session corresponding to the first multicast service, the user plane network element may receive the first information directly from the session management network element via an N4 link between the user plane network element and the session management network element. If the session management network element is a session management network element that manages a unicast session, the user plane network element may receive the first information from the session management network element via a multicast session management network element that manages the multicast session. The user plane network element may receive data of the first multicast service from the application server.

[0160] For example, the user plane network element is not an anchor of the first multicast service. If the session management network element is a multicast session management network element that manages a multicast session corresponding to the first multicast service, the user plane network element may receive the first information of a unicast session management network element corresponding to the user plane network element. The first information is forwarded to the unicast session management network element by said session management network element (i.e., the multicast session management network element). If the session management network element is a session management network element that manages a unicast session, the user plane network element may directly receive the first information of the session management network element. The user plane network element may receive data of the first multicast service from the anchor of the first multicast service.

[0161] Step 503: The user plane network element sends notification information to the session management network element based on the first information. In response, the session management network element receives the notification information.

[0162] The notification information may indicate that data of the first multicast service has arrived at the user plane network element. The notification information may include information for identifying the data of the first multicast service, such as a TMGI of a multicast group corresponding to the first multicast service, an IP address of an application server, a service identifier of the first multicast service, packet filter information of the data of the first multicast service, or an identification rule of the data of the first multicast service.

[0163] For example, the user plane network element may send an N4 response message to the session management network element, and the N4 response message may carry the notification information. Alternatively, the user plane network element may send the notification information to the session management network element, and the notification information may carry the notification information.

[0164] Moreover, if the first information further indicates to buffer the data of the first multicast service, the user plane network element determines to buffer the data of the first multicast service arriving at the user plane network element based on the first identification information carried in the first information. Thus, upon receiving the data of the first multicast service sent by the application server, the user plane network element does not map the data of the first multicast service to a corresponding QF for transmission, and stores the data of the first multicast service in a buffer.

[0165] Furthermore, if the first information does not instruct to buffer the data of the first multicast service but instructs to drop the data of the first multicast service, after receiving the data of the first multicast service, the user plane network element stops transmitting the data of the first multicast service and drops the received data of the first multicast service, or the user plane network element still continues to transmit the received data of the first multicast service to avoid affecting the reception of the data of the first multicast service by another terminal in a connected state.

[0166] Step 504: The session management network element sends second information to the mobility management network element based on the notification information.

[0167] In one example, in step 501, when the session management network element records a terminal in a preset state in the context of a multicast group corresponding to a first multicast service with terminal granularity, after receiving the notification information, the session management network element determines that data of the first multicast service has arrived at the user plane network element based on the identification information of the first multicast service carried in the notification information. The session management network element finds the context of the multicast group corresponding to the first multicast service by using the identification information of the first multicast service as an index, finds the terminal in a preset state from the context of the multicast group, and separately sends information for triggering the establishment of a communication connection between the terminal and the access network device to the mobility management network element corresponding to the terminal in the preset state based on the correspondence between the terminal and the mobility management network element.

[0168] The correspondence between the terminal and the mobility management network element may include a correspondence between the identification information of the terminal and the ID of the mobility management network element. The correspondence may be stored in the session management network element when the terminal establishes a PDU session. The ID of the mobility management network element is for identifying the mobility management network element. The identification information of the terminal has been described above. Details will not be described again.

[0169] For example, the at least one terminal in the preset state includes a first terminal. The session management network element may send the second information to a mobility management network element corresponding to the first terminal. For example, the session management network element may send a N1N2 Message Transfer (Namf_Communication_N1N2Message Transfer) message to the mobility management network element corresponding to the first terminal, where the N1N2 Message Transfer message carries the second information.

[0170] The second information may be for transmitting data of the first multicast service and for triggering the establishment of a communication connection between the first terminal and the first access network device. The second information may include an identification information of the first terminal (e.g., an identification information of a PDU session of the first terminal) and N2 session management (SM) information. The N2 SM information may be air interface resource configuration information, for allocating air interface resources corresponding to the first multicast service to the first terminal. The N2 SM information may include related information of the first multicast service. The related information of the first multicast service is for triggering the first access network device to allocate air interface resources to the multicast session and to include the first terminal again in the multicast group corresponding to the first multicast service. For example, the related information of the first multicast service may include identification information of the first multicast service, and may further include a quality of service flow identifier (QFI) of a multicast quality of service (QoS) flow, QoS parameter information corresponding to the QFI of the multicast QoS flow, information about a unicast QoS flow corresponding to the multicast QoS flow, one or more QoS profiles of the multicast service, information about a data transmission channel for transmitting uplink data on the core network side (e.g., core network N3 tunnel information), and a multicast session tunnel establishment request or indication. The information about the unicast QoS flow may include a QFI of the unicast QoS flow, and QoS parameter information corresponding to the unicast QoS flow.The QoS parameter information may include one or more of a QFI, an allocation and retention priority (ARP) information, a maximum flow bit rate (MFBR), and a guaranteed flow bit rate (GFBR) information. Optionally, the second information may include a TMGI of a multicast group corresponding to the first multicast service.

[0171] In another embodiment, when in step 501 the session management network element records that there is at least one terminal in a preset state in the multicast group at the granularity of the multicast group, after receiving the notification information, the session management network element determines that the data of the first multicast service has arrived at the user plane network element based on the identification information of the first multicast service carried in the notification information, and transmits information for triggering the establishment of a communication connection between the terminal and the access network device to the mobility management network element corresponding to the multicast group based on the correspondence between the identification information of the mobility management network element and the identification information of the first multicast service in step 501, where the information may carry the above-mentioned N2 SM information. It should be noted that in this example, the information transmitted by the session management network element to the mobility management network element corresponding to the multicast group and for triggering the establishment of a communication connection between the terminal and the access network device may not carry the identification information of a specific terminal, but may carry the TMGI of the multicast group, the identification information of the first multicast service, etc.

[0172] It should be noted that the session management network element may directly send the second information to the mobility management network element, or may send the second information to the mobility management network element via the first network element or another network element, which is not limited in this application.

[0173] Similarly, for a terminal managed by another mobility management network element and in a preset state, the session management network element may send information for triggering establishment of a communication connection between the terminal and the access network device to another mobility management network element until the session management network element sends information for triggering establishment of a communication connection between the terminal and the access network device to the mobility management network elements corresponding to all terminals in the preset state, so that all terminals in the preset state are paged by the mobility management network element and establish a communication connection to the access network device when transitioning from the preset state to the RRC connected state.

[0174] In the present application, one mobility management network element may manage one or more terminals in a multicast group. When the mobility management network element manages multiple terminals and all of the multiple terminals are in a preset state, in a possible design, the session management network element may send multiple second information to the mobility management network element, where the multiple second information have a one-to-one correspondence with the multiple terminals in the preset state. The single second information includes identification information of one terminal, and the second information is for triggering establishment of a communication connection between a terminal corresponding to the second information and the first access network device. In another possible design, to reduce signaling overhead, the session management network element sends one second information to the mobility management network element. The second information may be for triggering establishment of a communication connection between the multiple terminals in the preset state and the first access network device, and the second information may include identification information of the multiple terminals. It should be understood that the second information including identification information of the multiple terminals may be replaced as follows: the second information includes a UE list, and the UE list includes identification information of the multiple terminals.

[0175] For example, it is assumed that the mobility management network element manages a first terminal and a second terminal in a multicast group, and both the first terminal and the second terminal are in a preset state. In this case, the session management network element may transmit two independent second information to the mobility management network element. One second information is for triggering the establishment of a communication connection between the first terminal and the first access network device, and the other second information is for triggering the establishment of a communication connection between the second terminal and the first access network device. Alternatively, in order to reduce signaling overhead, the session management network element transmits one second information to the mobility management network element, and the second information is for triggering the establishment of a communication connection between the first terminal and the first access network device and a communication connection between the second terminal and the first access network device.

[0176] It should be noted that the session management network element may or may not simultaneously transmit information for triggering the establishment of communication connections between terminals in a preset state and an access network device to different mobility management network elements. When a mobility management network element manages multiple terminals and multiple terminals are in a preset state, the session management network element may or may not simultaneously transmit multiple pieces of information for triggering the establishment of communication connections between multiple terminals and an access network device to the mobility management network element. This is not limited.

[0177] For example, the multicast group includes {UE1, UE2, UE3, UE4}, UE1, UE2, and UE3 are in a preset state, UE1 and UE2 are managed by a mobility management network element 1, and UE3 is managed by a mobility management network element 2. After receiving the notification information, the session management network element may send information 1 to the mobility management network element 1 and send information 2 to the mobility management network element 2. The information 1 includes an identification information of UE1 and an identification information of UE2, and the information 1 is for triggering the establishment of a communication connection between UE1 and an access network device and a communication connection between UE2 and an access network device. The information 2 includes an identification information of UE3, and the information 2 is for triggering the establishment of a communication connection between UE3 and an access network device.

[0178] Step 505: The mobility management network element receives second information from the session management network element, and sends fifth information to the first access network device based on the second information.

[0179] The first access network device may be an access network device corresponding to the first terminal, and the first access network device may provide a network service to the first terminal.

[0180] The fifth information may be used by the first access network device to transmit data of the first multicast service and to establish a communication connection between the first access network device and the first terminal. For example, the fifth information may be used by the access network device to allocate air interface resources corresponding to the first multicast service to the first terminal. The fifth information may carry the N2 SM information carried in the second information. Optionally, the fifth information may further carry an identification information of the first terminal or an identification information of the first multicast service (e.g., a TMGI of a multicast group corresponding to the first multicast service), and security configuration information. The security configuration information may include one or more of the following: security configuration information used when data of the first multicast service is transmitted in a unicast manner, or security configuration information used when data of the first multicast service is transmitted in a multicast manner. It should be noted that when the first terminal is in an inactive state, the air interface resources of the first terminal are released, and the security configuration information of the first terminal is still reserved and is not released. Therefore, the fifth information may include N2 SM information and does not include security configuration information. When the first terminal is in an idle state, both the air interface resources of the first terminal and the security configuration information of the first terminal are released, and the fifth information includes N2 SM information and security configuration information.

[0181] For example, when the second information carries the identification information of one terminal, for example, the identification information of the first terminal, after receiving the second information from the session management network element, the mobility management network element searches for the correspondence between the terminal identification information and the terminal state for the preset state of the first terminal by using the identification information of the first terminal carried in the second information as an index. When the first terminal is in an idle state, the mobility management network element obtains a paging area based on the registration area of ​​the first terminal, for example, uses the registration area of ​​the first terminal as the paging area. Then, the mobility management network element sends a paging message to page the first terminal to the first access network device corresponding to the paging area. The first access network device receives and broadcasts the paging message. After the first terminal detects the paging message and establishes an RRC connection, it transitions the state of the first terminal from the idle state to the connected state, and sends a service request message to the mobility management network element via the first access network device. The mobility management network element receives a service request message sent by the first terminal, and establishes an N2 connection between the mobility management network element and the first access network device in response to the service request message sent by the first terminal, so that the state of the terminal changes to a CM connected state, and sends an N2 request to the first access network device, where the N2 request carries fifth information. In this case, the fifth information may carry N2 SM information and security configuration information. When the first terminal is in an inactive state, the mobility management network element sends an N2 request to the first access network device, where the N2 request carries fifth information. In this case, the fifth information may carry N2 SM information and not need to carry security configuration information.

[0182] It should be noted that the second information corresponds to multiple terminals if the second information carries the identification information of multiple terminals, including the identification information of the first terminal, or the second information carries the TMGI of a multicast group corresponding to the first multicast service, and the mobility management network element stores the TMGI of the multicast group and the identification information of the corresponding terminal. After receiving the second information from the session management network element, the mobility management network element may search for the correspondence between the terminal identification information and the terminal state for the preset states of the multiple terminals corresponding to the second information by using the identification information of the terminal carried in the second information as an index, or the mobility management network element searches for the identification information of the terminal corresponding to the TMGI by using the TMGI carried in the second information as an index, and searches for the correspondence between the terminal identification information and the terminal state for the preset states of the multiple terminals corresponding to the second information. When the multiple terminals corresponding to the second information are in an idle state, the mobility management network element performs a calculation on the union of registration areas of the multiple terminals corresponding to the second information to obtain a paging area.

[0183] It should be noted that the present application is not limited to the time sequence in which the first terminal transitions the state of the first terminal from the idle state to the connected state. The first terminal may transition the state of the first terminal from the idle state to the connected state when it receives a paging message, or may transition the state of the first terminal from the idle state to the connected state after the first terminal establishes a communication connection to the access network device. In this case, the connected state may be the RRC connected state.

[0184] In the present application, the mobility management network element may subscribe to the state of each terminal in a multicast group from the first access network device. For example, the mobility management network element may send a subscription request to the first access network device to subscribe to the RRC state of the terminal. The first access network device receives the subscription request, includes a subscription response in the RRC state of the terminal, and notifies the mobility management network element. The mobility management network element receives the subscription response and stores the correspondence between the terminal identity and the terminal state. The RRC state of the terminal may include an RRC state and a CM state, and the CM state includes a CM connected state and a CM idle state. The RRC state may include an idle state, an inactive state, etc.

[0185] Similarly, for another terminal in a preset state, the mobility management network element may send information to an access network device corresponding to another terminal in a preset state to instruct the access network device to establish a communication connection to the terminal based on the above process. For example, a second terminal is a terminal in a preset state, and the second terminal corresponds to a second access network device. The mobility management network element sends sixth information to the second access network device based on the second information, and the sixth information is used by the second access network device to establish a communication connection to the second terminal until information instructing the access network devices corresponding to all terminals in a preset state to establish a communication connection to the terminal in a preset state is sent to the access network device to trigger all terminals in a preset state to establish a communication connection to the access network device.

[0186] In the present application, the same access network device may correspond to or serve one or more terminals in a preset state. When the access network device corresponds to or serves multiple terminals in a preset state, the mobility management network element may send multiple pieces of information to the access network device. The multiple pieces of information have a one-to-one correspondence with the multiple terminals in the preset state, and each piece of information is for establishing a communication connection between the terminal corresponding to the information and the access network device. Alternatively, in order to reduce signaling overhead, the mobility management network element may send one piece of information to the access network device, and the information is for establishing a communication connection between the multiple terminals and the access network device.

[0187] For example, it is assumed that the first access network device corresponds to the first terminal and the second terminal, and the first terminal and the second terminal are in a preset state. In this case, the mobility management network element may send two independent fifth information to the first access network device, one fifth information is for establishing a communication connection between the first terminal and the first access network device, and the other fifth information is for establishing a communication connection between the second terminal and the first access network device. Alternatively, in order to reduce signaling overhead, the mobility management network element sends one fifth information to the first access network device, and the fifth information is for establishing a communication connection between the first terminal and the first access network device, and for establishing a communication connection between the second terminal and the first access network device.

[0188] Step 506: The first access network device receives the fifth information, and establishes a communication connection to the first terminal based on the fifth information.

[0189] For example, after receiving the fifth information, the first access network device allocates air interface resources corresponding to the first multicast service to the first terminal based on the N2 SM information carried in the fifth information. For example, the first access network device configures a corresponding data radio bearer (DRB) for transmitting data of the first multicast service in a unicast manner based on the unicast QFI carried in the N2 SM information and the QoS parameter information corresponding to the unicast QFI, configures a corresponding DRB for transmitting data of the first multicast service in a multicast manner based on the QoS parameter information corresponding to the multicast QFI, and transmits related information of the configured DRB to the first terminal via an RRC connection reconfiguration process or an RRC resumption process, so that the first terminal can receive data of the first multicast service on the DRB. In this way, a communication connection to the first terminal is established. Furthermore, if the fifth information carries security configuration information, the first access network device transmits the security configuration information to the first terminal.

[0190] The RRC connection reconfiguration process may include: when the first terminal is in an idle state, the first access network device performs an RRC connection reconfiguration with the first terminal, and sends an RRC reconfiguration message to the first terminal, carrying related information of the DRB configured by the first access network device. The RRC resumption process may include: when the first terminal is in an inactive state, the first access network device sends a paging message to the first terminal. Upon detecting the paging message, the first terminal transitions the state of the first terminal from an inactive state to a connected state, and sends an RRC message, for example, an RRC resume request message, to the first access network device. The first access network device receives the RRC resume request message, and sends an RRC resume message to the first terminal, carrying related information of the DRB.

[0191] In the present application, the first access network device may send a paging message to the first terminal on a first channel, which may be any one of the following channels: a unicast channel between the first access network device and the first terminal, a common channel, and a dedicated channel of a multicast group corresponding to a first multicast service.

[0192] Similarly, the first access network device may establish a communication connection to another terminal according to the above-mentioned method, and the details will not be described again.

[0193] Further, after step 506, the first access network device sends a first indication information to the mobility management network element, where the first indication information may indicate that the establishment of the communication connection between the first terminal and the first access network device is completed, and the first indication information may include the identification information of the first terminal. If there is no communication connection between the first access network device and the user plane network element and the N2 SM information further includes a multicast session tunnel establishment request, the first access network device further allocates multicast session tunnel information, for example, the tunnel information of the first access network device. The tunnel information of the first access network device is for establishing a tunnel / channel for transmitting data of the first multicast service. The first indication information received by the mobility management network element may include the tunnel information of the first access network device, the QFI of the QoS flow of the PDU session, etc. The mobility management network element sends a PDU session context update request to the session management network element, carrying the tunnel information of the first access network device and the QFI of the QoS flow of the PDU session. The session management network element receives the PDU session context update request and performs an N4 session update in the user plane network element. The user plane network element establishes a communication connection between the user plane network element and the first access network device based on the tunnel information of the first access network device, and then the user plane network element sends an N4 session update response to the session management network element.

[0194] Similarly, for another terminal transitioning from a preset state to a connected state, the first access network device may also send, to the mobility management network element, indication information indicating that the establishment of the communication connection between the terminal and the first access network device is completed. For example, a second terminal is used as an example. The first access network device sends second indication information to the mobility management network element. The second indication information may indicate that the establishment of the communication connection between the second terminal and the first access network device is completed. The second indication information may include identification information of the second terminal.

[0195] It should be noted that in order to reduce signaling overhead, when the same first access network device serves / serves multiple terminals in a preset state, when the multiple terminals in the preset state all perform the process shown in step 506 to establish communication connections to the first access network device, the first access network device may send indication information to the mobility management network element, where the indication information indicates that the multiple terminals in the preset state have established communication connections to the first access network device, and the indication information may include identification information of the multiple terminals.

[0196] Further, after receiving the first indication information, the mobility management network element sends second indication information to the session management network element based on the first indication information. The second indication information may carry identification information of the first terminal, and the second indication information may indicate that the establishment of the communication connection between the first terminal and the first access network device has been completed. Similarly, the mobility management network element receives third indication information from the second access network device, the third indication information indicating that the establishment of the communication connection between the second terminal and the second access network device has been completed. The mobility management network element sends fourth indication information to the session management network element based on the third indication information, and the fourth indication information indicating that the establishment of the communication connection between the second terminal and the second access network device has been completed.

[0197] Alternatively, in order to reduce signaling overhead, the mobility management network element may send one indication information to the session management network element after receiving indication information sent by multiple access network devices and indicating that the establishment of the communication connections is completed. The indication information may indicate that the establishment of all the communication connections is completed, and the session management network element requests the mobility management network element to trigger the establishment of the communication connections. For example, after receiving the first indication information and the second indication information, the mobility management network element sends one indication information to the session management network element based on the first indication information and the second indication information, the indication information includes an identification information of the first terminal and an identification information of the second terminal, and the indication information indicates that the establishment of both the communication connection between the first terminal and the first access network device and the communication connection between the second terminal and the first access network device is completed, or the indication information indicates that the establishment of all the communication connections is completed, and the session management network element requests the mobility management network element to trigger the establishment of the communication connections.

[0198] Alternatively, the mobility management network element sends fifth indication information to the session management network element based on the second preset waiting duration, where the fifth indication information indicates that establishment of all communication connections that the session management network element triggers the mobility management network element to establish has been completed. The mobility management network element sends fifth indication information to the session management network element based on the second preset waiting duration, where the indication information is sent to the session management network element in one of the following two manners:

[0199] Manner 1: The second preset waiting duration may be set as needed. Alternatively, when the mobility management network element requests establishment by multiple access network devices, a preset duration is configured for each of the multiple access network devices, and the shortest preset duration is used as the second preset waiting duration.

[0200] In the first scheme, the mobility management network element maintains a timer, and the duration of the timer is a second preset waiting duration. The timer is started when or immediately after the mobility management network element requests the first access network device to establish a communication connection. When the timer expires after the second preset waiting duration, the fifth indication information is sent to the session management network element. Alternatively, the timer is started when or immediately after the mobility management network element requests the last access network device to establish a communication connection. When the timer expires after the second preset waiting duration, the fifth indication information is sent to the session management network element.

[0201] Method 2: When the mobility management network element requests the establishment by multiple access network devices, one timer is set for each of the multiple access network devices, and the duration of the timer of each access network device is a second preset waiting duration. For each access network device, the timer is started when or immediately after the mobility management network element initiates a request to the access network device to establish a communication connection. When the timers of all the access network devices expire after execution, a fifth indication information is sent to the session management network element.

[0202] Further, optionally, the session management network element receives the indication information, for example, the second indication information, the fourth indication information, or the fifth indication information, sent by the mobility management network element, and determines based on the indication information that the communication connection that the session management network element requests the mobility management network element to trigger is completed. If the session management network element receives the indication information sent by the mobility management network element and determines based on the indication information that the establishment of the communication connection between each terminal in the multicast group corresponding to the first multicast service and the access network device is completed, the session management network element transmits the third information to the user plane network element. Alternatively, if the session management network element receives the indication information, for example, the second indication information or the fourth indication information, sent by the mobility management network element, and determines based on the indication information that the establishment of the communication connection between each of the at least one terminal in the preset state and the access network device is completed, the session management network element transmits the third information to the user plane network element. Alternatively, in addition to relying on the indication information sent by the mobility management network element, the session management network element may send third information to the user plane network element based on the first preset waiting duration.

[0203] The third information may be for notifying the user plane network element to transmit data of the first multicast service. The third information may include second identification information, and the second identification information may include one or more of a TMGI of a multicast group corresponding to the first multicast service, an IP address of an application server, a service identifier of the first multicast service, packet filter information of the data of the first multicast service, or an identification rule of the data of the first multicast service.

[0204] The session management network element sending the third information to the user plane network element based on the first preset waiting duration may include one of the following two manners.

[0205] Method 1: The first preset waiting duration may be set as needed. Alternatively, when a session management network element triggers multiple mobility management network elements to establish a communication connection, a preset period is configured for each of the multiple mobility management network elements, and the shortest preset duration is used as the first preset waiting duration.

[0206] In the first scheme, the session management network element maintains a timer, and the duration of the timer is a first preset waiting duration. The timer is started when or immediately after the session management network element triggers the first mobility management network element to establish the communication connection. When the timer expires after the execution of the first preset waiting duration, the third information is sent to the user plane network element.

[0207] Method 2: The session management network element sets a timer for the first second information to be sent to each mobility management network element, and the duration of the timer is a first preset waiting duration. For each mobility management network element, the timer is started after or when the session management network element sends the first second information to the mobility management network element. When the timer expires after execution, it is determined that the establishment of the communication connection between each terminal corresponding to the mobility management network element and the first access network device is completed. After the timer corresponding to each mobility management network element expires and it is determined that the establishment of the communication connection between each terminal and the first access network device is completed, the third information is sent to the user plane network element.

[0208] Further, the user plane network element receives the third information and transmits the buffered data of the first multicast service based on the third information. For example, the user plane network element may map the data of the first multicast service to the QF and transmit the data to the first access network device by using the QF, and the first access network device transmits the data to the terminal via the communication connection between the first access network device and the terminal. Alternatively, if step 502 is replaced by the user plane network element dropping the received data of the first multicast service based on the first information after receiving the data of the first multicast service, the user plane network element may receive the third information, continue to receive the data of the first multicast service retransmitted by the application server based on the third information, and transmit the data of the first multicast service.

[0209] Based on the method shown in Figure 5, if there is at least one terminal in a preset state in the multicast group corresponding to the multicast service, after receiving the data of the multicast service, the session management network element may be triggered to notify the user plane network element corresponding to the multicast service to first buffer the data of the multicast service, and then trigger paging of the terminal through the core network device, so that the terminal is in a connected state. When a communication connection is established between each terminal in the multicast group and the access network device, the user plane network element is triggered to send the received data or buffered data of the multicast service to the terminal in the multicast group through the access network device, so as to ensure that the terminal in the multicast group receives the data of the multicast service.

[0210] It should be noted that in the embodiments of the present application, words such as "first" and "second" are used to distinguish the same or similar items having basically the same functions and effects. Those skilled in the art may understand that terms such as "first" and "second" do not limit the number or execution order, and terms such as "first" and "second" do not indicate clear differences. For example, the first multicast service in the present application may be replaced with a multicast service.

[0211] With reference to the communication system shown in Figure 3b, the following will describe in detail the method shown in Figure 5 by using an example where the session management network element is an SMF, the user plane network element is a UPF, the access network device is a RAN, the terminals in the multicast group share the same UPF, and the multicast group includes multiple UEs, such as UE1 and UE2. Figures 6a and 6b are flowcharts of a data transmission method according to an embodiment of the present application. As shown in Figures 6a and 6b, the method may include the following steps:

[0212] Step 601: UE1 and UE2 establish PDU sessions separately. After UE1 and UE2 establish PDU sessions, UE1 and UE2 further trigger the SMF to establish a channel for transmitting data of the first multicast service by using a PDU session change request or a join request sent by the user plane to join a multicast group corresponding to a first multicast service in the manner shown in Fig. 1a, and select a QF corresponding to either UE1 or UE2's PDU session as a QF for transmitting data of the first multicast service, for example, select a QF corresponding to UE2's PDU session as a QF for transmitting data of the first multicast service. Alternatively, the SMF provides the RAN with relevant information about the participation of UE1 and UE2, and triggers the RAN to establish a dedicated channel of the multicast group, and the dedicated channel of the multicast group includes a QF for transmitting data of the first multicast service.

[0213] The process in which UE1 and UE2 establish a PDU session can be seen in the prior art and will not be described in detail.

[0214] Furthermore, after the session management network element selects a QF for transmitting the data of the first multicast service, the SMF may configure the UPF to store a correspondence relationship between the downlink tunnel information of the RAN and the QFI, a correspondence relationship between the QFI and the identification information of the multicast service, etc. Furthermore, the SMF further stores a context of a multicast group, where the context of the multicast group includes a correspondence relationship between the identification information of the UE in the multicast group, the identification information of the UPF, and the identification information of the multicast service.

[0215] Step 602: UE1 receives an RRC release message sent by the RAN, and triggers the AMF to send fourth information to the SMF to instruct UE1 to enter an idle state or an inactive state and deactivate user plane transmission resources of UE1.

[0216] For the execution process of step 602, please refer to Figure 2. The details will not be described again.

[0217] UE2 may be in an RRC connected state, and the user plane transmission resources of UE2 may be in a deactivated state or an activated state, which is not limited.

[0218] Step 603: The SMF receives the fourth information and sends the first information to the UPF. In response, the UPF receives the first information.

[0219] For a related description of the first information, please refer to step 501. The first information is used to configure the UPF to send notification information to the SMF when the data of the first multicast service arrives at the UPF. In addition, the first information may further include indication information to instruct the UPF to buffer the data of the first multicast service. Specifically, for a process in which the SMF sends the first information to the UPF, please refer to step 501 in FIG. 5. This is not limited.

[0220] Step 604: The UPF receives and identifies data which is of the first multicast service and sent by the AS.

[0221] Step 605: The UPF buffers the received data of the first multicast service according to the first information received in step 603.

[0222] Alternatively, step 605 may be the UPF sending the received data of the first multicast service or discarding the received data of the first multicast service based on the first information received in step 603.

[0223] Step 606: The UPF sends the notification information to the SMF.

[0224] For relevant descriptions of the notification information and the process of the UPF sending the notification information to the SMF, please refer to the embodiment corresponding to Figure 5. The details will not be described again.

[0225] Step 607: The SMF receives the notification information, finds UE1 according to the notification information, and sends an N1N2 message transfer message carrying second information to the AMF corresponding to UE1. In response, the AMF receives the N1N2 message transfer message.

[0226] For a related description of the second information and the process of the SMF sending an N1N2 message transfer message carrying the second information to the AMF corresponding to UE1, please refer to the embodiment corresponding to Figure 5. Details will not be described again.

[0227] It should be noted that when there are multiple UEs in a preset state in a multicast group and the multiple UEs correspond to one or more AMFs, the SMF may send the N11 message to one or more AMFs separately. One AMF corresponds to one N11 message, and the one N11 message includes identification information of PDU sessions of all UEs in a preset state corresponding to the AMF. Alternatively, one AMF corresponds to multiple N11 messages, and the one N11 message includes identification information of PDU sessions of multiple UEs in a preset state corresponding to the AMF. This is not limited.

[0228] Further, if UE1 is in an idle state, steps 608 to 615 are executed to terminate the procedure, and if UE1 is in an inactive state, steps 610 to 615 are executed to terminate the procedure.

[0229] Step 608: The AMF determines that UE1 is in an idle state, and the AMF sends a paging message to UE1 via the RAN.

[0230] The paging message may be for paging UE 1. The paging message may include identification information of UE 1, etc.

[0231] Step 609: UE1 receives the paging message and sends a service request message to the AMF. In response, the AMF receives the service request message.

[0232] The service request message may request the network side to establish a context for the UE and establish a CM connection between the RAN and the network side. The service request message may include security parameters, identification information of the UE, etc.

[0233] Step 610: The AMF sends the fifth information to the RAN.

[0234] The fifth information carries N2 SM information. For related description of the fifth information, please refer to FIG. 5. Details will not be described again.

[0235] Step 611: The RAN receives the fifth information, and establishes a communication connection between the RAN and the UE1 based on the fifth information.

[0236] Specifically, for step 611, please refer to step 506. Details will not be described again.

[0237] Step 612: The RAN sends first indication information to the AMF, the AMF receives the first indication information, and sends second indication information to the SMF based on the first indication information.

[0238] The first indication information and the second indication information may indicate that the establishment of the communication connection between the RAN and the UE1 has been completed.

[0239] Similarly, when the establishment of a communication connection between the UE and another RAN served by the AMF is completed, an indication information may also be sent to the SMF with reference to the process shown in step 612. The indication information may indicate that the establishment of all communication connections between the RANs and the UE in the multicast group corresponding to the AMF is completed. Note that after receiving the indication information returned by all RANs receiving the N2 SM information and indicating that the establishment of all communication connections is completed, the AMF sends the SMF a fifth indication information indicating that the establishment of all communication connections that the SMF requests the AMF to trigger is completed. Alternatively, the AMF sets a timer, and the duration of the timer is a second preset waiting duration. After the timer expires, the AMF sends the SMF a fifth indication information indicating that the establishment of all communication connections that the SMF requests the AMF to trigger is completed.

[0240] In addition, when the transmission tunnel between the RAN and the UPF is released and the N2 SM information further carries a multicast session tunnel establishment request or instruction, the RAN may further send the RAN downlink tunnel information to the SMF via the AMF, so that the SMF sends the RAN downlink tunnel information to the UPF. The UPF sends data of the first multicast service to the RAN based on the RAN downlink tunnel information, and the RAN sends data to the UEs in the multicast group.

[0241] Step 613: After the SMF receives the second indication information and completes the establishment of communication connections between the access network device and all UEs in the multicast group or at least one UE in the preset state, or after the first preset waiting duration, send an N4 message to the UPF, where the N4 message carries third information.

[0242] The third information may instruct the UPF to transmit data of the first multicast service. The N4 message may further include identification information of the first multicast service, downlink tunnel information of the RAN, etc.

[0243] It should be noted that after receiving the indication information returned by all AMFs that receive the N1N2 message transfer message, the SMF sends an N4 message to the UPF or sets a timer. The duration of the timer is the first preset waiting duration. After the timer expires, the SMF sends an N4 message carrying the third information to the UPF. This is not limited.

[0244] Step 614: The UPF receives the N4 message, and sends the buffered data of the first multicast service based on the N4 message.

[0245] It should be noted that step 614 is optional. Step 614 is performed only if the first information sent by the SMF to the UPF in step 605 includes information instructing the UPF to buffer data of the first multicast service.

[0246] Step 615: The RAN receives data of the first multicast service, and transmits data of the first multicast service.

[0247] Based on the methods shown in Figures 6a and 6b, the SMF instructs the UPF to buffer the data of the first multicast service, so that when some UEs in the multicast group are in an inactive state, the UPF can buffer the data of the first multicast service in time, and the UPF transmits the data of the first multicast service only when all UEs in the multicast group are in a connected state, which can ensure that all UEs can receive the data of the first multicast service without loss.

[0248] In the method shown in Figure 5 or Figure 6b, the data transmission method provided in this embodiment of the present application is described by using an example in which the user plane network element buffers data of the first multicast service under the instruction of the session management network element when there is a terminal in a preset state in the multicast group, triggers paging of the terminal in the preset state, and establishes a communication connection between the terminal and the access network device, and then when the establishment of the communication connection between the terminal in the preset state in the multicast group and the access network device is completed, the session management network element triggers the user plane network element to transmit the buffered data of the first multicast service. Alternatively, the RAN may receive and buffer data of the first multicast service, page the terminal in the preset state, and transmit the buffered data of the first multicast service when the terminal in the preset state in the multicast group transitions to a connected state and establishes a communication connection to the access network device. Please refer to Figure 7 for this method.

[0249] 7 is a flowchart of another data transmission method according to an embodiment of the present application. As shown in FIG. 7, the method may include the following steps:

[0250] Step 701: A user plane network element sends data of a first multicast service to a first access network device. In response, the first access network device receives the data of the first multicast service.

[0251] For the relevant description of the first multicast service, please refer to step 501. The details will not be described again.

[0252] For example, the first access network device may receive data of a first multicast service from a user plane network element corresponding to the first multicast service via a downlink transmission tunnel between the first access network device and the user plane network element.

[0253] Step 702: If there is at least one terminal served by the first access network device in a multicast group corresponding to the first multicast service and in a preset state, the first access network device buffers data of the first multicast service.

[0254] For example, the first access network device may determine whether a terminal that is served by the first access network device and is in a multicast group corresponding to a first multicast service is in a preset state through the RRC connection release process shown in Figure 2. For example, the first terminal is used as an example. After receiving an RRC release message from the first terminal, the first access network device determines that the first terminal is in a preset state: RRC_idle state or RRC_inactive state based on the RRC release message sent by the first terminal.

[0255] Step 703: The first access network device sends a paging message to the first terminal. In response, the first terminal receives the paging message.

[0256] The paging message may be for paging the first terminal, so that the first terminal transitions from a preset state to an RRC connected state, for example, transitions from an idle state to an RRC connected state, or transitions from an inactive state to an RRC connected state. The first terminal is included in at least one terminal in a preset state. The paging message may include identification information of the first terminal. The identification information of the first terminal is described in the manner shown in FIG. 5. Details will not be described again.

[0257] For example, the first access network device may send a paging message to the first terminal on a first channel, which may include any one of the following channels: a unicast channel between the first access network device and the first terminal, a common channel, and a dedicated channel of a multicast group corresponding to a first multicast service.

[0258] Similarly, in the case of another terminal in a preset state, the first access network device may also send a paging message to the other terminal. For example, the at least one terminal in a preset state further includes a second terminal, and the first access network device sends a paging message to the second terminal to page the second terminal. The rest may be inferred by analogy until the first access network device pages all of the at least one terminal in a preset state. It should be noted that the first access network device may or may not page the at least one terminal in a preset state at the same time. This is not limited.

[0259] Further, optionally, the method illustrated in FIG. 7 may further include the following steps:

[0260] Step 704: The first terminal sends a first RRC message to the first access network device. In response, the first access network device receives the first RRC message from the first terminal.

[0261] The first RRC message may be requested to establish a communication connection between the first terminal and the first access network device, and the communication connection may be for transmitting data of the first multicast service. When the first terminal is in an idle state, the first RRC message may be a service request message. When the first terminal is in an inactive state, the first RRC message may be an RRC resume request message.

[0262] Similarly, all terminals receiving the paging message sent by the first access network device may send a first RRC message to the first access network device based on step 704 to request the first access network device to establish a communication connection to the terminal.

[0263] Step 705: The first access network device obtains fifth information from the mobility management network element based on the first RRC message.

[0264] The fifth information may be for establishing a communication connection between the first terminal and the first access network device. For a related description of the fifth information, please refer to the description of step 505. Details will not be described again.

[0265] For example, the fifth information may be N2 SM information. The first access network device may obtain the fifth information from the mobility management network element, and the mobility management network element may obtain the fifth information from the session management network element. The mobility management network element obtaining the fifth information from the session management network element may include: the mobility management network element sending fourth information to the session management network element for deactivating user plane transmission resources of the first terminal, the session management network element receiving the fourth information from the mobility management network element, and sending the fifth information to the mobility management network element in response to the fourth information by using the fourth information as a trigger condition. Alternatively, the session management network element sending a subscription request to the mobility management network element based on the fourth information, the subscription request is for requesting to subscribe to a first event, and the first event is the first terminal transitioning from a preset state to a connected state. When the session management network element receives the first event notified by the mobility management network element, the session management network element sends fifth information to the mobility management network element.

[0266] For the related description of the fourth information, please refer to the method shown in Figure 5. The details will not be described again.

[0267] Step 706: The first access network device sends seventh information to the first terminal based on the fifth information.

[0268] The seventh information indicates an associated configuration of a communication connection between the first terminal and the first access network device, e.g., air interface resources / DRB configured for the first terminal and for transmitting data of the first multicast service.

[0269] For example, after receiving the fifth information, the first access network device allocates air interface resources corresponding to the first multicast service to the first terminal based on the N2 SM information carried in the fifth information. For example, the first access network device configures a corresponding DRB for transmitting data of the first multicast service in a unicast manner based on the unicast QFI carried in the N2 SM information and the QoS parameter information corresponding to the unicast QFI, configures a corresponding DRB for transmitting data of the first multicast service in a multicast manner based on the QoS parameter information corresponding to the multicast QFI, and sends related information of the configured DRB to the first terminal via an RRC connection reconfiguration process or an RRC resume process, so that the first terminal can receive data of the first multicast service on the DRB. Furthermore, if the fifth information carries security configuration information, the first access network device sends the security configuration information to the first terminal.

[0270] In this way, the establishment of a communication connection between the first access network device and the first terminal is completed.

[0271] Similarly, referring to the above process, the other terminal may transition to a connected state, and a communication connection between the other terminal in the preset state and the first access network device is established. Details are not described again.

[0272] Further, if there are no terminals served by the first access network device in a multicast group corresponding to the first multicast service and in a preset state, the first access network device transmits buffered data of the first multicast service.

[0273] Alternatively, the first access network device transmits the buffered data of the first multicast service based on the third preset waiting duration. For example, a timer is set, and the duration of the timer is equal to the third preset waiting duration. The first access network device starts the timer when it starts paging the terminal. After the execution of the timer ends, the first access network device transmits the buffered data of the first multicast service. In other words, the buffered data of the first multicast service is transmitted only after the timer expires, so as to reduce the packet loss problem of the terminal in the multicast group as much as possible.

[0274] For example, it is assumed that the first access network device serves the multicast group 1, and there are 10 terminals in the multicast group, 3 terminals in the connected state, and 7 terminals in the idle state. The 7 terminals in the idle state have different speeds of transitioning from the idle state to the connected state. In addition, the 3 terminals in the connected state do not need to be paged first, that is, the terminals are already in the connected state. Therefore, if the air interface resources are immediately allocated to the terminal in the connected state to transmit the buffered data of the first multicast service, when another terminal returns to the connected state at a slow speed and is still in the process of returning to the connected state and establishing a communication connection, a packet loss problem of another terminal for the data of the first multicast service will be generated, affecting the service experience of another terminal in the multicast group. The purpose of setting a timer by the first access network device and transmitting the buffered data of the first multicast service after the timer expires is to enable most terminals in the multicast group to return to the connected state and establish a communication connection as much as possible within the duration of the timer, thereby reducing the packet loss problem of the terminals in the multicast group as much as possible.

[0275] Based on the method shown in FIG. 7, when there is at least one terminal in a preset state in a multicast group served by a first access network device and corresponding to a first multicast service, after receiving the data of the multicast service, the first access network device is triggered to first buffer the data of the multicast service, and then pages the terminal so that the terminal enters a connected state, and transmits the buffered data of the multicast service to ensure that the terminals in the multicast group receive the data of the multicast service when all the terminals in the multicast group have established a communication connection with the first access network device.

[0276] With reference to the communication system shown in Fig. 3b, the following will describe in detail the method shown in Fig. 7 by using an example in which the session management network element is an SMF, the mobility management network element is an AMF, the user plane network element is a UPF, the first access network device is a RAN, the terminals in the multicast group share the same UPF, and UE1 and UE2 corresponding to / served by the RAN are in a multicast group corresponding to a first multicast service. Fig. 8a is a flowchart of another data transmission method according to an embodiment of the present application. As shown in Fig. 8a, the method may include the following steps:

[0277] Step 801: UE1 and UE2 establish PDU sessions separately. After UE1 and UE2 establish PDU sessions, UE1 and UE2 further trigger the SMF to establish a channel for transmitting data of the first multicast service by using a PDU session change request or a join request sent by the user plane to join a multicast group corresponding to a multicast service, and select a QF corresponding to the PDU session of either UE1 or UE2 as a QF for transmitting data of the first multicast service in the manner shown in Fig. 1a, for example, select a QF corresponding to the PDU session of UE2 as a QF for transmitting data of the first multicast service.

[0278] For step 801, please refer to step 601. The details will not be explained again.

[0279] Step 802: UE1 receives an RRC release message sent by the RAN, and triggers the AMF to send fourth information to the SMF to instruct UE1 to enter an idle or inactive state and deactivate user plane transmission resources of UE1.

[0280] For step 802, please refer to step 602. The details will not be explained again.

[0281] Further, after receiving the fourth information, the SMF may send fifth information to the AMF in response to the fourth information, and the AMF receives and stores the fifth information, or the SMF subscribes to a first event from the AMF, and the first event is that UE1 transitions from the preset state to the connected state.

[0282] For related descriptions of the fourth information and the fifth information, please refer to the embodiment corresponding to Fig. 5. The details will not be described again.

[0283] Step 803: The UPF receives and identifies data which is of a first multicast service and sent by the AS.

[0284] Step 804: The UPF sends data of the first multicast service to the RAN.

[0285] Step 805: The RAN receives data of the first multicast service, and buffers the data of the first multicast service.

[0286] For example, the RAN may learn that UE1 in a preset state exists in a multicast group according to step 802, and buffer data of the first multicast service.

[0287] Step 806: The RAN sends a paging message to UE1.

[0288] Step 807: UE1 receives the paging message and sends a first RRC message to the RAN.

[0289] The first RRC message may be a service request message or an RRC resume request message.

[0290] Step 808: The RAN receives the first RRC message and obtains the fifth information from the AMF.

[0291] Specifically, for the relevant description of the fifth information, please refer to the embodiment corresponding to FIG. 5. The details will not be described again.

[0292] In one example, when UE1 enters the preset state in step 802, specifically, when the SMF receives the fourth information sent by the AMF, the SMF is triggered to send the fifth information to the AMF in advance, and the AMF stores the fifth information. After receiving the first RRC message, the RAN is triggered to obtain the fifth information from the AMF.

[0293] In another embodiment, after receiving the first RRC message, the RAN notifies the SMF of the first event via the AMF and triggers the SMF to send fifth information to the RAN via the AMF, so that the RAN determines the fifth information based on the fifth information.

[0294] Step 809: The RAN sends the seventh information to UE1 based on the fifth information.

[0295] The seventh information indicates an associated configuration of a communication connection between UE1 and the first access network device, e.g., air interface resources / DRB configured for UE1 and for transmitting data of the first multicast service.

[0296] For step 809, please refer to step 506. The details will not be explained again.

[0297] Step 810: The RAN determines that there is no UE in a preset state in a multicast group served by the RAN and corresponding to a first multicast service, and the RAN transmits data of the first multicast service to the UEs in the multicast group via a communication connection between the RAN and the UEs in the multicast group.

[0298] According to the method shown in Fig. 8a, when there is no UE in a preset state in the multicast group served by the RAN and corresponding to the first multicast service, the RAN buffers the data of the first multicast service in time. When there is no UE in a preset state in the multicast group served by the RAN, the RAN transmits the data of the first multicast service. This can ensure that the UEs in all states can receive the data of the first multicast service without loss.

[0299] It should be understood that, in order to reduce signaling overhead, after receiving notification information indicating that the user plane network element has received the data of the first multicast service, the session management network element may instruct the mobility management network element to a terminal to join the multicast group by using a signaling message, so that the mobility management network element pages the terminal in an idle state to receive the data of the first multicast service. Specifically, please refer to Figure 8b for this method.

[0300] Figure 8b shows another data transmission method according to an embodiment of the present application. As shown in Figure 8b, the method may include the following steps:

[0301] S8b1: The session management network element sends a UE list of a multicast group to the mobility management network element, and in response, the mobility management network element receives the UE list of the multicast group.

[0302] The session management network element may be the SMF of Fig. 3b. The session management network element may manage a PDU session of the terminal, and the PDU session is associated with a multicast session corresponding to the multicast group. The mobility management network element may be the AMF of Fig. 3b, and the terminal that joins the multicast group may perform network registration via the mobility management network element.

[0303] The UE list may indicate / correspond to the terminals joining the multicast group. It should be understood that the terminals joining the multicast group in this specification may include all terminals joining the multicast group, or may include some terminals among the terminals joining the multicast group, for example, may include terminals joining the multicast group and being in a preset state, or may include terminals among the terminals managed by the session management network element that satisfy the following conditions: joining the multicast group, joining the multicast group and being in a preset state, or joining the multicast group and not establishing a communication connection for transmitting data of the first multicast service.

[0304] Specifically, the UE list may include identification information of multiple terminals participating in the multicast group. It should be noted that the identification information of multiple terminals included in the UE list and participating in the multicast group may be the identification information of the terminals sending a multicast group join request to the session management network element, not the identification information of all terminals participating in the multicast group in the network. In other words, the UE list may correspond to the identification information of the terminals participating in the multicast group stored by the session management network element. For example, the UE list may include the identification information of the first terminal, the identification information of the second terminal, etc. The UE list may be carried in the second information, and the second information may be for triggering the establishment of a communication connection between the terminal participating in the multicast group and the access network device, and the communication connection is for transmitting data of the first multicast service. The second information may further carry the identification information of the multicast group. Specifically, please refer to step 504 for a related description of the second information.

[0305] For example, the session management network element may receive notification information from the user plane network element to notify that data of the first multicast service has been received, and send second information carrying a UE list of a multicast group to the mobility management network element based on the notification information. Specifically, for an implementation process in which the session management network element sends the second information, please refer to steps 501 to 504.

[0306] S8b2: The mobility management network element determines an idle terminal among the terminals indicated by the UE list, and sends a paging message to the idle terminal.

[0307] In S8b2, in order to ensure that the terminal can normally receive data of the first multicast service through the communication connection, the corresponding terminal in the idle state (or referred to as CM-IDLE state) needs to be further transitioned to the connected state (or referred to as CM-CONNECTED state). In the present application, the terminal in the idle state may be paged by a group paging manner. Specifically, the group paging manner may include: a mobility management network element determines a terminal in the idle state among the terminals indicated by the UE list, obtains a registration area of ​​the terminal in the idle state, obtains a first paging area through calculation based on the registration area of ​​the terminal in the idle state, and sends a paging message carrying the identification information of the multicast group in the first paging area.

[0308] There may be one or more terminals in an idle state. The mobility management network element's determining of a terminal in an idle state among the terminals indicated by the UE list may include: the mobility management network element may search for a context of the terminal stored by the mobility management network element by using the identification information of the terminal as an index, and determine that the terminal is in an idle state if the terminal status information in the found context of the terminal indicates that the terminal is in an idle state (e.g., the terminal context includes an idle radio network temporary identifier (I-RNTI)) or the terminal context does not include an AMF UE Next Generation Application Protocol ID (AMF UE NGAP ID).

[0309] In this embodiment of the present application, the paging message may be for paging a terminal in an idle state. In a group paging scheme, the paging message may carry the identification information of a multicast group. After a terminal that needs to receive data of a first multicast service detects a paging message carrying the identification information of a multicast group on a paging channel, the terminal may transition from an idle state to a connected state.

[0310] For example, the terminals in the idle state may include a first terminal and a second terminal, and the mobility management network element may transmit a paging message carrying an identification information of a multicast group in a first paging area, and if the first terminal is successfully paged, the mobility management network element may receive a service request message from the first terminal, and / or if the second terminal is successfully paged, the mobility management network element may receive a service request message from the second terminal.

[0311] In this embodiment of the present application, the registration area of ​​each terminal may be configured by a mobility management network element and pre-assigned to the terminal. The registration area of ​​each terminal may include one or more cells, and the registration area of ​​the terminal may include the signal area coverage areas of one or more access network devices. For example, the registration area of ​​UE1 may include the signal area coverage areas of base stations in area 1, area 2, and area 3.

[0312] The first paging area includes the registration area of ​​the first terminal and the registration area of ​​the second terminal, i.e., includes the union / universal set of the registration area of ​​the first terminal and the registration area of ​​the second terminal. Optionally, in order to allow more terminals to receive the data of the first multicast service, the first paging area further includes the registration areas of terminals other than the first terminal and the second terminal in the UE list. Alternatively, the first paging area further includes the registration areas of terminals in idle state other than the first terminal and the second terminal in the UE list. In this way, group paging can be initiated in the registration areas of more terminals, so that more terminals are paged to receive the data of the first multicast service.

[0313] For example, the UE list includes UE1 to UE3, and registration areas are pre-assigned to UE1 and UE2 in idle state. For example, the registration area of ​​UE1 includes Area 1, Area 2, and Area 3, and the registration area of ​​UE2 includes Area 2, Area 3, and Area 4. Group paging is assumed to be performed at a granularity of multiple UEs. Since Areas 2 and 3 in the registration area of ​​UE1 overlap with Areas 2 and 3 in the registration area of ​​UE2, there is no overlapping area between Area 1 in the registration area of ​​UE1 and the registration area of ​​UE2, and there is no overlapping area between Area 4 in the registration area of ​​UE2 and the registration area of ​​UE1, in a paging cycle, a paging message carrying a multicast group identification information (e.g., MBS Session ID) may be transmitted in Area 1, Area 2, Area 3, and Area 4. Compared with paging at a granularity of UE, this solution reduces paging signaling overhead. Alternatively, a paging message carrying identification information of the multicast group (e.g., an MBS session ID) is transmitted in Area 1, Area 2, Area 3, Area 4, and the registration area of ​​UE3 so that more terminals can be paged to receive data of the first multicast service.

[0314] Further, optionally, in the case of a terminal that has not established a communication connection to an access network device for transmitting data of the first multicast service, in order to ensure successful transmission of the data of the first multicast service, the method further includes the following steps:

[0315] S8b3: The mobility management network element sends, to an access network device corresponding to the terminal, information used by the access network device to establish a communication connection to the terminal joining the multicast group.

[0316] The access network devices may include one or more access network devices that have not established a communication connection for transmitting data of the first multicast service. The mobility management network element sending, to the access network devices, information used by the access network devices to establish a communication connection to a terminal joining the multicast group may include: the mobility management network element separately sending, to the one or more access network devices, the information for establishing a communication connection to the terminal.

[0317] For example, when the first terminal and the second terminal do not establish a communication connection for transmitting data of the first multicast service to the access network device, the first terminal corresponds to the first access network device, the second terminal corresponds to the second access network device, and the mobility management network element may separately transmit to the first access network device the fifth information used by the first access network device to establish a communication connection to the first terminal, and to the second access network device the sixth information used by the second access network device to establish a communication connection to the second terminal. Specifically, for the related description and transmission manner of the fifth information and the sixth information, please refer to step 505. Details will not be described again.

[0318] It should be understood that the time sequence in which the mobility management network element separately transmits to the access network device corresponding to the terminal the information used by the access network device to establish a communication connection to the terminal that joins the multicast group is not limited in the present application. For example, the fifth information and the sixth information may be transmitted consecutively or simultaneously. This is not limited.

[0319] S8b4: The access network device establishes a communication connection to the terminal based on the information used by the access network device to establish a communication connection to the terminal joining the multicast group.

[0320] Specifically, for S8b4, please refer to the process in which the first access network device establishes a communication connection to the first terminal in step 506. Details will not be described again.

[0321] Based on the method shown in Fig. 8b, group paging may be triggered in a registration area of ​​multiple terminals by using one signaling message to reduce paging signaling overhead. In addition, to reduce signaling overhead, communication connections between multiple terminals and an access network device for receiving data of a multicast service are established.

[0322] The above mainly describes the solutions provided in the embodiments of the present application from the perspective of interactions between nodes. It will be understood that, in order to implement the aforementioned functions, the nodes, such as the session management network element, the mobility management network element, the user plane network element, and the first access network device, each include corresponding hardware structures and / or software modules for implementing each function. In combination with the algorithms and steps in the examples described in the embodiments disclosed herein, those skilled in the art should easily realize that the present application can be implemented by hardware or a combination of hardware and computer software. Whether the functions are performed by hardware or by hardware driven by computer software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the functions described for each specific application, but the implementation form should not be considered to go beyond the scope of the present application.

[0323] In the embodiment of the present application, based on the above-mentioned method example, functional module division may be performed for the session management network element, the mobility management network element, the user plane network element, the first access network device, etc., for example, the functional module may be divided based on the function, or two or more functions may be integrated into one processing module. The integrated module may be implemented in the form of hardware, or may be implemented in the form of a software function module. It should be noted that in the embodiment of the present application, the division of the module is an example, and is merely a logical functional division. In actual implementation, another division method may be used.

[0324] 9 is a schematic block diagram of a communication device 90 according to an embodiment of the present application. The communication device 90 may be a session management network element, or a chip or a system-on-chip in the session management network element. In a possible design, as shown in FIG. 9, the communication device 90 may include a transmitting unit 901 and a receiving unit 902.

[0325] The sending unit 901 is configured to send first information to the user plane network element when there is at least one terminal in a preset state in a multicast group corresponding to the first multicast service, and the first information is used by the user plane network element to send notification information to the session management network element when data of the first multicast service arrives at the user plane network element. For example, the sending unit 901 may be configured to support the communication device 90 in performing steps 501 and 603.

[0326] The receiving unit 902 is configured to receive notification information from the user plane network element, where the notification information indicates that data of the first multicast service has arrived at the user plane network element. For example, the receiving unit 902 is configured to support the communication device 90 in performing steps 504 and 607.

[0327] The sending unit 901 is further configured to send second information to the mobility management network element based on the notification information, the second information is for triggering establishment of a communication connection between the first terminal and the first access network device, and the first terminal belongs to at least one terminal in a preset state. For example, the sending unit 901 is configured to support the communication device 90 in performing steps 504 and 607.

[0328] Specifically, in a possible design, all the relevant contents of the steps related to the session management network element in the above-mentioned method embodiment in Figure 5 and Figure 6a and Figure 6b may be cited in the functional description of the corresponding functional module. The details will not be described again here. The communication device 90 in the possible design is configured to perform the functions of the session management network element in the data transmission method shown in Figure 5 and Figure 6a and Figure 6b, and thus can achieve the same effect as that achieved by the above-mentioned data transmission method.

[0329] It should be noted that in another possible implementation, the communication device 90 shown in FIG. 9 may include a processing module and a communication module. The functions of the sending unit 901 and the receiving unit 902 may be integrated into the communication module. The processing module is configured to control and manage the operation of the communication device 90. For example, the processing module is configured to support the communication device 90 in performing another process of the technology described herein. The communication module is configured to perform steps 501, 504, 607, etc., and support the communication device 90 in communicating with another network entity. Furthermore, the communication device 90 shown in FIG. 9 may further include a storage module configured to store program codes and data of the communication device 90.

[0330] The processing module may be a processor or a controller. The processor may implement or execute various exemplary logic blocks, modules, and circuits described with reference to the contents disclosed in this application. Alternatively, the processor may be a combination of processors implementing computing functions, such as a combination of one or more microprocessors, or a combination of a DSP and a microprocessor. The communication module may be a transceiver circuit, or a communication interface, or the like. The storage module may be a memory. If the processing module is a processor, the communication module is a communication interface, and the storage module is a memory, the communication device 90 shown in FIG. 9 may be the communication device 400 shown in FIG. 4.

[0331] 10 is a schematic configuration diagram of a communication device 100 according to an embodiment of the present application. The communication device 100 may be a user plane network element, or a chip or a system-on-chip in a user plane network element. As shown in FIG. 10, the communication device 100 may include a receiving unit 1001 and a transmitting unit 1002.

[0332] The receiving unit 1001 is configured to receive first information from the session management network element, the first information being used by the user plane network element to send notification information to the session management network element when data of the first multicast service arrives at the user plane network element, and to receive data of the first multicast service. For example, the receiving unit 1001 is configured to support the communication device 100 in performing steps 502 and 603.

[0333] The sending unit 1002 is configured to send notification information to the session management network element based on the first information, where the notification information indicates that data of the first multicast service has arrived at the user plane network element. For example, the sending unit 1002 is configured to support the communication device 100 in performing steps 502, 605, and 606.

[0334] Specifically, in a possible design, all relevant contents of the steps related to the user plane network element in the above-mentioned method embodiment in Figure 5 and Figure 6a and Figure 6b may be cited in the functional description of the corresponding functional module. Details will not be described again here. The communication device 100 in the possible design is configured to perform the functions of the user plane network element in the data transmission method shown in Figure 5 and Figure 6a and Figure 6b, and thus can achieve the same effect as that achieved by the above-mentioned data transmission method.

[0335] It should be noted that in another possible implementation, the communication device 100 shown in FIG. 10 may include a processing module and a communication module. The functions of the receiving unit 1001 and the transmitting unit 1002 may be integrated into the communication module. The processing module is configured to control and manage the operation of the communication device 100. For example, the processing module is configured to support the communication device 100 in performing another process of the technology described herein. The communication module is configured to perform step 502, step 605, step 606, etc., and support the communication device 100 in communicating with another network entity. Furthermore, the communication device 100 shown in FIG. 10 may further include a storage module configured to store program codes and data of the communication device 100. If the processing module is a processor, the communication module is a communication interface, and the storage module is a memory, the communication device 100 shown in FIG. 10 may be the communication device 400 shown in FIG. 4.

[0336] 11 is a schematic diagram of a communication device 110 according to an embodiment of the present application. The communication device 110 may be a mobility management network element, or a chip or a system-on-chip in the mobility management network element. As shown in FIG. 11, the communication device 110 may include a receiving unit 1101 and a transmitting unit 1102.

[0337] The receiving unit 1101 is configured to receive second information from the session management network element, the second information is for triggering establishment of a communication connection between the first terminal and the first access network device, the communication connection is for transmitting data of the first multicast service. For example, the receiving unit 1101 is configured to support the communication device 110 in performing steps 505 and 607.

[0338] The sending unit 1102 is configured to send fifth information to the first access network device based on the second information, and the fifth information is used by the first access network device to establish a communication connection to the first terminal. For example, the sending unit 1102 is configured to support the communication apparatus 110 in performing steps 505 and 610.

[0339] In another possible design, the receiving unit 1101 is configured to receive a user equipment list (UE list) of a multicast group from the session management network element, the multicast group corresponding to the first multicast service, and the UE list indicating terminals to join the multicast group. For example, the receiving unit 1101 is configured to support the communication device 110 in performing S8b1.

[0340] The sending unit 1102 is configured to send a paging message to a terminal in an idle state among the terminals indicated by the UE list. For example, the sending unit 1102 is configured to support the communication device 110 in performing S8b2.

[0341] Specifically, in a possible design, all relevant contents of the steps related to the mobility management network element in the above-mentioned method embodiment in Figure 5, Figure 6a and Figure 6b, and Figure 8b may be cited in the functional description of the corresponding functional module. Details will not be described again here. The communication device 110 in the possible design is configured to perform the functions of the mobility management network element in the data transmission method shown in Figure 5, Figure 6a and Figure 6b, and Figure 8b, and thus can achieve the same effect as that achieved by the above-mentioned data transmission method.

[0342] It should be noted that in another possible implementation, the communication device 110 shown in FIG. 11 may include a processing module and a communication module. The functions of the receiving unit 1101 and the transmitting unit 1102 may be integrated into the communication module. The processing module is configured to support the communication device 110 in controlling and managing the operation of the communication device 110. The communication module is configured to perform steps 505, 607, 610, S8b1, S8b2, etc., and support the communication device 110 in communicating with another network entity. Furthermore, the communication device 110 shown in FIG. 11 may further include a storage module configured to store program codes and data of the communication device 110. If the processing module is a processor, the communication module is a communication interface, and the storage module is a memory, the communication device 110 shown in FIG. 11 may be the communication device 400 shown in FIG. 4.

[0343] 12 is a schematic diagram of a communication device 120 according to an embodiment of the present application. The communication device 120 may be a first access network device, or a chip or system-on-chip in the first access network device. As shown in FIG. 12, the communication device 120 may include a receiving unit 1201, a processing unit 1202, and a sending unit 1203.

[0344] The receiving unit 1201 is configured to receive data of a first multicast service. For example, the receiving unit 1201 can support the communication device 120 in performing steps 701 and 805.

[0345] When there is at least one terminal served by the first access network device in the multicast group corresponding to the first multicast service in the preset state, the processing unit 1202 is configured to buffer data of the first multicast service. For example, the processing unit 1202 can support the communication device 120 in performing steps 702 and 805.

[0346] The sending unit 1203 is configured to send a paging message for paging a first terminal, the first terminal being in a preset state and belonging to at least one terminal served by the first access network device. For example, the sending unit 1203 can support the communication device 120 in performing step 703 and step 806.

[0347] Further, the receiving unit 1201 may be further configured to receive an RRC message from the first terminal, where the RRC message is for requesting to establish a communication connection between the first terminal and the first access network device, where the communication connection is for transmitting data of the first multicast service. For example, the receiving unit 1201 can support the communication device 120 in performing step 704 and step 808.

[0348] The sending unit 1203 may be further configured to send seventh information to the first terminal. For example, the sending unit 1203 may support the communication device 120 in performing steps 705 and 809.

[0349] Specifically, in a possible design, all relevant contents of the steps related to the first access network device in the above-mentioned method embodiment in Figures 7 to 8b may be cited in the functional description of the corresponding functional modules. Details will not be described again here. The communication device 120 in the possible design is configured to perform the functions of the first access network device in the data transmission method shown in Figures 7 to 8b, and thus can achieve the same effects as those achieved by the above-mentioned data transmission method.

[0350] It should be noted that in another possible implementation, the communication device 120 shown in FIG. 12 may include a processing module and a communication module. The processing module may integrate the functions of the processing unit 1202, and the communication module may integrate the functions of the receiving unit 1201 and the transmitting unit 1203. The processing module is configured to perform step 702 and step 805 to support the communication device 120 in controlling and managing the operation of the communication device 120. The communication module is configured to perform step 701, step 805, step 703, step 806, step 705, step 809, etc. to support the communication device 120 in communicating with another network entity. Furthermore, the communication device 120 shown in FIG. 12 may further include a storage module configured to store program codes and data of the communication device 120. If the processing module is a processor, the communication module is a communication interface, and the storage module is a memory, the communication device 120 shown in FIG. 12 may be the communication device 400 shown in FIG. 4.

[0351] 13 is a schematic configuration diagram of a communication system according to an embodiment of the present application. As shown in FIG. 13, the communication system may include a terminal 130, an AMF 131, an SMF 132, a RAN 133, and a UPF 134.

[0352] The function of the SMF 132 is the same as that of the communication device 90. The function of the UPF 134 is the same as that of the communication device 100. The function of the AMF 131 is the same as that of the communication device 110. The function of the RAN 133 is the same as that of the communication device 120.

[0353] For example, in a possible design, the SMF 132 is configured to send first information to the UPF 134 when there is at least one terminal 130 in a preset state in a multicast group corresponding to a first multicast service, the UPF 134 being an anchor corresponding to the first multicast service, and the first information instructs the UPF 134 to send notification information to a session management network element when data of the first multicast service arrives at a user plane network element.

[0354] The UPF 134 is configured to receive first information from the SMF 132. When the data of the first multicast service arrives at the UPF 134, the UPF 134 sends notification information to the SMF 132, where the notification information indicates that the data of the first multicast service has arrived at the UPF 134.

[0355] The SMF132 is further configured to receive the notification information returned by the UPF134 and send second information to the AMF131 based on the notification information, the second information being for triggering establishment of a communication connection between the first terminal 130 and the RAN133, the first terminal 130 being a terminal included in the at least one terminal 130 in a preset state and managed by the AMF131.

[0356] The AMF 131 is configured to receive second information from the SMF 132 and transmit fifth information to the RAN 133 based on the second information, the second information being for triggering establishment of a communication connection between the first terminal 130 and the RAN 133, and the fifth information instructing the RAN 133 to establish a communication connection between the RAN 133 and the first terminal 130.

[0357] In a possible design, the RAN 133 is configured to receive data of a first multicast service, buffer the data of the first multicast service, and send a paging message to the first terminal 130 to page the first terminal 130 when there is at least one terminal 130 in a preset state in a multicast group served by the RAN 133 and corresponding to the first multicast service.

[0358] In another possible design, the SMF 132 is configured to send a UE list of a multicast group to the AMF 131, where the multicast group corresponds to a first multicast service, and the UE list indicates the terminals that will join the multicast group.

[0359] The AMF 131 is configured to receive a user equipment list (UE list) of a multicast group from the SMF 132, the multicast group corresponds to a first multicast service, and to send a paging message to terminals in an idle state among the terminals indicated by the UE list.

[0360] Specifically, for the execution process of each network element in Figure 13, please refer to the execution steps of the corresponding network element in the above-mentioned method in Figures 5 to 8b, and details will not be described here.

[0361] An embodiment of the present application further provides a computer-readable storage medium. All or part of the processes in the aforementioned method embodiments may be implemented by a computer program instructing relevant hardware. The program may be stored in a computer-readable storage medium. When the program is executed, the processes of the aforementioned method embodiments may be included. The computer-readable storage medium may be, for example, an internal storage unit of the terminal device in any one of the aforementioned embodiments, including the data sender and / or the data receiver. For example, the computer-readable storage medium may be a hard disk or memory of the terminal device. Alternatively, the computer-readable storage medium may be an external storage device of the terminal device, for example, a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, or a flash card configured in the terminal device. Furthermore, the computer-readable storage medium may include both the internal storage unit of the terminal device and the external storage device. The computer-readable storage medium is configured to store the computer program, as well as other programs and data required by the terminal device. The computer-readable storage medium may be further configured to temporarily store the output data or the outputted data.

[0362] An embodiment of the present application further provides computer instructions. All or part of the procedures in the above-mentioned method embodiments may be implemented by computer instructions that instruct related hardware (such as computers, processors, network devices, and terminals). The program may be stored in the above-mentioned computer-readable storage medium.

[0363] In the embodiment of the present application, it should be understood that "B corresponding to A" indicates that B is associated with A. For example, B may be determined based on A. It should be further understood that determining B based on A does not mean that B is determined based only on A. B may alternatively be determined based on A and / or other information. In addition, in the embodiment of the present application, "connection" refers to various connection methods such as direct connection or indirect connection for implementing communication between devices. This is not limited in the embodiment of the present application.

[0364] In the embodiments of the present application, unless otherwise specified, "transmission" (transmit / transmit) refers to bidirectional transmission, including a transmitting operation and / or a receiving operation. Specifically, "transmission" in the embodiments of the present application includes data transmission, data reception, or data transmission and data reception. In other words, data transmission herein includes uplink and / or downlink data transmission. Data may include channels and / or signals. An uplink data transmission is an uplink channel transmission and / or an uplink signal transmission, and a downlink data transmission is a downlink channel transmission and / or a downlink signal transmission. In the embodiments of the present application, "network" and "system" represent the same concept, and a communication system is a communication network.

[0365] In the description of this application, " / " represents an "or" relationship between related objects unless otherwise specified. For example, A / B can represent A or B. The term "and / or" in this application represents only the related relationship between related objects and represents that three relationships may exist. For example, A and / or B may represent the following three cases: only A is present, both A and B are present, and only B is present, in which case A and B can be singular or plural. In addition, in the description of this application, "plurality" means two or more than two, unless otherwise specified. At least one of the following (elements) or similar expressions refers to any combination of these, including any combination of singular or plural ones (elements). For example, at least one of a, b, or c (elements) can represent a, b, c, a and b, a and c, b and c, or a, b, and c, in which case a, b, and c can be singular or plural. In addition, in order to clearly describe the technical solutions in the embodiments of the present application, words such as "example" or "for example" are used in the embodiments of the present application to represent giving an example, illustration, or explanation. Any embodiment or design manner described as "example" or "for example" in the embodiments of the present application is not described as being preferred or having more advantages than another embodiment or design manner. Rather, the use of words such as "example" or "for example" is intended to present a relative concept in a specific manner for ease of understanding.

[0366] From the above description of the implementation form, those skilled in the art can understand that for the sake of convenient and concise description, the above-mentioned division of functional modules is regarded as an example for explanation. In practical application, the above-mentioned functions can be allocated to various modules and implemented according to requirements, that is, the internal structure of the device is divided into various functional modules to implement all or part of the above-mentioned functions.

[0367] In some embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the described apparatus embodiments are merely examples. For example, the division into modules or units is merely a logical division of functions, and may be other divisions in actual implementation. For example, multiple units or components may be combined or integrated into another apparatus, and some features may be ignored or not implemented. In addition, the shown or discussed mutual couplings or direct couplings or communication connections may be implemented using some interfaces. Indirect couplings or communication connections between apparatuses or units may be implemented in electronic, mechanical, or other forms.

[0368] The units described as separate parts may or may not be physically separate. The parts shown as units may be one or more physical units, specifically located in one location or distributed across multiple different locations. Some or all of the units may be selected based on actual requirements to achieve the objectives of the solutions of the embodiments.

[0369] In addition, the functional units of the embodiments of the present application may be integrated into one processing unit, each part may exist physically alone, or two or more parts may be integrated into one part. The integrated unit may be implemented in the form of hardware or in the form of a software functional unit.

[0370] When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, the integrated unit may be stored in a readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially implemented in the form of a software product, or the part that contributes to the current technology, or all or part of the technical solutions. The software product includes some instructions stored in a storage medium and instructs a device, for example, the device may be a single-chip microcomputer or chip, or a processor, to perform all or part of the steps of the method of the embodiments of the present application. The aforementioned storage medium includes any medium that can store program code, such as a USB flash drive, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

[0371] The above description is merely a specific implementation form of the present application, and is not intended to limit the protection scope of the present application. Any modification or replacement within the technical scope disclosed in the present application shall be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims. [Explanation of symbols]

[0372] 90 Communication Equipment 100 Communication equipment 110 Communication equipment 120 Communication Equipment 130 terminals 400 Communication equipment 401 Processor 402 Communication lines 403 Communication Interface 404 Memory 405 Output Device 406 Input Devices 407 Processor 901 Transmitter Unit 902 Receiver Unit 1001 Receiver Unit 1002 Transmitter unit 1101 Receiver unit 1102 Transmitter unit 1201 Receiver Unit 1202 Processing Unit 1203 Transmitter Unit

Claims

1. 1. A data transmission method, comprising: receiving, by a mobility management network element, second information from a session management network element, the second information for triggering establishment of a communication connection between a first terminal and a first access network device, the communication connection for transmitting data of a first multicast service; sending, by the mobility management network element, fifth information to the first access network device based on the second information, the fifth information being used by the first access network device to establish a communication connection to the first terminal; the second information includes identification information of a plurality of terminals, the plurality of terminals including the first terminal, the plurality of terminals being members of a multicast group corresponding to the first multicast service, and the data transmission method includes: Searching, by the mobility management network element, for the states of the plurality of terminals, a correspondence between terminal identification information and terminal state by using the identification information of the plurality of terminals as an index; When the states of the terminals are in an idle state, obtaining a paging area by the mobility management network element based on a union of registration areas of the terminals, wherein the first access network device is an access network device corresponding to the paging area. method.

2. the second information includes a Temporary Mobile Group Identification (TMGI) of a multicast group corresponding to the first multicast service; The method of claim 1.

3. the plurality of terminals includes a third terminal, a state of the third terminal is an idle state, and the second information is further for triggering establishment of a communication connection between the third terminal and the first access network device; 3. The method according to claim 1 or 2.

4. the fifth information is further for establishing the communication connection between the third terminal and the first access network device; The method of claim 3.

5. the fifth information includes an identification of the first multicast service; 5. The method according to any one of claims 1 to 4.

6. the identification information of the first multicast service includes a Temporary Mobile Group Identification (TMGI) of a multicast group corresponding to the first multicast service; The method of claim 5.

7. the second information is further for triggering establishment of a communication connection between a second terminal and a second access network device, the second terminal being a member of a multicast group corresponding to the first multicast service, and a state of the second terminal being an idle state; and the method further comprises: and transmitting, by the mobility management network element, sixth information to the second access network device based on the second information, the sixth information being used by the second access network device to establish the communication connection to the second terminal.

7. The method according to any one of claims 1 to 6.

8. receiving, by the mobility management network element, first indication information from the first access network device, the first indication information indicating that establishment of the communication connection between the first terminal and the first access network device has been completed; receiving, by the mobility management network element, a third indication from the second access network device, the third indication indicating that establishment of the communication connection between the second terminal and the second access network device has been completed; and sending, by the mobility management network element, an indication to the session management network element, the indication indicating that establishment of all communication connections has been completed, and the session management network element requests the mobility management network element to trigger establishment of all the communication connections. The method of claim 7.

9. The one instruction information includes identification information of the first terminal and identification information of the second terminal; The method of claim 8.

10. A communication system, the communication system including a mobility management network element and a session management network element, The mobility management network element is configured to perform the method according to any one of claims 1 to 9, the session management network element is configured to transmit the second information; Communication systems.

11. A communications device, the communications device comprising one or more processors and a communications interface, the one or more processors and the communications interface configured to support the communications device in performing a method according to any one of claims 1 to 9.

12. 10. A computer readable storage medium having stored thereon computer instructions which, when executed on a computer, enable the computer to carry out the method of any one of claims 1 to 9.

13. 1. A data transmission method, comprising: transmitting, by a session management network element, second information, the second information for triggering establishment of a communication connection between a first terminal and a first access network device, the communication connection for transmitting data of a first multicast service; receiving, by a mobility management network element, the second information; sending, by the mobility management network element, fifth information to the first access network device based on the second information, the fifth information being used by the first access network device to establish a communication connection to the first terminal; the second information includes identification information of a plurality of terminals, the plurality of terminals including the first terminal, the plurality of terminals being members of a multicast group corresponding to the first multicast service, and the data transmission method includes: Searching, by the mobility management network element, for the states of the plurality of terminals, a correspondence between terminal identification information and terminal state by using the identification information of the plurality of terminals as an index; When the states of the terminals are in an idle state, obtaining a paging area by the mobility management network element based on a union of registration areas of the terminals, wherein the first access network device is an access network device corresponding to the paging area. method.

Citation Information

Patent Citations

  • Paging client nodes in a group communication system

    JP2019512972A

  • Systems and methods to support group communications

    US20200045753A1