WO2019104857A1 - 一种报文组播、报文广播方法及设备 - Google Patents

一种报文组播、报文广播方法及设备 Download PDF

Info

Publication number
WO2019104857A1
WO2019104857A1 PCT/CN2018/074025 CN2018074025W WO2019104857A1 WO 2019104857 A1 WO2019104857 A1 WO 2019104857A1 CN 2018074025 W CN2018074025 W CN 2018074025W WO 2019104857 A1 WO2019104857 A1 WO 2019104857A1
Authority
WO
WIPO (PCT)
Prior art keywords
entity
upf entity
terminal device
multicast
identifier
Prior art date
Application number
PCT/CN2018/074025
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 JP2018548178A priority Critical patent/JP6983169B2/ja
Publication of WO2019104857A1 publication Critical patent/WO2019104857A1/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
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a packet multicast, packet broadcast method, and device.
  • the user plane function (UPF) entity that sinks to the edge has the capability of multimedia broadcast and multicast services (MBMS), and can be used as an edge gateway (local gateway, local GW).
  • MBMS multimedia broadcast and multicast services
  • the base station communicates, and the UPF entity can also communicate with the core network control plane function (CPF) entity.
  • CPF core network control plane function
  • multiple UPF entities are capable of communicating with a V2X server (V2X server).
  • the core requirement of the V2X communication is that the service is low-latency.
  • the V2X server needs to process packets from multiple UPF entities and send packets to multiple UPF entities.
  • the processing power of the V2X server is likely to become a performance bottleneck for V2X.
  • another scenario is proposed, that is, the V2X server and the UPF entity are both sunk to the edge, for example, a V2X server is set for each UPF entity, such a V2X server can be called a local V2X server.
  • the UPF entity that sinks to the edge may be referred to as an edge UPF entity.
  • a local V2X server basically only needs to be responsible for communicating with the corresponding edge UPF entity, which has lower performance requirements for the local V2X server and can also reduce the delay.
  • the V2X server can communicate with multiple edge UPF entities. However, if the V2X server is sunk to the edge to form a local V2X server, then a local V2X server can only have an edge UPF corresponding to the local V2X server. Entity communication, but not communication with other edge UPF entities, will increase the latency of network communication.
  • the embodiment of the present application provides a packet multicast and packet broadcast method and device, which are used to reduce delay.
  • a message multicast method is provided, which can be performed by a CPF entity.
  • the method includes: the CPF entity receives a multicast group join request, the multicast group join request is used by the first terminal device to request to join the multicast group indicated by the multicast address; and the CPF entity adds the terminal device to the a multicast group; the CPF entity generates a multicast forwarding route whose destination address is the multicast address; the CPF entity sends the multicast forwarding route to at least one UPF entity, where the at least one UPF entity includes the The UPF entity where all the terminal devices included in the multicast group are located.
  • the CPF entity may generate a multicast forwarding route, and send the multicast forwarding route to the at least one UPF entity, so that at least one UPF entity can directly forward the route according to the multicast forwarding route.
  • the received multicast packet is forwarded to the corresponding device in the multicast group indicated by the multicast address. If the multicast group includes devices under other UPF entities, the UPF entity can forward the route according to the multicast forwarding.
  • the packet is sent to the device in the other UPF entity.
  • the V2X server is sunk to the edge, the UPF entity can directly forward the packet without the participation of the local V2X server.
  • the delay of network communication is small. Moreover, there is no need to deploy a local V2X server for packet forwarding, which can reduce the deployment amount of the local V2X server, effectively reduce the cost, and reduce the complexity of the forwarding path of the packet.
  • the CPF entity receives a multicast group establishment request, the multicast group establishment request carries formation information, and the formation indicated by the formation information includes at least one terminal device, and the multicast group establishment request For requesting a multicast address for the formation, the at least one terminal device includes the first terminal device; the CPF entity assigns the multicast address to the formation.
  • the CPF entity After receiving a multicast group establishment request, the CPF entity can create a multicast group and generate a multicast address. At least one terminal device can belong to the multicast group. The multicast packets in a multicast group can pass through the UPF entity. To achieve multicast, the communication delay is small.
  • the CPF entity determines that the second terminal device performs cell handover, and the cell after the second terminal device handover and the cell before the handover of the terminal device belong to different base stations, and the second The terminal device belongs to the multicast group; the CPF entity updates the multicast forwarding route; the CPF entity sends the updated multicast forwarding route to the at least one UPF entity, and sends the The UPF entity where the terminal device is switched.
  • the multicast route of the multicast group changes. Then, the CPF entity can update the multicast forwarding route in time, and send the updated multicast forwarding route to the UPF entity, so that the UPF entity can forward the packet according to the updated multicast forwarding route, thereby improving the success rate of packet forwarding.
  • a second aspect provides a packet broadcast method, where the method is performed by a first UPF entity, and the first UPF entity is an edge UPF entity.
  • the method includes: the first UPF entity receives the first packet; the first UPF entity determines, according to the destination address carried in the first packet, that the first packet is a broadcast packet, and the first UPF The entity determines that the first identifier carried in the first packet is an authorized identifier, where the first identifier is an identifier of the terminal device that sends the first packet, or is a service flow to which the first packet belongs.
  • the flow identifier; the first UPF entity broadcasts the first packet.
  • the embodiment of the present application provides a low-latency broadcast capability that does not require the participation of the V2X server. As long as the corresponding identifier is authorized, the UPF entity can directly implement the broadcast of the packet, and the forwarding delay can be better reduced. And because the V2X server is not required to participate in the broadcast, the deployment amount of the V2X server can be reduced, and the cost can be effectively reduced.
  • the first UPF entity receives a notification message from a CPF entity, the notification message is used to indicate that the first identifier is the authorized identifier; and the first UPF entity is in accordance with the notification The message determines that the first identifier is the authorized identifier, and the first UPF entity directly broadcasts a broadcast packet carrying the authorized identifier.
  • a message broadcast method which can be performed by a CPF entity.
  • the method includes: the CPF entity receives a broadcast permission request, and the broadcast permission request is used to request to directly broadcast a broadcast message carrying the first identifier by using the first UPF entity, where the first identifier is a terminal device that sends the broadcast packet And the identifier of the traffic of the service flow to which the broadcast packet belongs; the CPF entity sends a notification message to the first UPF entity, where the notification message is used to indicate that the first identifier is the authorized The identifier, where the first UPF entity directly broadcasts a broadcast message carrying the authorized identifier.
  • the CPF entity can authorize the corresponding identifier and notify the UPF entity. After receiving the notification message sent by the CPF entity, the UPF entity can determine which identifiers are authorized identifiers. The UPF entity can directly broadcast the broadcast packet carrying the authorized identifier, eliminating the need to broadcast through the V2X server, shortening the path of packet broadcast, and reducing the communication delay.
  • the first UPF entity receives the first packet, where the first UPF entity receives the first packet from a terminal device served by the first UPF entity, or the first The UPF entity receives the first message from the second UPF entity.
  • the first packet may be sent by the terminal device to the first UPF entity, or may be sent by the second UPF entity to the first UPF entity, for example, the terminal device under the second UPF entity sends the second UPF entity,
  • the second UPF entity is sent to the first UPF entity, so that broadcast messages of the terminal devices under other UPF entities can be broadcasted under the UPF entity, and the UPF entities can directly communicate without using the V2X server or the core network. Implement communication and reduce communication delay.
  • the first UPF entity determines that the temporary mobility group identifier requested by the first UPF entity further includes an identifier of the second UPF entity; the first UPF entity to the second The UPF entity sends a multicast request message, and is used to request that the second UPF entity join the same multicast group.
  • the UPF entities in a multicast group can communicate with each other, so that one of the UPF entities can also send broadcast packets to other UPF entities for broadcast.
  • the communication delay is small and the broadcast range is large.
  • a CPF entity has the functionality to implement the CPF entity in the above method design. These functions can be implemented in hardware or in software by executing the corresponding software.
  • the hardware or software includes one or more units corresponding to the functions described above.
  • the specific structure of the CPF entity may include a transceiver and a processor.
  • the processor and transceiver may perform the respective functions of the methods provided by any of the possible aspects of the first aspect or the first aspect described above.
  • a UPF entity has the functionality to implement the UPF entity in the above method design. These functions can be implemented in hardware or in software by executing the corresponding software.
  • the hardware or software includes one or more units corresponding to the functions described above.
  • the specific structure of the UPF entity may include a transceiver and a processor.
  • the processor and transceiver may perform the respective functions of the methods provided by any of the possible aspects of the second aspect or the second aspect described above.
  • a CPF entity has the functionality to implement the CPF entity in the above method design. These functions can be implemented in hardware or in software by executing the corresponding software.
  • the hardware or software includes one or more units corresponding to the functions described above.
  • the specific structure of the CPF entity may include a transceiver and a processor.
  • the processor and transceiver may perform the respective functions of the methods provided by any of the possible aspects of the third or third aspect above.
  • a CPF entity has the functionality to implement the CPF entity in the above method design. These functions can be implemented in hardware or in software by executing the corresponding software.
  • the hardware or software includes one or more units corresponding to the functions described above.
  • the specific structure of the CPF entity may include a transceiver module and a processing module.
  • the processing module and the transceiver module may perform the respective functions of the methods provided by any of the possible aspects of the first aspect or the first aspect described above.
  • a UPF entity has the functionality to implement the UPF entity in the above method design. These functions can be implemented in hardware or in software by executing the corresponding software.
  • the hardware or software includes one or more units corresponding to the functions described above.
  • the specific structure of the UPF entity may include a transceiver module and a processing module.
  • the processing module and the transceiver module may perform the respective functions of the methods provided by any of the possible aspects of the second aspect or the second aspect described above.
  • a CPF entity has the functionality to implement the CPF entity in the above method design. These functions can be implemented in hardware or in software by executing the corresponding software.
  • the hardware or software includes one or more units corresponding to the functions described above.
  • the specific structure of the CPF entity may include a transceiver module and a processing module.
  • the processing module and the transceiver module may perform the respective functions of the methods provided by any of the possible aspects of the third aspect or the third aspect described above.
  • a communication device may be a CPF entity in the above method design, or a chip disposed in a CPF entity.
  • the communication device includes a memory for storing computer executable program code, and a processor coupled to the memory.
  • the program code stored in the memory includes instructions that, when executed by the processor, cause the communication device to perform the method performed by the CPF entity in any of the possible aspects of the first aspect or the first aspect described above.
  • a communication device may be a UPF entity in the above method design or a chip disposed in the UPF entity.
  • the communication device includes a memory for storing computer executable program code, and a processor coupled to the memory.
  • the program code stored in the memory includes instructions which, when executed by the processor, cause the communication device to perform the method performed by the UPF entity in any of the possible designs of the second aspect or the second aspect above.
  • a communication device may be a CPF entity in the above method design, or a chip disposed in a CPF entity.
  • the communication device includes a memory for storing computer executable program code, and a processor coupled to the memory.
  • the program code stored in the memory includes instructions which, when executed by the processor, cause the communication device to perform the method performed by the CPF entity in any of the possible aspects of the third aspect or the third aspect above.
  • a communication system comprising the UPF entity as described in the fifth aspect, and the CPF entity as described in the sixth aspect.
  • a computer storage medium stores instructions that, when run on a computer, cause the computer to perform any one of the first aspect or the first aspect of the first aspect The method described in the above.
  • a computer storage medium stores instructions that, when run on a computer, cause the computer to perform any of the possible aspects of the second aspect or the second aspect described above The method described in the above.
  • a computer storage medium stores instructions that, when run on a computer, cause the computer to perform any of the possible aspects of the third aspect or the third aspect described above The method described in the above.
  • a seventeenth aspect a computer program product comprising instructions, wherein instructions stored in a computer program product, when executed on a computer, cause the computer to perform any of the first aspect or the first aspect described above The method described in the design.
  • a computer program product comprising instructions for storing instructions for causing a computer to perform any one of the second aspect or the second aspect described above when executed on a computer The method described in the design.
  • a nineteenth aspect a computer program product comprising instructions, wherein the computer program product stores instructions that, when run on a computer, cause the computer to perform any one of the third aspect or the third aspect described above The method described in the design.
  • the UPF entity can directly forward the packet without the participation of the local V2X server, thereby implementing information exchange between the UPF entities and reducing the delay of the network communication. .
  • the UPF entity can directly forward the packet without the participation of the local V2X server, thereby implementing information exchange between the UPF entities and reducing the delay of the network communication.
  • there is no need to deploy a local V2X server for packet forwarding which can reduce the deployment amount of the local V2X server, effectively reduce the cost, and reduce the complexity of the forwarding path of the packet.
  • FIG. 1 is a schematic diagram of an application scenario of V2X in the prior art
  • FIG. 2 is a schematic diagram of an application scenario according to an embodiment of the present application.
  • FIG. 3 is a schematic diagram of another application scenario according to an embodiment of the present application.
  • FIG. 4 is a flowchart of a packet multicast method according to an embodiment of the present disclosure.
  • FIG. 5 is a flowchart of a method for updating a multicast route according to an embodiment of the present application
  • FIG. 6 is a flowchart of a packet multicast method according to an embodiment of the present disclosure.
  • FIG. 7 is a flowchart of a packet broadcast method according to an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a CPF entity according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of a UPF entity according to an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a CPF entity according to an embodiment of the present disclosure.
  • 11A-11B are schematic structural diagrams of a communication apparatus according to an embodiment of the present application.
  • LTE Long Term Evolution
  • 5G fifth generation mobile communication systems
  • a terminal device including a device that provides voice and/or data connectivity to a user, for example, may include a handheld device having a wireless connection function, or a processing device connected to a wireless modem.
  • the terminal device can communicate with the core network via a radio access network (RAN) to exchange voice and/or data with the RAN.
  • the terminal device may include a user equipment (UE), a wireless terminal device, a mobile terminal device, a subscriber unit, a subscriber station, a mobile station, a mobile station, and a remote station.
  • Remote station access point (AP), remote terminal, access terminal, user terminal, user agent, or user Equipment (user device) and so on.
  • a mobile phone or "cellular" phone
  • a computer with a mobile terminal device a portable, pocket, handheld, computer built-in or in-vehicle mobile device, smart wearable device, and the like.
  • PCS personal communication service
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • smart watches smart helmets, smart glasses, smart bracelets, and other equipment.
  • restricted devices such as devices with lower power consumption, or devices with limited storage capacity, or devices with limited computing capabilities. Examples include information sensing devices such as bar code, radio frequency identification (RFID), sensors, global positioning system (GPS), and laser scanners.
  • RFID radio frequency identification
  • GPS global positioning system
  • the terminal device may further include a V2X device, for example, an onboard unit (OBU) in the vehicle, and hereinafter, the terminal device is a V2X device as an example.
  • a V2X device for example, an onboard unit (OBU) in the vehicle
  • OBU onboard unit
  • An access network device for example, including a base station (e.g., an access point), can refer to a device in the access network that communicates over the air interface with the wireless terminal over one or more sectors.
  • the base station can be used to convert the received air frame to an Internet Protocol (IP) packet as a router between the terminal and the rest of the access network, wherein the remainder of the access network can include an IP network.
  • IP Internet Protocol
  • the base station can also coordinate attribute management of the air interface.
  • the base station may include an evolved base station (eNB or e-NodeB, evolved Node B) in an LTE system or an evolved LTE system (LTE-A), or a small base station in an LTE system or an LTE-A system (micro/pico eNB), or may include a next generation node B (gNB) in the NR system, or a transmission point (TP), or a transmission and receiver point (transmission and receiver point, TRP), etc., is not limited by the embodiment of the present invention.
  • eNB or e-NodeB, evolved Node B in an LTE system or an evolved LTE system (LTE-A)
  • LTE-A evolved LTE system
  • micro/pico eNB small base station in an LTE system
  • gNB next generation node B
  • TP transmission point
  • TRP transmission and receiver point
  • the core network device includes, for example, a Mobility Management Entity (MME), a Broadcast Multicast Service Center (BMSC), or an MBMS-GW, or may also include a 5G new radio (NR) system.
  • MME Mobility Management Entity
  • BMSC Broadcast Multicast Service Center
  • NR 5G new radio
  • CPF entities CPF entities or UPF entities.
  • V2X vehicles can communicate by vehicle to vehicle (V2V) or vehicle to roadside infrastructure (V2I), or communication between vehicles and pedestrians (vehicle to Pedestrian, V2P), or vehicle to network (V2N) to obtain road condition information or receive information in time.
  • V2X communication can be collectively referred to as V2X communication.
  • V2V and V2I Take the most common V2V and V2I as an example: the vehicle can communicate with its surrounding vehicles by V2V communication, and its own speed, direction of travel, specific position, emergency brakes, etc., and the surrounding vehicles obtain the information to make the driver It is better to perceive the traffic conditions outside the line of sight, so that the dangerous situation can be pre-judged in advance, and then timely avoidance can be made.
  • the roadside infrastructure can also provide various types of service information and data network access for vehicles, and functions such as non-stop charging and in-vehicle entertainment greatly improve traffic intelligence.
  • the network used by V2X communication is generally referred to as an Internet of Vehicles.
  • MEC Mobile edge computing
  • ETSI European Telecommunications Standards Institute
  • MEC can improve the user experience and save bandwidth resources.
  • sinking computing power to mobile edge nodes it provides third-party application integration, which provides unlimited possibilities for service innovation of mobile edge portal.
  • a MEC can include a local V2X server and a UPF entity, and the UPF entity is an edge UPF entity.
  • the edge UPF entity can communicate with the base station, and can forward the packet sent by the base station to the local V2X server, or forward the packet generated by the local V2X server to the base station.
  • the edge UPF entity can also communicate with the CPF entity.
  • eMBMS evolved multimedia broadcast and multicast services
  • FIG. 2 includes two sets of MECs, namely, MEC1 and MEC2, and a first UPF entity, a first local V2X server, and a first base station are deployed in the MEC1, and the first base station can communicate with the first terminal device and the second terminal device.
  • a second UPF entity, a second local V2X server, and a second base station are deployed under the MEC2, and the second base station is capable of communicating with the third terminal device and the fourth terminal device.
  • the first UPF entity and the second UPF entity are both edge UPF entities, and both the first UPF entity and the second UPF entity can communicate with the CPF entity, and can also communicate with the central UPF entity, and the central UPF entity can be understood as not sinking to Edge UPF entity.
  • the first local V2X server and the second local V2X server in FIG. 1 are all indicated by a dotted line. This indicates that the local V2X server may be deployed or not deployed in the embodiment of the present application. The solution can actually eliminate the need for a local V2X server, so the local V2X server can be deployed without cost. However, since the local V2X server can also implement some other functions, it can continue to be deployed.
  • the local V2X server when deploying the local V2X server, you may not need to deploy the local V2X server under each MEC according to the specific requirements, and it can also reduce the cost to a certain extent.
  • the local V2X server is simply referred to as a server.
  • FIG. 3 is another application scenario of the embodiment of the present application.
  • a remote controller is added in FIG. 3, and the remote control center can be used to control terminal devices under each MEC.
  • the terminal device is an intelligent vehicle, the remote control center can uniformly control these smart vehicles.
  • the remote control center communicates with the V2X server, and in the embodiment of the present application, the remote control center can communicate with the local V2X server or with the UPF entity.
  • a UPF entity (such as the first UPF entity or the second UPF entity shown in FIG. 2 or FIG. 3), which is hereinafter referred to as FIG. 2 or FIG. 3, refers to an edge UPF entity, and these UPF entities have MBMS capabilities.
  • an embodiment of the present application provides a message multicasting method.
  • the application scenario shown in FIG. 2 or the application scenario shown in FIG. 3 is used as an example. The flow of this method is described below.
  • the first terminal device attaches to the network, and the attaching process may refer to a standard attaching process.
  • the first terminal device is taken as an example, and is actually applicable to any one of the terminal devices under any edge UPF entity.
  • the first terminal device After the first terminal device is attached to the network, the first terminal device applies to the formation management server to join the corresponding formation.
  • the first terminal device needs to be registered to the formation management server first, and then apply to join the corresponding formation.
  • the first terminal device may apply for registration to the formation management server immediately after being attached to the network, or the first terminal device may apply to the formation management server for registration when it needs to join the corresponding formation after attaching to the network.
  • the first terminal device may apply to the formation management service installed in the formation management server through the V2X application (APP) program installed in the first terminal device to apply for joining the formation.
  • the formation management server can communicate with a plurality of terminal devices. For example, the registration request sent by the first terminal device to the formation management server carries the identification of the formation, and after receiving the registration request, the formation management server can obtain the identification of the formation, thereby determining that the first terminal device is to join the formation. Identify the formation indicated.
  • the formation management service program is used to manage formations.
  • the terminal device is specifically an OBU in the vehicle, and the plurality of OBUs may form a formation, that is, one formation may include at least one terminal device, thereby facilitating unified scheduling management for the OBU.
  • the 10 vehicles ie the OBU in the vehicle
  • the OBUs in the 10 vehicles can negotiate in advance to determine the identity of the formation to be joined.
  • the OBUs of the 10 vehicles can negotiate a formation ID, and the OBUs of the 10 vehicles all request the formation management service program to join the formation logo. formation.
  • the first terminal device can apply to join the formation management service program to join the corresponding formation immediately after registering with the formation management service program, or the first terminal device can work normally after registering with the formation management service program, and considers that it needs to join. Apply to the formation management service program to join the formation when the team is formed accordingly.
  • S403. The formation management service program adds the first terminal device to the formation and sends a multicast group establishment request to the CPF entity, and the CPF entity receives the multicast group establishment request from the formation management service program.
  • S403 includes two parts, one part is that the formation management server adds the first terminal device to the formation, and the other part is that the formation management server sends a multicast group establishment request to the CPF entity.
  • the multicast group establishment request carries the formation information of the formation, and the formation information includes, for example, an identifier of the formation, the multicast group establishment request is used to request a multicast address for the formation, and optionally, the multicast group establishment request is further Can be used to request multicast permissions for this formation.
  • Applying for multicast rights and multicast addresses for the formation is equivalent to grouping the formation into a multicast group, so that the terminal devices included in the formation can communicate with each other through multicast. If the formation management service program has previously applied for multicast rights and multicast addresses for the formation to which the first terminal device is applied for, the formation management service program in S402 may not need to apply for the formation multicast rights and multicast to the CPF entity. address.
  • the CPF entity allocates a multicast address to the multicast group, that is, a packet forwarding route when the multicast address is used as the destination address.
  • the CPF entity may authorize the formation indicated by the formation information to form a multicast group, and the multicast group includes all the terminal devices included in the formation, and the CPF entity allocates a multicast address to the multicast group, and may also Indicate multicast rights for this multicast group.
  • the CPF entity sends the allocated multicast address to the formation management service program, and the formation management service program receives the multicast address.
  • the formation management service program sends the formation access result and the multicast address to the first terminal device, and the first terminal device receives the formation access result and the multicast address.
  • the formation management service program sends the multicast address assigned by the CPF entity to the first terminal device. Therefore, it can be understood that the CPF entity sends the multicast address to the first terminal device, or it is understood that the CPF entity passes the formation management service. The program sends the multicast address to the first terminal device.
  • the result of the formation access indicates that the first terminal device has been added to the formation to which the first terminal device is applied for, or the first terminal device is refused to join the formation to which the first terminal device is applied for.
  • the formation management service program will not send the multicast address to the first terminal device, therefore, the S406 is formed in a queue.
  • the access result indicates that the first terminal device is added to the formation of the first terminal device to join, and then the first terminal device can subsequently send a multicast packet in the multicast group, and can also receive the multicast. Multicast packets sent by other devices in the group.
  • the process of adding other terminal devices in the formation to the formation and obtaining the multicast address can refer to the execution process of S401-S406, and will not be repeated.
  • the remote control center applies to the formation management service program to join the formation.
  • the remote control center is described in the application scenario shown in FIG. 3.
  • the remote control center can be used to control multiple terminal devices in the system.
  • the multiple terminal devices can belong to the same UPF entity or belong to different UPF entities.
  • the multiple terminal devices can form multiple multicast groups, and the remote control center can join each multicast group.
  • the remote control center is a member device in the multicast group.
  • the status is the same as that of other terminal devices in the multicast group.
  • the remote control center can function as a control device to control the operation of the terminal device.
  • the terminal device is specifically an OBU in the vehicle
  • the remote control center can control the behavior of the vehicle, for example, according to at least one of the road condition, the weather condition, the speed of each vehicle, and the distance between the vehicles, and of course, according to Other factors are used to control the travel of the vehicle, reduce the probability of a car accident, and make the vehicle run in an orderly manner.
  • the 10 vehicles can apply to join the same formation.
  • the OBUs in the 10 vehicles can negotiate in advance to determine the identity of the formation to be joined.
  • the OBUs of the 10 vehicles can negotiate a formation ID, and the OBUs of the 10 vehicles request the formation management service program to join the formation indicated by the formation's logo.
  • the remote control center can communicate with each terminal device, the remote control center can obtain the formation information of the formation, so that the remote control center can also apply to the formation management service program to join the formation indicated by the formation information, that is, with the 10 Vehicles join the same formation and join the same multicast group.
  • the formation management service program sends the multicast address assigned by the CPF entity to the remote control center, and the remote control center receives the multicast address.
  • the formation management service program since the formation management service program has obtained the multicast address of the multicast group to which the formation indicated by the formation information belongs by executing S402-S405, the formation management service program does not need to request the group again from the CPF entity.
  • the broadcast address is directly sent to the remote control center by the multicast address assigned by the CPF entity in S404. If the formation management service program has not obtained the multicast address of the multicast group corresponding to the formation requested by the remote control center, the formation management service program may continue to apply for the multicast address to the CPF entity according to the steps described in S402-S405.
  • S402-S406, and S407-S408, the execution order of the two parts may be arbitrary, for example, S402-S406 is performed before S407-S408, or S402-S406 is performed after S407-S408, or S402-S406 is at S407- S408 is performed at the same time, and the embodiment of the present application is not limited.
  • S402-S406 may mean that S402 is before S407, and the order between S403-S406 and S408 may be arbitrary, for example, S408 may be performed before S403, or after S403 and before S404, or Execute after S404 and before S405, or after S405 and before S407, or after S407. The same is true for S402-S406 after S407-S408 or S402-S406 are performed simultaneously at S407-S408.
  • the first terminal device may send a multicast group join request to the CPF entity, and the CPF entity receives the multicast group join request from the first terminal device.
  • the multicast group join request is used by the first terminal device to request to join the multicast group indicated by the multicast address.
  • S409 can be performed.
  • the first terminal device may send a multicast group join request to the UPF entity where the first terminal device is located, for example, the first UPF entity shown in FIG. 2 or FIG. 3, and the first UPF entity receives the multicast group. Join the request. Then, the first UPF entity forwards the multicast group join request to the CPF entity, and the CPF entity receives the multicast group join request.
  • the CPF entity adds the first terminal device to the multicast group.
  • the CPF entity generates a multicast forwarding route whose destination address is the multicast address.
  • a multicast packet whose destination address is the multicast address can be forwarded according to the multicast forwarding route.
  • the CPF entity If the first terminal device is the first terminal device to join the multicast group, the CPF entity generates a multicast forwarding route whose destination address is the multicast address, for example, a multicast address is 224.X.X.X. As shown in Figure 4, the CPF entity generates a multicast forwarding route. If the first terminal device is not the first terminal device to join the multicast group, for example, the other terminal device applies to the CPF entity to join the multicast group. Then, the CPF entity may have generated a multicast forwarding route whose destination address is the multicast address, and S411 should be: the CPF entity updates the multicast forwarding route. That is, the CPF entity can generate a multicast forwarding route when the first terminal device is added to the multicast group. If a terminal device requests to join the multicast group, the multicast forwarding route generated before the CPF entity is updated is Yes, there is no need to generate a multicast forwarding route again.
  • the remote control center can also apply to join the multicast group.
  • the remote control center applies to join the multicast group and the processing process of the CPF entity. Refer to the introduction of S409-S411, where the remote control center processes and the first process. The processing of the terminal device is the same.
  • the CPF entity sends the generated multicast forwarding route to the at least one UPF entity, and the at least one UPF entity receives the multicast forwarding route from the CPF entity.
  • the at least one UPF entity is a UPF entity in which all terminal devices included in the multicast group are located. Only the first UPF entity is shown in FIG. 4, and the processes of receiving the multicast forwarding route by other UPF entities are similar.
  • the multicast forwarding route includes a mapping relationship between the multicast address and all the terminal devices included in the multicast group, where the mapping relationship between the multicast address and the terminal device may include the a mapping relationship between a UPF entity in which each terminal device is located in the multicast group and a base station in which each of the terminal devices is located, and a base station between the base station in which the terminal device is located and each of the terminal devices Mapping relations.
  • the route of the terminal device included in the multicast forwarding route is: the UPF entity where the terminal device is located - the base station where the terminal device is located - the terminal device .
  • the UPF entity where the first terminal device is located is the first UPF entity
  • the first UPF entity receives the multicast packet sent by other devices in the multicast group, according to the multicast forwarding route
  • the multicast packet is sent to the base station where the first terminal device is located, so that the base station where the first terminal device is located can further send the multicast packet to the first terminal device.
  • the second UPF entity receives the multicast packet sent by the other device in the multicast group, the second UPF entity and the first UPF entity are different UPF entities, and the second UPF entity forwards according to the multicast
  • the multicast packet can be sent to the first UPF entity.
  • the first UPF entity After receiving the multicast packet, the first UPF entity can send the multicast packet to the base station where the first terminal device is located, so that the first terminal The base station where the device is located sends the multicast packet to the first terminal device. That is, with the technical solution provided by the embodiment of the present application, information interaction can be directly performed between the UPF entities, so that information exchange between the UPF entities can be implemented.
  • the local V2X server can be deployed without the participation of the local V2X server, which can reduce the cost of the local V2X server, effectively reduce the cost, and make the packet forwarding path simpler.
  • the CPF entity may send a communication connection to at least one of the at least two UPF entities.
  • a request is established to request a communication connection between each of the at least two UPF entities, so that the UPF entities in which the terminal devices included in one multicast group can send information to each other, thereby implementing multicast.
  • a UPF entity may store multiple multicast forwarding routes, and the multiple multicast forwarding routes may include all multicast groups joined by all terminal devices served by the UPF entity.
  • the route, the route of a multicast group includes the mapping relationship between all the terminal devices included in the multicast group, the base station where each terminal device is located, each base station and the UPF entity, and the three. .
  • the terminal device served by the first UPF entity includes the first terminal device and the third terminal device, the first terminal device joins the multicast group 1 and the multicast group 2, and the third terminal device joins the multicast group 3, then
  • the multicast forwarding route stored by a UPF entity includes the routing of multicast group 1, the routing of multicast group 2, and the routing of multicast group 3.
  • the multicast group 1 includes a first terminal device and a second terminal device, and the UPF entity to which the first terminal device belongs is the first UPF entity, and the base station to which the first terminal device belongs is the first base station under the first UPF entity.
  • the UPF entity to which the second terminal device belongs is the second UPF entity, and the base station to which the second terminal device belongs is the second base station in the second UPF entity, and the multicast forwarding route stored by the first UPF entity includes the following mapping relationship:
  • the above only indicates the information included in the multicast forwarding route, and does not represent the actual storage mode of the multicast forwarding route.
  • the UPF entity can directly send the received multicast packet according to the stored multicast forwarding route.
  • the above describes how to generate a multicast forwarding route. After the multicast forwarding route is generated, if the terminal device in the multicast group changes, for example, a new terminal device joins, or a terminal device exits, or If the path of the terminal device changes, it will also involve the process of updating the multicast forwarding route, which is described below.
  • an embodiment of the present application provides a method for updating a multicast forwarding route.
  • the application scenario shown in FIG. 2 or the application scenario shown in FIG. 3 is used as an example. The method can be performed after the execution of the embodiment shown in FIG.
  • the CPF entity determines that the second terminal device performs the cell handover, and the CPF entity determines that the base station where the cell after the second terminal device is switched and the base station where the cell before the second terminal device is switched are different base stations.
  • the second terminal device is a terminal device included in the multicast group introduced in the embodiment shown in FIG. 4 .
  • the handover process involves the CPF entity. Therefore, the CPF entity can be aware of the handover process of the terminal device. This part of the content can refer to the cell handover process in the standard, and details are not described herein.
  • the CPF entity updates the multicast forwarding route of the multicast address, that is, the CPF entity updates the multicast forwarding route generated in the embodiment shown in FIG.
  • the multicast forwarding route may not change, but if the second terminal device switches, If the base station where the cell is located and the base station where the cell before the second terminal device is switched are different base stations, the route change may be involved in multicasting.
  • the base station where the cell after the second terminal device is switched and the base station where the cell before the second terminal device is switched are different base stations, and different situations are involved, which involve different route change modes, which are described below.
  • the base station where the cell after the second terminal device is switched belongs to the same UPF entity as the base station where the cell before the second terminal device is switched.
  • the original mapping relationship is the first UPF entity - the first base station - the second
  • the CPF entity can update the mapping relationship in the multicast forwarding route to the first UPF entity-second base station- Two terminal devices.
  • the base station where the cell after the second terminal device is switched and the base station where the cell before the second terminal device is switched belong to different UPF entities.
  • the original mapping relationship is the first UPF entity - the first base station - the second terminal device, that is, the UPF entity originally serving the second terminal device is the first UPF entity.
  • the second base station is switched to the second base station, and the CPF entity can update the mapping relationship in the multicast forwarding route to the second UPF entity-second base station-second terminal device. That is, the direct destination device is changed from the first UPF entity to the second UPF entity.
  • the CPF entity sends the updated multicast forwarding route to the at least one UPF entity, and sends the UPF entity to the UPF entity where the second base station switches the base station.
  • At least one UPF entity here is a UPF entity in which all terminal devices included in the multicast group are located.
  • Figure 5 shows an example in which the CPF entity sends the updated multicast forwarding route to the first UPF entity.
  • the UPF entity in which the second terminal device is switched after the second terminal device is switched may be the same UPF entity or the same UPF entity as the second terminal device is switched.
  • the UPF entity in which the base station is located is different from the UPF entity in which the base station before the second terminal device is switched, and the UPF entity after the second terminal device is switched may be one of the at least one UPF entity, or may be before
  • the embodiment of the present application does not limit the UPF entity that does not belong to the multicast group.
  • the UPF entity that does not belong to a multicast group refers to the UPF entity that is not the terminal device included in the multicast group.
  • the UPF entity after the second terminal device is switched does not belong to the UPF entity.
  • the UPF entity of the multicast group may not establish a communication connection between the UPF entity after the second terminal device handover and the UPF entity belonging to the multicast group. Therefore, in this case, the core network device may send a communication connection establishment request to the at least one UPF entity that is switched by the second terminal device and the UPF entity that belongs to the multicast group, so that after the second terminal device switches A communication connection is established between the UPF entity and each of the UPF entities belonging to the multicast group.
  • the CPF entity updates the multicast forwarding route because a cell handover occurs in a terminal device in the multicast group.
  • a new terminal device joins the multicast group.
  • the terminal device is removed from the multicast group.
  • the CPF entity needs to update the multicast forwarding route and send the updated multicast forwarding route to the corresponding UPF entity. If a new terminal device is added to the multicast group, the CPF entity sends the updated multicast forwarding route to the UPF entity where all the terminal devices included in the multicast group are located. In addition, the updated multicast forwarding route is sent to the UPF entity where the newly added terminal device is located.
  • the UPF entity in which the newly added device is located may be in the UPF entity where all the terminal devices included in the multicast group are located.
  • the CPF entity sends the updated multicast forwarding route to the UPF entity where all the terminal devices included in the multicast group are located. All terminal devices included in the multicast group also include the exit terminal devices.
  • the following describes how the UPF entity obtains the multicast forwarding route and how to update the multicast forwarding route.
  • the following describes how the UPF entity forwards the multicast packet according to the multicast forwarding route.
  • an embodiment of the present application provides a packet multicasting method.
  • the application scenario shown in FIG. 2 or the application scenario shown in FIG. 3 is used as an example.
  • the UPF entity can implement the forwarding of the multicast packet according to the multicast forwarding route generated in the embodiment shown in FIG. 4 or according to the multicast forwarding route updated in the embodiment shown in FIG. 5.
  • the first terminal device generates a multicast packet, where the multicast packet carries a multicast address.
  • the first terminal device can obtain the multicast address allocated by the CPF entity in S405. Therefore, the first terminal device can directly carry the multicast address when the multicast packet needs to be sent.
  • the first terminal device may join multiple multicast groups, and the multicast packet may be sent to one of the multiple multicast groups.
  • S602 The first terminal device sends the multicast packet to the first UPF entity, where the first UPF entity receives the multicast packet.
  • the first UPF entity is the UPF entity where the first terminal device is located.
  • the first terminal device sends the multicast packet to the first UPF entity, where the first terminal device is located at the first terminal device.
  • the first base station sends the multicast packet, and the first base station sends the multicast packet to the first UPF entity.
  • the first UPF entity After receiving the packet, the first UPF entity can know the type of the packet, such as a broadcast packet, a multicast packet, or a unicast packet, by using the destination address of the packet.
  • the first terminal device belongs to the first base station, and the first base station is not shown in FIG. 6. Therefore, the arrow pointed to by the first terminal device in the first UPF entity in S601 in FIG. 6 actually means that the first terminal device will The multicast packet is sent to the first base station, and the first base station sends the multicast packet to the first UPF entity.
  • the terminal device for the communication described between the terminal device and the UPF entity, unless otherwise specified, it indicates that the terminal device communicates with the UPF entity through the base station.
  • the first UPF entity queries the stored multicast forwarding route, and forwards the multicast packet to the device indicated by the multicast forwarding route.
  • the multicast forwarding route indicates that the multicast group corresponding to the multicast address includes three destination devices, which are a second terminal device under the first UPF entity, a remote control center, and a third terminal under the second UPF entity. device.
  • the multicast forwarding route indicates that the route to the second terminal device is the first UPF entity - the first base station - the second terminal device, and the route to the remote control center is the current UPF entity - the remote control center, to the third
  • the route of the terminal device is a first UPF entity - a second UPF entity - a second base station - a third terminal device.
  • the forwarding process includes:
  • the first UPF entity encapsulates the multicast packet into a tunnel where the second terminal device is located, that is, sends the multicast packet to the first base station, where the first base station receives the multicast packet, and then the first The base station sends the multicast packet to the second terminal device.
  • the first base station is not shown in FIG. 6. Therefore, the arrow pointed to by the first UPF entity to the second terminal device in S6031 in FIG. 6 has a practical meaning.
  • the first UPF entity sends the multicast packet to the first base station, and then the first base station sends the multicast packet to the second terminal device;
  • the current UPF entity is the first UPF entity
  • the first UPF entity converts the multicast packet into a unicast packet, and sends the multicast packet to the remote control center in an uplink manner, and the remote control center receives the multicast packet
  • the first UPF entity encapsulates the multicast packet into a tunnel between the first UPF entity and the second UPF entity, to send the multicast packet to the second UPF entity, where the second UPF entity receives the group. Broadcast message.
  • the second UPF entity also stores the multicast forwarding route. After receiving the multicast packet, the second UPF entity can send the multicast packet to the second base station according to the multicast forwarding route, so that the second base station can The multicast packet is sent to the third terminal device, such as S6033 shown by the dotted line in FIG. 6, except that the second base station is not shown in FIG.
  • the execution order of the three steps S6031-S6033 may be arbitrary, and the number of the steps does not represent a limitation on the execution order.
  • the UPF entity can directly forward the multicast packet, and the local V2X server can be used to reduce the complexity of the packet forwarding path and reduce the deployment cost of the local V2X server.
  • the process of message multicasting is performed.
  • the broadcast of the message can also be directly implemented by the UPF entity, so that the information can be exchanged between the UPF entities, and the following embodiments are used.
  • a message broadcast method provided by an embodiment of the present application is introduced.
  • the application scenario shown in FIG. 2 or the application scenario shown in FIG. 3 is used as an example. Referring to Figure 7, the flow of the method is described below.
  • the terminal device applies for a broadcast address and a broadcast permission to the local V2X server.
  • the terminal device may send a message for applying for a broadcast address and a broadcast right to the base station where the terminal device is located, and the base station where the terminal device is located receives the message, and forwards the message to the UPF entity where the base station is located, where the base station is located.
  • the UPF entity receives the message and forwards the message to the local V2X Server, and the local V2X Server receives the message.
  • the local V2X server sends a broadcast permission request to the CPF entity, where the broadcast permission request is used to directly broadcast the broadcast packet carrying the first identifier by using the first UPF entity, and the CPF entity receives the broadcast permission request. It can be understood that the broadcast permission request can be used to request the first UPF entity to convert the broadcast message carrying the first identifier from the uplink unicast to the downlink broadcast.
  • the local V2X server can directly allocate a broadcast address to the terminal device according to the request of the terminal device, and the local V2X server can carry the broadcast address in the broadcast permission request and send it to the core network device.
  • S701 and S702 are the local V2X servers deployed in the system. If the local V2X server is not deployed in the system, or the local V2X server is not deployed on the MEC where the terminal device resides, the terminal device can directly apply for broadcast to the CPF entity. Address and broadcast rights, then it can be understood that the terminal device sends the broadcast permission request to the CPF entity. In this case, the broadcast address can be assigned by the CPF entity.
  • the first UPF entity is a UPF entity in which the terminal device is located, and the first identifier is an identifier of the terminal device that sends the broadcast packet, or the first identifier is a flow identifier of the service flow to which the broadcast packet belongs.
  • the CPF entity may query whether the first identifier is an authorized identifier, and if the first identifier is an authorized identifier, perform S703. If the first identifier is not authorized, the CPF entity may authorize the first identifier, and then execute S703. . After the authorization, the broadcast message carrying the first identifier can be directly broadcasted by the first UPF entity.
  • the CPF entity sends a notification message to the first UPF entity, where the first UPF entity receives the notification message.
  • the notification message is used to indicate that the first identifier is an authorized identifier.
  • the first UPF entity may directly broadcast the broadcast packet carrying the authorized identifier, that is, for the broadcast packet carrying the authorized identifier, the first UPF entity may encapsulate the broadcast packet according to the matched flow rule. Forwarding to the downstream MBMS session (SMS) without sending the broadcast packet carrying the authorized identifier to the local V2X Server.
  • SMS downstream MBMS session
  • the local V2X server After the SCF and the CPF entity complete the forwarding authorization and policy update of the first UPF entity, the local V2X server sends a broadcast permission response to the local V2X server, and the local V2X server receives the broadcast permission response.
  • the broadcast permission response is a response to a broadcast permission request sent by the local V2X Server.
  • the local V2X server sends a broadcast capability request response to the terminal device, and the terminal device receives the broadcast capability request response.
  • the broadcast capability application response may carry the rights information and the authorized broadcast address, and the authorized broadcast address is the broadcast address generated by the local V2X Server or the CPF entity as described above.
  • the rights information may be used to indicate that the first UPF entity is allowed to directly broadcast the broadcast message carrying the first identifier, or is used to indicate that the first UPF entity is not allowed to directly broadcast the broadcast message carrying the first identifier.
  • the privilege information is used to indicate that the first UPF entity is not allowed to directly broadcast the broadcast packet carrying the first identifier
  • the local V2X Server does not send the broadcast address to the terminal device, so S705 is used to indicate permission.
  • the first UPF entity directly broadcasts a broadcast packet carrying the first identifier as an example.
  • S704 and S705 continue to use the local V2X server deployed in the system. If the local V2X server is not deployed in the system, or the local V2X server is not deployed in the MEC where the terminal device is located, the core network completes the first UPF entity. After the forwarding authorization and the policy update, the terminal may directly respond to the broadcast permission request of the terminal device. For example, the CPF entity may send the rights information and the authorized broadcast address to the terminal device, and the terminal device receives the rights information and the authorized broadcast address.
  • the terminal device generates a first packet, where the first packet carries a broadcast address.
  • the first packet is the broadcast packet, and the broadcast address carried in the first packet is the authorized broadcast address as described in the previous step.
  • the first packet carries the first identifier.
  • the terminal device If the terminal device needs to broadcast, it generates an uplink packet, and the uplink packet is encapsulated according to a broadcast format, and the broadcast address is an authorized broadcast address.
  • S707 The terminal device sends the first packet to the first UPF entity, where the first UPF entity receives the first packet.
  • the first packet can be forwarded to the first UPF entity through the uplink unicast tunnel.
  • the terminal device sends the first packet to the base station where the terminal device is located, and then the base station where the terminal device is located sends the first packet to the first UPF entity, which is not described in detail.
  • the first packet may be sent by the other UPF entity to the first UPF entity.
  • the terminal device in the second UPF entity generates the first packet
  • the terminal device sends the first packet to the second UPF.
  • the entity, the second UPF entity sends the first packet to the first UPF entity.
  • the first UPF entity determines that the first packet is a broadcast packet according to the destination address carried in the first packet, and the first UPF entity determines that the first identifier carried in the first packet is an authorized identifier.
  • the first UPF entity may parse the first packet, and determine, according to the destination address of the first packet, what type of packet is the first packet, for example, a broadcast packet or a multicast packet. Text or unicast message.
  • the first UPF entity may determine whether the identifier carried by the broadcast packet is an authorized identifier, for example, the broadcast packet carries the first identifier, which is introduced in the previous step, where the first identifier is Authorized ID.
  • the first UPF entity broadcasts the first packet.
  • the first UPF entity determines that the first packet can be directly broadcast by the first UPF entity, and the first packet does not need to be sent to the local V2X server. Therefore, the first UPF entity queries the stored broadcast route to broadcast the first message.
  • the local V2X Server first applies for a temporary mobile group identity (TMGI) to the CPF entity.
  • TMGI temporary mobile group identity
  • the UPF entity at the edge needs to apply to the peer UPF entity to join a multicast group and become the downstream node forwarded by the peer UPF entity.
  • the downstream nodes that the two UPF entities forward to each other are implemented.
  • the first UPF entity when the first UPF entity is broadcasting, if the other UPF entity is the downstream node forwarded by the first UPF entity, that is, the first UPF entity and the other UPF entity belong to one multicast group, the first UPF entity may also be combined.
  • the first packet is multicast to the UPF entities, and the UPF entities can receive the first packet. After receiving the first packet, the UPF entity continues to broadcast the first packet.
  • a low-latency multicast or broadcast forwarding capability that does not require V2X server participation is provided, and the forwarding delay can be better reduced.
  • the V2X server is not required to participate in multicast or broadcast, the deployment amount of the V2X server can be reduced, and the cost can be effectively reduced.
  • the V2X server after the V2X server is sunk to the edge, it can support the forwarding of multicast messages or broadcast messages between MECs, thereby effectively matching the needs of the service.
  • FIG. 8 shows a schematic structural diagram of a CPF entity 800.
  • the CPF entity 800 can implement the functionality of the CPF entities referred to above.
  • the CPF entity 800 can be a CPF entity as described above or can be a chip disposed in the CPF entity described above.
  • the CPF entity 800 can include a processor 801 and a transceiver 802. Wherein, the processor 801 can be used to execute S404, S410, and S411 in the embodiment shown in FIG. 4, and S503 in the embodiment shown in FIG. 5, and/or other techniques for supporting the techniques described herein. process.
  • the transceiver 802 can be used to perform S403, S405, S409, and S412 in the embodiment shown in FIG. 4, and S501 and S502 in the embodiment shown in FIG. 5, and/or to support the techniques described herein. Other processes.
  • the transceiver 802 is configured to receive a multicast group join request, where the multicast group join request is used by the first terminal device to request to join the multicast group indicated by the multicast address.
  • the processor 801 is configured to add the terminal device to the multicast group, and generate a multicast forwarding route whose destination address is the multicast address.
  • the transceiver 802 is further configured to send the multicast forwarding route to at least one UPF entity, where the at least one UPF entity includes a UPF entity in which all terminal devices included in the multicast group are located.
  • FIG. 9 shows a schematic structural diagram of a UPF entity 900.
  • the UPF entity 900 can implement the functionality of the first UPF entity referred to above.
  • the UPF entity 900 may be the first UPF entity described above or may be a chip disposed in the first UPF entity described above.
  • the UPF entity 900 can include a processor 901 and a transceiver 902.
  • the processor 901 can be used to execute S708 in the embodiment shown in FIG. 7, and/or other processes for supporting the techniques described herein.
  • Transceiver 902 can be used to perform S703, S707, and S709 in the embodiment shown in FIG. 7, and/or other processes for supporting the techniques described herein.
  • the transceiver 902 can be used as an integral module to interact with the terminal device or with other UPF entities.
  • the transceiver 902 includes a plurality of transceiver interfaces, a portion of which is for interacting with the terminal device, and a portion of the transceiver interface for interacting with other UPF entities.
  • the transceiver 902 is configured to receive the first packet.
  • the processor 901 is configured to determine, according to the destination address carried in the first packet, that the first packet is a broadcast packet, and the first UPF entity determines that the first identifier carried by the first packet is An identifier of the service device, or the identifier of the terminal device that sends the first packet, or the flow identifier of the service flow to which the first packet belongs;
  • the transceiver 902 is further configured to broadcast the first packet.
  • FIG. 10 shows a schematic structural diagram of a CPF entity 1000.
  • the CPF entity 1000 can implement the functions of the CPF entities referred to above.
  • the CPF entity 1000 may be a CPF entity as described above or may be a chip disposed in the CPF entity described above.
  • the CPF entity 1000 can include a processor 1001 and a transceiver 1002.
  • the processor 1001 can be used to execute S703 and S704 in the embodiment shown in FIG. 7, and/or other processes for supporting the techniques described herein.
  • the processor 1001 executes S703, which mainly means that the processor 1001 queries whether the first identifier is an authorized identifier. If the first identifier is not authorized, the processor 1001 may authorize the first identifier.
  • the processor 1001 executes S704, mainly to mean that the processor 1001 generates a notification message.
  • the transceiver 1002 can be used to perform S702, S703, and 704 in the embodiment shown in FIG. 7, and/or other processes for supporting the techniques described herein.
  • the transceiver 1002 is configured to receive a broadcast permission request, where the broadcast permission request is used to directly broadcast a broadcast message carrying the first identifier by using the first UPF entity, where the first identifier is sent by the broadcast packet.
  • the processor 1001 is configured to authorize the first identifier.
  • the transceiver 1002 is further configured to send, to the first UPF entity, a notification message, where the notification message is used to indicate that the first identifier is the authorized identifier, where the first UPF entity directly broadcasts a carrier A broadcast message indicating the authorized identity.
  • CPF entity 800, UPF entity 900 or CPF entity 1000 may also be implemented by the structure of communication device 1100 as shown in FIG. 11A.
  • the communication device 1100 can implement the functions of the CPF entity or the first UPF entity referred to above.
  • the communication device 1100 can include a processor 1101. Wherein, when the communication device 1100 is used to implement the functions of the CPF entity 800 in the embodiment shown in FIG. 4 or the embodiment shown in FIG. 5, the processor 1101 can be used to execute S404 in the embodiment shown in FIG. S410, and S411, and S503 in the embodiment shown in FIG. 5, and/or other processes for supporting the techniques described herein.
  • the processor 1101 can be used to execute S708 in the embodiment shown in FIG. 7, and/or to support the text herein. Other processes of the described technology.
  • the processor 1101 can be used to execute S703 and S704 in the embodiment shown in FIG. 7, and/or to support this document. Other processes of the described techniques.
  • the communication device 1100 can pass through a field-programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), a central processor (central processor). Unit, CPU), network processor (NP), digital signal processor (DSP), microcontroller (micro controller unit (MCU), or programmable logic device (programmable logic device, The PLD) or other integrated chip implementation, the communication device 1100 can be configured in the CPF entity or the first UPF entity in the embodiment of the present application, so that the CPF entity or the first UPF entity implements the packet group provided by the embodiment of the present application. Broadcast method or message broadcast method.
  • FPGA field-programmable gate array
  • ASIC application specific integrated circuit
  • SoC system on chip
  • CPU central processor
  • NP network processor
  • DSP digital signal processor
  • MCU microcontroller
  • programmable logic device programmable logic device
  • the communication device 1100 may further include a memory 1102, which may be referred to FIG. 11B, where the memory 1102 is used to store computer programs or instructions, and the processor 1101 is used to decode and execute the computer programs or instructions. .
  • these computer programs or instructions may include the functional programs of the CPF entity or the first UPF entity described above.
  • the communication device 1100 can be configured to implement the function of the CPF entity in the message multicast method or the message broadcast method of the embodiment of the present application.
  • the communication device 1100 can be configured to implement the function of the first UPF entity in the message broadcast method of the embodiment of the present application.
  • the functional programs of the CPF entities or the first UPF entities are stored in a memory external to the communication device 1100.
  • the function program of the CPF entity is decoded and executed by the processor 1101, part or all of the contents of the function program of the CPF entity are temporarily stored in the memory 1102.
  • the function program of the first UPF entity is decoded and executed by the processor 1101, part or all of the content of the function program of the first UPF entity is temporarily stored in the memory 1102.
  • the functional programs of the CPF entities or the first UPF entities are disposed in a memory 1102 stored within the communication device 1100.
  • the function program of the CPF entity is stored in the memory 112 inside the communication device 1100
  • the communication device 1100 can be disposed in the CPF entity of the embodiment of the present application.
  • the function program of the first UPF entity is stored in the memory 1102 inside the communication device 1100
  • the communication device 1100 can be disposed in the first UPF entity of the embodiment of the present application.
  • portions of the functional programs of the CPF entities are stored in a memory external to the communication device 1100, and other portions of the functional programs of the CPF entities are stored in the memory 1102 internal to the communication device 1100.
  • portions of the functional programs of the first UPF entities are stored in a memory external to the communication device 1100, and other portions of the functional programs of the first UPF entities are stored in the memory 1102 inside the communication device 1100.
  • the CPF entity 800, the UPF entity 900, the CPF entity 1000, and the communication device 1100 are presented in the form of dividing each functional module into functional modules, or may be presented in an integrated manner to divide the functional modules.
  • a “module” herein may refer to an ASIC, a processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other devices that provide the functionality described above.
  • the CPF entity 800 provided by the embodiment shown in FIG. 8 can also be implemented in other forms.
  • the CPF entity includes a processing module and a transceiver module.
  • the processing module can be implemented by the processor 801, and the transceiver module can be implemented by the transceiver 802.
  • the processing module can be used to execute S404, S410, and S411 in the embodiment shown in FIG. 4, and S503 in the embodiment shown in FIG. 5, and/or other processes for supporting the techniques described herein.
  • the transceiver module can be used to perform S403, S405, S409, and S412 in the embodiment shown in FIG. 4, and S501 and S502 in the embodiment shown in FIG. 5, and/or to support the techniques described herein. Other processes.
  • the transceiver module is configured to receive a multicast group join request, where the multicast group join request is used by the first terminal device to request to join the multicast group indicated by the multicast address;
  • a processing module configured to add the terminal device to the multicast group; and generate a multicast forwarding route whose destination address is the multicast address;
  • the transceiver module is further configured to send the multicast forwarding route to at least one UPF entity, where the at least one UPF entity includes a UPF entity in which all terminal devices included in the multicast group are located.
  • the UPF entity 900 provided by the embodiment shown in FIG. 9 can also be implemented in other forms.
  • the UPF entity includes a processing module and a transceiver module.
  • the processing module can be implemented by the processor 901, and the transceiver module can be implemented by the transceiver 902.
  • the processing module can be used to perform S708 in the embodiment shown in FIG. 7, and/or other processes for supporting the techniques described herein.
  • the transceiver module can be used to perform S703, S707, and S709 in the embodiment shown in FIG. 7, and/or other processes for supporting the techniques described herein.
  • the transceiver module can be used as an integral module to interact with the terminal device or with other UPF entities.
  • the transceiver module includes a plurality of sub-transceiver modules, a portion of the sub-transceiver modules are configured to interact with the terminal device, and a portion of the sub-transceiver modules are configured to interact with other UPF entities.
  • a sub-transceiver module can be implemented by a transceiver interface as described above.
  • the transceiver module is configured to receive the first packet
  • a processing module configured to determine, according to the destination address carried in the first packet, that the first packet is a broadcast packet, and the first UPF entity determines that the first identifier carried by the first packet is An identifier of the authorization, where the first identifier is an identifier of the terminal device that sends the first packet, or is a flow identifier of the service flow to which the first packet belongs;
  • the transceiver module is further configured to broadcast the first packet.
  • the CPF entity 1000 provided by the embodiment shown in FIG. 10 can also be implemented in other forms.
  • the CPF entity includes a processing module and a transceiver module.
  • the processing module can be implemented by the processor 1001, and the transceiver module can be implemented by the transceiver 1002.
  • the processing module can be used to execute S703 and S704 in the embodiment shown in FIG. 7, and/or other processes for supporting the techniques described herein.
  • the processing module executes S703, which mainly means that the processing module queries whether the first identifier is an authorized identifier. If the first identifier is not authorized, the processor 1001 may authorize the first identifier.
  • the processing module executes S704, mainly, the processing module generates a notification message.
  • the transceiver module can be used to perform S702, S703, and 704 in the embodiment shown in FIG. 7, and/or other processes for supporting the techniques described herein.
  • the transceiver module is configured to receive a broadcast permission request, where the broadcast permission request is used to directly broadcast a broadcast message carrying the first identifier by using the first UPF entity, where the first identifier is a terminal that sends the broadcast packet.
  • a processing module configured to generate a notification message, where the notification message is used to indicate that the first identifier is the authorized identifier, where the first UPF entity directly broadcasts a broadcast packet that carries the authorized identifier ;
  • the transceiver module is further configured to send the notification message to the first UPF entity.
  • the CPF entity 800, the UPF entity 900, the CPF entity 1000, and the communication device 1100 provided by the embodiments of the present application may be used to execute the embodiment shown in FIG. 4, the embodiment shown in FIG. 5, the embodiment or the diagram shown in FIG.
  • the method provided by the embodiment shown in FIG. 7 and therefore the technical effects that can be obtained can be referred to the above method embodiment, and details are not described herein again.
  • Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present application. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG.
  • These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another readable storage medium, for example, the computer instructions can be passed from a website site, computer, server or data center Wired (eg, coaxial cable, fiber, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.) to another website site, computer, server, or data center.
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD) ))Wait.
  • a magnetic medium eg, a floppy disk, a hard disk, a magnetic tape
  • an optical medium eg, a digital versatile disc (DVD)
  • DVD digital versatile disc
  • semiconductor medium eg, 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

一种报文组播、报文广播方法及设备，用于减小时延。报文组播方法包括：CPF实体接收组播组加入请求，所述组播组加入请求用于第一终端设备请求加入组播地址所指示的组播组；所述CPF实体将所述终端设备加入所述组播组；所述CPF实体生成目的地址为所述组播地址的组播转发路由；所述CPF实体将所述组播转发路由发送给至少一个UPF实体，所述至少一个UPF实体包括所述组播组所包括的所有终端设备所在的UPF实体。

Description

一种报文组播、报文广播方法及设备
本申请要求于2017年11月29日提交中国专利局、申请号为201711226691.7、发明名称为“一种报文组播、报文广播方法及设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种报文组播、报文广播方法及设备。
背景技术
请参考图1，针对车到一切(vehicle to everything，V2X)的通讯方式，目前提供了一种场景。其中，下沉到边缘的核心网用户面功能(user plane function，UPF)实体具有多媒体广播和组播业务(multimedia broadcast and multicast services，MBMS)能力，可以作为边缘网关(local gateway，local GW)与基站通信，以及，UPF实体还能与核心网控制面功能(control plane function，CPF)实体通信。另外，多个UPF实体都能够与V2X服务器(V2X server)通信。
V2X通讯对网络带来的核心需求首要的就是业务低时延，而在图1所示的场景下，V2X server需要处理来自多个UPF实体的报文，也需要向多个UPF实体发送报文，则V2X server的处理能力很可能成为V2X的性能瓶颈。鉴于此，目前又提出了另一种场景，即，将V2X server和UPF实体都下沉到边缘，例如为每个UPF实体设置一个V2X server，这样的V2X server可称为本地(local)V2X server，下沉到边缘的UPF实体可称为边缘UPF实体。这样，一个local V2X server基本只需负责与相应的边缘UPF实体通信，对local V2X server的性能要求较低，也能够减小时延。
在图1所示的场景中，V2X server可以与多个边缘UPF实体通信，然而如果将V2X server下沉到边缘形成local V2X server，则一个local V2X server只能与该local V2X server对应的边缘UPF实体通信，而跟其他的边缘UPF实体之间无法通信，从而会增加网络通信的时延。
发明内容
本申请实施例提供一种报文组播、报文广播方法及设备，用于减小时延。
第一方面，提供一种报文组播方法，该方法可由CPF实体执行。该方法包括：CPF实体接收组播组加入请求，所述组播组加入请求用于第一终端设备请求加入组播地址所指示的组播组；所述CPF实体将所述终端设备加入所述组播组；所述CPF实体生成目的地址为所述组播地址的组播转发路由；所述CPF实体将所述组播转发路由发送给至少一个UPF实体，所述至少一个UPF实体包括所述组播组所包括的所有终端设备所在的UPF实体。
本申请实施例中，CPF实体为编队分配组播地址后，可以生成组播转发路由，并将组播转发路由发送给至少一个UPF实体，从而至少一个UPF实体根据该组播转发路由，可以直接将接收的组播报文转发给该组播地址所指示的组播组中的相应的设备，如果该组播组中包括其他UPF实体下的设备，则UPF实体根据组播转发路由就能将报文发送给其他UPF实体下的设备，这 样，在将V2X server下沉到边缘后，无需local V2X server的参与，UPF实体就可以直接转发报文，实现了UPF实体之间的信息互通，减小了网络通信的时延。而且，也无需为了报文转发而部署local V2X server，可以减少local V2X server的部署量，有效降低成本，也降低了报文的转发路径的复杂性。
在一个可能的设计中，所述CPF实体接收组播组建立请求，所述组播组建立请求携带编队信息，所述编队信息所指示的编队包括至少一个终端设备，所述组播组建立请求用于为所述编队请求组播地址，所述至少一个终端设备包括所述第一终端设备；所述CPF实体为所述编队分配所述组播地址。
CPF实体接收组播组建立请求后即可创建组播组，并生成组播地址，从而至少一个终端设备都可以属于该组播组，一个组播组中的组播报文通过UPF实体就可以实现组播，通信时延较小。
在一个可能的设计中，所述CPF实体确定第二终端设备进行了小区切换，且所述第二终端设备切换后的小区与所述终端设备切换前的小区属于不同的基站，所述第二终端设备属于所述组播组；所述CPF实体更新所述组播转发路由；所述CPF实体将更新后的所述组播转发路由发送给所述至少一个UPF实体，以及发送给所述第二终端设备切换后所在的UPF实体。
如果组播组中的第二终端设备进行了小区切换，且切换后的小区与切换前的小区属于不同的基站，则该组播组的组播路由就会发生变化。那么CPF实体可以及时更新组播转发路由，并将更新后的组播转发路由发送给UPF实体，使得UPF实体能够根据更新后的组播转发路由转发报文，提高报文转发的成功率。
第二方面，提供一种报文广播方法，该方法可由第一UPF实体执行，第一UPF实体为边缘UPF实体。该方法包括：第一UPF实体接收第一报文；所述第一UPF实体根据所述第一报文携带的目的地址确定所述第一报文为广播报文，以及，所述第一UPF实体确定所述第一报文携带的第一标识为已授权的标识，所述第一标识为发送所述第一报文的终端设备的标识，或为所述第一报文所属的业务流的流标识；所述第一UPF实体广播所述第一报文。
本申请实施例提供了无需V2X server参与的低时延的广播能力，只要为相应的标识授权，则UPF实体就能够直接实现报文的广播，能够更好地降低的转发时延。且因为无需V2X server参与广播，能够减少V2X server的部署量，有效降低成本。
在一个可能的设计中，所述第一UPF实体从CPF实体接收通知消息，所述通知消息用于指示所述第一标识为所述已授权的标识；所述第一UPF实体根据所述通知消息确定所述第一标识为所述已授权的标识，其中，所述第一UPF实体直接广播携带所述已授权的标识的广播报文。
相应的，第三方面，提供一种报文广播方法，该方法可由CPF实体执行。该方法包括：CPF实体接收广播权限请求，所述广播权限请求用于请求通过第一UPF实体直接广播携带第一标识的广播报文，所述第一标识为发送所述广播报文的终端设备的标识，或为所述广播报文所属的业务流的流标识；所述CPF实体向所述第一UPF实体发送通知消息，所述通知消息用于指示所述第一标识为所述已授权的标识，其中，所述第一UPF实体直接广播携带所述已授权的标识的广播报文。
CPF实体可以为相应的标识授权，并通知UPF实体，则UPF实体接收CPF实体发送的通知消息后就可以确定哪些标识是已授权的标识。UPF实体可以直接广播携带已授权的标识的广播报文，无需再通过V2X server实现广播，缩短报文广播的路径，减小通信时延。
在一个可能的设计中，第一UPF实体接收第一报文，包括：所述第一UPF实体从所述第一UPF实体服务的终端设备接收所述第一报文，或，所述第一UPF实体从第二UPF实体接收所述第一报文。
第一报文可能是终端设备发送给第一UPF实体的，或者也可能是第二UPF实体发送给第一UPF实体的，例如是第二UPF实体下的终端设备发送给第二UPF实体，第二UPF实体再发送给第一UPF实体，从而能够将其他的UPF实体下的终端设备的广播报文在本UPF实体下进行广播，UPF实体之间能够直接通信，无需借助于V2X server或核心网实现通信，减小通信时延。
在一个可能的设计中，所述第一UPF实体确定所述第一UPF实体所请求的临时移动组标识中还包括所述第二UPF实体的标识；所述第一UPF实体向所述第二UPF实体发送组播请求消息，用于请求与所述第二UPF实体加入同一组播组。
一个组播组中的UPF实体可以互相通信，从而其中的一个UPF实体也可以将广播报文发送给其他的UPF实体进行广播，通信时延较小，且广播的范围较大。
第四方面，提供一种CPF实体。该CPF实体具有实现上述方法设计中的CPF实体的功能。这些功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元。
在一个可能的设计中，该CPF实体的具体结构可包括收发器和处理器。处理器和收发器可执行上述第一方面或第一方面的任意一种可能的设计所提供的方法中的相应功能。
第五方面，提供一种UPF实体。该UPF实体具有实现上述方法设计中的UPF实体的功能。这些功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元。
在一个可能的设计中，该UPF实体的具体结构可包括收发器和处理器。处理器和收发器可执行上述第二方面或第二方面的任意一种可能的设计所提供的方法中的相应功能。
第六方面，提供一种CPF实体。该CPF实体具有实现上述方法设计中的CPF实体的功能。这些功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元。
在一个可能的设计中，该CPF实体的具体结构可包括收发器和处理器。处理器和收发器可执行上述第三方面或第三方面的任意一种可能的设计所提供的方法中的相应功能。
第七方面，提供一种CPF实体。该CPF实体具有实现上述方法设计中的CPF实体的功能。这些功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元。
在一个可能的设计中，该CPF实体的具体结构可包括收发模块和处理模块。处理模块和收发模块可执行上述第一方面或第一方面的任意一种可能的设计所提供的方法中的相应功能。
第八方面，提供一种UPF实体。该UPF实体具有实现上述方法设计中的UPF实体的功能。这些功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元。
在一个可能的设计中，该UPF实体的具体结构可包括收发模块和处理模块。处理模块和收发模块可执行上述第二方面或第二方面的任意一种可能的设计所提供的方法中的相应功能。
第九方面，提供一种CPF实体。该CPF实体具有实现上述方法设计中的CPF实体的功能。这些功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个 或多个与上述功能相对应的单元。
在一个可能的设计中，该CPF实体的具体结构可包括收发模块和处理模块。处理模块和收发模块可执行上述第三方面或第三方面的任意一种可能的设计所提供的方法中的相应功能。
第十方面，提供一种通信装置。该通信装置可以为上述方法设计中的CPF实体，或者为设置在CPF实体中的芯片。该通信装置包括：存储器，用于存储计算机可执行程序代码；以及处理器，处理器与存储器耦合。其中存储器所存储的程序代码包括指令，当处理器执行所述指令时，使通信装置执行上述第一方面或第一方面的任意一种可能的设计中CPF实体所执行的方法。
第十一方面，提供一种通信装置。该通信装置可以为上述方法设计中的UPF实体，或者为设置在UPF实体中的芯片。该通信装置包括：存储器，用于存储计算机可执行程序代码；以及处理器，处理器与存储器耦合。其中存储器所存储的程序代码包括指令，当处理器执行所述指令时，使通信装置执行上述第二方面或第二方面的任意一种可能的设计中UPF实体所执行的方法。
第十二方面，提供一种通信装置。该通信装置可以为上述方法设计中的CPF实体，或者为设置在CPF实体中的芯片。该通信装置包括：存储器，用于存储计算机可执行程序代码；以及处理器，处理器与存储器耦合。其中存储器所存储的程序代码包括指令，当处理器执行所述指令时，使通信装置执行上述第三方面或第三方面的任意一种可能的设计中CPF实体所执行的方法。
第十三方面，提供一种通信系统，该通信系统可包括如第五方面所述的UPF实体，以及如第六方面所述的CPF实体。
第十四方面，提供一种计算机存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述第一方面或第一方面的任意一种可能的设计中所述的方法。
第十五方面，提供一种计算机存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述第二方面或第二方面的任意一种可能的设计中所述的方法。
第十六方面，提供一种计算机存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述第三方面或第三方面的任意一种可能的设计中所述的方法。
第十七方面，提供一种包含指令的计算机程序产品，所述计算机程序产品中存储有指令，当其在计算机上运行时，使得计算机执行上述第一方面或第一方面的任意一种可能的设计中所述的方法。
第十八方面，提供一种包含指令的计算机程序产品，所述计算机程序产品中存储有指令，当其在计算机上运行时，使得计算机执行上述第二方面或第二方面的任意一种可能的设计中所述的方法。
第十九方面，提供一种包含指令的计算机程序产品，所述计算机程序产品中存储有指令，当其在计算机上运行时，使得计算机执行上述第三方面或第三方面的任意一种可能的设计中所述的方法。
本申请实施例中，在将V2X server下沉到边缘后，无需local V2X server的参与，UPF 实体就可以直接转发报文，实现了UPF实体之间的信息互通，减小了网络通信的时延。而且，也无需为了报文转发而部署local V2X server，可以减少local V2X server的部署量，有效降低成本，也降低了报文的转发路径的复杂性。
附图说明
图1为现有技术中V2X的一种应用场景示意图；
图2为本申请实施例的一种应用场景示意图；
图3为本申请实施例的另一种应用场景示意图；
图4为本申请实施例提供的一种报文组播方法的流程图；
图5为本申请实施例提供的一种更新组播路由的方法的流程图；
图6为本申请实施例提供的一种报文组播方法的流程图；
图7为本申请实施例提供的一种报文广播方法的流程图；
图8为本申请实施例提供的CPF实体的一种结构示意图；
图9为本申请实施例提供的UPF实体的一种结构示意图；
图10为本申请实施例提供的CPF实体的一种结构示意图；
图11A-图11B为本申请实施例提供的通信装置的结构示意图。
具体实施方式
为了使本发明实施例的目的、技术方案和优点更加清楚，下面将结合附图对本发明实施例作进一步地详细描述。
本文中描述的技术可用于各种通信系统，例如长期演进(Long Term Evolution，LTE)系统，第五代移动通信系统(5G)，以及其他此类通信系统。
以下，对本发明实施例中的部分用语进行解释说明，以便于本领域技术人员理解。
(1)终端设备，包括向用户提供语音和/或数据连通性的设备，例如可以包括具有无线连接功能的手持式设备、或连接到无线调制解调器的处理设备。该终端设备可以经无线接入网(radio access network，RAN)与核心网进行通信，与RAN交换语音和/或数据。该终端设备可以包括用户设备(user equipment，UE)、无线终端设备、移动终端设备、订户单元(subscriber unit)、订户站(subscriber station)，移动站(mobile station)、移动台(mobile)、远程站(remote station)、接入点(access point，AP)、远程终端设备(remote terminal)、接入终端设备(access terminal)、用户终端设备(user terminal)、用户代理(user agent)、或用户装备(user device)等。例如，可以包括移动电话(或称为“蜂窝”电话)，具有移动终端设备的计算机，便携式、袖珍式、手持式、计算机内置的或者车载的移动装置，智能穿戴式设备等。例如，个人通信业务(personal communication service，PCS)电话、无绳电话、会话发起协议(session initiation protocol，SIP)话机、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、智能手表、智能头盔、智能眼镜、智能手环、等设备。还包括受限设备，例如功耗较低的设备，或存储能力有限的设备，或计算能力有限的设备等。例如包括条码、射频识别(radio frequency identification，RFID)、传感器、全球定位系统(global positioning system，GPS)、激光扫描器等信息传感设备。
在本发明实施例中，终端设备还可以包括V2X设备，例如为车辆中的车载单元(on board unit，OBU)，且下文中主要以终端设备是V2X设备为例。
(2)网络设备，例如包括接入网设备和核心网设备。接入网设备例如包括基站(例如，接入点)，可以是指接入网中在空中接口上通过一个或多个扇区与无线终端通信的设备。基站可用于将收到的空中帧与网际协议(IP)分组进行相互转换，作为终端与接入网的其余部分之间的路由器，其中接入网的其余部分可包括IP网络。基站还可协调对空中接口的属性管理。例如，基站可以包括LTE系统或演进的LTE系统(LTE-Advanced，LTE-A)中的演进型基站(eNB或e-NodeB，evolved Node B)，或LTE系统或LTE-A系统中的小基站(micro/pico eNB)，或者也可以包括NR系统中的下一代节点B(next generation node B，gNB)，或者是传输点(transmission point，TP)，也可以是收发节点(transmission and receiver point，TRP)，等等，本发明实施例并不限定。
核心网设备例如包括移动管理实体(Mobility Management Entity，MME)、广播多播服务中心(broadcast multicast service center，BMSC)、或MBMS-GW等，或者也可以包括5G新无线(new radio，NR)系统中的相应功能实体，例如CPF实体或UPF实体等。
(3)V2X，目前，车辆可以通过车辆与车辆之间通信(vehicle to vehicle，V2V)或者车辆与路边基础设施通信(vehicle to infrastructure，V2I)，或者车辆与行人之间的通信(vehicle to pedestrian，V2P)，或者车辆与网络通信(vehicle to network，V2N)等方式来及时获取路况信息或接收信息，这些通信方式可以统称为V2X通信。以最常见的V2V和V2I为例：车辆通过V2V通信，可以将自身的车速、行驶方向、具体位置、是否踩了紧急刹车等信息广播给周围车辆，周围车辆通过获取该类信息，使得驾驶员可以更好地感知视距外的交通状况，从而对危险状况作出提前预判，进而作出及时避让。而对于V2I通信，除了上述安全信息的交互外，路边基础设施还可以为车辆提供各类服务信息和数据网络的接入等，不停车收费、车内娱乐等功能都极大地提高了交通智能化。一般将V2X通信所使用的网络称为车联网。
(4)移动边缘计算(mobile edge computing，MEC)，为避免移动承载网络被管道化，电信标准组织和运营商正在研究在未来5G网络中，如何与移动互联网及物联网业务深度融合，进而提升移动网络带宽的价值。欧洲电信标准协会(european telecommunications standards institute，ETSI)提出的MEC是基于5G演进的架构，并将移动接入网与互联网业务深度融合的一种技术。MEC一方面可以改善用户体验，节省带宽资源，另一方面通过将计算能力下沉到移动边缘节点，提供第三方应用集成，为移动边缘入口的服务创新提供了无限可能。
目前，可以在多个区域应用MEC，例如一个区域部署一套MEC，一套MEC可以包括一个local V2X server以及一个UPF实体，该UPF实体即为边缘UPF实体。边缘UPF实体可以与基站通信，可将基站发送的报文转发给local V2X server，也可以将local V2X server生成的报文转发给基站。边缘UPF实体也可以与CPF实体通信。这也是在演进的多媒体广播和组播业务(evolved multimedia broadcast and multicast services，eMBMS)基础上进行的改进，相当于将MBMS能力下沉部署到了边缘UPF实体，其中边缘UPF实体就可以看做是通过边缘网关实现，同时将local V2X server也同步部署到了边缘，满足低时延的需求。
(5)本发明实施例中的术语：“系统”和“网络”可被互换使用。“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，字符“/”，如无特殊说 明，一般表示前后关联对象是一种“或”的关系。
为了更好地理解本发明实施例提供的技术方案，请参考图2，介绍本申请实施例的一种应用场景。图2中包括两套MEC，分别为MEC1和MEC2，MEC1下部署了第一UPF实体、第一local V2X server、以及第一基站，第一基站能够与第一终端设备和第二终端设备通信，MEC2下部署了第二UPF实体、第二local V2X server、以及第二基站，第二基站能够与第三终端设备和第四终端设备通信。第一UPF实体和第二UPF实体均为边缘UPF实体，第一UPF实体和第二UPF实体均能够与CPF实体通信，也均能够与中心UPF实体通信，中心UPF实体可理解为未下沉到边缘的UPF实体。其中，图1中的第一local V2X server和第二local V2X server均以虚线表示，这是表明，在本申请实施例中，local V2X server可以部署也可以无需部署，本申请实施例所提供的方案实际上可以无需用到local V2X server，因此local V2X server可以无需部署，降低成本。但鉴于local V2X server还可以实现一些其他的功能，因此也可以继续部署。那么在部署local V2X server时，可以根据具体需求，可能无需在每套MEC下都部署local V2X server，也能够在一定程度上降低成本。另外在下文中，为了简单起见，将local V2X server简称为server。
另外请参考图3，为本申请实施例的另一种应用场景。与图2相比，图3中增设了远程控制中心(remote controller)，远程控制中心可用于控制各个MEC下的终端设备。例如终端设备为智能车辆，则远程控制中心可统一控制这些智能车辆。在现有技术中，远程控制中心是与V2X server通信，而在本申请实施例中，远程控制中心既可以与local V2X server通信，也可以与UPF实体通信。
后文中将会提及的UPF实体(例如图2或图3中所示的第一UPF实体或第二UPF实体)，如无特殊说明，则均是指边缘UPF实体，且这些UPF实体均具有MBMS能力。
请参见图4，本申请实施例提供一种报文组播方法，在下文的介绍过程中，以该方法应用在图2所示的应用场景或图3所示的应用场景为例。该方法的流程介绍如下。
S401、第一终端设备附着(attach)到网络，附着过程可参考标准的附着过程。
这里是以第一终端设备为例，实际上可适用于任意一个边缘UPF实体下的任意一个终端设备。
S402、第一终端设备附着网络后，第一终端设备向编队管理服务器申请加入相应的编队。当然，第一终端设备需要首先注册到编队管理服务器，再申请加入相应的编队。其中，第一终端设备在附着到网络后可以立即向编队管理服务器申请注册，或者，第一终端设备在附着到网络后也可以在需要加入相应编队时再向编队管理服务器申请注册。
具体的，可以是第一终端设备通过第一终端设备中安装的V2X应用(APP)程序向编队管理服务器中安装的编队管理服务程序(platooning manager)申请，以申请加入编队。编队管理服务器可以与多个终端设备通信。例如，第一终端设备发送给编队管理服务器的注册请求中携带编队的标识，编队管理服务器接收该注册请求后，就可以获得编队的标识，从而确定该第一终端设备要加入的是该编队的标识所指示的编队。
其中，编队管理服务程序用于管理编队。例如，终端设备具体为车辆中的OBU，多个OBU可以组成一个编队，即，一个编队可包括至少一个终端设备，从而便于对OBU实现统一调度管理。例如有一个车队，该车队包括10个车辆，则这10个车辆(即车辆中的OBU)可以申请加入同一个编队，例如这10个车辆中的OBU可以事先协商，确定待加入的编队的标识，显然，如果 这10个车辆加入同一个编队，则这10个车辆中的OBU可以协商得到一个编队的标识，这10个车辆的OBU都向编队管理服务程序请求加入该编队的标识所指示的编队。
其中，第一终端设备在向编队管理服务程序注册后可即刻向编队管理服务程序申请加入相应的编队，或者第一终端设备在向编队管理服务程序注册后也可以先正常工作，在认为需要加入相应编队时再向编队管理服务程序申请加入编队。
S403、编队管理服务程序将第一终端设备加入编队，并向CPF实体发送组播组建立请求，则CPF实体从编队管理服务程序接收该组播组建立请求。图4中，S403就包括两个部分，一个部分是编队管理服务器将第一终端设备加入编队，另一个部分是编队管理服务器向CPF实体发送组播组建立请求。
该组播组建立请求携带该编队的编队信息，该编队信息例如包括该编队的标识，该组播组建立请求用于为该编队请求组播地址，可选的，该组播组建立请求还可用于为该编队请求组播权限。
为编队申请组播权限和组播地址，相当于将该编队组成一个组播组，从而该编队包括的终端设备之间可以通过组播的方式互通信息。如果编队管理服务程序事先已经为第一终端设备所申请加入的编队申请了组播权限和组播地址，则S402中编队管理服务程序可以无需再向CPF实体申请该编队的组播权限和组播地址。
S404、CPF实体为该组播组分配组播地址，即，以该组播地址作为目的地址时的报文转发路由。
CPF实体可以授权该编队信息所指示的编队构成一个组播组，则该组播组就包括了该编队所包括的全部的终端设备，且CPF实体为该组播组分配组播地址，还可以为该组播组指示组播权限。
S405、CPF实体将分配的组播地址发送给编队管理服务程序，则编队管理服务程序接收该组播地址。
S406、编队管理服务程序向第一终端设备发送编队接入结果和组播地址，则第一终端设备接收编队接入结果和组播地址。
编队管理服务程序是将CPF实体分配的组播地址发送给第一终端设备，所以也可以理解为是CPF实体将组播地址发送给第一终端设备，或者理解为，是CPF实体通过编队管理服务程序将组播地址发送给第一终端设备。
编队接入结果表明已将第一终端设备加入第一终端设备所申请加入的编队，或者表明拒绝将第一终端设备加入第一终端设备所申请加入的编队。当然，如果编队接入结果表明拒绝将第一终端设备加入第一终端设备所申请加入的编队，则编队管理服务程序也就不会向第一终端设备发送组播地址，因此，S406是以编队接入结果表明已将第一终端设备加入第一终端设备所申请加入的编队为例，那么，第一终端设备后续就可以在该组播组中发送组播报文，也可以接收该组播组中的其他设备发送的组播报文。
该编队中的其他终端设备加入编队并获取组播地址的过程均可参考S401-S406的执行过程，不多赘述。
S407、远程控制中心向编队管理服务程序申请加入该编队。
图3所示的应用场景中介绍了远程控制中心，远程控制中心可用于控制系统中的多个终端设备，这多个终端设备可以属于同一个UPF实体，也可以属于不同的UPF实体。这多个终端设 备可以构成多个组播组，那么远程控制中心可以加入其中的每个组播组，对于一个组播组来说，远程控制中心就是该组播组中的一个成员设备，其地位与该组播组中的其他终端设备的地位相同。然而对于多个终端设备来说，远程控制中心可以作为一个控制设备，能够对终端设备的操作进行控制。例如终端设备具体为车辆中的OBU，则远程控制中心可以控制车辆的行为，例如可以根据路况、天气情况、每个车辆的车速、以及车辆之间的间距中的至少一个因素，当然还可以根据其他的因素，来控制车辆的行进，减少车祸概率，使得车辆有序行驶。
例如有一个车队，该车队包括10个车辆，则这10个车辆(即车辆中的OBU)可以申请加入同一个编队，例如这10个车辆中的OBU可以事先协商，确定待加入的编队的标识，显然，如果这10个车辆加入同一个编队，则这10个车辆的OBU可以协商得到一个编队的标识，这10个车辆的OBU都向编队管理服务程序请求加入该编队的标识所指示的编队。因为远程控制中心能够与每个终端设备通信，则远程控制中心可以获取该编队的编队信息，从而远程控制中心也可以向编队管理服务程序申请加入该编队信息所指示的编队，即，与这10个车辆加入同一编队，进而加入同一个组播组。
S408、编队管理服务程序将CPF实体分配的组播地址发送给远程控制中心，则远程控制中心接收该组播地址。
在本申请实施例中，因为通过执行S402-S405，编队管理服务程序已经获得了该编队信息所指示的编队所属的组播组的组播地址，因此编队管理服务程序无需再次向CPF实体请求组播地址，而是直接将CPF实体在S404中分配的组播地址发送给远程控制中心即可。如果编队管理服务程序还未获得远程控制中心所申请加入的编队对应的组播组的组播地址，则编队管理服务程序可继续按照S402-S405所介绍的步骤，向CPF实体申请组播地址。
其中，S402-S406，以及S407-S408，这两个部分的执行顺序可以任意，例如S402-S406在S407-S408之前执行，或者S402-S406在S407-S408之后执行，或者S402-S406在S407-S408同时执行，本申请实施例不作限制。其中，S402-S406在S407-S408之前，可以是指S402在S407之前，而S403-S406和S408之间的顺序可以任意，例如S408可以在S403之前执行，或者在S403之后以及S404之前执行，或者在S404之后以及S405之前执行，或者在S405之后以及S407之前执行，或者在S407之后执行。对于S402-S406在S407-S408之后或S402-S406在S407-S408同时执行的情况也是同样。
S409、第一终端设备获取组播地址后，则可以向CPF实体发送组播组加入请求，CPF实体从第一终端设备接收该组播组加入请求。该组播组加入请求用于第一终端设备请求加入该组播地址所指示的组播组。
其中，在S408执行完毕后就可以S409。
具体的，第一终端设备可以是向第一终端设备所在的UPF实体发送组播组加入请求，例如为图2或图3中所示的第一UPF实体，则第一UPF实体接收组播组加入请求。之后，第一UPF实体将该组播组加入请求转发给CPF实体，则CPF实体接收该组播组加入请求。
S410、CPF实体将第一终端设备加入该组播组。
S411、CPF实体生成目的地址为该组播地址的组播转发路由。
对于目的地址是该组播地址的组播报文，根据该组播转发路由就可以实现转发。
如果第一终端设备是第一个加入该组播组的终端设备，则CPF实体生成目的地址为该组播地址的组播转发路由，例如一种组播地址为224.X.X.X。图4以CPF实体生成组播转发路由为例， 而如果第一终端设备不是第一个加入该组播组的终端设备，例如还有该其他终端设备先向CPF实体申请加入该组播组，则CPF实体可能已经生成了目的地址为该组播地址的组播转发路由，则S411应该为：CPF实体更新该组播转发路由。即，CPF实体可以在该组播组中添加第一个终端设备时就生成组播转发路由，后续如果有终端设备再请求加入该组播组，则CPF实体更新之前生成的组播转发路由即可，无需再次生成组播转发路由。
同理，远程控制中心也可以申请加入该组播组，远程控制中心申请加入该组播组、以及CPF实体的处理过程，可参考S409-S411的介绍，其中远程控制中心的处理过程与第一终端设备的处理过程相同。
S412、CPF实体将生成的组播转发路由发送给至少一个UPF实体，则至少一个UPF实体从CPF实体接收该组播转发路由。其中，至少一个UPF实体为该组播组所包括的所有的终端设备所在的UPF实体。图4中只画出了第一UPF实体，其他UPF实体接收组播转发路由的过程都是类似的。
在本申请实施例中，组播转发路由包括该组播地址与该组播组所包括的所有终端设备之间的映射关系，这里的组播地址与终端设备之间的映射关系，可以包括该组播组中的每个终端设备所在的UPF实体与所述每个终端设备所在的基站之间的映射关系，以及包括所述每个终端设备所在的基站与所述每个终端设备之间的映射关系。简单理解来说，例如对于该组播组中的一个终端设备，则组播转发路由所包括的该终端设备的路由为：该终端设备所在的UPF实体-该终端设备所在的基站-该终端设备。
例如，第一终端设备所在的UPF实体为第一UPF实体，则第一UPF实体如果接收了该组播组中的其他设备所发送的组播报文，根据该组播转发路由，就可以直接将该组播报文发送给第一终端设备所在的基站，从而第一终端设备所在的基站可以进一步将该组播报文发送给第一终端设备。或者，如果第二UPF实体接收了该组播组中的其他设备所发送的组播报文，第二UPF实体和第一UPF实体为不同的UPF实体，则第二UPF实体根据该组播转发路由，就可以将该组播报文发送给第一UPF实体，第一UPF实体接收该组播报文后，可以将该组播报文发送给第一终端设备所在的基站，从而第一终端设备所在的基站将该组播报文发送给第一终端设备。即，通过本申请实施例提供的技术方案，UPF实体之间可以直接进行信息交互，从而能够实现UPF实体之间的信息互通。另外，在进行报文组播时甚至可以无需local V2X server的参与，可以减少local V2X server的部署量，有效降低成本，也使得报文的转发路径更为简单。
UPF实体之间要进行信息交互，需要首先在UPF实体之间建立通信连接。在本申请实施例中，如果CPF实体确定一个组播组所包括的终端设备所属的UPF实体为至少两个UPF实体，则CPF实体可以向至少两个UPF实体中的至少一个UPF实体发送通信连接建立请求，以请求至少两个UPF实体中的每两个UPF实体之间建立通信连接，这样，一个组播组包括的终端设备所在的UPF实体之间可以互相发送信息，从而实现组播。
在本申请实施例中，对于一个UPF实体来说，其可以存储多个组播转发路由，这多个组播转发路由可以包括该UPF实体所服务的所有的终端设备所加入的所有组播组的路由，一个组播组的路由，就包括该组播组所包括的所有的终端设备、其中的每个终端设备所在的基站、其中的每个基站与UPF实体，三者之间的映射关系。例如，第一UPF实体服务的终端设备包括第一终端设备和第三终端设备，第一终端设备加入了组播组1和组播组2，第三终端设备加入了组播组3，则第一UPF实体所存储的组播转发路由就包括组播组1的路由、组播组2的路由、及组播组3的路由。例如，组播组1中包括第一终端设备和第二终端设备，第一终端设备所属的 UPF实体为第一UPF实体，第一终端设备所属的基站为第一UPF实体下的第一基站，第二终端设备所属的UPF实体为第二UPF实体，第二终端设备所属的基站为第二UPF实体下的第二基站，则第一UPF实体所存储的组播转发路由就包括如下映射关系：
Figure PCTCN2018074025-appb-000001
对于组播组2和组播组3来说也是同样，不多赘述。当然如上只是表示组播转发路由所包括的信息，不代表组播转发路由的实际存储方式。
总之，UPF实体可以直接根据存储的组播转发路由发送所接收的组播报文。
如上介绍的是如何生成组播转发路由的过程，而在生成组播转发路由之后，如果该组播组中的终端设备发生了变动，例如有新的终端设备加入，或者有终端设备退出，或者有终端设备的路径发生改变，则还会涉及到更新该组播转发路由的过程，下面进行介绍。
请参见图5，本申请实施例提供一种更新组播转发路由的方法，在下文的介绍过程中，以该方法应用在图2所示的应用场景或图3所示的应用场景为例。该方法可以在图4所示的实施例执行完毕后执行。
S501、CPF实体确定第二终端设备进行了小区切换，且CPF实体确定第二终端设备切换后的小区所在的基站与第二终端设备切换前的小区所在的基站为不同的基站。其中，第二终端设备为图4所示的实施例中介绍的组播组所包括的终端设备。
终端设备在进行小区切换时，切换流程涉及到CPF实体，因此CPF实体可以感知终端设备的切换过程，这部分内容可参考标准中的小区切换过程，不多赘述。
S502、CPF实体更新目的地址为该组播地址的组播转发路由，即，CPF实体更新图4所示的实施例中生成的组播转发路由。
如果第二终端设备切换后的小区所在的基站与第二终端设备切换前的小区所在的基站为同一个基站，则组播转发路由可能不存在改变的情况，但如果第二终端设备切换后的小区所在的基站与第二终端设备切换前的小区所在的基站为不同的基站，则在进行组播时可能就会涉及到路由改变的情况。第二终端设备切换后的小区所在的基站与第二终端设备切换前的小区所在的基站为不同的基站，又包括不同的情况，涉及到不同的路由改变方式，下面进行介绍。
情况1、第二终端设备切换后的小区所在的基站与第二终端设备切换前的小区所在的基站属于同一个UPF实体。
在这种情况下，只需更改组播转发路由中UPF实体到基站之间的映射关系即可，例如在组播转发路由中，原本的映射关系为第一UPF实体-第一基站-第二终端设备，第二终端设备发生切换后，切换到了该第一UPF实体下的第二基站，则CPF实体可以将组播转发路由中的该映射关系更新为第一UPF实体-第二基站-第二终端设备。
情况2、第二终端设备切换后的小区所在的基站与第二终端设备切换前的小区所在的基站属于不同的UPF实体。
在这种情况下，需要更改组播转发路由中的直接目的设备。例如在组播转发路由中，原本的映射关系为第一UPF实体-第一基站-第二终端设备，即，原本为第二终端设备服务的UPF实体为第一UPF实体。第二终端设备发生切换后，切换到了第二UPF实体下的第二基站，则CPF实体可以将组播转发路由中的该映射关系更新为第二UPF实体-第二基站-第二终端设备，即，将直接目的设备由第一UPF实体更改为第二UPF实体。
S503、CPF实体将更新后的组播转发路由发送给至少一个UPF实体，以及，发送给第二终端设备切换后的基站所在的UPF实体。这里的至少一个UPF实体是该组播组包括的所有的终端设备所在的UPF实体。图5以CPF实体将更新后的组播转发路由发送给第一UPF实体为例。
其中，第二终端设备切换后的基站所在的UPF实体与第二终端设备切换前的基站所在的UPF实体可能是同一个UPF实体，也可能是不同的UPF实体，如果第二终端设备切换后的基站所在的UPF实体与第二终端设备切换前的基站所在的UPF实体是不同的UPF实体，则第二终端设备切换后的UPF实体可以是至少一个UPF实体中的一个，或者也可以是之前并不属于该组播组的UPF实体，本申请实施例不作限制。其中，不属于一个组播组的UPF实体，是指不是该组播组所包括的终端设备所在的UPF实体。
另外，如果第二终端设备切换后的基站所在的UPF实体与第二终端设备切换前的基站所在的UPF实体是不同的UPF实体，且第二终端设备切换后的UPF实体是之前并不属于该组播组的UPF实体，则第二终端设备切换后的UPF实体与属于该组播组的UPF实体之间可能还未建立通信连接。因此在这种情况下，核心网设备可以向第二终端设备切换后的UPF实体和属于该组播组的UPF实体中的至少一个UPF实体发送通信连接建立请求，以使得第二终端设备切换后的UPF实体和属于该组播组的UPF实体中的每个UPF实体之间建立通信连接。
图5所示的实施例中，CPF实体更新组播转发路由是因为组播组中有终端设备发生了小区切换，而在其他一些场景中，例如该组播组中有新的终端设备加入，或者该组播组中有终端设备退出，CPF实体都需要更新组播转发路由，并将更新后的组播转发路由发送给相应的UPF实体。其中，如果该组播组中有新的终端设备加入，则CPF实体更新组播转发路由后，除了将更新的组播转发路由发送给该组播组包括的所有的终端设备所在的UPF实体之外，还将更新的组播转发路由发送给新加入的终端设备所在的UPF实体，当然，新加入的设备所在的UPF实体可能是该组播组包括的所有的终端设备所在的UPF实体中的一个，也可能原本不属于该组播组包括的所有的终端设备所在的UPF实体，这里所述的该组播组包括的所有的终端设备，暂时不包括新加入的终端设备。如果该组播组中有终端设备退出，则CPF实体更新组播转发路由后，将更新的组播转发路由发送给该组播组包括的所有的终端设备所在的UPF实体，这里所述的该组播组包括的所有的终端设备，也包括退出的终端设备。其他的相应过程可参考图5所示的实施例的介绍，不多赘述。
如上的实施例中，主要介绍了UPF实体如何得到组播转发路由，也介绍了组播转发路由如何更新，那么下面就介绍UPF实体如何根据组播转发路由来转发组播报文。
请参见图6，本申请实施例提供一种报文组播方法，在下文的介绍过程中，以该方法应用在图2所示的应用场景或图3所示的应用场景为例。在该方法中，UPF实体可根据图4所示的实施例中生成的组播转发路由或根据图5所示的实施例中更新的组播转发路由实现组播报文的转发。
S601、第一终端设备生成组播报文，该组播报文携带组播地址。
在图4所示的实施例中，第一终端设备在S405中可以获得CPF实体分配的组播地址，因此第一终端设备在需要发送组播报文时，可以直接携带组播地址。第一终端设备可能加入多个组播组，该组播报文可以发送给多个组播组中的一个组播组。
S602、第一终端设备向第一UPF实体发送该组播报文，则第一UPF实体接收该组播报文。
其中，第一UPF实体是第一终端设备所在的基站所在的UPF实体，具体的，第一终端设备向第一UPF实体发送该组播报文，可以是第一终端设备向第一终端设备所在的第一基站发送该组播报文，第一基站再向第一UPF实体发送该组播报文。
第一UPF实体接收报文后，通过该报文携带的目的地址就可以知道该报文是什么类型的报文，例如是广播报文、组播报文或单播报文。
例如第一终端设备属于第一基站，图6中未画出第一基站，因此图6中的S601中由第一终端设备指向第一UPF实体的箭头，实际上的含义是第一终端设备将该组播报文发送给第一基站，再由第一基站将该组播报文发送给第一UPF实体。
在本申请实施例中，对于描述为终端设备与UPF实体之间的通信，如无特殊说明的，都表明终端设备是通过基站与UPF实体通信。
S603、第一UPF实体查询存储的组播转发路由，将该组播报文转发给组播转发路由所指示的设备。
例如组播转发路由指示，该组播地址所对应的组播组包括3个目的设备，分别为第一UPF实体下的第二终端设备、远程控制中心、以及第二UPF实体下的第三终端设备。且该组播转发路由指示了，到第二终端设备的路由为第一UPF实体-第一基站-第二终端设备，到远程控制中心的路由为当前的UPF实体-远程控制中心，到第三终端设备的路由为第一UPF实体-第二UPF实体-第二基站-第三终端设备。那么，第一UPF实体根据组播转发路由的指示，转发过程包括：
S6031、第一UPF实体将该组播报文封装到第二终端设备所在的隧道，即，将该组播报文发送给第一基站，第一基站接收该组播报文，再由第一基站将该组播报文发送给第二终端设备；其中，图6中未画出第一基站，因此图6中的S6031中由第一UPF实体指向第二终端设备的箭头，实际上的含义是第一UPF实体将该组播报文发送给第一基站，再由第一基站将该组播报文发送给第二终端设备；
S6032、当前的UPF实体就是第一UPF实体，第一UPF实体将该组播报文转换为单播报文，通过上行方式发送给远程控制中心，则远程控制中心接收该组播报文；
S6033、第一UPF实体将该组播报文封装到第一UPF实体和第二UPF实体之间的隧道，以将该组播报文发送给第二UPF实体，则第二UPF实体接收该组播报文。
第二UPF实体也存储了组播转发路由，第二UPF实体接收该组播报文后，根据组播转发路由就可以将该组播报文发送给第二基站，从而由第二基站将该组播报文发送给第三终端设备，如图6中的虚线所示的S6033，只是图6中未画出第二基站。
其中，S6031-S6033这3个步骤的执行顺序可以任意，步骤的编号不代表对执行顺序的限制。
本申请实施例中，可由UPF实体直接实现组播报文的转发，无需经过local V2X server，降低报文转发路径的复杂性，且可以减少local V2X server的部署量，降低成本。
如前介绍的都是报文组播的过程，在本申请实施例中，报文的广播也可以由UPF实体来直接实现，从而UPF实体之间可以实现信息的互通，下面通过另外的实施例来介绍本申请实施例提供的一种报文广播方法。在下文的介绍过程中，继续以该方法应用在图2所示的应用场景或图3所示的应用场景为例。请参见图7，该方法的流程介绍如下。
S701、终端设备向local V2X Server申请广播地址和广播权限。
例如，终端设备可以将用于申请广播地址和广播权限的消息发送给该终端设备所在的基站，该终端设备所在的基站接收该消息，将该消息转发给该基站所在的UPF实体，该基站所在的UPF实体接收该消息，再将该消息转发给local V2X Server，则local V2X Server接收该消息。
S702、local V2X Server向CPF实体发送广播权限请求，该广播权限请求用于请求通过第一UPF实体直接广播携带第一标识的广播报文，则CPF实体接收该广播权限请求。可以理解为，该广播权限请求可以用于请求第一UPF实体将携带第一标识的广播报文由上行单播转为下行广播。
其中，local V2X Server可以直接根据终端设备的请求为终端设备分配广播地址，则local V2X Server可将广播地址携带在广播权限请求中一并发送给核心网设备。
或者，S701和S702是以系统中部署了local V2X Server为例，如果系统中未部署local V2X Server，或者该终端设备所在的MEC未部署local V2X Server，则终端设备也可以直接向CPF实体申请广播地址和广播权限，那么可以理解为，终端设备向CPF实体发送该广播权限请求。在这种情况下，广播地址可以由CPF实体分配。
其中，第一UPF实体为该终端设备所在的UPF实体，第一标识为发送该广播报文的终端设备的标识，或者第一标识为该广播报文所属的业务流的流标识。
CPF实体可以查询第一标识是否为已授权的标识，如果第一标识为已授权的标识，则可以执行S703，如果第一标识还未授权，则CPF实体可以为第一标识授权，之后执行S703。在授权后，就可以通过第一UPF实体直接广播携带第一标识的广播报文。
S703、CPF实体向第一UPF实体发送通知消息，则第一UPF实体接收该通知消息。该通知消息用于指示第一标识为已授权的标识。
其中，第一UPF实体可直接广播携带已授权的标识的广播报文，即，对于携带已授权的标识的广播报文，第一UPF实体可以根据匹配的流规则，将此类广播报文封装到下行MBMS会话(Session)中进行转发，而无需再将携带已授权的标识的广播报文发送给local V2X Server后再转发。
S704、CPF实体完成对第一UPF实体的转发授权和策略更新后，响应local V2X Server的申请，具体的，CPF实体向local V2X Server发送广播权限响应，则local V2X Server接收该广播权限响应。该广播权限响应是对local V2X Server发送的广播权限请求的响应。
S705、local V2X Server向终端设备发送广播能力申请响应，则终端设备接收该广播能力申请响应。
其中，该广播能力申请响应可携带权限信息和授权的广播地址，该授权的广播地址就是如前介绍的local V2X Server或CPF实体生成的广播地址。权限信息可用于指示允许第一UPF实体直接广播携带第一标识的广播报文，或用于指示不允许第一UPF实体直接广播携带第一标识的广播报文。当然，如果权限信息用于指示不允许第一UPF实体直接广播携带第一 标识的广播报文，则local V2X Server也就不会向终端设备发送广播地址，因此S705是以权限信息用于指示允许第一UPF实体直接广播携带第一标识的广播报文为例。
另外，S704和S705继续是以系统中部署了local V2X Server为例，如果系统中未部署local V2X Server，或者该终端设备所在的MEC中未部署local V2X Server，则核心网完成对第一UPF实体的转发授权和策略更新后，可直接响应终端设备的广播权限请求，例如CPF实体可向终端设备发送权限信息和授权的广播地址，则终端设备接收该权限信息和授权的广播地址。
S706、终端设备生成第一报文，第一报文携带广播地址。则第一报文也就是广播报文，第一报文携带的广播地址为如前的步骤中所介绍的授权的广播地址。另外，第一报文还携带第一标识。
终端设备如有需要广播，则生成上行报文，该上行报文是按照广播格式进行封装，广播地址为授权的广播地址。
S707、终端设备将第一报文发送给第一UPF实体，则第一UPF实体接收该第一报文。
该第一报文可通过上行单播隧道转发到第一UPF实体。当然，终端设备是将第一报文发送给该终端设备所在的基站，再由该终端设备所在的基站将第一报文发送给第一UPF实体，该过程不多赘述。
或者，第一报文也可能是其他的UPF实体发送给第一UPF实体的，例如第二UPF实体下的终端设备生成第一报文，则该终端设备将第一报文发送给第二UPF实体，第二UPF实体又将第一报文发送给第一UPF实体。
S708、第一UPF实体根据第一报文携带的目的地址确定第一报文为广播报文，且第一UPF实体确定第一报文携带的第一标识为已授权的标识。
第一UPF实体接收第一报文后可以对第一报文进行解析，根据第一报文的目的地址就可以确定第一报文为何种类型的报文，例如为广播报文、组播报文或单播报文。
如果是广播报文，则第一UPF实体可以确定该广播报文携带的标识是否为已授权的标识，例如该广播报文携带第一标识，在如前的步骤中介绍了，第一标识为已授权的标识。
S709、第一UPF实体广播第一报文。
因为第一标识为已授权的标识，则第一UPF实体确定可由第一UPF实体直接广播第一报文，而无需再将第一报文发送给local V2X Server。因此，第一UPF实体查询存储的广播路由，从而广播该第一报文。
另外，在执行S701之前，local V2X Server会首先向CPF实体申请临时移动组标识(temporary mobile group identity，TMGI)，这部分内容可参考现有技术中的介绍。如果local V2X Server申请的TMGI覆盖了多个UPF实体的转发控制区域，则边缘的UPF实体需要分别向对端UPF实体申请加入一个组播组，成为对端UPF实体转发的下游节点，总之，要使得TMGI覆盖的多个UPF实体中的任意两个UPF实体中，都实现这两个UPF实体互为对方转发的下游节点。
因此，第一UPF实体在进行广播时，如果有其他UPF实体是第一UPF实体转发的下游节点，即第一UPF实体和其他UPF实体属于一个组播组，则第一UPF实体也可以一并将该第一报文组播给这些UPF实体，则这些UPF实体可以接收第一报文。这些UPF实体接收第一报文后，再继续广播第一报文。
本申请实施例中，提供了无需V2X server参与的低时延的组播或广播转发能力，能够更好地降低的转发时延。且因为无需V2X server参与组播或广播，能够减少V2X server的部署量，有效降低成本。另外，在将V2X server下沉到边缘后，能够支持组播消息或广播消息在MEC之间的转发，从而有效匹配业务的需求。
下面结合附图介绍本申请实施例提供的装置。
图8示出了一种CPF实体800的结构示意图。该CPF实体800可以实现上文中涉及的CPF实体的功能。该CPF实体800可以是上文中所述的CPF实体，或者可以是设置在上文中所述的CPF实体中的芯片。该CPF实体800可以包括处理器801和收发器802。其中，处理器801可以用于执行图4所示的实施例中的S404、S410、及S411，以及图5所示的实施例中的S503，和/或用于支持本文所描述的技术的其它过程。收发器802可以用于执行图4所示的实施例中的S403、S405、S409、及S412，以及图5所示的实施例中的S501和S502，和/或用于支持本文所描述的技术的其它过程。
例如，收发器802，用于接收组播组加入请求，所述组播组加入请求用于第一终端设备请求加入组播地址所指示的组播组；
处理器801，用于将所述终端设备加入所述组播组；及，生成目的地址为所述组播地址的组播转发路由；
收发器802，还用于将所述组播转发路由发送给至少一个UPF实体，所述至少一个UPF实体包括所述组播组所包括的所有终端设备所在的UPF实体。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
图9示出了一种UPF实体900的结构示意图。该UPF实体900可以实现上文中涉及的第一UPF实体的功能。该UPF实体900可以是上文中所述的第一UPF实体，或者可以是设置在上文中所述的第一UPF实体中的芯片。该UPF实体900可以包括处理器901和收发器902。其中，处理器901可以用于执行图7所示的实施例中的S708，和/或用于支持本文所描述的技术的其它过程。收发器902可以用于执行图7所示的实施例中的S703、S707、及S709，和/或用于支持本文所描述的技术的其它过程。其中，收发器902可以作为一个整体模块，既可以与终端设备进行交互，也可以与其他的UPF实体进行交互。或者，收发器902包括多个收发接口，其中的一部分收发接口用于与终端设备进行交互，还有一部分收发接口用于与其他的UPF实体进行交互。
例如，收发器902，用于接收第一报文；
处理器901，用于根据所述第一报文携带的目的地址确定所述第一报文为广播报文，以及，所述第一UPF实体确定所述第一报文携带的第一标识为已授权的标识，所述第一标识为发送所述第一报文的终端设备的标识，或为所述第一报文所属的业务流的流标识；
收发器902，还用于广播所述第一报文。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
图10示出了一种CPF实体1000的结构示意图。该CPF实体1000可以实现上文中涉及的CPF实体的功能。该CPF实体1000可以是上文中所述的CPF实体，或者可以是设置在上文中所述的CPF实体中的芯片。该CPF实体1000可以包括处理器1001和收发器1002。其中，处 理器1001可以用于执行图7所示的实施例中的S703及S704，和/或用于支持本文所描述的技术的其它过程。其中，处理器1001执行S703，主要是指，处理器1001查询第一标识是否为已授权的标识，如果第一标识还未授权，则处理器1001可以为第一标识授权。处理器1001执行S704，主要是指，处理器1001生成通知消息。收发器1002可以用于执行图7所示的实施例中的S702、S703、及704，和/或用于支持本文所描述的技术的其它过程。
例如，收发器1002，用于接收广播权限请求，所述广播权限请求用于请求通过第一UPF实体直接广播携带第一标识的广播报文，所述第一标识为发送所述广播报文的终端设备的标识，或为所述广播报文所属的业务流的流标识；
处理器1001，用于授权所述第一标识；
收发器1002，还用于向所述第一UPF实体发送通知消息，所述通知消息用于指示所述第一标识为所述已授权的标识，其中，所述第一UPF实体直接广播携带所述已授权的标识的广播报文。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在一个简单的实施例中，本领域的技术人员可以想到，还可以将CPF实体800、UPF实体900或CPF实体1000通过如图11A所示的通信装置1100的结构实现。该通信装置1100可以实现上文中涉及的CPF实体或第一UPF实体的功能。该通信装置1100可以包括处理器1101。其中，在该通信装置1100用于实现图4所示的实施例或图5所示的实施例中的CPF实体800的功能时，处理器1101可用于执行图4所示的实施例中的S404、S410、及S411，以及图5所示的实施例中的S503，和/或用于支持本文所描述的技术的其它过程。在该通信装置1100用于实现图7所示的实施例中的第一UPF实体的功能时，处理器1101可用于执行图7所示的实施例中的S708，和/或用于支持本文所描述的技术的其它过程。在该通信装置1100用于实现图7所示的实施例中的CPF实体800的功能时，处理器1101可用于执行图7所示的实施例中的S703及S704，和/或用于支持本文所描述的技术的其它过程。
其中，通信装置1100可以通过现场可编程门阵列(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)或其他集成芯片实现，则通信装置1100可被设置于本申请实施例的CPF实体或第一UPF实体中，以使得该CPF实体或第一UPF实体实现本申请实施例提供的报文组播方法或报文广播方法。
在一种可选实现方式中，该通信装置1100还可以包括存储器1102，可参考图11B，其中，存储器1102用于存储计算机程序或指令，处理器1101用于译码和执行这些计算机程序或指令。应理解，这些计算机程序或指令可包括上述CPF实体或第一UPF实体的功能程序。当CPF实体的功能程序被处理器1101译码并执行时，可使得该通信装置1100实现本申请实施例的报文组播方法或报文广播方法中CPF实体的功能。当第一UPF实体的功能程序被处理器1101译码并执行时，可使得该通信装置1100实现本申请实施例的报文广播方法中第一UPF实体的功能。
在另一种可选实现方式中，这些CPF实体或第一UPF实体的功能程序存储在通信装置1100 外部的存储器中。当CPF实体的功能程序被处理器1101译码并执行时，存储器1102中临时存放上述CPF实体的功能程序的部分或全部内容。当第一UPF实体的功能程序被处理器1101译码并执行时，存储器1102中临时存放上述第一UPF实体的功能程序的部分或全部内容。
在另一种可选实现方式中，这些CPF实体或第一UPF实体的功能程序被设置于存储在通信装置1100内部的存储器1102中。当通信装置1100内部的存储器112中存储有CPF实体的功能程序时，通信装置1100可被设置在本申请实施例的CPF实体中。当通信装置1100内部的存储器1102中存储有第一UPF实体的功能程序时，通信装置1100可被设置在本申请实施例的第一UPF实体中。
在又一种可选实现方式中，这些CPF实体的功能程序的部分内容存储在通信装置1100外部的存储器中，这些CPF实体的功能程序的其他部分内容存储在通信装置1100内部的存储器1102中。或，这些第一UPF实体的功能程序的部分内容存储在通信装置1100外部的存储器中，这些第一UPF实体的功能程序的其他部分内容存储在通信装置1100内部的存储器1102中。
在本申请实施例中，CPF实体800、UPF实体900、CPF实体1000及通信装置1100对应各个功能划分各个功能模块的形式来呈现，或者，可以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指ASIC，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。
另外，图8所示的实施例提供的CPF实体800还可以通过其他形式实现。例如该CPF实体包括处理模块和收发模块。例如处理模块可通过处理器801实现，收发模块可通过收发器802实现。其中，处理模块可以用于执行图4所示的实施例中的S404、S410、及S411，以及图5所示的实施例中的S503，和/或用于支持本文所描述的技术的其它过程。收发模块可以用于执行图4所示的实施例中的S403、S405、S409、及S412，以及图5所示的实施例中的S501和S502，和/或用于支持本文所描述的技术的其它过程。
例如，收发模块，用于接收组播组加入请求，所述组播组加入请求用于第一终端设备请求加入组播地址所指示的组播组；
处理模块，用于将所述终端设备加入所述组播组；及，生成目的地址为所述组播地址的组播转发路由；
收发模块，还用于将所述组播转发路由发送给至少一个UPF实体，所述至少一个UPF实体包括所述组播组所包括的所有终端设备所在的UPF实体。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
图9所示的实施例提供的UPF实体900还可以通过其他形式实现。例如该UPF实体包括处理模块和收发模块。例如处理模块可通过处理器901实现，收发模块可通过收发器902实现。其中，处理模块可以用于执行图7所示的实施例中的S708，和/或用于支持本文所描述的技术的其它过程。收发模块可以用于执行图7所示的实施例中的S703、S707、及S709，和/或用于支持本文所描述的技术的其它过程。其中，收发模块可以作为一个整体模块，既可以与终端设备进行交互，也可以与其他的UPF实体进行交互。或者，收发模块包括多个子收发模块，其中的一部分子收发模块用于与终端设备进行交互，还有一部分子收发模块用于与其他的UPF实体进行交互。一个子收发模块可通过前文所述的一个收发接口实现。
例如，收发模块，用于接收第一报文；
处理模块，用于根据所述第一报文携带的目的地址确定所述第一报文为广播报文，以及，所述第一UPF实体确定所述第一报文携带的第一标识为已授权的标识，所述第一标识为发送所述第一报文的终端设备的标识，或为所述第一报文所属的业务流的流标识；
收发模块，还用于广播所述第一报文。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
图10所示的实施例提供的CPF实体1000还可以通过其他形式实现。例如该CPF实体包括处理模块和收发模块。例如处理模块可通过处理器1001实现，收发模块可通过收发器1002实现。其中，处理模块可以用于执行图7所示的实施例中的S703及S704，和/或用于支持本文所描述的技术的其它过程。其中，处理模块执行S703，主要是指，处理模块查询第一标识是否为已授权的标识，如果第一标识还未授权，则处理器1001可以为第一标识授权。处理模块执行S704，主要是指，处理模块生成通知消息。收发模块可以用于执行图7所示的实施例中的S702、S703、及704，和/或用于支持本文所描述的技术的其它过程。
例如，收发模块，用于接收广播权限请求，所述广播权限请求用于请求通过第一UPF实体直接广播携带第一标识的广播报文，所述第一标识为发送所述广播报文的终端设备的标识，或为所述广播报文所属的业务流的流标识；
处理模块，用于生成通知消息，所述通知消息用于指示所述第一标识为所述已授权的标识，其中，所述第一UPF实体直接广播携带所述已授权的标识的广播报文；
收发模块，还用于向所述第一UPF实体发送所述通知消息。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
由于本申请实施例提供的CPF实体800、UPF实体900、CPF实体1000及通信装置1100可用于执行图4所示的实施例、图5所示的实施例、图6所示的实施例或图7所示的实施例所提供的方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
本申请实施例是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算 机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，数字通用光盘(digital versatile disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disk，SSD))等。
显然，本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (20)

  1. 一种报文组播方法，其特征在于，包括：
    控制面功能CPF实体接收组播组加入请求，所述组播组加入请求用于第一终端设备请求加入组播地址所指示的组播组；
    所述CPF实体将所述终端设备加入所述组播组；
    所述CPF实体生成目的地址为所述组播地址的组播转发路由；
    所述CPF实体将所述组播转发路由发送给至少一个用户面功能UPF实体，所述至少一个UPF实体包括所述组播组所包括的所有终端设备所在的UPF实体。
  2. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    所述CPF实体接收组播组建立请求，所述组播组建立请求携带编队信息，所述编队信息所指示的编队包括至少一个终端设备，所述组播组建立请求用于为所述编队请求组播地址，所述至少一个终端设备包括所述第一终端设备；
    所述CPF实体为所述编队分配所述组播地址。
  3. 如权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述CPF实体确定第二终端设备进行了小区切换，且所述第二终端设备切换后的小区与所述终端设备切换前的小区属于不同的基站，所述第二终端设备属于所述组播组；
    所述CPF实体更新所述组播转发路由；
    所述CPF实体将更新后的所述组播转发路由发送给所述至少一个UPF实体，以及发送给所述第二终端设备切换后所在的UPF实体。
  4. 一种报文广播方法，其特征在于，包括：
    第一用户面功能UPF实体接收第一报文；
    所述第一UPF实体根据所述第一报文携带的目的地址确定所述第一报文为广播报文，以及，所述第一UPF实体确定所述第一报文携带的第一标识为已授权的标识，所述第一标识为发送所述第一报文的终端设备的标识，或为所述第一报文所属的业务流的流标识；
    所述第一UPF实体广播所述第一报文。
  5. 如权利要求4所述的方法，其特征在于，所述方法还包括：
    所述第一UPF实体从控制面功能CPF实体接收通知消息，所述通知消息用于指示所述第一标识为所述已授权的标识；
    所述第一UPF实体根据所述通知消息确定所述第一标识为所述已授权的标识，其中，所述第一UPF实体直接广播携带所述已授权的标识的广播报文。
  6. 如权利要求4或5所述的方法，其特征在于，第一UPF实体接收第一报文，包括：
    所述第一UPF实体从所述第一UPF实体服务的终端设备接收所述第一报文，或，所述第一UPF实体从第二UPF实体接收所述第一报文。
  7. 如权利要求4-6任一所述的方法，其特征在于，所述方法还包括：
    所述第一UPF实体确定所述第一UPF实体所请求的临时移动组标识中还包括所述第二UPF实体的标识；
    所述第一UPF实体向所述第二UPF实体发送组播请求消息，用于请求与所述第二UPF实体加入同一组播组。
  8. 一种报文广播方法，其特征在于，包括：
    控制面功能CPF实体接收广播权限请求，所述广播权限请求用于请求通过第一用户面功能UPF实体直接广播携带第一标识的广播报文，所述第一标识为发送所述广播报文的终端设备的标识，或为所述广播报文所属的业务流的流标识；
    所述CPF实体向所述第一UPF实体发送通知消息，所述通知消息用于指示所述第一标识为所述已授权的标识，其中，所述第一UPF实体直接广播携带所述已授权的标识的广播报文。
  9. 一种控制面功能CPF实体，其特征在于，包括：
    收发模块，用于接收组播组加入请求，所述组播组加入请求用于第一终端设备请求加入组播地址所指示的组播组；
    处理模块，用于将所述终端设备加入所述组播组；
    所述处理模块，还用于生成目的地址为所述组播地址的组播转发路由；
    所述收发模块，还用于将所述组播转发路由发送给至少一个用户面功能UPF实体，所述至少一个UPF实体包括所述组播组所包括的所有终端设备所在的UPF实体。
  10. 如权利要求9所述的CPF实体，其特征在于，
    所述收发模块，还用于接收组播组建立请求，所述组播组建立请求携带编队信息，所述编队信息所指示的编队包括至少一个终端设备，所述组播组建立请求用于为所述编队请求组播地址，所述至少一个终端设备包括所述第一终端设备；
    所述处理模块，还用于为所述编队分配所述组播地址。
  11. 如权利要求9或10所述的CPF实体，其特征在于，
    所述处理模块，还用于确定第二终端设备进行了小区切换，且所述第二终端设备切换后的小区与所述终端设备切换前的小区属于不同的基站，所述第二终端设备属于所述组播组；及，更新所述组播转发路由；
    所述收发模块，还用于将更新后的所述组播转发路由发送给所述至少一个UPF实体，以及发送给所述第二终端设备切换后所在的UPF实体。
  12. 一种用户面功能UPF实体，其特征在于，包括：
    收发模块，用于接收第一报文；
    处理模块，用于根据所述第一报文携带的目的地址确定所述第一报文为广播报文，以及，所述第一UPF实体确定所述第一报文携带的第一标识为已授权的标识，所述第一标识为发送所述第一报文的终端设备的标识，或为所述第一报文所属的业务流的流标识；
    所述收发模块，还用于广播所述第一报文。
  13. 如权利要求12所述的UPF实体，其特征在于，
    所述收发模块，还用于从控制面功能CPF实体接收通知消息，所述通知消息用于指示所述第一标识为所述已授权的标识；
    所述处理模块，还用于根据所述通知消息确定所述第一标识为所述已授权的标识，其中，所述第一UPF实体直接广播携带所述已授权的标识的广播报文。
  14. 如权利要求12或13所述的UPF实体，其特征在于，所述收发模块，具体用于：
    从所述第一UPF实体服务的终端设备接收所述第一报文，或，从第二UPF实体接收所述第一报文。
  15. 如权利要求12-14任一所述的UPF实体，其特征在于，
    所述处理模块，还用于确定所述第一UPF实体所请求的临时移动组标识中还包括所述第二UPF实体的标识；
    所述收发模块，还用于向所述第二UPF实体发送组播请求消息，用于请求与所述第二UPF实体加入同一组播组。
  16. 一种控制面功能CPF实体，其特征在于，包括：
    收发模块，用于接收广播权限请求，所述广播权限请求用于请求通过第一用户面功能UPF实体直接广播携带第一标识的广播报文，所述第一标识为发送所述广播报文的终端设备的标识，或为所述广播报文所属的业务流的流标识；
    处理模块，用于授权所述第一标识；
    所述收发模块，还用于向所述第一UPF实体发送通知消息，所述通知消息用于指示所述第一标识为所述已授权的标识，其中，所述第一UPF实体直接广播携带所述已授权的标识的广播报文。
  17. 一种通信系统，其特征在于，包括如权利要求12-15任一项所述的用户面功能UPF实体，以及如权利要求16所述的控制面功能CPF实体。
  18. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储程序或指令，当所述程序或指令被一个或多个处理器运行时，实现根据权利要求1至3任一所述的方法。
  19. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储程序或指令，当所述程序或指令被一个或多个处理器运行时，实现根据权利要求4至7任一所述的方法。
  20. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储程序或指令，当所述程序或指令被一个或多个处理器运行时，实现根据权利要求8所述的方法。
PCT/CN2018/074025 2017-11-29 2018-01-24 一种报文组播、报文广播方法及设备 WO2019104857A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2018548178A JP6983169B2 (ja) 2017-11-29 2018-01-24 メッセージマルチキャスト方法、メッセージブロードキャスト方法およびデバイス

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711226691.7A CN109842854B (zh) 2017-11-29 2017-11-29 一种报文组播、报文广播方法及设备
CN201711226691.7 2017-11-29

Publications (1)

Publication Number Publication Date
WO2019104857A1 true WO2019104857A1 (zh) 2019-06-06

Family

ID=66665358

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/074025 WO2019104857A1 (zh) 2017-11-29 2018-01-24 一种报文组播、报文广播方法及设备

Country Status (3)

Country Link
JP (1) JP6983169B2 (zh)
CN (1) CN109842854B (zh)
WO (1) WO2019104857A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113973076A (zh) * 2020-07-24 2022-01-25 华为技术有限公司 一种多播切换方法及装置
CN115134761A (zh) * 2021-03-29 2022-09-30 维沃移动通信有限公司 切换方法、装置、网络侧设备及终端
CN115515088A (zh) * 2021-06-22 2022-12-23 北京新媒传信科技有限公司 一种业务流程链的编排方法、5g消息的交互方法及装置

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110247779B (zh) * 2019-06-17 2021-08-10 腾讯科技（深圳）有限公司 虚拟网络群组的组播组的组播方法、装置、设备及系统
CN112866931B (zh) * 2019-06-17 2022-04-15 腾讯科技（深圳）有限公司 虚拟网络群组的广播方法、装置、设备及系统
WO2021142767A1 (zh) * 2020-01-17 2021-07-22 华为技术有限公司 通信方法和通信装置
CN115280812B (zh) * 2020-03-13 2024-01-02 华为技术有限公司 设置组播地址的方法、装置和系统
CN117939406A (zh) * 2022-10-24 2024-04-26 华为技术有限公司 组播通信方法及相关装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1929638A (zh) * 2006-10-20 2007-03-14 中兴通讯股份有限公司 一种无线局域网ip组播帧传输的组播成员管理方法
CN101127717A (zh) * 2007-09-30 2008-02-20 中控科技集团有限公司 一种报文转发的方法和交换机
CN104579994A (zh) * 2015-01-21 2015-04-29 杭州华三通信技术有限公司 报文认证方法和设备
WO2016062354A1 (en) * 2014-10-24 2016-04-28 Telefonaktiebolaget L M Ericsson (Publ) Maintaining user plane session and restoring control plane session in case of control plane module failure of gateway for multicast transmissions
CN107070866A (zh) * 2016-12-30 2017-08-18 北京奇虎科技有限公司 一种流数据的传输方法和装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101702672A (zh) * 2009-11-04 2010-05-05 华为技术有限公司 组播数据报文转发方法和转发装置
CN107040898A (zh) * 2016-02-04 2017-08-11 中兴通讯股份有限公司 一种实现车联网业务的方法及本地化网络架构
WO2018098609A1 (zh) * 2016-11-29 2018-06-07 华为技术有限公司 一种通信方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1929638A (zh) * 2006-10-20 2007-03-14 中兴通讯股份有限公司 一种无线局域网ip组播帧传输的组播成员管理方法
CN101127717A (zh) * 2007-09-30 2008-02-20 中控科技集团有限公司 一种报文转发的方法和交换机
WO2016062354A1 (en) * 2014-10-24 2016-04-28 Telefonaktiebolaget L M Ericsson (Publ) Maintaining user plane session and restoring control plane session in case of control plane module failure of gateway for multicast transmissions
CN104579994A (zh) * 2015-01-21 2015-04-29 杭州华三通信技术有限公司 报文认证方法和设备
CN107070866A (zh) * 2016-12-30 2017-08-18 北京奇虎科技有限公司 一种流数据的传输方法和装置

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113973076A (zh) * 2020-07-24 2022-01-25 华为技术有限公司 一种多播切换方法及装置
CN115134761A (zh) * 2021-03-29 2022-09-30 维沃移动通信有限公司 切换方法、装置、网络侧设备及终端
CN115515088A (zh) * 2021-06-22 2022-12-23 北京新媒传信科技有限公司 一种业务流程链的编排方法、5g消息的交互方法及装置
CN115515088B (zh) * 2021-06-22 2023-10-20 北京新媒传信科技有限公司 一种业务流程链的编排方法、5g消息的交互方法及装置

Also Published As

Publication number Publication date
CN109842854A (zh) 2019-06-04
JP2021504982A (ja) 2021-02-15
CN109842854B (zh) 2021-01-05
JP6983169B2 (ja) 2021-12-17

Similar Documents

Publication Publication Date Title
WO2019104857A1 (zh) 一种报文组播、报文广播方法及设备
US11638200B2 (en) Method, apparatus, system and computer program for vehicular communication smart radio access zones
WO2022121991A1 (zh) 通信方法、装置及系统
US20230328520A1 (en) Aerial Service
US20230164729A1 (en) Uplink Data via Packet Data Network Connection
WO2018223824A1 (zh) 一种业务数据传输方法及装置
US20230328821A1 (en) Modifying PDU Sessions In Underlay Networks
US20240073848A1 (en) Network Slice in a Wireless Network
WO2021018260A1 (zh) 通信方法及相关装置
JP7395768B2 (ja) Ｖ２ｘ通信方法および装置
US20240049333A1 (en) Wireless Communications for Sidelink Ranging
US20240031929A1 (en) Connection Establishment
US20230413225A1 (en) Change of Height of Wireless Device
US20230422293A1 (en) Network Slice Based Priority Access
US20240073996A1 (en) Network Slice Management based on Inactivity
CN111436086B (zh) 安全保护方法及装置
US20230337089A1 (en) Aerial Service
US20230397155A1 (en) Height-Based Management of Wireless Device
WO2023134516A1 (zh) 一种广播通信方法和装置
US20240179647A1 (en) Timing Service Type for Timing Resiliency Service
WO2023215379A1 (en) Ranging service
CN109155785A (zh) 一种v2x消息传输方法及相关网元
WO2024026020A1 (en) Multicast broadcast service control
WO2024072952A2 (en) Tracking area of mobile base station relay
WO2024015462A1 (en) Multicast broadcast service control with respect to inactive state

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2018548178

Country of ref document: JP

Kind code of ref document: A

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

Ref document number: 18883797

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: 18883797

Country of ref document: EP

Kind code of ref document: A1