WO2021127946A1 - 数据包处理方法和装置 - Google Patents

数据包处理方法和装置 Download PDF

Info

Publication number
WO2021127946A1
WO2021127946A1 PCT/CN2019/127674 CN2019127674W WO2021127946A1 WO 2021127946 A1 WO2021127946 A1 WO 2021127946A1 CN 2019127674 W CN2019127674 W CN 2019127674W WO 2021127946 A1 WO2021127946 A1 WO 2021127946A1
Authority
WO
WIPO (PCT)
Prior art keywords
data packet
address
network element
multicast service
public
Prior art date
Application number
PCT/CN2019/127674
Other languages
English (en)
French (fr)
Inventor
葛翠丽
杨艳梅
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2019/127674 priority Critical patent/WO2021127946A1/zh
Publication of WO2021127946A1 publication Critical patent/WO2021127946A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management

Definitions

  • This application relates to the field of communications, and in particular to a data packet processing method and device.
  • the application function (AF) or application server (AS) can be unicast or multicast through the user plane function (UPF).
  • UPF user plane function
  • Network elements and wireless access network (RAN) network elements send application data to terminal devices.
  • the RAN network element allocates a group of radio network temporary identity (RNTI) to these terminal devices, and sends the quality of service (QoS) of the first terminal device on the radio air interface resources corresponding to the group of RNTI.
  • the data packet in the flow that is, the destination Internet Protocol (IP) address of the data packet is the IP address of the first terminal device.
  • the destination IP address of the received data packet is not The IP address of the terminal device, so the data packet will be discarded, and the application data load in the data packet will not be passed to the upper application layer.
  • the embodiments of the present application provide a data packet processing method and device, which are used to prevent a terminal device from packet loss during transmission optimization.
  • a data packet processing method including: a first network element receives first indication information and a first data packet, the first data packet corresponds to a first multicast service, and the destination Internet Protocol IP of the first data packet The address is the IP address of the first terminal device; the first network element sends a second data packet according to the first indication information and the first data packet, and the destination IP address of the second data packet is the public IP address of the first multicast service, The public IP address is used to transmit the data of the first multicast service to at least two terminal devices; wherein the first indication information is used to indicate that the public IP address of the first multicast service is used to transmit the data of the first multicast service.
  • the first network element receives the first indication information and the first data packet, and the first indication information may be used to instruct the use of a public IP address to transmit the data of the first multicast service, and the first data
  • the packet carries the first multicast service of the first terminal device, and the destination IP address of the first data packet is the IP address of the first terminal device.
  • the first network element sends a second data packet according to the first indication information and the first data packet, and the destination IP address of the second data packet is the public IP address of the first multicast service.
  • the terminal device can determine to accept the second data packet based on its destination IP address being the public IP address, and will not discard the second data packet, which can prevent the terminal device from packet loss during transmission optimization.
  • the method further includes: the first network element receives a third data packet, the third data packet corresponds to the first multicast service, and the destination IP address of the third data packet is the IP of the second terminal device Address, the content carried by the third data packet is the same as the content carried by the first data packet; the first network element discards the third data packet.
  • the first network element discards data packets with the same content as the first data packet to reduce occupied bandwidth.
  • the first network element receiving the first indication information includes: the first network element receives the first indication information from the session management function network element.
  • the first indication information includes the association relationship between the identification information of the first multicast service and the public IP address. According to the identification information of the first multicast service in the first data packet, the first network element can determine to optimize the transmission of the first data packet, and generate a data packet whose destination IP address is the corresponding public IP address.
  • the first indication information includes the identification information of the first multicast service, but does not include the public IP address
  • the method further includes: the first network element receives the public IP address from the session management function network element, or , The first network element obtains the public IP address according to the identification information of the first multicast service.
  • the first network element is a user plane function network element; the first network element sends the second data packet according to the first indication information and the first data packet, including: the first network element according to the first data packet The instruction information and the first data packet are used to send the second data packet to the network element of the access network.
  • the first network element is an access network network element; the first network element sends the second data packet according to the first indication information and the first data packet, including: the first network element according to the first data packet For the indication information and the first data packet, the second data packet is sent in an air interface multicast mode.
  • a data packet processing method including: acquiring identification information of a first multicast service; sending first indication information to a first network element according to the identification information of the first multicast service; wherein, the first The indication information is used to indicate that the public IP address is used to transmit the data of the first multicast service, and the public IP address is used to transmit the data of the first multicast service to at least two terminal devices.
  • the data packet processing method provides a method for how the first network element obtains the first indication information, so that when the first network element optimizes the transmission of the first data packet of the first multicast service, it can be based on the first network element.
  • An instruction message and the first data packet send a second data packet, the destination IP address of the first data packet is the IP address of the first terminal device, and the destination IP address of the second data packet is the public IP address of the first multicast service.
  • the terminal device can determine to accept the second data packet based on its destination IP address being the public IP address, and will not discard the second data packet, which can prevent the terminal device from packet loss during transmission optimization.
  • the method further includes: acquiring first indication information.
  • the method further includes: sending a public IP address to the first network element.
  • the first indication information includes a public IP address.
  • the method further includes: generating a public IP address; or, receiving the public IP address from the application server.
  • acquiring the identification information of the first multicast service includes: generating identification information of the first multicast service, or receiving identification information of the first multicast service from an application server.
  • a data packet processing method including: obtaining the user plane Internet Protocol IP address of the user plane function network element corresponding to the first multicast service and the user plane port number of the user plane function network element; using the user plane IP address and user plane port number, send the first data packet and the second data packet to the user plane function network element, where the first data packet and the second data packet both include the first data of the first multicast service, and the first data packet
  • the destination IP address of the data packet is the IP address of the first terminal device, and the destination IP address of the second data packet is the IP address of the second terminal device.
  • the application server uses The user plane IP address and the user plane port number send at least two data packets of the first multicast service to the UPF network element, and the UPF network element can determine according to the user plane IP address and the user plane port number
  • the at least two data packets correspond to the first multicast service, so that the transmission optimization of the at least two data packets can be performed.
  • a data packet processing method including: a terminal device receives a first data packet, the first data packet corresponds to a first multicast service, and the destination Internet Protocol IP address of the first data packet is the first multicast service
  • the public IP address is used to transmit the data of the first multicast service to at least two terminal devices; the second data packet is obtained according to the first data packet, and the destination IP address of the second data packet is the IP address of the terminal device .
  • the terminal device after the terminal device receives the first data packet, it can determine to accept the first data packet based on its destination IP address being the public IP address, and will not discard the first data packet, which can prevent transmission
  • the terminal device loses packets during optimization.
  • the method further includes: the terminal device receives the public IP address.
  • the method further includes: the terminal device sends a first message to the session management function network element, the first message includes the identification information or the public IP address of the first multicast service, and the first message is used to request The data of the first multicast service.
  • a communication device including: a transceiver module, configured to receive first indication information and a first data packet, the first data packet corresponds to a first multicast service, and the destination Internet Protocol IP address of the first data packet Is the IP address of the first terminal device; the transceiver module is also used to send a second data packet according to the first indication information and the first data packet, and the destination IP address of the second data packet is the public IP address of the first multicast service
  • the public IP address is used to transmit the data of the first multicast service to at least two terminal devices; wherein the first indication information is used to indicate that the public IP address of the first multicast service is used to transmit the data of the first multicast service.
  • it further includes a processing module, a transceiver module, and is further configured to receive a third data packet, the third data packet corresponds to the first multicast service, and the destination IP address of the third data packet is the second terminal device
  • the content carried by the third data packet is the same as the content carried by the first data packet; the processing module is used to discard the third data packet.
  • the transceiver module is specifically configured to receive the first indication information from the session management function network element.
  • the first indication information includes the association relationship between the identification information of the first multicast service and the public IP address.
  • the first indication information includes the identification information of the first multicast service, but does not include the public IP address
  • the communication device further includes a processing module: a transceiver module, which is also used to receive from the session management function network element The public IP address, or the processing module, is used to obtain the public IP address according to the identification information of the first multicast service.
  • the communication device is a UPF; the transceiver module is specifically configured to: send the second data packet to the access network element according to the first indication information and the first data packet.
  • the communication device is an access network element; the transceiver module is specifically configured to: according to the first indication information and the first data packet, send the second data packet in an air interface multicast manner.
  • a communication device including: a processing module, configured to obtain identification information of a first multicast service; and a transceiver module, configured to send the first multicast service identification information to a first network element according to the identification information of the first multicast service.
  • An indication information where the first indication information is used to indicate the use of a public IP address to transmit the data of the first multicast service, and the public IP address is used to transmit the data of the first multicast service to at least two terminal devices.
  • the processing module is further configured to: obtain the first indication information.
  • the transceiver module is further configured to: send a public IP address to the first network element.
  • the first indication information includes a public IP address.
  • the processing module is also used to generate a public IP address; or the transceiver module is also used to receive a public IP address from the application server.
  • the processing module is further configured to generate identification information of the first multicast service, or the transceiver module is further configured to receive identification information of the first multicast service from the application server.
  • a communication device including: a processing module configured to obtain a user plane Internet Protocol IP address of a user plane function network element corresponding to a first multicast service and a user plane port number of the user plane function network element;
  • the transceiver module is configured to use the user plane IP address and the user plane port number to send the first data packet and the second data packet to the user plane function network element, wherein the first data packet and the second data packet both include the first multicast
  • the destination IP address of the first data packet is the IP address of the first terminal device
  • the destination IP address of the second data packet is the IP address of the second terminal device.
  • a communication device including: a transceiver module, configured to receive a first data packet, the first data packet corresponds to a first multicast service, and the destination Internet Protocol IP address of the first data packet is the first multicast
  • the public IP address of the service, the public IP address is used to transmit the data of the first multicast service to at least two terminal devices; the processing module is used to obtain the second data packet according to the first data packet, and the destination IP address of the second data packet Is the IP address of the terminal device.
  • the transceiver module is also used to receive a public IP address.
  • the transceiver module is further configured to send a first message to the session management function network element, the first message includes the identification information or the public IP address of the first multicast service, and the first message is used to request the first multicast service. Data of a multicast service.
  • a communication device in a ninth aspect, includes a processor, a memory, and a transceiver.
  • the processor is coupled to the memory.
  • the processor executes a computer program or instruction in the memory, The method described in one aspect and any of its embodiments, or, the method described in the second aspect and any of its embodiments, or, the method described in the third aspect and any of its embodiments, or, as The method according to the fourth aspect and any one of its embodiments.
  • a chip including a processor and an interface, used to call and run a computer program stored in the memory from a memory, and execute the method as described in the first aspect and any one of its implementation manners, Or, the method as described in the second aspect and any of its embodiments, or, the method as described in the third aspect and any of its embodiments, or, the method as described in the fourth aspect and any of its embodiments .
  • a computer-readable storage medium stores instructions.
  • the computer or the processor executes the operations as described in the first aspect and The method according to any one of its embodiments, or the method according to the second aspect and any one of its embodiments, or the method according to the third aspect and any one of its embodiments, or, as the fourth aspect And the method described in any of the embodiments.
  • a computer program product containing instructions is provided.
  • the computer or the processor executes the method described in the first aspect and any one of its implementations, Or, the method as described in the second aspect and any of its embodiments, or, the method as described in the third aspect and any of its embodiments, or, the method as described in the fourth aspect and any of its embodiments .
  • FIG. 1 is a schematic diagram of the architecture of a communication system provided by an embodiment of this application.
  • FIG. 2 is a schematic structural diagram of a terminal device provided by an embodiment of this application.
  • FIG. 3 is a schematic structural diagram of a base station provided by an embodiment of this application.
  • FIG. 4 is a schematic structural diagram of a network device provided by an embodiment of this application.
  • FIG. 5 is a schematic diagram of a QoS flow provided by an embodiment of this application.
  • FIG. 6 is a schematic diagram of application layer unicast and network layer unicast according to an embodiment of the application
  • FIG. 7 is a schematic diagram of application layer multicast and network layer unicast provided by an embodiment of the application.
  • FIG. 8 is a schematic diagram of an application layer multicast network layer broadcast provided by an embodiment of the application.
  • FIG. 9 is a schematic diagram of another application layer multicast network layer broadcast provided by an embodiment of the application.
  • FIG. 10 is a schematic diagram of multicast transmission between an application server and a UPF network element according to an embodiment of this application;
  • FIG. 11 is a schematic diagram of transmission optimization of a UFP network element according to an embodiment of the application.
  • FIG. 12 is a schematic diagram of transmission optimization of a RAN network element provided by an embodiment of this application.
  • FIG. 13 is a schematic diagram of both UPF network element and RAN network element performing transmission optimization according to an embodiment of this application;
  • FIG. 14 is a first schematic flowchart of a data packet processing method provided by an embodiment of this application.
  • FIG. 15 is a second schematic flowchart of a data packet processing method provided by an embodiment of this application.
  • FIG. 16 is a third schematic flowchart of a data packet processing method provided by an embodiment of this application.
  • FIG. 17 is a fourth schematic flowchart of a data packet processing method provided by an embodiment of this application.
  • FIG. 18 is a schematic diagram of a protocol stack provided by an embodiment of this application.
  • FIG. 19 is a fifth schematic flowchart of a data packet processing method provided by an embodiment of this application.
  • FIG. 20 is a sixth flowchart of a data packet processing method provided by an embodiment of this application.
  • FIG. 21 is a seventh flowchart of a data packet processing method provided by an embodiment of this application.
  • FIG. 22 is an eighth flowchart of a data packet processing method provided by an embodiment of this application.
  • FIG. 23 is a ninth flowchart of a data packet processing method provided by an embodiment of this application.
  • FIG. 24 is a tenth schematic flowchart of a data packet processing method provided by an embodiment of this application.
  • 25 is a schematic eleventh flowchart of a data packet processing method provided by an embodiment of this application.
  • FIG. 26 is a twelfth flowchart of a data packet processing method provided by an embodiment of this application.
  • FIG. 27 is a thirteenth schematic flowchart of a data packet processing method provided by an embodiment of this application.
  • FIG. 28 is a schematic diagram of generating a second data packet in a UPF network element according to an embodiment of this application.
  • FIG. 29 is a fourteenth flowchart of a data packet processing method provided by an embodiment of this application.
  • FIG. 30 is a schematic diagram 1 of generating a second data packet in a RAN network element according to an embodiment of the application
  • FIG. 31 is a fifteenth schematic flowchart of a data packet processing method provided by an embodiment of this application.
  • FIG. 32 is a second schematic diagram of generating a second data packet in a RAN network element according to an embodiment of this application.
  • FIG. 33 is a schematic structural diagram of a communication device provided by an embodiment of this application.
  • FIG. 34 is a schematic structural diagram of another communication device provided by an embodiment of this application.
  • FIG. 35 is a schematic structural diagram of another communication device provided by an embodiment of this application.
  • FIG. 36 is a schematic structural diagram of still another communication device provided by an embodiment of this application.
  • TDD time division duplexing
  • FDD frequency division duplexing
  • the embodiments of this application rely on the 5G network scenario in the wireless communication network. It should be pointed out that the solutions in the embodiments of this application can also be applied to other wireless communication networks, and the corresponding names can also be used in other wireless communication networks. Replace the name of the corresponding function.
  • Figure 1 provides a communication system architecture, including: terminal equipment 101, radio access network ((radio) access network, (R) AN) network element 102, user plane function (UPF) network element 103, Data network (DN) 104, access and mobility management function (AMF) network element 105, session management function (session management function, SMF) network element 106, policy control network element (policy) A control function (PCF) network element 107, a unified data management (UDM) network element 108, and an application function (AF) network element 109.
  • radio access network (radio) access network, (R) AN) network element 102
  • UPF user plane function
  • DN Data network
  • AMF access and mobility management function
  • SMF session management function
  • policy control network element policy control network element
  • PCF policy control network element
  • UDM unified data management
  • AF application function
  • the name of the interface between the various network elements in Figure 1 is only an example, and the name of the interface in the specific implementation may be other names, which are not limited.
  • the interface between the terminal device 101 and the AMF network element 105 may be an N1 interface
  • the interface between the RAN network element 102 and the AMF network element 105 may be an N2 interface
  • the interface between the RAN network element 102 and the UPF network element 103 It can be an N3 interface
  • the interface between UPF network element 103 and SMF network element 106 can be an N4 interface
  • the interface between PCF network element 107 and AF network element 109 can be an N5 interface
  • the interface can be N6 interface
  • the interface between SMF network element 106 and PCF network element 107 can be N7 interface
  • the interface between AMF network element 105 and UDM network element 108 can be N8 interface
  • the interface between element 103 can be N9 interface
  • the terminal device 101 may include various handheld devices, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to wireless modems with wireless communication functions; it may also include subscriber units and cellular phones. , Smart phone (smart phone), wireless data card, personal digital assistant (personal digital assistant, PDA) computer, tablet computer, wireless modem (modem), handheld device (handheld), laptop computer (laptop computer), cordless Cordless phone or wireless local loop (WLL) station, machine type communication (MTC) terminal, user equipment (UE), mobile station (mobile station, MS), terminal Device (terminal device) or relay user equipment, etc.
  • the relay user equipment may be a 5G residential gateway (RG).
  • RG 5G residential gateway
  • the terminal device 200 may include: a memory 120 and a processor 180. Further, the terminal device 200 may also include components such as a radio frequency (RF) circuit 100, other input devices 130, a display screen 140, a sensor 150, an audio circuit 160, an I/O subsystem 170, and a power supply 190.
  • RF radio frequency
  • the structure of the mobile phone shown in the figure does not constitute a limitation on the mobile phone, and may include more or less components than those shown in the figure, or combine certain components, or split certain components, or Different component arrangements.
  • the display screen 140 belongs to a user interface (UI), and the display screen 140 may include a display panel 141 and a touch panel 142.
  • the mobile phone may also include functional modules or devices such as a camera and a Bluetooth module, which will not be repeated here.
  • the processor 180 is connected to the RF circuit 100, the memory 120, the audio circuit 160, the I/O subsystem 170, and the power supply 190, respectively.
  • the I/O subsystem 170 is respectively connected with other input devices 130, the display screen 140, and the sensor 150.
  • the RF circuit 100 can be used to receive and send signals in the process of sending and receiving information or talking. In particular, after receiving downlink information from a network device, it is sent to the processor 180 for processing.
  • the memory 120 may be used to store software programs and modules.
  • the processor 180 executes various functional applications and data processing of the mobile phone by running the software programs and modules stored in the memory 120, for example, executes the methods and functions of the terminal device in the embodiments of the present application.
  • the other input device 130 can be used to receive input digital or character information, and generate keyboard signal input related to the user settings and function control of the mobile phone.
  • the display screen 140 can be used to display information input by the user or information provided to the user and various menus of the mobile phone, and can also accept user input.
  • the sensor 150 may be a light sensor, a motion sensor, or other sensors.
  • the audio circuit 160 may provide an audio interface between the user and the mobile phone.
  • the I/O subsystem 170 is used to control input and output external devices, and the external devices may include other device input controllers, sensor controllers, and display controllers.
  • the processor 180 is the control center of the terminal device 200, which uses various interfaces and lines to connect the various parts of the entire mobile phone, runs or executes software programs and/or modules stored in the memory 120, and calls data stored in the memory 120 , Perform various functions of the mobile phone and process data, so as to monitor the mobile phone as a whole.
  • the power source 190 (such as a battery) is used to supply power to the above-mentioned components.
  • the power source may be logically connected to the processor 180 through a power management system, so that functions such as charging, discharging, and power consumption can be managed through the power management system.
  • the terminal device 101 may receive a signal from the RAN network element 102 or send a signal to the RAN network element 102 through the RF circuit 100.
  • the RAN network element 102 is used to provide wireless access services to the terminal device 101.
  • the RAN network element 102 includes, but is not limited to, eNodeB, wireless fidelity (Wi-Fi) access point (AP), worldwide interoperability for microwave access (WiMAX) base station, new air interface ( new radio, NR) etc.
  • the RAN network element 102 may include a single RAN network element or a dual RAN network element.
  • dual RAN network elements include a primary radio access network (master radio access network, M-RAN) network element and a secondary radio access network (secondary radio access network, S-RAN) network element.
  • a single RAN network element or a dual RAN network element can transmit packets with the UPF network element through a dual tunnel.
  • the base station 300 may include an indoor baseband processing unit (building baseband unit, BBU) 301 and a remote radio unit (RRU) 302.
  • the RRU 302 is connected to an antenna feeder system (that is, an antenna) 337, and the BBU 301 and RRU 302 can be disassembled and used as needed.
  • the BBU 301 may include a processor 331, a memory 332, and a bus system 333.
  • the processor 331 and the memory 332 of the BBU 301 are connected to each other through the bus system 333.
  • the above-mentioned bus system may be a standard bus for interconnecting peripheral components or an extended industrial standard structure bus.
  • the bus can be divided into an address bus, a data bus, a control bus, and so on.
  • the figure is represented by only one line, but it does not mean that there is only one bus or one type of bus.
  • the RRU 302 may include an RF circuit 334, and the base station 300 may also include an optical fiber 335 and a coaxial cable 336.
  • the RF circuit 334 in the RRU 302 and the BBU 301 are connected to each other through an optical fiber 335, and the RF circuit 334 and the antenna 337 in the RRU 302 are connected to each other through a coaxial cable 336.
  • Base stations may include various forms of base stations, such as macro base stations, micro base stations (also called small stations), relay stations, and access points.
  • the RAN network element 102 described in the embodiment of the present application is used to transmit data between the terminal device 101 and the core network device.
  • the UPF network element 103 is used to process user messages, such as forwarding and charging.
  • the DN 104 is used to provide users with data transmission services, such as DNs that provide IP multimedia services (IP multi-media service, IMS), and DNs that provide Internet (Internet) services.
  • IP multimedia services IP multi-media service, IMS
  • IMS IP multi-media service
  • Internet Internet
  • the AMF network element 105 is used for mobility management in the mobile network, such as user location update, user registration network, user handover, and so on.
  • the SMF network element 106 is used for session management in the mobile network, such as session establishment, modification, and release. For example, assign IP addresses to users, select UPF network elements that provide message forwarding functions, and so on.
  • the PCF network element 107 is used to provide policies, such as QoS policies, slice selection policies, etc., to the terminal device 101, the RAN network element 102, the UPF network element 103, and the SMF network element 106.
  • policies such as QoS policies, slice selection policies, etc.
  • the UDM network element 108 is used to store user data, such as subscription information and authentication/authorization information.
  • the AF network element 109 provides services to a 3rd generation partnership project (3rd generation partnership project, 3GPP) network, and interacts with the PCF network element 107 for policy control and so on.
  • 3rd generation partnership project 3rd generation partnership project, 3GPP
  • the terminal device 101 can access by establishing a protocol data unit (PDU) session between the terminal device 101, the RAN network element 102, and the UPF network element 103 to the DN 104 DN 104.
  • PDU protocol data unit
  • the UPF network element 103, the AMF network element 105, the SMF network element 106, the PCF network element 107, and the UDM network element 108 may be collectively referred to as core network elements.
  • the following takes a network device as an example to illustrate the structure of these core network elements.
  • the embodiment of this application does not limit that each core network element must have a unit or device as shown in FIG. 4, and may have more or Fewer units or devices.
  • the network device 400 may include at least one processor 401, a communication line 402, a memory 403, and at least one communication interface 404.
  • the processor 401 may be a general-purpose central processing unit (central processing unit, CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of this application.
  • the communication line 402 may include a path to transmit information between the aforementioned components.
  • the communication interface 404 can use any device such as a transceiver to communicate with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN) Wait.
  • RAN radio access network
  • WLAN wireless local area networks
  • the memory 403 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM), or other types that can store information and instructions
  • the dynamic storage device can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disk storage, optical disc storage (Including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program codes in the form of instructions or data structures and can be used by a computer Any other media accessed, but not limited to this.
  • the memory 403 may exist independently and is connected to the processor through a communication line 402.
  • the memory 403 may also be integrated with the processor 401. Among them, the memory 403 is used to store computer-executable instructions (which may be referred to as application code) for executing the solution of the present application.
  • the processor 401 is configured to execute computer-executable instructions stored in the memory 403, so as to implement the actions of each core network element in the method provided in the following embodiments of the present application.
  • Application is an abbreviation for application or application software, and is a program that implements tasks with specific functions.
  • the application program running on the terminal device can be called an application client.
  • the application client obtains services from the application server through the network and completes the interactive tasks with the user.
  • An application running on a network device of an application service provider (ASP) can be called an application server (or server application).
  • the application server provides business logic to the application client through various protocols.
  • An application can provide one or more services.
  • the multicast application can provide a multicast service, and the multicast service may include different contents, channels, services, etc., which is not limited by this application.
  • a live video app running on a terminal device can provide different live content, such as live sports events, live entertainment programs, live shopping, etc., and users can watch them through the APP.
  • the application server involved in the embodiment of the present application can not only perform the functions of the control plane of the AF network element 109, but also perform the functions of the user plane, such as providing the first multicast service involved in the present application.
  • an application can be identified by a triplet or application identifier, and the triplet or application identifier serves as an application descriptor.
  • the triplet includes a transmission protocol (for example, transmission control protocol (TCP), user datagram protocol (UDP)), server-side IP address and its port number.
  • TCP transmission control protocol
  • UDP user datagram protocol
  • the IP data stream corresponding to an application can be identified by a five-tuple, which includes the transmission protocol, the source IP address and its port number, and the destination IP address and its port number.
  • a business can be identified by the identification information of the business.
  • the identification information of the service may be any of the following: application identification, triplet, service identifier, and the user plane IP address of the UPF network element and the user plane port number of the UPF network element.
  • a service can be identified by a service identifier.
  • the service identifier includes, for example, a service ID, a service ID (serviceID), and a (temporary) group ID.
  • serviceID service ID
  • temporary temporary group ID
  • an application provides only one service, it is also possible to identify a service through the triplet of the application or the application identifier.
  • one service can be identified by triples or application identifiers combined with public IP addresses.
  • a service can be identified by the user plane IP address of the UPF network element and the user plane port number of the UPF network element.
  • the public IP address is an IP unicast address or IP multicast address, which is used to transmit service data to a group of terminal devices.
  • the public IP address may be generated by the application server, or generated by the SMF network element or the UPF network element.
  • the application server can use the unicast IP address of the terminal device to encapsulate a service data packet and send the data packet to the terminal device.
  • the destination IP address of the data packet is determined by the terminal device’s destination IP address.
  • the unicast IP address is replaced with a public IP address, and then it continues to be sent to the terminal device.
  • the terminal device determines that it is the recipient of the data packet according to the public IP address, does not discard the data packet, and delivers the data packet to the upper application client according to the port number of the data packet.
  • the application server and the application client on the terminal device can also negotiate in advance to establish two socket connections, one of which is bound to the public IP address; or the application server and the application client on the terminal device One socket connection between the two IP connections corresponds to two IP connections, and the terminal device side IP address of one of the IP connections corresponds to the public IP address.
  • the user plane IP address of the UPF network element and the user plane port number of the UPF network element it is mainly used to identify a service between the application server and the UPF network element.
  • the user plane IP address and the user plane port number may be generated by the SMF network element and sent to the UPF network element, or the SMF network element may request it from the UPF network element.
  • the application server can obtain the service identifier of the service and the corresponding user-plane IP address and user-plane port number from the SMF network element, thereby combining the service identifier of the service with the user-plane IP address of the UPF network element and the user-plane port of the UPF network element Numbers correspond to each other.
  • the application server can use the user plane IP address of the UPF network element and the user plane port number of the UPF network element to encapsulate the data packet corresponding to the terminal device of the service, and send the data packet corresponding to the terminal device of the service to the UPF network element ( That is, IP in IP or IP tunnel mode), the UPF network element determines the corresponding service according to the user plane IP address and the user plane port number.
  • the data packet corresponding to the terminal device of the service refers to the data packet sent to the terminal device by the application server of the service.
  • QoS flow is the finest granularity of QoS differentiation in a PDU session.
  • a QoS flow is established for terminal devices through a PDU session establishment process or a PDU session modification process.
  • QFI QoS flow ID
  • QFI may be dynamically allocated by SMF network elements, or may be a preset 5G QoS identifier (5G QoS identifier, 5QI).
  • user plane data flows may be referred to as data flows
  • the QFI are applicable to the same QoS flow mapping rules (for example, scheduling rules, access thresholds, etc.).
  • the QFI may be carried in the header of a GPRS tunnelling protocol user plane (GPRS tunnelling protocol user plane, GTP-U) message on the N3 interface and the N9 interface.
  • GPRS tunnelling protocol user plane GPRS tunnelling protocol user plane
  • Terminal equipment, RAN network elements, and UPF network elements can obtain QoS flow mapping rules in the following ways:
  • the SMF network element can send one or more QoS flow mapping rules to the terminal equipment through the AMF network element and the N1 interface.
  • it can also send the QoS parameters associated with the QoS flow mapping rule to the terminal equipment.
  • the terminal device derives the QoS flow mapping rule by applying reflected QoS control.
  • the terminal device may receive a QoS flow from the RAN network element on the corresponding radio air interface resource according to the QoS flow mapping rule, or send a QoS flow to the RAN network element.
  • the SMF network element can send a QoS profile (QoS profile) to the RAN network element through the AMF network element and the N2 interface; or, the QoS profile is pre-configured in the RAN network element.
  • the QoS configuration file includes QoS flow mapping rules.
  • the RAN network element can receive a QoS flow from the terminal device on the corresponding radio air interface resource according to the QoS flow mapping rule, or send a QoS flow to the terminal device.
  • the RAN network element may receive the QoS flow from the UPF network element according to the above-mentioned QoS flow mapping rule, or send the QoS flow to the UPF network element.
  • the SMF network element can configure one or more upstream and downstream packet detection rules (PDR) to the UPF network element through the N4 interface.
  • the PDR is the QoS flow mapping rule.
  • the UPF network element can receive a QoS flow from the RAN network element according to the above-mentioned QoS flow mapping rule, or send a QoS flow to the RAN network element.
  • the transmission mode of the first multicast service at the application layer and the network layer is the transmission mode of the first multicast service at the application layer and the network layer:
  • the transmission mode of the application layer refers to the way the application server encapsulates and sends application data packets.
  • the application server can use unicast to send application service data to the application client corresponding to the application service, that is, the application server uses the IP address of the application client (unicast IP address) to encapsulate the application service data, and sends the application service data to the application client
  • the application service data received by different application clients corresponding to the same application service may be the same or different.
  • the application server can also use multicast to send application service data to the application client corresponding to the application service, that is, the application server uses the multicast address to encapsulate the application service data, and sends the application service data through the IP multicast technology, and the application corresponding to the application service Both clients can receive the same application business data.
  • the transmission method of the network layer refers to the method of transmitting application service data within the mobile communication network.
  • the unicast QoS flow and air interface unicast channel of the mobile communication network can be used to send application service data to the terminal device where the application client of the application service is located, that is, the terminal where the application client corresponding to the application service is located.
  • the device establishes a unicast QoS flow with the UPF network element, and the UPF network element sends application service data to the unicast QoS flow that passes through the terminal device alone.
  • Each application client corresponding to the application service receives the application service through the terminal device where it is located. Data, the received application service data can be the same or different.
  • the multicast QoS stream and air interface multicast channel of the mobile communication network can also be used to send application service data to the terminal device where the application client of the application service is located, that is, the application service corresponding to the application service under the same base station
  • the terminal device where the application client is located establishes an air interface multicast group with the base station.
  • the base station and the UPF network element use a multicast QoS stream (for example, it can be a public N3 QoS stream; or it can be a certain application under the base station.
  • the terminal device where the application client corresponding to the service is located receives the unicast QoS flow of the application service.
  • QoS flow that is, the UPF network element sends application service data to a base station through a QoS flow.
  • the base station uses the group RNTI to send the application service data to the terminal device where the application client corresponding to the application service under the base station is located, and the application service corresponds to All application clients can receive the same application business data.
  • Method 1 Application layer unicast, network layer unicast
  • the application server sends application service data to the application client through the application layer unicast mode
  • the mobile communication network sends the application service data to the terminal device through the network layer unicast mode.
  • the destination IP address of the first data packet sent by the application server to the terminal device (such as terminal device 1) where the application client of the application service is located is the terminal device (such as terminal device 1).
  • IP address for example, IP1
  • the application server sends the first data packet to the UPF network element through unicast
  • the UPF network element sends the first data packet to the RAN network element through the unicast QoS flow
  • the RAN network element passes The unicast channel of the air interface sends the first data packet to the terminal device (for example, the terminal device 1).
  • Method 2 Application layer multicast, network layer unicast
  • the application server sends application service data to the application client through the application layer multicast mode
  • the mobile communication network sends the application service data to the terminal device through the network layer unicast mode.
  • the application server and the terminal device have agreed in advance to use the first multicast IP address (for example, IPm) to transmit data, and the UPF network element has joined the multicast group identified by the first multicast IP address.
  • the multicast group is the multicast group of the first multicast service.
  • the destination IP address of the first data packet sent by the application server to the terminal device is the first multicast IP address (for example, IPm).
  • the UPF network element copies multiple copies of the received application service data, and sends the first data packet to the RAN network element through the unicast QoS flow, and the RAN network element sends the first data packet to the RAN network element through the unicast channel of the air interface.
  • the terminal device (for example, terminal device 1) where the application client of the application service is located.
  • Method 3 Application layer multicast, network layer multicast
  • the application server sends application service data to the application client through the application layer multicast method
  • the mobile communication network sends the application service data to the terminal device through the network layer multicast method.
  • the application server and multiple terminal devices have agreed in advance to use the first multicast IP address (for example, IPm) to transmit data, and the UPF network element has been added to the first multicast IP address.
  • the destination IP address of the first data packet sent by the application server to these terminal devices is the first multicast IP address (for example, IPm).
  • the UPF network element sends the first data packet to the RAN network element through the public multicast tunnel with the RAN network element, and the RAN network element sends the first data packet through the multicast channel of the air interface, and configures multiple terminals of the multicast channel All devices can receive the first data packet.
  • the application server and each terminal device have agreed in advance to use the first multicast IP address (for example, IPm) to transmit data, and the UPF network element has been added to the first multicast IP address.
  • the destination IP address of the first data packet sent by the application server to each terminal device is the first multicast IP address (for example, IPm).
  • the UPF network element encapsulates the first data packet in the first multicast data packet and sends the first multicast data packet to the RAN network element through a QoS flow, where the destination IP address of the first multicast data packet is the second A multicast IP address (for example, IPn), and the second multicast IP address is a multicast IP address that multiple RAN network elements have joined.
  • the RAN network element After receiving the first multicast data packet, the RAN network element removes the header of the multicast packet to obtain the first data packet, and sends the first data packet through the multicast channel of the air interface. All terminal devices configured with the multicast channel can receive the first data packet. One packet.
  • the application server may encapsulate the first data packet in the second multicast data packet.
  • the second multicast data packet is sent to the UPF network element through the N6 tunnel.
  • the destination IP address of the second multicast data packet is the third multicast IP address (for example, IPo), where multiple UPF network elements have joined the multicast group identified by the third multicast IP address, and the multicast group is The multicast group of the first multicast service.
  • the UPF network element After receiving the second multicast data packet, the UPF network element removes the multicast packet header to obtain the first data packet, and then sends the first data packet to the RAN network element in the manner in the manner 2 or the manner 3.
  • method 1 application layer unicast and network layer unicast, if the network device transmits the same application service data to multiple terminal devices (for example, multiple terminal devices watch live sports events through the video playback APP), in order to avoid wasting network resources
  • data packet transmission optimization or transmission merging
  • UPF network elements and/or RAN network elements can be performed on UPF network elements and/or RAN network elements to save network resources or radio air interface resources, that is, the following method 4 can be adopted.
  • Method 4 Application layer unicast, network layer multicast
  • the application server sends application service data to the application client through the application layer unicast mode
  • the mobile communication network sends the application service data to the terminal device through the network layer multicast mode.
  • the destination IP address of the first data packet sent by the application server to the terminal device (such as terminal device 1) where the application client of the application service is located is the IP address (such as terminal device 1) of the terminal device (such as terminal device 1). IP1)
  • the application server sends the first data packets of multiple terminal devices to the UPF network element.
  • the UPF network element selects the first data packet of one of the terminal devices and sends it to the multiple terminal devices through network layer multicast, and discards or does not process the first data packets of other terminal devices that are not selected. .
  • UFP network elements are optimized for transmission:
  • the UPF network element performs transmission optimization, which means that when the data packets to be transmitted to multiple terminal devices carry the same content, the UPF network element can send the terminal device to the RAN network element through the QoS flow corresponding to one of the multiple terminal devices The data packets of other terminal devices are not processed or discarded. Then, the RAN network element sends the data packets of the terminal device to the above-mentioned multiple terminal devices.
  • the SMF network element can configure detection rules for the UPF network element, and the UPF network element can determine the content carried by the data packet sent to the terminal device 1, the terminal device 2, and the terminal device 3 according to the detection rule.
  • the source IP address of the data packet sent to the terminal device 1 from the video playback APP, the data packet sent to the terminal device 2, and the data packet sent to the terminal device 3 are all 123.123.123.123 and the port number is 123.
  • the video playback APP is a multicast service application, and the UPF network element can determine that the contents carried in these data packets are the same (for example, they are all live sports events).
  • the UPF network element can optimize the transmission of the data packets of these three terminal devices, that is, only select the data packet of one of the terminal devices for transmission. For example, the data packet of the terminal device 1 can be selected for transmission, and the data packet of the terminal device 1 can be transmitted to the RAN through QoS flow 1.
  • the network element sends the data packet of the terminal device 1.
  • the QoS flow 1 may be the QoS flow of the service received by the terminal device 1, or may be a public QoS flow corresponding to the service between the RAN network element and the UPF network element.
  • the RAN network element may determine to send the data packet in the QoS flow 1 to the terminal device 1, the terminal device 2, and the terminal device 3 according to the association relationship between the service configured by the SMF network element and the terminal device. Specifically, the RAN network element schedules the data packets received from the QoS flow 1 for the terminal device 1, the terminal device 2, and the terminal device 3 on the radio air interface resources corresponding to a group of RNTI. In this way, terminal device 1, terminal device 2, and terminal device 3 can receive the same data packet on the air interface.
  • the group RNTI involved in the embodiment of the present application is an RNTI that is pre-configured to multiple terminal devices (such as terminal device 1, terminal device 2, and terminal device 3) in advance (for example, in the session establishment phase).
  • the group RNTI may also be called multiple RNTI shared by terminal devices (for example, terminal device 1, terminal device 2, and terminal device 3).
  • RAN network element performs transmission optimization:
  • the RAN network element performs transmission optimization, which means that the RAN network element can configure a group of RNTI for at least two terminal devices, and the RAN network element sends data of one of the terminals to the at least two terminal devices on the radio air interface resources corresponding to the group of RNTIs. Or from data on the public N3 tunnel.
  • the SMF network element can configure detection rules for the UPF network element, and the UPF network element can determine the content carried by the data packet sent to the terminal device 1, the terminal device 2, and the terminal device 3 according to the detection rule.
  • terminal device 1 corresponds to QoS flow 1
  • terminal device 2 corresponds to QoS flow 2
  • terminal device 3 corresponds to QoS flow 3.
  • the UPF network element can mark the data packets carried in QoS flow 1, QoS flow 2, and QoS flow 3 with the same Label (for example, index or content ID), but the UPF network element still uses the QoS flow corresponding to each terminal device to send the data packet of each terminal device to the RAN network element, that is, the UPF network element passes QoS Flow 1 sends the data packet of terminal device 1, sends the data packet of terminal device 2 through QoS flow 2, and sends the data packet of terminal device 3 through QoS flow 3.
  • QoS Flow 1 sends the data packet of terminal device 1
  • the RAN network element can determine that the data packets on QoS flow 1, QoS flow 2 and QoS flow 3 are the same according to the label of the received data packet, and the RAN network element can configure a group of RNTI to terminal device 1, terminal device 2, and terminal Device 3, and send the data packet received from QoS flow 1 on the wireless air interface resource corresponding to the group of RNTI, so that terminal device 1, terminal device 2 and terminal device 3 can use the wireless air interface resource corresponding to this group of RNTI The same data packet is received at the same time.
  • Both UPF network elements and RAN network elements perform transmission optimization, which means that both UPF network element transmission optimization and RAN network element transmission optimization must be performed.
  • the multiple terminal devices served by the RAN network element correspond to different UPF network elements.
  • the content carried by the data packets sent by the application server to the terminal device 1, the terminal device 2, and the terminal device 3 are the same.
  • the terminal device 1 and the terminal device 2 correspond to the UPF network element 1
  • the terminal device 3 corresponds to UPF network element 2.
  • the UPF network element 1 can optimize the transmission of the data packets sent to the terminal device 1 and the terminal device 2, and send the data packet corresponding to the terminal device 1 to the RAN network element through the QoS flow 1.
  • the UPF network element 2 sends the data packet corresponding to the terminal device 3 to the RAN network element through the QoS flow 3.
  • the RAN network element can optimize the transmission of QoS flow 1 and QoS flow 3.
  • the RAN network element can configure a group of RNTI to terminal equipment 1, terminal equipment 2 and terminal equipment 3.
  • the RAN network element recognizes QoS flow 1 and QoS flow 3.
  • the RAN network element determines to transmit the data packet in QoS flow 1 on the radio air interface resource, and the RAN network element sends the data packet in QoS flow 1 on the radio air interface resource corresponding to the group of RNTI, so , Terminal device 1, terminal device 2, and terminal device 3 can receive the same data packet on the air interface at the same time.
  • the RAN network element sends the data packet in QoS flow 1 to the terminal device 1, the terminal device 2 and the terminal device 3 on the radio air interface resources corresponding to the group RNTI, and the destination IP address of the data packet is the terminal
  • the IP address of the device 1 makes the terminal device 2 and the terminal device 3 receive the data packet, but because the destination IP address is not the IP address of the terminal device, the received data packet will be discarded.
  • the first network element when the first network element (for example, a UPF network element or a RAN network element) performs transmission optimization, the first network element performs transmission optimization according to the first indication information and the first multicast service.
  • the data packet generates a second data packet.
  • the first indication information is used to indicate that the public IP address of the first multicast service is used to transmit the data of the first multicast service
  • the destination IP address of the first data packet is the IP address of the first terminal device
  • the destination IP address of the second data packet is The destination IP address is a public IP address.
  • the first network element can modify the destination IP address of the multicast service data packet sent to the first terminal device to a public IP address, so as to implement multiple terminal devices (which may include the first terminal device) It can receive the data packets of the multicast service of the first terminal device at the same time. After the multiple terminal devices receive the data packets of the multicast service of the first terminal device, they can accept the public IP address according to their destination IP address. It is not that the data packet of the multicast service of the first terminal device is discarded.
  • an embodiment of the present application provides a data packet processing method, and the method includes:
  • the first network element receives first indication information and a first data packet.
  • the first network element may be a UPF network element or a RAN network element, which is not limited.
  • the first data packet corresponds to the first multicast service, and the destination IP address of the first data packet is the IP address of the first terminal device.
  • the first data packet may be used to transmit data of the first multicast service to the first terminal device, or in other words, the first data packet may be used to carry the first multicast service of the first terminal device.
  • the first data packet is used to transmit video stream data and audio stream data of the live sports event to the first terminal device.
  • the first terminal device may be any terminal device, and is not limited to a special terminal device.
  • the terminal device receiving the first multicast service includes terminal device 1 (IP address is IP1), terminal device 2 (IP address is IP2), ..., terminal device n (IP address is IPn), then the first terminal The device may be one of terminal device 1 to terminal device n.
  • the IP address of the first terminal device is the IP address IP1 of the terminal device 1.
  • the first network element may also receive data packets of the first multicast service of other terminal devices, and the content carried by the data packets of the first multicast service of these other terminal devices is the same as the content carried by the first data packet. , That is, the data of the first multicast service carried is the same.
  • the first indication information may be used to indicate that the public IP address of the first multicast service is used to transmit the data of the first multicast service.
  • the first multicast service may be a multicast service or a broadcast service.
  • the first indication information includes identification information of the first multicast service, but does not include the public IP address.
  • the first network element may pre-configure the public IP address, or the first network element may receive the public IP address from the SMF network element, or the first network element may be based on the identification information of the first multicast service Obtain the public IP address, or if the first network element is a UPF network element, the first network element may generate the public IP address according to the identification information of the first multicast service, and save it locally.
  • the first indication information includes identification information of a QoS flow carrying the first multicast service, or includes identification information of the first terminal device.
  • the identification information of the QoS flow is used to identify a QoS flow, and may be a QoS flow identifier (QoS flow identifier, QFI) or 5QI.
  • the identification information of the first terminal is used to identify the first terminal device, and may be a subscription permanent identifier (SUPI), a generic public subscription identifier (GPSI), or an IP address.
  • SUPI subscription permanent identifier
  • GPSI generic public subscription identifier
  • the first indication information includes an association relationship between the identification information of the first multicast service and the public IP address, and the association relationship means that the public IP address corresponds to the identification information of the first multicast service.
  • the identification information of the first multicast service is used to indicate or identify the first multicast service.
  • the identification information of the first multicast service can be any one of the following: the application identifier of the first multicast service, the triplet of the first multicast service, the service identifier corresponding to the first multicast service, and the user of the UPF network element The IP address of the plane and the user plane port number of the UPF network element.
  • the association relationship between the identification information of the first multicast service and the public IP address may include the following situations:
  • the association relationship between the identification information of the first multicast service and the public IP address is an association relationship between an application identifier and the public IP address, or an association relationship between a triplet and the public IP address.
  • an application can provide only one service; or, an application can provide multiple services, but the sending end and the receiving end do not need to distinguish between different services of the application.
  • the identification information of the multicast service has a one-to-one correspondence with the public IP address, which is equivalent to the one-to-one correspondence between the application identifier of the application and the public IP address, and is also equivalent to the triplet of the application and the public IP address.
  • the association relationship between the identification information of the first multicast service and the public IP address is the association relationship between the service identifier and the public IP address.
  • the sending end and the receiving end distinguish between different services of an application, and the identification information of a service corresponds to a public IP address one-to-one.
  • the association relationship between the identification information of the first multicast service and the public IP address is the association relationship between the user plane IP address of the UPF network element and the user plane port number of the UPF network element and the public IP address.
  • the user plane IP address of the UPF network element and the user plane port number of the UPF network element have a one-to-one correspondence with the public IP address.
  • a user-plane IP address and user-plane port number can be assigned to only one service of an application.
  • the UPF network element identifies a service through the user-plane IP address and user-plane port number, or a user-plane IP address and user-plane port number.
  • the port number can be allocated to multiple applications.
  • the UPF network element distinguishes different services through the user-plane IP address and the user-plane port number, and the IP address of the application server.
  • the first network element may obtain the public IP address according to the identification information of the first multicast service and the foregoing association relationship.
  • the first network element may obtain the public IP address from local information according to the service identifier in the identification information of the first multicast service; or, the first network element may obtain the identifier of the first multicast service
  • the user plane IP address in the information serves as the public IP address.
  • the public IP address may be used to transmit the data of the first multicast service to the multiple terminal devices by the first network element within the mobile communication network.
  • the public IP address may be an IP address of a data packet corresponding to the first multicast service received by multiple terminal devices. It can also be an IP unicast address, an unoccupied IP unicast address, or an unoccupied IP multicast address of any terminal among multiple terminal devices.
  • the UPF network element can allocate or reserve an IP unicast address or an IP multicast address for use as a public IP address.
  • the first network element may receive the first indication information from the SMF network element; or, the first network element may receive the first indication information from the terminal device; or, the first network element may receive the first indication information from the application server The first instruction information.
  • the first indication information may be indicated in explicit or implicit ways.
  • the first indication information may be a message with the function of the first indication information, or in the message A parameter or a set of parameters, or one or more bits in the message.
  • the first network element when the first network element is a UPF network element, the first network element may receive the first data packet from the application server; or, when the first network element is a RAN network element, the first network element The first data packet can be received from the UPF network element.
  • the first network element sends a second data packet according to the first indication information and the first data packet.
  • the destination IP address of the second data packet is the public IP address of the first multicast service.
  • the first network element may generate a second data packet according to the first indication information and the first data packet, and send the second data packet.
  • the first network element is a RAN network element
  • step S1402 includes: the first network element uses air interface multicast to send the second data packet according to the first indication information and the first data packet .
  • step S1402 in combination with the first implementation scenario, step S1402 will be described in detail for the case where the content of the first indication information is different.
  • the first indication information includes the association relationship between the identification information of the first multicast service and the public IP address of the first multicast service.
  • the first network element may determine, according to the identification information of the first multicast service, that the content transmitted by the first multicast service for multiple terminal devices is the same, and the data of the first multicast service may be The package is optimized for transmission. Furthermore, the first network element generates a second data packet according to the first data packet of the first multicast service and the public IP address.
  • the first network element is a RAN network element
  • the first network element receives a first data packet including identification information (for example, a service identifier) of the first multicast service from the UPF network element , Or, receiving the first data packet of the QoS flow of the first multicast service or the public QoS flow from the designated terminal device from the UPF network element, or receiving the first data packet of the specific terminal device from the UPF network element, the The specific terminal device can be instructed by the SMF network element to the RAN network element during the session establishment or session update phase, or determined by the RAN network element itself, then the first network element can determine that the first data packet can use the first multicast service. Public IP address to transmit, thereby generating the second data packet.
  • identification information for example, a service identifier
  • the first network element may only replace the destination IP address of the IP header of the first data packet with the public IP address of the first multicast service to obtain the second data packet.
  • the first network element may take out the payload part of the first data packet and re-encapsulate the IP header to obtain the second data packet, where the destination IP address of the IP header of the second data packet is the public IP address.
  • the first network element may configure a group of RNTIs to the multiple terminal devices, and send the second data packet to the multiple terminal devices at the air interface through the wireless air interface resources corresponding to the group of RNTIs.
  • the first indication information includes the identification information of the first multicast service, but does not include the public IP address of the first multicast service.
  • the first network element may locally retrieve the public IP address corresponding to the identification information of the first multicast service. Then, according to the manner in case 1a, a second data packet is generated according to the first data packet of the first multicast service and the public IP address, and the second data packet is sent to the plurality of terminal devices.
  • the first network element is a UPF network element
  • step S1402 includes: the first network element sends a second data packet to the RAN network element according to the first indication information and the first data packet.
  • step S1402 in combination with the second implementation scenario, step S1402 will be described in detail with respect to different contents of the first indication information.
  • the first indication information includes the association relationship between the identification information of the first multicast service and the public IP address of the first multicast service.
  • the first network element may generate a second data packet according to the first data packet of the first multicast service and the public IP address in the manner in case 1a, and then forward the second data packet to the RAN network element. data pack.
  • the first network element may directly or indirectly send the second data packet to the RAN network element through an intermediate UPF (itermediate UPF, I-UPF) network element.
  • I-UPF intermediate UPF
  • a UPF network element can send a second N3 QoS flow corresponding to the first multicast service, a public N3 tunnel, or each terminal device corresponding to the first multicast service's respective N3 QoS flow to the RAN network element. data pack.
  • the first indication information includes the identification information of the first multicast service, but does not include the public IP address of the first multicast service.
  • the first network element may locally retrieve the public IP address corresponding to the identification information of the first multicast service. Then, according to the method in case 2a, a second data packet is generated according to the first data packet of the first multicast service and the public IP address, and the second data packet is sent to the RAN network element.
  • the first network element may determine that the first data packet carries data of the first multicast service. Since the first indication information includes the identification information of the first multicast service, the first network element can determine that the first data packet can be transmitted using the public IP address of the first multicast service, thereby generating the second data packet.
  • the destination IP address of the second data packet is the public IP address of the first multicast service.
  • association relationship between the identification information of the first multicast service and the public IP address is the association relationship between the application identifier and the public IP address, or the association relationship between the triple and the public IP address is derived from Say:
  • the application identifier corresponds to the triplet, and the first network element can search for the corresponding triplet according to the application identifier.
  • the first network element receives the first data packet from the application server, if the triplet in the first data packet is the same as the triplet in the identification information of the first multicast service, or if the triplet in the first data packet is The triplet of is the same as the triplet corresponding to the application identifier in the identification information of the first multicast service, the first network element can determine that the first data packet can be transmitted using the public IP address of the first multicast service , Thereby generating a second data packet.
  • association relationship between the identification information of the first multicast service and the public IP address is the association relationship between the service identifier and the public IP address:
  • the first network element When the first network element receives the first data packet from the application server, if the first network element is the first data packet received from the tunnel corresponding to the service identifier in the identification information of the first multicast service, then A network element can determine that the first data packet can be transmitted using the public IP address of the first multicast service, thereby generating the second data packet.
  • the association relationship between the identification information of the first multicast service and the public IP address is the association relationship between the user plane IP address of the UPF network element and the user plane port number of the UPF network element and the public IP address
  • the first network element It is a UPF network element.
  • Case 1 If a user plane IP address and user plane port number are only allocated to one service of an application, when the UPF network element is from the user plane IP address of the UPF network element corresponding to the first multicast service and the user of the UPF network element When the first data packet is received by the port number, the UPF network element can determine that the first data packet can be transmitted using the public IP address of the first multicast service, thereby generating the second data packet.
  • Case 2 If a user plane IP address and user plane port number are allocated to multiple applications, when the UPF network element is from the user plane IP address of the UPF network element corresponding to the first multicast service and the user plane port number of the UPF network element After receiving the first data packet, the triplet of the data packet is the same as the triplet of the first multicast service, the UPF network element can determine that the first data packet can be transmitted using the public IP address of the first multicast service , Thereby generating a second data packet.
  • Case 3 If the first indication information includes a service identifier, the UPF network element may determine the corresponding user plane IP address according to the service identifier, and then generate the second data packet according to the above-mentioned case 1 or case 2.
  • the first network element receives the first indication information and the first data packet, and the first indication information may be used to instruct the use of a public IP address to transmit the data of the first multicast service, and the first data
  • the packet carries the first multicast service of the first terminal device, and the destination IP address of the first data packet is the IP address of the first terminal device.
  • the first network element sends a second data packet according to the first indication information and the first data packet, and the destination IP address of the second data packet is the public IP address of the first multicast service.
  • the terminal device can determine to accept the second data packet based on its destination IP address being the public IP address, and will not discard the second data packet, which can prevent the terminal device from packet loss during transmission optimization.
  • the foregoing method further includes: the first network element receives a third data packet, the third data packet corresponds to the first multicast service, and the destination IP address of the third data packet is the first multicast service. 2. The IP address of the terminal device; the first network element discards the third data packet.
  • the third data packet corresponding to the first multicast service may mean that the third data packet carries data of the first multicast service.
  • the content carried by the third data packet is the same as the content carried by the first data packet, that is, the load portion of the third data packet is the same as the load portion of the first data packet.
  • the second terminal device is another terminal device among the plurality of terminal devices.
  • the first network element discards the third data packet, which can be replaced by: the first network element does not process the third data packet.
  • the first network element can optimize the transmission of at least two received data packets (the first data packet and the third data packet) according to the first indication information, that is, only Sending the second data packet generated from the first data packet and the first indication information, and discarding or not processing the third data packet.
  • the first network element may be obtained from the SMF network element.
  • an embodiment of the present application provides a data packet processing method. As shown in FIG. 15, the method includes:
  • the SMF network element obtains the identification information of the first multicast service.
  • the SMF network element may locally generate the identification information of the first multicast service.
  • the SMF may pre-generate the identification information of a group of multicast services (such as temporary group identification, etc.), and the SMF network element may generate the identification information of the first multicast service in advance.
  • the SMF network element After a multicast transmission service request from the application server of the multicast service, one of the identification information of a group of multicast services is allocated to the first multicast service; or, the SMF network element can obtain the service from the application server of the first multicast service. Obtain the identification information of the first multicast service.
  • the application server of the first multicast service may carry the application identifier in the multicast transmission service request.
  • At least one of the triple information or the identifier of the first multicast service generated by the application server itself (for example, temporary group identifier); or, the SMF network element may obtain the identifier of the first multicast service from the UPF network element Information for example, when the application server of the first multicast service requests a multicast transmission service from the SMF network element, the SMF network element may request the UPF network element for the user plane IP address of the UPF network element corresponding to the first multicast service and The user plane port number of the UPF network element; or, the SMF network element may receive the identification information of the first multicast service from the terminal device.
  • the terminal device may carry the first multicast service identification information in the session establishment/update request message sent to the SMF network element.
  • the SMF network element may determine the user plane IP address of the UPF network element corresponding to the first multicast service and the user plane port number of the UPF network element according to the identification information of the first multicast service. Then the above information is sent to the application server, so that the application server sends the data packets of multiple terminal devices to the corresponding UPF network element through a tunnel. Or, when the SMF network element interacts with the UPF network element, the above information can be used as an index or as an IP data flow forwarding rule to instruct the UPF network element how to proceed if it receives a data packet from the user plane IP address and user plane port number Forward.
  • the SMF network element may directly add the user plane IP address in the identification information of the first multicast service.
  • the address is determined as the user plane IP address of the UPF network element corresponding to the first multicast service
  • the user plane port number in the identification information of the first multicast service is determined as the user plane port of the UPF network element corresponding to the first multicast service number.
  • the identification information of the first multicast service includes the service identifier:
  • the SMF network element can use the pre-configured user plane IP address as the UPF network element corresponding to the first multicast service.
  • User plane IP address using the pre-configured user plane port number as the user plane port number of the UPF network element corresponding to the first multicast service.
  • the SMF network element can use the dynamically allocated user plane IP address as the UPF network corresponding to the first multicast service.
  • the user plane IP address of the element, and the dynamically allocated user plane port number is used as the user plane port number of the UPF network element corresponding to the first multicast service.
  • the SMF network element may use the dynamically allocated user plane IP address as the first A user plane IP address of the UPF network element corresponding to the multicast service, and the dynamically allocated user plane port number is used as the user plane port number of the UPF network element corresponding to the first multicast service.
  • the SMF network element dynamically allocates the user plane IP address for the service identifier as the user plane IP address of the UPF network element corresponding to the first multicast service, and dynamically allocates the user plane port number as the UPF network corresponding to the first multicast service The user plane port number of the yuan.
  • the SMF network element requests the UPF network element to dynamically allocate a user plane IP address and a user plane port number for the service identifier, then the SMF network element can use the dynamically allocated user plane IP address as the UPF corresponding to the first multicast service
  • the user plane IP address of the network element uses the dynamically allocated user plane port number as the user plane port number of the UPF network element corresponding to the first multicast service.
  • the SMF network element sends first indication information to the first network element according to the identification information of the first multicast service.
  • the SMF network element may obtain the first indication information from the application server; or, the SMF network element may obtain the first indication information from the terminal device; or, the SMF network element generates the first indication information by itself.
  • the SMF network element can determine the corresponding first indication information according to the acquired identification information of the first multicast service, so as to send the corresponding first indication information to the first network element.
  • the first network element may be a UPF network element or a RAN network element.
  • the public IP address may be included in the first indication information, or the public IP address may not be included.
  • the SMF network element may also The public IP address may be sent to the first network element separately.
  • the SMF network element can obtain the public IP address in the following manner: In a possible implementation manner, the SMF network element can generate the public IP address. Or, in another possible implementation manner, the SMF network element may receive the public IP address from the application server.
  • the data packet processing method provides a method for how the first network element obtains the first indication information, so that when the first network element optimizes the transmission of the first data packet of the first multicast service, it can be based on the first network element.
  • An instruction message and the first data packet send a second data packet, the destination IP address of the first data packet is the IP address of the first terminal device, and the destination IP address of the second data packet is the public IP address of the first multicast service.
  • the terminal device can determine to accept the second data packet based on its destination IP address being the public IP address, and will not discard the second data packet, which can prevent the terminal device from packet loss during transmission optimization.
  • the identification information of the first multicast service as the user plane IP address of the UPF network element corresponding to the first multicast service and the user plane port number of the UPF network element as an example, how the AF network element sends the first multicast service to the UPF network element At least two data packets corresponding to the multicast service.
  • the embodiment of the present application provides another data packet processing method. As shown in FIG. 16, the method includes:
  • the application server obtains the user plane IP address of the UPF network element and the user plane port number of the UPF network element corresponding to the first multicast service.
  • the application server is the application server of the first multicast service.
  • the application server may obtain the user plane IP address of the UPF network element and the user plane port number of the UPF network element corresponding to the first multicast service generated by the UPF network element through the SMF network element.
  • the application server may obtain the user plane IP address of the UPF network element and the user plane port number of the UPF network element corresponding to the first multicast service generated by the SMF network element.
  • the application server uses the user plane IP address and the user plane port number to send a first data packet and a third data packet to the UPF network element.
  • the UPF network element receives the first data packet and the third data packet from the application server through the user plane IP address and the user plane port number.
  • the first data packet and the third data packet both carry the first data of the first multicast service
  • the destination IP address of the first data packet is the IP address of the first terminal device
  • the destination IP address of the third data packet is The IP address is the IP address of the second terminal device, that is, the data of the first multicast service carried by the first data packet and the third data packet are the same, that is, the load portion of the first data packet and the third data packet are the same.
  • the UPF network element can determine that the first data packet and the third data packet correspond to the first multicast service according to the user plane IP address and the user plane port number, so that transmission optimization can be performed.
  • the application server uses The user plane IP address and the user plane port number send at least two data packets of the first multicast service to the UPF network element, and the UPF network element can determine according to the user plane IP address and the user plane port number
  • the at least two data packets correspond to the first multicast service, so that the transmission optimization of the at least two data packets can be performed.
  • the following describes how to process the terminal device after receiving the first data packet optimized for transmission.
  • the embodiment of the present application provides another data packet processing method. As shown in FIG. 17, the method includes:
  • the terminal device receives the first data packet.
  • the first data packet corresponds to the first multicast service, and the destination IP address of the first data packet is the public IP address of the first multicast service.
  • the first data packet, and the public IP address see the previous description .
  • the terminal device may also receive the public IP address.
  • the public IP address may be received from an application server, or the public IP address may be received from a PCF network element, or the public IP address may be received from an SMF network element. That is, the application server, PCF network element, or SMF network element can instruct the terminal device that the data packet whose destination IP address is the public IP address of the first multicast service is sent to the terminal device.
  • the terminal device determines to accept the first data packet according to the public IP address of the destination IP address of the first data packet, and does not discard the first data packet, which can prevent the terminal device from packet loss during transmission optimization.
  • the terminal device may also send a first message to the SMF network element, where the first message includes the identification information of the first multicast service or the public IP address, and the first message is used To request the data of the first multicast service.
  • This implementation manner may enable the SMF network element to send the identification information of the first multicast service or the public IP address to the UPF network element or the RAN network element.
  • the terminal device obtains a second data packet according to the first data packet.
  • the destination IP address of the second data packet is the IP address of the terminal device.
  • the terminal device may replace the destination IP address of the first data packet with the IP address of the terminal device to obtain the second data packet.
  • the terminal device may re-encapsulate the first data packet to obtain the second data packet.
  • the PDU layer on the terminal device side includes two parts (PDU layer 1 and PDU layer 2).
  • the PDU layer 2 is used to replace the destination IP address of the first data packet with the IP address of the terminal device to obtain the second data packet, or to re-encapsulate the first data packet to obtain the second data packet.
  • the PDU layer 2 is used to decapsulate the second data packet and transfer the application data load to the upper application layer.
  • the terminal device if the terminal device establishes a socket (Socket) connection corresponding to the public IP address for the application, the terminal device directly passes the application data payload in the second data packet to the upper application.
  • Socket Socket
  • the terminal device if the terminal device establishes a socket (Socket) connection corresponding to the unicast IP address for the application, the terminal device first obtains the association relationship between the public IP address and the socket (Socket) connection from the configuration file, or through The interaction between the application layer and the communication layer obtains the association relationship between the public IP address and the socket (Socket) connection, and then passes the application data payload in the second data packet to the upper application.
  • Socket socket
  • the terminal device after the terminal device receives the first data packet, it can determine to accept the first data packet based on its destination IP address being the public IP address, and will not discard the first data packet, which can prevent transmission
  • the terminal device loses packets during optimization.
  • the embodiment of the present application provides another data packet processing method. As shown in FIG. 19, the method includes:
  • the SMF network element obtains the identification information of the first multicast service.
  • This step can refer to step S1501, which will not be repeated here.
  • the SMF network element sends first indication information to the UPF network element according to the identification information of the first multicast service.
  • This step can refer to step S1502, which will not be repeated here.
  • the UPF network element receives the first indication information from the SMF network element.
  • the application server sends the first data packet to the UPF network element.
  • the UPF network element receives the first data packet from the application server.
  • the UPF network element sends a second data packet to the RAN network element according to the first indication information and the first data packet.
  • the RAN network element receives the second data packet.
  • step S1402 reference may be made to the related description when the first network element is a UPF network element in step S1402, which will not be repeated here.
  • the RAN network element sends a second data packet to at least two terminal devices in an air interface multicast manner.
  • the at least two terminal devices receive the second data packet.
  • the RAN network element may configure a group of RNTIs to the at least two terminal devices, and send the second data packet to the at least two terminal devices through the radio air interface resources corresponding to the group of RNTIs.
  • the at least two terminal devices obtain respective third data packets according to the second data packets.
  • each terminal device obtains the third data packet from the second data packet are independent of each other.
  • the third data packets obtained by different terminal devices are different, and the destination IP address of the third data packet is The IP address of this terminal device, but the load carried is the same.
  • the terminal device may replace the destination IP address of the second data packet with the IP address of the terminal device to obtain the third data packet.
  • the terminal device may re-encapsulate the second data packet to obtain the third data packet.
  • the UPF network element receives the first indication information and the first data packet.
  • the first indication information may be used to indicate the data of the first multicast service using the public IP address
  • the first data packet Corresponding to the first multicast service, the destination IP address of the first data packet is the IP address of the first terminal device.
  • the UPF network element sends a second data packet according to the first indication information and the first data packet, and the destination IP address of the second data packet is the public IP address of the first multicast service.
  • the terminal device can determine to accept the second data packet based on its destination IP address being the public IP address, and will not discard the second data packet, which can prevent the terminal device from packet loss during transmission optimization.
  • the embodiment of the present application provides another data packet processing method. As shown in FIG. 20, the method includes:
  • the SMF network element obtains the identification information of the first multicast service.
  • This step can refer to step S1501, which will not be repeated here.
  • the SMF network element sends the first indication information to the RAN network element according to the identification information of the first multicast service.
  • the RAN network element receives the first indication information from the SMF network element.
  • This step can refer to step S1502, which will not be repeated here.
  • the application server sends the first data packet to the UPF network element, and the UPF network element sends the first data packet to the RAN network element.
  • the RAN network element receives the first data packet from the application server.
  • the RAN network element sends the second data packet to at least two terminal devices in an air interface multicast manner according to the first indication information and the first data packet.
  • the at least two terminal devices receive the second data packet.
  • step S1402 reference may be made to the related description when the first network element is a RAN network element in step S1402, which will not be repeated here.
  • the at least two terminal devices obtain respective third data packets according to the second data packets.
  • This step can refer to step S1906, which will not be repeated here.
  • the RAN network element receives the first indication information and the first data packet.
  • the first indication information may be used to indicate the data of the first multicast service using the public IP address
  • the first data packet Corresponding to the first multicast service, the destination IP address of the first data packet is the IP address of the first terminal device.
  • the RAN network element sends a second data packet according to the first indication information and the first data packet, and the destination IP address of the second data packet is the public IP address of the first multicast service.
  • the terminal device can determine to accept the second data packet based on its destination IP address being the public IP address, and will not discard the second data packet, which can prevent the terminal device from packet loss during transmission optimization.
  • the following describes several ways for the SMF network element to obtain the first indication information.
  • the SMF network element may obtain the first indication information through the process of AF influence (influence) application flow routing.
  • the SMF network element is notified of the first indication information due to changes in application data in the operator's unified data repository (UDR) network element.
  • UDR unified data repository
  • method one includes:
  • the application server constructs an application request (AF request) message according to the first indication information.
  • the application request (AF request) message includes the first indication information.
  • the application request (AF request) message may also include the public IP address.
  • the application server sends an application request (AF request) message to the NEF network element.
  • AF request application request
  • the NEF network element receives the application request message from the application server.
  • the application server can influence the creation/update (Nnef_TrafficInfluence_Create/Update) service by calling the application traffic of the NEF network element, or the application policy creation (Nnef_ApplyPolicy_Create) service of the NEF network element, or the service parameter creation/update of the NEF network element.
  • the (Nnef_ServiceParameter_Create/Update) service sends an application request (AF request) message to the NEF network element.
  • the application server can send an application traffic influence creation/update request (Nnef_TrafficInfluence_Create/Update request) message, or an application policy creation request (Nnef_ApplyPolicy_Create request) message, or a service parameter creation/update request (Nnef_ServiceParameter_Create/) to the NEF network element.
  • the Update request message includes an application request (AF request) message in the sent message.
  • the NEF network element stores the first indication information in the UDR network element.
  • the NEF network element may store the first indication information in the UDR as a part of the policy/description information of the application.
  • the policy/description information of the application is used to detect and forward data packets of the application.
  • the first indication information and the public IP address may be stored in the UDR as part of the policy/description information of the application.
  • the NEF network element may send a response message of an application request (AF request) message to the application server.
  • AF request application request
  • the UDR network element sends a data management notification (Nudr_DM_Notify notification) message to the PCF network element.
  • the message includes the first indication information.
  • the public IP address may also be included in the message.
  • the PCF network element determines that the application request (AF request) modification event affects the existing PDU session, and for each PDU session, updates the policy and charging control of the SMF network element according to the first instruction information, PCC) rules (rule).
  • PCC first instruction information
  • the application request (AF request) modification event affects the existing PDU session, which means that one terminal device currently has a service related to the application request (AF request) modification event, for example, at least one terminal device is playing APP through video Get the video clips of the live sports event, and the application request (AF request) modification event modifies the strategy/description information of the live sports event.
  • PCC rules are used to detect and forward user data.
  • the PCF network element can update the first indication information to the PCC rule of the SMF network element through the session management policy control update notification (Npcf_SMPolicyControl_UpdateNotify) service.
  • the first indication information may be stored in an application detection filter or service data flow filter (application detection filters/service data flow filter(s)) of the PCC rule.
  • the PCF network element may update the public IP address to the PCC rule of the SMF network element.
  • the public IP address can also be stored in the application detection filter or service data flow filter (application detection filters/service data flow filter(s)) of the PCC rule.
  • the SMF network element sends first indication information to the first network element.
  • the SMF network element may send the public IP address to the first network element.
  • the SMF network element may send the above-mentioned information (the first indication information, the public IP address) to the first network element during the establishment and modification of the user plane QoS flow.
  • the SMF network element may carry the foregoing information in the PDU session management message sent to the UPF network element.
  • the above-mentioned information can be carried in a packet detection rule (PDR), for example, it can be carried in the (IP) packet filter ((IP) packet filter) of the PDR, and application detection filters (application detection filters). Or in the service data flow filter(s).
  • PDR packet detection rule
  • IP IP packet filter
  • application detection filters application detection filters
  • the SMF network element may obtain the first indication information from the UDR network element during the establishment or modification of the user plane QoS flow.
  • the second method includes two stages.
  • the first stage as shown in Figure 22, refers to the application server sending the first indication information to the UDR network element.
  • the second stage is shown in Figure 23, where the SMF network element obtains the first indication information from the UDR network element.
  • the first stage includes:
  • the application server determines the first indication information, and sends the first indication information to the NEF network element.
  • the application server may send a packet flow description management create/update (Nnef_PFDManagement_Create/Update request) message to the NEF network element.
  • the message includes the first indication information.
  • the first indication information may be carried through the extended PFD, that is, one item of first indication information is added to the extended PFD. If the first identification indication information does not include the public IP address, the public IP address can also be added to the extended PFD.
  • the application server may send multiple first indication information to the NEF network element at one time, corresponding to different applications or different services of an application.
  • the NEF network element may send multiple first indication information to the NEF network element at one time, corresponding to different applications or different services of an application.
  • the application identifier or triplet uniquely identifies an application
  • the Application identifier represents the application identifier. It can be seen that the first indication information 1 and the first indication information 2 correspond to different services of one application, and the first indication information 3 and the first indication information 4 correspond to different applications.
  • the NEF network element may also be arranged on the same network element as the packet flow description function (PFDF) network element.
  • PFDF packet flow description function
  • the NEF network element performs authorization checks to determine that the application server has the authority to modify the PFD.
  • the NEF network element sends a UDR data management creation/update request (Nudr_DM_Create/Update request) message to the UDR network element.
  • the message may include the first indication information.
  • the PFD may be extended to carry the first indication information.
  • the UDR network element updates the first indication information.
  • the UDR network element may update the PFD corresponding to the application identifier to update the first indication information.
  • the UDR network element sends a UDR data management creation/update response (Nudr_DM_Create/Update response) message to the NEF network element.
  • This message is used to confirm the UDR data management creation/update request (Nudr_DM_Create/Update request) message.
  • the NEF network element sends a data packet flow description management creation/update response (Nnef_PFDManagement_Create/Update response) message to the application server.
  • This message is used to confirm the Nnef_PFDManagement_Create/Update request (Nnef_PFDManagement_Create/Update request) message.
  • the second stage includes:
  • the SMF network element sends a data packet flow description management acquisition request (Nnef_PFDManagement_Fetch request) message to the NEF network element to request first indication information.
  • Nnef_PFDManagement_Fetch request a data packet flow description management acquisition request
  • the message includes the application identifier.
  • the NEF network element checks whether there is a PFD corresponding to the application identifier locally, and if so, execute step S2304. Otherwise, the NEF network element sends a data management query request (Nudr_DM_Query request) message to the UDR network element to obtain the PFD including the first indication information.
  • a data management query request Nudr_DM_Query request
  • the message includes the application identifier.
  • the UDR network element sends a data management query response (Nudr_DM_Query response) message to the NEF network element.
  • the message includes the extended PFD, and the extended PFD includes the first indication information.
  • the UDR network element can query the corresponding extended PFD according to the application identifier.
  • the NEF network element sends a data packet flow description management acquisition response (Nnef_PFDManagement_Fetch response) message to the SMF network element.
  • Nnef_PFDManagement_Fetch response a data packet flow description management acquisition response
  • the message includes the extended PFD, and the extended PFD includes the first indication information.
  • the SMF network element sends first indication information to the first network element.
  • This step is the same as step S2106 and will not be repeated here.
  • the application server configures the first indication information in the UDR network element through the service specific parameter provisioning process, and the PCF network element obtains the first indication information from the UDR network element and displays it on the subsequent user plane.
  • the first indication information is sent to the SMF network element.
  • the third method includes:
  • the application server constructs an application request (AF request) message according to the first indication information.
  • This step is the same as step S2101 and will not be repeated here.
  • the application server sends an application request (AF request) message to the NEF network element.
  • AF request application request
  • the application server may send an application request (AF request) message to the NEF network element by calling the service parameter creation/update (Nnef_ServiceParameter_Create/Update) service of the NEF network element.
  • AF request application request
  • service parameter creation/update Nnef_ServiceParameter_Create/Update
  • the application server may send a service parameter creation/update request (Nnef_ServiceParameter_Create/Update request) message to the NEF network element, and the message includes an application request (AF request) message.
  • a service parameter creation/update request (Nnef_ServiceParameter_Create/Update request) message to the NEF network element, and the message includes an application request (AF request) message.
  • the NEF network element stores the first indication information in the UDR network element.
  • This step is the same as step S2103 and will not be repeated here.
  • the NEF network element sends a service parameter creation/update response (Nnef_ServiceParameter_Create/Update response) message to the application server.
  • This message is used to confirm the service parameter creation/update request (Nnef_ServiceParameter_Create/Update request) message.
  • the UDR network element sends a data management notification (Nudr_DM_Notify notification) message to the PCF network element.
  • the message includes the first indication information.
  • the public IP address may also be included in the message.
  • the PCF network element determines that the application data modification (data modification) event affects the existing PDU session, and for each PDU session, updates the policy and charging control of the SMF network element according to the first instruction information, PCC) rules (rule).
  • the application data modification (data modification) event affects the existing PDU session, which means that one terminal device currently has performed services related to the application data modification (data modification) event, for example, at least one terminal device is playing APP through video Obtain video clips of live sports events, and apply data modification events to modify the strategy/descriptive information of the live sports events.
  • the PCF network element determines that the application request (AF request) modification event affects the existing PDU session.
  • step S2105 The other contents of this step are the same as step S2105, and will not be repeated here.
  • the SMF network element sends first indication information to the first network element.
  • This step is the same as step S2106 and will not be repeated here.
  • the application server may send the first indication information to the PCF network element when establishing an application session (AF session) for each terminal device (per UE), and the PCF network element may establish/modify the subsequent session policy association ( In the SM policy Association establishment/modification process, the first indication information is sent to the SMF network element.
  • AF session application session
  • UE terminal device
  • mode four includes:
  • the application server sends first indication information to the NEF network element.
  • the application server may send the first indication information to the NEF network element through the application function QoS session creation (Nnef_AFsessionWithQoS_create) service of the NEF network element.
  • the application server sends an application function QoS session creation request (Nnef_AFsessionWithQoS_create request) message to the NEF network element.
  • the message may include the IP address of the terminal device, the application function identifier (AF identifier), and the description of the application flows. ).
  • the data flow filtering information (traffic filtering information) described by the application data flow includes the first indication information.
  • the source IP address in the quintuple is changed to the user plane IP address in the first instruction information or the user plane IP address corresponding to the service identifier in the first instruction information .
  • the existing quintuple can be extended, and the user plane IP address or the service identifier in the first indication information can be added on the basis of the quintuple, which can be called an enhanced quintuple or a six-tuple or other names .
  • the NEF network element performs an authorization check to determine that the application server has the authority to perform the requested operation.
  • the NEF network element sends a policy authorization creation request (Npcf_policyAuthoization_Create request) message to the PCF network element.
  • Npcf_policyAuthoization_Create request a policy authorization creation request
  • the message includes the parameters obtained from the application server in step S2501, and the parameters include the first indication information.
  • the PCF network element generates PCC rules based on these parameters, and the generated PCC rules include the first indication information.
  • the PCF network element sends a policy authorization creation response (Npcf_policyAuthoization_Create response) message to the NEF network element.
  • Npcf_policyAuthoization_Create response a policy authorization creation response
  • This message is used to confirm the policy authorization creation request (Npcf_policyAuthoization_Create request) message.
  • the NEF network element sends an application function QoS session creation response (Nnef_AFsessionWithQoS_Create response) message to the application server.
  • This message is used to confirm the application function QoS session creation request (Nnef_AFsessionWithQoS_create request) message.
  • the PCF network element initiates a session policy association establishment/modification (SM policy Association establishment/modification) process, and sends the first indication information to the SMF network element.
  • SM policy Association establishment/modification session policy association establishment/modification
  • the first indication information may be included in the PCC rules, specifically, it may be included in the packet filters, application detection filters, or service data flow filters of the PCC rules. s)).
  • step S2506 and steps S2504-S2505 are executed in no order.
  • the SMF network element sends first indication information to the first network element.
  • This step is the same as step S2106 and will not be repeated here.
  • the terminal device may send the first indication information to the SMF network element when initiating the QoS flow establishment or modification process.
  • mode five includes:
  • the terminal device sends a PDU session establishment or update message to the SMF network element.
  • the message includes the first indication information.
  • the first indication information may be carried in an IP packet filter (IP packet filter) of the message.
  • IP packet filter IP packet filter
  • the SMF network element sends first indication information to the first network element.
  • This step is the same as step S2106 and will not be repeated here.
  • the UPF network element has obtained the first indication information and the public IP address, how the UPF network element sends the second data packet according to the first indication information and the first data packet will be described.
  • an embodiment of the present application provides another method for processing the data packet, and the method includes:
  • At least two terminal devices respectively initiate a PDU session establishment or modification process to respectively request the establishment of a user plane connection (that is, a dedicated QoS flow) for the first multicast service.
  • a user plane connection that is, a dedicated QoS flow
  • At least two terminal devices respectively send a PDU session establishment/modification request (PDF session establishment/modification request) message to the SMF network element.
  • PDU session establishment/modification request PDF session establishment/modification request
  • the SMF network element determines, according to the first indication information in the PCC rule, that the data packet of the first multicast service can be optimized for transmission, and establishes the transmission of the first multiple for the at least two terminal devices.
  • the SMF network element may send an N4 session establishment/modification request (N4 session establishment/modification request) message to the UPF network element to establish a dedicated QoS flow for transmitting the first multicast service for the at least two terminal devices .
  • N4 session establishment/modification request N4 session establishment/modification request
  • the UPF network element may send an N4 session establishment/modification response (N4 session establishment/modification response) message to the SMF network element. This message is used to confirm the N4 session establishment/modification request (N4 session establishment/modification request) message.
  • N4 session establishment/modification response N4 session establishment/modification response
  • the dedicated QoS flow means that the QoS flow can only be used to transmit the data packets of the first multicast service, and the data packets of other applications or services of the terminal device cannot be mapped to the QoS flow, that is, the data packets of other applications or services. It cannot be transmitted to the terminal device through this QoS stream.
  • the SMF network element when other applications or services of the terminal device request to establish a QoS flow, the SMF network element sends the PCC rule to the UPF network element in the process of responding to the request: SMF network element will not send the first multicast service
  • the dedicated QoS flow is bound to other applications or services.
  • the SMF network element may establish a new PCC rule in the PCC rule, which contains the first indication information.
  • the UPF network element receives data packets of the first multicast service corresponding to at least two terminal devices from the application server, including the first data packets.
  • the UPF network element may regard the data packet of the first terminal device as the first data packet, where the first terminal device is the terminal device of the first data packet received by the UPF network element, that is, the first data received by the UPF network element
  • the packet is a data packet sent to the first terminal device.
  • the data packet sent to the first terminal device is selected as the first data packet according to a preset rule.
  • the received data packets of the first multicast service of the remaining terminal devices may be discarded or not processed.
  • the UPF network element can send the received packets within the time window. Optimize the data packets of the first multicast service of at least two terminal devices.
  • the time window may be pre-configured by the operator, or may be dynamically configured by the operator as required.
  • the UPF network element sends a second data packet to the RAN network element according to the first indication information and the first data packet.
  • this step realizes that the second data packet is generated on the UPF network element, and the destination IP address of the second data packet is the public IP address.
  • the RAN network element sends a second data packet to the at least two terminal devices in an air interface multicast manner.
  • the RAN network element RAN network element may configure a group RNTI to the at least two terminal devices, and send the second data packet to the at least two terminal devices at the air interface through the radio air interface resources corresponding to the group RNTI.
  • the at least two terminal devices obtain respective third data packets according to the second data packets.
  • This step can refer to step S1906, which will not be repeated here.
  • the UPF network element sends only the first multicast service data packet corresponding to the first terminal device among the at least two terminal devices to the RAN network element.
  • an embodiment of the present application provides another method for processing the data packet, and the method includes:
  • At least two terminal devices or application servers respectively initiate a PDU session establishment or modification process to request the establishment or modification of a QoS flow for a specific terminal device to receive data from the application server.
  • the QoS flow is used to carry the application layer signaling or media data exchanged between the terminal device and the application server.
  • At least two terminal devices respectively send a PDU session establishment/modification request (PDU session establishment/modification request) message to the SMF network element.
  • PDU session establishment/modification request PDU session establishment/modification request
  • the SMF network element initiates an N4 session establishment process to the UPF network element, and generates first indication information.
  • the SMF network element may send an N4 session establishment/modification request (N4 session establishment/modification request) message to the UPF network element.
  • the UPF network element may send an N4 session establishment/modification response (N4 session establishment/modification response) message to the SMF network element.
  • the N4 session establishment/modification response (N4 session establishment/modification response) message may include the user plane IP address and the user plane port number of the UPF network element.
  • the SMF network element may generate the first indication information according to the user plane IP address and user plane port number corresponding to the first multicast service.
  • the SMF network element sends the first indication information to the RAN network element.
  • the first indication information may be carried in a PDU session resource setup request transfer (PDU session resource setup request transfer) message (which may also be understood as N2 session management information (N2 SM info)).
  • PDU session resource setup request transfer PDU session resource setup request transfer
  • N2 SM info N2 session management information
  • the UPF network element receives data packets of the first multicast service corresponding to at least two terminal devices from the application server, which include the first data packets.
  • This step is the same as step S2703 and will not be repeated here.
  • the UPF network element sends the first data packet to the RAN network element through the QoS flow of the first multicast service corresponding to the first terminal device or the N3 public QoS flow corresponding to the first multicast service between the UPF network element and the RAN.
  • the UPF network element optimizes the transmission of the data packet of the first multicast service.
  • the RAN network element sends a second data packet to the at least two terminal devices in an air interface multicast manner according to the first indication information and the first data packet.
  • the first network element is a RAN network element, and will not be repeated here.
  • this step realizes that the second data packet is generated on the RAN network element, and the destination IP address of the second data packet is the public IP address.
  • the at least two terminal devices obtain respective third data packets according to the second data packets.
  • This step can refer to step S1906, which will not be repeated here.
  • the UPF network element sends the first multicast service data packet corresponding to the at least two terminal devices to the RAN network element.
  • an embodiment of the present application provides another method for processing the data packet, and the method includes:
  • Steps S3101-S3103 are the same as steps S2901-S2903 in FIG. 29, and will not be repeated here.
  • the UPF network element sends data packets corresponding to each terminal device to the RAN network element in a unicast manner.
  • the RAN network element receives the data packet of the first multicast service corresponding to each terminal device from the UPF network element.
  • the UPF network element does not optimize the transmission of the data packet of the first multicast service.
  • Steps S3105-S3107 are the same as steps S2905-S2907 and will not be repeated here.
  • this step realizes that the second data packet is generated on the RAN network element, and the destination IP address of the second data packet is the public IP address.
  • the methods and/or steps implemented by the terminal device can also be implemented by components (such as chips or circuits) that can be used in the terminal device, and the methods and/or steps implemented by the network device can also be implemented by the terminal device. It can also be implemented by components that can be used in network devices.
  • an embodiment of the present application also provides a communication device, which is used to implement the foregoing various methods.
  • the communication device may be the terminal device in the foregoing method embodiment, or a device including the foregoing terminal device, or a chip or functional module in the terminal device; or, the communication device may be the network device in the foregoing method embodiment, or A device containing the above-mentioned network equipment, or a chip or functional module in the network equipment.
  • the communication device includes hardware structures and/or software modules corresponding to each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.
  • the embodiments of the present application may divide the communication device into functional modules according to the foregoing method embodiments.
  • each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or software functional modules. It should be noted that the division of modules in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • FIG. 33 shows a schematic structural diagram of a communication device 330.
  • the communication device 330 includes a processing module 3301 and a transceiver module 3302.
  • the communication device 330 may be the first network element in Figure 14, Figure 21, Figure 23, Figure 24, Figure 25, Figure 26, the RAN network element in Figure 19, Figure 20, Figure 27, Figure 29, Figure 31, or UPF network element.
  • the processing module 3301 may also be referred to as a processing unit, and is configured to implement the processing function of the first network element, the RAN network element, or the UPF network element in the foregoing method embodiment. For example, step S3105 in FIG. 31 is executed.
  • the transceiver module 3302 which may also be referred to as a transceiver unit, is used to implement the transceiver function of the first network element, the RAN network element, or the UPF network element in the foregoing method embodiment. For example, execute steps S1401-S1402 in Figure 14, steps S1902, S1903, S1904, and S1905 in Figure 19, steps S2002, S2003, and S2004 in Figure 20, step S2106 in Figure 21, step S2305 in Figure 23, and Step S2407 in Figure 24, Step S2507 in Figure 25, Step S2602 in Figure 26, Steps S2702, S2703, S2704, and S2705 in Figure 27, Steps S2902, S2903, S2904, S2905, S2906 in Figure 29, and Figure 31 Steps S3102, S3103, S3104, and S3106 in.
  • the transceiver module 3302 may be referred to as a transceiver circuit, a transceiver, a transceiver, or a communication interface.
  • the transceiver module 3302 is configured to receive the first indication information and the first data packet, the first data packet corresponds to the first multicast service, and the destination Internet Protocol IP address of the first data packet is the IP address of the first terminal device
  • the transceiver module 3302 is also used to send a second data packet according to the first indication information and the first data packet.
  • the destination IP address of the second data packet is the public IP address of the first multicast service, and the public IP address is used to At least two terminal devices transmit the data of the first multicast service; wherein the first indication information is used to indicate that the public IP address of the first multicast service is used to transmit the data of the first multicast service.
  • it further includes a processing module 3301, a transceiver module 3302, and is further configured to receive a third data packet, the third data packet corresponds to the first multicast service, and the destination IP address of the third data packet is the second For the IP address of the terminal device, the content carried by the third data packet is the same as the content carried by the first data packet; the processing module 3301 is configured to discard the third data packet.
  • the transceiver module 3302 is specifically configured to receive the first indication information from the session management function network element.
  • the first indication information includes the association relationship between the identification information of the first multicast service and the public IP address.
  • the first indication information includes the identification information of the first multicast service, but does not include the public IP address
  • the communication device further includes a processing module 3301: a transceiver module 3302, which is also used for subscribing to the session management function network.
  • the element receives the public IP address, or the processing module 3301 is configured to obtain the public IP address according to the identification information of the first multicast service.
  • the communication device is a user plane function network element; the transceiver module 3302 is specifically configured to: send a second data packet to the access network network element according to the first indication information and the first data packet.
  • the communication device is an access network network element; the transceiver module 3302 is specifically configured to: according to the first indication information and the first data packet, send the second data packet in an air-interface multicast manner.
  • the communication device 330 is presented in the form of dividing various functional modules in an integrated manner.
  • the "module” here can refer to a specific ASIC, circuit, processor and memory that executes one or more software or firmware programs, integrated logic circuit, and/or other devices that can provide the above-mentioned functions.
  • the communication device 330 may adopt the form of the base station 300 shown in FIG. 3.
  • the processor 331 in the base station 300 shown in FIG. 3 may invoke the computer execution instructions stored in the memory 332 to make the base station 300 execute the method in the foregoing method embodiment.
  • the function/implementation process of the processing module 3301 in FIG. 33 may be implemented by the processor 331 in the base station 300 shown in FIG. 3 calling a computer execution instruction stored in the memory 332.
  • the function/implementation process of the transceiver module 3302 in FIG. 33 may be implemented by the RF circuit 334 in the base station 300 shown in FIG. 3.
  • the communication device 330 may take the form of the network device 400 shown in FIG. 4.
  • the processor 401 in the network device 400 shown in FIG. 4 may invoke the computer execution instructions stored in the memory 403 to make the network device 400 execute the method in the foregoing method embodiment.
  • the function/implementation process of the processing module 3301 in FIG. 33 may be implemented by the processor 401 in the network device 400 shown in FIG. 4 calling a computer execution instruction stored in the memory 403.
  • the function/implementation process of the transceiver module 3302 in FIG. 33 may be implemented through the communication interface 404 in the network device 400 shown in FIG. 4.
  • the communication device 330 provided in this embodiment can perform the above-mentioned method, the technical effects that can be obtained can refer to the above-mentioned method embodiment, which will not be repeated here.
  • FIG. 34 shows a schematic structural diagram of a communication device 340.
  • the communication device 340 includes a processing module 3401 and a transceiver module 3402.
  • the communication device 340 may be the SMF network element in FIG. 15, FIG. 19, FIG. 20, FIG. 21, FIG. 23, FIG. 24, FIG. 25, FIG. 26, FIG. 27, FIG. 29, and FIG. 31.
  • the processing module 3401 may also be referred to as a processing unit, and is used to implement the processing function of the SMF network element in the foregoing method embodiment. For example, step S1501 in FIG. 15, step S1901 in FIG. 19, and step S2001 in FIG. 20 are executed.
  • the transceiver module 3402 which may also be referred to as a transceiver unit, is used to implement the transceiver function of the SMF network element in the foregoing method embodiment. For example, execute step S1502 in FIG. 15, step S1902 in FIG. 19, step S2002 in FIG. 20, steps S2105 and S2106 in FIG. 21, steps S2301, S2304, and S2305 in FIG. 23, and steps S2406 and S2406 in FIG. 24. S2407, steps S2506 and S2507 in FIG. 25, steps S2601 and S2602 in FIG. 26, steps S2701 and S2702 in FIG. 27, steps S2901, S2902, S2903 in FIG. 29, and steps S3101, S3102, S3103 in FIG. 31 .
  • the transceiver module 3402 may be referred to as a transceiver circuit, a transceiver, a transceiver, or a communication interface.
  • the processing module 3401 is configured to obtain the identification information of the first multicast service; the transceiver module 3402 is configured to send the first indication information to the first network element according to the identification information of the first multicast service; An indication information is used to indicate that the public IP address is used to transmit the data of the first multicast service, and the public IP address is used to transmit the data of the first multicast service to at least two terminal devices.
  • the processing module 3401 is further configured to: obtain the first indication information.
  • the transceiver module 3402 is further configured to: send a public IP address to the first network element.
  • the first indication information includes a public IP address.
  • the processing module 3401 is also used to generate a public IP address; or the transceiver module 3402 is also used to receive a public IP address from the application server.
  • the processing module 3401 is further configured to generate identification information of the first multicast service, or the transceiver module 3402 is further configured to receive identification information of the first multicast service from the application server.
  • the communication device 340 is presented in the form of dividing various functional modules in an integrated manner.
  • the "module” here can refer to a specific ASIC, circuit, processor and memory that executes one or more software or firmware programs, integrated logic circuit, and/or other devices that can provide the above-mentioned functions.
  • the communication device 340 may take the form of the network device 400 shown in FIG. 4.
  • the processor 401 in the network device 400 shown in FIG. 4 may invoke the computer execution instructions stored in the memory 402 to make the network device 400 execute the method in the foregoing method embodiment.
  • the function/implementation process of the processing module 3401 in FIG. 34 may be implemented by the processor 401 in the network device 400 shown in FIG. 4 invoking a computer execution instruction stored in the memory 403.
  • the function/implementation process of the transceiver module 3402 in FIG. 34 may be implemented through the communication interface 404 in the network device 400 shown in FIG. 4.
  • the communication device 340 provided in this embodiment can perform the above-mentioned method, the technical effects that can be obtained can refer to the above-mentioned method embodiment, which will not be repeated here.
  • FIG. 35 shows a schematic structural diagram of a communication device 350.
  • the communication device 350 includes a processing module 3501 and a transceiver module 3502.
  • the communication device 200 may be the application server in Fig. 16, Fig. 19, Fig. 20, Fig. 21, Fig. 22, Fig. 24, Fig. 25, Fig. 27, Fig. 29, and Fig. 31.
  • the processing module 3501 may also be referred to as a processing unit, which is used to implement the processing function of the application server in the foregoing method embodiment. For example, step S1601 in FIG. 16, step S2101 in FIG. 21, step S2201 in FIG. 22, and step S2401 in FIG. 24 are executed.
  • the transceiver module 3502 which may also be referred to as a transceiver unit, is used to implement the transceiver function of the application server in the foregoing method embodiment. For example, execute step S1602 in FIG. 16, step S1903 in FIG. 19, step S2003 in FIG. 20, step S2102 in FIG. 21, step S2201 in FIG. 22, steps S2402, S2404 in FIG. 24, and step S2404 in FIG. Step S2501, step S2703 in FIG. 27, and steps S2901 and S2904 in FIG. 29.
  • the transceiver module 3502 may be referred to as a transceiver circuit, a transceiver, a transceiver, or a communication interface.
  • the processing module 3501 is used to obtain the user plane Internet Protocol IP address of the user plane function network element corresponding to the first multicast service and the user plane port number of the user plane function network element; the transceiver module 3502 is used to use the user
  • the first data packet and the second data packet are sent to the user-plane function network element by using the plane IP address and the user plane port number, where the first data packet and the second data packet both include the first data of the first multicast service, and the first data packet is the first data packet of the first multicast service.
  • the destination IP address of one data packet is the IP address of the first terminal device, and the destination IP address of the second data packet is the IP address of the second terminal device.
  • the communication device 350 is presented in the form of dividing various functional modules in an integrated manner.
  • the "module” here can refer to a specific ASIC, circuit, processor and memory that executes one or more software or firmware programs, integrated logic circuit, and/or other devices that can provide the above-mentioned functions.
  • the communication device 350 may take the form of the network device 400 shown in FIG. 4.
  • the processor 401 in the network device 400 shown in FIG. 4 may invoke the computer execution instructions stored in the memory 402 to make the network device 400 execute the method in the foregoing method embodiment.
  • the function/implementation process of the processing module 3501 in FIG. 35 may be implemented by the processor 401 in the network device 400 shown in FIG. 4 invoking a computer execution instruction stored in the memory 403.
  • the function/implementation process of the transceiver module 3502 in FIG. 35 may be implemented through the communication interface 404 in the network device 400 shown in FIG. 4.
  • the communication device 350 provided in this embodiment can perform the above-mentioned method, the technical effects that can be obtained can refer to the above-mentioned method embodiment, which will not be repeated here.
  • FIG. 36 shows a schematic structural diagram of a communication device 360.
  • the communication device 360 includes a processing module 3601 and a transceiver module 3602.
  • the communication device 360 may be the terminal device in FIG. 17, FIG. 19, FIG. 20, FIG. 26, FIG. 27, FIG. 29, and FIG. 31.
  • the processing module 3601 may also be referred to as a processing unit, and is used to implement the processing function of the terminal device in the foregoing method embodiment. For example, step S1702 in FIG. 17, step S1906 in FIG. 19, step S2005 in FIG. 20, step S2706 in FIG. 27, step S2907 in FIG. 29, and step S3107 in FIG. 31 are executed.
  • the transceiver module 3602 which may also be referred to as a transceiver unit, is used to implement the transceiver function of the terminal device in the foregoing method embodiment. For example, execute step S1701 in FIG. 17, step S1905 in FIG. 19, step S2004 in FIG. 20, step S2601 in FIG. 26, steps S2701 and S2705 in FIG. 27, steps S2901, S2906 in FIG. 29, and step S2906 in FIG. 31 Steps S3101, S3106 in.
  • the transceiver module 3602 may be referred to as a transceiver circuit, transceiver, transceiver, or communication interface.
  • the transceiver module 3602 is configured to receive a first data packet, the first data packet corresponds to the first multicast service, and the destination Internet Protocol IP address of the first data packet is the public IP address of the first multicast service, and the public IP The address is used to transmit data of the first multicast service to at least two terminal devices; the processing module 3601 is used to obtain a second data packet according to the first data packet, and the destination IP address of the second data packet is the IP address of the terminal device.
  • the transceiver module 3602 is also used to receive a public IP address.
  • the transceiver module 3602 is further configured to send a first message to the session management function network element, the first message includes the identification information or the public IP address of the first multicast service, and the first message is used to request The data of the first multicast service.
  • the communication device 360 is presented in the form of dividing various functional modules in an integrated manner.
  • the "module” here can refer to a specific ASIC, circuit, processor and memory that executes one or more software or firmware programs, integrated logic circuit, and/or other devices that can provide the above-mentioned functions.
  • the communication device 360 may take the form of the terminal device 105 shown in FIG. 2.
  • the processor 180 in the terminal device 200 shown in FIG. 2 may invoke a computer execution instruction stored in the memory 120 to make the terminal device 200 execute the method in the foregoing method embodiment.
  • the function/implementation process of the processing module 3601 in FIG. 36 may be implemented by the processor 180 in the terminal device 200 shown in FIG. 2 invoking a computer execution instruction stored in the memory 120.
  • the function/implementation process of the transceiver module 3602 in FIG. 36 may be implemented by the RF circuit 100 in the terminal device 200 shown in FIG. 2.
  • the communication device 360 provided in this embodiment can perform the above-mentioned method, the technical effects that can be obtained can refer to the above-mentioned method embodiment, which will not be repeated here.
  • the embodiment of the present application also provides a communication device.
  • the communication device includes a processor, a memory, and a transceiver.
  • the processor is coupled with the memory.
  • the processor executes a computer program or instruction in the memory, 23.
  • the method corresponding to the first network element in Figure 24, Figure 25, and Figure 26 is executed, or the method corresponding to the RAN network element in Figure 19, Figure 20, Figure 27, Figure 29, and Figure 31 is executed, or , Figure 19, Figure 20, Figure 27, Figure 29, Figure 31 corresponding to the UPF network element method is executed.
  • the embodiment of the present application also provides a communication device.
  • the communication device includes a processor, a memory, and a communication interface.
  • the processor is coupled with the memory.
  • the processor executes a computer program or instruction in the memory, 20, Figure 21, Figure 23, Figure 24, Figure 25, Figure 26, Figure 27, Figure 29, Figure 31 corresponding to the method of the SMF network element is executed.
  • the embodiment of the present application also provides a communication device.
  • the communication device includes a processor, a memory, and a communication interface.
  • the processor is coupled with the memory.
  • the processor executes a computer program or instruction in the memory, 20, Figure 21, Figure 22, Figure 24, Figure 25, Figure 27, Figure 29, Figure 31 corresponding to the method of the application server is executed.
  • the embodiment of the present application also provides a communication device.
  • the communication device includes a processor, a memory, and an RF circuit.
  • the processor is coupled with the memory.
  • the processor executes the computer program or instruction in the memory, the communication device shown in FIG. 17, FIG. 19, and FIG. 20.
  • the method corresponding to the terminal device in FIG. 26, FIG. 27, FIG. 29, and FIG. 31 is executed.
  • the embodiment of the present application also provides a chip, including: a processor and an interface, used to call from the memory and run the computer program stored in the memory, and execute FIG. 14, FIG. 21, FIG. 23, FIG. 24, FIG. 25, and FIG.
  • the embodiment of the present application also provides a chip, including: a processor and an interface, used to call from the memory and run the computer program stored in the memory, and execute FIG. 15, FIG. 19, FIG. 20, FIG. 21, FIG. 23, and FIG. 24.
  • a chip including: a processor and an interface, used to call from the memory and run the computer program stored in the memory, and execute FIG. 15, FIG. 19, FIG. 20, FIG. 21, FIG. 23, and FIG. 24.
  • the embodiment of the present application also provides a chip, including: a processor and an interface, used to call from the memory and run the computer program stored in the memory, and execute FIG. 16, FIG. 19, FIG. 20, FIG. 21, FIG. 22, and FIG. 24.
  • a chip including: a processor and an interface, used to call from the memory and run the computer program stored in the memory, and execute FIG. 16, FIG. 19, FIG. 20, FIG. 21, FIG. 22, and FIG. 24.
  • the embodiment of the present application also provides a chip, including: a processor and an interface, used to call from the memory and run the computer program stored in the memory, and execute FIG. 17, FIG. 19, FIG. 20, FIG. 26, FIG. 27, and FIG. 29.
  • a chip including: a processor and an interface, used to call from the memory and run the computer program stored in the memory, and execute FIG. 17, FIG. 19, FIG. 20, FIG. 26, FIG. 27, and FIG. 29.
  • the embodiment of the present application also provides a computer-readable storage medium that stores instructions in the computer-readable storage medium.
  • the computer or the processor executes FIG. 14, FIG. 21, and FIG.
  • the method corresponding to the first network element in Figure 23, Figure 24, Figure 25, and Figure 26, or the method corresponding to the RAN network element in Figure 19, Figure 20, Figure 27, Figure 29, and Figure 31 is performed, or the method corresponding to the RAN network element in Figure 19, Figure 20, Figure 27, Figure 29, and Figure 31 is performed.
  • the embodiment of the present application also provides a computer-readable storage medium that stores instructions in the computer-readable storage medium.
  • the instructions run on a computer or a processor
  • the computer or the processor executes FIG. 15, FIG. 19, and FIG.
  • the embodiment of the present application also provides a computer-readable storage medium that stores instructions in the computer-readable storage medium.
  • the computer or the processor executes FIG. 16, FIG. 19, and FIG.
  • the embodiment of the present application also provides a computer-readable storage medium, which stores instructions in the computer-readable storage medium.
  • the instructions run on a computer or a processor
  • the computer or the processor executes FIG. 17, FIG. 19, and FIG. Methods corresponding to the terminal devices in Figure 20, Figure 26, Figure 27, Figure 29, and Figure 31.
  • the embodiment of the present application also provides a computer program product containing instructions.
  • the computer or the processor executes Figure 14, Figure 21, Figure 23, Figure 24, Figure 25, Figure 26
  • Figure 14, Figure 21, Figure 23, Figure 24, Figure 25, Figure 26 The method corresponding to the first network element in Figure 19, Figure 20, Figure 27, Figure 29, Figure 31, or the method corresponding to the RAN network element in Figure 19, Figure 20, Figure 27, Figure 29 , The method corresponding to the UPF network element in Figure 31.
  • the embodiment of the present application also provides a computer program product containing instructions.
  • the instructions run on a computer or a processor, the computer or the processor executes Figure 15, Figure 19, Figure 20, Figure 21, Figure 23, Figure 24 , Figure 25, Figure 26, Figure 27, Figure 29, Figure 31 SMF network elements corresponding methods.
  • the embodiment of the present application also provides a computer program product containing instructions.
  • the instructions run on a computer or a processor
  • the computer or the processor executes Figure 16, Figure 19, Figure 20, Figure 21, Figure 22, and Figure 24.
  • the embodiment of the present application also provides a computer program product containing instructions.
  • the instructions run on a computer or a processor
  • the computer or the processor executes Figure 17, Figure 19, Figure 20, Figure 26, Figure 27, Figure 29 , The method corresponding to the terminal device in Figure 31.
  • An embodiment of the present application provides a chip system, which includes a processor for a communication device to execute the method corresponding to the first network element in FIG. 14, FIG. 21, FIG. 23, FIG. 24, FIG. 25, and FIG. 26, Or, perform the method corresponding to the RAN network element in Figure 19, Figure 20, Figure 27, Figure 29, and Figure 31, or perform the method corresponding to the UPF network element in Figure 19, Figure 20, Figure 27, Figure 29, and Figure 31 method.
  • the embodiment of the present application provides a chip system, which includes a processor, which is used by a communication device to execute FIG. 15, FIG. 19, FIG. 20, FIG. 21, FIG. 23, FIG. 24, FIG. 25, FIG. 26, and FIG. 27.
  • the embodiment of the present application provides a chip system, which includes a processor, which is used by a communication device to execute FIG. 16, FIG. 19, FIG. 20, FIG. 21, FIG. 22, FIG. 24, FIG. 25, FIG. 27, and FIG. 29.
  • the embodiment of the present application provides a chip system, the chip system includes a processor, which is used for a communication device to execute the method corresponding to the terminal device in FIG. 17, FIG. 19, FIG. 20, FIG. 26, FIG. 27, FIG. 29, and FIG. 31 .
  • the above chip system also includes a memory, which is used to store necessary program instructions and data for the terminal device.
  • the chip system may include a chip, an integrated circuit, or may include a chip and other discrete devices, which is not specifically limited in the embodiment of the present application.
  • the communication device, chip, computer storage medium, computer program product, or chip system provided in the present application are all used to execute the method described above. Therefore, the beneficial effects that can be achieved can refer to the implementation manners provided above. The beneficial effects in the process will not be repeated here.
  • the processor involved in the embodiment of the present application may be a chip.
  • it can be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), or a central processing unit.
  • the central processor unit (CPU) can also be a network processor (NP), a digital signal processing circuit (digital signal processor, DSP), or a microcontroller (microcontroller unit, MCU) It can also be a programmable logic device (PLD) or other integrated chips.
  • NP network processor
  • DSP digital signal processor
  • MCU microcontroller unit
  • PLD programmable logic device
  • the memory involved in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), and electrically available Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (RAM), which is used as an external cache.
  • RAM random access memory
  • static random access memory static random access memory
  • dynamic RAM dynamic RAM
  • DRAM dynamic random access memory
  • synchronous dynamic random access memory synchronous DRAM, SDRAM
  • double data rate synchronous dynamic random access memory double data rate SDRAM, DDR SDRAM
  • enhanced synchronous dynamic random access memory enhanced SDRAM, ESDRAM
  • synchronous connection dynamic random access memory serial DRAM, SLDRAM
  • direct rambus RAM direct rambus RAM
  • the size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not correspond to the embodiments of the present application.
  • the implementation process constitutes any limitation.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection between devices or units through some interfaces, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or includes one or more data storage devices such as servers, data centers, etc. that can be integrated with the medium.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).

Landscapes

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

Abstract

本公开提供了一种数据包处理方法和装置，涉及通信领域，用于防止进行传输优化时终端设备丢包。数据包处理方法包括：第一网元接收第一指示信息和第一数据包，第一数据包对应第一多播业务，第一数据包的目的互联网协议IP地址为第一终端设备的IP地址；第一网元根据第一指示信息和第一数据包，发送第二数据包，第二数据包的目的IP地址为第一多播业务的公共IP地址，公共IP地址用于向至少两个终端设备传输第一多播业务的数据；其中，第一指示信息用于指示使用第一多播业务的公共IP地址传输第一多播业务的数据。

Description

数据包处理方法和装置 技术领域
本申请涉及通信领域，尤其涉及一种数据包处理方法和装置。
背景技术
在第五代(5th generation，5G)通信系统中，应用功能(application function，AF)或应用服务器(application server，AS)可以通过单播或多播方式，经由用户面功能(user plane function，UPF)网元和无线接入网(wireless access network，RAN)网元向终端设备发送应用数据。
当AS通过单播方式向多个终端设备发送承载相同内容的报文时，如果UPF网元或RAN网元检测到这些报文中内容相同时，可以进行传输优化，即只传输该内容的一份拷贝。由RAN网元为这些终端设备分配一个组无线网络临时标识(radio network temporary identity，RNTI)，在该组RNTI对应的无线空口资源上发送其中第一终端设备的服务质量(quality of service，QoS)流中的数据包，即数据包的目的互联网协议(internet protocol，IP)地址为第一终端设备的IP地址。这样，虽然这些终端设备可以在空口上通过“(伪)广播”的方式接收到相同的数据包，但是对于除了第一终端设备以外的终端设备来说，由于接收的数据包的目的IP地址不是本终端设备的IP地址，因此会将该数据包丢弃，而不会将数据包中的应用数据载荷传递给上层的应用层。
发明内容
本申请实施例提供一种数据包处理方法和装置，用于防止进行传输优化时终端设备丢包。
为达到上述目的，本申请的实施例采用如下技术方案：
第一方面，提供了一种数据包处理方法，包括：第一网元接收第一指示信息和第一数据包，第一数据包对应第一多播业务，第一数据包的目的互联网协议IP地址为第一终端设备的IP地址；第一网元根据第一指示信息和第一数据包，发送第二数据包，第二数据包的目的IP地址为第一多播业务的公共IP地址，公共IP地址用于向至少两个终端设备传输第一多播业务的数据；其中，第一指示信息用于指示使用第一多播业务的公共IP地址传输第一多播业务的数据。
本申请实施例提供的数据包处理方法，第一网元接收第一指示信息和第一数据包，第一指示信息可以用于指示使用公共IP地址传输第一多播业务的数据，第一数据包承载第一终端设备的第一多播业务，第一数据包的目的IP地址为第一终端设备的IP地址。第一网元根据第一指示信息和第一数据包，发送第二数据包，第二数据包的目的IP地址为第一多播业务的公共IP地址。终端设备接收到第二数据包后，根据其目的IP地址为公共IP地址可以确定接受第二数据包，不会丢弃第二数据包，可以防止进行传输优化时终端设备丢包。
在一种可能的实施方式中，该方法还包括：第一网元接收第三数据包，第三数据 包对应第一多播业务，第三数据包的目的IP地址为第二终端设备的IP地址，第三数据包承载的内容与第一数据包承载的内容相同；第一网元丢弃第三数据包。该实施方式中，第一网元通过丢弃与第一数据包内容相同的数据包，减少占用带宽。
在一种可能的实施方式中，第一网元接收第一指示信息包括：第一网元从会话管理功能网元接收第一指示信息。
在一种可能的实施方式中，第一指示信息包括第一多播业务的标识信息和公共IP地址之间的关联关系。通过第一数据包中的第一多播业务的标识信息，第一网元可以确定对第一数据包进行传输优化，并生成目的IP地址为对应公共IP地址的数据包。
在一种可能的实施方式中，第一指示信息包括第一多播业务的标识信息，而不包括公共IP地址，方法还包括：第一网元从会话管理功能网元接收公共IP地址，或者，第一网元根据第一多播业务的标识信息，获得公共IP地址。
在一种可能的实施方式中，第一网元为用户面功能网元；第一网元根据第一指示信息和第一数据包，发送第二数据包，包括：第一网元根据第一指示信息和第一数据包，向接入网网元发送第二数据包。
在一种可能的实施方式中，第一网元为接入网网元；第一网元根据第一指示信息和第一数据包，发送第二数据包，包括：第一网元根据第一指示信息和第一数据包，采用空口组播方式发送第二数据包。
第二方面，提供了一种数据包处理方法，包括：获取第一多播业务的标识信息；根据第一多播业务的标识信息，向第一网元发送第一指示信息；其中，第一指示信息用于指示使用公共IP地址传输第一多播业务的数据，公共IP地址用于向至少两个终端设备传输第一多播业务的数据。
本申请实施例提供的数据包处理方法，提供了第一网元如何获取第一指示信息的方法，使得第一网元对第一多播业务的第一数据包进行传输优化时，可以根据第一指示信息和第一数据包发送第二数据包，第一数据包的目的IP地址为第一终端设备的IP地址，第二数据包的目的IP地址为第一多播业务的公共IP地址。终端设备接收到第二数据包后，根据其目的IP地址为公共IP地址可以确定接受第二数据包，不会丢弃第二数据包，可以防止进行传输优化时终端设备丢包。
在一种可能的实施方式中，该方法还包括：获取第一指示信息。
在一种可能的实施方式中，该方法还包括：向第一网元发送公共IP地址。
在一种可能的实施方式中，第一指示信息包括公共IP地址。
在一种可能的实施方式中，该方法还包括：生成公共IP地址；或者，从应用服务器接收公共IP地址。
在一种可能的实施方式中，获取第一多播业务的标识信息，包括：生成第一多播业务的标识信息，或者，从应用服务器接收第一多播业务的标识信息。
第三方面，提供了一种数据包处理方法，包括：获取第一多播业务对应的用户面功能网元的用户面互联网协议IP地址和用户面功能网元的用户面端口号；使用用户面IP地址和用户面端口号，向用户面功能网元发送第一数据包和第二数据包，其中，第一数据包和第二数据包均包括第一多播业务的第一数据，第一数据包的目的IP地址为第一终端设备的IP地址，第二数据包的目的IP地址为第二终端设备的IP地址。
本申请实施例提供的数据包处理方法，在第一多播业务的标识信息为第一多播业务对应的UPF网元的用户面IP地址和UPF网元的用户面端口号时，应用服务器使用所述用户面IP地址和所述用户面端口号向UPF网元发送第一多播业务的至少两个数据包，UPF网元根据所述用户面IP地址和所述用户面端口号即可以确定所述至少两个数据包对应第一多播业务，从而可以对所述至少两个数据包进行传输优化。
第四方面，提供了一种数据包处理方法，包括：终端设备接收第一数据包，第一数据包对应第一多播业务，第一数据包的目的互联网协议IP地址为第一多播业务的公共IP地址，公共IP地址用于向至少两个终端设备传输第一多播业务的数据；根据第一数据包得到第二数据包，第二数据包的目的IP地址为终端设备的IP地址。
本申请实施例提供的数据包处理方法，终端设备接收到第一数据包后，根据其目的IP地址为公共IP地址可以确定接受第一数据包，不会丢弃第一数据包，可以防止进行传输优化时终端设备丢包。
在一种可能的实施方式中，该方法还包括：终端设备接收公共IP地址。
在一种可能的实施方式中，该方法还包括：终端设备向会话管理功能网元发送第一消息，第一消息包括第一多播业务的标识信息或者公共IP地址，第一消息用于请求第一多播业务的数据。
第五方面，提供了一种通信装置，包括：收发模块，用于接收第一指示信息和第一数据包，第一数据包对应第一多播业务，第一数据包的目的互联网协议IP地址为第一终端设备的IP地址；收发模块，还用于根据第一指示信息和第一数据包，发送第二数据包，第二数据包的目的IP地址为第一多播业务的公共IP地址，公共IP地址用于向至少两个终端设备传输第一多播业务的数据；其中，第一指示信息用于指示使用第一多播业务的公共IP地址传输第一多播业务的数据。
在一种可能的实施方式中，还包括处理模块，收发模块，还用于接收第三数据包，第三数据包对应第一多播业务，第三数据包的目的IP地址为第二终端设备的IP地址，第三数据包承载的内容与第一数据包承载的内容相同；处理模块，用于丢弃第三数据包。
在一种可能的实施方式中，收发模块，具体用于从会话管理功能网元接收第一指示信息。
在一种可能的实施方式中，第一指示信息包括第一多播业务的标识信息和公共IP地址之间的关联关系。
在一种可能的实施方式中，第一指示信息包括第一多播业务的标识信息，而不包括公共IP地址，通信装置还包括处理模块：收发模块，还用于从会话管理功能网元接收公共IP地址，或者，处理模块，用于根据第一多播业务的标识信息，获得公共IP地址。
在一种可能的实施方式中，通信装置为UPF；收发模块，具体用于：根据第一指示信息和第一数据包，向接入网网元发送第二数据包。
在一种可能的实施方式中，通信装置为接入网网元；收发模块，具体用于：根据第一指示信息和第一数据包，采用空口组播方式发送第二数据包。
第六方面，提供了一种通信装置，包括：处理模块，用于获取第一多播业务的标 识信息；收发模块，用于根据第一多播业务的标识信息，向第一网元发送第一指示信息；其中，第一指示信息用于指示使用公共IP地址传输第一多播业务的数据，公共IP地址用于向至少两个终端设备传输第一多播业务的数据。
在一种可能的实施方式中，处理模块，还用于：获取第一指示信息。
在一种可能的实施方式中，收发模块，还用于：向第一网元发送公共IP地址。
在一种可能的实施方式中，第一指示信息包括公共IP地址。
在一种可能的实施方式中，处理模块，还用于生成公共IP地址；或者，收发模块，还用于从应用服务器接收公共IP地址。
在一种可能的实施方式中，处理模块，还用于生成第一多播业务的标识信息，或者，收发模块，还用于从应用服务器接收第一多播业务的标识信息。
第七方面，提供了一种通信装置，包括：处理模块，用于获取第一多播业务对应的用户面功能网元的用户面互联网协议IP地址和用户面功能网元的用户面端口号；收发模块，用于使用用户面IP地址和用户面端口号，向用户面功能网元发送第一数据包和第二数据包，其中，第一数据包和第二数据包均包括第一多播业务的第一数据，第一数据包的目的IP地址为第一终端设备的IP地址，第二数据包的目的IP地址为第二终端设备的IP地址。
第八方面，提供了一种通信装置，包括：收发模块，用于接收第一数据包，第一数据包对应第一多播业务，第一数据包的目的互联网协议IP地址为第一多播业务的公共IP地址，公共IP地址用于向至少两个终端设备传输第一多播业务的数据；处理模块，用于根据第一数据包得到第二数据包，第二数据包的目的IP地址为终端设备的IP地址。
在一种可能的实施方式中，收发模块，还用于接收公共IP地址。
在一种可能的实施方式中，收发模块，还用于向会话管理功能网元发送第一消息，第一消息包括第一多播业务的标识信息或者公共IP地址，第一消息用于请求第一多播业务的数据。
第九方面，提供了一种通信装置，所述通信装置包括处理器、存储器和收发器，所述处理器与存储器耦合，当所述处理器执行存储器中的计算机程序或指令时，执行如第一方面及其任一实施方式所述的方法，或者，如第二方面及其任一实施方式所述的方法，或者，如第三方面及其任一实施方式所述的方法，或者，如第四方面及其任一实施方式所述的方法。
第十方面，提供了一种芯片，包括：处理器和接口，用于从存储器中调用并运行所述存储器中存储的计算机程序，执行如第一方面及其任一实施方式所述的方法，或者，如第二方面及其任一实施方式所述的方法，或者，如第三方面及其任一实施方式所述的方法，或者，如第四方面及其任一实施方式所述的方法。
第十一方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当该指令在计算机或处理器上运行时，使得计算机或处理器，执行如第一方面及其任一实施方式所述的方法，或者，如第二方面及其任一实施方式所述的方法，或者，如第三方面及其任一实施方式所述的方法，或者，如第四方面及其任一实施方式所述的方法。
第十二方面，提供了一种包含指令的计算机程序产品，当该指令在计算机或处理器上运行时，使得计算机或处理器，执行如第一方面及其任一实施方式所述的方法，或者，如第二方面及其任一实施方式所述的方法，或者，如第三方面及其任一实施方式所述的方法，或者，如第四方面及其任一实施方式所述的方法。
第五方面至第十二方面的技术效果可以参照第一方面至第四方面的各种可能实施方式所述内容。
附图说明
图1为本申请实施例提供的一种通信系统的架构示意图；
图2为本申请实施例提供的一种终端设备的结构示意图；
图3为本申请实施例提供的一种基站的结构示意图；
图4为本申请实施例提供的一种网络设备的结构示意图；
图5为本申请实施例提供的一种QoS流的示意图；
图6为本申请实施例提供的一种应用层单播网络层单播的示意图；
图7为本申请实施例提供的一种应用层组播网络层单播的示意图；
图8为本申请实施例提供的一种应用层组播网络层广播的示意图；
图9为本申请实施例提供的另一种应用层组播网络层广播的示意图；
图10为本申请实施例提供的一种应用服务器与UPF网元之间组播传输的示意图；
图11为本申请实施例提供的一种UFP网元进行传输优化的示意图；
图12为本申请实施例提供的一种RAN网元进行传输优化的示意图；
图13为本申请实施例提供的一种UPF网元和RAN网元都进行传输优化的示意图；
图14为本申请实施例提供的一种数据包处理方法的流程示意图一；
图15为本申请实施例提供的一种数据包处理方法的流程示意图二；
图16为本申请实施例提供的一种数据包处理方法的流程示意图三；
图17为本申请实施例提供的一种数据包处理方法的流程示意图四；
图18为本申请实施例提供的一种协议栈的示意图；
图19为本申请实施例提供的一种数据包处理方法的流程示意图五；
图20为本申请实施例提供的一种数据包处理方法的流程示意图六；
图21为本申请实施例提供的一种数据包处理方法的流程示意图七；
图22为本申请实施例提供的一种数据包处理方法的流程示意图八；
图23为本申请实施例提供的一种数据包处理方法的流程示意图九；
图24为本申请实施例提供的一种数据包处理方法的流程示意图十；
图25为本申请实施例提供的一种数据包处理方法的流程示意图十一；
图26为本申请实施例提供的一种数据包处理方法的流程示意图十二；
图27为本申请实施例提供的一种数据包处理方法的流程示意图十三；
图28为本申请实施例提供的一种在UPF网元生成第二数据包的示意图；
图29为本申请实施例提供的一种数据包处理方法的流程示意图十四；
图30为本申请实施例提供的一种在RAN网元生成第二数据包的示意图一；
图31为本申请实施例提供的一种数据包处理方法的流程示意图十五；
图32为本申请实施例提供的一种在RAN网元生成第二数据包的示意图二；
图33为本申请实施例提供的一种通信装置的结构示意图；
图34为本申请实施例提供的另一种通信装置的结构示意图；
图35为本申请实施例提供的又一种通信装置的结构示意图；
图36为本申请实施例提供的再一种通信装置的结构示意图。
具体实施方式
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
本申请实施例中，“/”表示该符号前后两者是并列关系。
本申请实施例既可以应用于时分双工(time division duplexing，TDD)的场景，也可以适用于频分双工(frequency division duplexing，FDD)的场景，不予限制。
本申请实施例依托无线通信网络中5G网络的场景进行说明，应当指出的是，本申请实施例中的方案还可以应用于其他无线通信网络中，相应的名称也可以用其他无线通信网络中的对应功能的名称进行替代。
图1提供了一种通信系统架构，包括：终端设备101、无线接入网((radio)access network，(R)AN)网元102、用户面功能(user plane function，UPF)网元103、数据网络(data network，DN)104、接入和移动性管理功能(access and mobility management function，AMF)网元105、会话管理功能(session management function，SMF)网元106、策略控制网元(policy control function，PCF)网元107、统一数据管理网元(unified data management，UDM)网元108以及应用功能(application function，AF)网元109。
需要说明的是，图1中的各个网元之间的接口名字只是一个示例，具体实现中接口名字可能为其他名字，不予限制。例如，终端设备101与AMF网元105之间的接口可以为N1接口，RAN网元102与AMF网元105之间的接口可以为N2接口，RAN网元102与UPF网元103之间的接口可以为N3接口，UPF网元103与SMF网元106之间的接口可以为N4接口，PCF网元107与AF网元109之间的接口可以为N5接口，UPF网元103与DN 104之间的接口可以为N6接口，SMF网元106与PCF网元107之间的接口可以为N7接口，AMF网元105与UDM网元108之间的接口可以为N8接口，UPF网元103与UPF网元103之间的接口可以为N9接口，SMF网元106与UDM网元108之间的接口可以为N10接口，AMF网元105与SMF网元106之间的接口可以为N11接口，PCF网元107与UDM网元108之间的接口可以为N25接口。
终端设备101可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其他处理设备；还可以包括用户单元(subscriber unit)、蜂窝电话(cellular phone)、智能电话(smart phone)、无线数据卡、个人数字助理(personal digital assistant，PDA)电脑、平板型电脑、无线调制解调器(modem)、手持设备(handheld)、膝上型电脑(laptop computer)、无绳电话(cordless phone)或者无线本地环路(wireless local loop，WLL)台、机器类型通信(machine type communication，MTC)终端、用户设备(user equipment，UE)、移 动台(mobile station，MS)、终端设备(terminal device)或者中继用户设备等。其中，中继用户设备可以是5G家庭网关(residential gateway，RG)。为方便描述，上面提到的设备可以统称为终端设备。
以终端设备101为手机为例，对终端设备101的硬件架构进行说明。如图2所示，终端设备200可以包括：存储器120和处理器180。进一步地，终端设备200还可以包括：射频(radio frequency，RF)电路100、其他输入设备130、显示屏140、传感器150、音频电路160、I/O子系统170、以及电源190等部件。本领域技术人员可以理解，图中所示的手机的结构并不构成对手机的限定，可以包括比图示更多或者更少的部件，或者组合某些部件，或者拆分某些部件，或者不同的部件布置。本领域技术人员可以理解显示屏140属于用户界面(user interface，UI)，显示屏140可以包括显示面板141和触摸面板142。尽管未示出，手机还可以包括摄像头、蓝牙模块等功能模块或器件，在此不再赘述。
进一步地，处理器180分别与RF电路100、存储器120、音频电路160、I/O子系统170以及电源190连接。I/O子系统170分别与其他输入设备130、显示屏140、传感器150连接。其中，RF电路100可用于在收发信息或通话过程中对信号的接收和发送，特别地，接收来自网络设备的下行信息后，发送给处理器180处理。存储器120可用于存储软件程序以及模块。处理器180通过运行存储在存储器120的软件程序以及模块，从而执行手机的各种功能应用以及数据处理，例如执行本申请实施例中终端设备的方法和功能。其他输入设备130可用于接收输入的数字或字符信息，以及产生与手机的用户设置以及功能控制有关的键盘信号输入。显示屏140可用于显示由用户输入的信息或提供给用户的信息以及手机的各种菜单，还可以接受用户输入。传感器150可以为光传感器、运动传感器或者其他传感器。音频电路160可提供用户与手机之间的音频接口。I/O子系统170用来控制输入输出的外部设备，外部设备可以包括其他设备输入控制器、传感器控制器、显示控制器。处理器180是终端设备200的控制中心，利用各种接口和线路连接整个手机的各个部分，通过运行或执行存储在存储器120内的软件程序和/或模块，以及调用存储在存储器120内的数据，执行手机的各种功能和处理数据，从而对手机进行整体监控。电源190(比如电池)用于给上述各个部件供电，优选的，电源可以通过电源管理系统与处理器180逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗等功能。在本申请实施例中终端设备101可以通过RF电路100从RAN网元102接收信号或向RAN网元102发送信号。
RAN网元102，用于向终端设备101提供无线接入服务。RAN网元102包括但不限于eNodeB、无线保真(wireless fidelity，Wi-Fi)接入点(access point，AP)、全球微波互联接入(worldwide interoperability for microwave access，WiMAX)基站、新空口(new radio，NR)等。RAN网元102可以包括单RAN网元，或者包括双RAN网元。例如，双RAN网元包括主无线接入网(master radio access network，M-RAN)网元和辅无线接入网(secondary radio access network，S-RAN)网元。单RAN网元或者双RAN网元可以与UPF网元通过双隧道传输报文。
以RAN网元102为基站为例，对RAN网元102的硬件架构进行说明。如图3所示，基站300可以包括室内基带处理单元(building baseband unit，BBU)301和远端 射频模块(remote radio unit，RRU)302，RRU 302和天馈系统(即天线)337连接，BBU 301和RRU 302可以根据需要拆开使用。其中，BBU 301可以包括处理器331、存储器332及总线系统333，BBU 301的处理器331、存储器332通过总线系统333相互连接。上述总线系统可以是外设部件互连标准总线或扩展工业标准结构总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图中仅用一条线表示，但并不表示仅有一根总线或一种类型的总线。RRU 302可以包括RF电路334，基站300还可以包括光纤335、同轴电缆336。RRU 302中的RF电路334与BBU 301之间通过光纤335相互连接，RRU 302中的RF电路334与天线337之间通过同轴电缆336相互连接。
基站可以包括各种形式的基站，例如：宏基站，微基站(也称为小站)，中继站，接入点等。本申请实施例所述的RAN网元102用于在终端设备101与核心网设备之间传输数据。
UPF网元103，用于对用户报文进行处理，例如转发、计费等。
DN 104，用于为用户提供数据传输服务，例如提供IP多媒体业务(IP multi-media service，IMS)的DN、提供互联网(Internet)业务的DN等。
AMF网元105，用于移动网络中的移动性管理，例如用户位置更新、用户注册网络、用户切换等。
SMF网元106，用于移动网络中的会话管理，例如会话建立、修改、释放等。例如，为用户分配IP地址，选择提供报文转发功能的UPF网元等。
PCF网元107，用于向终端设备101、RAN网元102、UPF网元103、SMF网元106提供策略，例如QoS策略、切片选择策略等。
UDM网元108，用于存储用户数据，例如签约信息、鉴权/授权信息。
AF网元109，于向第三代合作伙伴计划(3rd generation partnership project，3GPP)网络提供业务，与PCF网元107之间交互以进行策略控制等。
基于图1所示的网络架构，终端设备101可以通过建立终端设备101、RAN网元102、UPF网元103到DN 104之间的协议数据单元(protocol data unit，PDU)会话(session)来访问DN 104。
其中，UPF网元103、AMF网元105、SMF网元106、PCF网元107、UDM网元108这些网元可以统称为核心网网元。下面以一种网络设备为例，对这些核心网网元的结构进行说明，本申请实施例并不限定各核心网网元必须具有如图4中所示的单元或器件，可以具有更多或更少的单元或器件。
如图4所示，网络设备400可以包括至少一个处理器401、通信线路402、存储器403以及至少一个通信接口404。处理器401可以是通用中央处理器(central processing unit，CPU)、微处理器、特定应用集成电路(application-specific integrated circuit，ASIC)或一个或多个用于控制本申请方案程序执行的集成电路。通信线路402可以包括一通路，在上述组件之间传送信息。通信接口404，可以使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网、无线接入网(radio access network，RAN)、无线局域网(wireless local area networks，WLAN)等。存储器403可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备、 随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器403可以是独立存在，通过通信线路402与处理器相连接。存储器403也可以和处理器401集成在一起。其中，存储器403用于存储执行本申请方案的计算机执行指令(可以称之为应用程序代码)。处理器401用于执行存储器403中存储的计算机执行指令，从而实现本申请下述实施例提供的方法中各核心网网元的动作。
首先对本申请实施例涉及的一些概念进行描述：
应用和业务：
应用(application，APP)，是应用程序或应用软件的简称，是实现了特定功能的任务的程序。在终端设备上运行的应用程序可以称为应用客户端。应用客户端通过网络从应用服务器获取业务，并完成与用户的交互任务。运行在应用业务提供商(application service provider，ASP)的网络设备上的应用程序可以称为应用服务器(或服务器应用)。应用服务器通过各种协议把业务逻辑提供给应用客户端。一个应用可以提供一种或多种业务。其中，多播应用可以提供多播业务，多播业务可以包含不同的内容、频道、服务等，本申请不作限定。例如，终端设备上运行的视频直播APP可以提供不同的直播内容，例如体育赛事直播、娱乐节目直播、购物直播等，用户可以通过该APP进行观看。
本申请实施例中涉及的应用服务器不仅可以执行AF网元109控制面的功能，还可以执行用户面的功能，例如提供本申请涉及的第一多播业务。
在5G通信系统中，一个应用可以通过三元组或应用标识符标识来标识，三元组或应用标识符作为应用的描述器(application descriptor)。三元组包括传输协议(例如传输控制协议(transmission control protocol，TCP)、用户数据报协议(user datagram protocol，UDP))、服务器侧IP地址及其端口号。
一个应用对应的IP数据流可以通过五元组来标识，五元组包括传输协议、源IP地址及其端口号、目标IP地址及其端口号。
一个业务可以通过业务的标识信息来标识。业务的标识信息可以为以下任意一种：应用标识、三元组、业务标识符以及UPF网元的用户面IP地址和UPF网元的用户面端口号。
具体的，可以通过业务标识符来标识一个业务，业务标识符包括例如业务ID、服务ID(serviceID)、(临时)群组标识等。或者，当一个应用仅提供一个业务时，也可以通过应用的三元组或应用标识符来标识一个业务。或者，当一个应用提供多个业务时，可以通过三元组或应用标识符结合公共IP地址来标识一个业务。或者，可以通过UPF网元的用户面IP地址和UPF网元的用户面端口号来标识一个业务。
其中，公共IP地址为一个IP单播地址或IP多播地址，用于向一组终端设备传输业务的数据。
该公共IP地址可以由应用服务器生成，或者由SMF网元或者UPF网元生成。
例如，应用服务器可以使用终端设备的单播IP地址封装一个业务的数据包并向终端设备发送该数据包，在经过UPF网元或RAN网元时，该数据包的目的IP地址由终端设备的单播IP地址被替换为公共IP地址，然后继续发送给终端设备。终端设备在接收到该数据包之后，根据公共IP地址确定自己是该数据包的接收者，不会丢弃该数据包，根据该数据包的端口号将数据包递交给上层的应用客户端。
或者，应用服务器和终端设备上的应用客户端也可以预先协商建立两条套接字(socket)连接，其中一条套接字连接绑定该公共IP地址；或者应用服务器和终端设备上的应用客户端之间一个套接字连接对应的两条IP连接，其中一条IP连接的终端设备侧IP地址对应该公共IP地址。
对于UPF网元的用户面IP地址和UPF网元的用户面端口号来说，主要用于应用服务器和UPF网元之间标识一个业务。用户面IP地址和用户面端口号可以由SMF网元生成后发送给UPF网元，或者，由SMF网元从UPF网元请求得到。应用服务器可以从SMF网元获取业务的业务标识符以及对应的用户面IP地址和用户面端口号，从而将业务的业务标识符与UPF网元的用户面IP地址和UPF网元的用户面端口号一一对应。
应用服务器可以使用UPF网元的用户面IP地址和UPF网元的用户面端口号封装该业务的与终端设备对应的数据包，并向UPF网元发送该业务的与终端设备对应的数据包(即IP in IP或IP隧道的方式)，UPF网元根据用户面IP地址和用户面端口号确定对应的业务。该业务的与终端设备对应的数据包指该业务的应用服务器发送给该终端设备的数据包。
QoS流(flow)映射规则：
QoS流是PDU会话中QoS差异化的最细粒度。在5G通信系统中，通过PDU会话建立过程或PDU会话修改过程为终端设备建立QoS流。
PDU会话中的每个QoS流可以通过QoS流标识(QoS flow ID，QFI)来唯一标识。QFI可以由SMF网元动态分配，也可以为预设的5G服务质量标识(5G QoS identifier，5QI)。在一个PDU会话中具有相同QFI的用户面数据流(可以简称数据流)适用相同的QoS流映射规则(例如调度规则、准入门限等)。具体的，QFI可以承载在N3接口和N9接口的GPRS隧道协议用户面(GPRS tunnelling protocol user plane，GTP-U)报文的头部中。
终端设备、RAN网元和UPF网元可以通过以下方式获取QoS流映射规则：
对于终端设备来说，SMF网元可以通过AMF网元及N1接口向终端设备发送一个或多个QoS流映射规则，可选的，还可以向终端设备发送与QoS流映射规则相关联的QoS参数。或者，终端设备通过应用反射QoS控制派生得到QoS流映射规则。如图5所示，终端设备可以根据QoS流映射规则在对应的无线空口资源上从RAN网元接收QoS流，或者，向RAN网元发送QoS流。
对于RAN网元来说，SMF网元可以通过AMF网元及N2接口向RAN网元发送QoS配置文件(QoS profile)；或者，RAN网元中预先配置QoS配置文件。其中，QoS配置文件中包括QoS流映射规则。如图5所示，RAN网元可以根据QoS流映射规则 在对应的无线空口资源上从终端设备接收QoS流，或者，向终端设备发送QoS流。另外，RAN网元可以根据上述QoS流映射规则从UPF网元接收QoS流，或者，向UPF网元发送QoS流。
对于UPF网元来说，SMF网元可以通过N4接口向UPF网元配置一个或多个上行和下行包检测规则(packet detection rule，PDR)，该PDR即为QoS流映射规则。如图5所示，UPF网元可以根据上述QoS流映射规则从RAN网元接收QoS流，或者，向RAN网元发送QoS流。
第一多播业务在应用层和网络层的传输方式：
应用层的传输方式指的是应用服务器在封装和发送应用数据包的方式。应用服务器可以使用单播方式向应用业务对应的应用客户端发送应用业务数据，即应用服务器使用该应用客户端的IP地址(单播IP地址)封装应用业务数据，向该应用客户端发送应用业务数据，同一应用业务对应的不同应用客户端接收到的应用业务数据可以相同也可以不同。应用服务器还可以使用多播方式向应用业务对应的应用客户端发送应用业务数据，即应用服务器使用组播地址封装应用业务数据，通过IP组播的技术发送应用业务数据，该应用业务对应的应用客户端都可以接受到相同的应用业务数据。
网络层的传输方式指的是移动通信网络内部的传输应用业务数据的方式。可以使用移动通信网络的单播QoS流(unicast QoS flow)和空口单播信道向该应用业务的应用客户端所在的终端设备发送应用业务的数据，即该应用业务对应的应用客户端所在的终端设备分别与UPF网元建立单播QoS流，UPF网元向通过该终端设备独自的单播QoS流发送应用业务数据，每个该应用业务对应的应用客户端通过其所在的终端设备接收应用业务数据，接收到的应用业务数据可以相同也可以不同。在网络层，还可以使用移动通信网络的组播QoS流和空口组播信道向该应用业务的应用客户端所在的终端设备发送应用业务的数据，即在同一个基站下的该应用业务对应的应用客户端所在的终端设备与该基站建立一个空口多播组，该基站和UPF网元使用一条组播QoS流(例如，可以是公共N3 QoS流；或者，可以是该基站下某个该应用业务对应的应用客户端所在的终端设备接收该应用业务的单播QoS流，因为这个单播QoS流中的数据会发给多个终端设备，所以这里可以称为组播QoS流，或伪组播QoS流)，即UPF网元通过一条QoS流向一个基站发送应用业务数据，该基站使用组RNTI为该基站下该应用业务对应的应用客户端所在的终端设备发送应用业务数据，该应用业务对应的应用客户端都可以接受到相同的应用业务数据。
具体对于应用业务数据从应用服务器传输到应用客户端，可以有以下方式：
方式1：应用层单播，网络层单播
即应用服务器通过应用层单播方式向应用客户端发送应用业务数据，移动通信网络通过网络层单播方式向终端设备发送应用业务数据。
如图6所示，在该方式中，应用服务器向该应用业务的应用客户端所在的终端设备(例如终端设备1)发送的第一数据包的目的IP地址为该终端设备(例如终端设备1)的IP地址(例如IP1)，应用服务器通过单播的方式将第一数据包发送给UPF网元，UPF网元通过单播QoS流将第一数据包发送给RAN网元，RAN网元通过空口的单播信道将第一数据包发送给该终端设备(例如终端设备1)。
方式2：应用层多播，网络层单播
即应用服务器通过应用层多播方式向应用客户端发送应用业务数据，移动通信网络通过网络层单播方式向终端设备发送应用业务数据。
如图7所示，在该方式中，应用服务器与终端设备已经预先商定使用第一组播IP地址(例如IPm)传输数据，UPF网元已经加入第一组播IP地址标识的组播组，该组播组为第一组播业务的组播组。应用服务器向该终端设备(例如终端设备1)发送的第一数据包的目的IP地址为第一组播IP地址(例如IPm)。UPF网元将接收到的一份应用业务数据拷贝多份，通过单播QoS流将第一数据包发送给RAN网元，RAN网元通过空口的单播信道将第一数据包发送给该该应用业务的应用客户端所在的终端设备(例如终端设备1)。
方式3：应用层多播，网络层多播
即应用服务器通过应用层多播方式向应用客户端发送应用业务数据，移动通信网络通过网络层多播方式向终端设备发送应用业务数据。
如图8所示，在该方式中，应用服务器和多个终端设备已经预先商定使用第一组播IP地址(例如IPm)传输数据，UPF网元已经加入到第一组播IP地址。应用服务器向这些终端设备(例如终端设备1)发送的第一数据包的目的IP地址为第一组播IP地址(例如IPm)。UPF网元通过与RAN网元之间的公共组播隧道将第一数据包发给RAN网元，RAN网元通过空口的多播信道发送第一数据包，配置该多播信道的多个终端设备都可以接收到该第一数据包。
或者，如图9所示，在该方式中，应用服务器和各个终端设备已经预先商定使用第一组播IP地址(例如IPm)传输数据，UPF网元已经加入到第一组播IP地址。应用服务器向各个终端设备(例如终端设备1)发送的第一数据包的目的IP地址为第一组播IP地址(例如IPm)。UPF网元将第一数据包封装在第一组播数据包中并通过一个QoS流将第一组播数据包发送给RAN网元，其中，第一组播数据包的目的IP地址为第二组播IP地址(例如IPn)，第二组播IP地址为多个RAN网元已经加入的组播IP地址。RAN网元在接收到第一组播数据包后，除去组播包头得到第一数据包，通过空口的多播信道发送第一数据包，配置该多播信道的终端设备都可以接收到该第一数据包。
需要说明的是，对于方式2和方式3中的应用服务器和UPF网元之间传输的组播数据包来说，如图10所示，应用服务器可以将第一数据包封装在第二组播数据包中并通过N6隧道将第二组播数据包发送给UPF网元。其中，第二组播数据包的目的IP地址为第三组播IP地址(例如IPo)，其中，多个UPF网元已经加入第三组播IP地址标识的组播组，该组播组为第一组播业务的组播组。UPF网元在接收到第二组播数据包后，除去组播包头得到第一数据包，然后按照方式2或方式3中的方式发送给RAN网元。
针对方式1应用层单播且网络层单播的情况，如果网络设备向多个终端设备传输的应用业务数据相同(例如多个终端设备通过视频播放APP观看体育赛事直播)，为了避免浪费网络资源和无线空口资源，可以在UPF网元和/或RAN网元对数据包进行传输优化(或称传输合并)，从而节省网络资源或无线空口资源，即可以采用下面的 方式4。
方式4：应用层单播，网络层多播
即应用服务器通过应用层单播方式向应用客户端发送应用业务数据，移动通信网络通过网络层多播方式向终端设备发送应用业务数据。
在该方式中，应用服务器向该应用业务的应用客户端所在的终端设备(例如终端设备1)发送的第一数据包的目的IP地址为该终端设备(例如终端设备1)的IP地址(例如IP1)，应用服务器将多个终端设备的第一数据包均发送给UPF网元。UPF网元选择其中的一个终端设备的第一数据包，通过网络层多播的方式发送给所述多个终端设备，而对于未选择的其他终端设备的第一数据包做丢弃处理或者不处理。
UFP网元进行传输优化：
UPF网元进行传输优化，指当待传输给多个终端设备的数据包承载的内容相同时，UPF网元可以通过该多个终端设备中一个终端设备对应的QoS流向RAN网元发送该终端设备的数据包，而不处理或者丢弃其他终端设备的数据包，然后，由RAN网元将该终端设备的数据包发送给上述多个终端设备。
示例性的，如图11所示，SMF网元可以为UPF网元配置检测规则，UPF网元根据该检测规则可以确定发送给终端设备1、终端设备2、终端设备3的数据包承载的内容是相同的。例如，来自视频播放APP的发送给终端设备1的数据包、发送给终端设备2的数据包、发送给终端设备3的数据包，其源IP地址均为123.123.123.123，端口号均为123，视频播放APP为多播业务的应用，则UPF网元可以确定这些数据包中承载的内容相同(例如均为体育赛事直播)。UPF网元可以将这三个终端设备的数据包进行传输优化，即只选择其中一个终端设备的数据包进行传输，例如，可以选择终端设备1的数据包进行传输，并通过QoS流1向RAN网元发送终端设备1的数据包，QoS流1可以是终端设备1接收该业务的QoS流，也可以是RAN网元和UPF网元之间与该业务对应的公共QoS流。
RAN网元可以根据SMF网元配置的业务和终端设备的关联关系，确定将QoS流1中的数据包发送给终端设备1、终端设备2、终端设备3。具体地，RAN网元在一个组RNTI对应的无线空口资源上为终端设备1、终端设备2、终端设备3调度从QoS流1中接收到的数据包。这样，终端设备1、终端设备2和终端设备3就可以在空口上接收到了相同的数据包。
其中，本申请实施例涉及的组RNTI为预先(例如在会话建立阶段)配置给多个终端设备(例如终端设备1、终端设备2和终端设备3)的RNTI，组RNTI也可以称为多个终端设备(例如终端设备1、终端设备2和终端设备3)共享的RNTI。
RAN网元进行传输优化：
RAN网元进行传输优化，指RAN网元可以为至少两个终端设备配置一个组RNTI，RAN网元在该组RNTI对应的无线空口资源上向所述至少两个终端设备发送其中一个终端的数据或者来自公共N3隧道上的数据。
示例性的，如图12所示，SMF网元可以为UPF网元配置检测规则，UPF网元根据该检测规则可以确定发送给终端设备1、终端设备2、终端设备3的数据包承载的内容是相同的。例如，终端设备1对应QoS流1，终端设备2对应QoS流2，终端设备 3对应QoS流3，UPF网元可以将QoS流1、QoS流2以及QoS流3中承载的数据包均打上相同的标签(例如，索引(index)或内容标识(content ID))，但UPF网元依然分别使用各个终端设备对应的QoS流发送各个终端设备的数据包给RAN网元，即UPF网元通过QoS流1发送终端设备1的数据包，通过QoS流2发送终端设备2的数据包，通过QoS流3发送终端设备3的数据包。RAN网元可以根据接收到的数据包的标签，确定QoS流1、QoS流2以及QoS流3上的数据包相同，RAN网元可以将一个组RNTI配置给终端设备1、终端设备2和终端设备3，并在该组RNTI对应的无线空口资源上发送从QoS流1上接收到的数据包，这样，终端设备1、终端设备2和终端设备3就可以通过该组RNTI对应的无线空口资源同时接收到相同的数据包。
UPF网元和RAN网元都进行传输优化：
UPF网元和RAN网元都进行传输优化，指UPF网元进行传输优化和RAN网元进行传输优化都要执行。
这种情况下，RAN网元服务的多个终端设备对应的UPF网元不同。示例性的，如图13所示，应用服务器发送给终端设备1、终端设备2、终端设备3的数据包承载的内容是相同的，终端设备1和终端设备2对应UPF网元1，终端设备3对应UPF网元2。UPF网元1可以对发送给终端设备1和终端设备2的数据包进行传输优化，通过QoS流1向RAN网元发送终端设备1对应的数据包。UPF网元2通过QoS流3向RAN网元发送终端设备3对应的数据包。RAN网元可以对QoS流1和QoS流3进行传输优化，RAN网元可以将一个组RNTI配置给终端设备1、终端设备2和终端设备3，RAN网元识别QoS流1和QoS流3中的数据包承载的是相同内容，RAN网元确定在无线空口资源上传输QoS流1中的数据包，RAN网元在该组RNTI对应的无线空口资源上发送QoS流1中的数据包，这样，终端设备1、终端设备2和终端设备3就可以同时在空口上接收到相同的数据包。
针对以上三种传输优化方式，RAN网元在组RNTI对应的无线空口资源上向终端设备1、终端设备2和终端设备3发送QoS流1中的数据包，该数据包的目的IP地址为终端设备1的IP地址，使得终端设备2和终端设备3虽然接收到了数据包，但是由于目的IP地址不是本终端设备的IP地址，所以会丢弃收到的数据包。
本申请实施例提供的数据包处理方法，在第一网元(例如，UPF网元或RAN网元)进行传输优化时，第一网元根据第一指示信息和第一多播业务的第一数据包生成第二数据包。其中，第一指示信息用于指示使用第一多播业务的公共IP地址传输第一多播业务的数据，第一数据包的目的IP地址为第一终端设备的IP地址，第二数据包的目的IP地址为公共IP地址。例如，通过该方法，第一网元可以将发送给第一终端设备的多播业务的数据包的目的IP地址修改为公共IP地址，以实现多个终端设备(可以包括该第一终端设备)能够同时接收该第一终端设备的多播业务的数据包，所述多个终端设备接收到该第一终端设备的多播业务的数据包后，根据其目的IP地址为公共IP地址确定接受而不是丢弃该第一终端设备的多播业务的数据包。
如图14所示，本申请实施例提供了一种数据包处理方法，该方法包括：
S1401、第一网元接收第一指示信息和第一数据包。
其中，第一网元可以为UPF网元或RAN网元，不予限制。
其中，第一数据包对应第一多播业务，且第一数据包的目的IP地址为第一终端设备的IP地址。
具体地，第一数据包可以用于向第一终端设备传输第一多播业务的数据，或者说，第一数据包用于承载该第一终端设备的第一多播业务。例如，对于体育赛事直播来说，第一数据包用于向第一终端设备传输体育赛事直播的视频流(video stream)数据和音频流(audio stream)数据。
需要说明的是，该第一终端设备可以是任意一个终端设备，不限定为特殊的终端设备。例如，假设接收第一多播业务的终端设备包括终端设备1(IP地址为IP1)、终端设备2(IP地址为IP2)、……、终端设备n(IP地址为IPn)，则第一终端设备可以为终端设备1至终端设备n中的一个。
假设第一终端设备为终端设备1，则第一终端设备的IP地址为终端设备1的IP地址IP1。
需要说明的是，第一网元还可以接收其他终端设备的第一多播业务的数据包，这些其他终端设备的第一多播业务的数据包承载的内容与第一数据包承载的内容相同，即承载的第一多播业务的数据相同。
其中，第一指示信息可以用于指示使用第一多播业务的公共IP地址传输第一多播业务的数据。
其中，第一多播业务可以为组播业务或广播业务。
在一种可能的实施方式中，第一指示信息包括第一多播业务的标识信息，而不包括所述公共IP地址。
具体地，第一网元可以预配置所述公共IP地址，或者，第一网元可以从SMF网元接收所述公共IP地址，或者，第一网元可以根据第一多播业务的标识信息获得所述公共IP地址，或者，对于第一网元为UPF网元来说，第一网元可以根据第一多播业务的标识信息生成所述公共IP地址，并保存在本地。
在另一种可能的实施方式中，第一指示信息包括承载第一多播业务的QoS流的标识信息，或者，包括第一终端设备的标识信息。其中，QoS流的标识信息用于标识一个QoS流，可以为QoS流标识(QoS flow identifier，QFI)或5QI。第一终端的标识信息用于标识第一终端设备，可以为签约永久标识(subscription permanent identifier，SUPI)、通用签约标识(generic public subscription identifier，GPSI)或IP地址等。
在又一种可能的实施方式中，第一指示信息包括第一多播业务的标识信息和公共IP地址之间的关联关系，该关联关系指公共IP地址对应于第一多播业务的标识信息指示的第一多播业务。
其中，第一多播业务的标识信息用于指示或标识第一多播业务。第一多播业务的标识信息可以为以下任意一种：第一多播业务的应用标识、第一多播业务的三元组、第一多播业务对应的业务标识符以及UPF网元的用户面IP地址和UPF网元的用户面端口号。
相应的，针对上述不同的第一多播业务的标识信息，第一多播业务的标识信息与所述公共IP地址的关联关系可以包括以下几种情况：
情况1、第一多播业务的标识信息与所述公共IP地址的关联关系为应用标识符与 所述公共IP地址的关联关系，或者，三元组与所述公共IP地址的关联关系。
也就是说，一个应用可以只提供一种业务；或者，一个应用可以提供多种业务，但是发送端和接收端对该应用的不同业务不必进行区分。该多播业务的标识信息与所述公共IP地址一一对应，等价于该应用的应用标识符与所述公共IP地址一一对应，也等价于该应用的三元组与所述公共IP地址一一对应。
情况2、第一多播业务的标识信息与所述公共IP地址的关联关系为业务标识符与所述公共IP地址的关联关系。
也就是说，发送端和接收端对一个应用的不同业务进行区分，一个业务的标识信息与一个公共IP地址一一对应。
情况3、第一多播业务的标识信息与所述公共IP地址的关联关系为UPF网元的用户面IP地址和UPF网元的用户面端口号与所述公共IP地址的关联关系。
也就是说，UPF网元的用户面IP地址和UPF网元的用户面端口号与所述公共IP地址一一对应。一个用户面IP地址和用户面端口号可以只分配给一个应用的一个业务使用，此时UPF网元通过用户面IP地址和用户面端口号识别一个业务，或者，一个用户面IP地址和用户面端口号可以分配给多个应用使用，此时UPF网元通过用户面IP地址和用户面端口号以及应用服务器的IP地址来区别不同的业务。
第一网元可以根据第一多播业务的标识信息和上述关联关系，获得所述公共IP地址。示例性的，第一网元可以根据第一多播业务的标识信息中的业务标识符，从本地信息中获取所述公共IP地址；或者，第一网元可以将第一多播业务的标识信息中的用户面IP地址作为所述公共IP地址。
其中，公共IP地址可以用于在移动通信网络内部第一网元向多个终端设备传输第一多播业务的数据。所述公共IP地址可以是多个终端设备接收第一多播业务对应的数据包的IP地址。也可以是多个终端设备中任意一个终端的IP单播地址、未被占用的IP单播地址或未被占用的IP组播地址。具体地，UPF网元可以分配或预留IP单播地址或者IP组播地址用做公共IP地址。
具体地，在步骤S1401中，第一网元可以从SMF网元接收第一指示信息；或者，第一网元可以从终端设备接收第一指示信息；或者，第一网元可以从应用服务器接收第一指示信息。
本申请不限定第一指示信息的具体形式，可以通过显式、隐式等方式来指示第一指示信息，例如第一指示信息可以是一个具备第一指示信息的作用的消息，或者是消息中的一个参数或一组参数集合，或者是消息中的一个或多个比特位。
具体地，在步骤S1401中，当第一网元为UPF网元时，第一网元可以从应用服务器接收第一数据包；或者，当第一网元为RAN网元时，第一网元可以从UPF网元接收第一数据包。
S1402、第一网元根据第一指示信息和第一数据包，发送第二数据包。
其中，第二数据包的目的IP地址为第一多播业务的公共IP地址。
具体地，在步骤S1402中，第一网元可以根据第一指示信息和第一数据包，生成第二数据包，并发送该第二数据包。
可选的，在第一种实施场景下，第一网元为RAN网元，步骤S1402包括：第一 网元根据第一指示信息和第一数据包，采用空口组播方式发送第二数据包。
下面结合第一种实施场景，针对第一指示信息的内容不同的情况，对步骤S1402进行详细描述。
情况1a、第一指示信息包括第一多播业务的标识信息和第一多播业务的公共IP地址之间的关联关系。
相应地，在骤S1402中，第一网元可以根据第一多播业务的标识信息确定该第一多播业务对于多个终端设备传输的内容是相同的，可以对第一多播业务的数据包进行传输优化。进而第一网元根据第一多播业务的第一数据包和公共IP地址生成第二数据包。
在一个示例中，假设第一网元为RAN网元，且在步骤S1401中第一网元从UPF网元接收到包括第一多播业务的标识信息(例如业务标识符)的第一数据包，或者，从UPF网元接收到来自指定终端设备的第一多播业务的QoS流或公共QoS流的第一数据包，或者，从UPF网元接收到特定终端设备的第一数据包，该特定终端设备可以由SMF网元在会话建立或会话更新阶段指示给RAN网元的，或者RAN网元自己确定的，那么第一网元可以确定该第一数据包可以使用第一多播业务的公共IP地址来传输，从而生成第二数据包。
第一网元可以仅仅将第一数据包的IP头部(IP header)的目的IP地址替换为第一多播业务的公共IP地址得到第二数据包。或者，第一网元可以取出第一数据包的载荷(payload)部分，重新封装IP头部，得到第二数据包，其中，第二数据包的IP头部的目的IP地址为所述公共IP地址。
第一网元可以将一个组RNTI配置给所述多个终端设备，在空口通过该组RNTI对应的无线空口资源向所述多个终端设备发送第二数据包。
情况1b、第一指示信息包括第一多播业务的标识信息，而不包括第一多播业务的公共IP地址。
相应地，在骤S1402中，第一网元可以在本地检索第一多播业务的标识信息对应的公共IP地址。然后按照情况1a中的方式来根据第一多播业务的第一数据包和公共IP地址生成第二数据包，并向所述多个终端设备发送第二数据包。
可选的，在第二种实施场景下，第一网元为UPF网元，步骤S1402包括：第一网元根据第一指示信息和第一数据包，向RAN网元发送第二数据包。
下面结合第二种实施场景，针对第一指示信息的内容不同，对步骤S1402进行详细描述。
情况2a、第一指示信息包括第一多播业务的标识信息和第一多播业务的公共IP地址之间的关联关系。
相应地，在骤S1402中，第一网元可以按照情况1a中的方式来根据第一多播业务的第一数据包和公共IP地址生成第二数据包，然后向RAN网元改送第二数据包。具体地，第一网元可以直接或通过中间UPF(itermediate UPF，I-UPF)网元间接向RAN网元发送第二数据包。
例如，UPF网元可以在一个终端设备对应该第一多播业务的N3 QoS流、公共N3隧道，或者每个终端设备对应该第一多播业务的各自的N3 QoS流向RAN网元发送第 二数据包。
情况2b、第一指示信息包括第一多播业务的标识信息，而不包括第一多播业务的公共IP地址。
相应地，在骤S1402中，第一网元可以可以在本地检索第一多播业务的标识信息对应的公共IP地址。然后按照情况2a中的方式来根据第一多播业务的第一数据包和公共IP地址生成第二数据包，并向RAN网元发送第二数据包。
当第一指示信息中包括第一多播业务的标识信息时，第一网元可以确定第一数据包承载的是第一多播业务的数据。由于第一指示信息中包括第一多播业务的标识信息，第一网元可以确定该第一数据包可以使用第一多播业务的公共IP地址来传输，从而生成第二数据包。第二数据包的目的IP地址为第一多播业务的公共IP地址。
具体的，对于第一多播业务的标识信息与所述公共IP地址的关联关系为应用标识符与所述公共IP地址的关联关系，或者，三元组与所述公共IP地址的关联关系来说：
应用标识符与三元组是对应的，第一网元可以根据应用标识符查找对应的三元组。当第一网元从应用服务器接收到第一数据包时，如果第一数据包中的三元组与第一多播业务的标识信息中的三元组相同，或者，如果第一数据包中的三元组与第一多播业务的标识信息中的应用标识符对应的三元组相同，则第一网元可以确定该第一数据包可以使用第一多播业务的公共IP地址来传输，从而生成第二数据包。
对于第一多播业务的标识信息与所述公共IP地址的关联关系为业务标识符与所述公共IP地址的关联关系来说：
当第一网元从应用服务器接收到第一数据包时，如果第一网元是从第一多播业务的标识信息中的业务标识符对应的隧道上接收到的第一数据包，则第一网元可以确定该第一数据包可以使用第一多播业务的公共IP地址来传输，从而生成第二数据包。
对于第一多播业务的标识信息与所述公共IP地址的关联关系为UPF网元的用户面IP地址和UPF网元的用户面端口号与公共IP地址的关联关系来说，第一网元为UPF网元。
情况一、如果一个用户面IP地址和用户面端口号只分配给一个应用的一个业务使用，当UPF网元从第一多播业务对应的UPF网元的用户面IP地址和UPF网元的用户面端口号接收到第一数据包时，则UPF网元可以确定该第一数据包可以使用第一多播业务的公共IP地址来传输，从而生成第二数据包。
情况二、如果一个用户面IP地址和用户面端口号分配给多个应用使用，当UPF网元从第一多播业务对应的UPF网元的用户面IP地址和UPF网元的用户面端口号接收到第一数据包，该数据包的三元组与第一多播业务的三元组相同，则UPF网元可以确定该第一数据包可以使用第一多播业务的公共IP地址来传输，从而生成第二数据包。
情况三、如果第一指示信息中包括业务标识符，则UPF网元可以根据该业务标识符确定对应的用户面IP地址，然后根据上述情况一或情况二的方式来生成第二数据包。
本申请实施例提供的数据包处理方法，第一网元接收第一指示信息和第一数据包，第一指示信息可以用于指示使用公共IP地址传输第一多播业务的数据，第一数据包承 载第一终端设备的第一多播业务，第一数据包的目的IP地址为第一终端设备的IP地址。第一网元根据第一指示信息和第一数据包，发送第二数据包，第二数据包的目的IP地址为第一多播业务的公共IP地址。终端设备接收到第二数据包后，根据其目的IP地址为公共IP地址可以确定接受第二数据包，不会丢弃第二数据包，可以防止进行传输优化时终端设备丢包。
可选的，在上述实施的一种实时场景下，上述方法还包括：第一网元接收第三数据包，第三数据包对应第一多播业务，第三数据包的目的IP地址为第二终端设备的IP地址；第一网元丢弃第三数据包。
其中，第三数据包对应第一多播业务可以指的是第三数据包承载第一多播业务的数据。
第三数据包承载的内容与第一数据包承载的内容相同，即第三数据包的载荷部分与第一数据包的载荷部分相同。第二终端设备为所述多个终端设备中的又一个终端设备。
其中，第一网元丢弃第三数据包，可以替换为：第一网元不处理第三数据包。
也就是说，对于同一多播业务来说，第一网元可以根据第一指示信息对接收到的至少两个数据包(第一数据包和第三数据包)进行传输优化，即可以只发送由第一数据包和第一指示信息生成的第二数据包，而丢弃或不处理第三数据包。
针对前文中第一网元使用的第一指示信息，第一网元可以从SMF网元来获取。
具体的，本申请实施例提供了一种数据包处理方法，如图15所示，该方法包括：
S1501、SMF网元获取第一多播业务的标识信息。
可选的，SMF网元可以在本地生成第一多播业务的标识信息，例如SMF可以预先生成一组多播业务的标识信息(例如临时群组标识等)，SMF网元在接收到来自第一多播业务的应用服务器的多播传输服务请求后，将一组多播业务的标识信息中的一个分配给第一多播业务；或者，SMF网元可以从第一多播业务的应用服务器获取第一多播业务的标识信息，在第一多播业务的应用服务器向SMF网元请求多播传输服务时，第一多播业务的应用服务器可以在多播传输服务请求中携带应用标识符、三元组信息或该应用服务器自己生成的第一多播业务的标识符(例如临时群组标识)中的至少一个；或者，SMF网元可以从UPF网元获取第一多播业务的标识信息，例如，在第一多播业务的应用服务器向SMF网元请求多播传输服务时，SMF网元可以向UPF网元请求该第一多播业务对应的UPF网元的用户面IP地址和UPF网元的用户面端口号；或者，SMF网元可以从终端设备接收第一多播业务的标识信息，例如，终端设备在发送给SMF网元的会话建立/更新请求消息中，携带第一多播业务的应用标识符、三元组或第一多播业务的标识符中的至少一个。
需要说明的是，SMF网元可以根据第一多播业务的标识信息确定该第一多播业务对应的UPF网元的用户面IP地址和UPF网元的用户面端口号。然后将上述信息发送给应用服务器，以便应用服务器通过隧道的方式将多个终端设备的数据包发送给对应的UPF网元。或者，SMF网元在与UPF网元交互时，可以使用上述信息作为索引或者作为IP数据流转发规则，指示UPF网元如果从该用户面IP地址和用户面端口号接收到数据包，如何进行转发。
在一种可能的实施方式中，当第一多播业务的标识信息中包括用户面IP地址和用户面端口号时，SMF网元可以直接将第一多播业务的标识信息中的用户面IP地址确定为第一多播业务对应的UPF网元的用户面IP地址，将第一多播业务的标识信息中的用户面端口号确定为第一多播业务对应的UPF网元的用户面端口号。
在另一种可能的实施方式中，当第一多播业务的标识信息中包括业务标识符时：
如果SMF网元已经被预配置该业务标识符对应的用户面IP地址和用户面端口号，则SMF网元可以将该预配置的用户面IP地址作为第一多播业务对应的UPF网元的用户面IP地址，将该预配置的用户面端口号作为该第一多播业务对应的UPF网元的用户面端口号。
或者，如果SMF网元之前已经为该业务标识符动态分配了用户面IP地址和用户面端口号，则SMF网元可以将该动态分配的用户面IP地址作为第一多播业务对应的UPF网元的用户面IP地址，将该动态分配的用户面端口号作为该第一多播业务对应的UPF网元的用户面端口号。
或者，如果SMF网元之前已经从UPF网元获取UPF网元为该业务标识符动态分配的用户面IP地址和用户面端口号，则SMF网元可以将该动态分配的用户面IP地址作为第一多播业务对应的UPF网元的用户面IP地址，将该动态分配的用户面端口号作为该第一多播业务对应的UPF网元的用户面端口号。
或者，SMF网元为该业务标识符动态分配用户面IP地址作为第一多播业务对应的UPF网元的用户面IP地址，动态分配用户面端口号作为该第一多播业务对应的UPF网元的用户面端口号。
或者，SMF网元向UPF网元请求为该业务标识符动态分配用户面IP地址和用户面端口号，则SMF网元可以将该动态分配的用户面IP地址作为第一多播业务对应的UPF网元的用户面IP地址，将该动态分配的用户面端口号作为该第一多播业务对应的UPF网元的用户面端口号。
关于第一多播业务的标识信息见前文描述，在此不再重复。
S1502、SMF网元根据第一多播业务的标识信息，向第一网元发送第一指示信息。
可选的，SMF网元可以从应用服务器获取第一指示信息；或者，SMF网元可以从终端设备获取第一指示信息；或者，SMF网元自己生成第一指示信息。
由于第一指示信息中也包括第一多播业务的标识信息，SMF网元可以根据获取的第一多播业务的标识信息确定对应的第一指示信息，从而向第一网元发送对应的第一指示信息。第一网元可以为UPF网元或RAN网元。
另外，如前文所述的，第一指示信息中可以包括所述公共IP地址，或者不包括所述公共IP地址，对于第一指示信息中不包括所述公共IP地址来说，SMF网元还可以单独向第一网元发送所述公共IP地址。
对于公共IP地址，SMF网元可以通过以下方式来获取：在一种可能的实施方式中，SMF网元可以生成所述公共IP地址。或者，在另一种可能的实施方式中，SMF网元可以从应用服务器接收所述公共IP地址。
关于第一多播业务的标识信息、第一指示信息以及公共IP地址的详细介绍，见前面步骤的描述，在此不再重复。
本申请实施例提供的数据包处理方法，提供了第一网元如何获取第一指示信息的方法，使得第一网元对第一多播业务的第一数据包进行传输优化时，可以根据第一指示信息和第一数据包发送第二数据包，第一数据包的目的IP地址为第一终端设备的IP地址，第二数据包的目的IP地址为第一多播业务的公共IP地址。终端设备接收到第二数据包后，根据其目的IP地址为公共IP地址可以确定接受第二数据包，不会丢弃第二数据包，可以防止进行传输优化时终端设备丢包。
下面以第一多播业务的标识信息为第一多播业务对应的UPF网元的用户面IP地址和UPF网元的用户面端口号为例，说明AF网元如何向UPF网元发送第一多播业务对应的至少两个数据包。
具体的，本申请实施例提供了另一种数据包处理方法，如图16所示，该方法包括：
S1601、应用服务器获取第一多播业务对应的UPF网元的用户面IP地址和UPF网元的用户面端口号。
应用服务器为第一多播业务的应用服务器。
可选的，应用服务器可以通过SMF网元获取由UPF网元生成的第一多播业务对应的UPF网元的用户面IP地址和UPF网元的用户面端口号。或者，应用服务器可以获取由SMF网元生成的第一多播业务对应的UPF网元的用户面IP地址和UPF网元的用户面端口号。
S1602、应用服务器使用所述用户面IP地址和所述用户面端口号，向UPF网元发送第一数据包和第三数据包。
相应地，UPF网元通过所述用户面IP地址和所述用户面端口号从应用服务器接收第一数据包和第三数据包。
其中，第一数据包和第三数据包均承载的是所述第一多播业务的第一数据，第一数据包的目的IP地址为第一终端设备的IP地址，第三数据包的目的IP地址为第二终端设备的IP地址，即第一数据包和第三数据包承载的第一多播业务的数据相同，即第一数据包和第三数据包的载荷部分相同。
UPF网元根据所述用户面IP地址和所述用户面端口号即可以确定第一数据包和第三数据包对应第一多播业务，从而可以进行传输优化。
本申请实施例提供的数据包处理方法，在第一多播业务的标识信息为第一多播业务对应的UPF网元的用户面IP地址和UPF网元的用户面端口号时，应用服务器使用所述用户面IP地址和所述用户面端口号向UPF网元发送第一多播业务的至少两个数据包，UPF网元根据所述用户面IP地址和所述用户面端口号即可以确定所述至少两个数据包对应第一多播业务，从而可以对所述至少两个数据包进行传输优化。
下面对终端设备接收到经过传输优化的第一数据包后如何进行处理进行说明。
具体的，本申请实施例提供了另一种数据包处理方法，如图17所示，该方法包括：
S1701、终端设备接收第一数据包。
第一数据包对应第一多播业务，第一数据包的目的IP地址为第一多播业务的公共IP地址，关于第一多播业务、第一数据包、所述公共IP地址见前面描述。
可选的，终端设备还可以接收所述公共IP地址。例如，可以从应用服务器接收所述公共IP地址，或者，从PCF网元接收所述公共IP地址，或者，从SMF网元接收所 述公共IP地址。即应用服务器、PCF网元或SMF网元可以指示终端设备，对于目的IP地址为第一多播业务的公共IP地址的数据包是发送给该终端设备的。终端设备根据第一数据包的目的IP地址为公共IP地址确定接受第一数据包，不会丢弃第一数据包，可以防止进行传输优化时终端设备丢包。
可选的，在接收第一数据包之前，终端设备还可以向SMF网元发送第一消息，第一消息包括第一多播业务的标识信息或者所述公共IP地址，所述第一消息用于请求第一多播业务的数据。该实施方式可以使得SMF网元将第一多播业务的标识信息或者所述公共IP地址发送给UPF网元或RAN网元。
S1702、终端设备根据第一数据包得到第二数据包。
第二数据包的目的IP地址为终端设备的IP地址。
终端设备可以将第一数据包的目的IP地址替换为本终端设备的IP地址得到第二数据包。或者，终端设备可以对第一数据包重新进行封装得到第二数据包。
如图18所示，为本申请实施例提供的一种协议栈，终端设备侧的PDU层包括两部分(PDU层1和PDU层2)。PDU层2用于将第一数据包的目的IP地址替换为本终端设备的IP地址得到第二数据包，或者，对第一数据包重新进行封装得到第二数据包。PDU层2用于对第二数据包进行解封装，并将应用数据载荷传递给上层的应用层。
具体的，如果终端设备为该应用建立了公共IP地址对应的套接字(Socket)连接，则终端设备直接将第二数据包中的应用数据载荷递给上层应用。
或者，如果终端设备为该应用建立了单播IP地址对应的套接字(Socket)连接，则终端设备先从配置文件获取公共IP地址与套接字(Socket)连接的关联关系，或者，通过应用层和通信层的层间交互获取公共IP地址与套接字(Socket)连接的关联关系，然后将第二数据包中的应用数据载荷递给上层应用。
本申请实施例提供的数据包处理方法，终端设备接收到第一数据包后，根据其目的IP地址为公共IP地址可以确定接受第一数据包，不会丢弃第一数据包，可以防止进行传输优化时终端设备丢包。
下面对UPF网元进行传输优化的过程的一种示例进行说明。
具体的，本申请实施例提供了另一种数据包处理方法，如图19所示，该方法包括：
S1901、SMF网元获取第一多播业务的标识信息。
该步骤可以参照步骤S1501，在此不再重复。
S1902、SMF网元根据第一多播业务的标识信息，向UPF网元发送第一指示信息。
该步骤可以参照步骤S1502，在此不再重复。
相应地，UPF网元从SMF网元接收第一指示信息。
S1903、应用服务器向UPF网元发送第一数据包。
相应地，UPF网元从应用服务器接收第一数据包。
关于第一数据包可以参照步骤S1401中关于第一数据包的描述，在此不再重复。
S1904、UPF网元根据第一指示信息和第一数据包，向RAN网元发送第二数据包。
相应地，RAN网元接收第二数据包。
该步骤可以参照步骤S1402中第一网元为UPF网元时的相关描述，在此不再重复。
S1905、RAN网元采用空口组播方式向至少两个终端设备发送第二数据包。
相应地，所述至少两个终端设备接收第二数据包。
即RAN网元可以将一个组RNTI配置给所述至少两个终端设备，通过该组RNTI对应的无线空口资源向所述至少两个终端设备发送第二数据包。
S1906、所述至少两个终端设备分别根据第二数据包得到各自的第三数据包。
需要说明的是，各个终端设备根据第二数据包得到各自的第三数据包的过程是相互独立的，不同的终端设备得到的第三数据包是不同的，第三数据包的目的IP地址为本终端设备的IP地址，但是承载的载荷是相同的。
终端设备可以将第二数据包的目的IP地址替换为本终端设备的IP地址得到第三数据包。或者，终端设备可以对第二数据包重新进行封装得到第三数据包。
本申请实施例提供的数据包处理方法，UPF网元接收第一指示信息和第一数据包，第一指示信息可以用于指示使用公共IP地址的第一多播业务的数据，第一数据包对应第一多播业务，第一数据包的目的IP地址为第一终端设备的IP地址。UPF网元根据第一指示信息和第一数据包，发送第二数据包，第二数据包的目的IP地址为第一多播业务的公共IP地址。终端设备接收到第二数据包后，根据其目的IP地址为公共IP地址可以确定接受第二数据包，不会丢弃第二数据包，可以防止进行传输优化时终端设备丢包。
下面对RAN网元进行传输优化的过程的一种示例进行说明。
具体的，本申请实施例提供了另一种数据包处理方法，如图20所示，该方法包括：
S2001、SMF网元获取第一多播业务的标识信息。
该步骤可以参照步骤S1501，在此不再重复。
S2002、SMF网元根据第一多播业务的标识信息，向RAN网元发送第一指示信息。
相应地，RAN网元从SMF网元接收第一指示信息。
该步骤可以参照步骤S1502，在此不再重复。
S2003、应用服务器向UPF网元发送第一数据包，UPF网元向RAN网元发送第一数据包。
相应地，RAN网元接收来自应用服务器的第一数据包。
关于第一数据包可以参照步骤S1401中关于第一数据包的描述，在此不再重复。
S2004、RAN网元根据第一指示信息和第一数据包，采用空口组播方式向至少两个终端设备发送第二数据包。
相应地，所述至少两个终端设备接收第二数据包。
该步骤可以参照步骤S1402中第一网元为RAN网元时的相关描述，在此不再重复。
S2005、所述至少两个终端设备分别根据第二数据包得到各自的第三数据包。
该步骤可以参照步骤S1906，在此不再重复。
本申请实施例提供的数据包处理方法，RAN网元接收第一指示信息和第一数据包，第一指示信息可以用于指示使用公共IP地址的第一多播业务的数据，第一数据包对应第一多播业务，第一数据包的目的IP地址为第一终端设备的IP地址。RAN网元根据第一指示信息和第一数据包，发送第二数据包，第二数据包的目的IP地址为第一多播业务的公共IP地址。终端设备接收到第二数据包后，根据其目的IP地址为公共 IP地址可以确定接受第二数据包，不会丢弃第二数据包，可以防止进行传输优化时终端设备丢包。
下面对SMF网元获取第一指示信息的几种方式进行说明。
在方式一中，SMF网元可以通过AF影响(influence)应用流程路由的过程获取第一指示信息。在AF影响过程中，SMF网元由于运营商的归一化数据仓库(unified data repository，UDR)网元中应用数据变化而被通知第一指示信息。
如图21所示，方式一包括：
S2101、应用服务器根据第一指示信息构造应用请求(AF request)消息。
即应用请求(AF request)消息中包括第一指示信息。
可选的，应用请求(AF request)消息还可以包括所述公共IP地址。
关于第一指示信息、所述公共IP地址的内容见前面描述，在此不再重复。
S2102、应用服务器向NEF网元发送应用请求(AF request)消息。
相应地，NEF网元从应用服务器接收应用请求消息。
具体的，应用服务器可以通过调用NEF网元的应用流量影响创建/更新(Nnef_TrafficInfluence_Create/Update)服务，或者，NEF网元的应用策略创建(Nnef_ApplyPolicy_Create)服务，或者，NEF网元的服务参数创建/更新(Nnef_ServiceParameter_Create/Update)服务向NEF网元发送应用请求(AF request)消息。
也就是说，应用服务器可以向NEF网元发送应用流量影响创建/更新请求(Nnef_TrafficInfluence_Create/Update request)消息，或者，应用策略创建请求(Nnef_ApplyPolicy_Create request)消息，或者，服务参数创建/更新请求(Nnef_ServiceParameter_Create/Update request)消息，在发送的消息中包括应用请求(AF request)消息。
S2103、NEF网元将第一指示信息保存在UDR网元中。
具体的，NEF网元可以将第一指示信息作为该应用的策略/描述信息的一部分存储在UDR中。其中，应用的策略/描述信息用于对该应用的数据包的检测及转发。
可选的，将第一指示信息和所述公共IP地址可以作为该应用的策略/描述信息的一部分存储在UDR中。
可选的，NEF网元可以向应用服务器发送应用请求(AF request)消息的响应消息。
S2104、如果PCF网元已经订阅了应用请求(AF request)修改事件，则UDR网元向PCF网元发送数据管理通知(Nudr_DM_Notify notification)消息。
该消息中包括第一指示信息。
可选的，该消息中还可以包括所述公共IP地址。
S2105、PCF网元确定应用请求(AF request)修改事件影响到现有的PDU会话，则针对每一个PDU会话，根据第一指示信息更新SMF网元的策略及计费控制(policy and charging control，PCC)规则(rule)。
应用请求(AF request)修改事件影响到现有的PDU会话，指当前有至一个终端设备已经进行与应用请求(AF request)修改事件相关的业务，例如，至少一个终端设备中正在通过视频播放APP获取体育赛事直播的视频片段，而应用请求(AF request) 修改事件修改了体育赛事直播的策略/描述信息。
PCC规则用于对用户数据的检测和转发。PCF网元可以通过会话管理策略控制更新通知(Npcf_SMPolicyControl_UpdateNotify)服务，将第一指示信息更新至SMF网元的PCC规则。该第一指示信息可以存储在PCC规则的应用检测过滤器或业务数据流过滤器(application detection filters/service data flow filter(s))中。
可选的，PCF网元可以将所述公共IP地址更新至SMF网元的PCC规则。该公共IP地址同样可以存储在PCC规则的应用检测过滤器或业务数据流过滤器(application detection filters/service data flow filter(s))中。
S2106、SMF网元向第一网元发送第一指示信息。
可选的，SMF网元可以向第一网元发送所述公共IP地址。
SMF网元可以在用户面QoS流建立和修改过程中向第一网元发送上述信息(第一指示信息、所述公共IP地址)。
示例性的，SMF网元可以在向UPF网元发送的PDU会话管理消息中携带上述信息。具体地，上述信息可以携带在包检测规则(packet detection rule，PDR)中，例如，可以携带在PDR的(IP)包过滤器((IP)packet filter)、应用检测过滤器(application detection filters)或业务数据流过滤器(service data flow filter(s))中。
在方式二中，SMF网元可以在用户面QoS流建立或修改过程中，从UDR网元获取第一指示信息。方式二包括两个阶段，第一阶段如图22所示，指应用服务器向UDR网元发送第一指示信息。第二阶段如图23所示，指SMF网元从UDR网元获取第一指示信息。
如图22所示，第一阶段包括：
S2201、应用服务器确定第一指示信息，并向NEF网元发送第一指示信息。
具体地，应用服务器可以向NEF网元发送数据包流描述管理创建/更新(Nnef_PFDManagement_Create/Update request)消息。该消息中包括第一指示信息。
具体地，可以通过扩展PFD来携带第一指示信息，即在扩展PFD中增加一项第一指示信息。如果第一标识指示信息不包括所述公共IP地址，还可以在扩展PFD中添加所述公共IP地址。
需要说明的是，应用服务器可以一次向NEF网元发送多个第一指示信息，分别对应不同的应用或者一个应用的不同业务。例如：
<Application identifier 1/三元组(IP 1，port 1，protocol ID 1),第一指示信息1>；
<Application identifier 1/三元组(IP 1，port 1，protocol ID 1),第一指示信息2>；
<Application identifier 2/三元组(IP 1，port 2，protocol ID 1),第一指示信息3>；
<Application identifier 3/三元组(IP 2，port 2，protocol ID 1),第一指示信息4>。
其中，应用标识符或三元组唯一标识一个应用，Application identifier表示应用标识符。从中可以看出，第一指示信息1和第一指示信息2对应一个应用的不同业务，第一指示信息3和第一指示信息4对应不同应用。
NEF网元也可以与数据包流描述功能(packet flow description function，PFDF)网元布置在同一网元上。
S2202、NEF网元做授权检查判断应用服务器有权限修改PFD。
S2203、NEF网元向UDR网元发送UDR数据管理创建/更新请求(Nudr_DM_Create/Update request)消息。
该消息可以包括第一指示信息。
具体的，可以通过扩展PFD来携带第一指示信息。
S2204、UDR网元更新第一指示信息。
具体地，UDR网元可以更新应用标识符对应的PFD从而更新第一指示信息。
S2205、UDR网元向NEF网元发送UDR数据管理创建/更新响应(Nudr_DM_Create/Update response)消息。
该消息用于对UDR数据管理创建/更新请求(Nudr_DM_Create/Update request)消息进行确认。
S2206、NEF网元向应用服务器发送数据包流描述管理创建/更新响应(Nnef_PFDManagement_Create/Update response)消息。
该消息用于对数据包流描述管理创建/更新请求(Nnef_PFDManagement_Create/Update request)消息进行确认。
如图23所示，第二阶段包括：
S2301、SMF网元向NEF网元发送数据包流描述管理获取请求(Nnef_PFDManagement_Fetch request)消息，以请求获取第一指示信息。
该消息中包括应用标识符。
S2302、NEF网元检查本地是否存在该应用标识符对应的PFD，如果有则执行步骤S2304。否则，NEF网元向UDR网元发送数据管理查询请求(Nudr_DM_Query request)消息，以获取包括第一指示信息的PFD。
该消息中包括应用标识符。
S2303、UDR网元向NEF网元发送数据管理查询响应(Nudr_DM_Query response)消息。
该消息中包括扩展PFD，扩展PFD中包括第一指示信息。
UDR网元可以根据应用标识符查询对应的扩展PFD。
S2304、NEF网元向SMF网元发送数据包流描述管理获取响应(Nnef_PFDManagement_Fetch response)消息。
该消息中包括扩展PFD，扩展PFD中包括第一指示指示信息。
S2305、SMF网元向第一网元发送第一指示信息。
该步骤与步骤S2106相同，在此不再重复。
在方式三中，应用服务器通过业务特定参数配置(service specific parameter provisioning)流程，将第一指示信息配置在UDR网元中，PCF网元从UDR网元获取第一指示信息，并在后续用户面QoS建立流程中将第一指示信息发送给SMF网元。
如图24所示，方式三包括：
S2401、应用服务器根据第一指示信息构造应用请求(AF request)消息。
该步骤与步骤S2101相同，在此不再重复。
S2402、应用服务器向NEF网元发送应用请求(AF request)消息。
具体的，应用服务器可以通过调用NEF网元的服务参数创建/更新 (Nnef_ServiceParameter_Create/Update)服务向NEF网元发送应用请求(AF request)消息。
也就是说，应用服务器可以向NEF网元发送服务参数创建/更新请求(Nnef_ServiceParameter_Create/Update request)消息，该消息中包括应用请求(AF request)消息。
S2403、NEF网元将第一指示信息保存UDR网元中。
该步骤与步骤S2103相同，在此不再重复。
S2404、NEF网元向应用服务器发送服务参数创建/更新响应(Nnef_ServiceParameter_Create/Update response)消息。
该消息用于对服务参数创建/更新请求(Nnef_ServiceParameter_Create/Update request)消息进行确认。
S2405、如果PCF网元已经订阅了数据修改(data modification)事件，则UDR网元向PCF网元发送数据管理通知(Nudr_DM_Notify notification)消息。
该消息中包括第一指示信息。
可选的，该消息中还可以包括所述公共IP地址。
S2406、PCF网元确定应用数据修改(data modification)事件影响到现有的PDU会话，则针对每一个PDU会话，根据第一指示信息更新SMF网元的策略及计费控制(policy and charging control，PCC)规则(rule)。
应用数据修改(data modification)事件影响到现有的PDU会话，指当前有至一个终端设备已经进行与应用数据修改(data modification)事件相关的业务，例如，至少一个终端设备中正在通过视频播放APP获取体育赛事直播的视频片段，而应用数据修改(data modification)事件修改了体育赛事直播的策略/描述信息。
也就是说，如果当前有至少两个终端设备已经与数据修改(data modification)事件中的业务有交互，例如，至少两个终端设备中有一个终端设备正在通过视频播放APP获取体育赛事直播的视频片段，则PCF网元确定应用请求(AF request)修改事件影响到现有的PDU会话。
该步骤其他内容与步骤S2105相同，在此不再重复。
S2407、SMF网元向第一网元发送第一指示信息。
该步骤与步骤S2106相同，在此不再重复。
在方式四中，应用服务器可以在建立针对每个终端设备(per UE)的应用会话(AF session)时，向PCF网元发送第一指示信息，PCF网元在后续会话策略关联建立/修改(SM policy Association establishment/modification)流程中将第一指示信息发送给SMF网元。
如图25所示，方式四包括：
S2501、应用服务器向NEF网元发送第一指示信息。
具体地，应用服务器可以通过NEF网元的应用功能QoS会话创建(Nnef_AFsessionWithQoS_create)服务向NEF网元发送第一指示信息。
即应用服务器向NEF网元发送应用功能QoS会话创建请求(Nnef_AFsessionWithQoS_create request)消息，该消息中可以包括终端设备的IP地 址、应用功能标识符(AF identifier)、应用数据流描述(description of the application flows)。应用数据流描述的数据流过滤信息(traffic filtering information)中包括第一指示信息。
例如通过对现有五元组进行修改，将五元组中的源IP地址变更为该第一指示信息中的用户面IP地址或者与第一指示信息中的业务标识符对应的用户面IP地址。或者，可以对现有五元组进行扩展，在五元组的基础上添加上述用户面IP地址或第一指示信息中的业务标识符，可以称为增强五元组或六元组或其他名称。
S2502、NEF网元做授权检查判断应用服务器有权限执行这个请求操作。
S2503、NEF网元向PCF网元发送策略授权创建请求(Npcf_policyAuthoization_Create request)消息。
该消息中包含步骤S2501中从应用服务器获取的参数，参数中包括第一指示信息。PCF网元基于这些参数生成PCC规则，生成的PCC规则包括第一指示信息。
S2504、PCF网元向NEF网元发送策略授权创建响应(Npcf_policyAuthoization_Create response)消息。
该消息用于对策略授权创建请求(Npcf_policyAuthoization_Create request)消息进行确认。
S2505、NEF网元向应用服务器发送应用功能QoS会话创建响应(Nnef_AFsessionWithQoS_Create response)消息。
该消息用于对应用功能QoS会话创建请求(Nnef_AFsessionWithQoS_create request)消息进行确认。
S2506、PCF网元发起会话策略关联建立/修改(SM policy Association establishment/modification)流程，向SMF网元发送第一指示信息。
第一指示信息可以包含在PCC规则中，具体地，可以包含在PCC规则的包过流器(packet filter)、应用检测过滤器(application detection filters)或业务数据流过滤器(service data flow filter(s))中。
需要说明的是，步骤S2506与步骤S2504-S2505无先后执行顺序。
S2507、SMF网元向第一网元发送第一指示信息。
该步骤与步骤S2106相同，在此不再重复。
在方式五中，终端设备可以在发起QoS流建立或修改流程时，向SMF网元发送第一指示信息。
如图26所示，方式五包括：
S2601、终端设备向SMF网元发送PDU会话建立或更新消息。
该消息中包括第一指示信息，例如，可以在该消息的IP包过滤器(IP packet filter)中携带第一指示信息。
S2602、SMF网元向第一网元发送第一指示信息。
该步骤与步骤S2106相同，在此不再重复。
下面，在UPF网元已经获取第一指示信息以及公共IP地址的基础上，对UPF网元如何根据第一指示信息和第一数据包发送第二数据包进行描述。
如图27所示，本申请实施例提供了另一种该数据包处理方法，该方法包括：
S2701、至少两个终端设备分别发起PDU会话建立或修改流程，以分别请求为该第一多播业务建立用户面连接(即专用QoS流)。
具体的，至少两个终端设备分别向SMF网元发送PDU会话建立/修改请求(PDF session establishment/modification request)消息。
S2702、在PDU会话建立或修改过程中，SMF网元根据PCC规则中第一指示信息确定第一多播业务的数据包可以进行传输优化，并为所述至少两个终端设备建立传输第一多播业务的专用QoS流。
示例性的，SMF网元可以向UPF网元发送N4会话建立/修改请求(N4 session establishment/modification request)消息，用于为所述至少两个终端设备建立传输第一多播业务的专用QoS流。
UPF网元可以向SMF网元发送N4会话建立/修改响应(N4 session establishment/modification response)消息。该消息用于对N4会话建立/修改请求(N4 session establishment/modification request)消息进行确认。
其中，专用QoS流指该QoS流只能用于传输该第一多播业务的数据包，终端设备的其他应用或业务的数据包不能映射到该QoS流上，即其他应用或业务的数据包不能通过该QoS流传输给终端设备。
具体的，在终端设备的其他应用或业务请求建立QoS流时，SMF网元在对该请求进行响应过程中，发给UPF网元的PCC规则是：SMF网元不会将第一多播业务的专用QoS流与其他应用或业务绑定。
或者，SMF网元可以在PCC规则中建立新的PCC规则，其中包含第一指示信息。
S2703、UPF网元从应用服务器接收至少两个终端设备对应的第一多播业务的数据包，其中包括第一数据包。
UPF网元可以将第一终端设备的数据包作为第一数据包，其中第一终端设备为UPF网元接收到的第一个数据包的终端设备，即UPF网元接收到的第一个数据包是发送给第一终端设备的数据包。或者，按照预设规则选择发送给第一终端设备的数据包作为第一数据包。对于接收到的其余终端设备的第一多播业务的数据包可以丢弃或不处理。
需要说明的是，由于有时应用服务器通过UPF网元发送给不同终端设备的同一多播业务的数据包不是同一时刻到达UPF网元，因此，UPF网元可以在时间窗内对接收到的发送给至少两个终端设备的第一多播业务的数据包进行优化优化。该时间窗可以是运营商预配置的，或者，可以是运营商按需动态配置的。
S2704、UPF网元根据第一指示信息和第一数据包，向RAN网元发送第二数据包。
该步骤可以参照S1402中第一网元为UPF网元的相关描述，在此不再重复。
如图28所示，该步骤实现了在UPF网元生成第二数据包，并且第二数据包的目的IP地址为公共IP地址。
S2705、RAN网元采用空口组播方式向所述至少两个终端设备发送第二数据包。
具体的，RAN网元RAN网元可以将一个组RNTI配置给所述至少两个终端设备，在空口通过组RNTI对应的无线空口资源向所述至少两个终端设备发送第二数据包。
S2706、所述至少两个终端设备分别根据第二数据包得到各自的第三数据包。
该步骤可以参照步骤S1906，在此不再重复。
下面，在RAN网元已经获取第一指示信息以及公共IP地址的基础上，对RAN网元如何根据第一指示信息和第一数据包发送第二数据包的一种方式进行描述。在该方式中，UPF网元向RAN网元只发送所述至少两个终端设备中第一终端设备对应的第一多播业务的数据包。
如图29所示，本申请实施例提供了另一种该数据包处理方法，该方法包括：
S2901、至少两个终端设备或应用服务器分别发起PDU会话建立或修改流程，以请求建立或修改特定终端设备接收应用服务器数据的QoS流。
该QoS流用于承载终端设备和应用服务器之间交互的应用层信令或媒体数据。
具体的，至少两个终端设备分别向SMF网元发送PDU会话建立/修改请求(PDU session establishment/modification request)消息。
S2902、SMF网元向UPF网元发起N4会话建立流程，并生成第一指示信息。
具体的，SMF网元可以向UPF网元发送N4会话建立/修改请求(N4 session establishment/modification request)消息。UPF网元可以向SMF网元发送N4会话建立/修改响应(N4 session establishment/modification response)消息。N4会话建立/修改响应(N4 session establishment/modification response)消息中可以包括UPF网元的用户面IP地址和用户面端口号。
SMF网元获取第一多播业务的对应的用户面IP地址和用户面端口号后，可以根据第一多播业务对应的用户面IP地址和用户面端口号生成第一指示信息。
S2903、在QoS流建立或修改过程中，SMF网元向RAN网元发送第一指示信息。
具体的，第一指示信息可以携带在PDU会话资源建立请求转移(PDU session resource setup request transfer)消息(也可以理解为N2会话管理信息(N2 SM info))中。
S2904、UPF网元从应用服务器接收至少两个终端设备对应的第一多播业务的数据包，其中包括第一数据包。
该步骤与步骤S2703相同，在此不再重复。
S2905、UPF网元通过第一终端设备对应的第一多播业务的QoS流或UPF网元和RAN之间的与第一多播业务对应的N3公共QoS流向RAN网元发送第一数据包。
也就是说，UPF网元对第一多播业务的数据包进行传输优化。
S2906、RAN网元根据第一指示信息和第一数据包，采用空口组播方式向所述至少两个终端设备发送第二数据包。
该步骤可以参照S1402中第一网元为RAN网元的相关描述，在此不再重复。
如图30所示，该步骤实现了在RAN网元生成第二数据包，并且第二数据包的目的IP地址为公共IP地址。
S2907、所述至少两个终端设备分别根据第二数据包得到各自的第三数据包。
该步骤可以参照步骤S1906，在此不再重复。
下面，在RAN网元已经获取第一指示信息以及公共IP地址的基础上，对RAN网元如何根据第一指示信息和第一数据包发送第二数据包的另一种方式进行描述。在该方式中，UPF网元向RAN网元发送所述至少两个终端设备对应的第一多播业务的数 据包。
如图31所示，本申请实施例提供了另一种该数据包处理方法，该方法包括：
步骤S3101-S3103与图29中的步骤S2901-S2903相同，在此不再重复。
S3104、UPF网元以单播的方式向RAN网元发送各个终端设备对应的数据包。
相应地，RAN网元从UPF网元接收各个终端设备对应的第一多播业务的数据包。也就是说，UPF网元不对第一多播业务的数据包进行传输优化。
步骤S3105-S3107与步骤S2905-S2907相同，在此不再重复。
如图32所示，该步骤实现了在RAN网元生成第二数据包，并且第二数据包的目的IP地址为公共IP地址。
可以理解的是，以上各个实施例中，由终端设备实现的方法和/或步骤，也可以由可用于终端设备的部件(例如芯片或者电路)实现，由网络设备实现的方法和/或步骤，也可以由可用于网络设备的部件实现。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。相应的，本申请实施例还提供了通信装置，该通信装置用于实现上述各种方法。该通信装置可以为上述方法实施例中的终端设备，或者包含上述终端设备的装置，或者为终端设备内的芯片或功能模块；或者，该通信装置可以为上述方法实施例中的网络设备，或者包含上述网络设备的装置，或者为网络设备内的芯片或功能模块。可以理解的是，该通信装置为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。
本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法实施例对通信装置进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
比如，以通信装置为上述方法实施例中的第一网元、RAN网元或UPF网元为例。图33示出了一种通信装置330的结构示意图。该通信装置330包括处理模块3301和收发模块3302。该通信装置330可以为图14、图21、图23、图24、图25、图26中的第一网元，图19、图20、图27、图29、图31中的RAN网元或UPF网元。处理模块3301也可以称为处理单元，用以实现上述方法实施例中第一网元、RAN网元或UPF网元的处理功能。例如执行图31中的步骤S3105。收发模块3302，也可以称为收发单元，用以实现上述方法实施例中第一网元、RAN网元或UPF网元的收发功能。例如执行图14中的步骤S1401-S1402，图19中的步骤S1902、S1903、S1904、S1905，图20中的步骤S2002、S2003、S2004，图21中的步骤S2106，图23中的步骤S2305，图24中的步骤S2407，图25中的步骤S2507，图26中的步骤S2602，图27中的步骤 S2702、S2703、S2704、S2705，图29中的步骤S2902、S2903、S2904、S2905、S2906，图31中的步骤S3102、S3103、S3104、S3106。收发模块3302可以称为收发电路、收发机、收发器或者通信接口。
示例性的，收发模块3302，用于接收第一指示信息和第一数据包，第一数据包对应第一多播业务，第一数据包的目的互联网协议IP地址为第一终端设备的IP地址；收发模块3302，还用于根据第一指示信息和第一数据包，发送第二数据包，第二数据包的目的IP地址为第一多播业务的公共IP地址，公共IP地址用于向至少两个终端设备传输第一多播业务的数据；其中，第一指示信息用于指示使用第一多播业务的公共IP地址传输第一多播业务的数据。
在一种可能的实施方式中，还包括处理模块3301，收发模块3302，还用于接收第三数据包，第三数据包对应第一多播业务，第三数据包的目的IP地址为第二终端设备的IP地址，第三数据包承载的内容与第一数据包承载的内容相同；处理模块3301，用于丢弃第三数据包。
在一种可能的实施方式中，收发模块3302，具体用于从会话管理功能网元接收第一指示信息。
在一种可能的实施方式中，第一指示信息包括第一多播业务的标识信息和公共IP地址之间的关联关系。
在一种可能的实施方式中，第一指示信息包括第一多播业务的标识信息，而不包括公共IP地址，通信装置还包括处理模块3301：收发模块3302，还用于从会话管理功能网元接收公共IP地址，或者，处理模块3301，用于根据第一多播业务的标识信息，获得公共IP地址。
在一种可能的实施方式中，通信装置为用户面功能网元；收发模块3302，具体用于：根据第一指示信息和第一数据包，向接入网网元发送第二数据包。
在一种可能的实施方式中，通信装置为接入网网元；收发模块3302，具体用于：根据第一指示信息和第一数据包，采用空口组播方式发送第二数据包。
在本实施例中，该通信装置330以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。
在一个简单的实施例中，本领域的技术人员可以想到该通信装置330可以采用图3所示的基站300的形式。
比如，图3所示的基站300中的处理器331可以通过调用存储器332中存储的计算机执行指令，使得基站300执行上述方法实施例中的方法。
具体的，图33中的处理模块3301的功能/实现过程可以通过图3所示的基站300中的处理器331调用存储器332中存储的计算机执行指令来实现。或者，图33中的收发模块3302的功能/实现过程可以通过图3中所示的基站300中的RF电路334来实现。
在另一个简单的实施例中，本领域的技术人员可以想到该通信装置330可以采用图4所示的网络设备400的形式。
比如，图4所示的网络设备400中的处理器401可以通过调用存储器403中存储的计算机执行指令，使得网络设备400执行上述方法实施例中的方法。
具体的，图33中的处理模块3301的功能/实现过程可以通过图4所示的网络设备400中的处理器401调用存储器403中存储的计算机执行指令来实现。或者，图33中的收发模块3302的功能/实现过程可以通过图4中所示的网络设备400中的通信接口404来实现。
由于本实施例提供的通信装置330可执行上述方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
比如，以通信装置为上述方法实施例中的SMF网元为例。图34示出了一种通信装置340的结构示意图。该通信装置340包括处理模块3401和收发模块3402。该通信装置340可以为图15、图19、图20、图21、图23、图24、图25、图26、图27、图29、图31中的SMF网元。处理模块3401也可以称为处理单元，用以实现上述方法实施例中SMF网元的处理功能。例如执行图15中的步骤S1501，图19中的步骤S1901，图20中的步骤S2001。收发模块3402，也可以称为收发单元，用以实现上述方法实施例中SMF网元的收发功能。例如执行图15中的步骤S1502，图19中的步骤S1902，图20中的步骤S2002，图21中的步骤S2105、S2106，图23中的步骤S2301、S2304、S2305，图24中的步骤S2406、S2407，图25中的步骤S2506、S2507，图26中的步骤S2601、S2602，图27中的步骤S2701、S2702，图29中的步骤S2901、S2902、S2903，图31中的步骤S3101、S3102、S3103。收发模块3402可以称为收发电路、收发机、收发器或者通信接口。
示例性的，处理模块3401，用于获取第一多播业务的标识信息；收发模块3402，用于根据第一多播业务的标识信息，向第一网元发送第一指示信息；其中，第一指示信息用于指示使用公共IP地址传输第一多播业务的数据，公共IP地址用于向至少两个终端设备传输第一多播业务的数据。
在一种可能的实施方式中，处理模块3401，还用于：获取第一指示信息。
在一种可能的实施方式中，收发模块3402，还用于：向第一网元发送公共IP地址。
在一种可能的实施方式中，第一指示信息包括公共IP地址。
在一种可能的实施方式中，处理模块3401，还用于生成公共IP地址；或者，收发模块3402，还用于从应用服务器接收公共IP地址。
在一种可能的实施方式中，处理模块3401，还用于生成第一多播业务的标识信息，或者，收发模块3402，还用于从应用服务器接收第一多播业务的标识信息。
在本实施例中，该通信装置340以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。
在一个简单的实施例中，本领域的技术人员可以想到该通信装置340可以采用图4所示的网络设备400的形式。
比如，图4所示的网络设备400中的处理器401可以通过调用存储器402中存储的计算机执行指令，使得网络设备400执行上述方法实施例中的方法。
具体的，图34中的处理模块3401的功能/实现过程可以通过图4所示的网络设备400中的处理器401调用存储器403中存储的计算机执行指令来实现。或者，图34中 的收发模块3402的功能/实现过程可以通过图4中所示的网络设备400中的通信接口404来实现。
由于本实施例提供的通信装置340可执行上述方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
比如，以通信装置为上述方法实施例中的应用服务器为例。图35示出了一种通信装置350的结构示意图。该通信装置350包括处理模块3501和收发模块3502。该通信装置200可以为图16、图19、图20、图21、图22、图24、图25、图27、图29、图31中的应用服务器。处理模块3501也可以称为处理单元，用以实现上述方法实施例中应用服务器的处理功能。例如执行图16中的步骤S1601，图21中的步骤S2101，图22中的步骤S2201，图24中的步骤S2401。收发模块3502，也可以称为收发单元，用以实现上述方法实施例中应用服务器的收发功能。例如执行图16中的步骤S1602，图19中的步骤S1903，图20中的步骤S2003，图21中的步骤S2102，图22中的步骤S2201，图24中的步骤S2402、S2404，图25中的步骤S2501，图27中的步骤S2703，图29中的步骤S2901、S2904。收发模块3502可以称为收发电路、收发机、收发器或者通信接口。
示例性的，处理模块3501，用于获取第一多播业务对应的用户面功能网元的用户面互联网协议IP地址和用户面功能网元的用户面端口号；收发模块3502，用于使用用户面IP地址和用户面端口号，向用户面功能网元发送第一数据包和第二数据包，其中，第一数据包和第二数据包均包括第一多播业务的第一数据，第一数据包的目的IP地址为第一终端设备的IP地址，第二数据包的目的IP地址为第二终端设备的IP地址。
在本实施例中，该通信装置350以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到该通信装置350可以采用图4所示的网络设备400的形式。
比如，图4所示的网络设备400中的处理器401可以通过调用存储器402中存储的计算机执行指令，使得网络设备400执行上述方法实施例中的方法。
具体的，图35中的处理模块3501的功能/实现过程可以通过图4所示的网络设备400中的处理器401调用存储器403中存储的计算机执行指令来实现。或者，图35中的收发模块3502的功能/实现过程可以通过图4中所示的网络设备400中的通信接口404来实现。
由于本实施例提供的通信装置350可执行上述方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
比如，以通信装置为上述方法实施例中的终端设备为例。图36示出了一种通信装置360的结构示意图。该通信装置360包括处理模块3601和收发模块3602。该通信装置360可以为图17、图19、图20、图26、图27、图29、图31中的终端设备。处理模块3601也可以称为处理单元，用以实现上述方法实施例中终端设备的处理功能。例如执行图17中的步骤S1702，图19中的步骤S1906，图20中的步骤S2005，图27中的步骤S2706，图29中的步骤S2907，图31中的步骤S3107。收发模块3602，也 可以称为收发单元，用以实现上述方法实施例中终端设备的收发功能。例如执行图17中的步骤S1701，图19中的步骤S1905，图20中的步骤S2004，图26中的步骤S2601，图27中的步骤S2701、S2705，图29中的步骤S2901、S2906，图31中的步骤S3101、S3106。收发模块3602可以称为收发电路、收发机、收发器或者通信接口。
示例性的，收发模块3602，用于接收第一数据包，第一数据包对应第一多播业务，第一数据包的目的互联网协议IP地址为第一多播业务的公共IP地址，公共IP地址用于向至少两个终端设备传输第一多播业务的数据；处理模块3601，用于根据第一数据包得到第二数据包，第二数据包的目的IP地址为终端设备的IP地址。
在一种可能的实施方式中，收发模块3602，还用于接收公共IP地址。
在一种可能的实施方式中，收发模块3602，还用于向会话管理功能网元发送第一消息，第一消息包括第一多播业务的标识信息或者公共IP地址，第一消息用于请求第一多播业务的数据。
在本实施例中，该通信装置360以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到该通信装置360可以采用图2所示的终端设备105的形式。
比如，图2所示的终端设备200中的处理器180可以通过调用存储器120中存储的计算机执行指令，使得终端设备200执行上述方法实施例中的方法。
具体的，图36中的处理模块3601的功能/实现过程可以通过图2所示的终端设备200中的处理器180调用存储器120中存储的计算机执行指令来实现。或者，图36中的收发模块3602的功能/实现过程可以通过图2中所示的终端设备200中的RF电路100来实现。
由于本实施例提供的通信装置360可执行上述方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
本申请实施例还提供了一种通信装置，该通信装置包括处理器、存储器和收发器，处理器与存储器耦合，当处理器执行存储器中的计算机程序或指令时，图14、图21、图23、图24、图25、图26中的第一网元对应的方法被执行，或者，图19、图20、图27、图29、图31中的RAN网元对应的方法被执行，或者，图19、图20、图27、图29、图31中的UPF网元对应的方法被执行。
本申请实施例还提供了一种通信装置，该通信装置包括处理器、存储器和通信接口，处理器与存储器耦合，当处理器执行存储器中的计算机程序或指令时，图15、图19、图20、图21、图23、图24、图25、图26、图27、图29、图31中的SMF网元对应的方法被执行。
本申请实施例还提供了一种通信装置，该通信装置包括处理器、存储器和通信接口，处理器与存储器耦合，当处理器执行存储器中的计算机程序或指令时，图16、图19、图20、图21、图22、图24、图25、图27、图29、图31中的应用服务器对应的方法被执行。
本申请实施例还提供了一种通信装置，该通信装置包括处理器、存储器和RF电 路，处理器与存储器耦合，当处理器执行存储器中的计算机程序或指令时，图17、图19、图20、图26、图27、图29、图31中的终端设备对应的方法被执行。
本申请实施例还提供了一种芯片，包括：处理器和接口，用于从存储器中调用并运行存储器中存储的计算机程序，执行图14、图21、图23、图24、图25、图26中的第一网元对应的方法，或者，执行图19、图20、图27、图29、图31中的RAN网元对应的方法，或者，执行图19、图20、图27、图29、图31中的UPF网元对应的方法。
本申请实施例还提供了一种芯片，包括：处理器和接口，用于从存储器中调用并运行存储器中存储的计算机程序，执行图15、图19、图20、图21、图23、图24、图25、图26、图27、图29、图31中的SMF网元对应的方法。
本申请实施例还提供了一种芯片，包括：处理器和接口，用于从存储器中调用并运行存储器中存储的计算机程序，执行图16、图19、图20、图21、图22、图24、图25、图27、图29、图31中的应用服务器对应的方法。
本申请实施例还提供了一种芯片，包括：处理器和接口，用于从存储器中调用并运行存储器中存储的计算机程序，执行图17、图19、图20、图26、图27、图29、图31中的终端设备对应的方法。
本申请实施例还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当该指令在计算机或处理器上运行时，使得计算机或处理器执行图14、图21、图23、图24、图25、图26中的第一网元对应的方法，或者，执行图19、图20、图27、图29、图31中的RAN网元对应的方法，或者，执行图19、图20、图27、图29、图31中的UPF网元对应的方法。
本申请实施例还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当该指令在计算机或处理器上运行时，使得计算机或处理器执行图15、图19、图20、图21、图23、图24、图25、图26、图27、图29、图31中的SMF网元对应的方法。
本申请实施例还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当该指令在计算机或处理器上运行时，使得计算机或处理器执行图16、图19、图20、图21、图22、图24、图25、图27、图29、图31中的应用服务器对应的方法。
本申请实施例还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当该指令在计算机或处理器上运行时，使得计算机或处理器执行图17、图19、图20、图26、图27、图29、图31中的终端设备对应的方法。
本申请实施例还提供了一种包含指令的计算机程序产品，当指令在计算机或处理器上运行时，使得计算机或处理器执行图14、图21、图23、图24、图25、图26中的第一网元对应的方法，或者，执行图19、图20、图27、图29、图31中的RAN网元对应的方法，或者，执行图19、图20、图27、图29、图31中的UPF网元对应的方法。
本申请实施例还提供了一种包含指令的计算机程序产品，当指令在计算机或处理器上运行时，使得计算机或处理器执行图15、图19、图20、图21、图23、图24、图25、图26、图27、图29、图31中的SMF网元对应的方法。
本申请实施例还提供了一种包含指令的计算机程序产品，当指令在计算机或处理器上运行时，使得计算机或处理器执行图16、图19、图20、图21、图22、图24、图25、图27、图29、图31中的应用服务器对应的方法。
本申请实施例还提供了一种包含指令的计算机程序产品，当指令在计算机或处理器上运行时，使得计算机或处理器执行图17、图19、图20、图26、图27、图29、图31中的终端设备对应的方法。
本申请实施例提供了一种芯片系统，该芯片系统包括处理器，用于通信装置执行图14、图21、图23、图24、图25、图26中的第一网元对应的方法，或者，执行图19、图20、图27、图29、图31中的RAN网元对应的方法，或者，执行图19、图20、图27、图29、图31中的UPF网元对应的方法。
本申请实施例提供了一种芯片系统，该芯片系统包括处理器，用于通信装置执行图15、图19、图20、图21、图23、图24、图25、图26、图27、图29、图31中的SMF网元对应的方法。
本申请实施例提供了一种芯片系统，该芯片系统包括处理器，用于通信装置执行图16、图19、图20、图21、图22、图24、图25、图27、图29、图31中的应用服务器对应的方法。
本申请实施例提供了一种芯片系统，该芯片系统包括处理器，用于通信装置执行图17、图19、图20、图26、图27、图29、图31中的终端设备对应的方法。
需要说明的是，上述芯片系统还包括存储器，该存储器，用于保存终端设备必要的程序指令和数据。该芯片系统，可以包括芯片，集成电路，也可以包含芯片和其他分立器件，本申请实施例对此不作具体限定。
其中，本申请提供的通信装置、芯片、计算机存储介质、计算机程序产品或芯片系统均用于执行上文所述的方法，因此，其所能达到的有益效果可参考上文所提供的实施方式中的有益效果，此处不再赘述。
本申请实施例涉及的处理器可以是一个芯片。例如，可以是现场可编程门阵列(field programmable gate array，FPGA)，可以是专用集成芯片(application specific integrated circuit，ASIC)，还可以是系统芯片(system on chip，SoC)，还可以是中央处理器(central processor unit，CPU)，还可以是网络处理器(network processor，NP)，还可以是数字信号处理电路(digital signal processor，DSP)，还可以是微控制器(micro controller unit，MCU)，还可以是可编程控制器(programmable logic device，PLD)或其他集成芯片。
本申请实施例涉及的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、 双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、设备和方法，可以通过其它的方式实现。例如，以上所描述的设备实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，设备或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(Digital Subscriber Line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体 介质(例如固态硬盘(Solid State Disk，SSD))等。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (34)

  1. 一种数据包处理方法，其特征在于，包括：
    第一网元接收第一指示信息和第一数据包，所述第一数据包对应第一多播业务，所述第一数据包的目的互联网协议IP地址为第一终端设备的IP地址；
    所述第一网元根据所述第一指示信息和所述第一数据包，发送第二数据包，所述第二数据包的目的IP地址为所述第一多播业务的公共IP地址，所述公共IP地址用于向至少两个终端设备传输所述第一多播业务的数据；
    其中，所述第一指示信息用于指示使用所述第一多播业务的公共IP地址传输所述第一多播业务的数据。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述第一网元接收第三数据包，所述第三数据包对应所述第一多播业务，所述第三数据包的目的IP地址为第二终端设备的IP地址，所述第三数据包承载的内容与所述第一数据包承载的内容相同；
    所述第一网元丢弃所述第三数据包。
  3. 根据权利要求1所述的方法，其特征在于，所述第一网元接收第一指示信息包括：
    所述第一网元从会话管理功能网元接收所述第一指示信息。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述第一指示信息包括所述第一多播业务的标识信息和所述公共IP地址之间的关联关系。
  5. 根据权利要求1-3任一项所述的方法，其特征在于，所述第一指示信息包括所述第一多播业务的标识信息，而不包括所述公共IP地址，所述方法还包括：
    所述第一网元从会话管理功能网元接收所述公共IP地址，或者，
    所述第一网元根据所述第一多播业务的标识信息，获得所述公共IP地址。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，所述第一网元为用户面功能网元；所述第一网元根据所述第一指示信息和所述第一数据包，发送第二数据包，包括：
    所述第一网元根据所述第一指示信息和所述第一数据包，向接入网网元发送所述第二数据包。
  7. 根据权利要求1-5任一项所述的方法，所述第一网元为接入网网元；所述第一网元根据所述第一指示信息和所述第一数据包，发送第二数据包，包括：
    所述第一网元根据所述第一指示信息和所述第一数据包，采用空口组播方式发送所述第二数据包。
  8. 一种数据包处理方法，其特征在于，包括：
    获取第一多播业务的标识信息；
    根据所述第一多播业务的标识信息，向第一网元发送第一指示信息；
    其中，所述第一指示信息用于指示使用公共IP地址传输所述第一多播业务的数据，所述公共IP地址用于向至少两个终端设备传输所述第一多播业务的数据。
  9. 根据权利要求8所述的方法，其特征在于，所述方法还包括：
    获取所述第一指示信息。
  10. 根据权利要求8或9所述的方法，其特征在于，所述方法还包括：
    向所述第一网元发送所述公共IP地址。
  11. 根据权利要求8或9所述的方法，其特征在于，所述第一指示信息包括所述公共IP地址。
  12. 根据权利要求8-11任一项所述的方法，其特征在于，所述方法还包括：
    生成所述公共IP地址；或者，
    从应用服务器接收所述公共IP地址。
  13. 根据权利要求8-12任一项所述的方法，其特征在于，所述获取第一多播业务的标识信息，包括：
    生成所述第一多播业务的标识信息，或者，从应用服务器接收所述第一多播业务的标识信息。
  14. 一种数据包处理方法，其特征在于，包括：
    获取第一多播业务对应的用户面功能网元的用户面互联网协议IP地址和所述用户面功能网元的用户面端口号；
    使用所述用户面IP地址和所述用户面端口号，向所述用户面功能网元发送第一数据包和第二数据包，其中，所述第一数据包和所述第二数据包均包括所述第一多播业务的第一数据，所述第一数据包的目的IP地址为第一终端设备的IP地址，所述第二数据包的目的IP地址为第二终端设备的IP地址。
  15. 一种数据包处理方法，其特征在于，包括：
    终端设备接收第一数据包，所述第一数据包对应第一多播业务，所述第一数据包的目的互联网协议IP地址为所述第一多播业务的公共IP地址，所述公共IP地址用于向至少两个终端设备传输所述第一多播业务的数据；
    根据所述第一数据包得到第二数据包，所述第二数据包的目的IP地址为所述终端设备的IP地址。
  16. 根据权利要求15所述的方法，其特征在于，所述方法还包括：
    所述终端设备接收所述公共IP地址。
  17. 根据权利要求15所述的方法，其特征在于，所述方法还包括：
    所述终端设备向会话管理功能网元发送第一消息，所述第一消息包括所述第一多播业务的标识信息或者所述公共IP地址，所述第一消息用于请求所述第一多播业务的数据。
  18. 一种通信装置，其特征在于，包括：
    收发模块，用于接收第一指示信息和第一数据包，所述第一数据包对应第一多播业务，所述第一数据包的目的互联网协议IP地址为第一终端设备的IP地址；
    所述收发模块，还用于根据所述第一指示信息和所述第一数据包，发送第二数据包，所述第二数据包的目的IP地址为所述第一多播业务的公共IP地址，所述公共IP地址用于向至少两个终端设备传输所述第一多播业务的数据；
    其中，所述第一指示信息用于指示使用所述第一多播业务的公共IP地址传输所述第一多播业务的数据。
  19. 根据权利要求18所述的通信装置，其特征在于，还包括处理模块，
    所述收发模块，还用于接收第三数据包，所述第三数据包对应所述第一多播业务，所述第三数据包的目的IP地址为第二终端设备的IP地址，所述第三数据包承载的内容与所述第一数据包承载的内容相同；
    所述处理模块，用于丢弃所述第三数据包。
  20. 根据权利要求18所述的通信装置，其特征在于，
    所述收发模块，具体用于从会话管理功能网元接收所述第一指示信息。
  21. 根据权利要求18-20任一项所述的通信装置，其特征在于，所述第一指示信息包括所述第一多播业务的标识信息和所述公共IP地址之间的关联关系。
  22. 根据权利要求18-20任一项所述的通信装置，其特征在于，所述第一指示信息包括所述第一多播业务的标识信息，而不包括所述公共IP地址，所述通信装置还包括处理模块：
    所述收发模块，还用于从会话管理功能网元接收所述公共IP地址，或者，
    所述处理模块，用于根据所述第一多播业务的标识信息，获得所述公共IP地址。
  23. 根据权利要求18-22任一项所述的通信装置，其特征在于，所述通信装置为用户面功能网元；所述收发模块，具体用于：
    根据所述第一指示信息和所述第一数据包，向接入网网元发送所述第二数据包。
  24. 根据权利要求18-22任一项所述的通信装置，所述通信装置为接入网网元；所述收发模块，具体用于：
    根据所述第一指示信息和所述第一数据包，采用空口组播方式发送所述第二数据包。
  25. 一种通信装置，其特征在于，包括：
    处理模块，用于获取第一多播业务的标识信息；
    收发模块，用于根据所述第一多播业务的标识信息，向第一网元发送第一指示信息；
    其中，所述第一指示信息用于指示使用公共IP地址传输所述第一多播业务的数据，所述公共IP地址用于向至少两个终端设备传输所述第一多播业务的数据。
  26. 根据权利要求25所述的通信装置，其特征在于，所述处理模块，还用于：
    获取所述第一指示信息。
  27. 根据权利要求25或26所述的通信装置，其特征在于，所述收发模块，还用于：
    向所述第一网元发送所述公共IP地址。
  28. 根据权利要求25或26所述的通信装置，其特征在于，所述第一指示信息包括所述公共IP地址。
  29. 根据权利要求25-28任一项所述的通信装置，其特征在于，
    所述处理模块，还用于生成所述公共IP地址；或者，
    所述收发模块，还用于从应用服务器接收所述公共IP地址。
  30. 根据权利要求25-29任一项所述的通信装置，其特征在于，
    所述处理模块，还用于生成所述第一多播业务的标识信息，或者，所述收发模块，还用于从应用服务器接收所述第一多播业务的标识信息。
  31. 一种通信装置，其特征在于，包括：
    处理模块，用于获取第一多播业务对应的用户面功能网元的用户面互联网协议IP地址和所述用户面功能网元的用户面端口号；
    收发模块，用于使用所述用户面IP地址和所述用户面端口号，向所述用户面功能网元发送第一数据包和第二数据包，其中，所述第一数据包和所述第二数据包均包括所述第一多播业务的第一数据，所述第一数据包的目的IP地址为第一终端设备的IP地址，所述第二数据包的目的IP地址为第二终端设备的IP地址。
  32. 一种通信装置，其特征在于，包括：
    收发模块，用于接收第一数据包，所述第一数据包对应第一多播业务，所述第一数据包的目的互联网协议IP地址为所述第一多播业务的公共IP地址，所述公共IP地址用于向至少两个终端设备传输所述第一多播业务的数据；
    处理模块，用于根据所述第一数据包得到第二数据包，所述第二数据包的目的IP地址为所述终端设备的IP地址。
  33. 根据权利要求32所述的通信装置，其特征在于，
    所述收发模块，还用于接收所述公共IP地址。
  34. 根据权利要求32所述的通信装置，其特征在于，
    所述收发模块，还用于向会话管理功能网元发送第一消息，所述第一消息包括所述第一多播业务的标识信息或者所述公共IP地址，所述第一消息用于请求所述第一多播业务的数据。
PCT/CN2019/127674 2019-12-23 2019-12-23 数据包处理方法和装置 WO2021127946A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/127674 WO2021127946A1 (zh) 2019-12-23 2019-12-23 数据包处理方法和装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/127674 WO2021127946A1 (zh) 2019-12-23 2019-12-23 数据包处理方法和装置

Publications (1)

Publication Number Publication Date
WO2021127946A1 true WO2021127946A1 (zh) 2021-07-01

Family

ID=76573496

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/127674 WO2021127946A1 (zh) 2019-12-23 2019-12-23 数据包处理方法和装置

Country Status (1)

Country Link
WO (1) WO2021127946A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109391909A (zh) * 2017-08-14 2019-02-26 华为技术有限公司 一种组播方法及装置
CN109699013A (zh) * 2017-10-24 2019-04-30 华为技术有限公司 一种通信系统、通信方法及其装置
CN109769150A (zh) * 2017-11-09 2019-05-17 华为技术有限公司 一种传输组播业务的方法和设备
US20190182875A1 (en) * 2017-12-08 2019-06-13 Comcast Cable Communications, Llc User Plane Function Selection For Isolated Network Slice
CN110519172A (zh) * 2018-05-21 2019-11-29 华为技术有限公司 无线通信方法和设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109391909A (zh) * 2017-08-14 2019-02-26 华为技术有限公司 一种组播方法及装置
CN109699013A (zh) * 2017-10-24 2019-04-30 华为技术有限公司 一种通信系统、通信方法及其装置
CN109769150A (zh) * 2017-11-09 2019-05-17 华为技术有限公司 一种传输组播业务的方法和设备
US20190182875A1 (en) * 2017-12-08 2019-06-13 Comcast Cable Communications, Llc User Plane Function Selection For Isolated Network Slice
CN110519172A (zh) * 2018-05-21 2019-11-29 华为技术有限公司 无线通信方法和设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "IPTV Solution update and interim conclusion", 3GPP DRAFT; S2-1810715-IPTV SOLUTION UPDATE AND INTERIM CONCLUSION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Dongguan, China; 20181015 - 20181019, 9 October 2018 (2018-10-09), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051539666 *

Similar Documents

Publication Publication Date Title
US10973000B2 (en) Message sending method and apparatus
CN111200791B (zh) 群组通信方法、设备及系统
JP7183416B2 (ja) 時間依存ネットワーキング通信方法及び装置
CN111586860B (zh) 一种通信方法及装置
WO2021031562A1 (zh) 一种获取信息的方法及装置
US20230019215A1 (en) TSC-5G QoS MAPPING WITH CONSIDERATION OF ASSISTANCE TRAFFIC INFORMATION AND PCC RULES FOR TSC TRAFFIC MAPPING AND 5G QoS FLOWS BINDING
WO2022105897A1 (zh) 业务路径建立方法、通信装置及存储介质
WO2021135650A1 (zh) 通信方法及装置
WO2021254001A1 (zh) 会话建立方法、装置、系统及计算机存储介质
JP2023531312A (ja) データ伝送方法および装置
WO2016188128A1 (zh) 一种能力开放方法及系统、能力开放功能实体
WO2022017285A1 (zh) 报文转发方法、装置及系统
US20220263879A1 (en) Multicast session establishment method and network device
JP2023502849A (ja) データ伝送方法及び装置、ゲートウェイ、チップ、並びに記憶媒体
WO2022012361A1 (zh) 一种通信方法及装置
WO2021174377A1 (zh) 切换方法和通信装置
JP6044020B2 (ja) データパケット処理の方法、システム、およびデバイス
WO2023284551A1 (zh) 通信方法、装置和系统
WO2022267652A1 (zh) 一种通信方法、通信装置及通信系统
WO2023102680A1 (zh) 拥塞控制方法、装置、设备、介质、芯片、产品及程序
WO2021127946A1 (zh) 数据包处理方法和装置
CN114424498B (zh) 数据传输方法、装置、系统和存储介质
WO2021169309A1 (zh) 通信方法、装置及系统
WO2024051313A1 (zh) 通信资源管理方法、装置、系统及存储介质
WO2023116356A1 (zh) 信息配置方法、装置、相关设备及存储介质

Legal Events

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

Ref document number: 19957381

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19957381

Country of ref document: EP

Kind code of ref document: A1