|
(11) | EP 3 860 171 B1 |
| (12) | EUROPEAN PATENT SPECIFICATION |
|
|
| (54) |
CONFIGURATION PARAMETER UPDATE METHOD AND APPARATUS VERFAHREN UND VORRICHTUNG ZUR AKTUALISIERUNG VON KONFIGURATIONSPARAMETERN PROCÉDÉ ET APPAREIL DE MISE À JOUR DE PARAMÈTRES DE CONFIGURATION |
|
|
|||||||||||||||||||||||||||||||
| Note: Within nine months from the publication of the mention of the grant of the European patent, any person may give notice to the European Patent Office of opposition to the European patent granted. Notice of opposition shall be filed in a written reasoned statement. It shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention). |
TECHNICAL FIELD
[0001] This application relates to the field of communications technologies, and in particular, to a configuration parameter update method and apparatus.
BACKGROUND
[0002] A vehicle-to-everything (vehicle to X, V2X) is a key technology of an intelligent transportation system. The V2X includes vehicle to vehicle (vehicle to vehicle, V2V), vehicle to infrastructure (vehicle to infrastructure, V2I), vehicle to network (vehicle to network, V2N), and vehicle to pedestrian (vehicle to pedestrian, V2P). A series of traffic information such as a real-time road condition, road information, and pedestrian information may be obtained through communication between V2Xs, to improve road safety and traffic efficiency, and provide rich streaming media services for a user.
[0003] Generally, the V2Xs communicate with each other through a proximity communication five (proximity communication five, PCS) interface. For example, in a V2V scenario, vehicles communicate with each other through the PC5. The PC5 communication supports two communication modes: a mode 3 and a mode 4. The mode 3 is a base station scheduling mode. Abase station schedules a PC5 communication resource, and allocates the PC5 communication resource to a terminal device. The mode 4 is an autonomous selection mode. A resource pool is pre-configured for a terminal device, and the terminal device obtains a PC5 communication resource from a PC5 communication resource pool by using a competitive mechanism. In the mode 4, PC5 communication resource pools are divided in different regions, in other words, users in a same region share a same PC5 communication resource pool, and each PC5 communication resource pool corresponds to a region identifier.
[0004] In an actual application, a PC5 configuration parameter needs to be configured for the base station in the mode 3 and the terminal device in the mode 4. The PC5 configuration parameter includes a PC5 communication resource pool, a resource selection policy, and the like. In the mode 3, the base station may allocate the PC5 communication resource to the terminal device based on the configured PC5 configuration parameter. In the mode 4, the terminal device may compete for the PC5 communication resource based on the configured PC5 configuration parameter.
[0005] In the prior art, a vehicle-to-everything application server (V2X application server, V2X AS) usually generates the PC5 configuration parameter, and then delivers the PC5 configuration parameter to the base station or the terminal device for configuration. To ensure quality of communication between terminal devices in the V2X, the V2X AS needs to update the PC5 configuration parameter in time, to adjust the PC5 communication resource pool. However, it is found in practice that currently, the V2X AS cannot update the PC5 configuration parameter in time. Therefore, how to update the PC5 configuration parameter in time is an urgent problem to be resolved at present. Further, WO 2017/133769 A1 refers to a network apparatus, such as a road side unit, measuring signalling transmitted from vehicle devices, to obtain the status of road traffic in the proximity of the road side unit. If a pre-defined triggering event is detected in the status of the road traffic in the proximity of the road side unit, the road side unit transmits to a serving network node, a status report in order to report the obtained road traffic status to the serving network node. The road side unit receives, from the serving network node, control signalling indicating at least one road side unit operation mode selected for communication, and sets the operation mode of the road side unit to correspond to the at least one selected road side unit operation mode for the communication.
SUMMARY
[0006] Embodiments of this application provide a configuration parameter update method and apparatus, to help update a PC5 configuration parameter in time. This problem is solved by the subject matter of the independent claims. Further implementation forms are provided in the dependent claims.
BRIEF DESCRIPTION OF DRAWINGS
[0007]
FIG. 1 and FIG. 2 are schematic diagrams of a communications system according to an embodiment of this application;
FIG. 3 to FIG. 7 are schematic flowcharts of a configuration parameter update method according to an embodiment of this application; and
FIG. 8 and FIG. 9 are schematic structural diagrams of a configuration parameter update apparatus according to an embodiment of this application.
DESCRIPTION OF EMBODIMENTS
[0008] The following further describes specific embodiments of this application in detail with reference to accompanying drawings.
[0009] In an existing actual application, a vehicle-to-everything application server (V2X application server, V2X AS) usually generates a PC5 configuration parameter, and then delivers the PC5 configuration parameter to a base station or a terminal device for parameter configuration. To ensure quality of communication between terminal devices in a V2X, the V2X AS needs to update the PC5 configuration parameter in time, to adjust a PC5 communication resource pool. However, it is found in practice that currently, the V2X AS cannot update the PC5 configuration parameter in time. To update the PC5 configuration parameter in time, the embodiments of this application provide a configuration parameter update method and apparatus.
[0010] To better understand the embodiments of this application, the following describes a system architecture to which the embodiments of this application are applicable.
[0011] FIG. 1 and FIG. 2 are schematic diagrams of system architectures according to an embodiment of this application. A system architecture shown in FIG. 1 includes a first device, a second device, and a plurality of terminal devices. Optionally, the first device may be one of a V2X AS, a vehicle-to-everything service control function (V2X control function, V2X CF), and an access network device. The access network device may be a base station or another access network device. Optionally, the second device may be a home platform or a traffic management platform of the terminal device. Optionally, as shown in FIG. 2, the second device may also be the terminal device. The home platform of the terminal device may be a platform that can register a service for the terminal device and deregister a service for the terminal device, for example, an automotive enterprise platform. The traffic management platform is a platform that can detect a service volume impact event. For example, the service volume impact event may be a traffic control event, a road construction event, or the like. The terminal device may include one or more of a vehicle, a mobile phone, a tablet computer, a roadside unit, and the like. The roadside unit is a roadside device that has a communication capability and that is installed on a roadside.
[0012] The first device may update a PC5 configuration parameter. The PC5 configuration parameter includes a PC5 communication resource pool. The PC5 communication resource pool corresponds to an area. The PC5 communication resource pool includes a PC5 communication resource. The PC5 communication resource is used for communication between terminal devices in a V2X through PC5. Optionally, when the first device is the V2X AS or the V2X CF, after the first device updates the PC5 configuration parameter, in other words, after the first device generates a new PC5 configuration parameter, the first device delivers the new PC5 configuration parameter to the access network device or the terminal device to perform configuration update. When the first device is the access network device, the first device may perform a configuration update on a PC5 configuration parameter of the first device. Alternatively, after the first device generates a new PC5 configuration parameter, the first device may deliver the new PC5 configuration parameter to the terminal device to perform a configuration update.
[0013] The following further describes a configuration parameter update method and a related device that are provided in this application.
[0014] FIG. 3 is a schematic diagram of a configuration parameter update method according to an embodiment of this application. As shown in FIG. 3, the configuration parameter update method includes the following steps 301 to 304.
[0016] The first monitoring request is used to request the second device to monitor a target event, and the target event includes one or more of a service change event, a service volume impact event, and a service volume change event.
[0017] The service change event is an event in which a service of a terminal device is changed. The service change of the terminal device includes service registration and service deregistration of the terminal device. For example, if the terminal device deregisters a warning service or the terminal device adds a map download service, the service change event occurs. Therefore, the service change event may include a service registration event and/or a service deregistration event.
[0018] The service volume impact event is an event in which a service volume is affected. The service volume is a quantity of messages that are sent through a PC5 in a unit time. For example, the event in which the service volume is affected may be a traffic control event and/or a road construction event.
[0019] The service volume change event is an event in which the service volume is greater than a first threshold or the service volume is less than a second threshold. The first threshold is greater than the second threshold. Therefore, the service volume change event may include a service volume overload event and/or a service volume release event. The service volume overload event is an event in which the service volume is greater than the first threshold, and the service volume release event is an event in which the service volume is less than the second threshold.
[0020] Optionally, before the step 301, the first device has performed initial configuration on a PC5 configuration parameter of an access network device in a mode 3 or a terminal device in a mode 4. Steps 301 to 304 are a process of updating the PC5 configuration parameter of the access network device or the terminal device. The mode 3 is a scheduling mode of the access network device. The access network device schedules a PC5 communication resource, and allocates the PC5 communication resource to the terminal device. The mode 4 is an autonomous selection mode. APC5 communication resource pool is preconfigured for the terminal device, and the terminal device obtains the PC5 communication resource from the PC5 communication resource pool through a competitive mechanism.
[0022] In this embodiment of this application, after receiving the first monitoring request, the second device monitors the target event.
[0023] In an optional implementation, the first monitoring request carries one or more of a type of terminal that needs to be monitored, an area that needs to be monitored, the first threshold, the second threshold, a service volume statistics period, and a reporting condition of the first information. If the first monitoring request carries the type of terminal that needs to be monitored, the second device monitors only a terminal device of the type of terminal that needs to be monitored. If the first monitoring request carries the area that needs to be monitored, the second device monitors only the area that needs to be monitored. If the first monitoring request carries a service volume statistics period, the second device collects statistics on a service volume based on the service volume statistics period. If the first monitoring request carries the reporting condition of the first information, after monitoring the target event, the second device reports the first information to the first device only when the reporting condition is met. Based on this implementation, the first device can specify, for the second device, the type of terminal that needs to be monitored, the area that needs to be monitored, the first threshold, the second threshold, the service volume statistics period, and the reporting condition of the first information. Optionally, the type of terminal that needs to be monitored, the area that needs to be monitored, the first threshold, the second threshold, the service volume statistics period, and the reporting condition of the first information may also be preset on the second device, or may be obtained by the second device in another manner. This is not limited in this embodiment of this application.
[0024] Optionally, the first monitoring request further carries an identifier of the target event, to indicate the target event that is requested to be monitored. For example, the first monitoring request may carry an identifier of the service registration event and an identifier of the service deregistration event, to request to monitor the service registration event and the service deregistration event. After receiving the first monitoring request, the second device monitors the service registration event and the service deregistration event. Alternatively, the first monitoring request may not carry the identifier of the target event. This is not limited in this embodiment of this application.
[0025] 303: After monitoring the target event, the second device reports the first information of the target event to the first device.
[0026] The first information includes one or more of service change information, service volume impact information, and service volume change information. For example, if the service change event is monitored, the first information includes the service change information. If the service volume impact event is monitored, the first information includes the service volume impact information. If the service volume change event is monitored, the first information includes the service volume change information.
[0027] 304: The first device updates the PC5 configuration parameter based on the first information.
[0028] In this embodiment of this application, after receiving the first information reported by the second device, the first device updates the PC5 configuration parameter based on the first information. Specifically, the first device may determine, based on the first information, a PC5 communication resource required in the area, and further update, based on the PC5 communication resource required in the area, the PC5 communication resource pool that corresponds to the area and that is in the PC5 configuration parameter. Optionally, in addition to updating, based on the PC5 communication resource required in the area, the PC5 communication resource pool that corresponds to the area and that is in the PC5 configuration parameter, the first device may further update a PC5 communication resource pool that corresponds to an adjacent area of the area. For example, the area is an area 2, and an area 1 and an area 3 are adjacent areas of the area 2. When the PC5 communication resource in the area 2 need to be added, if PC5 communication resources in the area 1 and the area 3 are sufficient, a part of the PC5 communication resources in the area 1 and the area 3 may be appropriately reduced, and the reduced PC5 communication resources are added to the PC5 communication resource pool in the area 2. Alternatively, when the PC5 communication resource in the area 2 need to be reduced, if PC5 communication resources in the area 1 and the area 3 are relatively few, the PC5 communication resource in the area 2 may be reduced, the reduced PC5 communication resource is added to PC5 communication resource pools in the area 1 and the area 3. Optionally, updating the PC5 communication resource pool may include adjusting a subframe (subframe) division rule, a quantity of subframes, a quantity of subchannels (subchannel), a start subchannel, or the like, to add or reduce the PC5 communication resource.
[0029] When the first device is the V2X AS or the V2X CF, after updating the PC5 configuration parameter based on the first information, the first device delivers a new PC5 configuration parameter to the access network device or the terminal device to perform a configuration update. When the first device is the access network device, the first device may perform a configuration update on a PC5 configuration parameter of the first device based on the first information. Alternatively, after updating the PC5 configuration parameter based on the first information, the first device may deliver a new PC5 configuration parameter to the terminal device to perform configuration update.
[0030] It can be learned that according to the method described in FIG. 3, the first device can receive the first information in time, and further update the PC5 configuration parameter in time based on the first information.
[0031] FIG. 4 is a schematic diagram of another configuration parameter update method according to an embodiment of this application. FIG. 4 shows an example of monitoring a service change event. In the method shown in FIG. 4, a second device may be a home platform or a terminal device, or another device that can monitor the service change event. As shown in FIG. 4, the configuration parameter update method includes the following steps 401 to 407. The steps 404 to 407 are a specific implementation of the step 304.
[0033] The first monitoring request is used to request the second device to monitor a service change event. The service change event includes a service registration event and/or a service deregistration event. The first device may request the second device to monitor only the service registration event, or monitor only the service deregistration event. Alternatively, the first device may request the second device to monitor the service registration event and the service deregistration event.
[0035] In this embodiment of this application, after receiving the first monitoring request, the second device monitors the service change event.
[0036] Optionally, the first monitoring request may carry an identifier of the service change event, to indicate the service change event that is requested to be monitored. For example, the first monitoring request may carry an identifier of the service registration event and an identifier of the service deregistration event, to request to monitor the service registration event and the service deregistration event. After receiving the first monitoring request, the second device monitors the service registration event and the service deregistration event. Alternatively, the first monitoring request may not carry the identifier of the service change event. This is not limited in this embodiment of this application.
[0037] Optionally, the first monitoring request may carry one or more of a type of terminal that needs to be monitored and an area that needs to be monitored. If the first monitoring request carries the type of terminal that needs to be monitored, the second device monitors only whether the service change event occurs on the terminal device of the type of terminal that needs to be monitored. If the first monitoring request carries the area that needs to be monitored, the second device monitors only whether the service change event occurs in the area that needs to be monitored. For example, if the type of terminal that needs to be monitored and that is carried in the first monitoring request is a vehicle, and if the area that needs to be monitored is the area 1, the second device may monitor only whether the service change event occurs on the vehicle in the area 1. Optionally, the type of terminal that needs to be monitored and the area that needs to be monitored may also be preset on the second device.
[0038] 403: After monitoring the service change event, the second device reports first information of the service change event to the first device.
[0039] Specifically, when the second device is the home platform, the second device may receive a service registration request sent by the terminal device. The service registration request may carry an identifier of a registered terminal device and a registered service, and the service registration request may further carry an area in which the registered service is used. After the second device registers the service for the terminal device, the second device determines that the service registration event is monitored. After determining that the service registration event is monitored, the second device sends the first information of the service registration event to the first device. The second device may also receive a service deregistration request sent by the terminal device. The service deregistration request may carry an identifier of a deregistered terminal and a deregistered service, and the service deregistration request may further carry an area in which the deregistered service is used. After the second device deregisters the service for the terminal device, the second device determines that the service deregistration event is monitored. After determining that the service deregistration event is monitored, the second device sends first information of the service deregistration event to the first device.
[0040] When the second device is the terminal device, after the terminal device successfully registers with the service, the terminal device determines that the service registration event is monitored, and the terminal device sends the first information of the service registration event to the first device. After the terminal device successfully deregisters the service, the terminal device determines that the service deregistration event is monitored, and the terminal sends the first information of the service deregistration event to the first device.
[0041] The first information includes service change information. The service change information includes a changed service and an identifier of a first area, and the first area is an area in which the changed service is used. Optionally, the service change information may further carry an identifier of the monitored service change event, to indicate the monitored service change event.
[0042] For example, the second device receives a service registration request sent by the terminal device. The service registration request carries an identifier of a terminal device 1 that registers a service, a registered service 1, and an area in which the service 1 is used. After registering the service 1 for the terminal device 1, the second device determines that the service registration event is monitored. The second device sends first information of the service registration event to the first device. The first information carries the identifier of the service registration event, the registered service 1, and an identifier of the area in which the service 1 is used. The second device monitors the service deregistration event in a similar way. Details are not described herein again.
[0043] 404: The first device determines, based on the changed service, a target service used in the first area.
[0045] In this embodiment of this application, after receiving the first information, the first device determines, based on the changed service in the first information, the target service used in the first area, and determines the quantity of terminals that have the target service.
[0046] 406: The first device determines, based on the target service and the quantity of terminals, a PC5 communication resource required in the first area.
[0047] 407: The first device updates, based on the PC5 communication resource required in the first area, a PC5 communication resource pool that corresponds to the first area and that is in the PC5 configuration parameter.
[0048] For example, the first device may record, based on first information received within a time period, service distribution statuses in a plurality of areas and a quantity of terminals that have each service. As shown in the following Table 1, the area 1 includes the service 1, and a quantity of terminal devices that have the service 1 is 1000. An area 2 includes a service 2, and a quantity of terminal devices that have the service 2 is 500. An area 3 includes a service 3, and a quantity of terminal devices that have the service 3 is 200.
| Area | Service in an area | Quantity of terminal devices that have a corresponding service |
| Area 1 | Service 1 | 1000 |
| Area 2 | Service 2 | 500 |
| Area 3 | Service 3 | 200 |
[0049] If the first device receives first information reported by the second device, and the first information carries a registered service 4 and an identifier of the area 1, as shown in Table 2, the first device may determine that target services used in the area 1 include the service 1 and the service 4, the quantity of terminals that have the service 1 is 1000, and the quantity of terminals that have the service 4 is 1. The first device may determine, based on the services in the area 1 and the quantity of terminals corresponding to each service in the area 1, a PC5 communication resource required in the area 1. For example, because the service 1 and the service 4 are services that need to consume a relatively large quantity of PC5 communication resources, and the quantity of terminal devices that have the service 1 is relatively large, the area 1 needs a relatively large quantity of PC5 communication resources. Therefore, PC5 communication resources in a resource pool that corresponds to the area 1 and that is in the PC5 configuration parameter may be added based on the PC5 communication resources required in the area 1.
| Area | Service in an area | Quantity of terminal devices that have a corresponding service |
| Area 1 | Service 1 | 1000 |
| Area 1 | Service 4 | 1 |
| Area 2 | Service 2 | 500 |
| Area 3 | Service 3 | 200 |
[0050] If the first device receives first information reported by the second device, and the first information carries the deregistered service 3 and an identifier of the area 3, as shown in Table 3, the first device may determine that a target service used in the area 3 includes the service 3, and a quantity of terminals that have the service 3 is 199. The first device may determine, based on the service in the area 3 and the quantity of terminals corresponding to each service in the area 3, a PC5 communication resource required in the area 3. For example, because the service 3 is a service that needs to consume a relatively small quantity of PC5 communication resources, and the quantity of terminal devices that have the service 3 is relatively small, the area 3 needs a relatively small quantity of PC5 communication resources. Therefore, PC5 communication resources in a resource pool that corresponds to the area 3 and that is in the PC5 configuration parameter may be reduced based on the PC5 communication resources required in the area 3.
| Area | Service in an area | Quantity of terminal devices that have a corresponding service |
| Area 1 | Service 1 | 1000 |
| Area 1 | Service 4 | 1 |
| Area 2 | Service 2 | 500 |
| Area 3 | Service 3 | 199 |
[0051] As an optional implementation, the service change information further includes an identifier of a terminal of a changed service. A specific implementation of that the first device determines the quantity of terminals that have the target service includes: determining, based on the identifier of the terminal of the changed service, the quantity of terminals that have the target service. In this implementation, the first device does not need to directly record the quantity of terminal devices that have the corresponding service, as shown in Table 1 to Table 3. The first device may record an identifier of the terminal device that has the corresponding service, and further determine, based on the identifier of the terminal device, the quantity of terminal devices that have the corresponding service. Based on this implementation, the first device can accurately determine the quantity of terminals that have the target service.
[0052] As shown in Table 4, the first device may determine, based on an identifier of the terminal device that has the service 1, that the quantity of terminal devices that have the service 1 is 1000. The first device may determine, based on an identifier of the terminal device that has the service 2, that the quantity of terminal devices that have the service 2 is 500. The first device may determine, based on an identifier of the terminal device that has the service 3, that the quantity of terminal devices that have the service 3 is 200.
| Area | Service in an area | Identifiers of terminal devices that have a corresponding service |
| Area 1 | Service 1 | Identifier of a terminal device 1 to an identifier of a terminal device 1000 |
| Area 2 | Service 2 | Identifier of a terminal device 1 to an identifier of a terminal device 500 |
| Area 3 | Service 3 | Identifier of a terminal device 1 to an identifier of a terminal device 200 |
[0053] If the first device receives first information reported by the second device, and the first information carries the registered service 4, the identifier of the area 1, and the identifier of the terminal device 1, the first device may record information shown in the following Table 5. Therefore, the first device may determine that target services used in the area 1 include the service 1 and the service 4, the quantity of terminals that have the service 1 is 1000, and the quantity of terminals that have the service 4 is 1. The first device determines, based on the services in the area 1 and the quantity of terminals corresponding to each service in the area 1, a PC5 communication resource required in the area 1. For example, because the service 1 and the service 4 are services that need to consume a relatively large quantity of PC5 communication resources, and the quantity of terminal devices that have the service 1 is relatively large, the area 1 needs a relatively large quantity of PC5 communication resources. Therefore, PC5 communication resources in a resource pool that corresponds to the area 1 and that is in the PC5 configuration parameter may be added based on the PC5 communication resources required in the area 1. The second device monitors the service deregistration event in a similar way. Details are not described herein again.
| Area | Service in an area | Identifiers of terminal devices that have a corresponding service |
| Area 1 | Service 1 | Identifier of a terminal device 1 to an identifier of a terminal device 1000 |
| Area 1 | Service 4 | Identifier of a terminal device 1 |
| Area 2 | Service 2 | Identifier of a terminal device 1 to an identifier of a terminal device 500 |
| Area 3 | Service 3 | Identifier of a terminal device 1 to an identifier of a terminal device 200 |
[0054] Optionally, if the service registration event is monitored, the first device further needs to update, in the PC5 configuration parameter, one or more of a destination layer-2 address corresponding to the registered service, a privacy update time point corresponding to the registered service, spectrum information corresponding to the registered service, and the like.
[0055] Optionally, in addition to updating, based on the PC5 communication resource required in the first area, the PC5 communication resource pool that corresponds to the first area and that is in the PC5 configuration parameter, the first device may further update a PC5 communication resource pool that corresponds to an adjacent area of the first area. For a specific implementation principle, refer to the corresponding description in the 304 in the foregoing embodiment. Details are not described herein again.
[0056] It can be learned that by implementing the method described in FIG. 4, the first device can accurately determine the PC5 communication resource required in the first area, and the first device can properly update the PC5 configuration parameter in time based on the PC5 communication resource required in the first area.
[0057] FIG. 5 is a schematic diagram of another configuration parameter update method according to an embodiment of this application. FIG. 5 shows an example in which a service volume impact event is monitored. In the method shown in FIG. 5, a second device may be a traffic management platform or another device that can monitor the service volume impact event. As shown in FIG. 5, the configuration parameter update method includes the following steps 501 to 505. Steps 505 and 505 are another specific implementation of the step 304.
[0059] The first monitoring request is used to request the second device to monitor the service volume impact event. The service volume impact event is an event in which a service volume is affected. The service volume is a quantity of messages that are sent through a PC5 in a unit time. For example, the event in which the service volume is affected may be a traffic control event and/or a road construction event.
[0061] In this embodiment of this application, after receiving the first monitoring request, the second device monitors the service volume impact event.
[0062] Optionally, the first monitoring request may carry an identifier of the service volume impact event, to indicate the service volume impact event that is requested to be monitored. For example, the first monitoring request may carry an identifier of the traffic control event and an identifier of the road construction event, to request to monitor the traffic control event and the road construction event. After receiving the first monitoring request, the second device monitors the traffic control event and the road construction event. Alternatively, the first monitoring request may not carry the identifier of the service volume impact event. This is not limited in this embodiment of this application.
[0063] Optionally, the first monitoring request may further carry an area that needs to be monitored. In this way, the second device may monitor only whether the service volume impact event occurs in the area that needs to be monitored. For example, if the area that needs to be monitored is an area 1, the second device may monitor only whether the service volume impact event occurs in the area 1. Optionally, the area that needs to be monitored may also be preset on the second device.
[0064] 503: After monitoring the service volume impact event, the second device reports first information of the service volume impact event to the first device.
[0065] The first information includes service volume impact information. The service volume impact information includes the monitored service volume impact event and an identifier of a first area, and the first area is an area affected by the service volume impact event. That the service volume impact information includes the monitored service volume impact event may be specifically the following: The service volume impact information may include an identifier of the monitored service volume impact event.
[0066] For example, the second device monitors the road construction event. The second device sends, to the first device, first information used to indicate that the road construction event is monitored. The first information carries an identifier of the road construction event and an identifier of the area 1 affected by the road construction event.
[0067] 504: The first device determines, based on the monitored service volume impact event, a PC5 communication resource required in the first area.
[0068] 505: The first device updates, based on the PC5 communication resource required in the first area, a PC5 communication resource pool that corresponds to the first area and that is in a PC5 configuration parameter.
[0069] For example, the second device monitors the road construction event, and the second device sends service volume impact information of the road construction event to the first device. The service volume impact information carries the identifier of the road construction event and the identifier of the area 1 affected by the road construction event. Because the road construction event affects vehicle traffic, a service volume in the area 1 is reduced. Therefore, a PC5 communication resource required in the area 1 is reduced. The first device may reduce, based on the PC5 communication resource required in the first area, a PC5 communication resource in the PC5 communication resource pool that corresponds to the first area and that is in the PC5 configuration parameter.
[0070] Optionally, in addition to updating, based on the PC5 communication resource required in the first area, the PC5 communication resource pool that corresponds to the first area and that is in the PC5 configuration parameter, the first device may further update a PC5 communication resource pool that corresponds to an adjacent area of the first area. For a specific implementation principle, refer to the corresponding description in the 304 in the foregoing embodiment. Details are not described herein again.
[0071] As an optional implementation, the service volume impact information further includes a first time period, and the first time period is a time period the service volume impact event lasts. After that the first device updates, based on the PC5 communication resource required in the first area, the PC5 communication resource pool that corresponds to the first area and that is in the PC5 configuration parameter, the first device restores, based on the first time period, the PC5 communication resource pool corresponding to the first area to a resource pool used before the updating. Based on this implementation, the first device can properly restore the PC5 configuration parameter in time.
[0072] For example, the first device receives first information. The first information carries the identifier of the road construction event, the identifier of the area 1 affected by the road construction event, and the first time period from 8:00 to 9:00. After receiving the first information, the first device determines, based on the road construction event, a PC5 communication resource required in the first area, and updates, based on the PC5 communication resource required in the first area, a PC5 communication resource pool 1 corresponding to the area 1, to obtain a PC5 communication resource pool 2. A PC5 communication resource in the PC5 communication resource pool 2 is less than a PC5 communication resource in the PC5 communication resource pool 1. After 9:00, in other words, after the first time period ends, the first device restores the PC5 communication resource pool corresponding to the area 1 to the PC5 communication resource pool 1.
[0073] It can be learned that by implementing the method described in FIG. 5, the first device can accurately determine the PC5 communication resource required in the first area, and the first device can properly update the PC5 configuration parameter in time based on the PC5 communication resource required in the first area.
[0074] FIG. 6 is a schematic diagram of another configuration parameter update method according to an embodiment of this application. FIG. 6 shows an example in which a service volume change event is monitored. In the method shown in FIG. 6, the second device may be another device that can monitor a service volume, such as a home platform or a roadside unit. As shown in FIG. 6, the configuration parameter update method includes the following steps 601 to 605. Steps 604 and 605 are a specific implementation of the step 304.
[0076] The first monitoring request is used to request the second device to monitor a service change event. The service volume change event is an event in which the service volume is greater than a first threshold or the service volume is less than a second threshold. The first threshold is greater than the second threshold. Therefore, the service volume change event may include a service volume overload event and/or a service volume release event. The service volume overload event is an event in which the service volume is greater than the first threshold, and the service volume release event is an event in which the service volume is less than the second threshold.
[0078] In this embodiment of this application, after receiving the first monitoring request, the second device monitors the service change event.
[0079] Optionally, the first monitoring request may carry an identifier of the service change event, to indicate the service change event that is requested to be monitored. For example, the first monitoring request may carry an identifier of a service volume overload event and an identifier of a service volume release event, to request to monitor the service volume overload event and the service volume release event. After receiving the first monitoring request, the second device monitors the service volume overload event and the service volume release event. Alternatively, the first monitoring request may not carry the identifier of the service volume change event. This is not limited in this embodiment of this application.
[0080] Optionally, the first monitoring request may further carry one or more of an area that needs to be monitored, the first threshold, the second threshold, a type of terminal that needs to be monitored, a service volume statistics period, and a reporting condition of first information. Optionally, the reporting condition of the first information may be that the service volume overload event is detected for a preset quantity of consecutive times or the service volume release event is detected for a preset quantity of consecutive times. Alternatively, the reporting condition of the first information may be that the service volume overload event is detected for a preset quantity of times within a preset time period, or the service volume release event is detected for a preset quantity of times within a preset time period.
[0081] For example, the first monitoring request carries the type of terminal that needs to be monitored, the area that needs to be monitored, the first threshold, the second threshold, the service volume statistics period, and the reporting condition of the first information. The type of terminal that needs to be monitored is a vehicle, the area that needs to be monitored is an area 1, the service volume statistics period is 10 minutes, and the reporting condition of the first information is that the service volume overload event is detected for three consecutive times or the service volume release event is detected for three consecutive times. After the second device receives the first monitoring request, the second device collects statistics on a service volume of a vehicle in the area 1 at an interval of 10 minutes, and reports the first information to the first device when the second device detects the service volume overload event for three consecutive times or detects the service volume release event for three consecutive times.
[0082] 603: After monitoring the service volume change event, the second device reports first information of the service change event to the first device.
[0083] The first information includes service volume change information. The service volume change information includes a changed service volume and an identifier of a first area. The first area is an area in which the service volume is changed. Optionally, the service volume change information may further include an identifier of the monitored service volume change event, to indicate the monitored service volume change event.
[0084] For example, the second device monitors the service volume overload event. The second device sends, to the first device, first information used to indicate that the service volume overload event is monitored. The first information carries the identifier of the service volume overload event, the changed service volume, and an identifier of the area 1 in which the service volume is changed.
[0085] 604: The first device determines, based on the first information, a PC5 communication resource required in the first area.
[0086] 605: The first device updates, based on the PC5 communication resource required in the first area, a PC5 communication resource pool that corresponds to the first area and that is in a PC5 configuration parameter.
[0087] For example, the second device monitors the service volume overload event, and the second device sends the first information of the service volume overload event to the first device. The first information carries the changed service volume and the identifier of the area 1 in which the service volume is changed. Because the changed service volume is large, a PC5 communication resource required in the area 1 is added. The first device may determine, based on the changed service volume, the PC5 communication resource required in the area 1, and then add, based on the PC5 communication resource required in the first area, a PC5 communication resource in the PC5 communication resource pool that corresponds to the first area and that is in the PC5 configuration parameter. Likewise, if the second device monitors the service volume release event, the second device sends first information of the service volume release event to the first device. The first information carries a changed service volume and an identifier of the area 1 in which the service volume is changed. Because the changed service volume is small, the PC5 communication resource required in the area 1 is reduced. The first device may determine, based on the changed service volume, the PC5 communication resource required in the area 1, and then reduce, based on the PC5 communication resource required in the first area, a PC5 communication resource in the PC5 communication resource pool that corresponds to the first area and that is in the PC5 configuration parameter.
[0088] Optionally, in addition to updating, based on the PC5 communication resource required in the first area, the PC5 communication resource pool that corresponds to the first area and that is in the PC5 configuration parameter, the first device may further update a PC5 communication resource pool that corresponds to an adjacent area of the first area. For a specific implementation principle, refer to the corresponding description in the 304 in the foregoing embodiment. Details are not described herein again.
[0089] Optionally, the first information further includes one or more of a type of a target terminal and a size of a message sent by the target terminal through PC5. The target terminal is a terminal that performs communication in the first area through the PC5. Based on this implementation, the first device can more accurately determine, based on more parameters, the PC5 communication resource required in the first area.
[0090] For example, if the first information further includes the type of target terminal, the first device may determine, based on the changed service volume and the type of target terminal, the PC5 communication resource required in the first area. Different types of terminal devices require different PC5 communication resources. Therefore, the PC5 communication resource required in the first area may be determined based on the changed service volume and the type of target terminal.
[0091] For another example, if the first information further includes the size of the message sent by the target terminal through the PC5, the first device may determine, based on the changed service volume and the size of the message sent by the target terminal through the PC5, the PC5 communication resource required in the first area. Different sizes of messages require different PC5 communication resources. A larger message requires more PC5 communication resources. Therefore, the PC5 communication resource required in the first area may be determined based on the changed service volume and the size of the message sent by the target terminal through the PC5.
[0092] For another example, if the first information further includes the type of target terminal and the size of the message sent by the target terminal through the PC5, the first device may determine, based on the type of target terminal, the changed service volume, and the size of the message sent by the target terminal through the PC5, the PC5 communication resource required in the first area.
[0093] It can be learned that by implementing the method described in FIG. 6, the first device can accurately determine the PC5 communication resource required in the first area, and the first device can properly update the PC5 configuration parameter in time based on the PC5 communication resource required in the first area.
[0094] FIG. 7 is a schematic diagram of another configuration parameter update method according to an embodiment of this application. As shown in FIG. 7, the configuration parameter update method includes the following steps 701 to 707. The step 707 is another specific implementation of the step 304.
[0097] 703: After monitoring the target event, the second device reports first information of the target event to the first device.
[0098] Specific implementations of the steps 701 to 703 are the same as the specific implementations of the steps 301 to 303. Details are not described herein again.
[0100] The second monitoring request is used to request the terminal device to monitor a network congestion event.
[0102] In this embodiment of this application, after receiving the second monitoring request, the terminal device monitors the network congestion event.
[0103] Optionally, if detecting that a network parameter does not meet a preset condition, the terminal device determines that the network congestion event is monitored. For example, the network parameter may be a signal receiving success rate. If the signal receiving success rate is less than a preset threshold, the terminal device determines that the network congestion event is monitored. For another example, the network parameter may be a communication delay. If the communication delay is greater than a preset delay, the terminal device determines that the network congestion event is monitored. For another example, the network parameter may be a throughput. If the throughput is less than a preset throughput, the terminal device determines that the network congestion event is monitored.
[0104] Optionally, the second monitoring request further carries one or more of an area that needs to be monitored, a network parameter that needs to be monitored, and a reporting condition of second information. If the second monitoring request further carries the area that needs to be monitored, the terminal device monitors only whether the network congestion event occurs in the area that needs to be monitored. If the second monitoring request further carries the network parameter that needs to be monitored, the terminal device monitors the network parameter that needs to be monitored, and determines, based on the monitored network parameter, whether the network congestion event occurs. If the second monitoring request further carries the reporting condition of the second information, after detecting the network congestion event, the terminal device reports the second information to the first device if the reporting condition of the second information is met. Optionally, the reporting condition of the second information may be that the network congestion event is detected for a preset quantity of consecutive times. Alternatively, the reporting condition of the second information may be that the network congestion event is detected for a preset quantity of times within a preset time period. Based on this implementation, the first device can specify, for the terminal device, the area that needs to be monitored, the network parameter that needs to be monitored, and the reporting condition of the second information.
[0105] For example, the area that needs to be monitored and that is carried by the second monitoring request is an area 1, the network parameter that needs to be monitored is a communication delay, and the reporting condition of the second information is that the network congestion event is detected for three consecutive times. The terminal device monitors the communication delay in the area 1, and if the communication delay is greater than the preset delay, determines that the network congestion event is monitored. If the network congestion event is detected for three consecutive times, the terminal device reports the second information to the first device.
[0106] 706: After monitoring the network congestion event, the terminal device reports the second information of the network congestion event to the first device.
[0107] 707: The first device updates a PC5 configuration parameter based on the first information and the second information.
[0108] In this embodiment of this application, after receiving the first information reported by the second device and the second information reported by the terminal device, the first device updates the PC5 configuration parameter based on the first information and the second information. Specifically, the first device determines, based on the first information and the second information, a PC5 communication resource required in an area, and then updates, based on the PC5 communication resource required in the area, a PC5 communication resource in a PC5 communication resource pool that corresponds to the area and that is in the PC5 configuration parameter. Optionally, in addition to updating, based on the PC5 communication resource required in the area, the PC5 communication resource pool that corresponds to the area and that is in the PC5 configuration parameter, the first device may further update a PC5 communication resource pool that corresponds to an adjacent area of the area.
[0109] The second information includes a network parameter of the terminal device and current location information of the terminal device. The current location information of the terminal device may be a current area in which the terminal device is located, or current location coordinates of the terminal device. For detailed descriptions of the first information, refer to the corresponding descriptions in the foregoing method embodiments. Details are not described herein again.
[0110] For example, the first device receives first information reported by the second device. The first information includes a registered service 1 and an identifier of an area 1 in which the service 1 is used. The first device receives second information reported by the terminal device. The second information includes a communication delay and the area 1 in which the terminal device is currently located. The first device determines, based on the first information and the second information, a PC5 communication resource required in the area 1. For example, if a service in the area 1 requires a relatively large quantity of PC5 communication resources, a quantity of terminals that have the service in the area 1 is relatively large, and a communication delay is relatively low, the first device may determine that the area 1 requires a relatively large quantity of PC5 communication resources. The first device updates, based on the PC5 communication resource required in the area 1, a PC5 communication resource pool that corresponds to the area 1 and that is in the PC5 configuration parameter.
[0111] Optionally, the second information may further include a type of terminal device. The first device may determine, based on the first information and the network parameter of the terminal device and the type of terminal device that are in the second information, the PC5 communication resource required in the area, and update, based on the PC5 communication resource required in the area, the PC5 communication resource in the PC5 communication resource pool that corresponds to the area and that is in the PC5 configuration parameter. Different types of terminal devices require different PC5 communication resources. Therefore, the PC5 communication resource required in the area may be determined based on the type of terminal device.
[0112] It should be noted that the first device may enable a plurality of different second devices to monitor different events, determine, based on first information uploaded by the plurality of different second devices and second information uploaded by the terminal device, a PC5 communication resource required in an area, and further update, based on the PC5 communication resource required in the area, a PC5 communication resource pool that corresponds to the area and that is in the PC5 configuration parameter. For example, the first device sends a first monitoring request 1 to a home platform, where the first monitoring request 1 requests to monitor a service change event. The first device sends a first monitoring request 2 to a traffic management platform, where the first monitoring request 2 requests to monitor a service volume impact event. The first device sends a first monitoring request 3 to a roadside unit, where the first monitoring request 3 requests to monitor a service volume change event. The first device receives the first information 1 sent by the home platform, where the first information 1 includes service change information. The first device receives the first information 2 sent by the traffic management platform, where the first information 2 includes service volume impact information. The first device receives the first information 3 sent by the home platform, where the first information 3 includes service volume change information. The first device sends a second monitoring request to a terminal device, where the second monitoring request is used to request to monitor a network congestion event. The first device receives second information reported by the terminal device. The first device determines, based on the service change information, the service volume impact information, the service volume change information, and the second information, a PC5 communication resource required in an area, and further updates, based on the PC5 communication resource required in the area, a PC5 communication resource pool that corresponds to the area and that is in the PC5 configuration parameter.
[0113] It can be learned that by implementing the method described in FIG. 7, the first device can properly update the PC5 configuration parameter in time.
[0114] The foregoing describes in detail the configuration parameter update method according to the embodiments of this application. The following describes a related apparatus in the embodiments of this application.
[0115] In the embodiments of the present invention, the device may be divided into function modules based on the foregoing method examples. For example, each function module may be obtained through division based on each corresponding function, or two or more functions may be integrated into one module. The integrated module may be implemented in a form of hardware, or may be implemented in a form of a software functional module. It should be noted that, in this embodiment of the present invention, module division is exemplary, and is merely a logical function division. In actual implementation, another division manner may be used.
[0116] FIG. 8 is a schematic structural diagram of a configuration parameter update apparatus according to an embodiment of this application. The configuration parameter update apparatus in this embodiment of this application may be applied to the first device in the foregoing method embodiment. The configuration parameter update apparatus may be configured to perform some or all functions of the first device in the foregoing method embodiments. The configuration parameter update apparatus may include a communications module 801 and a processing module 802. The details are as follows:
[0117] The communications module 801 is configured to send a first monitoring request to a second device. The first monitoring request is used to request the second device to monitor a target event, and the target event includes one or more of a service change event, a service volume impact event, and a service volume change event. The service volume change event is an event in which a service volume is greater than a first threshold or a service volume is less than a second threshold, and the first threshold is greater than the second threshold. The communications module 801 is further configured to receive first information that is of the target event and that is reported by the second device. The first information includes one or more of service change information, service volume impact information, and service volume change information. The processing module 802 is configured to update a PC5 configuration parameter based on the first information.
[0118] In an optional implementation, the first information includes the service change information, the service change information includes a changed service and an identifier of a first area, and the first area is an area in which the changed service is used. A manner in which the processing module 802 updates the PC5 configuration parameter based on the first information specifically includes: determining, based on the changed service, a target service used in the first area; determining a quantity of terminals that have the target service; determining, based on the target service and the quantity of terminals, a proximity communication PC5 communication resource required in the first area; and updating, based on the PC5 communication resource required in the first area, a PC5 communication resource pool that corresponds to the first area and that is in the PC5 configuration parameter.
[0119] As an optional implementation, the service change information further includes an identifier of a terminal of the changed service. A manner in which the processing module 802 determines the quantity of terminals that have the target service specifically includes: determining, based on the identifier of the terminal of the changed service, the quantity of terminals that have the target service.
[0120] In an optional implementation, the first information includes the service volume impact information, the service volume impact information includes a monitored service volume impact event and an identifier of a first area, and the first area is an area affected by the service volume impact event. A manner in which the processing module 802 updates the PC5 configuration parameter based on the first information specifically includes: determining, based on the monitored service volume impact event, a proximity communication PC5 communication resource required in the first area; and updating, based on the PC5 communication resource required in the first area, a PC5 communication resource pool that corresponds to the first area and that is in the PC5 configuration parameter.
[0121] As an optional implementation, the service volume impact information further includes a first time period, and the first time period is a time period the service volume impact event lasts. The processing module 802 is further configured to: after updating, based on the PC5 communication resource required in the first area, the PC5 communication resource pool that corresponds to the first area and that is in the PC5 configuration parameter, restore, based on the first time period, the PC5 communication resource pool that corresponds to the first area to a resource pool used before the updating.
[0122] In an optional implementation, the first information includes the service volume change information, the service volume change information includes a changed service volume and an identifier of a first area, and the first area is an area in which a service volume is changed. A manner in which the processing module 802 updates the PC5 configuration parameter based on the first information specifically includes: determining, based on the first information, a proximity communication PC5 communication resource required in the first area; and updating, based on the PC5 communication resource required in the first area, a PC5 communication resource pool that corresponds to the first area and that is in the PC5 configuration parameter.
[0123] In an optional implementation, the first information further includes one or more of a type of a target terminal and a size of a message sent by the target terminal through PC5, and the target terminal is a terminal that performs communication in the first area through the PC5.
[0124] In an optional implementation, the first device sends a second monitoring request to a terminal device, where the second monitoring request is used to request the terminal device to monitor a network congestion event. The first device receives second information that is of the network congestion event and that is reported by the terminal device, where the second information includes a network parameter of the terminal device and current location information of the terminal device. A manner in which the processing module 802 updates the PC5 configuration parameter based on the first information specifically includes: updating, by the first device, the PC5 configuration parameter based on the first information and the second information.
[0125] In an optional implementation, the second information further includes a type of terminal device.
[0126] In an optional implementation, the second monitoring request carries one or more of an area that needs to be monitored, a network parameter that needs to be monitored, and a reporting condition of the second information.
[0127] In an optional implementation, the first monitoring request further carry one or more of a type of terminal that needs to be monitored, an area that needs to be monitored, the first threshold, the second threshold, a service volume statistics period, and a reporting condition of the first information.
[0128] In an optional implementation, the first device is one of a vehicle-to-everything application server V2X AS, a vehicle-to-everything service control function V2X CF, and an access network device, and the second device is one of the terminal device, a home platform of the terminal device, and a traffic management platform.
[0129] Based on a same inventive concept, for a problem-resolving principle and beneficial effects of the configuration parameter update apparatus, refer to the implementations of the foregoing method embodiments. Details are not described herein.
[0130] FIG. 8 is a schematic structural diagram of a configuration parameter update apparatus according to an embodiment of this application. The configuration parameter update apparatus in this embodiment of this application may be applied to the second device in the foregoing method embodiment. The configuration parameter update apparatus may be configured to perform some or all functions of the second device in the foregoing method embodiments. The configuration parameter update apparatus may include a communications module 801 and a processing module 802. The details are as follows:
[0131] The communications module 801 is configured to receive a first monitoring request sent by a first device. The first monitoring request is used to request the second device to monitor a target event, and the target event includes one or more of a service change event, a service volume impact event, or a service volume change event. The service volume change event is an event in which a service volume is greater than a first threshold or a service volume is less than a second threshold, and the first threshold is greater than the second threshold. The processing module 802 is configured to monitor the target event. The communications module 801 is further configured to: after the processing module 802 monitors the target event, report first information of the target event to the first device. The first information includes one or more of service change information, service volume impact information, or service volume change information.
[0132] In an optional implementation, the first information includes the service change information, the service change information includes a changed service and an identifier of a first area, and the first area is an area in which the changed service is used.
[0133] As an optional implementation, the service change information further includes an identifier of a terminal of the changed service.
[0134] In an optional implementation, the first information includes the service volume impact information, the service volume impact information includes a monitored service volume impact event and an identifier of a first area, and the first area is an area affected by the service volume impact event.
[0135] In an optional implementation, the service volume impact information further includes a first time period, and the first time period is a time period the service volume impact event lasts.
[0136] In an optional implementation, the first information includes the service volume change information, the service volume change information includes a changed service volume and an identifier of a first area, and the first area is an area in which a service volume is changed.
[0137] In an optional implementation, the first information further includes one or more of a type of a target terminal and a size of a message sent by the target terminal through PC5, and the target terminal is a terminal that performs communication in the first area through the PC5.
[0138] In an optional implementation, the communications module 801 is further configured to receive a second monitoring request sent by the first device, where the second monitoring request is used to request the second device to monitor a network congestion event. The processing module 802 is further configured to monitor the network congestion event. The communications module 801 is further configured to: after the processing module 802 monitors the network congestion event, report second information of the network congestion event to the first device, where the second information includes a network parameter of the second device and current location information of the second device.
[0139] In an optional implementation, the second information further includes a type of terminal device.
[0140] In an optional implementation, the second monitoring request carries one or more of an area that needs to be monitored, a network parameter that needs to be monitored, and a reporting condition of the second information.
[0141] In an optional implementation, the first monitoring request further carry one or more of a type of terminal that needs to be monitored, an area that needs to be monitored, the first threshold, the second threshold, a service volume statistics period, and a reporting condition of the first information.
[0142] In an optional implementation, the first device is one of a vehicle-to-everything application server V2X AS, a vehicle-to-everything service control function V2X CF, and an access network device, and the second device is one of the terminal device, a home platform of the terminal device, and a traffic management platform.
[0143] Based on a same inventive concept, for a problem-resolving principle and beneficial effects of the configuration parameter update apparatus, refer to the implementations of the foregoing method embodiments. Details are not described herein.
[0144] FIG. 9 is a schematic structural diagram of a configuration parameter update apparatus according to an embodiment of this application. The configuration parameter update apparatus may perform behavior functions of the first device or the second device in the foregoing method embodiments. As shown in FIG. 9, the configuration parameter update apparatus includes a processor 901, a memory 902, and a communications interface 903. The processor 901, the memory 902, and the communications interface 903 are connected.
[0145] The processor 901 may be a central processing unit (central processing unit, CPU), a general-purpose processor, a co-processor, a digital signal processor (digital signal processing, DSP), an application-specific integrated circuit (application-specific integrated circuit, ASIC), a field programmable gate array (field programmable gate array, FPGA), or another programmable logical device, a transistor logical device, a hardware component, or any combination thereof. Alternatively, the processor 901 may be a combination of processors implementing a computing function, for example, a combination of one or more microprocessors, or a combination of the DSP and a microprocessor.
[0146] The communications interface 903 is configured to implement communication with another network element.
[0147] The processor 901 invokes program code stored in the memory 902, to perform the steps performed by the first device or the second device in the foregoing method embodiments.
[0148] Based on a same inventive concept, for a problem-resolving principle and beneficial effects of the configuration parameter update apparatus, refer to the implementations of the foregoing method embodiments. Details are not described herein.
[0149] It should be noted that, in the foregoing embodiments, the description of each embodiment has respective focuses. For a part that is not described in detail in an embodiment, refer to related descriptions in other embodiments.
• sending (step 601) a first monitoring request to a second device, wherein the first monitoring request is used to request the second device to monitor traffic for detecting a target event, the target event comprising a service volume change event,
o the service volume change event is an event in which a service volume is greater than a first threshold or the service volume is less than a second threshold, and the first threshold is greater than the second threshold,
wherein the service volume is a quantity of messages sent through a PC5 in a unit time;
• receiving (step 603) first information that is of the target event from the second device, wherein the first information comprises:
o service volume change information, the service volume change information comprises, as the service volume being greater than the first threshold or less than the second threshold, a changed service volume and an identifier of a first area, and the first area is an area in which a service volume is changed to the changed service volume, and
o in a first alternative, a type of a target terminal, or, in a second alternative
instead of the first alternative, a size of a message sent by the target terminal
through the PC5, and the target terminal is a terminal that performs communication
in the first area through the PC5;
wherein the target terminal is a terminal that performs communication in the first
area through the PC5; and
• updating a PC5 configuration parameter based on the first information, wherein the updating the PC5 configuration parameter based on the first information comprises:
∘ if the first information comprises the first alternative, determining (step 604), based on the changed service volume and the type of the target terminal, a PC5 communication resource required in the first area;
∘ if the first information comprises the second alternative, determining (step 604), based on the changed service volume and the size of the message sent by the target terminal, the PC5 communication resource required in the first area, and
o in the first and second alternative, updating (step 605), based on the PC5 communication resource required in the first area, a PC5 communication resource pool that corresponds to the first area and that is in the PC5 configuration parameter.
• sending a second monitoring request to a terminal device, wherein the second monitoring request is used to request the terminal device to monitor a network congestion event; and
• receiving second information that is of the network congestion event and that is reported by the terminal device, wherein the second information comprises a network parameter of the terminal device and current location information of the terminal device; and
• the updating the PC5 configuration parameter based on the first information comprises:
• updating the PC5 configuration parameter based on the first information and the second information.
• receiving (step 601) a first monitoring request from a first device, wherein the first monitoring request is used to request the second device to monitor traffic for detecting a target event, the target event comprising a service volume change event,
o the service volume change event is an event in which a service volume is greater than a first threshold or the service volume is less than a second threshold, and the first threshold is greater than the second threshold,
wherein the service volume is a quantity of messages sent through a PC5 in a unit time;
• detecting (step 602) the target event during the monitoring of the traffic; and
• after monitoring the target event, reporting (step 603) first information of the target event to the first device, wherein the first information comprises:
o service volume change information, the service volume change information comprises, as the service volume being greater than the first threshold or less than the second threshold, a changed service volume and an identifier of a first area, and the first area is an area in which a service volume is changed to the changed service volume, and
o in a first alternative, a type of a target terminal, or, in a second alternative instead of the first alternative, a size of a message sent by the target terminal through the PC5, and the target terminal is a terminal that performs communication in the first area through the PC5,
wherein the target terminal is a terminal that performs communication in the first area through the PC5.• a memory configured to store one or more programs; and
• a processor configured to execute the program in the memory, so that the first device performs the method according to any one of claims 1 to 3.
• a memory configured to store one or more programs; and
• a processor configured to execute the program in the memory, so that the second device performs the method according to claim 4.
• Senden (Schritt 601) einer ersten Überwachungsanfrage an eine zweite Vorrichtung, wobei die erste Überwachungsanfrage dafür verwendet wird, die zweite Vorrichtung aufzufordern, Traffic zum Detektieren eines Zielereignisses zu überwachen, wobei das Zielereignis ein Dienstvolumenänderungsereignis umfasst,
o wobei das Dienstvolumenänderungsereignis ein Ereignis ist, bei dem ein Dienstvolumen größer als eine erste Schwelle ist oder das Dienstvolumen kleiner als eine zweite Schwelle ist und die erste Schwelle größer als die zweite Schwelle ist, wobei das Dienstvolumen eine Menge von Nachrichten ist, die durch eine PC5-Schnittstelle in einer Einheitszeit gesendet werden;
• Empfangen (Schritt 603) erster Informationen, die von dem Zielereignis stammen, von der zweiten Vorrichtung, wobei die ersten Informationen umfassen:
o Dienstvolumenänderungsinformationen, wobei die Dienstvolumenänderungsinformationen, da das Dienstvolumen größer als die erste Schwelle oder kleiner als die zweite Schwelle ist, ein geändertes Dienstvolumen und eine Kennung eines ersten Bereichs umfassen und der erste Bereich ein Bereich ist, in dem ein Dienstvolumen zu dem geänderten Dienstvolumen geändert wird, und
o in einer ersten Alternative einen Typ eines Zielendgeräts oder in einer zweiten
Alternative anstelle der ersten Alternative eine Größe einer Nachricht, die von dem
Zielendgerät über die PC5-Schnittstelle gesendet wird, und wobei das Zielendgerät
ein Endgerät ist, das Kommunikation in dem ersten Bereich über die PC5-Schnittstelle
durchführt;
wobei das Zielendgerät ein Endgerät ist, das Kommunikation in dem ersten Bereich über
die PC5-Schnittstelle durchführt; und
• Aktualisieren eines PCS-Konfigurationsparameters auf der Grundlage der ersten Informationen, wobei das Aktualisieren des PCS-Konfigurationsparameters auf der Grundlage der ersten Informationen umfasst:
o wenn die ersten Informationen die erste Alternative umfassen, Bestimmen (Schritt 604) einer PC5-Kommunikationsressource, die in dem ersten Bereich erforderlich ist, auf der Grundlage des geänderten Dienstvolumens und des Typs des Zielendgeräts;
o wenn die ersten Informationen die zweite Alternative umfassen, Bestimmen (Schritt 604) der PC5-Kommunikationsressource, die in dem ersten Bereich erforderlich ist, auf der Grundlage des geänderten Dienstvolumens und der Größe der Nachricht, die von dem Zielendgerät gesendet wird, und
o in der ersten und zweiten Alternative Aktualisieren (Schritt 605) eines PC5-Kommunikationsressourcenpools, der dem ersten Bereich entspricht und der sich in dem PCS-Konfigurationsparameter befindet, auf der Grundlage der PC5-Kommunikationsressource, die in dem ersten Bereich erforderlich ist.
• Senden einer zweiten Überwachungsanfrage an eine zweite Endgerätevorrichtung, wobei die zweite Überwachungsanfrage dafür verwendet wird, die Endgerätevorrichtung aufzufordern, ein Netzwerküberlastungsereignis zu überwachen, und
• Empfangen zweiter Informationen, die von dem Netzwerküberlastungsereignis stammen und die von der Endgerätevorrichtung gemeldet werden, wobei die zweiten Informationen einen Netzwerkparameter der Endgerätevorrichtung und eine aktuelle Standortinformationen der Endgerätevorrichtung umfassen, und
• wobei das Aktualisieren des PCS-Konfigurationsparameters auf der Grundlage der ersten Informationen umfasst:
• Aktualisieren des PCS-Konfigurationsparameters auf der Grundlage der ersten Informationen und der zweiten Informationen.
• Empfangen (Schritt 601) einer ersten Überwachungsanfrage von einer ersten Vorrichtung, wobei die erste Überwachungsanfrage dafür verwendet wird, die zweite Vorrichtung aufzufordern, Traffic zum Detektieren eines Zielereignisses zu überwachen, wobei das Zielereignis ein Dienstvolumenänderungsereignis umfasst,
o wobei das Dienstvolumenänderungsereignis ein Ereignis ist, bei dem ein Dienstvolumen größer als eine erste Schwelle ist oder das Dienstvolumen kleiner als eine zweite Schwelle ist und die erste Schwelle größer als die zweite Schwelle ist, wobei das Dienstvolumen eine Menge von Nachrichten ist, die durch eine PC5-Schnittstelle in einer Einheitszeit gesendet werden;
• Detektieren (Schritt 602) des Zielereignisses während des Überwachens des Traffics; und
• nach dem Überwachen des Zielereignisses Melden (Schritt 603) erster Informationen des Zielereignisses an die erste Vorrichtung, wobei die ersten Informationen umfassen:
o Dienstvolumenänderungsinformationen, wobei die Dienstvolumenänderungsinformationen, da das Dienstvolumen größer als die erste Schwelle oder kleiner als die zweite Schwelle ist, ein geändertes Dienstvolumen und eine Kennung eines ersten Bereichs umfassen und der erste Bereich ein Bereich ist, in dem ein Dienstvolumen zu dem geänderten Dienstvolumen geändert wird, und
o in einer ersten Alternative einen Typ eines Zielendgeräts oder in einer zweiten Alternative anstelle der ersten Alternative eine Größe einer Nachricht, die von dem Zielendgerät über die PC5-Schnittstelle gesendet wird, und wobei das Zielendgerät ein Endgerät ist, das Kommunikation in dem ersten Bereich über die PC5-Schnittstelle durchführt,
wobei das Zielendgerät ein Endgerät ist, das Kommunikation in dem ersten Bereich über die PC5-Schnittstelle durchführt.• einen Speicher, der dazu ausgelegt ist, ein oder mehrere Programme zu speichern; und
• einen Prozessor, der dazu ausgelegt ist, das Programm in dem Speicher derart auszuführen, dass die erste Vorrichtung das Verfahren nach einem der Ansprüche 1 bis 3 durchführt.
• einen Speicher, der dazu ausgelegt ist, ein oder mehrere Programme zu speichern; und
• einen Prozessor, der dazu ausgelegt ist, das Programm in dem Speicher derart auszuführen, dass die zweite Vorrichtung das Verfahren nach Anspruch 4 durchführt.
• envoyer (étape 601) une première demande de surveillance à un deuxième dispositif, la première demande de surveillance étant utilisée pour demander au deuxième dispositif de surveiller un trafic pour détecter un événement cible, l'événement cible comprenant un événement de changement de volume de service,
∘ l'événement de changement de volume de service est un événement au cours duquel un volume de service est supérieur à un premier seuil ou le volume de service est inférieur à un deuxième seuil, et le premier seuil est supérieur au deuxième seuil, dans lequel le volume de service est une quantité de messages envoyés par une PC5 dans une unité de temps ;
• recevoir (étape 603) en provenance du deuxième dispositif des premières informations qui sont celles de l'événement cible, les premières informations comprenant :
∘ des informations de changement de volume de service, les informations de changement de volume de service comprenant, lorsque le volume de service est supérieur au premier seuil ou inférieur au deuxième seuil, un volume de service modifié et un identifiant d'une première zone, et la première zone est une zone dans laquelle un volume de service a changé pour devenir le volume de service modifié, et
∘ dans une première variante, un type d'un terminal cible, ou, dans une deuxième variante
utilisée à la place de la première variante, une taille d'un message envoyé par le
terminal cible par la PC5, et le terminal cible est un terminal qui effectue une communication
dans la première zone par la PC5 ;
dans lequel le terminal cible est un terminal qui effectue une communication dans
la première zone par la PC5 ; et
• mettre à jour un paramètre de configuration PC5 sur la base des premières informations, la mise à jour du paramètre de configuration PC5 basée sur les premières informations comprenant les étapes consistant à :
∘ si les premières informations comprennent la première variante, déterminer (étape 604), sur la base du volume de service modifié et du type du terminal cible, une ressource de communication PC5 exigée dans la première zone ;
∘ si les premières informations comprennent la deuxième variante, déterminer (étape 604), sur la base du volume de service modifié et de la taille du message envoyé par le terminal cible, la ressource de communication PC5 exigée dans la première zone, et
∘ dans les première et deuxième variantes, mettre à jour (étape 605), sur la base de la ressource de communication PC5 exigée dans la première zone, un pool de ressources de communication PC5 qui correspond à la première zone et qui se trouve dans le paramètre de configuration PC5.
• envoyer une deuxième demande de surveillance à un dispositif terminal, la deuxième demande de surveillance étant utilisée pour demander au dispositif terminal de surveiller un événement de congestion de réseau ; et
• recevoir des deuxièmes informations qui sont celles de l'événement de congestion de réseau et qui sont rapportés par le dispositif terminal, les deuxièmes informations comprenant un paramètre de réseau du dispositif terminal et des informations d'emplacement actuel du dispositif terminal ; et
• la mise à jour du paramètre de configuration PC5 sur la base des premières informations comprenant l'étape consistant à :
• mettre à jour le paramètre de configuration PC5 sur la base des premières informations et des deuxièmes informations.
• recevoir (étape 601) une première demande de surveillance en provenance d'un premier dispositif, la première demande de surveillance étant utilisée pour demander au deuxième dispositif de surveiller un trafic pour détecter un événement cible, l'événement cible comprenant un événement de changement de volume de service,
∘ l'événement de changement de volume de service est un événement au cours duquel un volume de service est supérieur à un premier seuil ou le volume de service est inférieur à un deuxième seuil, et le premier seuil est supérieur au deuxième seuil, dans lequel le volume de service est une quantité de messages envoyés par une PC5 dans une unité de temps ;
• détecter (étape 602) l'événement cible durant la surveillance du trafic ; et
• après la surveillance de l'événement cible, rapporter (étape 603) des premières informations de l'événement cible au premier dispositif, les premières informations comprenant :
∘ des informations de changement de volume de service, les informations de changement de volume de service comprenant, lorsque le volume de service est supérieur au premier seuil ou inférieur au deuxième seuil, un volume de service modifié et un identifiant d'une première zone, et la première zone est une zone dans laquelle un volume de service a changé pour devenir le volume de service modifié, et
∘ dans une première variante, un type d'un terminal cible, ou, dans une deuxième variante utilisée à la place de la première variante, une taille d'un message envoyé par le terminal cible par la PC5, et le terminal cible est un terminal qui effectue une communication dans la première zone par la PC5 ;
dans lequel le terminal cible est un terminal qui effectue une communication dans la première zone par la PC5.• une mémoire configurée pour stocker un ou plusieurs programmes ; et
• un processeur configuré pour exécuter le programme dans la mémoire, afin que le premier dispositif effectue le procédé selon l'une quelconque des revendications 1 à 3.
• une mémoire configurée pour stocker un ou plusieurs programmes ; et
• un processeur configuré pour exécuter le programme dans la mémoire, afin que le deuxième dispositif effectue le procédé selon la revendication 4.
REFERENCES CITED IN THE DESCRIPTION
This list of references cited by the applicant is for the reader's convenience only. It does not form part of the European patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be excluded and the EPO disclaims all liability in this regard.
Patent documents cited in the description