Method for transmitting and receiving messages in wireless communication system, and apparatus for performing same

The proposed method and device for transmitting and receiving POIM-PA messages in ITS systems address the inefficiency in parking operations by providing real-time parking availability information, enhancing the efficiency and smoothness of parking services.

WO2025058301A1PCT designated stage expired Publication Date: 2025-03-20LG ELECTRONICS INC
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2024/013099
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-09-11
Filing Date
2024-09-02
Publication Date
2025-03-20

AI Technical Summary

Technical Problem

Existing wireless communication systems in Intelligent Transport Systems (ITS) lack an efficient method to transmit and receive messages related to parking availability, leading to confusion and inefficiency in parking operations.

Method used

A method and device for transmitting and receiving messages about parking availability in ITS, using a POIM-PA (Point of Interest Message - Parking Assistance) message format that includes information on occupied and unoccupied parking spaces, vehicles waiting to park, and expected waiting times.

Benefits of technology

This solution enables more efficient and smooth parking services by providing real-time information on parking availability, helping vehicles determine if they can park and reducing the likelihood of vehicles entering a full parking lot.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2024013099_20032025_PF_FP_ABST
    Figure KR2024013099_20032025_PF_FP_ABST
Patent Text Reader

Abstract

A method by which a first device transmits messages in a wireless communication system, according to at least one of various embodiments, comprises: obtaining information about a parking lot; and transmitting messages notifying whether parking in the parking lot is available on the basis of the obtained information about the parking lot, wherein the obtained information about the parking lot includes information about unoccupied parking spaces in the parking lot and information about vehicles that are not parked from among vehicles that have entered the parking lot, and the message can include information related to whether the number of the vehicles that are not parked exceeds the number of unoccupied parking spaces.
Need to check novelty before this filing date? Find Prior Art

Description

Method for transmitting and receiving messages in a wireless communication system and device for performing the same

[0001] This specification relates to a wireless communication system, and more specifically, to a method for transmitting and receiving messages related to parking in an intelligent transport system (ITS) and a device for performing the same.

[0002] A wireless communication system is a multiple access system that supports communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power, etc.). Examples of multiple access systems include code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and multi-carrier frequency division multiple access (MC-FDMA).

[0003] Intelligent Transport Systems (ITS) utilize wireless communication technologies to manage transportation systems more efficiently and improve safety. ITS systems can monitor traffic conditions in real time and collect and process data using CCTV, sensor networks, GPS devices, and wireless communication systems. ITS systems can also support inter-vehicle communication, allowing vehicles to communicate with each other and share information about their surroundings to enhance autonomous driving and traffic safety.

[0004] The technical task to be achieved is to provide a method and device for providing parking-related messages in a wireless communication system. For example, the parking-related messages may include information regarding parking availability.

[0005] The technical challenges are not limited to those mentioned above, and other technical challenges not mentioned can be derived from the description below.

[0006] In a wireless communication system according to one aspect of the present disclosure, a method for transmitting a message by a first device comprises: obtaining information about a parking lot; and transmitting a message indicating whether parking is available in the parking lot based on the obtained information about the parking lot, wherein the obtained information about the parking lot includes information about unoccupied parking spaces within the parking lot and information about unparked vehicles among vehicles that have entered the parking lot, and the message may include information related to whether the number of unparked vehicles exceeds the number of unoccupied parking spaces.

[0007] The above message may include information about the number of excess vehicles based on whether the number of unparked vehicles exceeds the number of unoccupied parking spaces.

[0008] The information about the above parking lot may further include information about vehicles waiting to enter the above parking lot.

[0009] The above message may further include information about the number of vehicles waiting.

[0010] The above message may further include information regarding the expected waiting time required to enter the parking lot. The expected waiting time may be calculated based on the leading vehicle among the waiting vehicles.

[0011] Information about the number of vehicles waiting may be included in the message based on whether all parking spaces in the parking lot are occupied.

[0012] The above first device may be an RSU (road side unit) that monitors the parking lot.

[0013] The above message may be a POIM-PA (point of interest message - parking assistance) message.

[0014] According to another aspect of the present disclosure, a non-transitory computer-readable recording medium having recorded thereon a program for performing the method described above may be provided.

[0015] In another aspect of the present disclosure, a first device comprises: at least one memory configured to store instructions; and at least one processor configured to perform operations by executing the instructions, wherein the operations performed by the at least one processor include: obtaining information about a parking lot; and transmitting a message indicating whether parking is available in the parking lot based on the obtained information about the parking lot, wherein the obtained information about the parking lot includes information about unoccupied parking spaces within the parking lot and information about unparked vehicles among vehicles that have entered the parking lot, and the message may include information related to whether the number of unparked vehicles exceeds the number of unoccupied parking spaces.

[0016] The above first device may further include a transceiver.

[0017] The above first device may be an RSU (road side unit) that monitors the parking lot.

[0018] In another aspect of the present disclosure, a method for a second device to receive a message in a wireless communication system comprises: receiving a message from a first device; and determining whether parking is available in a parking lot based on the message, wherein the message may include information regarding whether the number of unparked vehicles among vehicles entering the parking lot exceeds the number of unoccupied parking spaces within the parking lot.

[0019] In a wireless communication system according to another aspect of the present disclosure, a second device includes at least one memory configured to store instructions; and at least one processor configured to perform operations by executing the instructions, wherein the operations performed by the at least one processor include receiving a message from a first device; and determining whether parking is available in a parking lot based on the message, wherein the message may include information related to whether the number of unparked vehicles among vehicles entering the parking lot exceeds the number of unoccupied parking spaces within the parking lot.

[0020] The second device may further include a transceiver.

[0021] The second device may be a vehicle.

[0022] According to one embodiment of the present disclosure, a more smooth and efficient parking service can be provided by transmitting and receiving parking-related messages.

[0023] The effects that can be obtained in various embodiments are not limited to the effects mentioned above, and other effects not mentioned can be derived from the description below.

[0024] Figure 1 is a diagram for explaining V2X communication.

[0025] Figure 2 shows a radio protocol architecture for SL communication.

[0026] Figure 3 shows a terminal performing V2X or SL communication.

[0027] Figure 4 illustrates various types of ITS-Stations (ITS-S) that provide parking availability services.

[0028] Figure 5 illustrates PAM transmission and reception for parking availability service between ITS-Ss.

[0029] Figure 6 illustrates an example of a POIM PDU.

[0030] Figure 7 illustrates an example of a Parking Availability PDU.

[0031] Figure 8 illustrates an example of a parking lot that is over occupant.

[0032] FIG. 9 is a diagram illustrating the operation of a first device that transmits a message including information about parking availability according to one embodiment.

[0033] FIG. 10 is a diagram illustrating the operation of a second device that receives a message including information about parking availability according to one embodiment.

[0034] FIG. 11 is a diagram illustrating the operation of a first device that transmits a message including information about parking availability according to another embodiment.

[0035] FIG. 12 is a diagram illustrating the operation of a second device that receives a message including information about parking availability according to another embodiment.

[0036] Figure 13 illustrates a flow of a message transmission method according to one embodiment.

[0037] Figure 14 illustrates a flow of a message receiving method according to one embodiment.

[0038] Figure 15 illustrates a communication system applicable to the present disclosure.

[0039] Figure 16 illustrates a wireless device applicable to the present disclosure.

[0040] Figure 17 illustrates another example of a wireless device applicable to the present disclosure.

[0041] Figure 18 illustrates a vehicle or autonomous vehicle applicable to the present disclosure.

[0042] Sidelink (SL) refers to a communication method that establishes a direct link between user equipment (UE), allowing voice or data to be exchanged directly between terminals without going through a base station (BS). SL is being considered as a solution to address the burden on base stations due to rapidly increasing data traffic.

[0043] V2X (vehicle-to-everything) refers to a communication technology that exchanges information with other vehicles, pedestrians, and infrastructure-based objects through wired / wireless communication. V2X can be divided into four types: V2V (vehicle-to-vehicle), V2I (vehicle-to-infrastructure), V2N (vehicle-to-network), and V2P (vehicle-to-pedestrian). V2X communication can be provided through the PC5 interface and / or Uu interface.

[0044] Figure 1 is a diagram for comparing and explaining V2X communication based on RAT before NR and V2X communication based on NR.

[0045] In relation to V2X communication, in RATs prior to NR, methods for providing safety services based on V2X messages such as Basic Safety Message (BSM), Cooperative Awareness Message (CAM), and Decentralized Environmental Notification Message (DENM) were mainly discussed. V2X messages may include location information, dynamic information, attribute information, etc. For example, a terminal may transmit a CAM of a periodic message type and / or a DENM of an event triggered message type to another terminal.

[0046] For example, a CAM may include basic vehicle information such as dynamic vehicle status information, such as direction and speed, static vehicle data, such as dimensions, external lighting conditions, and route history. For example, a terminal may broadcast a CAM, and the latency of the CAM may be less than 100 ms. For example, in the event of an emergency, such as a vehicle breakdown or accident, a terminal may generate a DENM and transmit it to other terminals. For example, all vehicles within the transmission range of the terminal may receive the CAM and / or DENM. In this case, the DENM may have a higher priority than the CAM.

[0047] Since then, various V2X scenarios have been proposed in NR in relation to V2X communications. For example, various V2X scenarios may include vehicle platooning, advanced driving, extended sensors, and remote driving.

[0048] For example, based on vehicle platooning, vehicles can dynamically form groups and move together. For example, to perform platoon operations based on vehicle platooning, vehicles in the group can receive periodic data from the lead vehicle. For example, vehicles in the group can use this periodic data to narrow or widen the gap between vehicles.

[0049] For example, based on improved driving, vehicles can become semi-autonomous or fully automated. For example, each vehicle can adjust its trajectories or maneuvers based on data acquired from local sensors of nearby vehicles and / or nearby logical entities. Furthermore, for example, each vehicle can share driving intentions with nearby vehicles.

[0050] For example, based on extended sensors, raw data, processed data, or live video data acquired through local sensors can be exchanged between vehicles, logical entities, pedestrian terminals, and / or V2X application servers. Thus, for example, a vehicle can perceive its environment better than it can perceive using its own sensors.

[0051] For example, based on remote driving, a remote driver or V2X application can operate or control the remote vehicle for people who cannot drive or for remote vehicles located in hazardous environments. For example, in cases where the route is predictable, such as public transportation, cloud computing-based driving can be utilized to operate or control the remote vehicle. Additionally, access to a cloud-based back-end service platform, for example, can be considered for remote driving.

[0052] Meanwhile, a method to specify service requirements for various V2X scenarios, such as vehicle platooning, enhanced driving, expanded sensors, and remote driving, is being discussed in NR-based V2X communication.

[0053] Figure 2 illustrates a radio protocol architecture for SL communication. Specifically, Figure 2 (a) illustrates the user plane protocol stack of NR, and Figure 2 (b) illustrates the control plane protocol stack of NR.

[0054] Figure 3 shows a terminal performing V2X or SL communication.

[0055] Referring to FIG. 3, the term "terminal" in V2X or SL communications may primarily refer to a user's terminal. However, if a network device, such as a base station, transmits and receives signals according to a communication method between terminals, the base station may also be considered a type of terminal. For example, terminal 1 may be a first device (100), and terminal 2 may be a second device (200).

[0056] For example, terminal 1 can select a resource unit corresponding to a specific resource within a resource pool, which represents a set of resources. Then, terminal 1 can transmit an SL signal using the resource unit. For example, terminal 2, which is a receiving terminal, can be configured with a resource pool in which terminal 1 can transmit a signal, and can detect a signal from terminal 1 within the resource pool.

[0057] Here, if terminal 1 is within the connection range of the base station, the base station can inform terminal 1 of the resource pool. On the other hand, if terminal 1 is outside the connection range of the base station, another terminal can inform terminal 1 of the resource pool, or terminal 1 can use a pre-configured resource pool.

[0058] In general, a resource pool can be composed of multiple resource units, and each terminal can select one or multiple resource units to use for its SL signal transmission.

[0059] How to send and receive messages related to parking

[0060] A method for providing parking-related messages and the operations of a device / system for doing so are described. For example, a parking-related message may include information regarding parking availability.

[0061] The parking availability service (PAS) can be managed by the device's parking management application and provides real-time information on parking availability. The parking availability service can also be integrated with other mobility services (e.g., valet parking, electric vehicle charging). The parking availability service can provide real-time information on parking spots, their management, and complex status information on areas of interest related to the parking spots.

[0062] Figure 4 illustrates various types of ITS-Stations (ITS-S) that provide parking availability services.

[0063] Referring to FIG. 4, (i) the ITS-S corresponding to the cloud / edge and / or (ii) the ITS-S corresponding to the road infrastructure can manage the linked areas of interest (POI) through parking application management. (iii) the ITS-S corresponding to the vehicle can drive the mobility application through vehicle motion management. (iv) the ITS-S corresponding to the portable device can drive the mobility application through motorized VRU assistance.

[0064] Figure 5 illustrates PAM transmission and reception for parking availability service between ITS-Ss.

[0065] In Fig. 5, each ITS-S can provide a parking availability service, which can be controlled by an ITS mobility application (e.g., a Parking Management Application). Messages for providing parking availability services (e.g., Parking Availability Message, PAM) can be transmitted and received via unicast and / or broadcast.

[0066] As an example of PAM, let's look at the POIM-PA (point of interest message - parking assistance) message.

[0067] Figure 6 illustrates an example of a POIM PDU.

[0068] Referring to FIG. 6, a POIM PDU (packet data unit) consists of a header and a payload, and the payload may include one or more Wrapped POI Information Blocks. Up to eight Wrapped POI Information Blocks may be included.

[0069] The Wrapped POI Information Block can be categorized into, but is not limited to, a Parking Availability Block, an Energy Supply Block, a Public Transport Block, or a Facility Topology Block, depending on the PoI Type. For example, PoI Types can be categorized as shown in Table 1.

[0070] parkingAvailability PoiType ::= 1energySupply PoiType ::= 2publicTransport PoiType ::= 3facilityTopology PoiType ::= 4

[0071] Referring to Table 1, the POI type indicating Parking Availability POI is defined as 1. Among the Wrapped POI Information Blocks, the Parking Availability Block is referred to as Parking Availability PDU.

[0072] Figure 7 illustrates an example of a Parking Availability PDU.

[0073] Referring to FIG. 7, the Parking Availability PDU may include at least one of a management header, a general parking place container, parking status, parking supply capabilities, and a related POI, each of which may be configured as a mandatory or optional container depending on the type and role of the data.

[0074] Table 2 illustrates the ASN.1 code for ParkingAvailabilityBlock.

[0075] ParkingAvailabilityBlock::= SEQUENCE{managementContainer PoiBlockManagementContainer,placeInfo GeneralParkingPlaceContainer,aggregatedstatus ParkingStatusContainer,detailedstatus ParkingSupplyCapabilitiesContainer OPTIONAL,relatedPoi RelatedPoiInfoBlockContainer OPTIONAL,...}

[0076] Table 3 illustrates the ASN.1 code of PoiBlockManagementContainer in Table 2.

[0077] PoiBlockManagementContainer::= SEQUENCE {serviceProviderId Provider,blockIdentificationNumber Identifier2B,timestamp TimestampIts,linkedIvims IvimReferences OPTIONAL,linkedMapems MapReferences OPTIONAL,...}

[0078] Table 4 illustrates the ASN.1 code of GeneralParkingPlaceContainer in Table 2.

[0079] GeneralParkingPlaceContainer::= SEQUENCE{position GeoPosition,name UTF8String (SIZE (1..31)),openingPeriods Periods OPTIONAL,address UTF8String (SIZE (1..255)) OPTIONAL,phoneNumber UTF8String (SIZE (1..31)) OPTIONAL,website UTF8String (SIZE (1..31)) OPTIONAL,...}

[0080] Table 5 illustrates the ASN.1 code of ParkingStatusContainer in Table 2.

[0081] ParkingStatusContainer::= SEQUENCE {currentFacilityStatus OpeningStatus,currentOccupancy OccupancyWithConfidence OPTIONAL,detailedStatus ParkingStatusList,...}

[0082] The ParkingStatusList in Table 5 consists of 1 to 16 ParkingStatus values. The ASN.1 codes for ParkingStatus are as shown in Table 6.

[0083] ParkingStatus ::= SEQUENCE {vehicleTypes SEQUENCE (SIZE(1..4,...)) OF EuVehicleCategoryCode OPTIONAL,reservationTypes SEQUENCE (SIZE(1..4,...)) OF ParkingReservationType OPTIONAL,loadTypes SEQUENCE (SIZE(1..4,...)) OF LoadType OPTIONAL,parkingFeeTypes SEQUENCE (SIZE(1..4,...)) OF ParkingFeeType OPTIONAL,occupancyTypes SEQUENCE (SIZE(1..4,...)) OF ParkingOccupancyInfo OPTIONAL,currentOccupancy OccupancyWithConfidence}

[0084] 표 2에서 ParkingSupplyCapabilitiesContainer의 ASN. 1 코드는 표 7과 같이 Parking Area의 sequence로 정의된다.

[0085] ParkingSupplyCapabilitiesContainer::= SEQUENCE OF ParkingAreasParkingArea::=SEQUENCE{id Identifier2B,currentOccupancy OccupancyWithConfidence,location GeoPosition,level INTEGER(-8..16,...) DEFAULT 0,arrangementType ParkingAreaArrangementType,boundary DeltaPositions OPTIONAL,orientation Wgs84Angle OPTIONAL,accessViaLane Identifier2B OPTIONAL,allowedVehicleCategories SEQUENCE (SIZE(1..4,...)) OF EuVehicleCategoryCode,notAllowedEngineCharacteristics SEQUENCE (SIZE(1..4,...)) OF EngineCharacteristics OPTIONAL,allowedLoadTypes SEQUENCE (SIZE(1..4,...)) OF LoadType OPTIONAL,notAllowedLoadTypes SEQUENCE (SIZE(1..4,...)) OF LoadType OPTIONAL,heightRestriction VehicleHeight OPTIONAL,reservationType SEQUENCE (SIZE(1..4,...)) OF ParkingReservationType OPTIONAL,pricingInformation UTF8String OPTIONAL,paymentInformation UTF8String OPTIONAL,bookingContactInfo UTF8String OPTIONAL,accessCharachteristics UTF8String OPTIONAL,freeSpacesPosition SEQUENCE OF DeltaPosition OPTIONAL,freespacesId SEQUENCE OF Identifier2B OPTIONAL,spacesBasic ParkingSpacesBasic OPTIONAL,spacesDetailed ParkingSpacesDetailed OPTIONAL,...}.

[0086] 표 2에서 RelatedPoiInfoBlockContainer의 ASN.1 코드는 표 8과 같이 RelatedPoiInfoBlock의 Sequence로 정의된다.

[0087] RelatedPoiInfoBlock::= SEQUENCE{poiInfoBlockType PoiType,serviceProviderId Provider,blockIdentificationNumber Identifier2B,timestamp TimestampIts OPTIONAL,...}

[0088] The POIM-PA message discussed above can contain information about parking availability in a specific parking area analyzed at a specific point in time by a road side unit (RSU) or a central ITS station (e.g., a Service Provider server, an OEM server, etc.). The POIM-PA message can contain parking availability information determined by a Parking Availability Application installed in the RSU or central ITS station, for example, parking availability information at the time the POIM-PA message was generated. Meanwhile, there may be vehicles that are not connected to the parking lot, and such vehicles may enter the parking lot to park without receiving the POIM-PA message. In this case, there is a problem that the parking lot may end up with more vehicles entering than the number of available parking spaces.

[0089] Alternatively, multiple connected vehicles may receive a POIM-PA message and the POIM-PA message may indicate that parking is available at a specific time, and the vehicles may enter the parking lot. However, a problem may arise where the number of vehicles entering exceeds the number of free spaces available for parking.

[0090] Additionally, even if the RSU determines that parking is not available in the current parking lot and sends a POIM-PA message, there may be a vehicle waiting in front of the parking lot to park in the parking lot.

[0091] Considering such various situations, this specification proposes a method of transmitting parking availability information through a POIM-PA message that can notify various problematic situations, such as when unconnected vehicles enter a parking lot while the parking lot's full occupancy is exceeded or when more vehicles enter the parking lot and are moving than the number of free spaces.

[0092] Additionally, this specification proposes to include information related to vehicles waiting to park in a parking lot in the POIM-PA message, regardless of whether the parking lot is available or not.

[0093] Proposal 1. Method of notifying when occupancy exceeds full capacity.

[0094] Figure 8 illustrates an example of a parking lot that is over occupant. Referring to Figure 8, while there are three free spaces available for parking, six vehicles have entered the parking lot and are attempting to move / park in search of a parking space, resulting in a parking lot over occupant capacity of three vehicles.

[0095] A device monitoring the status of a parking lot (e.g., RSU or Central ITS Station) may include information in the POIM-PA message indicating that more vehicles are currently attempting to move / park in the parking lot than there are free spaces available for parking, if the number of vehicles entering the parking lot and attempting to move / park in the parking lot is greater than the number of free spaces available for parking.

[0096] Specifically, as described through Table 2 and Table 5, the POIM-PA message includes a ParkingStatusContainer that indicates the Parking Status, and according to one embodiment, the ParkingStatusContainer can indicate that more vehicles are currently attempting to move / park in the parking lot than there are free spaces available for parking.

[0097] A device (e.g., an RSU or Central ITS Station) can monitor a parking lot to determine the number of available parking spaces. The number of available spaces can be compared with the number of vehicles entering the parking lot, and the corresponding information can be set in the message's ParkingStatusContainer.

[0098] Table 9 shows an example of ParkingStatusContainer according to Proposal 1.

[0099] ParkingStatusContainer::= SEQUENCE {currentFacilityStatus OpeningStatus,currentOccupancy OccupancyWithConfidence OPTIONAL,detailedStatus ParkingStatusList,exceededThanTotalSpaces INTEGER OPTIONAL,...}

[0100] Referring to Table 9, (i) the currentFacilityStatus field may include information about the current status of the parking lot, for example, whether it is open or not. (ii) the currentOccupancy field may indicate the current occupancy status of the entire parking lot and may be composed of optional fields. For example, the currentOccupancy field may be provided only when the parking lot consists of spaces of the same type (e.g., personal car parking spaces). (iii) the detailedStatus field may indicate detailed parking availability status. (iv) the exceededThanTotalSpaces field may indicate the number of vehicles exceeding the total spaces for parking when the number of vehicles entering the parking lot exceeds the total spaces for parking and may be composed of optional fields. For example, the exceededThanTotalSpaces field may be provided only when the parking lot consists of only spaces of the same type (e.g., personal car parking spaces). In this way, if the number of vehicles currently entering and moving in the parking lot is greater than the number of free spaces, a message notifying this can be provided to the connected vehicle. Even if the vehicle confirms that there are empty spaces in the parking lot through currentOccupancy, it can determine that more vehicles have already entered than free spaces before entering. Therefore, the problem of the vehicle entering the parking lot under the mistaken belief that parking is available can be solved.

[0101] Figure 9 is a diagram illustrating the operation of a first device transmitting a message containing information about parking availability according to Proposal 1. The first device is a device that monitors a parking lot, and may be, for example, an RSU or a Central ITS-S. The message may be formatted in the POIM-PA message format, but is not limited thereto.

[0102] Referring to FIG. 9, a first device can execute a parking availability application (601). The first device can determine the number of free spaces not occupied by vehicles and / or the number of spaces occupied by vehicles within a parking lot (602). By monitoring the parking lot, the first device can detect vehicles entering the parking lot and / or vehicles attempting to move / park within the parking lot (603).

[0103] The first device can compare the number of free spaces within the parking lot with the number of vehicles moving / attempting to park within the parking lot for parking (604). If the number of vehicles moving / attempting to park within the parking lot exceeds the number of free spaces, information about the number of vehicles exceeding the number can be included in a message and transmitted (605, 606).

[0104] Figure 10 is a diagram illustrating the operation of a second device receiving a message containing information about parking availability according to Proposal 1. The second device may be a vehicle or a device belonging to a user riding in the vehicle. For convenience of explanation, Figure 10 assumes that the number of vehicles moving or attempting to park within the parking lot exceeds the number of free spaces.

[0105] Referring to FIG. 10, a second device may execute a parking availability application (701). The second device may receive a message containing information related to parking availability (702). Based on the received message, the second device may obtain information regarding the number of vehicles exceeding the number of free spaces in the parking lot (703). Based on the number of vehicles exceeding the number of free spaces, the second device may determine whether to park in the parking lot (704).

[0106] Proposal 2. A method to inform vehicles waiting for parking and their waiting times.

[0107] Even if there are no available parking spaces in the parking lot, there may be vehicles waiting in the parking lot entrance aisle after a certain waiting period. Considering this, the POIM-PA message can provide information on the expected waiting time and the number of waiting vehicles. This information can be captured and acquired through monitoring sensors installed on devices such as RSUs installed near the parking lot.

[0108] As a specific example, information about the expected waiting time and waiting vehicles can be transmitted via the ParkingStatusContainer included in the POIM-PA message.

[0109] As explained in Table 2 and Table 5 above, ParkingStatusContainer is mandatory included in the POIM-PA message, and can indicate the current parking lot opening status, the occupancy status when the type of vehicle that can park in the parking lot is unified to one, and can include a list of detailed status information.

[0110] Table 10 shows an example of ParkingStatusContainer according to Proposal 2.

[0111] ParkingStatusContainer::= SEQUENCE {currentFacilityStatus OpeningStatus,currentOccupancy OccupancyWithConfidence OPTIONAL,detailedStatus ParkingStatusList,waitingInfo WaitingInfo OPTIONAL,...}WaitingInfo::= SEQUENCE {numOfWaitingVehicles INTEGER (0..10),expectedWaitingTime ExpectedWaitingTime (Or INTEGER) OPTIONAL,...}ExpectedWaitingTime::= ENUMERATED {Unknown (0),Less than 5min (1),5min~10min (2),10~30min (3),30min~1hour (4),More than 1hour(5)} (0..5)

[0112] Referring to Table 10, (i) the currentFacilityStatus field may include information about the current status of the parking lot, for example, whether it is open. (ii) the currentOccupancy field may indicate the current occupancy status of the entire parking lot and may be composed of optional fields. For example, the currentOccupancy field may be provided only when the parking lot consists of spaces of the same type (e.g., personal car parking spaces). (iii) the detailedStatus field may indicate detailed parking availability status. (iv) the waitingInfo field may provide information about waiting vehicles when the status of the currentOccupancy field is full. For example, the waitingInfo field is an optional field and may be provided only when the parking lot consists of spaces of the same type (e.g., personal car parking spaces). The waitingInfo field may include at least one of the subfields numOfWaitingVehicles and expectedWaitingTime. The numOfWaitingVehicles subfield can indicate the number of vehicles waiting to park in the parking lot. The expectedWaitingTime can indicate the expected waiting time from the first vehicle in the queue to parking. It can be expressed as a value defined in the ENUMERATED format or as an arbitrary integer representing the expected waiting time. If the ENUMERATED format is used for expectedWaitingTime and the RSU cannot calculate the expected waiting time, the expectedWaitingTime can be '0', indicating unknown.If an integer is used for expectedWaitingTime, the waiting time may be displayed in more precise minutes.

[0113] According to Proposal 2, even if a vehicle has to wait in a parking lot with no free space, it can be informed of the number of vehicles waiting and when the first vehicle in the queue can park through the POIM-PA message.

[0114] The ParkingStatusContainer in Proposal 2 can be configured separately from the ParkingStatusContainer in Proposal 1 or in combination. If Proposals 1 and 2 are implemented together, the ParkingStatusContainer can contain both exceededThanTotalSpaces in Proposal 1 and waitingInfo in Proposal 2.

[0115] Figure 11 is a diagram illustrating the operation of a first device transmitting a message containing information about parking availability according to Proposal 2. The first device is a device that monitors a parking lot, and may be, for example, an RSU or a Central ITS-S. The message may be formatted in a POIM-PA message format, but is not limited thereto.

[0116] Referring to FIG. 11, a first device can execute a parking availability application (801). The first device can determine the number of free spaces not occupied by vehicles and / or the number of spaces occupied by vehicles within a parking lot (802). By monitoring the parking lot, the first device can detect vehicles entering the parking lot and / or vehicles attempting to move / park within the parking lot (803).

[0117] The first device can determine whether there are vehicles waiting to park at the parking lot entrance (804). If there are vehicles waiting to park at the parking lot entrance, the first device can transmit a message including the number of vehicles waiting and the estimated time until parking becomes available (805, 806).

[0118] Figure 12 is a diagram illustrating the operation of a second device receiving a message containing information about parking availability according to Proposal 2. The second device may be a vehicle or a device of a user riding in the vehicle.

[0119] Referring to FIG. 12, a second device can execute a parking availability application (901). The second device can receive a message containing information related to parking availability (902). Based on the received message, the second device can determine the number of vehicles waiting to park at the parking lot entrance and the expected time until parking becomes available (903). Based on the number of vehicles waiting and the expected time until parking becomes available, the second device can determine whether to park in the parking lot (904).

[0120] Figure 13 illustrates a flowchart of a message transmission method according to one embodiment. In Figure 13, message transmission may be performed by a first device, and the first device may be an RSU (road side unit) monitoring the parking lot.

[0121] Referring to Figure 13, the first device can obtain information about a parking lot (A01). The obtained parking lot information may include information about unoccupied parking spaces within the parking lot and information about unparked vehicles among vehicles entering the parking lot.

[0122] The first device can transmit a message (A02) indicating whether parking is available in the parking lot based on the acquired parking space information. The message can include information regarding whether the number of unparked vehicles exceeds the number of unoccupied parking spaces.

[0123] The above message may include information about the number of excess vehicles based on whether the number of unparked vehicles exceeds the number of unoccupied parking spaces.

[0124] The information about the above parking lot may further include information about vehicles waiting to enter the above parking lot.

[0125] The above message may further include information about the number of vehicles waiting.

[0126] The above message may further include information regarding the expected waiting time required to enter the parking lot. The expected waiting time may be calculated based on the leading vehicle among the waiting vehicles.

[0127] Information about the number of vehicles waiting may be included in the message based on whether all parking spaces in the parking lot are occupied.

[0128] The above message may be a POIM-PA (point of interest message - parking assistance) message.

[0129] Fig. 14 illustrates a flowchart of a message receiving method according to one embodiment. In Fig. 14, message receiving may be performed by a second device, and the second device may be a vehicle.

[0130] The second device may receive a message from the first device (B01). The message may include information regarding whether the number of unparked vehicles entering the parking lot exceeds the number of unoccupied parking spaces within the parking lot.

[0131] The second device can determine whether parking is possible in the parking lot based on the above message (B02).

[0132] The above message may include information about the number of excess vehicles based on whether the number of unparked vehicles exceeds the number of unoccupied parking spaces.

[0133] The information about the above parking lot may further include information about vehicles waiting to enter the above parking lot.

[0134] The above message may further include information about the number of vehicles waiting.

[0135] The above message may further include information regarding the expected waiting time required to enter the parking lot. The expected waiting time may be calculated based on the lead vehicle among the waiting vehicles.

[0136] Information about the number of vehicles waiting may be included in the message based on whether all parking spaces in the parking lot are occupied.

[0137] The above message may be a POIM-PA (point of interest message - parking assistance) message.

[0138] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods and / or operational flowcharts of the present disclosure disclosed in this document may be applied to various fields requiring wireless communication / connectivity (e.g., 5G) between devices.

[0139] Hereinafter, more specific examples will be provided with reference to the drawings. In the drawings / descriptions below, the same drawing reference numerals may represent identical or corresponding hardware blocks, software blocks, or functional blocks, unless otherwise described.

[0140] Figure 15 illustrates a communication system applicable to this embodiment.

[0141] Referring to FIG. 15, a communication system (1) applicable to the present embodiment includes a wireless device, a base station, and a network. Here, the wireless device refers to a device that performs communication using a wireless access technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution)) and may be referred to as a communication / wireless / 5G device. Although not limited thereto, the wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (eXtended Reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Things) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing vehicle-to-vehicle communication, etc. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). XR devices include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, and can be implemented in the form of HMD (Head-Mounted Device), HUD (Head-Up Display) installed in a vehicle, television, smartphone, computer, wearable device, home appliance, digital signage, vehicle, robot, etc. Mobile devices can include smartphone, smart pad, wearable device (e.g., smart watch, smart glass), computer (e.g., laptop, etc.), etc. Home appliances can include TV, refrigerator, washing machine, etc. IoT devices can include sensors, smart meters, etc. For example, base stations and networks can also be implemented as wireless devices, and a specific wireless device (200a) can act as a base station / network node to other wireless devices.

[0142] Wireless devices (100a to 100f) can be connected to a network (300) via a base station (200). Artificial Intelligence (AI) technology can be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) via the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, etc. The wireless devices (100a to 100f) can communicate with each other via the base station (200) / network (300), but can also communicate directly (e.g., sidelink communication) without going through the base station / network. For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to Everything) communication). In addition, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0143] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a~100f) / base stations (200), and base stations (200) / base stations (200). Here, wireless communication / connection can be achieved through various wireless access technologies (e.g., 5G NR) such as uplink / downlink communication (150a), sidelink communication (150b) (or, D2D communication), and communication between base stations (150c) (e.g., relay, IAB (Integrated Access Backhaul). Through wireless communication / connection (150a, 150b, 150c), wireless devices and base stations / wireless devices, and base stations and base stations can transmit / receive wireless signals to each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, at least some of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes can be performed based on various proposals of the present disclosure.

[0144] Figure 16 illustrates a wireless device applicable to the present disclosure.

[0145] Referring to FIG. 16, the first wireless device (100) and the second wireless device (200) can transmit and receive wireless signals through various wireless access technologies (e.g., LTE, NR). Here, {the first wireless device (100), the second wireless device (200)} can correspond to {the wireless device (100x), the base station (200)} and / or {the wireless device (100x), the wireless device (100x)} of FIG. 27.

[0146] A first wireless device (100) includes one or more processors (102) and one or more memories (104), and may further include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memories (104) and / or the transceivers (106), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (102) may process information in the memory (104) to generate first information / signal, and then transmit a wireless signal including the first information / signal via the transceiver (106). In addition, the processor (102) may receive a wireless signal including second information / signal via the transceiver (106), and then store information obtained from signal processing of the second information / signal in the memory (104). The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may perform some or all of the processes controlled by the processor (102), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chipset designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). The transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In this specification, wireless device may also mean a communication modem / circuit / chipset.

[0147] Specifically, the UE may include a processor (102) and a memory (104) connected to the RF transceiver. The memory (104) may include at least one program capable of performing operations related to the embodiments described in FIGS. 15 to 27.

[0148] Alternatively, a chipset may be configured that includes a processor (102) and a memory (104). In this case, the chipset may include at least one processor and at least one memory operably connected to the at least one processor and, when executed, causing the at least one processor to perform operations.

[0149] The second wireless device (200) includes one or more processors (202), one or more memories (204), and may further include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memories (204) and / or the transceivers (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (202) may process information in the memory (204) to generate third information / signals, and then transmit a wireless signal including the third information / signals via the transceivers (206). Furthermore, the processor (202) may receive a wireless signal including fourth information / signals via the transceivers (206), and then store information obtained from signal processing of the fourth information / signals in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF unit. In this specification, a wireless device may also mean a communication modem / circuit / chip.

[0150] Hereinafter, the hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed herein, and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein.

[0151] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software configured to perform one or more processors (102, 202) or stored in one or more memories (104, 204) and executed by one or more processors (102, 202). The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions.

[0152] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0153] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or flowcharts of this document, to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts of this document, from one or more other devices. For example, one or more transceivers (106, 206) can be connected to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be coupled to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, or the like, as referred to in the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein, via one or more antennas (108, 208). In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202).One or more transceivers (106, 206) may convert user data, control information, wireless signals / channels, etc. processed by one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or filter.

[0154] Figure 17 illustrates another example of a wireless device applicable to this embodiment. The wireless device may be implemented in various forms depending on the use case / service.

[0155] Referring to FIG. 17, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 16 and may be composed of various elements, components, units / units, and / or modules. For example, the wireless device (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130), and additional elements (140). The communication unit may include a communication circuit (112) and a transceiver(s) (114). For example, the communication circuit (112) may include one or more processors (102, 202) and / or one or more memories (104, 204) of FIG. 17. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 16. The control unit (120) is electrically connected to the communication unit (110), the memory unit (130), and the additional elements (140) and controls the overall operation of the wireless device. For example, the control unit (120) may control the electrical / mechanical operation of the wireless device based on the program / code / command / information stored in the memory unit (130). In addition, the control unit (120) may transmit information stored in the memory unit (130) to an external device (e.g., another communication device) via a wireless / wired interface through the communication unit (110), or store information received from an external device (e.g., another communication device) via a wireless / wired interface in the memory unit (130).

[0156] The additional element (140) may be configured in various ways depending on the type of the wireless device. For example, the additional element (140) may include at least one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computing unit. Although not limited thereto, the wireless device may be implemented in the form of a robot (Fig. 15, 100a), a vehicle (Fig. 15, 100b-1, 100b-2), an XR device (Fig. 15, 100c), a portable device (Fig. 15, 100d), a home appliance (Fig. 15, 100e), an IoT device (Fig. 15, 100f), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or a financial device), a security device, a climate / environmental device, an AI server / device (Fig. 15, 400), a base station (Fig. 15, 200), a network node, etc. Wireless devices may be mobile or stationary depending on the use / service.

[0157] In FIG. 17, various elements, components, units / parts, and / or modules within the wireless device (100, 200) may be entirely interconnected via a wired interface, or at least some may be wirelessly connected via a communication unit (110). For example, within the wireless device (100, 200), the control unit (120) and the communication unit (110) may be wired, and the control unit (120) and a first unit (e.g., 130, 140) may be wirelessly connected via the communication unit (110). In addition, each element, component, unit / part, and / or module within the wireless device (100, 200) may further include one or more elements. For example, the control unit (120) may be composed of a set of one or more processors. For example, the control unit (120) may be composed of a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing processor, a memory control processor, etc. As another example, the memory unit (130) may be composed of RAM (Random Access Memory), DRAM (Dynamic RAM), ROM (Read Only Memory), flash memory, volatile memory, non-volatile memory, and / or a combination thereof.

[0158] Figure 18 illustrates a vehicle or autonomous vehicle applicable to this embodiment. The vehicle or autonomous vehicle may be implemented as a mobile robot, a car, a train, a manned or unmanned aerial vehicle (AV), a ship, etc.

[0159] Referring to FIG. 18, a vehicle or autonomous vehicle (100) may include an antenna unit (108), a communication unit (110), a control unit (120), a driving unit (140a), a power supply unit (140b), a sensor unit (140c), and an autonomous driving unit (140d). The antenna unit (108) may be configured as a part of the communication unit (110). Blocks 110 / 130 / 140a to 140d correspond to blocks 110 / 130 / 140 of FIG. 16, respectively.

[0160] The communication unit (110) can transmit and receive signals (e.g., data, control signals, etc.) with external devices such as other vehicles, base stations (e.g., base stations, road side units, etc.), and servers. The control unit (120) can control elements of the vehicle or autonomous vehicle (100) to perform various operations. The control unit (120) can include an ECU (Electronic Control Unit). The drive unit (140a) can drive the vehicle or autonomous vehicle (100) on the ground. The drive unit (140a) can include an engine, a motor, a power train, wheels, brakes, a steering device, etc. The power supply unit (140b) supplies power to the vehicle or autonomous vehicle (100) and can include a wired / wireless charging circuit, a battery, etc. The sensor unit (140c) can obtain vehicle status, surrounding environment information, user information, etc. The sensor unit (140c) may include an IMU (inertial measurement unit) sensor, a collision sensor, a wheel sensor, a speed sensor, an incline sensor, a weight detection sensor, a heading sensor, a position module, a vehicle forward / backward sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illuminance sensor, a pedal position sensor, etc. The autonomous driving unit (140d) may implement a technology for maintaining a driving lane, a technology for automatically controlling speed such as adaptive cruise control, a technology for automatically driving along a set path, a technology for automatically setting a path and driving when a destination is set, etc.

[0161] For example, the communication unit (110) can receive map data, traffic information data, etc. from an external server. The autonomous driving unit (140d) can generate an autonomous driving route and driving plan based on the acquired data. The control unit (120) can control the drive unit (140a) so that the vehicle or autonomous vehicle (100) moves along the autonomous driving route according to the driving plan (e.g., speed / direction control). During autonomous driving, the communication unit (110) can irregularly / periodically acquire the latest traffic information data from an external server and can acquire surrounding traffic information data from surrounding vehicles. In addition, during autonomous driving, the sensor unit (140c) can acquire vehicle status and surrounding environment information. The autonomous driving unit (140d) can update the autonomous driving route and driving plan based on newly acquired data / information. The communication unit (110) can transmit information regarding the vehicle location, autonomous driving route, driving plan, etc. to the external server. External servers can predict traffic information data in advance using AI technology or other technologies based on information collected from vehicles or autonomous vehicles, and provide the predicted traffic information data to the vehicles or autonomous vehicles.

[0162] Here, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification may include not only LTE, NR, and 6G, but also Narrowband Internet of Things for low-power communication. At this time, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification may perform communication based on LTE-M technology. At this time, for example, LTE-M technology may be an example of LPWAN technology, and may be called by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology can be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification can include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create PAN (personal area networks) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.

[0163] The embodiments described above are combinations of components and features of the present disclosure in a predetermined form. Each component or feature should be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, it is also possible to form embodiments of the present disclosure by combining some components and / or features. The order of operations described in the embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment. It is self-evident that claims that do not have an explicit citation relationship in the patent claims may be combined to form embodiments or incorporated as new claims through post-application amendments.

[0164] In this document, the embodiments of the present disclosure have been described primarily focusing on the signal transmission and reception relationship between a terminal and a base station. This transmission and reception relationship is equally / similarly extended to signal transmission and reception between a terminal and a relay or a base station and a relay. Certain operations described as being performed by a base station in this document may, in some cases, be performed by its upper node. That is, it is obvious that various operations performed for communication with a terminal in a network composed of multiple network nodes including a base station may be performed by the base station or other network nodes other than the base station. The base station may be replaced by terms such as a fixed station, a Node B, an eNode B (eNB), an access point, etc. The terminal may also be replaced by terms such as a User Equipment (UE), a Mobile Station (MS), or a Mobile Subscriber Station (MSS).

[0165] Embodiments according to the present disclosure may be implemented by various means, for example, hardware, firmware, software, or a combination thereof. In the case of hardware implementation, an embodiment of the present disclosure may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, etc.

[0166] When implemented via firmware or software, one embodiment of the present disclosure may be implemented in the form of a module, procedure, function, or the like that performs the functions or operations described above. The software code may be stored in a memory unit and executed by a processor. The memory unit may be located within or outside the processor and may exchange data with the processor via various known means.

[0167] It will be apparent to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the technical features described herein. Therefore, the above detailed description should not be construed as limiting in any respect, but rather as illustrative. The scope of the present invention should be determined by a reasonable interpretation of the appended claims, and all modifications within the scope of equivalents of the present invention are intended to be included within the scope of the present invention.

[0168] The embodiments of the present disclosure as described above can be applied to various devices of an intelligent transportation system.

Claims

1. In a method for transmitting a message by a first device in a wireless communication system, Obtain information about parking lots; and Including transmitting a message notifying whether parking is available in the parking lot based on the information about the acquired parking lot, The information about the above-obtained parking lot includes information about unoccupied parking spaces within the parking lot and information about unparked vehicles among the vehicles that entered the parking lot. A method wherein the message includes information regarding whether the number of unparked vehicles exceeds the number of unoccupied parking spaces.

2. In paragraph 1, A method wherein the message includes information about the excess number of vehicles based on whether the number of unparked vehicles exceeds the number of unoccupied parking spaces.

3. In paragraph 1, A method wherein the information about the parking lot further includes information about vehicles waiting to enter the parking lot.

4. In paragraph 3, A method wherein the above message further includes information about the number of vehicles waiting.

5. In paragraph 3, A method wherein the message further includes information about an expected waiting time required to enter the parking lot.

6. In paragraph 5, A method wherein the above expected waiting time is calculated based on the leading vehicle among the waiting vehicles.

7. In paragraph 3, A method wherein information about the number of vehicles waiting is included in the message based on whether all parking spaces in the parking lot are occupied.

8. In paragraph 1, A method wherein the first device is an RSU (road side unit) that monitors the parking lot.

9. In paragraph 1, The above message is a POIM-PA (point of interest message - parking assistance) message.

10. A non-transitory computer-readable recording medium having recorded thereon a program for performing the method described in paragraph 1.

11. In a first device in a wireless communication system, At least one memory configured to store instructions; and At least one processor configured to perform operations by executing the above instructions, The operations performed by at least one processor are: Obtain information about parking lots; and Including transmitting a message notifying whether parking is available in the parking lot based on the information about the acquired parking lot, The information about the above-obtained parking lot includes information about unoccupied parking spaces within the parking lot and information about unparked vehicles among the vehicles that entered the parking lot. The first device, wherein the message includes information regarding whether the number of unparked vehicles exceeds the number of unoccupied parking spaces.

12. In paragraph 11, The above first device further comprises a transmitter and receiver, The first device is a road side unit (RSU) that monitors the parking lot.

13. In a method for a second device to receive a message in a wireless communication system, Receive a message from the first device; and Including determining whether parking is available in the parking lot based on the above message, A method wherein the message includes information regarding whether the number of unparked vehicles among the vehicles entering the parking lot exceeds the number of unoccupied parking spaces within the parking lot.

14. In a second device in a wireless communication system, At least one memory configured to store instructions; and At least one processor configured to perform operations by executing the above instructions, The operations performed by at least one processor are: Receive a message from the first device; and Including determining whether parking is available in the parking lot based on the above message, A second device, wherein the message includes information regarding whether the number of unparked vehicles among the vehicles entering the parking lot exceeds the number of unoccupied parking spaces within the parking lot.

15. In paragraph 14, The second device further comprises a transmitter and receiver, The second device is a vehicle.

Citation Information

Patent Citations

  • Method for using vehicles of parking lot as resource of datacenter

    KR101957343B1

  • Method for navigation service using of car driving information and car navigation system of that

    KR1020090074907A

  • Two-way traffic information collecting system and method thereof

    KR102155753B1

  • System that collects and analyzes vehicle driving-related data in parking lot

    KR102479938B1

  • KR20210089409A