JP6983169B2 - Message multicast method, message broadcast method and device - Google Patents

Description

This application gives priority to the Chinese patent application filed with the China Patent Office on November 29, 2017, with an application number of 201411226691.7 and the title of the invention being "message multicast method, message broadcast method and device". Claimed as a right, the entire contents of which are incorporated into this application by reference.

The present application relates to the field of communication technology, in particular to message multicast, message broadcasting methods and devices.

With reference to FIG. 1, a scenario is currently provided for a communication method of communication between a car and a thing (Vehicle to X, V2X). Among them, the core network user plane function (UPF) entity sunk to the edge has multimedia broadcast and multicast service (multicast and multicast services, MBMS) functions, and is an edge gateway (local gateway). , LocalGW) can communicate with the base station. The UPF entity can also communicate with the control plane function (CPF) entity. Further, a plurality of UPF entities can communicate with a V2X server (V2X server).

Low service latency is a major core requirement brought to the network by V2X communication. In the scenario shown in FIG. 1, the V2X server needs to process messages from a plurality of UPF entities and also needs to send messages to a plurality of UPF entities. Therefore, the processing power of the V2X server tends to be a bottleneck in the performance of V2X. In light of this, another scenario is currently being submitted. That is, both the V2X server and the UPF entity sink to the edge. For example, a V2X server is placed for each UPF entity. Such a V2X server may be referred to as a local V2X server. UPF entities subsided to the edge may be referred to as edge UPF entities. Then, since one local V2X server is basically in charge of communication only with the corresponding edge UPF entity, the demand for the performance of the local V2X server is low, and the delay can be reduced.

In the scenario shown in FIG. 1, the V2X server can communicate with a plurality of edge UPF entities. However, if the V2X server is subsided to the edge to form a local V2X server, one local V2X server can only communicate with the edge UPF entity corresponding to this local V2X server, and cannot communicate with other edge UPF entities. The delay of network communication will increase.

Embodiments of the present application provide methods and devices for message multicast, message broadcast, to reduce delays.

The first aspect provides a message multicast method. This method can be performed by a CPF entity. This method involves the following steps: The CPF entity receives the multicast group join request. This multicast group join request is used by the first terminal device to request participation in the multicast group indicated by the multicast address. The CPF entity joins the first terminal device to the multicast group. The CPF entity creates a multicast forwarding route whose destination address is a multicast address. The CPF entity sends a multicast forwarding route to at least one UPF entity. At least one UPF entity includes an UPF entity in which all terminal devices included in the multicast group are located.

In embodiments of the present application, the CPF entity may, after assigning a multicast address to the group, generate a multicast forwarding route and send the multicast forwarding route to at least one UPF entity. This allows at least one UPF entity to forward the received multicast message directly to the corresponding device in the multicast group indicated by the multicast address, according to the multicast forwarding route. If the multicast group includes other devices under the UPF entity, the UPF entity can send messages to devices under the other UPF entity according to the multicast forwarding route. In this way, after the V2X server is sunk to the edge, the UPF entity will be able to transfer messages directly without the participation of the local V2X server, enabling information exchange between the UPF entities and network communication. Reduce the delay of. Since it is not necessary to deploy a local V2X server for message forwarding, the number of local V2X servers deployed can be reduced, the cost can be effectively reduced, and the complexity of the message forwarding route can be reduced.

In one possible design, the CPF entity receives a multicast group creation request. The multicast group creation request has group information. The group indicated by the group information includes at least one terminal device. Multicast group creation requests are used to request a multicast address for a group. At least one terminal device includes a first terminal device. The CPF entity assigns a multicast address to the group.

Upon receiving the multicast group creation request, the CPF entity can create a multicast group and generate a multicast address. As a result, all of at least one terminal device belongs to the multicast group, and the multicast of the multicast message in one multicast group can be realized by the UPF entity, and the communication delay can be reduced.

In one possible design, the CPF entity belongs to a base station in which the second terminal device performs inter-cell handover and the cell after the second terminal device is switched and the cell before the terminal device is switched belong to different base stations. It is determined that the terminal device of 2 belongs to the multicast group. The CPF entity updates the multicast forwarding route. The CPF entity sends the updated multicast forwarding route to at least one UPF entity and to the UPF entity located after the second terminal device switches.

When the second terminal device in the multicast group performs inter-cell handover and the cell after the handover and the cell before the handover belong to different base stations, the multicast forwarding route of the multicast group is changed. The CPF entity updates the multicast forwarding route immediately and sends the updated multicast forwarding route to the UPF entity so that the UPF entity can forward the message according to the updated multicast forwarding route and the message forwarding is successful. Improve the rate.

The second aspect provides a message broadcasting method. This method can be performed by the first UPF entity. The first UPF entity is an edge UPF entity. This method includes the following steps: the first UPF entity receives the first message and the first UPF entity says that the first message is a broadcast message according to the destination address of the first message. judge. The first UPF entity determines that the first identifier of the first message is an authenticated identifier, and the first identifier is the identifier of the terminal device that sent the first message, or It is a stream identifier of the service stream to which the first message belongs. The first UPF entity broadcasts the first message.

Embodiments of this application provide low latency broadcast capability without the participation of a V2X server. By authenticating the corresponding identifier, the UPF entity can directly implement the broadcast of the message and further reduce the forwarding delay. Further, since the V2X server does not need to participate in the broadcast, the number of V2X servers arranged can be reduced, and the cost can be effectively reduced.

In one possible design, the first UPF entity receives a notification message from the CPF entity. The notification message is used to indicate that the first identifier is an authenticated identifier. The first UPF entity determines that the first identifier is the authenticated identifier according to the notification message. The first UPF entity directly broadcasts a broadcast message with an authenticated identifier.

Correspondingly, in the third aspect, a message broadcasting method is provided. This method can be performed by a CPF entity. This method involves the following steps: The CPF entity receives the broadcast permission request. The broadcast privilege request is used to directly broadcast a broadcast message with the first identifier through the first UPF entity. The first identifier is the identifier of the terminal device that sent the broadcast message, or the stream identifier of the service stream to which the broadcast message belongs. The CPF entity sends a notification message to the first UPF entity. The notification message is used to indicate that the first identifier is an authenticated identifier. The first UPF entity directly broadcasts a broadcast message with an authenticated identifier.

The CPF entity can authenticate the corresponding identifier and notify the UPF entity. Therefore, the UPF entity can determine which identifier is the authenticated identifier after receiving the notification message sent by the CPF entity. Since the UPF entity can directly broadcast a broadcast message with an authenticated identifier, it is not necessary to broadcast via the V2X server, the route of message broadcasting is shortened, and the communication delay is reduced.

In one possible design, the first UPF entity receives the first message. Includes the following steps: The first UPF entity receives the first message from the terminal device serviced by the first UPF entity, or the first UPF entity receives the first message from the second UPF entity. ..

The first message may be transmitted by the terminal device to the first UPF entity or may be transmitted by the second UPF entity to the first UPF entity. For example, it is transmitted to the second UPF entity by the terminal device under the second UPF entity, and then transmitted to the first UPF entity by the second UPF entity. As a result, the broadcast message of the terminal device under another UPF entity can be broadcast under the UPF entity. Communication between UPF entities does not need to be realized via a V2X server or a core network, and communication can be performed directly, thus reducing communication delay.

In one possible design, the first UPF entity determines that the temporary mobile group ID requested by the first UPF entity further includes the identifier of the second UPF entity. The first UPF entity sends a multicast request message to the second UPF entity to request to join the same multicast group as the second UPF entity.

One of the UPF entities can send a broadcast message to another UPF entity to broadcast because the UPF entities in the multicast group can communicate with each other. The communication delay is reduced and the broadcast range is widened.

A fourth aspect provides a CPF entity. The CPF entity has a function of realizing the CPF entity in the method design described above. These functions can be realized by hardware, and can be realized by executing software corresponding to the hardware. The hardware or software includes one or more units corresponding to this function.

In one possible design, the concrete structure of the CPF entity may include a transceiver module and a processing module. The processing module and the transceiver module can perform the relevant functions in the method according to any one of the first aspect or the first aspect described above.

A fifth aspect provides an UPF entity. The UPF entity has a function to realize the UPF entity in the above-mentioned method and design. These functions can be realized by hardware, and can be realized by executing software corresponding to the hardware. The hardware or software includes one or more units corresponding to this function.

In one possible design, the concrete structure of the CPF entity may include a transceiver module and a processing module. The processing module and the transceiver module can perform the relevant functions in the method according to any one of the second aspect or the second aspect described above.

A sixth aspect provides a CPF entity. The CPF entity has a function of realizing the CPF entity in the method and design described above. These functions can be realized by hardware, and can be realized by executing software corresponding to the hardware. The hardware or software includes one or more units corresponding to this function.

In one possible design, the concrete structure of the CPF entity may include a transceiver module and a processing module. The processing module and the transceiver module can perform the relevant functions in the method according to any one of the third aspect or the third aspect described above.

A seventh aspect provides a CPF entity. The CPF entity has a function of realizing the CPF entity in the method and design described above. These functions can be realized by hardware, and can be realized by executing software corresponding to the hardware. The hardware or software includes one or more units corresponding to this function.

In one possible design, the concrete structure of the CPF entity may include a transceiver module and a processing module. The processing module and the transceiver module can perform the relevant functions in the method according to any one of the first aspect or the first aspect described above.

In the eighth aspect, the UPF entity is provided. The UPF entity has a function to realize the UPF entity in the above-mentioned method and design. These functions can be realized by hardware, and can be realized by executing software corresponding to the hardware. The hardware or software includes one or more units corresponding to this function.

In one possible design, the concrete structure of the UPF entity may include a transceiver module and a processing module. The processing module and the transceiver module can perform the relevant functions in the method according to any one of the second aspect or the second aspect described above.

A ninth aspect provides a CPF entity. The CPF entity has a function of realizing the CPF entity in the method and design described above. These functions can be realized by hardware, and can be realized by executing software corresponding to the hardware. The hardware or software includes one or more units corresponding to this function.

In one possible design, the concrete structure of the CPF entity may include a transceiver module and a processing module. The processing module and the transceiver module can perform the relevant functions in the method according to any one of the third aspect or the third aspect described above.

A tenth aspect provides a communication device. The communication device may be a CPF entity in the method or design described above, or a chip located within the CPF entity. The communication device may include a memory for storing computer executable program code and a processor coupled to the memory. The program code stored in the memory contains instructions. When the instruction is executed by the processor, it causes the communication device to execute the method executed by the CPF entity according to any one of the first aspect or the first aspect of the possible design.

The eleventh aspect provides a communication device. The communication device may be an UPF entity in the method or design described above, or a chip located within the UPF entity. The communication device may include a memory for storing computer executable program code and a processor coupled to the memory. The program code stored in the memory contains instructions. When the instruction is executed by the processor, it causes the communication device to execute the method executed by the UPF entity according to any one of the second aspects or the second aspect of the possible design.

A twelfth aspect provides a communication device. The communication device may be a CPF entity in the method or design described above, or a chip located within the CPF entity. The communication device may include a memory for storing computer executable program code and a processor coupled to the memory. The program code stored in the memory contains instructions. When the instruction is executed by the processor, it causes the communication device to execute the method executed by the CPF entity according to any one of the third aspect or the third aspect.

A thirteenth aspect provides a communication system. The communication system may include the UPF entity described in the fifth aspect and the CPF entity described in the sixth aspect.

A fourteenth aspect provides a computer storage medium. Instructions are stored in the computer storage medium, and when executed on the computer, the instructions cause the computer to perform any one of the possible design methods of the first aspect or the first aspect.

A fifteenth aspect provides a computer storage medium. Instructions are stored in the computer storage medium, and when executed on the computer, the instructions cause the computer to perform any one of the methods according to the possible design of the second aspect or the second aspect.

A sixteenth aspect provides a computer storage medium. Instructions are stored in the computer storage medium, and when executed on the computer, the instructions cause the computer to perform any one of the methods according to the possible design of the third aspect or the third aspect.

A seventeenth aspect provides a computer program product for storing instructions. Instructions are stored in a computer program product, and when executed on the computer, the instructions cause the computer to perform any one of the possible design methods of the first aspect or the first aspect.

In the eighteenth aspect, a computer program product for storing instructions is provided. Instructions are stored in a computer program product, and when executed on the computer, the instructions cause the computer to perform any one of the methods according to the possible design of the second aspect or the second aspect.

A nineteenth aspect provides a computer program product for storing instructions. Instructions are stored in the computer program product, and when executed on the computer, the instructions cause the computer to perform the method according to any one of the third aspect or the third aspect.

In embodiments of the present application, after the V2X server has been subsided to the edge, the UPF entity will be able to transfer messages directly without the participation of the local V2X server, enabling information exchange between UPF entities. Reduce network communication delays. Since it is not necessary to deploy a local V2X server for message forwarding, the number of local V2X servers deployed can be reduced, the cost can be effectively reduced, and the complexity of the message forwarding route can be reduced.

It is a schematic diagram of the application scenario of V2X in the prior art. It is a schematic diagram of the application scenario which concerns on embodiment of this application. It is a schematic diagram of another application scenario which concerns on embodiment of this application. It is a flowchart of the message multicast method which concerns on embodiment of this application. It is a flowchart of the method of updating the multicast route which concerns on embodiment of this application. It is a flowchart of the message multicast method which concerns on embodiment of this application. It is a flowchart of the message broadcast system which concerns on embodiment of this application. It is a schematic block diagram of the CPF entity which concerns on embodiment of this application. It is a schematic block diagram of the UPF entity which concerns on embodiment of this application. It is a schematic block diagram of the CPF entity which concerns on embodiment of this application. It is a schematic block diagram of the communication device which concerns on embodiment of this application. It is a schematic block diagram of the communication device which concerns on embodiment of this application.

Hereinafter, embodiments of the present invention will be described in more detail with reference to the drawings in order to further clarify the objectives, technical solutions and advantages of the embodiments of the present invention.

The techniques described herein can be applied to various communication systems such as Long Term Evolution (LTE) systems, 5th Generation Mobile Communication Systems (5G), and other similar communication systems. ..

Hereinafter, some terms in the present specification will be described so as to be easier for those skilled in the art to understand.

(1) The terminal device includes a device that provides voice and / or data connection to the user, and may include, for example, a handheld device having a wireless connection function or a processing device connected to a wireless modem. The terminal can communicate with the core network via a radio access network (RAN) and exchange voice and / or data with the RAN. This terminal device includes a user device (user equipment, UE), a wireless terminal device, a mobile terminal device, a participant unit (subscriber unit), a participant station (subscriber station), a mobile station (mobile station), and a mobile station (mobile). , Remote station, access point, AP, remote terminal, access terminal, user terminal, user agent or user device. (User device) and the like may be included. For example, it may include a mobile phone (or a "cellular" phone), a computer equipped with a mobile terminal device, a mobile device, a message type, a handheld type, a computer-embedded or in-vehicle mobile device, a smart wearable device, and the like. For example, personal communication service (PCS) telephones, cordless telephones, SIP (cession initiation protocol, SIP) telephones, wireless local loop (WLL) stations, personal digital assistants (personal digital assistants). Devices such as smart watches, smart helmets, smart glasses, and smart bracelets may be included. It also includes devices with low power consumption, devices with limited storage capacity, and devices with limited computing power. For example, information detection devices such as barcodes, radio frequency identification (RFID), sensors, global positioning system (GPS), laser scanners and the like are included.

In the embodiment of the present invention, the terminal device may further include, for example, a V2X device which is an on-board unit (OBU). In the specification, a case where the terminal device is a V2X device will be mainly described as an example.

(2) Network devices (eg, access network devices and core network devices). An access network device can refer to, for example, a device that includes a base station (eg, an access point) and communicates with a wireless terminal over one or more sectors on an air interface in an access network. The base station can be used as a router between the terminal and the rest of the access network to interconvert received airframes with Internet Protocol (IP) messages. Other parts of the access network may include an IP network. The base station can also coordinate the attribute management of the air interface. For example, a base station is an advanced base station (eNB or e-NodeB, evolved NodeB) in an LTE system or an evolved LTE system (LTE-Advanced, LTE-A), a small base station in an LTE system or an LTE-A system. (Micro / pico eNB) may be included, or next-generation node B (next generation nodeB, gNB), transmission point (transmission point, TP), transmission / reception point (transmission and receiver point, TRP), etc. in the NR system may be included. But it may be. Embodiments of the present invention do not limit this.

The core network device may include, for example, a mobility management entity (MME), a broadcast multicast service center (BMSC), or an MBMS-GW, or may be a CPF entity or an UPF entity. May include corresponding functional entities within a new 5G radio (NR) system.

(3) V2X. Currently, vehicles are vehicle-to-vehicle (V2V), vehicle-to-road infrastructure (V2I), vehicle-to-pedestrian (V2P), or vehicle-to-pedestrian (V2P), or vehicle-to-vehicle communication (V2P). By using a method such as communication between a vehicle and a network (Vehicle to network, V2N), road condition information can be immediately acquired or information can be received. These communication methods can be collectively referred to as V2X communication. Taking the most common V2V and V2I as an example, the vehicle can broadcast information such as its speed, direction of travel, specific position, and whether or not the emergency brake is applied to surrounding vehicles through V2V communication. By acquiring such information, peripheral vehicles will be able to better detect traffic conditions outside the field of vision, predict dangerous situations early, and avoid them in a timely manner. Regarding V2I communication, in addition to the above-mentioned exchange of security information, the roadside infrastructure can provide various service information, data net access, and the like to the vehicle information. Features such as toll payments and in-car entertainment without parking will significantly improve traffic intelligence. Generally, the network used for V2X communication is called a car network.

(4) Mobile edge computing (MEC). To avoid pipelines of mobile bearer networks, telecommunications standards bodies and carriers are trying to increase the value of mobile network bandwidth, how mobile internet in future 5G networks. And we are considering whether to integrate deeply with IoT services. Proposed by the European Telecommunications Standards Institute (ETSI), MEC is a technology that deeply integrates mobile access networks and Internet services based on the 5G evolutionary architecture. MEC provides integration with third-party applications by improving the user experience, saving bandwidth resources, and sinking computing power to mobile edge nodes for service innovation in mobile edge portals. Brings unlimited possibilities.

Currently, MEC is applicable in multiple regions. For example, one set of MECs is placed in one area. A set of MECs can include one local V2X server and one UPF entity. The UPF entity is an edge UPF entity. The Edge UPF entity can communicate with the base station and may forward the message sent by the base station to the local V2X server or the message generated by the local V2X server to the base station. .. Edge UPF entities can also communicate with CPF entities. It is also an improvement based on the evolved multimedia broadcast and multicast services (eMBMS), which corresponds to subsidence and placement of MBMS functionality in edge UPF entities. Among them, the edge UPF entity may be considered to be realized via the edge gateway and at the same time the local V2X server is simultaneously deployed at the edge in order to meet the low latency requirement.

(5) The terms in the embodiments of the present invention: "system" and "network" can be used interchangeably. "Multiple" means two or more. “And / or” means the relationship of the related object, and there can be three relationships. For example, A and / or B may have three cases: A exists alone, A and B exist at the same time, and B exists alone. Further, the sign "/" generally indicates that the context object is related to "or" unless otherwise specified.

In order to better understand the technical solutions according to the embodiments of the present invention, one application scenario of the embodiments of the present application will be described with reference to FIG. FIG. 2 includes two sets of MECs, MEC1 and MEC2. Below MEC1, a first UPF entity, a first local V2X server, and a first base station are located. 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 located under MEC2. The second base station can communicate with the third terminal device and the fourth terminal device. The first UPF entity and the second UPF entity are both edge UPF entities. 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. The central UPF entity can be understood as an UPF entity that does not sink to the edge. Both the first local V2X server and the second local V2X server in FIG. 1 are shown by dotted lines. This means that in embodiments of the present application, the local V2X server may or may not be located. Since the solution according to the embodiment of the present application does not need to actually use the local V2X server, it is not necessary to arrange the local V2X server in order to reduce the cost. However, it may still be deployed, considering that the local V2X server can provide other functionality. When arranging a local V2X server, if it is not necessary to arrange a local V2X server under each set of MECs according to specific needs, the cost can be reduced to some extent. In the following, for the sake of simplicity, the local V2X server is simply referred to as a server.

FIG. 3 is another application scenario according to an embodiment of the present application. Compared to FIG. 2, a remote control center (remote controller center) has been added to FIG. The remote control center can be used to control the terminal devices under each MEC. For example, if the terminal device is a smart vehicle, the remote control center can control these smart vehicles in a unified manner. In the prior art, the remote control center communicates with the V2X server, but in embodiments of the present application, the remote control center may communicate with the local V2X server or with the UPF entity.

The UPF entities described below (eg, the first UPF entity or the second UPF entity shown in FIG. 2 or 3) all refer to edge UPF entities unless otherwise noted. These UPF entities have MBMS capabilities.

With reference to FIG. 4, embodiments of the present application provide a message multicast method. In the following description, this method will be described by exemplifying the application scenario shown in FIG. 2 or the application scenario shown in FIG. The flow of this method will be described as follows.

S401: The first terminal device attaches to the network. The process related to attachment can refer to the standard attach process.

Here, the first terminal device is taken as an example, but in reality, it can be applied to any terminal device under any edge UPF entity.

S402: After the first terminal device is attached to the network, the first terminal device requests the grouping management server to join the corresponding group. As a matter of course, the first terminal device first registers with the grouping management server and then requests to join the corresponding group. Of these, the first terminal device may request registration from the grouping management server immediately after being attached to the network, or may wish to join the corresponding group after being attached to the network. You may request registration from the grouping management server.

Specifically, the first terminal device is a grouping management service program (platooning) installed on the grouping management server via a V2X application (APP) program installed on the first terminal device so as to join the group. It can be requested to the manager). The grouping management server can communicate with a plurality of terminal devices. For example, the registration request sent by the first terminal device to the grouping management server has a group identifier. After receiving this registration request, the grouping management server acquires the identifier of the group, and determines that the group to which the first terminal device wants to join is the group indicated by this identifier.

Of these, the grouping management service program is used to manage groups. For example, the terminal device is specifically an OBU in a vehicle, and a plurality of OBUs are organized as one group. That is, one group may include at least one terminal device. This will contribute to the unified procurement and management of OBU. For example, in the case of a vehicle group containing 10 vehicles, 10 vehicles (ie, the OBU in the vehicle) may be required to join the same group. For example, the OBUs in those 10 vehicles can be pre-negotiated to determine the identifier of the group to join. Obviously, if those 10 vehicles join the same group, the OBU in the 10 vehicles can negotiate to obtain the identifier of one group. The 10 OBUs request the grouping management service program to join the group indicated by the identifier of this group.

The first terminal device can immediately request the grouping management service program to join the corresponding group immediately after registering in the grouping management service program. Alternatively, when the first terminal device is registered in the grouping management service program and then operates normally and it is necessary to join the corresponding group, the group corresponding to the grouping management service program is used. You may request to join.

S403: The grouping management service program joins the first terminal device to the group and sends a multicast group creation request to the CPF entity. The CPF entity receives a multicast group creation request from the grouping management service program. In FIG. 4, S403 includes two parts. In one part, the grouping management server joins the first terminal device to the group, and in the other part, the grouping management server sends a multicast group creation request to the CPF entity.

This multicast group creation request has information about this group. This group information includes, for example, the identification information of this group. This multicast group creation request is used to apply for a multicast address for this group. Optionally, this multicast group creation request may also be used to apply for multicast privileges for this group.

Applying for multicast permissions and multicast addresses for a group is equivalent to configuring this group as a multicast group. As a result, the terminal devices included in this group can exchange information by multicast. If the grouping management service program has previously applied for multicast authority and multicast address for the group to which the first terminal device is going to join, the grouping management service program of S402 will multicast this group to the CPF entity. Eliminates the need to apply for permissions and multicast addresses.

S404: The CPF entity assigns a multicast address to the multicast group. That is, it is a message forwarding route when this multicast address is used as the destination address.

The CPF entity can allow the groups indicated by this group information to form one multicast group. This multicast group includes all terminals included in this group. Then, the CPF entity may assign the multicast address to the multicast group and specify the multicast authority to the multicast group.

S405: The CPF entity sends the assigned multicast address to the grouping management service program, and the grouping management service program receives the multicast address.

S406: The grouping management service program transmits the group joining result and the multicast address to the first terminal device, and the first terminal device receives the group joining result and the multicast address.

The grouping management service program sends the multicast address assigned by the CPF entity to the first terminal device. Therefore, the CPF entity may be understood to send the multicast address to the first terminal device. Alternatively, the CPF entity may be understood to send the multicast address to the first terminal device via the grouping management service program.

The group subscription result indicates that the first terminal device has been joined to the group to which the first terminal device wants to join, or the first terminal device is refused to join the group to which the first terminal device wants to join. Is shown. As a matter of course, if the group joining result indicates that the first terminal device refuses to join the group to which the first terminal device wants to join, the grouping management service program does not send the multicast address to the first terminal device. Therefore, S406 is an example in which the group joining result indicates that the first terminal device has joined the group to which the first terminal device wants to join. Then, the first terminal device can transmit the multicast message in the multicast group, and can also receive the multicast message transmitted from other devices in the multicast group.

The process in which another terminal device in the group joins the group and acquires the multicast address can refer to the execution process of S401 to S406. I will not repeat this.

S407: The remote control center requests the grouping management service program to join this group.

In the application scenario shown in FIG. 3, a remote control center will be described. The remote control center may be used to control multiple terminal devices in the system. The plurality of terminal devices may belong to the same UPF entity or may belong to different UPF entities. A plurality of terminal devices can form a plurality of multicast groups. In that case, the remote control center can join each multicast group within it. For a multicast group, the remote control center is one member device within this multicast group, and its status is the same as the status of other terminal devices within this multicast group. However, for a plurality of terminal devices, the remote control center can control the operation of the terminal device as a control device. For example, if the terminal device is specifically an OBU in a vehicle, the remote control center can control the operation of the vehicle. For example, depending on at least one of the factors such as road conditions, weather conditions, vehicle speed of each vehicle, distance between vehicles, and of course, the other factors also control the running of the vehicle and the possibility of an accident. Can be reduced and the vehicle can be driven regularly.

For example, in the case of a vehicle group containing 10 vehicles, 10 vehicles (ie, the OBU in the vehicle) may be required to join the same group. For example, the OBUs in those 10 vehicles can be pre-negotiated to determine the identifier of the group to join. Obviously, if those 10 vehicles join the same group, the OBU in the 10 vehicles can negotiate to obtain the identifier of one group. The 10 OBUs request the grouping management service program to join the group indicated by the identifier of this group. Since the remote control center can communicate with each terminal device, the group information of this group can be acquired. This also allows the remote control center to request the grouping management service program to join the group indicated by the group information, i.e., join the same group with those 10 vehicles and be the same. Join the multicast group of.

S408: The grouping 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.

In the embodiment of the present application, the grouping management service program acquires the multicast address of the multicast group to which the group indicated by the group information belongs by executing S402 to S405. Therefore, the grouping management service program does not need to request the multicast address from the CPF entity again, and may directly send the multicast address assigned by the CPF entity in S404 to the remote control center. If the grouping management service program has not yet obtained the multicast address of the multicast group corresponding to the group requested to join by the remote control center, it continues to multicast to the CPF entity according to the steps described in steps S402 to S405. You may request an address.

Of these, the two parts S402 to S406 and S407 to S408 may be executed in any order. For example, S402 to S406 are executed before S407 to S408, S402 to S406 are executed after S407 to S408, or S402 to S406 and S407 to S408 are executed at the same time. The embodiments of the present application do not limit this. Here, the execution of S402 to S406 before S407 to S408 means that S402 precedes S407 and the order between S403 to S406 and S408 may be arbitrary. For example, S408 may be executed before S403, after S403 and before S404, or after S404 and before S405, or S405. It may be executed after and before S407, or it may be executed after S407. The same applies to the case where S402 to S406 are executed after S407 to S408 and the case where S402 to S406 are executed at the same time as S407 to S408.

S409: The first terminal device can send a multicast group join request to the CPF entity after acquiring the multicast address. The CPF entity receives a multicast group join request from the first terminal device. The multicast group join request is used for the first terminal device to request to join the multicast group indicated by the multicast address.

Here, after the execution of S408 is completed, S409 can be executed.

Specifically, the first terminal device can send a multicast group join request to the UPF entity in which the first terminal device is located. For example, the first UPF entity shown in FIG. 2 or FIG. 3 receives a multicast group join request. The first UPF entity then forwards the multicast group join request to the CPF entity, which in turn receives the multicast group join request.

S410: The CPF entity joins the first terminal device to the multicast group.

S411: The CPF entity generates a multicast forwarding route whose destination address is a multicast address.

A multicast message whose destination address is a multicast address can be forwarded according to the multicast forwarding route.

When the first terminal device is the first terminal device that has joined the multicast group, the CPF entity generates a multicast forwarding route whose destination address is a multicast address. For example, the multicast address is 224. X. X. X. FIG. 4 shows an example in which a CPF entity generates a multicast forwarding route. If the first terminal device is not the first terminal device that has joined the multicast group, for example, if there is another terminal device that has requested to join the multicast group earlier, the CPF entity has a destination address of the multicast address. There is a possibility that the generation of the multicast forwarding rule is completed. In that case, in S411, the CPF entity updates the multicast forwarding route. That is, the CPF entity can generate a multicast forwarding route when joining the first terminal device to the multicast group. If another terminal device then requests to join the multicast group, the CPF entity may update the previously generated multicast forwarding route. There is no need to regenerate the multicast forwarding route.

Similarly, the remote control center can apply to join a multicast group. For the remote control center applying to join the multicast group and the processing process of the CPF entity, the description of S409 to S411 can be referred to. The processing process by the remote control center is the same as the processing process by the first terminal device.

S412: The CPF entity sends the generated multicast forwarding route to at least one UPF entity, and the at least one UPF entity receives the multicast forwarding route from the CPF entity. Here, at least one UPF entity is an UPF entity in which all terminal devices included in the multicast group are located. Although only the first UPF entity is shown in FIG. 4, the process by which the other UPF entities receive the multicast forwarding route is similar.

In embodiments of the present application, the multicast forwarding route comprises a mapping relationship between the multicast address and all terminal devices included in the multicast group. Here, the mapping relationship between the multicast address and the terminal device is the mapping relationship between the UPF entity in which each terminal device is located in the multicast group and the base station in which each terminal device is located, and each terminal. It may include a mapping relationship between the base station where the device is located and each terminal device. Simply put, for example, for one terminal device in a multicast group, 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.

For example, if the UPF entity in which the first terminal device is located is the first UPF entity, the first UPF entity receives a multicast message transmitted by another device in the multicast group, the multicast forwarding route. Therefore, the multicast message can be sent directly to the base station where the first terminal device is located. Subsequently, the base station where the first terminal device is located can further transmit the multicast message to the first terminal device. Also, if a second UPF entity that is different from the first UPF entity receives a multicast message sent by another device in the multicast group, the second UPF entity will first send the multicast message according to the multicast forwarding route. Can be sent to the UPF entity of. After receiving the multicast message, the first UPF entity sends a multicast message to the base station where the first terminal device is located, and the base station where the first terminal device is located is multicast to the first terminal device. Send a message. That is, information exchange can be directly performed between UPF entities by the technical solution according to the embodiment of the present application. As a result, information exchange between UPF entities can be realized. Furthermore, when multicasting messages, the participation of the local V2X server is not required. This can reduce the number of local V2X server deployments, reduce costs, and make message forwarding routes easier.

When exchanging information between UPF entities, it is first necessary to establish a communication connection between UPF entities. In an embodiment of the present application, if the CPF entity determines that the UPF entity to which the terminal device included in one multicast group belongs is at least two UPF entities, the CPF entity is each 2 in at least two UPF entities. A communication connection establishment request can be sent to at least one of at least two UPF entities in order to request that a communication connection be established between one entity. In this way, information can be transmitted to each other to realize multicast between UPF entities in which terminal devices included in one multicast group are located.

In embodiments of the present application, one UPF entity can store multiple multicast forwarding routes. The plurality of multicast forwarding routes may include routes of all multicast groups subscribed to by all terminals serviced by the UPF entity. The route of one multicast group includes all the terminal devices included in the multicast group, the base station where each terminal device is located, and the UPF entity where each base station is located. For example, a terminal device serviced by a first UPF entity includes a first terminal device and a third terminal device. The first terminal device is subscribed to the multicast group 1 and the multicast group 2, and the third terminal device is subscribed to the multicast group 3. The multicast forwarding route stored by the first UPF entity includes the route of multicast group 1, the route of multicast group 2, and the route of multicast group 3. For example, the multicast group 1 includes a first terminal device and a second terminal device. The UPF entity to which the first terminal device belongs is the first UPF entity. 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. The base station to which the second terminal device belongs is the second base station under the second UPF entity. In that case, the multicast forwarding route stored by the first UPF entity includes the following mapping relationships:

The same applies to the multicast group 2 and the multicast group 3. I will not repeat this. As a matter of course, the above-mentioned contents only indicate the information contained in the multicast forwarding route, and do not represent the actual storage mode of the multicast forwarding route.

In short, the UPF entity can directly send the received multicast message according to the stored multicast forwarding route.

The above is the process of how to generate a multicast forwarding route. After the multicast forwarding route is generated, if the terminal device in this multicast group is changed, for example, when a new terminal device joins, the terminal device leaves, or the route of the terminal device is changed. , May be involved in the process of updating multicast forwarding routes. This will be described below.

With reference to FIG. 5, embodiments of the present application provide a method of updating a multicast forwarding route. In the following description, this method will be described by exemplifying the application scenario shown in FIG. 2 or the application scenario shown in FIG. This method can be performed after execution of the embodiment shown in FIG.

S501: The CPF entity determines that the second terminal device has performed the inter-cell handover, and the base station in which the cell is located after the second terminal device is switched is before the second terminal device is switched. It is determined that the base station is different from the base station in which the cell is located. Among them, the second terminal device is a terminal device included in the multicast group according to the embodiment shown in FIG.

When the terminal device performs inter-cell handover, the handover process is involved in the CPF entity, so that the CPF entity can detect the handover process of the terminal device. For this content, the cell-to-cell handover process in the protocol can be referred to and is not repeated.

S502: The CPF entity updates the multicast forwarding route whose destination address is a multicast address. That is, the CPF entity updates the multicast forwarding route generated in the embodiment shown in FIG.

If the base station where the cell after the second terminal device is switched is the same base station as the base station where the cell before the second terminal device is switched is located, the multicast forwarding route should be changed. There is no. On the other hand, if the base station where the cell after the second terminal device is switched is located is different from the base station where the cell before the second terminal device is switched is located, the multicast forwarding route is changed. I have something to do. If the base station in which the cell after the second terminal device is switched is the same base station as the base station in which the cell before the second terminal device is switched is located, a plurality of situations are included. Involved in the routing change method of. This will be described below.

Situation 1: The base station in which the cell after the second terminal device is switched and the base station in which the cell before the second terminal device is switched belong to the same UPF entity.

In this case, the mapping relationship between the UPF entity and the base station in the multicast forwarding route may be changed. For example, in a multicast forwarding route, the original mapping relationship is the first UPF entity-the first base station-the second terminal device. After switching, the second terminal device is switched to the second base station under the first UPF entity, and the CPF entity has a mapping relationship in the multicast forwarding route between the first UPF entity and the second base station. -Can be updated to a second terminal device.

Situation 2: The base station in which the cell after the second terminal device is switched and the base station in which the cell before the second terminal device is switched belong to different UPF entities.

In this case, it is necessary to change the direct destination device in the multicast forwarding route. For example, in a multicast forwarding route, the original mapping relationship is the first UPF entity-the first base station-the second terminal device. That is, the original UPF entity that provided the service to the second terminal device was the first UPF entity. After switching, the second terminal device is switched to the second base station under the second UPF entity, and the CPF entity has a mapping relationship in the multicast forwarding route between the second UPF entity and the second base station. -Can be updated to a second terminal device. That is, the direct destination device is changed from the first UPF entity to the second UPF entity.

S503: The CPF entity sends the updated multicast forwarding route to at least one UPF entity and to the UPF entity where the base station is located after the second terminal has switched. Here, at least one UPF entity is an UPF entity in which all terminal devices included in the multicast group are located. FIG. 5 shows an example in which the CPF entity sends an updated multicast forwarding route to the first UPF entity.

The UPF entity in which the base station is located after the second terminal device is switched and the UPF entity in which the base station before the second terminal device is switched may be the same UPF entity. It may be a different UPF entity. When the UPF entity in which the base station is located after the second terminal device is switched and the UPF entity in which the base station before the second terminal device is switched are different UPF entities, the second terminal device is used. The UPF entity after the switch may be one of at least one UPF entity, or may be an UPF entity that did not previously belong to the multicast group. The embodiments of the present application do not limit this. Here, the UPF entity that does not belong to the multicast group means that the UPF entity in which the terminal device included in the multicast group is located is not the UPF entity.

Further, the UPF entity in which the base station is located after the second terminal device is switched and the UPF entity in which the base station before the second terminal device is switched are different UPF entities, and the second terminal device is switched. If the UPF entity after the terminal device is switched is an UPF entity that did not belong to the multicast group before, the communication between the UPF entity after the second terminal device is switched and the UPF entity belonging to the multicast group is , May not be established yet. Therefore, in this case, the core network device can send a communication connection establishment request to at least one UPF entity among the UPF entity and the UPF entity belonging to the multicast group after the second terminal device is switched. As a result, a communication connection is established between the UPF entity after the second terminal device is switched and each UPF entity in the UPF entity belonging to the multicast group.

In the embodiment shown in FIG. 5, the CPF entity updates the multicast forwarding route because there is a terminal device that performs inter-cell handover in the multicast group. In other scenarios, for example, if a new terminal device joins a multicast group or a terminal device in a multicast group leaves the multicast group, the CPF entity updates the multicast forwarding route and accommodates the updated multicast forwarding route. Need to be sent to the UPF entity. Here, when a new terminal device joins the multicast group, the CPF entity updates the multicast forwarding route and then 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 also transmitted to the UPF entity where the newly subscribed terminal device is located. Of course, the UPF entity where the newly joined device is located may be one of the UPF entities where all the terminal devices included in the multicast group are located, and all the terminal devices originally included in the multicast group are located. It may no longer belong to the UPF entity that is located. All terminals included in the multicast group described here do not include newly subscribed terminals for the time being. If there is a terminal device that has left the multicast group, the CPF entity updates the multicast forwarding route and then sends the updated multicast forwarding route to the UPF entity where all the terminals included in the multicast group are located. All terminals included in the multicast group described here include exited terminals. For other corresponding processes, the description of the embodiment shown in FIG. 5 can be referred to and is not repeated.

In the above-described embodiment, mainly, how the UPF entity acquires the multicast forwarding route and how to update the multicast forwarding route are also described. Hereinafter, how the UPF entity forwards the multicast message according to the multicast forwarding route will be described.

With reference to FIG. 6, embodiments of the present application provide a message multicast method. In the following description, this method is an example used for the application scenario shown in FIG. 2 or the application scenario shown in FIG. In this method, the UPF entity can realize the forwarding of multicast messages according to the multicast forwarding route generated in the embodiment shown in FIG. 4 or according to the updated multicast forwarding route in the embodiment shown in FIG.

S601: The first terminal device generates a multicast message, and this multicast message has a multicast address.

In the embodiment shown in FIG. 4, the first terminal device can acquire the multicast address assigned by the CPF entity in S405. As a result, the first terminal device can directly have a multicast address when trying to send a multicast message. The first terminal device can join a plurality of multicast groups, and the multicast message may be transmitted to one in the plurality of multicast groups.

S602: The first terminal device sends a multicast message to the first UPF entity, and the first UPF entity receives the multicast message.

Among them, the first UPF entity is the UPF entity in which the base station in which the first terminal device is located is located. Specifically, in the step of the first terminal device transmitting the multicast message to the first UPF entity, the first terminal device transmits the multicast message to the first base station in which the first terminal device is located. Therefore, the first base station may send a multicast message to the first UPF.

After receiving the message, the first UPF entity can know the type of the message according to the destination address of the message. For example, a broadcast message, a multicast message, or a unicast message.

For example, the first terminal device belongs to the first base station. The first base station is not shown in FIG. Therefore, the arrow from the first terminal device to the first UPF entity in S601 of FIG. 6 actually indicates the first base after the first terminal device sends a multicast message to the first base station. It means that the station sends a multicast message to the first UPF entity.

In embodiments of the present application, all communications between a terminal device and an UPF entity show that the terminal device communicates with the UPF entity via a base station, unless otherwise specified.

S603: The first UPF entity queries the stored multicast forwarding route and forwards the multicast message to the device indicated by the multicast forwarding route.

For example, in a multicast forwarding route, the multicast group corresponding to the multicast address has three destination addresses: a second terminal device under the first UPF entity, a remote control center, and a third terminal under the second UPF entity. Indicates that it contains. As for the multicast forwarding route, the route to the second terminal device is the terminal device of the first UPF entity-the first base station-2, and the route to the remote control center is the current UPF entity-remote control. It is a center and indicates that the route to the third terminal device is the first UPF entity-the second UPF entity-the second base station-the third terminal device. In that case, the process in which the first UPF entity performs forwarding in response to the instruction of the multicast forwarding route is as follows.

S6031: The first UPF entity encapsulates the multicast message in the tunnel where the second terminal device is located. That is, the multicast message is transmitted to the first base station. The first base station receives the multicast message and then transmits the multicast message to the second terminal device. Since the first base station is not shown in FIG. 6, the arrow from the first UPF entity to the second terminal device in S6031 of FIG. 6 actually indicates that the first UPF entity sends a multicast message. It means that after transmitting to one base station, the first base station transmits a multicast message to the second terminal device.

S6032: The current UPF entity is the first UPF entity, the first UPF entity converts the multicast message into a unicast message, sends it to the remote control center in an uplink manner, and the remote control center receives the multicast message. do.

S6033: The first UPF entity encapsulates the multicast message in a tunnel between the first UPF entity and the second UPF entity, sends the multicast message to the second UPF entity, and the second UPF entity Receive multicast messages.

As shown by the broken line in FIG. 6, the second UPF entity also stores the multicast forwarding route, and after receiving the multicast message, sends the multicast message to the second base station according to the multicast forwarding route. Can be done. As a result, the second base station can transmit the multicast message to the third terminal device. However, the second base station is not shown in FIG.

Here, the execution order of the three steps S6031 to S6033 may be arbitrary, and the step numbers do not limit the execution order.

In embodiments of the present application, UPF entities can directly forward multicast messages without going through a local V2X server. Reduce the complexity of the message forwarding route, reduce the number of local V2X servers deployed, and reduce costs. All of the above is the process of message multicasting. In embodiments of the invention, message broadcasting may also be implemented directly by the UPF entity. As a result, information exchange can be realized between UPF entities. Hereinafter, the message broadcasting method according to the embodiment of the present application will be described using other embodiments. In the following description, this method will be described as an example of applying this method to the application scenario shown in FIG. 2 or the application scenario shown in FIG. The flow of this method will be described below with reference to FIG. 7.

S701: The terminal device requests a broadcast address and broadcast authority from the local V2X server.

For example, the terminal device may send a message requesting a broadcast address and broadcast authority to the base station where the terminal device is located. The base station where the terminal device is located receives the message and transfers the message to the UPF entity where the base station is located. The UPF entity where the base station is located receives the message and forwards the message to the local V2X server. The local V2X server receives the message.

S702: The local V2X server sends a broadcast privilege request to the CPF entity. The broadcast privilege request is used to directly broadcast a broadcast message with the first identifier through the first UPF entity. The CPF entity receives the broadcast permission request. As will be understood, the broadcast privilege request is used by the first UPF entity to translate the broadcast message with the first identifier from uplink unicast to downlink broadcast.

Here, the local V2X server can directly assign a broadcast address to the terminal device in response to a request from the terminal device. The local V2X server can include the broadcast address in the broadcast permission request and send it to the core network device.

Alternatively, S701 and S702 are examples in which a local V2X server is located in the system. If the local V2X server is not deployed in the system, or if the local V2X server is not deployed in the MEC where the terminal device is located, the terminal device may request the broadcast address and broadcast authority directly from the CPF entity. .. As will be appreciated, the terminal device sends a broadcast privilege request to the CPF entity. In this case, the broadcast address can be assigned by the CPF entity.

Here, the first UPF entity is the UPF entity in which the terminal device is located, the first identifier is the identifier of the terminal device that transmits the broadcast message, or the first identifier is the identifier to which the broadcast message belongs. The stream identifier of the service stream to be used.

The CPF entity can query whether the first identifier is an authenticated identifier. If the first identifier is an authenticated identifier, S703 can be executed. If the first identifier is not authenticated, the CPF entity can authenticate the first identifier and execute S703. After authentication, the first UPF entity can directly broadcast the broadcast message with the first identifier.

S703: The CPF entity sends a notification message to the first UPF entity, and the first UPF entity receives the notification message. The notification message is used to indicate that the first identifier is an already authenticated identifier.

Here, the first UPF entity can directly broadcast a broadcast message with an authenticated identifier. That is, for a broadcast message with an authenticated identifier, the first UPF entity can encapsulate such a broadcast message into a downlink MBMS session and forward it according to the matched flow rules. There is no need to send a broadcast message with the authenticated identifier to the local V2X server.

S704: The CPF entity responds to the request of the local V2X server after completing the transfer authentication and policy update to the first UPF entity. Specifically, the CPF entity sends a broadcast privilege response to the local V2X server, which receives the broadcast privilege response. The broadcast authority response is a response to a broadcast authority request sent by the local V2X server.

S705: The local V2X server sends a broadcast capability request response to the terminal device, and the terminal device receives the broadcast capability request response.

Here, the broadcast capability request response can have authorization information and an authenticated broadcast address. The authenticated broadcast address is the broadcast address generated by the local V2X server or CPF entity as described above. Privilege information may be used to indicate that the first UPF entity is allowed to broadcast a broadcast message with the first identifier directly, or the first UPF entity has the first identifier. It may be used to indicate that a broadcast message is not allowed to be broadcast directly. Of course, the local V2X server does not send the broadcast address to the terminal device for authorization information to indicate that the first UPF entity is not allowed to broadcast the broadcast message with the first identifier directly. Therefore, S705 is an example of rights information to indicate that the first UPF entity is allowed to directly broadcast the broadcast message having the first identifier.

Note that S704 and S705 are also examples in which a local V2X server is arranged in the system. If the local V2X server is not deployed in the system, or if the local V2X server is not deployed in the MEC where the terminal device is located, the core network has completed forwarding authentication and policy updates for the first UPF entity. After that, it is possible to directly respond to the broadcast authority request of the terminal device. For example, a CPF entity can send authorization information and an authenticated broadcast address to a terminal device. The terminal device receives the authorization information and the authenticated broadcast address.

S706: The terminal device generates the first message. The first message has a broadcast address. The first message is a broadcast message. The broadcast address of the first message is an authenticated broadcast address, as described in the previous step. The first message also has a first identifier.

Generates an uplink message when the terminal device attempts to broadcast. Uplink messages are encapsulated according to the broadcast format. The broadcast address is an authenticated broadcast address.

S707: The terminal device sends the first message to the first UPF entity, and the first UPF entity receives the first message.

The first message can be forwarded to the first UPF entity via the uplink unicast tunnel. As a matter of course, the terminal device sends the first message to the base station where the terminal device is located, and then the base station where the terminal device is located sends the first message to the first UPF entity. Do not repeat this process.

Alternatively, the first message may be sent by another UPF entity to the first UPF entity. For example, the terminal device under the second UPF entity produces the first message. The terminal device sends the first message to the second UPF entity, and the second UPF entity sends the first message to the first UPF entity.

S708: The first UPF entity determines that the first message is a broadcast message according to the destination address of the first message, and determines that the first identifier of the first message is an authenticated identifier. judge.

After receiving the first message, the first UPF entity may parse the first message and determine what type of message the first message is according to the destination address of the first message. can. For example, a broadcast message, a multicast message, or a unicast message.

In the case of a broadcast message, the first UPF entity can determine whether the identifier of the broadcast message is an authenticated identifier. For example, a broadcast message has a first identifier. As described in the previous step, the first identifier is an authenticated identifier.

S709: The first UPF entity broadcasts the first message.

Since the first identifier is the authenticated identifier, the first UPF entity can be broadcast directly by the first UPF entity without the need for the first message to be sent to the local V2X server. judge. The first UPF entity then queries the stored broadcast route to broadcast the first message.

Further, before executing S701, the local V2X server first requests the CPF entity for a temporary mobile group ID entity (TMGI). For this content, refer to the introduction in the prior art. If the TMGI requested by the local V2X server covers the forwarding control area of multiple UPF entities, the UPF entity at the edge should join the multicast group to become a downstream node forwarded by the other UPF entity. It is necessary to request each of the other UPF entities. In short, in any two UPF entities of the plurality of UPF entities covered by TMGI, the two UPF entities are realized to be downstream nodes transferred by the other party to each other.

Therefore, when the first UPF entity is broadcasting, if there is another UPF entity in the downstream transferred by the first UPF entity, that is, the first UPF entity and the other UPF entity are the same. If they belong to a multicast group, the first message may also be multicast to those UPF entities. These UPF entities receive the first message and then continue to broadcast the first message.

In embodiments of the present application, a low-latency multicast or broadcast forwarding function without the involvement of a V2X server can be provided to further reduce the forwarding delay. Since the V2X server does not need to be involved in multicast or broadcast, the number of V2X servers deployed can be reduced and the cost can be effectively reduced. Furthermore, after the V2X server is sunk to the edge, it can effectively meet the service needs by supporting the forwarding of multicast and broadcast messages between MECs.

Hereinafter, the apparatus according to the embodiment of the present application will be described with reference to the accompanying drawings.

FIG. 8 shows a schematic structural diagram of the CPF entity 800. The CPF entity 800 can realize the functions of the CPF entity described above. The CPF entity 800 may be the above-mentioned CPF entity or a chip arranged in the above-mentioned CPF entity. The CPF entity 800 can include a processor 801 and a transceiver 802. Here, the processor 801 may be used to perform S404, S410 and S411 in the embodiment shown in FIG. 4, and S503 in the embodiment shown in FIG. 5, and / or the techniques described herein. It may be used to support other processes. Transceiver 802 may 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 described herein. It may be used to support other processes of the technology.

For example, transceiver 802 is configured to receive a multicast group join request. The multicast group join request is used to request the first terminal device to join the multicast group indicated by the multicast address.

The processor 801 is configured to join the terminal device to a multicast group and generate a multicast forwarding route whose destination address is a multicast address.

Transceiver 802 is further configured to send a multicast forwarding route to at least one UPF entity. At least one UPF entity includes an UPF entity in which all terminal devices included in the multicast group are located.

Here, all the relevant contents in each step according to the method embodiment described above can be incorporated into the functional description of the corresponding functional module. I will not repeat this.

FIG. 9 shows a schematic configuration diagram of the UPF entity 900. The UPF entity 900 can realize the function of the first UPF entity described above. The UPF entity 900 may be the first UPF entity described above, or may be a chip arranged in the first UPF entity described above. The UPF entity 900 can include a processor 901 and a transceiver 902. Among them, processor 901 may be used to perform S708 in the embodiment shown in FIG. 7 and / or may be used to support other processes of the techniques described herein. Transceiver 902 may be used to perform S703, S707 and S709 in the embodiments shown in FIG. 7 and / or may be used to support other processes of the techniques described herein. good. The transceiver 902 can be used as an integrated module capable of exchanging information with a terminal device or other UPF entity. Alternatively, the transceiver 902 includes a plurality of transceiver interfaces. In the transceiver interface, a part is used for exchanging information with a terminal device, and another part is used for exchanging information with another UPF entity.

For example, transceiver 902 is configured to receive the first message.

The processor 901 is configured to determine that the first message is a broadcast message according to the destination address of the first message. Then, the first UPF entity determines that the first identifier of the first message is the authenticated identifier. The first identifier is the identifier of the terminal device that sends the first message, or the stream identifier of the service stream to which the first message belongs.

Transceiver 902 is further configured to broadcast the first message.

Here, all the relevant contents in each step according to the method embodiment described above can be quoted in the functional description of the corresponding functional module. I will not repeat this.

FIG. 10 shows a schematic configuration diagram of the CPF entity 1000. The CPF entity 1000 can realize the functions of the CPF entity described above. The CPF entity 1000 may be the above-mentioned CPF entity or a chip arranged in the above-mentioned CPF entity. The CPF entity 1000 can include a processor 1001 and a transceiver 1002. Of which, processor 1001 may be used to perform S703 and S704 in the embodiments shown in FIG. 7 and / or may be used to support other processes of the techniques described herein. good. When the processor 1001 executes S703, the processor 1001 mainly inquires whether the first identifier is an authenticated identifier, and if the first identifier is not authenticated, the processor 1001 obtains the first identifier. It means to authenticate. When the processor 1001 executes S704, it mainly means that the processor 1001 generates a notification message. Transceiver 1002 may be used to perform S702, S703 and 704 in the embodiments shown in FIG. 7, and / or may be used to support other processes in the techniques described herein. good.

For example, transceiver 1002 is configured to receive a broadcast privilege request. The broadcast privilege request is used to directly broadcast a broadcast message with the first identifier by the first UPF entity. The first identifier may be the identifier of the terminal device that sends the broadcast message, or may be the stream identifier of the service stream to which the broadcast message belongs.

Processor 1001 is configured to authenticate the first identifier.

Transceiver 1002 is further configured to send a notification message to the first UPF entity. The notification message is used to indicate that the first identifier is an authenticated identifier. The first UPF entity directly broadcasts a broadcast message with an authenticated identifier.

Here, all the relevant contents in each step according to the method embodiment described above can be quoted in the functional description of the corresponding functional module. I will not repeat this.

In a simple embodiment, one of ordinary skill in the art can conceive that CPF entity 800, UPF entity 900 or CPF entity 1000 can be realized by the structure of the communication device 1100 shown in FIG. 11A. The communication device 1100 can realize the functions of the CPF entity or the first UPF entity described above. The communication device 1100 can include a processor 1101. Among them, when the communication device 1100 is used to realize the function of the CPF entity 800 in the embodiment shown in FIG. 4 or the embodiment shown in FIG. 5, the processor 1101 is S404, S410 and S411 in the embodiment shown in FIG. And may be used to perform S503 in the embodiment shown in FIG. 5, and / or may be used to support other processes in the techniques described herein. Processor 1101 may be used to perform S404, S410 and S411 in the embodiment shown in FIG. 4, and S503 in the embodiment shown in FIG. 5, and / or other in the techniques described herein. It may be used to support the process. When the communication device 1100 is used to realize the function of the first UPF entity in the embodiment shown in FIG. 7, the processor 1101 may be used to execute S708 in the embodiment shown in FIG. 7. And / or may be used to support other processes in the techniques described herein. When the communication device 1100 is used to realize the function of the CPF entity 800 in the embodiment shown in FIG. 7, the processor 1101 may be used to execute S703 and S704 in the embodiment shown in FIG. And / or may be used to support other processes in the techniques described herein.

The communication device 1100 includes a field programmable gate array (field-programmable gate array (FPGA)), an application specific integrated circuit (ASIC), a system on chip (system on chip), and a central processor. , CPU), network processor (network processor, NP), digital signal processor (DSP), microcontroller (micro controller unit, MCU), or programmable logic device (programmable logic device, PLD) realizable. The communication device 1100 is attached to the CPF entity or the first UPF entity according to the embodiment of the present application so that the CPF entity or the first UPF entity realizes the message multicast method or the message broadcast method according to the embodiment of the present application. It may be arranged.

In an alternative embodiment, the communication device 1100 may also include memory 1102. As shown in FIG. 11B, memory 1102 is used to store computer programs or instructions, and processor 1101 is used to decode and execute these computer programs or instructions. As will be appreciated, those computer programs or instructions can include the functional programs of the CPF entity or the first UPF entity described above. Function of CPF Entity When the program is decoded and executed by the processor 1101, depending on the communication device 1100, the function of the CPF entity in the message multicast method or the message broadcast method according to the embodiment of the present application can be realized. Function of First UPF Entity When the program is decoded and executed by the processor 1101, depending on the communication device 1100, the function of the first UPF entity in the message broadcasting method according to the embodiment of the present application can be realized. ..

In another alternative embodiment, the functional program of those CPF entities or the first UPF entity is stored in a memory external to the communication device 1100. When the functional program of the CPF entity is decoded and executed by the processor 1101, a part or all of the functional program of the CPF entity described above is temporarily stored in the memory 1102. When the functional program of the first UPF entity is decoded and executed by the processor 1101, a part or all of the functional program of the first UPF entity is temporarily stored in the memory 1102.

In another alternative embodiment, the functional program of those CPF entities or the first UPF entity is stored in the memory 1102 arranged in the communication device 1100. When the functional program of the CPF entity is stored in the memory 112 in the communication device 1100, the communication device 1100 can be placed in the CPF entity according to the embodiment of the present application. When the functional program of the first UPF entity is stored in the memory 1102 in the communication device 1100, the communication device 1100 can be arranged in the first UPF entity according to the embodiment of the present application.

In yet another alternative embodiment, some of the functional programs of those CPF entities are stored in a memory outside the communication device 1100, and some are stored in the memory 1102 inside the communication device 1100. Alternatively, a part of the functional program of those first UPF entities is stored in the memory outside the communication device 1100, and the other part is stored in the memory 1102 inside the communication device 1100.

In embodiments of the present application, the CPF entity 800, the UPF entity 900, the CPF entity 1000, and the communication device 1100 are configured in the form of each functional module divided corresponding to each function, or are divided by integration. It can be configured in the form of each functional module. A "module" herein can refer to an ASIC, a processor and memory running one or more software or firmware programs, an integrated logic circuit, and / or other device capable of providing the functions described above.

Further, the CPF entity 800 according to the embodiment shown in FIG. 8 can be realized in other forms. For example, a CPF entity includes a processing module and a transceiver module. For example, the processing module can be implemented by the processor 801 and the transceiver module can be implemented by the transceiver 802. Here, the processing module may be used to perform S404, S410 and S411 in the embodiment shown in FIG. 4 and S503 in the embodiment shown in FIG. 5, and / or in the techniques described herein. It may be used to support other processes. Transceiver modules may be used to perform S403, S405, S409 and S412 in the embodiments shown in FIG. 4, and S501 and S502 in the embodiments shown in FIG. 5, and / or described herein. It may be used to support other processes in the technology.

For example, the transceiver module is configured to receive a multicast group join request. The multicast group join request is used to request the first terminal device to join the multicast group indicated by the multicast address.

The processing module is configured to join the terminal device to a multicast group and generate a multicast forwarding route whose destination address is a multicast address.

The transceiver module is further configured to send a multicast forwarding route to at least one UPF entity. At least one UPF entity includes an UPF entity in which all terminal devices included in the multicast group are located.

Here, all the relevant contents in each step according to the method embodiment described above can be quoted in the functional description of the corresponding functional module. I will not repeat this.

The UPF entity 900 according to the embodiment shown in FIG. 9 can be realized in other embodiments. For example, UPF entities include processing modules and transceiver modules. For example, the processing module can be implemented by the processor 901 and the transceiver module can be implemented by the transceiver 902. Here, the processing module may be used to perform S708 in the embodiment shown in FIG. 7 and / or may be used to support other processes in the techniques described herein. good. Transceiver modules may be used to perform S703, S707 and S709 in the embodiments shown in FIG. 7 and / or to support other processes in the techniques described herein. You may. Here, the transceiver module can be used as an integrated module capable of exchanging information with a terminal device or other UPF entity. Alternatively, the transceiver module includes a plurality of sub-transceiver modules. In the sub-transceiver module, a part is configured to exchange information with a terminal device, and another part is configured to exchange information with another UPF entity. One sub-transceiver module can be implemented by the transceiver interface described above.

For example, the transceiver module is configured to receive the first message.

The processing module is configured to determine that the first message is a broadcast message according to the destination address of the first message. Then, the first UPF entity determines that the first identifier of the first message is the authenticated identifier. The first identifier may be the identifier of the terminal device that sends the first message, or may be the stream identifier of the service stream to which the first message belongs.

The transceiver module is further configured to broadcast the first message.

Here, all the relevant contents in each step according to the method embodiment described above can be quoted in the functional description of the corresponding functional module. I will not repeat this.

The CPF entity 1000 according to the embodiment shown in FIG. 10 can also be realized in other forms. For example, a CPF entity includes a processing module and a transceiver module. For example, the processing module may be implemented by the processor 1001 and the transceiver module may be implemented by the transceiver 1002. Here, the processing module may be used to perform S703 and S704 in the embodiments shown in FIG. 7 and / or to support other processes in the techniques described herein. May be good. Here, when the processing module executes S703, the processing module mainly inquires whether the first identifier is an authenticated identifier, and if the first identifier is not authenticated, the processor 1001 is the first. It means to authenticate the identifier of. When the processing module executes S704, it mainly means that the processing module generates a notification message. Transceiver modules may be used to perform S702, S703 and / or 704 in the embodiments shown in FIG. 7 and / or to support other processes in the techniques described herein. You may.

For example, the transceiver module is configured to receive broadcast permission requests. The broadcast privilege request is used to directly broadcast a broadcast message with the first identifier by the first UPF entity. The first identifier may be the identifier of the terminal device that sends the broadcast message, or may be the stream identifier of the service stream to which the broadcast message belongs.

The processing module is configured to generate a notification message. The notification message is used to indicate that the first identifier is an authenticated identifier. Among them, the first UPF entity directly broadcasts a broadcast message having an authenticated identifier.

The transceiver module is further configured to send a notification message to the first UPF entity.

Here, all the relevant contents in each step according to the method embodiment described above can be quoted in the functional description of the corresponding functional module. I will not repeat this.

CPF Entity 800, UPF Entity 900, CPF Entity 1000, and Communication Device 1100 according to embodiments of the present application are used to carry out the methods according to embodiments shown in FIGS. 4, 5, 6 or 7. Can be done. Therefore, the technical effect obtained can be referred to the above-mentioned method embodiment. I will not repeat it here.

The embodiments of the present application have been described with reference to the flow charts and / or block diagrams of the methods, devices (systems) and computer program products according to the embodiments of the present application. As will be appreciated, the respective flow and / or blocks in the flow chart and / or block diagram and the flow and / or block combination in the flow chart and / or block diagram can be realized by computer program instructions. These computer program instructions can be provided to a general purpose computer, a dedicated computer, an embedded processor, or the processor of another programmable data processing device to generate a device. Thereby, an instruction executed by the processor of a computer or other programmable data processing device performs the function specified by one block or multiple blocks in a flow chart or multiple flows and / or block diagrams. Generate the means to realize it.

The embodiments described above can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it may be implemented in whole or in part in the form of a computer program product. Computer program products include one or more computer instructions. When a computer program instruction is loaded and executed on a computer, the process or function according to an embodiment of the present application is generated in whole or in part. The computer may be a general purpose computer, a dedicated computer, a computer network, or other programmable device. Computer instructions can be stored on a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions can be wired (eg, coaxial cable, fiber, digital subscriber line, DSL) or wireless (eg, infrared, wireless, microwave) from a website, computer, server, or data center. Etc.) can be transmitted to another website, computer, server, or data center. The computer-readable storage medium may be any available medium accessible by a computer, or a data storage device such as a server, data center, etc. that includes a combination of one or more available media. Possible media are magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, digital versatile discs, DVDs), or semiconductor media (eg, solid state disks). , SSD))) and the like.

It will be apparent that one of ordinary skill in the art can make various changes and modifications to the embodiments of the present application without departing from the spirit and scope of the present application. And if such modifications or variations of embodiments of the present application fall within the claims of the present application and its equivalent technical scope, the present application is intended to include those modifications or variations.

Claims (20)

It is a message multicast method,
A step in which a CPF entity (Control Plane Function entity) receives a multicast group join request used by a first terminal device to request participation in a multicast group indicated by a multicast address.
A step in which the CPF entity causes the first terminal device to join the multicast group.
The step in which the CPF entity generates a multicast forwarding route whose destination address is a multicast address,
A step in which the CPF entity transmits the multicast forwarding route to at least one UPF entity (User Plane Function entity).
Including
The at least one UPF entity includes an UPF entity in which all terminal devices included in the multicast group are located.
Message multicast method. When the CPF entity receives a multicast group creation request having group information,
When the CPF entity assigns a group to the multicast address,
Including
The group shown in the group information includes at least one terminal device, the multicast group creation request is used to request a multicast address for the group, and the at least one terminal device is the first terminal device. Including terminal equipment,
The message multicast method according to claim 1. The CPF entity belongs to a base station in which the cell after the second terminal device performs inter-cell handover and the cell after the second terminal device is switched and the cell before the second terminal device is switched belong to different base stations. A step of determining that the second terminal device belongs to the multicast group,
A step in which the CPF entity updates the multicast forwarding route,
A step in which the CPF entity transmits the updated multicast forwarding route to the at least one UPF entity and to the UPF entity located after the second terminal device has switched.
The message multicast method according to claim 1 or 2, wherein the method comprises. It ’s a message broadcast method.
When the first UPF entity receives the first message,
A step in which the first UPF entity determines that the first message is a broadcast message based on the destination address of the first message.
A step of determining that the first identifier of the first message is an authenticated identifier by the first UPF entity.
The step in which the first UPF entity broadcasts the first message,
Including
The first identifier is an identifier of the terminal device that transmits the first message, or is a stream identifier of the service stream to which the first message belongs.
Message broadcast method. A step in which the first UPF entity receives a notification message from the CPF entity to indicate that the first identifier is an authenticated identifier.
A step in which the first UPF entity determines that the first identifier is an authenticated identifier based on the notification message.
A step in which the first UPF entity directly broadcasts a broadcast message with the authenticated identifier.
4. The message broadcasting method according to claim 4. The step in which the first UPF entity receives the first message is
A step in which the first UPF entity receives the first message from a terminal device serviced by the first UPF entity or from a second UPF entity.
4. The message broadcasting method according to claim 4 or 5. The step of determining that the first UPF entity further includes the identifier of the second UPF entity in the requested temporary mobile group identifier.
A step of sending a multicast request message to the second UPF entity in order for the first UPF entity to request participation in the same multicast group as the second UPF entity.
The message broadcasting method according to any one of claims 4 to 6, comprising the above. It ’s a message broadcast method.
When the CPF entity receives the broadcast permission request,
The step in which the CPF entity sends a notification message to the first UPF entity, and
A step in which the first UPF entity directly broadcasts a broadcast message with an authenticated identifier.
Including
The broadcast authority request is used to directly broadcast a broadcast message having a first identifier through the first UPF entity, where the first identifier is the identifier of the terminal device that sends the broadcast message. Is, or is the stream identifier of the service stream to which the broadcast message belongs.
The notification message is used to indicate that the first identifier is an authenticated identifier.
Message broadcast method. A CPF entity that contains a transceiver module and a processing module.
The transceiver module is configured to receive a multicast group join request, which is used by the first terminal device to request participation in the multicast group indicated by the multicast address.
The processing module is configured to join the first terminal device to the multicast group.
The processing module is further configured to generate a multicast forwarding route whose destination address is the multicast address.
The transceiver module is further configured to transmit the multicast forwarding route to at least one UPF entity, wherein the at least one UPF entity includes an UPF entity in which all terminal devices included in the multicast group are located.
CPF entity. The transceiver module is further configured to receive a multicast group creation request with group information, the group indicated by the group information includes at least one terminal device, and the multicast group creation request is multicast for the group. Used to request an address, said at least one terminal device includes said first terminal device.
The processing module is further configured to assign the group to the multicast address.
The CPF entity of claim 9. The processing module further belongs to a base station in which the cell after the second terminal device is switched and the cell before the terminal device is switched are different from each other after the second terminal device performs inter-cell handover. Is configured to update the multicast forwarding route by determining that the terminal device belongs to the multicast group.
The transceiver module is further configured to transmit the updated multicast forwarding route to the at least one UPF entity and to the UPF entity located after the second terminal device has switched.
The CPF entity according to claim 9 or 10. An UPF entity that includes a transceiver module and a processing module.
The transceiver module is configured to receive the first message.
The processing module is configured to determine that the first message is a broadcast message based on the destination address of the first message.
The first UPF entity is configured to determine that the first identifier of the first message is an authenticated identifier.
The transceiver module is further configured to broadcast the first message.
The first identifier is an UPF entity that is the identifier of the terminal device that sent the first message, or the stream identifier of the service stream to which the first message belongs. The transceiver module is further configured to receive a notification message from the CPF entity to indicate that the first identifier is an authenticated identifier.
The processing module is further configured to determine that the first identifier is an authenticated identifier based on the notification message.
The first UPF entity directly broadcasts a broadcast message with the authenticated identifier.
The UPF entity according to claim 12. The transceiver module is specifically configured to receive the first message from a terminal device serviced by the first UPF entity or from a second UPF entity.
The UPF entity according to claim 12 or 13. The processing module is further configured to determine that the first UPF entity further includes the identifier of the second UPF entity in the required temporary mobile group identifier.
The transceiver module is further configured to send a multicast request message to the second UPF entity in order to request participation in the same multicast group as the second UPF entity.
The UPF entity according to any one of claims 12 to 14. A CPF entity that contains a transceiver module and a processing module.
The transceiver module is configured to receive a broadcast privilege request, which is used to directly broadcast a broadcast message with a first identifier through a first UPF entity, said first. The identifier of is the identifier of the terminal device that sends the broadcast message, or is the stream identifier of the service stream to which the broadcast message belongs.
The processing module is configured to authenticate the first identifier.
The transceiver module is further configured to send a notification message to the first UPF entity, which is used to indicate that the first identifier is an authenticated identifier.
The first UPF entity directly broadcasts a broadcast message with the authenticated identifier.
CPF entity. A communication system including the UPF entity according to any one of claims 12 to 15 and the CPF entity according to claim 16. A program for causing a computer to execute the message multicast method according to any one of claims 1 to 3. A program for causing a computer to execute the message broadcasting method according to any one of claims 4 to 7. A program for causing a computer to execute the message broadcasting method according to claim 8.

Images