CN110753074B

CN110753074B - Event early warning method and device

Info

Publication number: CN110753074B
Application number: CN201810817921.5A
Authority: CN
Inventors: 赵灿
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Cloud Computing Technologies Co Ltd
Priority date: 2018-07-24
Filing date: 2018-07-24
Publication date: 2021-09-14
Anticipated expiration: 2038-07-24
Also published as: WO2020019989A1; CN110753074A

Abstract

The embodiment of the application discloses an event early warning method and device, relates to the field of Internet of vehicles, and solves the problem that a large amount of wireless resources are occupied due to the fact that event early warning messages are sent periodically. The specific scheme is as follows: and after the early warning event is detected, determining an early warning event sending mode according to the early warning event information, namely, changing the periodic sending of the event early warning message into the change of the early warning event, and sending the event early warning message. The method and the device are used for sending the early warning event.

Description

Event early warning method and device

Technical Field

The embodiment of the application relates to the field of Internet of vehicles, in particular to an event early warning method and device.

Background

The vehicle networking (V2X) technology is that a vehicle interacts information with the outside world through a Global Positioning System (GPS) navigation technology, a wireless communication technology and a remote sensing technology, senses the surrounding conditions of the vehicle and performs early warning in time, thereby achieving the purposes of improving driving safety, improving traffic efficiency, saving energy and protecting environment. V2X may include vehicle to vehicle (V2V) interworking, vehicle to pedestrian (V2P) interworking, vehicle to infrastructure (V2I) interworking, and vehicle to network (V2N) interworking. Among them, event early warning is one of important applications of V2X. In the prior art, a vehicle may periodically send an event warning message to other vehicles after detecting a warning event. However, the periodic transmission of the event warning message may result in a large amount of radio resources being occupied.

Disclosure of Invention

The embodiment of the application provides an event early warning method and device, and solves the problem that a large amount of wireless resources are occupied due to the fact that event early warning messages are sent periodically.

In order to achieve the above purpose, the embodiment of the present application adopts the following technical solutions:

in a first aspect, an embodiment of the present application provides an event early warning method, where the method is applicable to a server, and/or the method is applicable to a communication device that may support the server to implement the method, for example, the communication device includes a chip system, and the method includes: after receiving the event early warning message, sending a first instruction according to early warning event information included in the event early warning message, wherein the first instruction is used for indicating that the early warning event sending mode is a first sending mode, the first sending mode is sending the event early warning message when the early warning event is changed, and the event early warning message further comprises area range information needing to send the early warning event.

According to the event early warning method provided by the embodiment of the application, the event early warning message is sent when the early warning event sending mode is changed into the early warning event changing mode, the number of the same event early warning message is effectively reduced, the redundancy of the event early warning message is greatly reduced on the whole, the uplink and downlink resources are saved, and meanwhile, the computing resources for processing the redundant message by the terminal equipment are saved.

In one possible design, the sending the first indication according to the early warning event information specifically includes: determining that the early warning event meets an early warning event optimization strategy according to the early warning event information, wherein the early warning event optimization strategy is used for determining a sending mode of the early warning event; determining that the early warning event sending mode is a first sending mode; a first indication is sent.

In addition, the area range information that needs to send the warning event may include M multicast addresses and geographical area range information, where M is an integer greater than or equal to 1. And the M multicast addresses are multicast addresses corresponding to the geographical areas affected by the early warning events. The geographical area range information is used to create a corresponding relationship with a Service Area Identification (SAI), and the geographical area range is a geographical area range affected by the early warning event.

Further, with reference to the first aspect and the foregoing possible designs, in another possible design, after sending the first indication according to the warning event information, the method further includes: and sending a second instruction, wherein the second instruction is used for instructing the start of monitoring the multicast member change in the area range needing to send the early warning event. Therefore, the server agent forwards the early warning event, the redundancy of the downlink message is reduced, the downlink resource is saved, and meanwhile, the computing resource for processing the redundant message by the terminal equipment is saved.

Illustratively, after sending the second indication, the method further comprises: receiving a group member change message, and determining an early warning event associated with a member change area range; and sending an event early warning message related to the early warning event to the second terminal equipment. The group member change message comprises member change area range information and the address of the second terminal device. And if the area range information needing to send the early warning event comprises M multicast addresses, the member change area range information comprises a first multicast address, and the first multicast address is an address of a multicast group joined by the second terminal equipment. If the area range information required to send the warning event includes geographical area range information, the member change area range information includes at least one of a Temporary Mobile Group Identity (TMGI) and an SAI.

With reference to the foregoing possible design manner, in another possible design, after sending the second indication, the method further includes: receiving a cancellation event early warning message, wherein the cancellation event early warning message comprises area range information of an early warning event to be cancelled and early warning event cancellation information; and sending a third instruction, wherein the third instruction is used for instructing to cancel monitoring of multicast member change in the area range needing to send the early warning event.

It should be noted that, in another possible design, in a case that the area range information that needs to send the warning event includes M multicast addresses, before receiving the event warning message, the method further includes: and adding N multicast groups, wherein N is an integer greater than or equal to 1, and N is greater than or equal to M. Thereby, the server can forward the event early warning message conveniently.

In a second aspect, an embodiment of the present application provides an event early warning method, where the method is applicable to a first terminal device, and/or the method is applicable to a communication apparatus that can support the first terminal device to implement the method, for example, the communication apparatus includes a chip system, and the method includes: and after receiving a first instruction, sending an event early warning message after the early warning event is changed according to the first instruction, wherein the first instruction is used for indicating that the sending mode of the early warning event is a first sending mode, the first sending mode is the sending of the event early warning message when the early warning event is changed, and the event early warning message after the early warning event is changed comprises the area range information of the early warning event which needs to be sent after the change and the early warning event information after the change.

In one possible design, prior to receiving the first indication, the method further includes: and sending the event early warning message in a second sending mode, wherein the event early warning message comprises the area range information and the early warning event information of the early warning event to be sent, and the second sending mode is to periodically send the event early warning message.

In another possible design, after receiving the first indication, the method further includes: and sending a cancellation event early warning message, wherein the cancellation event early warning message comprises the area range information of the early warning event to be cancelled and the cancellation event information.

In a third aspect, an embodiment of the present application provides an event early warning method, where the method is applicable to a first terminal device, and/or the method is applicable to a communication apparatus that can support the first terminal device to implement the method, for example, the communication apparatus includes a chip system, and the method includes: determining that the early warning event sending mode is a first sending mode according to the early warning event information, and sending an event early warning message when the early warning event changes; and sending a fourth instruction, wherein the fourth instruction is used for instructing the server to forward the event early warning message.

In one possible design, determining that the early warning event sending mode is the first sending mode according to the early warning event information specifically includes: determining that the early warning event meets an early warning event optimization strategy according to the early warning event information, wherein the early warning event optimization strategy is used for determining a sending mode of the early warning event; and determining that the early warning event sending mode is a first sending mode.

With reference to the third aspect and the possible design described above, in another possible design, the fourth indication includes area range information and warning event information that the warning event needs to be sent.

Or before determining that the early warning event sending mode is the first sending mode according to the early warning event information, sending an event early warning message in a second sending mode, wherein the event early warning message comprises area range information and early warning event information of the early warning event to be sent, the second sending mode is to periodically send the event early warning message, the early warning event information comprises an early warning event identifier, and the fourth indication comprises the early warning event identifier.

In another possible design, after sending the fourth indication, the method further includes: and sending a cancellation event early warning message, wherein the cancellation event early warning message comprises the area range information of the early warning event to be cancelled and the cancellation event information.

It should be noted that the area range information that needs to send the warning event may include M multicast addresses and geographical area range information, where M is an integer greater than or equal to 1. And the M multicast addresses are multicast addresses corresponding to the geographical areas affected by the early warning events. The geographical area range information is used for creating a corresponding relation with the SAI, and the geographical area range is a geographical area range influenced by the early warning event.

In a fourth aspect, an embodiment of the present application provides an event early warning method, where the method is applicable to a server, and/or the method is applicable to a communication device that may support the server to implement the method, for example, where the communication device includes a chip system, and the method includes: receiving a fourth instruction, wherein the fourth instruction is used for instructing the server to forward the event early warning message; and sending a second instruction according to the fourth instruction, wherein the second instruction is used for instructing to start monitoring the multicast member change in the area range needing to send the early warning event.

According to the event early warning method provided by the embodiment of the application, the early warning event sending mode is changed into the early warning event sending mode when the early warning event is changed, the early warning event is forwarded by the server agent, the redundancy of the downlink message is reduced, the downlink resource is saved, and meanwhile, the computing resource for processing the redundant message by the terminal equipment is also saved.

In one possible design, the fourth indication may include area range information and pre-alarm event information that requires the pre-alarm event to be sent.

In another possible design, the fourth indication includes an early warning event identification. For example, prior to receiving the fourth indication, the method further comprises: and receiving an event early warning message, wherein the event early warning message comprises area range information and early warning event information of an early warning event to be sent, and the early warning event information comprises an early warning event identifier.

In another possible design, before receiving the fourth indication, the method further includes: and sending an early warning event optimization strategy, wherein the early warning event optimization strategy is used for determining an early warning event sending mode, the early warning event sending mode comprises a first sending mode and a second sending mode, the first sending mode is used for sending an event early warning message when the early warning event is changed, and the second sending mode is used for periodically sending the event early warning message. Therefore, the first terminal device can conveniently determine the early warning event sending mode according to the early warning event information.

Illustratively, after sending the second indication, the method further comprises: receiving a group member change message, and determining an early warning event associated with a member change area range; and sending an event early warning message related to the early warning event to the second terminal equipment. The group member change message comprises member change area range information and the address of the second terminal device. And if the area range information needing to send the early warning event comprises M multicast addresses, the member change area range information comprises a first multicast address, and the first multicast address is an address of a multicast group joined by the second terminal equipment. And if the area range information needing to send the early warning event comprises the geographical area range information, the member change area range information comprises at least one of TMGI and SAI.

In a fifth aspect, an embodiment of the present application provides an event early warning method, where the method is applicable to a multicast management entity, and/or the method is applicable to a communication device that can support the multicast management entity to implement the method, for example, the communication device includes a chip system, and the method includes: and receiving a second instruction, wherein the second instruction is used for instructing to start monitoring the multicast member change in the area range needing to send the early warning event.

In one possible design, the multicast management entity is an authentication server, a public data network gateway (PGW), or a base station, and after receiving the second indication, the method further includes: and determining that the second terminal equipment is added into the area range needing to send the early warning event.

In another possible design, the multicast management entity is a broadcast multicast service center (BM-SC) or a Service Capability Exposure Function (SCEF), and after receiving the second indication, the method further includes: and sending a fifth instruction to the base station through a Mobility Management Entity (MME) according to the area range where the early warning event needs to be sent, wherein the fifth instruction is used for instructing to start monitoring of multicast member change in the service area in the area range where the early warning event needs to be sent.

Further, in combination with the above possible design, in another possible design, a group member change message is sent, where the group member change message includes member change area range information and an address of the second terminal device. And if the area range information needing to send the early warning event comprises M multicast addresses, the member change area range information comprises a first multicast address, and the first multicast address is an address of a multicast group joined by the second terminal equipment. And if the area range information needing to send the early warning event comprises the geographical area range information, the member change area range information comprises at least one of TMGI and SAI.

Optionally, after receiving the second indication, the method further includes: and receiving a third instruction, wherein the third instruction is used for instructing to cancel monitoring of multicast member change in the area range needing to send the early warning event.

In a sixth aspect, an embodiment of the present application further provides a communication device, configured to implement the event early warning method described in the first aspect or the fourth aspect. The communication device implements the method described in the first aspect or the fourth aspect for a server or a support server, for example the communication device comprises a system-on-chip. For example, the communication apparatus includes: the device comprises a receiving unit, a processing unit and a sending unit. The receiving unit is used for receiving an event early warning message, wherein the event early warning message comprises area range information and early warning event information of an early warning event to be sent; the sending unit is used for sending a first instruction, the first instruction is used for indicating that the early warning event sending mode is a first sending mode, and the first sending mode is used for sending the event early warning message when the early warning event is changed. Or, the receiving unit is configured to receive a fourth instruction, where the fourth instruction is used to instruct the server to forward the event early warning message; and the sending unit is used for sending a second instruction according to the fourth instruction, wherein the second instruction is used for instructing the start of monitoring the multicast member change in the area range needing to send the early warning event.

Optionally, the communication device may further include: the processing unit is used for determining that the early warning event meets an early warning event optimization strategy according to the early warning event information, and the early warning event optimization strategy is used for determining a sending mode of the early warning event; and determining that the early warning event sending mode is a first sending mode.

Optionally, the specific event early warning method is the same as that described in the first aspect or the fourth aspect, and is not described herein again.

In a seventh aspect, an embodiment of the present application further provides a communication device, configured to implement the event early warning method described in the second aspect or the third aspect. The communication apparatus is a communication apparatus for implementing the method described in the second aspect or the third aspect for the first terminal device and/or for supporting the first terminal device, and for example, the communication apparatus includes a system-on-chip. For example, the communication apparatus includes: the device comprises a receiving unit, a processing unit and a sending unit. The receiving unit is used for receiving a first instruction, wherein the first instruction is used for indicating that the early warning event sending mode is a first sending mode, and the first sending mode is used for sending the event early warning message when the early warning event is changed; the sending unit is used for sending the event early warning message after the early warning event is changed in a first sending mode, and the event early warning message after the early warning event is changed comprises the area range information of the early warning event needing to be sent after the change and the early warning event information after the change. Or, the processing unit is configured to determine, according to the early warning event information, that the early warning event sending manner is a first sending manner, where the first sending manner is to send an event early warning message when the early warning event is changed, and the sending unit is configured to send a fourth instruction, where the fourth instruction is used to instruct the server to forward the event early warning message.

Optionally, the specific event early warning method is as described in the second aspect or the third aspect, and is not described herein again.

In an eighth aspect, an embodiment of the present application further provides a communication apparatus, configured to implement the method described in the fifth aspect. The communication device implements the event early warning method described in the fifth aspect for the multicast management entity and/or a communication device supporting the multicast management entity, for example, the communication device includes a chip system. For example, the communication apparatus includes: the device comprises a receiving unit, a processing unit and a sending unit. And the receiving unit is used for receiving a second instruction, and the second instruction is used for instructing the start of monitoring the multicast member change in the area range needing to send the early warning event. And the processing unit is used for determining that the second terminal equipment is added into the area range in which the early warning event needs to be sent. The sending unit is used for changing the message by the group members.

Optionally, the specific event early warning method is as described in the fifth aspect, and is not described herein again.

The functional modules in the sixth aspect to the eighth aspect may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described functions. For example, a transceiver for performing the functions of the receiving unit and the transmitting unit, a processor for performing the functions of the processing unit, and a memory for processing the program instructions of the event early warning method according to the embodiment of the present application. The processor, the communication interface and the memory are connected through a bus and complete mutual communication. In particular, reference may be made to the functionality of the behavior of the first terminal device or the server in the method of the first aspect to the method of the fifth aspect.

In a ninth aspect, an embodiment of the present application further provides a communication device, configured to implement the event early warning method described in the first aspect or the fourth aspect. The communication device implements the method described in the first aspect or the fourth aspect for a server or a support server, for example the communication device comprises a system-on-chip. For example, the communication device comprises a processor for implementing the functionality of the method described in the first or fourth aspect above. The communication device may also include a memory for storing program instructions and data. The memory is coupled to the processor, and the processor may call and execute the program instructions stored in the memory to implement the functions in the method described in the first aspect or the fourth aspect. The communication device may further comprise a communication interface for the communication device to communicate with other devices. Illustratively, if the communication device is a server, the other device is a first terminal device.

In one possible arrangement, the communication device comprises: a communication interface for the communication device to communicate with other devices. Illustratively, the communication interface may be a transceiver for receiving the event alert message, the transceiver further for transmitting the first indication. Alternatively, the transceiver is configured to receive the fourth indication, and the transceiver is further configured to transmit the second indication. A memory for storing program instructions. The processor is used for determining that the early warning event meets an early warning event optimization strategy according to the early warning event information, and the early warning event optimization strategy is used for determining a sending mode of the early warning event; and determining that the early warning event sending mode is a first sending mode.

In a tenth aspect, an embodiment of the present application further provides a communication device, configured to implement the event early warning method described in the second aspect or the third aspect. The communication apparatus is a first terminal device or a communication apparatus supporting the first terminal device to implement the method described in the second aspect or the third aspect, and for example, the communication apparatus includes a chip system. For example the communication device comprises a processor for implementing the functions in the method described in the second or third aspect above. The communication device may also include a memory for storing program instructions and data. The memory is coupled to the processor, and the processor may call and execute the program instructions stored in the memory to implement the functions in the method described in the second or third aspect. The communication device may further comprise a communication interface for the communication device to communicate with other devices. Illustratively, if the communication device is a first terminal device, the other device is a server.

In one possible arrangement, the communication device comprises: a communication interface for the communication device to communicate with other devices. Illustratively, the communication interface may be a transceiver. The transceiver is used for receiving the first indication, and the transceiver is also used for sending the event early warning message after the early warning event is changed in a first sending mode. Alternatively, the transceiver is configured to transmit the fourth indication. A memory for storing program instructions. And the processor is used for determining that the early warning event sending mode is a first sending mode according to the early warning event information, and sending the event early warning message when the early warning event is changed.

In an eleventh aspect, an embodiment of the present application further provides a communication device, configured to implement the event early warning method described in the fifth aspect. The communication device is a multicast management entity or a communication device supporting the multicast management entity to implement the method described in the fifth aspect, for example, the communication device includes a chip system. For example, the communication device comprises a processor for implementing the functions in the method described in the fifth aspect above. The communication device may also include a memory for storing program instructions and data. The memory is coupled to the processor, and the processor can call and execute the program instructions stored in the memory, so as to implement the functions in the method described in the fifth aspect. The communication device may further comprise a communication interface for the communication device to communicate with other devices. Illustratively, if the communication device is a multicast management entity, the other device is a server.

In one possible arrangement, the communication device comprises: a communication interface for the communication device to communicate with other devices. Illustratively, the communication interface may be a transceiver. The transceiver is configured to receive a second indication. A memory for storing program instructions. And the processor is used for determining that the second terminal equipment is added into the area range in which the early warning event needs to be sent.

In a twelfth aspect, an embodiment of the present application further provides a computer-readable storage medium, including: computer software instructions; the computer software instructions, when executed in a communication apparatus, cause the communication apparatus to perform the method of any of the first to fifth aspects described above.

In a thirteenth aspect, embodiments of the present application further provide a computer program product containing instructions, which when run in a communication apparatus, cause the communication apparatus to perform the method according to any one of the first to fifth aspects.

In a fourteenth aspect, an embodiment of the present application provides a chip system, where the chip system includes a processor, and may further include a memory, and is configured to implement the functions of the server or the first terminal device in the foregoing method. The chip system may be formed by a chip, and may also include a chip and other discrete devices.

In a fifteenth aspect, an embodiment of the present application further provides a communication system, where the communication system includes the server or the communication apparatus supporting the server to implement the event early warning method described in the first aspect or the fourth aspect, and the first terminal device or the communication apparatus supporting the first terminal device to implement the method described in the second aspect or the third aspect, and the multicast management entity or the communication apparatus supporting the multicast management entity to implement the method described in the fifth aspect;

or the communication system includes the server described in the ninth aspect or a communication apparatus supporting the server to implement the event early warning method described in the first aspect or the fourth aspect, the first terminal device described in the tenth aspect or a communication apparatus supporting the first terminal device to implement the method described in the second aspect or the third aspect, and the multicast management entity described in the eleventh aspect or a communication apparatus supporting the multicast management entity to implement the method described in the fifth aspect.

In addition, the technical effects brought by the design manners of any aspect can be referred to the technical effects brought by the different design manners of the first aspect to the fifth aspect, and are not described herein again.

In the embodiment of the present application, the names of the first terminal device, the server, and the communication apparatus do not limit the device itself, and in practical implementation, the devices may appear by other names. Provided that the function of each device is similar to the embodiments of the present application, and fall within the scope of the claims of the present application and their equivalents.

Drawings

FIG. 1 is a simplified block diagram of an Internet of vehicles system provided by the prior art;

fig. 2 is a flowchart of an event early warning method according to an embodiment of the present disclosure;

fig. 3 is a flowchart of an event early warning method according to an embodiment of the present disclosure;

fig. 4 is a flowchart of an event early warning method according to an embodiment of the present disclosure;

fig. 5 is a flowchart of an event early warning method according to an embodiment of the present disclosure;

fig. 6 is a flowchart of an event early warning method according to an embodiment of the present disclosure;

FIG. 7 is a simplified block diagram of an embodiment of a prior art Internet of vehicles system;

fig. 8 is a flowchart of an event early warning method according to an embodiment of the present disclosure;

fig. 9 is a flowchart of an event early warning method according to an embodiment of the present disclosure;

fig. 10 is a diagram illustrating a structure of a communication device according to an embodiment of the present application;

fig. 11 is a diagram illustrating a structure of a communication device according to the prior art.

Detailed Description

The terms "first," "second," and "third," etc. in the description and claims of this application and the above-described drawings are used for distinguishing between different objects and not for limiting a particular order.

In the embodiments of the present application, words such as "exemplary" or "for example" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

For clarity and conciseness of the following descriptions of the various embodiments, a brief introduction to the related art is first given:

the vehicle networking (V2X) is a huge interactive network formed by information such as vehicle position, speed and route. Fig. 1 is a simplified diagram illustrating an architecture of a car networking system provided in the prior art. The car networking system comprises a V2X application server (V2X application server, V2X AS), a V2X control function (V2X control function, V2X CF), a Home Subscriber Server (HSS), a Mobile Management Entity (MME), a public data network gateway (PGW)/Service Gateway (SGW), an evolved universal terrestrial radio access network (E-UTRAN), a first terminal device, a second terminal device, a third terminal device, and a fourth terminal device.

Wherein, the V2X AS is connected with the V2X CF through a V2 interface; the V2X AS is connected with the PGW or the SGW through the SGi interface; the V2X AS is connected to the first terminal device via a V1 interface. V2X AS is used to send and receive infrastructure information and information sent by the terminal device. In the embodiment of the present application, the V2X AS is further configured to receive the event early warning message, change an early warning event sending manner according to the early warning event information, trigger member change monitoring of the early warning event affected area, and forward the early warning event when a member in the early warning event affected area is changed.

The V2X CF is respectively connected with the first terminal device, the second terminal device, the third terminal device and the fourth terminal device through a V3 interface; the V2X CF is connected to the HSS via a V4 interface. The V2X CF is used to authorize the terminal device and the issuing of the relevant parameters.

The HSS is connected to the MME via an S6a interface. The HSS is used to store subscription data of the user.

The MME and the PGW or the SGW are used to provide bearer establishment from the terminal device to the V2X AS.

The E-UTRAN is connected with the MME, the PGW and the SGW through an S1 interface; the E-UTRAN is respectively connected with the first terminal equipment and the fourth terminal equipment through an LTE-Uu interface.

The terminal devices may be vehicles, pedestrians and stationary objects. For example, the first terminal device may be a vehicle, the second terminal device may be a vehicle, the third terminal device may be a pedestrian, and the fourth terminal device may be a traffic light. The terminal device is installed with V2X application software to facilitate communication with the V2X AS. The terminal devices are connected through a PC5 interface. The V2X application software can be connected and communicated through a V5 interface. The terminal equipment is used for receiving and sending the event early warning message related to the early warning event.

In the prior art, a corresponding relationship between an Internet Protocol (IP) multicast address and a geographical area is configured in advance. After the vehicles in the geographic area detect the early warning event, according to the multicast address corresponding to the range influenced by the early warning event, the vehicles periodically send event early warning messages to other terminal devices (for example, other vehicles) in the range influenced by the early warning event in a Uu mode. However, when the vehicle is not changed within the range influenced by the early warning event, the event early warning message is periodically sent to occupy a large amount of uplink resources, and the event early warning message is sent to other terminal equipment through the Uu port by adopting a unicast mechanism, so that a large amount of downlink resources are also occupied. In addition, vehicles that have received the event early warning message within the range affected by the early warning event still receive the same event early warning message periodically, which also causes waste of vehicle computing resources.

In order to solve the above problem, an embodiment of the present application provides an event early warning method, and the basic principle is as follows: after the early warning event is detected, the sending mode of the early warning event is determined according to the early warning event information, namely the event early warning message is sent when the early warning event is changed from the event early warning message sent periodically, so that the number of the same event early warning message is effectively reduced, the redundancy of the event early warning message is greatly reduced on the whole, the uplink and downlink resources are saved, and meanwhile, the computing resources for processing the redundant message by the terminal equipment are saved.

Embodiments of the present application will be described in detail below with reference to the accompanying drawings.

In a first implementation manner, the early warning event sending manner may be determined by a server, and the server may be V2X AS. As shown in fig. 2, a flowchart of an event early warning method provided in an embodiment of the present application may include:

and S201, V2X AS receives the event early warning message.

And the V2X AS receives an event early warning message sent by the first terminal equipment, wherein the event early warning message comprises area range information and early warning event information of an early warning event needing to be sent. The event early warning message may further include an IP address of the first terminal device, and the IP address of the first terminal device is a source IP address of the event early warning message.

In the embodiment of the present application, a correspondence between multicast addresses and geographic areas may be configured in advance, where each geographic area corresponds to one multicast address. For example, each administrative district of a city may correspond to a multicast address. Of course, the corresponding relationship of the multicast addresses may also be set in a smaller geographic area range, which is not limited herein. Multicast (multicast) is that one sender transmits the same data to a plurality of receivers at the same time, and only one copy of the same data packet needs to be copied, so that point-to-multipoint network connection between the sender and each receiver is realized, and the data transmission efficiency is effectively improved. In some scenarios, multicasting may also be referred to as multicasting. The multicast group corresponding to the multicast address includes two or more receivers. The membership in the multicast group is dynamic and hosts can join and leave the multicast group at any time. After the multicast message reaches the multicast group, a data packet is immediately sent to each receiver in the multicast group, and all hosts in the multicast group can receive the data packet. The multicast address uses a D-type IP address, and the D-type address cannot be used as a source IP address field of the IP message. The multicast group may be permanent or temporary. The permanent multicast group remains unchanged with its IP address and the membership in the permanent multicast group may change. The number of members in the permanent multicast group may be arbitrary or even zero. The address (permanent multicast address) of the permanent multicast group is a reserved multicast address 224.0.0.0-224.0.0.255, wherein the address 224.0.0.0 is reserved without allocation, and other addresses are used by a routing protocol. In addition, 224.0.1.0-224.0.1.255 are public multicast addresses and can be used for the Internet; 224.0.2.0-238.255.255.255 are multicast addresses (temporary multicast addresses) available for users, and are effective in the whole network range; 239.0.0.0-239.255.255.255 are local management multicast addresses, which are valid only within a specific local range. In the embodiment of the application, the multicast addresses 224.0.2.0-238.255.255.255 can be used.

The area range information that needs to send the early warning event may be a multicast address corresponding to a geographical area affected by the early warning event. If the early warning event occurs in the center of one geographical area, the early warning event may only affect the geographical area; if the early warning event occurs at the junction of the two geographical areas, the early warning event will affect the two geographical areas. Therefore, the area range information to send the warning event may include one multicast address or more than two multicast addresses. In the embodiment of the present application, it is assumed that the area range information that needs to send the warning event includes M multicast addresses, where M is an integer greater than or equal to 1. And the M multicast addresses are multicast addresses corresponding to the geographical areas affected by the early warning events. The M multicast addresses may be target IP addresses for the event warning messages.

The early warning event information may include information such as an early warning event identifier, an early warning event duration, and an early warning event moving speed.

And S202, the V2X AS sends a first instruction according to the early warning event information.

The V2X AS may determine whether the early warning event satisfies the early warning event optimization policy according to the early warning event information, and if the early warning event satisfies the early warning event optimization policy, determine that the early warning event sending mode is a first sending mode, where the first sending mode is sending the event early warning message when the early warning event is changed. Then, V2X AS sends the first indication according to the source IP address of the event warning message, for example, the first indication may be sent according to the IP address of the first terminal device. The first indication is used for indicating that the early warning event sending mode is a first sending mode. The first indication may include an early warning event identification and a first sending means identification.

The early warning event optimization strategy is used for determining a sending mode of the early warning event. The event early warning method in the embodiment of the application aims at static early warning events, and the static early warning events can mean events in which the place where the early warning events occur does not change or the place where the early warning events occur changes slowly. The early warning event optimization strategy can comprise the steps of judging whether the type of the early warning event is a static early warning event or not through the early warning event identification, whether the duration of the early warning event exceeds a threshold value or not, whether the moving speed of the early warning event is smaller than the threshold value or not and the like. For example, it is assumed that the early warning event is a traffic jam event, the early warning event identifier is a traffic jam event identifier, the duration of the early warning event is an expected duration of the traffic jam event, for example, an early peak duration and a late peak duration, and the moving speed of the early warning event is the moving speed of the vehicle in the traffic jam situation. The early warning event information may further include road segment information of the occurrence of the traffic congestion event.

It should be noted that, if the early-warning event does not satisfy the early-warning event optimization policy, the V2X AS does not need to change the early-warning event sending manner of the early-warning event, and the first terminal device continues to detect the early-warning event or sends the event early-warning message in the second sending manner, where the second sending manner is to periodically send the event early-warning message. For example, the early warning event is a dynamic early warning event. The dynamic warning event may refer to a localized and relatively massive event in which the warning event occurs, for example, a vehicle that is malfunctioning at high speed.

S203, the first terminal equipment receives the first indication.

And after receiving the first instruction, the first terminal equipment stops sending the event early warning message and stores the sending mode corresponding to the early warning event, namely, the early warning event corresponding to the early warning event identifier sends the event early warning message in the first sending mode.

And S204, the first terminal equipment sends the event early warning message after the early warning event is changed in a first sending mode.

After stopping sending the event early warning message, if the early warning event is changed, the first terminal device sends the event early warning message after the change of the early warning event, and the event early warning message after the change of the early warning event comprises the area range information of the early warning event needing to be sent after the change and the early warning event information after the change. The area range information of the early warning event needing to be sent after the change can be the same as or different from the area range information of the early warning event needing to be sent before the change of the early warning event. The changed early warning event information is different from the early warning event information before the early warning event is changed, and the changed early warning event information comprises related information after the early warning event is changed.

The first terminal device sends an event early warning message after the early warning event is changed to the PGW in a first sending mode, and after receiving the event early warning message after the early warning event is changed, the PGW sends the event early warning message after the early warning event is changed to other members in an area range where the changed early warning event needs to be sent, for example, sends the event early warning message after the early warning event is changed to other terminal devices in an M multicast address range.

According to the event early warning method provided by the embodiment of the application, the sending mode of the early warning event is determined according to the early warning event information through the V2X AS, namely the event early warning message is sent when the early warning event is changed from the event early warning message sent periodically, so that the number of the event early warning messages sent is effectively reduced, the redundancy of the event early warning messages is reduced, the uplink and downlink resources are saved, and meanwhile, the computing resources for processing the redundant messages by the terminal equipment are saved.

For the event early warning method flow for determining the sending mode of the early warning event according to the early warning event information by the V2X AS, other detailed steps may also be included, for example, before the V2X AS receives the event early warning message, the V2X AS needs to join all multicast groups first, and multicast members change and cancel the early warning event, and so on. Based on the event early warning method shown in fig. 2, as shown in fig. 3, a flowchart of an event early warning method provided in an embodiment of the present application is shown. In this embodiment, it is assumed that the area coverage information required to transmit the warning event includes M multicast addresses. Other detailed steps are exemplified below.

S301, V2X AS join N multicast groups.

N is an integer greater than or equal to 1. The V2X AS may send an MLD message to the PGW according to a Multicast Listener Discovery (MLD) protocol to request to join all multicast groups planned in advance, where a detailed process of specifically joining a multicast group may refer to descriptions in the prior art, and details of this embodiment of the present application are not described herein again. All multicast groups planned in advance may be multicast groups corresponding to the multicast addresses set forth in S201 configured in advance. Optionally, if there is a router between V2X AS and PGW, join the multicast group by sending an MLD message to the router.

S302, the first terminal device detects an early warning event.

S303, the first terminal equipment sends an event early warning message.

And the first terminal equipment sends the event early warning message to the PGW in a second sending mode. The second sending mode is to send the event early warning message periodically. The event alert message may include the M multicast address and alert event information. The M multicast addresses may be multicast addresses corresponding to geographical areas affected by the early warning event. The event early warning message is an IP multicast message.

S304, the PGW receives the event early warning message.

S305, the PGW forwards the event early warning message.

After receiving the event warning message, the PGW executes S305a to S305 b. And inquiring a multicast address routing table according to the M multicast addresses included in the event early warning message to forward the event early warning message to receivers within the area range of the M multicast addresses, wherein the receivers within the area range of the M multicast addresses comprise V2X AS.

S201 to S204 are executed, and for the detailed explanation of S201 to S204, reference may be made to the explanation in the embodiment shown in fig. 2, which is not described herein again in this embodiment of the present application.

In the prior art, after receiving the event early warning message, V2X AS needs to send the event early warning message to other terminal devices in the area range where the early warning event needs to be sent through the Uu port by using a unicast mechanism, which results in occupying a large amount of downlink resources. In the embodiment of the present application, the V2X AS proxy PGW may forward the event early warning message to the newly added member, and specifically, the embodiment of the present application further includes the following steps.

S306, V2X AS sends a second indication.

And the V2X AS sends a second instruction to the multicast management entity, wherein the second instruction is used for indicating the multicast member change in the area range of the M multicast addresses for starting monitoring. The second indication may include M multicast addresses and a multicast member change reporting flag.

It should be noted that the multicast management entity is configured to manage a multicast group. The multicast management entity may be an authentication server or a base station (e.g., eNB). In particular, the PGW may also perform the function of the multicast management entity. If the multicast management entity is a PGW, the multicast management entity and the PGW in fig. 3 may be the same network element, i.e., the PGW.

S307, the multicast management entity receives the second instruction.

And after receiving the second instruction sent by the V2X AS, the multicast management entity monitors multicast member change in the area range of the M multicast addresses. When there is a new member in the area range of the M multicast address, the multicast management entity may send a group member change message to the V2X AS, and the V2X AS receives the group member change message and forwards an event early warning message associated with the early warning event to the new member. Therefore, the V2X AS agent PGW forwards the early warning event, thereby reducing the redundancy of the downlink message, saving the downlink resource and saving the computing resource for processing the redundant message by the terminal equipment.

Illustratively, as shown in S308 to S3014, the flow is related to multicast member change in the area range of M multicast addresses.

And S308, the second terminal equipment joins the multicast group.

And the second terminal equipment sends an MLD message to the multicast management entity to trigger the joining of the IP multicast group.

S309, the multicast management entity determines that the second terminal device is added into the area range of the first multicast address.

The MLD message may include an identifier of the second terminal device, where the identifier of the second terminal device may refer to a geographic identifier of the second terminal device, and may also refer to an IP address of the second terminal device. And the multicast management entity determines whether the second terminal equipment is added into the area range of the M multicast addresses monitored by the V2X AS according to the identifier of the second terminal equipment, and if so, sends a group member change message to the V2X AS. For example, the multicast management entity determines that the second terminal device joins the area range of the first multicast address monitored by the V2X AS according to the identifier of the second terminal device, and executes S3010. The first multicast address may be any one of M multicast addresses.

S3010, the multicast management entity sends the group member change message.

The group member change message includes the first multicast address and the address of the second terminal device.

S3011 and V2X AS receive the group member change message.

S3012, V2X AS determines an early warning event associated with the area range of the first multicast address.

And S3013, the V2X AS sends an event early warning message related to the early warning event to the second terminal equipment.

And the V2X AS sends the event early warning message related to the early warning event to the second terminal equipment through IP unicast.

S3014, the second terminal device receives the event early warning message.

Further, if the early warning event is terminated, the terminal device may send an event cancellation early warning message to other devices, so that the other devices cancel attention to the early warning event. The embodiment of the application may further include an early warning event cancellation procedure, which is exemplarily described in detail in S3015 to S3021.

S3015, the first terminal device detects that the early warning event is ended.

S3016, the first terminal device sends a cancellation event early warning message.

The first terminal equipment sends a cancellation event early warning message to the PGW in a first sending mode, wherein the cancellation event early warning message comprises an M multicast address and cancellation early warning event information. The cancellation early warning event information comprises early warning event identifications of early warning events needing to be cancelled. The cancellation event warning message may further include an address of the first terminal device.

S3017, the PGW receives a cancel event early warning message.

S3018, the PGW forwards the cancellation event early warning message.

And after receiving the cancel event early warning message, the PGW executes S3018 a-S3018 b. And inquiring a multicast address routing table according to the M multicast addresses included in the cancellation event early warning message, and forwarding the cancellation event early warning message to the receivers in the area range of the M multicast addresses, wherein the receivers in the area range of the M multicast addresses comprise V2X AS.

S3019, V2X AS receives the cancel event warning message.

S3020, V2X AS send a third indication.

And the V2X AS sends a third instruction to the multicast management entity, wherein the third instruction is used for instructing to cancel monitoring the multicast member change in the area range of the M multicast addresses. The third indication may include the M multicast address and the cancellation of the monitoring of the new multicast member.

S3021, the multicast management entity receives the third instruction.

And after receiving the third instruction, the multicast management entity cancels monitoring the multicast member change in the area range of the M multicast addresses.

The event early warning method effectively reduces the number of the same event early warning messages, greatly reduces the redundancy of the event early warning messages on the whole, saves uplink and downlink resources, and meanwhile, the early warning event is forwarded by the V2X AS agent, reduces the redundancy of the downlink messages and saves the downlink resources.

In a second implementation manner, after the terminal device detects the early warning event, the terminal device may decide the sending manner of the early warning event. As shown in fig. 4, a flowchart of an event early warning method provided in an embodiment of the present application may include:

s401, the first terminal device determines that the early warning event sending mode is the first sending mode according to the early warning event information.

The first sending mode is to send the event early warning message when the early warning event is changed. For a specific method for determining, by the first terminal device, that the early warning event sending manner is the first sending manner according to the early warning event information, reference may be made to the description in S202, and details of the embodiment of the present application are not described herein again.

S402, the first terminal equipment sends a fourth instruction.

The fourth indication is used for instructing the server to forward the event early warning message. The fourth indication may comprise different content in different implementations.

First, the fourth indication may include area range information and warning event information that the warning event needs to be sent. For detailed explanation of the area range information and the warning event information that needs to be sent to the warning event, reference may be made to the explanation in S201, and details are not described herein in this embodiment of the present application.

And if the early warning event sending mode is determined to be the first sending mode according to the early warning event information, the first terminal equipment sends the event early warning message in a second sending mode, the event early warning message comprises area range information and early warning event information, and the early warning event information comprises an early warning event identifier. In this case, the fourth indication may comprise only the early warning event identification. The second sending mode is to send the event early warning message periodically.

S403, V2X AS receives the fourth indication.

S404, the V2X AS sends a second instruction according to the fourth instruction.

The second indication is used for indicating the start of monitoring the multicast member change in the area range needing to send the early warning event.

For mode one, the V2X AS sends a second indication to the multicast management entity. The second indication may include area range information that the early warning event needs to be sent and a multicast member change reporting identifier.

For the second mode, the V2X AS matches the pre-received area range information of the early warning event that needs to be sent corresponding to the same early warning event identifier according to the early warning event identifier, and then the V2X AS sends a second instruction to the multicast management entity. The second indication may include area range information that the early warning event needs to be sent and a multicast member change reporting identifier.

According to the event early warning method provided by the embodiment of the application, the first terminal equipment changes the sending mode of the early warning event according to the early warning event information, namely, the event early warning message is sent when the early warning event is changed from the event early warning message sent periodically, so that the number of the event early warning messages sent is effectively reduced, the redundancy of the event early warning messages is reduced, the uplink and downlink resources are saved, and meanwhile, the computing resources for the terminal equipment to process the redundant messages are saved.

For the event early warning method flow for determining the sending mode of the early warning event according to the early warning event information by the terminal device, other detailed steps can also be included, for example, before the terminal device determines the sending mode of the early warning event, an early warning event optimization strategy needs to be acquired first, and early warning events need to be changed and cancelled by multicast members, and the like. Based on the event early warning method shown in fig. 4, as shown in fig. 5, a flowchart of an event early warning method provided in an embodiment of the present application is shown. In this embodiment, it is assumed that the area coverage information required to transmit the warning event includes M multicast addresses. Other detailed steps are exemplified below.

S501, configuring an early warning event optimization strategy.

In one possible implementation manner, the terminal device may send a request message to the V2X AS, where the request message is used to obtain the early warning event optimization policy. Such as a registration request message. And the V2X AS sends an early warning event optimization strategy to the terminal equipment after receiving the request message.

In another possible implementation manner, the early warning event optimization strategy may be configured in advance when the terminal device leaves a factory.

S502, the first terminal device detects an early warning event.

S401 to S403 are executed, and for the detailed explanation of S401 to S403, reference may be made to the explanation in the embodiment shown in fig. 4, which is not described herein again in this embodiment.

And S503, the first terminal equipment sends the event early warning message after the early warning event is changed in a first sending mode.

For a detailed explanation of S503, reference may be made to the explanation in S204 above, and the embodiments of the present application are not described herein again.

And S504, V2X AS sends an event early warning message.

For the first mode, in the case that the fourth indication includes the M multicast addresses and the warning event information, the V2X AS sends the warning event information to the area range of the M multicast addresses according to the content included in the fourth indication.

For the second mode, before determining that the early warning event sending mode is the first sending mode according to the early warning event information, the first terminal device sends an event early warning message in the second sending mode, wherein the event early warning message comprises an M multicast address and early warning event information, and the early warning event information comprises an early warning event identifier. In this case, the fourth indication may comprise only the early warning event identification. And the V2X AS matches the same early warning event identifier included in the pre-received fourth indication and the M multicast address corresponding to the early warning event identifier according to the early warning event identifier, and then the V2X AS sends early warning event information to the area range of the M multicast address.

S505, the multicast management entity receives the second instruction.

For the detailed explanation of S505, reference may be made to the explanation in S307, and the embodiments of the present application are not described herein again. Therefore, the V2X AS agent forwards the early warning event, thereby reducing the redundancy of the downlink message, saving the downlink resource and saving the computing resource for processing the redundant message by the terminal equipment.

Illustratively, as shown in S506 to S5012, the flow relates to multicast member change in an area range where an early warning event needs to be sent.

And S506, the second terminal device joins the multicast group.

S507, the multicast management entity determines that the second terminal equipment is added into the area range of the first multicast address. S508 is performed.

S508, the multicast management entity sends the group member change message.

S509, V2X AS receives the group member change message.

S5010, V2X AS determines an early warning event associated with the first multicast address range.

S5011, V2X AS sends an event alert message related to the alert event to the second terminal device.

S5012, the second terminal equipment receives the event early warning message.

For the detailed explanation of S506 to S5012, reference may be made to the explanations of S308 to S3014, and the embodiments of the present application are not described herein again.

Further, if the early warning event is terminated, the terminal device may send an event cancellation early warning message to other devices, so that the other devices cancel attention to the early warning event. The embodiment of the application may further include an early warning event cancellation procedure, which is exemplarily described in detail in S5013 to S5018.

S5013, the first terminal device detects that the early warning event is ended.

S5014, the first terminal equipment sends a cancellation event early warning message.

The first terminal equipment transmits a cancellation event early warning message to the V2X AS in a first transmission mode. The cancellation event warning message includes an M multicast address and cancellation warning event information. The cancellation early warning event information comprises early warning event identifications of early warning events needing to be cancelled. The cancellation event warning message may further include an address of the first terminal device.

S5015, V2X AS receives the cancel event alert message.

S5016, V2X AS forwards the cancel event alert message.

And the V2X AS sends the cancellation early warning event information to the receivers within the area range of the M multicast addresses according to the M multicast addresses included in the cancellation event early warning message.

S5017, V2X AS sends a third indication.

And the V2X AS sends a third instruction to the multicast management entity, wherein the third instruction is used for instructing to cancel monitoring the multicast member change in the area range of the M multicast addresses. The third indication may include area range information of the M multicast addresses and a monitoring flag for canceling the new multicast member.

S5018, the multicast management entity receives the third indication.

And after receiving the third instruction, the multicast management entity cancels monitoring the multicast member change in the M multicast address range.

Optionally, after the first terminal device determines that the sending mode of the early warning event is the first sending mode according to the early warning event information, the first terminal device may send an event early warning message to the PGW, and the PGW forwards the event early warning message to an area where the early warning event needs to be sent, so that the V2X AS sends the second indication to the multicast management entity. Exemplarily, as shown in fig. 6, a flowchart of an event early warning method provided in an embodiment of the present application is shown.

S601, the first terminal equipment sends an event early warning message.

The first terminal equipment sends an event early warning message to the PGW in a first sending mode. The event alert message includes area range information of the M multicast addresses and alert event information. The event early warning message is an IP multicast message.

S602, the PGW receives the event early warning message.

S603, the PGW forwards the event early warning message.

After receiving the event warning message, the PGW performs S603a to S603 b. And inquiring a multicast address routing table according to the M multicast addresses included in the event early warning message and forwarding the multicast address routing table to the receivers in the area range of the M multicast addresses, wherein the receivers in the area range of the M multicast addresses include V2X AS, so that the V2X AS receives the event early warning message.

And S604, the V2X AS receives the event early warning message.

S601 to S604 implement the functions of S402 and S403, so that V2X AS receives the event warning message. Similarly, after receiving the cancellation event early warning message, the PGW executes S606 and S607a to S607b to implement the function of S5014, so that the V2X AS receives the cancellation event early warning message. And inquiring a multicast address routing table according to the M multicast addresses to forward the cancellation event early warning message to the receivers in the area range of the M multicast addresses, wherein the receivers in the area range of the M multicast addresses comprise V2X AS, so that the V2X AS receives the cancellation event early warning message.

Optionally, in addition to forwarding the event warning message by using the IP multicast technology, the MBMS may also be used to perform multicast forwarding of the event warning message.

Fig. 7 is a simplified diagram illustrating an architecture of a car networking system provided in the prior art. The vehicle networking system comprises a V2X AS, a BM-SC, a MBMS GW, an MME, an E-UTRAN and terminal equipment.

The V2X AS is connected with the terminal equipment through a V1 interface; the V2X AS is connected with the BM-SC through MB2-U or MB2-C interfaces. V2X AS is used to send and receive infrastructure information and information sent by the terminal device.

BM-SC connects with MBMS GW through SGi-mb or SGmb interface. The BM-SC is used to manage the MBMS multicast group, e.g. cancellation of establishment of bearers, etc.

The MBMS GW is connected with the E-UTRAN through an M1 interface; the MBMS GW is connected with the MME through an Sm interface. The MBMS GW is used for distribution of multicast messages.

The MME is connected with the E-UTRAN through an M3 or S1-MME interface. The MME is used to provide bearer establishment for the terminal device to the V2X AS.

The E-UTRAN is connected with the terminal equipment through an LTE-Uu interface.

The terminal devices may be vehicles, pedestrians and stationary objects.

In a third implementation manner, after the terminal device detects the early warning event, the flow of deciding the sending manner of the early warning event may refer to the detailed explanation in the first implementation manner and the second implementation manner. For example, the terminal device may determine the sending method of the early warning event or the V2X AS may determine the sending method of the early warning event, which is not described herein again in this embodiment of the present application. The difference from the first implementable manner and the second implementable manner is that the area range information to be sent the warning event may be geographical area range information, and the geographical area range information is geographical area range information affected by the warning event. The V2X AS may know a Service Area Identity (SAI) in advance, create a corresponding relationship with the SAI according to geographical area range information included in the event early warning message after the V2X AS receives the event early warning message, and send the event early warning message to a Temporary Mobile Group Identity (TMGI) and the SAI when the SAI is changed by an adult. One TMGI corresponds to multiple SAIs, as will be appreciated. In the embodiments of the present application, a plurality may mean one or more than one. As shown in fig. 8, a flowchart of an event early warning method provided in the embodiment of the present application may include the following steps.

S801 and V2X AS establish the corresponding relation between the geographic area range and the SAI.

After the V2X AS receives the event early warning message, the corresponding relationship between the geographical area range and the SAI may be created according to the area range information that needs to send the early warning event and is included in the event early warning message. For example, the area range information that needs to send the warning event may include location information of the first terminal device, determine an SAI where the first terminal device is located according to the location information of the first terminal device, and create a correspondence between the geographic area range and the SAI. Meanwhile, V2X AS applies for a TMGI from the BM-SC, and the group corresponding to the TMGI includes SAI related to the geographical area range.

S802, V2X AS sends event early warning information.

V2X AS sends an event alert message to recipients within the MBMS coverage area.

S803, V2X AS sends a second indication.

And the second indication is used for indicating the BM-SC to start monitoring the multicast member change of the corresponding SAI in the TMGI range. The second indication may include the TMGI and the multicast member change reporting flag. The BM-SC corresponds to a multicast management entity. In the implementation of the present application, the multicast management entity may also be an SCEF.

S804, the BM-SC receives the second indication.

S805, BM-SC sends a fifth indication.

And the BM-SC forwards the fifth indication to the eNB corresponding to the SAIs included by the TMGI through the MME. For example, S805 a-S805 c are executed. And the BM-SC sends a fifth instruction to the MME, wherein the fifth instruction comprises a plurality of SAIs (specific identifiers) corresponding to the TMGI (temporary mobility management index) and a multicast member change reporting identifier. The MME sends a fifth indication to the base station corresponding to each SAI of the plurality of SAIs. Each eNB receives the fifth indication.

S806, the second terminal equipment accesses the eNB.

The second terminal device triggers a Radio Resource Control (RRC) connection to access a new eNB.

S807, the eNB determines that the second terminal equipment is added into the area range of the TMGI.

S808, the eNB sends the group member change message.

The group member change message includes the TMGI and the address of the second terminal device. The eNB sends the group member change message to the V2X AS through the MME and the BM-SC.

S809, V2X AS receives the group member change message.

S8010, V2X AS determines an early warning event associated with a range of regions of the TMGI.

S8011, V2X AS sends an event alert message related to an alert event.

The V2X AS multicasts to the MBMS multicast group via MBMS multicast messages.

S8012, the second terminal device receives the event early warning message.

Optionally, the V2X AS may also send an event warning message related to the warning event to the second terminal device by means of IP unicast. For example, if the group member change message further includes an identification of the SAI. The V2X AS may also send an event warning message related to the warning event to the second terminal device according to the identifier of the SAI where the second terminal device is located. Or, the group member change message includes the address of the second terminal device, and the V2X AS may also send an event warning message related to the warning event to the second terminal device according to the address of the second terminal device.

In a possible scenario, since a plurality of SAIs are included in the MBMS, when V2X AS monitors whether a new member joins in the MBMS broadcast area, if the second terminal device moves from SAI1 to SAI2, both SAI1 and SAI2 belong to the MBMS broadcast area that needs to be monitored, and at this time, V2X AS senses that a new member joins in the MBMS broadcast area. Therefore, the BM-SC needs to identify the edge SAI list, and the eNB monitors whether the edge SAI list has the information of the new member. If the eNB monitors that the new members exist, the eNB informs the BM-SC of the source SAI identification and the target SAI identification, the BM-SC judges whether the source cell belongs to the MBMS broadcast domain, when the BM-SC determines that the source cell does not belong to the MBMS broadcast domain, the BM-SC can determine that the new members exist in the current MBMS domain, and then reports the information of the new members existing in the MBMS broadcast domain to the V2X AS. In this case, as shown in fig. 8, the sixth indication may include an edge SAI list and a multicast member change reporting identifier. The group member change message may include the TMGI, source SAI identification, and destination SAI identification. The group member change message may further include an address of the second terminal device.

In addition, a cancel event alert message is received at V2X AS, which also requires V2X AS to notify the base station. For a detailed explanation of other similar method steps, reference may be made to the descriptions in the first implementation manner and the second implementation manner, and further description of embodiments of the present application is omitted here.

According to the event early warning method provided by the embodiment of the application, when the sending period of the event early warning message is greater than the adding period of the newly-added member, the downlink message amount is greatly reduced.

In a fourth implementation manner, the first terminal device may send the event early warning message to the traffic control center, and then the traffic control center sends the event early warning message to the V2X AS. The traffic control center is used AS a sending entity of the event early warning message, and in this case, the V2X AS may be used for deciding the early warning event sending mode, or the traffic control center may be used for deciding the early warning event sending mode.

Illustratively, as shown in fig. 9, a flowchart of an event early warning method provided in an embodiment of the present application is shown. And after receiving the event early warning message, the traffic control center sends the event early warning message to the V2X AS, and the V2X AS decides an early warning event sending mode. For detailed explanation of specific method steps, reference may be made to the explanation in the first implementation manner, and details are not described herein in this embodiment of the present application. Of course, after the traffic control center receives the event early warning message, the traffic control center can also decide the early warning event sending mode. For detailed explanation of the specific method steps, reference may be made to the explanation in the second implementation manner, and details are not described herein in this embodiment of the present application. The area range information required to send the warning event may include M multicast addresses, and may also include a service area identifier of the MBMS.

In the embodiments provided in the present application, the method provided in the embodiments of the present application is introduced from the perspective of the server, the terminal device, and the interaction between the server and the terminal device. It is understood that, for each network element, for example, a server and a terminal device, to implement each function in the method provided in the embodiments of the present application, the server and the terminal device include corresponding hardware structures and/or software modules for performing each function. Those of skill in the art will readily appreciate that the present application is capable of hardware or a combination of hardware and computer software implementing the various illustrative algorithm steps described in connection with the embodiments disclosed herein. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiment of the present application, the server and the terminal device may be divided into the functional modules according to the above method examples, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, in the embodiment of the present application, the division of the module is schematic, and is only one logic function division, and there may be another division manner in actual implementation.

Fig. 10 shows a schematic diagram of a possible composition of the communication device according to the foregoing and related embodiments, in the case of dividing each functional module according to the corresponding function, and as shown in fig. 10, the communication device is a server or a communication device supporting the server to implement the method provided in the embodiments, and the communication device may be a chip system, for example. The server may be V2X AS. The communication device is capable of performing the steps performed by V2X AS in any of the method embodiments of the present application. The communication apparatus may include: a receiving unit 1001 and a transmitting unit 1002.

The receiving unit 1001 is configured to support the communication apparatus to execute the method described in the embodiment of the present application. For example, the receiving unit 1001 is configured to execute or support the communication device to execute S201 in the event early warning method shown in fig. 2, S201, S3011, and S3019 in the event early warning method shown in fig. 3, S403 in the event early warning method shown in fig. 4, S403, S509, and S5015 in the event early warning method shown in fig. 5, S604, S509, and S5015 in the event early warning method shown in fig. 6, S809 in the event early warning method shown in fig. 8, and S906, S9016, and S9024 in the event early warning method shown in fig. 9.

The sending unit 1002 is configured to support a communication device to execute the method described in the embodiment of the present application. For example, the transmitting unit 1002 is configured to execute or support the communication device to execute S202 in the event early warning method shown in fig. 2, S202, S306, S3013, and S3020 in the event early warning method shown in fig. 3, S404 in the event early warning method shown in fig. 4, S504, S404, S5011, S5016, and S5017 in the event early warning method shown in fig. 5, S404, S5011, and S5017 in the event early warning method shown in fig. 6, S801, S802, S803, and S8011 in the event early warning method shown in fig. 8, and S907, S909, S9010, S9018, and S9025 in the event early warning method shown in fig. 9.

In this embodiment, further, as shown in fig. 10, the communication apparatus may further include: a processing unit 1003.

The processing unit 1003 is configured to send data, for example, to support the communication device to execute S3012 in the event early warning method shown in fig. 3, S5010 in the event early warning method shown in fig. 5, S5010 in the event early warning method shown in fig. 6, S8010 in the event early warning method shown in fig. 8, and S9017 in the event early warning method shown in fig. 9.

It should be noted that all relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.

The communication device provided by the embodiment of the application is used for executing the method of any embodiment, so that the same effects as the method of the embodiment can be achieved.

If the communication apparatus shown in fig. 10 is a terminal device or a communication apparatus supporting the terminal device to implement the method provided in the embodiment, for example, the communication apparatus may be a chip system, and the terminal device may be a first terminal device or a second terminal device. The communication device is capable of performing the steps performed by the first terminal device or the second terminal device in any of the method embodiments of the present application.

The receiving unit 1001 is configured to support the communication apparatus to execute the method described in the embodiment of the present application. For example, the receiving unit 1001 is configured to execute or support the communication device to execute S203 in the event early warning method shown in fig. 2, S203 and S3014 in the event early warning method shown in fig. 3, S5012 in the event early warning method shown in fig. 5, S5012 in the event early warning method shown in fig. 6, S8012 in the event early warning method shown in fig. 8, and S9019 in the event early warning method shown in fig. 9.

The sending unit 1002 is configured to support a communication device to execute the method described in the embodiment of the present application. For example, the transmitting unit 1002 is configured to execute or support the communication device to execute S303 and S3016 in the event early warning method shown in fig. 3, S402 in the event early warning method shown in fig. 4, S402 and S5014 in the event early warning method shown in fig. 5, S601 and S605 in the event early warning method shown in fig. 6, and S903 and S9021 in the event early warning method shown in fig. 9.

A processing unit 1003, configured to transmit data, for example, to support the communication device to execute S204 in the event early warning method shown in fig. 2, S302, S204, and S3015 in the event early warning method shown in fig. 3, S401 in the event early warning method shown in fig. 4, S401, S502, and S5013 in the event early warning method shown in fig. 5, S502, S401, and S5013 in the event early warning method shown in fig. 6, and S902 and S9020 in the event early warning method shown in fig. 9.

If the communication device shown in fig. 10 is a multicast management entity or a communication device supporting the multicast management entity to implement the method provided in the embodiment, the communication device may be a chip system, for example. The communication device is capable of performing the steps performed by the multicast management entity in any of the method embodiments of the present application.

The receiving unit 1001 is configured to support the communication apparatus to execute the method described in the embodiment of the present application. For example, the receiving unit 1001 is configured to execute or support the communication apparatus to execute S307 and S3021 in the event early warning method shown in fig. 3, S505 and S5018 in the event early warning method shown in fig. 5, S505 and S5018 in the event early warning method shown in fig. 6, S804 in the event early warning method shown in fig. 8, and S9011 and S9026 in the event early warning method shown in fig. 9.

The sending unit 1002 is configured to support a communication device to execute the method described in the embodiment of the present application. For example, the sending unit 1002 is configured to execute or be used to support the communication device to execute S301 in the event early warning method shown in fig. 3, S508 in the event early warning method shown in fig. 5, S508 in the event early warning method shown in fig. 6, S805a in the event early warning method shown in fig. 8, and S9015 in the event early warning method shown in fig. 9.

A processing unit 1003, configured to send data, for example, to support the communication device to execute S309 in the event early warning method shown in fig. 3, S507 in the event early warning method shown in fig. 5, S507 in the event early warning method shown in fig. 6, and S9014 in the event early warning method shown in fig. 9.

Fig. 11 shows a communication device 1100 provided in the prior art for implementing the functions of the server in the method. The communication device 1100 may be a server or a device in a server. The server may be V2X AS. The communication device 1100 may be a chip system. In the embodiment of the present application, the chip system may be composed of a chip, and may also include a chip and other discrete devices. Alternatively, the communication apparatus 1100 is used to implement the functions of the terminal device in the above-described method. The communication apparatus 1100 may be a terminal device or an apparatus in a terminal device. The terminal device may be the first terminal device or the second terminal device. The communication device 1100 may be a chip system. In the embodiment of the present application, the chip system may be composed of a chip, and may also include a chip and other discrete devices.

The communication apparatus 1100 includes at least one processor 1101 for implementing the functions of the server or the terminal device in the method provided by the embodiment of the present application. For example, the processor 1101 may be configured to determine that the early warning event meets the early warning event optimization policy according to the early warning event information, determine that the sending mode of the early warning event is the first sending mode, and the like, which refer to the detailed description in the method example and are not described herein again.

The communications apparatus 1100 can also include at least one memory 1102 for storing program instructions and/or data. The memory 1102 is coupled to the processor 1101. The coupling in the embodiments of the present application is an indirect coupling or a communication connection between devices, units or modules, and may be an electrical, mechanical or other form for information interaction between the devices, units or modules. The processor 1101 may cooperate with the memory 1102. Processor 1101 may execute program instructions stored in memory 1102. At least one of the at least one memory may be included in the processor.

The communications apparatus 1100 may also include a communication interface 1103 for communicating with other devices over a transmission medium, such that the apparatus used in the communications apparatus 1100 may communicate with other devices. Illustratively, if the communication device is a server, the other device is a terminal device. If the communication device is a terminal device, the other device is a server. The processor 1101 transceives data using the communication interface 1103 and is configured to implement the method performed by the server or the terminal device described in the embodiments corresponding to fig. 2 to 6 and fig. 8 to 9.

In the embodiment of the present application, a specific connection medium among the communication interface 1103, the processor 1101, and the memory 1102 is not limited. In the embodiment of the present application, the communication interface 1103, the processor 1101, and the memory 1102 are connected by a bus 1104 in fig. 11, the bus is shown by a thick line in fig. 11, and the connection manner between other components is only schematically illustrated and is not limited thereto. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 11, but this is not intended to represent only one bus or type of bus.

In the embodiments of the present application, the processor may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the methods, steps, and logic blocks disclosed in the embodiments of the present application. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in a processor.

In the embodiment of the present application, the memory may be a nonvolatile memory, such as a Hard Disk Drive (HDD) or a solid-state drive (SSD), and may also be a volatile memory, for example, a random-access memory (RAM). The memory is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to such. The memory in the embodiments of the present application may also be circuitry or any other device capable of performing a storage function for storing program instructions and/or data. The terminal device according to the embodiment of the present application may be a communication apparatus shown in fig. 10. The server according to the embodiment of the present application may be a communication device shown in fig. 10.

Through the above description of the embodiments, it is clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the above described functions.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described device embodiments are merely illustrative, and for example, the division of the modules or units is only one logical functional division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another device, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may be one physical unit or a plurality of physical units, that is, may be located in one place, or may be distributed in a plurality of different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The method provided by the embodiment of the present application may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, a server, a terminal, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., Digital Video Disk (DVD)), or a semiconductor medium (e.g., SSD), among others.

The above description is only an embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. An event early warning method is applied to a server or a chip built in the server, and comprises the following steps:

receiving an event early warning message, wherein the event early warning message comprises area range information and early warning event information of an early warning event to be sent; the area range information needing to send the early warning event comprises M multicast addresses or geographical area range information, the geographical area range information is used for establishing a corresponding relation with a Service Area Identifier (SAI), and M is an integer greater than or equal to 1;

sending a first instruction according to the early warning event information, wherein the first instruction is used for indicating that an early warning event sending mode is a first sending mode, and the first sending mode is sending an event early warning message when the early warning event is changed;

after the sending of the first indication according to the early warning event information, the method further comprises:

and sending a second instruction, wherein the second instruction is used for instructing the start of monitoring the multicast member change in the area range needing to send the early warning event.

2. The event early warning method according to claim 1, wherein the sending a first instruction according to the early warning event information specifically includes:

determining that an early warning event meets an early warning event optimization strategy according to the early warning event information, wherein the early warning event optimization strategy is used for determining a sending mode of the early warning event;

determining that the early warning event sending mode is the first sending mode;

and sending the first indication.

3. The event early warning method as recited in claim 1, wherein after the sending the second indication, the method further comprises:

receiving a group member change message, wherein the group member change message comprises member change area range information and an address of second terminal equipment, and the member change area range information comprises at least one of a first multicast address, a Temporary Mobile Group Identifier (TMGI) and a Service Area Identifier (SAI);

determining an early warning event associated with the member change area range;

and sending an event early warning message related to the early warning event to the second terminal equipment.

4. The event early warning method as recited in claim 1, wherein after the sending the second indication, the method further comprises:

receiving a cancellation event early warning message, wherein the cancellation event early warning message comprises area range information of an early warning event to be cancelled and cancellation early warning event information;

and sending a third instruction, wherein the third instruction is used for instructing to cancel monitoring of multicast member change in the area range needing to send the early warning event.

5. The event alert method according to any one of claims 1 to 4, wherein the area range information of the alert event to be transmitted includes M multicast addresses, and before the receiving the event alert message, the method further comprises:

and adding N multicast groups, wherein N is an integer greater than or equal to 1, and N is greater than or equal to M.

6. An event early warning method is applied to a first terminal device or a chip built in the first terminal device, and comprises the following steps:

receiving a first indication, wherein the first indication is used for indicating that a sending mode of an early warning event is a first sending mode, the first sending mode is used for sending an event early warning message when the early warning event is changed, the event early warning message comprises area range information and early warning event information of the early warning event to be sent, the area range information of the early warning event to be sent comprises M multicast addresses or geographical area range information, the geographical area range information is used for establishing a corresponding relation with a Service Area Identifier (SAI), and M is an integer greater than or equal to 1;

and sending an event early warning message after the early warning event is changed according to the first indication so as to facilitate the server or a chip arranged in the server to send a second indication, wherein the second indication is used for indicating to start monitoring the multicast member change in the area range needing to send the early warning event.

7. The event early warning method as recited in claim 6, wherein prior to the receiving the first indication, the method further comprises:

and sending an event early warning message in a second sending mode, wherein the event early warning message comprises area range information and early warning event information of an early warning event to be sent, and the second sending mode is to periodically send the event early warning message.

8. The event early warning method according to claim 6 or 7, wherein after the receiving the first indication, the method further comprises:

and sending a cancellation event early warning message, wherein the cancellation event early warning message comprises area range information of the early warning event to be cancelled and cancellation early warning event information.

9. An event early warning method is applied to a first terminal device or a chip built in the first terminal device, and comprises the following steps:

determining that the early warning event sending mode is a first sending mode according to the early warning event information, wherein the first sending mode is to send an event early warning message when the early warning event is changed; the event early warning message comprises area range information and early warning event information of an early warning event to be sent, the area range information of the early warning event to be sent comprises M multicast addresses or geographical area range information, the geographical area range information is used for establishing a corresponding relation with a Service Area Identifier (SAI), and M is an integer greater than or equal to 1;

and sending a fourth instruction so that the server or a chip built in the server can send a second instruction, wherein the second instruction is used for instructing to start monitoring multicast member change in an area range needing to send the early warning event, and the fourth instruction is used for instructing the server to forward the event early warning message.

10. The event early warning method according to claim 9, wherein the determining that the early warning event transmission mode is the first transmission mode according to the early warning event information specifically includes:

determining that the early warning event meets an early warning event optimization strategy according to the early warning event information, wherein the early warning event optimization strategy is used for determining a sending mode of the early warning event;

and determining that the early warning event sending mode is the first sending mode.

11. The event alert method according to claim 9 or 10, wherein the fourth indication includes area range information that an alert event needs to be transmitted and the alert event information.

12. The event alert method according to claim 9 or 10, wherein before the determining that the alert event transmission mode is the first transmission mode according to the alert event information, the method further comprises:

and sending an event early warning message in a second sending mode, wherein the event early warning message comprises the area range information of the early warning event to be sent and the early warning event information, the second sending mode is to periodically send the event early warning message, the early warning event information comprises an early warning event identifier, and the fourth indication comprises the early warning event identifier.

13. An event early warning method is characterized by comprising the following steps:

receiving an event early warning message, wherein the event early warning message comprises area range information and early warning event information of an early warning event to be sent, the area range information of the early warning event to be sent comprises M multicast addresses or geographical area range information, the geographical area range information is used for establishing a corresponding relation with a Service Area Identifier (SAI), and M is an integer greater than or equal to 1;

receiving a fourth instruction, wherein the fourth instruction is used for instructing a server to forward an event early warning message; the fourth indication is sent after the first terminal device or a chip built in the first terminal device determines that the sending mode of the early warning event is the first sending mode according to the early warning event information, and the event early warning message is sent when the early warning event is changed;

and sending a second instruction according to the fourth instruction, wherein the second instruction is used for instructing to start monitoring the multicast member change in the area range needing to send the early warning event.

14. The event alert method as claimed in claim 13, wherein the fourth indication includes the area range information of the alert event to be transmitted and alert event information.

15. The event early warning method as recited in claim 13, wherein prior to the receiving the fourth indication, the method further comprises:

the early warning event information comprises an early warning event identifier, and the fourth indication comprises the early warning event identifier.

16. The event early warning method according to any one of claims 13-15, wherein prior to the receiving a fourth indication, the method further comprises:

and sending an early warning event optimization strategy, wherein the early warning event optimization strategy is used for determining an early warning event sending mode, the early warning event sending mode comprises a first sending mode and a second sending mode, the first sending mode is used for sending an event early warning message when the early warning event is changed, and the second sending mode is used for periodically sending the event early warning message.

17. A communications apparatus, comprising: at least one processor, a memory, a bus and a communication interface, wherein the memory is configured to store a computer program such that the computer program, when executed by the at least one processor, implements the event early warning method of any one of claims 1 to 5, or implements the event early warning method of any one of claims 6 to 8, or implements the event early warning method of any one of claims 9 to 12, or implements the event early warning method of any one of claims 13 to 16.

18. A computer readable storage medium comprising computer software instructions which, when run in a computer, cause the computer to perform the event pre-warning method of any one of claims 1 to 5, or to perform the event pre-warning method of any one of claims 6 to 8, or to implement the event pre-warning method of any one of claims 9 to 12, or to implement the event pre-warning method of any one of claims 13 to 16.