Method for subscribing to geo services in MEC architecture

Abstract

To provide a method for subscribing a mobile device to a geo-service.SOLUTION: A method for subscribing a mobile device (ME) to information about events from a geo-service hosted on a peripheral server (SP1) for processing data in a MEC (Mobile EDG Computing) architecture network, comprising sending a registration message (ME11) to a central server (SC), sending a subscription message (ME21) to the peripheral server (SP1) depending on the type of event, and receiving a message (E23).SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates generally to the field of telecommunications, and more particularly to a method for subscribing mobile devices to specific information about their geographical locations in a Mobile Edge Computing (MEC) architecture. [Background technology]

[0002] The MEC architecture, defined in the ETSI GS MEC 003 ("European Telecommunications Standards Institute Group Specification Mobile Edge Computing") specification, allows certain computations performed on mobile devices to be relocated to distributed servers located in a limited geographic zone around the mobile device's location and / or centralized in the MEC architecture. This allows mobile devices, particularly those embedded in connected cars, to take advantage of the vast computing power available on these servers, particularly to display real-time, event-rich, high-definition maps of roads that can be shared among connected cars. These servers also offer services that determine the virtual horizon, also known as the electronic horizon, and notify vehicles of upcoming obstacles or events that are not immediately accessible by the vehicle's built-in sensors. These mapping or electronic horizon services are geoservices, similar to the way the data they process depends on geographic location.

[0003] A mobile device ME of a vehicle wishing to benefit from such a service must first be identified and registered with the central server SC of the MEC architecture network in a first step E1, which corresponds to the sending of a registration message ME1 as shown in Figure 1. Upon receiving this message ME1, the central server SC authenticates the mobile device ME. Once the latter is authenticated, the central server SC confirms that the mobile device ME has the necessary rights to use the requested geo-service and authorizes it to do so.

[0004] In a second step E2, the mobile device ME sets up a communication session with a data processing peripheral server SP that instantiates this geo-service for the geographical zone in which the mobile device ME is located.

[0005] Once the communication session has been established, the mobile device ME sends a message ME3 to the peripheral server SP in step E3 to subscribe to the geoservice. This message ME3 consists of a list of events likely to be of interest in the region of interest ROI (region of interest), which are also indicated in this message ME3. The list of events consists, for example, of values ​​corresponding to traffic accidents and values ​​corresponding to traffic jams. Note that the message ME3 may be a secure http type request.

[0006] In a next step E4, the peripheral server SP sends an acknowledgement message ME4 (here a secure acknowledgement http message) to the mobile device ME.

[0007] When an event occurs that corresponds to the list sent by the mobile device ME in step E3, the peripheral server SP sends a secure message ME5 in step E5 to inform the mobile device ME of this. Summary of the Invention [Problem to be solved by the invention]

[0008] This procedure, which allows a mobile device to subscribe to geo-services, induces costly communications between the mobile device and the peripheral server. In fact, step E2 of the https (hypertext transfer protocol secure) connection involves the exchange of approximately 20 messages, including the opening of a communication session and TLS (transport layer security) negotiation. These communications also use high-quality-of-service (uRLLC) slices to accommodate real-time notifications from the mobile device. These communications are relatively expensive and data-intensive for both the mobile device and the MEC architecture network due to the limited resources of uRLLC, as well as the limited computing resources of the network's peripheral servers. The time used by the peripheral server to initiate geo-service execution is also costly.

[0009] Therefore, when a mobile device is a user of geo-services in an MEC architecture network, there is a need to limit the use of URLC resources and connections on peripheral servers.

[0010] One object of the present invention is to remedy at least some of the drawbacks of the prior art by providing a method for subscribing a mobile device to a geo service and a method for transmitting mobile device information linked to a geo service, in which the mobile device's subscription procedure is limited to cases where the peripheral server instantiating the geo service actually has information to provide to the mobile device. [Means for solving the problem]

[0011] To this end, the invention proposes a method for subscribing a mobile device to information about at least one type of event using a notification service linked to the geography of a location, said notification service being hosted on a data processing peripheral server of an MEC architecture network, said method being executed on said mobile device and comprising the following steps: sending a registration request message to a central server of said network requesting registration; sending a subscription message to a data processing peripheral server requesting subscription to said at least one event; receiving a message providing information about said at least one event to said mobile device (ME); the registration request message indicates the at least one type of event; The step of sending the subscription message is conditioned on the existence of a preceding step of receiving a notification message that the at least one type of event has occurred at the location, and corresponding information is stored in the data processing peripheral server, and the notification message is delivered to the mobile device via a high-speed messaging channel, also called a "paging" channel.

[0012] According to the present invention, the mobile device will initiate a subscription procedure with the data processing peripheral server only if the data processing peripheral server actually has the information to provide the mobile device, i.e., information corresponding to one or less of the event types for which the mobile device previously registered with the central server. Thus, unnecessary transmission of messages corresponding to the subscription procedure is avoided, saving URLLC resources of the MEC architecture and the core network, and reducing the vehicle's electricity consumption.

[0013] According to an advantageous feature of the subscription method according to the invention, the mobile device indicates in the subscription message an area of ​​interest to which the peripheral server must send the information relating to at least one type of said event.

[0014] In this way, even if the vehicle subscribes to certain types of events at the peripheral server, it is possible to reduce the transmission of information that does not correspond to a geographical zone that is purely of interest to the mobile device.

[0015] The mobile device is a communication module of a vehicle and the area of ​​interest corresponds to a route programmed in the vehicle. This use case of the invention is particularly advantageous as the area of ​​interest can be processed dynamically: a central server and peripheral servers can, for example, be coupled to the location service of the vehicle to track its position and dynamically restrict the broadcast zone of notification messages.

[0016] According to another advantageous feature of the subscription method according to the invention, the step of receiving a notification message comprises a sub-step of decoding a data field specific to such an event notification, said specific data field being included in a data field allocated in the core network and present in a "Paging Record" field of said high-speed messaging channel.

[0017] This particular data field is assigned to, for example, all V2X (short for vehicle-to-everything) services and allows specifying a list of types of events to which a vehicle can subscribe.

[0018] The present invention also relates to a method for transmitting information about a type of event to a mobile device by a data processing peripheral server hosting a notification service linked to the geography of a location in an MEC architecture network, said method being executed in said network and comprising the following steps: receiving, by a central server, a registration request message sent from the mobile device, the registration request message including at least an indication of the event type; said central server sending a message indicating at least the type of event to at least one data processing peripheral server of said network hosting said notification service; said at least one data processing peripheral server verifying the existence of an event of said type in its database; If said at least one data processing peripheral server contains an event of said type in its database, sending a message from said at least one data processing peripheral server to at least one base station connected to it for broadcasting a message informing said mobile device of the existence of an event of said type on a high speed messaging channel, called a "paging" channel; receiving, by said at least one peripheral server, a subscription message for said type of event sent from said mobile device; sending, by said at least one data processing peripheral server, a message to said mobile device providing information about said event.

[0019] Advantageously, said subscription message includes a region of interest and said step of sending an informative message is conditional on the fact that said event is related to said region of interest.

[0020] Also advantageously, in the step of sending by the central server a message indicating at least the type of event, the message indicating at least the type of event is sent only to data processing peripheral servers of the network hosting the notification service whose network coverage corresponds to the current or programmed location of the mobile device.

[0021] Advantageously, the at least one peripheral server is characterized in that it transmits, on a high-speed messaging channel, a message to broadcast to the mobile device the message informing the mobile device of the existence of the event only to the base station corresponding to the current or programmed location of the mobile device.

[0022] Also advantageously, said at least one peripheral server transmits said message to said at least one base station only if said event relates to a zone covered by said at least one base station.

[0023] Also advantageously, the step of the at least one peripheral server sending a message informing the mobile device is followed by a step of the at least one peripheral server sending a message to the at least one base station to which it is connected in order to stop broadcasting the notification message on the fast messaging channel when the event becomes obsolescent or when the mobile device leaves the zone served by the at least one information processing peripheral server.

[0024] The method of transmitting information about types of events to a mobile device by a data processing peripheral server according to the invention offers similar advantages as the subscription method according to the invention. [Effects of the Invention]

[0025] [Brief explanation of the drawings]

[0026] [Figure 1] FIG. 1 illustrates the procedure for subscribing a mobile device to an event using prior art geo-services, as described in connection with the prior art. [Figure 2]FIG. 2 illustrates a procedure for subscribing a mobile device to events using geo-services according to the present invention, and a method for transmitting information about these events to a mobile device according to the present invention, in a preferred embodiment of the present invention. [Figure 3] FIG. 3 illustrates the steps of stopping sending notification messages to a mobile device when the corresponding event becomes stale in this preferred embodiment of the present invention. [Figure 4] FIG. 4 represents a step of stopping the sending of notification messages to a mobile device when the mobile device leaves the corresponding coverage zone in a variant embodiment of the method according to the invention. DETAILED DESCRIPTION OF THE INVENTION

[0027] According to a preferred embodiment of the present invention, the mobile device ME subscribes to a location geography linked information notification service, called GeoServices, by the procedure depicted in FIG.

[0028] In a first step E11, a mobile device ME, which is here integrated in a vehicle, sends a registration message ME11 to a central server SC of the MEC architecture network. This message ME11 contains an identifier of the mobile device ME, values ​​of parameters that allow the evaluation of the processing and communication capabilities of the vehicle, an identifier of the geoservice to which the mobile device ME is registered, and one or more values ​​corresponding to the type of event the mobile device wants to be notified about. These events correspond, for example, to works, accidents, slow vehicles, traffic jams, etc. The message ME11 is, for example, based on the https protocol.

[0029] Upon receiving this message ME11, the central server SC authenticates the mobile device ME and then verifies that the mobile device ME has the necessary capabilities to use the requested geo service and authorizes it to be used by the data-processing peripheral server that instantiates it. After step E11, the central server SC sends messages ME12 to the first peripheral server SP1 in step E12 and ME13 to the second peripheral server SP2 in step E13. These servers correspond to the peripheral servers that instantiate the geo service and whose operators have granted the mobile device ME access in accordance with its subscription. Messages ME12 and ME13 are, for example, based on the secure layer HTTPS or MQTT (short for Message Queuing Telemetry Transport) protocols. Alternatively, if the central server SC interfaces with the location service of the mobile device ME, it sends messages immediately after the first step E11 only to the data-processing peripheral server that corresponds to the vehicle's approximate location. Thus, the vehicle can benefit from the geo service even if it is moving within a predefined distance zone.

[0030] Messages ME12 and ME13 each contain an identifier of the mobile device ME and a list of values ​​corresponding to the types of events for which notification is desired. The identifier of the mobile device is derived from its IMEI (International Mobile Equipment Identity) according to the standards of cellular networks. Steps E12 and E13 are followed by steps E14 and E15 respectively, which may for example be performed simultaneously.

[0031] Step E14 consists in the peripheral device SP1 verifying that one or more events of the type included in the list received in step E12 are stored in its database. In this exemplary embodiment of the invention, it is assumed that at least one of these events is stored in the database of the peripheral server SP1, for example an accident in the geographical zone covered by this peripheral server.

[0032] Similarly, step E15 consists in verifying by the peripheral server SP2 that it has stored in its database one or more events of the type included in the list received in step E13. In this exemplary embodiment of the invention, it is assumed that the peripheral server SP2 does not have any corresponding events stored in its database, so it stores the list received in step E13 but does not initiate a notification procedure with the mobile device ME.

[0033] After step E14, the peripheral server SP1 sends a message ME16 to the first base station SB1 in step E16 and a message ME18 to the second base station SB2 in step E18, these messages using, for example, the https protocol.

[0034] These base stations SB1, SB2 correspond to radio transceiver stations to which the peripheral server SP1 is connected. In a variant embodiment, if the peripheral server SP1 is integrated with the location services of the mobile device ME, the peripheral server SP1 will send messages immediately after step E14 only to the base stations that correspond to the vehicle's general position and / or to the base stations that correspond to events whose geographical extent is stored in the peripheral server SP1's database. Thus, the vehicle can benefit from geo-services even if it is moving within a predefined distance zone, and will only be notified of events related to this predefined distance zone.

[0035] Messages ME16 and ME18 each contain an identifier of the mobile device ME and one or more values ​​corresponding to the type of event stored in the database of the peripheral server SP1 and included in the list received in step E12 (here, values ​​corresponding to accidents).

[0036] Upon receiving the message ME16, the base station SB1 sends a notification message ME17 to the mobile device ME in step E17. The transmission of this notification message ME17 uses a fast messaging channel called the "paging" channel. To do this, the base station SB1 adds a specific data field "V2X" called "Paging Record" in the "Paging Record List" to the LTE (short for long term evolution) subfield called "Paging Occasion (PO)" which corresponds to the identifier of the mobile device. The "Paging Record List" is a list of data intended for the mobile devices connected to the base station SB1.

[0037] Next, the data field "Paging Record" consists of the following data fields: "UE-identity" is an encoded value of the mobile equipment ME's identifier. A "cn-domain" that takes one of the following values: "ps" for packet switched, "cs" for circuit switched, or a new value "V2X" used for notification to mobile devices according to the present invention. The selected value "cn-domain" corresponds to a message (incoming data communication, incoming voice communication, or notification message) intended for a mobile device according to the present invention. In this exemplary embodiment of the present invention, the "cn-domain" field takes the value "V2X". Specific Data Field "V2X" The specific data field "V2X" encodes the type of event, which in this exemplary embodiment corresponds to an accident. More generally, the content of this field is a table containing all events that are present in the database of the peripheral server associated to the base station in question and that are of potential interest to the mobile device with identifier "UE-identity", i.e., they form part of the registration message ME11. Thus, if, at the time of the registration message ME11, the vehicle indicated that it is interested in four types of events {accident, animals on the road, construction, traffic jam}, the peripheral server SP1 only has events of type accident in its database, and so the field "V2X" will take the value {accident}.

[0038] The message ME17 corresponding to this particular data field "V2X" is notified to the mobile device ME periodically, which typically wakes up every 1.048 seconds (seconds) to read the "paging occasion" field. This period of 1.048 corresponds to a discontinuous reception cycle called DRX, which allows the mobile device ME not to continuously monopolize radio resources to listen to the "paging" channel when in standby mode. Thus, upon receiving the message ME17 in this step E17, the mobile device ME decodes this particular field "V2X" of the message ME17 sent via the "paging" channel and determines that the geo-service has recorded an "accident" type event that likely corresponds to its region of interest ROI.

[0039] Likewise, upon receipt of message ME18, base station SB2 sends, in step E19, a notification message ME19 to the mobile device ME. The sending of this notification message ME17, which contains the type of event corresponding to the accident and the identifier of the mobile device, uses the "paging" channel, just as in step E17.

[0040] In this exemplary embodiment of the invention, it is assumed that the mobile device ME is located within the coverage of base station SB1 and has therefore received the notification message ME17.

[0041] Then, in the next step E20, a communication session is set up with the data processing peripheral server SP1 in order to recover information about the event of type "accident" that has just been notified. This step E20 is carried out in a similar way to step E2.

[0042] In a next step E21, the mobile device ME sends a subscription message ME21 subscribing to an event of type "accident", said message ME21 containing the identity of the mobile device, a value corresponding to the "accident" type of event and a corresponding region of interest ROI (which in this exemplary embodiment of the invention corresponds to the programmed route of the vehicle).

[0043] It should be noted that this message ME21 does not contain values ​​corresponding to types of events other than "accident", since the mobile device ME has been able to determine through the notification message ME17 that there are no other types of events stored in the database of the peripheral server SP1. Furthermore, the mobile device ME sends a subscription message only to the peripheral server SP1, since this is the one that corresponds to its geographical location.

[0044] If, in the meantime, a new type of event occurs in the database of the server SP1 (for example, an animal on the road is detected), the "V2X" field of the "Paging Record" of the mobile devices ME that are interested in this type of event will be updated, and the mobile devices ME will be notified of this new type of event at the next transmission of a fast message called a paging message. The mobile devices ME will receive a notification on this channel with the "V2X" field set to {accident, animal on the road}. After receiving this notification, the mobile devices can include this new type of event in their next subscription message to the server SP1.

[0045] Upon receiving the message ME21, the peripheral server SP1 sends an acknowledgement message ME22 to the mobile device ME in step E22. The peripheral server SP1 then checks whether the stored event is located within the region of interest ROI of the vehicle, which in this exemplary embodiment is assumed to have occurred within the region of interest ROI of the vehicle.

[0046] The next step E23 is then the sending by the peripheral server SP1 of a message ME23 to the mobile device ME containing information related to the accident, in particular the location of the accident.

[0047] It should be noted that depending on the occurrence of events handled by the geoservice, more or less message exchanges may be required in the MEC architecture network when using the present invention. If the accident did not occur within the vehicle's area of ​​interest, step E23 is not performed and in this case the periphery server does not send the corresponding information to the vehicle. If another type of event occurs within the zone served by the Periphery Server SP1 (for example, construction), the messages ME17 and ME19 contain in the specific data field "V2X" two values ​​corresponding to the types "accident" and "construction". If another event of a type included in the list received in step E13 occurs within the zone served by the peripheral server SP2, the peripheral server SP2 sends a message to the relevant base stations, which notify the mobile device ME of the existence of this other event by means of a "paging" channel. The latter will only receive this notification when it enters the coverage of one of these base stations.

[0048] It should be noted that the order of execution of the steps is different in a variant in which, in the last case, another event occurs in the zone served by the periphery server SP2, the central server SC sends a message containing the event of interest to the mobile device only to the periphery server SP1 serving the zone in which the vehicle is located. In fact, in this version, it is necessary to wait for the vehicle to enter the zone served by the periphery server SP2. To do this, the central server SC, notified by the location-based service of the vehicle's movement, sends a message containing the event of interest to the periphery server SP2, which in turn sends messages to the base stations to which it is connected, and these base stations notify the mobile device ME. If the periphery server SP2 is connected to the location-based service, it preferably sends the message only to the base station in which the mobile device ME is located, in order to further save network and radio resources, and possibly only if this other event is located in the zone covered by this base station.

[0049] 3, the additional steps E30 to E33 are provided in case the peripheral server SP1 does not store in its database the event for which the mobile device ME has requested to receive notification. In an example use case of the invention, it is assumed for example that a vehicle involved in an accident corresponding to the event notified in step E17 has left the road.

[0050] Next, in step E30, the event corresponding to this accident is deleted from the database of the peripheral server SP1.

[0051] In the following steps E32 and E33, the peripheral server SP1 sends messages ME32 and ME33 to the base stations SB2 and SB1, respectively, requesting them to stop inserting "V2X" messages corresponding to "accident" type events into the "paging" channel to the mobile device ME. The base stations SB2 and SB1 then delete this notification request from their databases, thereby freeing up radio and memory resources. It should be noted that the peripheral server does not delete in any way the data linked to the mobile device ME for the geo service, unless the mobile device unsubscribes from this geo service. Thus, if a new event of interest to the mobile device ME occurs, the peripheral server SP1 can resend messages similar to messages ME16 and ME18 to its attached base stations.

[0052] In an alternative embodiment in which the peripheral server SP1 is linked to a location service, the peripheral server SP1 sends a message via a "paging" channel only to the base station under whose coverage the mobile device ME is located, requesting that notifications to the mobile device ME be stopped.

[0053] The mobile device ME is informed of the disappearance of the incident by the absence of the "V2X" data field of the "Paging" channel in the next discontinuous reception cycle DRX. On the other hand, if the next "V2X" data field transmitted by the "Paging" channel contains a new type of event, for example corresponding to the work "work", contained in message ME11, the mobile device ME can renew its subscription request to receive the corresponding information by sending a new message similar to message ME21.

[0054] With reference to FIG. 4, in a variant of this embodiment in which the central server SC interfaces with the location services of the mobile device ME, additional steps E40 to E43 are provided.

[0055] Indeed, in this variant embodiment, in order to save radio resources, the central server SC releases the resources allocated to the mobile device ME in the peripheral server when the mobile device ME leaves the zone provided by this peripheral server. Of course, when the central server SC detects that the mobile device ME has returned to the zone provided by this peripheral server, these resources are reallocated by a message sent from the central server SC to the peripheral server.

[0056] Thus, in step E40, the central server SC detects that the mobile device ME leaves the zone provided by the peripheral server SP1.

[0057] In a next step E41, the central server SC sends a message ME41 to the peripheral server SP1, which message ME41 notifies that the mobile device ME has changed the peripheral server of attachment.

[0058] Upon receiving the message ME41, the peripheral server SP1 sends a message ME42 to the base station SB2 in step E42 and a message ME43 to the base station SB1 in step E43, after which it erases from its memory the data assigned to the mobile device ME relating to geo-services. These messages ME42 and ME43, like the messages ME32 and ME33, request that the mobile device ME be stopped from being notified by the "paging" channel of types of events that are of interest to the mobile device ME. The base stations SB2 and SB1 therefore free up radio and memory resources by erasing this notification request from their databases.

[0059] In a variant embodiment in which the peripheral server SP1 is linked to a location-based service, the peripheral server SP1 sends a message via a "paging" channel requesting the mobile device ME to stop notifications only to the base station under whose coverage the mobile device ME was located.

[0060] It should be noted that in the main variant embodiment, the resources allocated to event notification to the vehicle are deterministically released in the peripheral server and the general base station only upon deregistration of the vehicle from the geo service.

[0061] Furthermore, other variants of the invention are of course conceivable, and sometimes can be combined. For example, in a variant, the central server SC interfaces with the location service of the mobile device ME, but instead of dynamically allocating resources for the mobile device ME in different peripheral servers depending on the mobile device's location, it allocates these resources only once, after a registration message ME11, in all peripheral servers serving the mobile device ME's region of interest, e.g., a programmed route. In this case, the registration message ME11 contains the region of interest ROI of the mobile device ME. In this or another variant, the peripheral server is, for example, interfaced with a highly accurate location service, and can monopolize the mobile device ME's resources for geo-services only in the base station to which the mobile device ME is connected.

[0062] Finally, notification messages using the paging channel can be addressed to a single mobile device or a group of mobile devices (e.g., a group of vehicles subscribed to the same geo service). In this case, the identity associated with and transmitted on the notification channel is a collective identity. In this case, a single registration message is transmitted to a central server, e.g., via a fleet management server, for this group of vehicles.

[0063] (Addendum) (Appendix 1) 1. A method for subscribing a mobile device to information about at least one type of event from a notification service linked to geographical location information, the notification service being hosted on a data processing peripheral server of an MEC architecture network, the method being performed on the mobile device, the method comprising: sending a registration request message to a central server of said network requesting registration; sending a subscription message to a data processing peripheral server requesting subscription to said at least one event; receiving an information grant message that provides information about the at least one event to the mobile device; the registration request message indicates the at least one type of event; The mobile device indicates in the subscription message an area of ​​interest to which the data processing peripheral server should send the information regarding at least one type of the event. (Appendix 2) 10. The method of claim 1, wherein the mobile device is a communication module of a vehicle and the area of ​​interest corresponds to a route programmed in the vehicle. (Appendix 3) 1. A method for subscribing a mobile device to information about at least one type of event from a notification service linked to geographical location information, the notification service being hosted on a data processing peripheral server of an MEC architecture network, the method being performed on the mobile device, the method comprising: sending a registration request message to a central server of said network requesting registration; sending a subscription message to a data processing peripheral server requesting subscription to said at least one event; receiving an information grant message that provides information about the at least one event to the mobile device; the registration request message indicates the at least one type of event; receiving a notification message, the notification message including the sub-step of decoding a data field specific to the event notification; The unique data field is included in a data field allocated to the core network and is present in a "paging record" field of a high-speed messaging channel. (Appendix 4) 1. A method for transmitting information about a type of event to a mobile device by a data processing peripheral server hosting a notification service linked to the geography of a location in a MEC architecture network, the method being executed in the network and comprising: receiving, by a central server, a registration request message sent from the mobile device, the registration request message including at least an indication of the event type; said central server sending an event type message indicating at least the type of the event to at least one data processing peripheral server in said network hosting said notification service; said at least one data processing peripheral server verifying the existence of an event of said type in its database; If said at least one data processing peripheral server contains an event of said type in its database, sending a message from said at least one data processing peripheral server to at least one base station connected to it for broadcasting a notification message on a high speed messaging channel, called a "paging" channel, to said mobile device, informing said mobile device of the existence of an event of said type; receiving, by said at least one peripheral server, a subscription message for said type of event sent from said mobile device; sending, by said at least one data processing peripheral server, to said mobile device an informational message providing information about said event; the subscription message includes an area of ​​interest; A method wherein the step of sending the informational message is conditioned on the event being related to the region of interest. (Appendix 5) 5. The method of claim 4, further comprising transmitting, by the data processing peripheral server, mobile device information relating to an event of a type, A method in which, in the step of transmitting the event type message by the central server, the event type message is transmitted only to data processing peripheral servers of the network that host the notification service whose network coverage corresponds to the current or programmed location of the mobile device. (Appendix 6) 6. The method of claim 5, further comprising transmitting, by the data processing peripheral server, information about the type of event to the mobile device, The method wherein the at least one data processing peripheral server transmits a message (ME16) for broadcasting the notification message to the mobile device on a high-speed messaging channel only to a base station corresponding to the current location or a programmed location of the mobile device. (Appendix 7) 7. The method of claim 6, further comprising transmitting, by the data processing peripheral server, information about the type of event to the mobile device, The method, wherein said at least one data processing peripheral server transmits said message to said at least one base station only if said event relates to a zone covered by said at least one base station. (Appendix 8) The method according to any one of (Appendix 4 to 7), wherein the data processing peripheral server transmits information about the type of event to the mobile device. The method further comprises, following the step of sending by the data processing peripheral server a message informing the mobile device, sending by the at least one data processing peripheral server a message to the at least one base station to stop broadcasting the notification message on a fast messaging channel when the event becomes obsolete or when the mobile device leaves a zone served by the at least one data processing peripheral server. (Appendix 9) 10. The method of claim 1 or 4, wherein the region of interest includes the location of the vehicle. (Appendix 10) The method according to claim 1 or 3, wherein the step of sending the subscription message is conditioned on the existence of a preceding step of receiving a notification message that at least one type of event has occurred at the location, and corresponding information is stored in the data processing peripheral server, and the notification message is delivered to the mobile device via a high-speed messaging channel, called a "paging" channel.

Claims

1. 1. A method executed by a data processing peripheral server for providing services hosted on at least one data processing peripheral server in a MEC architecture network to a mobile device, the method comprising: The data processing peripheral server establishing a communications session with the mobile device; receiving a subscription message from the mobile device requesting subscription to at least one event; A method in which said subscription message indicates an area of ​​interest to which said data processing peripheral server should send information about at least one type of said event.

2. 1. A method executed on a mobile device for providing to the mobile device services hosted on at least one data processing peripheral server in a MEC architecture network, the method comprising: The mobile device establish a communication session with the data processing peripheral server; Send a subscription message requesting subscription to at least one event. A method in which said subscription message indicates an area of ​​interest to which said data processing peripheral server should send information about at least one type of said event.

3. 1. A method performed in a system including a mobile device, a data peripheral processing server, and a central server for subscribing the mobile device to a service hosted on at least one data processing peripheral server in a MEC architecture network, the method comprising: The data processing peripheral server establishing a communications session with the mobile device; receiving a subscription message from the mobile device requesting subscription to at least one event; A method in which said subscription message indicates an area of ​​interest to which said data processing peripheral server should send information about at least one type of said event.

4. The method according to any one of claims 1 to 3, wherein the data processing peripheral server sends an acknowledgement message upon receiving a join message.

5. determining whether the event stored by the data processing peripheral server is within a region of interest of the vehicle; A method according to any one of claims 1 to 4, wherein the region of interest is defined corresponding to a programmed route of the vehicle.

6. The method according to any one of claims 1 to 5, wherein the data processing peripheral server does not send information if the event did not occur within a region of interest.

7. When a vehicle related to the notified event has left, the data processing peripheral server The method according to any one of claims 1 to 6, wherein the mobile device is notified of the disappearance of an event.

8. The method of any one of claims 1 to 7, wherein data linked to the mobile device is not erased if the mobile device does not unsubscribe from the service.

9. sending a message including a second type of event to the central server after the mobile device has sent the message including the first type of event; The method of any one of claims 1 to 8, wherein the central server updates the subscription message.

10. A method according to any one of claims 1 to 9, wherein a central server releases resources allocated to said mobile device in said data processing peripheral server when it detects that said mobile device has left a zone.

11. A method according to any one of claims 1 to 10, wherein a central server reallocates resources when it detects that the mobile device has returned to a zone.

12. a central server detects that the mobile device has left a zone, and the central server sends a message to the data processing peripheral server; The method according to any one of claims 1 to 11, wherein, upon receiving the message, the data processing peripheral server erases the data after sending the message.

13. The data processing peripheral server corresponding to the location of the mobile device; The method according to any one of claims 1 to 12, wherein the information is extracted based on a registration request message sent by the mobile device requesting registration before the communication session is set up.

Images