EP3780902B1 - Procédé de transmission de données v2x dans un système de communication sans fil et dispositif associé - Google Patents

Procédé de transmission de données v2x dans un système de communication sans fil et dispositif associé Download PDF

Info

Publication number
EP3780902B1
EP3780902B1 EP19799655.6A EP19799655A EP3780902B1 EP 3780902 B1 EP3780902 B1 EP 3780902B1 EP 19799655 A EP19799655 A EP 19799655A EP 3780902 B1 EP3780902 B1 EP 3780902B1
Authority
EP
European Patent Office
Prior art keywords
service
direct communication
request message
communication request
data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP19799655.6A
Other languages
German (de)
English (en)
Other versions
EP3780902A1 (fr
EP3780902A4 (fr
Inventor
Laeyoung Kim
Sungduck Chun
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
LG Electronics Inc
Original Assignee
LG Electronics Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by LG Electronics Inc filed Critical LG Electronics Inc
Publication of EP3780902A1 publication Critical patent/EP3780902A1/fr
Publication of EP3780902A4 publication Critical patent/EP3780902A4/fr
Application granted granted Critical
Publication of EP3780902B1 publication Critical patent/EP3780902B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/04—Protocols for data compression, e.g. ROHC
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/022—Selective call receivers
    • H04W88/023—Selective call receivers with message or information receiving capability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/005—Moving wireless networks

Definitions

  • the following description relates to a wireless communication system, and more particularly, to a method and apparatus for efficiently processing optimized PC5 transmission for V2X services.
  • a wireless communication system is a multiple access system that supports communication of multiple users by sharing available system resources (a bandwidth, transmission power, etc.) among them.
  • multiple access systems include a code division multiple access (CDMA) system, a frequency division multiple access (FDMA) system, a time division multiple access (TDMA) system, an orthogonal frequency division multiple access (OFDMA) system, a single carrier frequency division multiple access (SC-FDMA) system, and a multi-carrier frequency division multiple access (MC-FDMA) system.
  • CDMA code division multiple access
  • FDMA frequency division multiple access
  • TDMA time division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single carrier frequency division multiple access
  • MC-FDMA multi-carrier frequency division multiple access
  • 5G technology is among the RATs.
  • Three major requirement categories for 5G include (1) a category of enhanced mobile broadband (eMBB), (2) a category of massive machine type communication (mMTC), and (3) a category of ultra-reliable and low latency communications (URLLC).
  • eMBB enhanced mobile broadband
  • mMTC massive machine type communication
  • URLLC ultra-reliable and low latency communications
  • Some use cases may require a plurality of categories for optimization and other use cases may focus only upon one key performance indicator (KPI).
  • KPI key performance indicator
  • eMBB far surpasses basic mobile Internet access and covers abundant bidirectional work and media and entertainment applications in cloud and augmented reality.
  • Data is one of 5G core motive forces and, in a 5G era, a dedicated voice service may not be provided for the first time.
  • voice will be simply processed as an application program using data connection provided by a communication system.
  • Main causes for increased traffic volume are an increase in the size of content and an increase in the number of applications requiring high data transmission rate.
  • a streaming service (of audio and video), conversational video, and mobile Internet access will be more widely used as more devices are connected to the Internet.
  • Cloud storage and applications are rapidly increasing in a mobile communication platform and may be applied to both work and entertainment.
  • the cloud storage is a special use case which accelerates growth of uplink data transmission rate.
  • 5G is also used for remote work of cloud. When a tactile interface is used, 5G demands much lower end-to-end latency to maintain user good experience.
  • Entertainment for example, cloud gaming and video streaming, is another core element which increases demand for mobile broadband capability. Entertainment is essential for a smartphone and a tablet in any place including high mobility environments such as a train, a vehicle, and an airplane.
  • Other use cases are augmented reality for entertainment and information search. In this case, the augmented reality requires very low latency and instantaneous data volume.
  • one of the most expected 5G use cases relates a function capable of smoothly connecting embedded sensors in all fields, i.e., mMTC. It is expected that the number of potential IoT devices will reach 204 hundred million up to the year of 2020.
  • An industrial IoT is one of categories of performing a main role enabling a smart city, asset tracking, smart utility, agriculture, and security infrastructure through 5G.
  • URLLC includes a new service that will change industry through remote control of main infrastructure and an ultra-reliable/available low-latency link such as a selfdriving vehicle.
  • a level of reliability and latency is essential to control a smart grid, automatize industry, achieve robotics, and control and adjust a drone.
  • 5G is a means of providing streaming evaluated as a few hundred megabits per second to gigabits per second and may complement fiber-to-the-home (FTTH) and cable-based broadband (or DOCSIS). Such fast speed is needed to deliver TV in resolution of 4K or more (6K, 8K, and more), as well as virtual reality and augmented reality.
  • Virtual reality (VR) and augmented reality (AR) applications include almost immersive sports games.
  • a specific application program may require a special network configuration. For example, for VR games, gaming companies need to incorporate a core server into an edge network server of a network operator in order to minimize latency.
  • Automotive is expected to be a new important motivated force in 5G together with many use cases for mobile communication for vehicles. For example, entertainment for passengers requires high simultaneous capacity and mobile broadband with high mobility. This is because future users continue to expect connection of high quality regardless of their locations and speeds.
  • Another use case of an automotive field is an AR dashboard.
  • the AR dashboard causes a driver to identify an object in the dark in addition to an object seen from a front window and displays a distance from the object and a movement of the object by overlapping information talking to the driver.
  • a wireless module enables communication between vehicles, information exchange between a vehicle and supporting infrastructure, and information exchange between a vehicle and other connected devices (e.g., devices accompanied by a pedestrian).
  • a safety system guides alternative courses of a behavior so that a driver may drive more safely drive, thereby lowering the danger of an accident.
  • the next stage will be a remotely controlled or self-driven vehicle. This requires very high reliability and very fast communication between different self-driven vehicles and between a vehicle and infrastructure. In the future, a self-driven vehicle will perform all driving activities and a driver will focus only upon abnormal traffic that the vehicle cannot identify.
  • Technical requirements of a self-driven vehicle demand ultra-low latency and ultra-high reliability so that traffic safety is increased to a level that cannot be achieved by human being.
  • a smart city and a smart home mentioned as a smart society will be embedded in a high-density wireless sensor network.
  • a distributed network of an intelligent sensor will identify conditions for costs and energy-efficient maintenance of a city or a home. Similar configurations may be performed for respective households. All of temperature sensors, window and heating controllers, burglar alarms, and home appliances are wirelessly connected. Many of these sensors are typically low in data transmission rate, power, and cost. However, real-time HD video may be demanded by a specific type of device to perform monitoring.
  • the smart grid collects information and connects the sensors to each other using digital information and communication technology so as to act according to the collected information. Since this information may include behaviors of a supply company and a consumer, the smart grid may improve distribution of fuels such as electricity by a method having efficiency, reliability, economic feasibility, production sustainability, and automation.
  • the smart grid may also be regarded as another sensor network having low latency.
  • a communication system may support remote treatment that provides clinical treatment in a faraway place. Remote treatment may aid in reducing a barrier against distance and improve access to medical services that cannot be continuously available in a faraway rural area. Remote treatment is also used to perform important treatment and save lives in an emergency situation.
  • the wireless sensor network based on mobile communication may provide remote monitoring and sensors for parameters such as heart rate and blood pressure.
  • Wireless and mobile communication gradually becomes important in the field of an industrial application.
  • Wiring is high in installation and maintenance cost. Therefore, a possibility of replacing a cable with reconstructible wireless links is an attractive opportunity in many industrial fields.
  • it is necessary for wireless connection to be established with latency, reliability, and capacity similar to those of the cable and management of wireless connection needs to be simplified. Low latency and a very low error probability are new requirements when connection to 5G is needed.
  • Logistics and freight tracking are important use cases for mobile communication that enables inventory and package tracking anywhere using a location-based information system.
  • the use cases of logistics and freight typically demand low data rate but require location information with a wide range and reliability.
  • US 2017/093541 A1 discloses a method and apparatus for a relay UE to receive packets from an eNB where the relay UE acts as a relay for forwarding the packets between a remote UE and the eNB.
  • the method includes the relay UE connecting with the eNB.
  • the method further includes the relay UE being configured with a radio bearer between the relay UE and the eNB.
  • the method also includes the relay UE receiving a downlink packet on the radio bearer from the eNB, wherein the downlink packet is to be transmitted to the remote UE.
  • the method includes the relay UE not transmitting any resource request to the eNB for requesting a SL grant for transmission of a sidelink packet including the downlink packet when the sidelink packet becomes available for transmission and there is currently no data available for transmission to the remote UE. Furthermore, the method includes the relay UE receiving the SL grant from the eNB. Also, the method includes the relay UE using the SL grant to transmit the sidelink packet to the remote UE.
  • WO 2018/016157 A1 discloses a transmitting device for transmitting vehicular data via a sidelink interface to one or more receiving devices.
  • the transmitting device performs autonomous radio resource allocation for transmitting the vehicular data via the sidelink interface.
  • An application layer generates the vehicular data and forwards the vehicular data together with a priority indication and one or more quality of service parameters to a transmission layer responsible for transmission of the vehicular data via the sidelink interface.
  • the transmission layer performs autonomous radio resource allocation based on the received priority indication and the one or more quality of service parameters.
  • the transmission layer transmits the vehicular data via the sidelink interface to the one or more receiving devices according to the performed autonomous radio resource allocation
  • the present invention is directed to a method and apparatus for transmitting V2X data in a wireless communication system that substantially obviate one or more problems due to limitations and disadvantages of the related art.
  • An object of the present invention lies on a method for efficiently performing unicast transmission to each of terminals desiring to receive a V2X service after performing a broadcast transmission to a plurality of terminals.
  • each component or feature may be considered as selective unless explicitly mentioned as otherwise.
  • Each component or feature may be executed in a form that is not combined with other components and features. Further, some components and/or features may be combined to configure an embodiment of the present invention. The order of operations described in the embodiments of the present invention may be changed. Some components or features of an embodiment may be included in another embodiment or may be substituted with a corresponding component or feature of the present invention.
  • the embodiments of the present invention may be supported by standard documents disclosed with respect to at least one of IEEE (Institute of Electrical and Electronics Engineers) 802 group system, 3GPP system, 3GPP LTE & LTE-A system and 3GPP2 system. Namely, the steps or portions having not been described in order to clarify the technical concept of the present invention in the embodiments of the present invention may be supported by the above documents. Furthermore, all terms disclosed in the present document may be described according to the above standard documents.
  • the technology below may be used for various wireless communication systems.
  • the description below centers on 3GPP LTE and 3GPP LTE-A, by which the technical idea of the present invention is not limited.
  • FIG. 1 is a schematic diagram showing the structure of an evolved packet system (EPS) including an evolved packet core (EPC).
  • EPS evolved packet system
  • EPC evolved packet core
  • the EPC is a core element of system architecture evolution (SAE) for improving performance of 3GPP technology.
  • SAE corresponds to a research project for determining a network structure supporting mobility between various types of networks.
  • SAE aims to provide an optimized packet-based system for supporting various radio access technologies and providing an enhanced data transmission capability.
  • the EPC is a core network of an IP mobile communication system for 3GPP LTE and can support real-time and non-real-time packet-based services.
  • functions of a core network are implemented through a circuit-switched (CS) sub-domain for voice and a packet-switched (PS) sub-domain for data.
  • CS and PS sub-domains are unified into one IP domain.
  • connection of terminals having IP capability can be established through an IP-based business station (e.g., an eNodeB (evolved Node B)), EPC, and an application domain (e.g., IMS).
  • an IP-based business station e.g., an eNodeB (evolved Node B)
  • EPC electronic circuitry
  • IMS application domain
  • the EPC may include various components.
  • FIG. 1 shows some of the components, namely, a serving gateway (SGW), a packet data network gateway (PDN GW), a mobility management entity (MME), a serving GPRS (general packet radio service) supporting node (SGSN) and an enhanced packet data gateway (ePDG).
  • SGW serving gateway
  • PDN GW packet data network gateway
  • MME mobility management entity
  • SGSN serving GPRS (general packet radio service) supporting node
  • ePDG enhanced packet data gateway
  • SGW (or S-GW) operates as a boundary point between a radio access network (RAN) and a core network and maintains a data path between an eNodeB and the PDN GW.
  • RAN radio access network
  • the SGW functions as a local mobility anchor point. That is, packets. That is, packets may be routed through the SGW for mobility in an evolved UMTS terrestrial radio access network (E-UTRAN) defined after 3GPP release-8.
  • E-UTRAN evolved UMTS terrestrial radio access network
  • the SGW may serve as an anchor point for mobility of another 3GPP network (a RAN defined before 3GPP release-8, e.g., UTRAN or GERAN (global system for mobile communication (GSM)/enhanced data rates for global evolution (EDGE) radio access network).
  • a RAN defined before 3GPP release-8 e.g., UTRAN or GERAN (global system for mobile communication (GSM)/enhanced data rates for global evolution (EDGE) radio access network).
  • GSM global system for mobile communication
  • EDGE enhanced data rates for global evolution
  • the PDN GW corresponds to a termination point of a data interface for a packet data network.
  • the PDN GW may support policy enforcement features, packet filtering and charging support.
  • the PDN GW may serve as an anchor point for mobility management with a 3GPP network and a non-3GPP network (e.g., an unreliable network such as an interworking wireless local area network (I-WLAN) and a reliable network such as a code division multiple access (CDMA) or WiMax network).
  • I-WLAN interworking wireless local area network
  • CDMA code division multiple access
  • the SGW and the PDN GW are configured as separate gateways in the example of the network structure of FIG. 1 , the two gateways may be implemented according to a single gateway configuration option.
  • the MME performs signaling and control functions for supporting access of a UE for network connection, network resource allocation, tracking, paging, roaming and handover.
  • the MME controls control plane functions associated with subscriber and session management.
  • the MME manages numerous eNodeBs and signaling for selection of a conventional gateway for handover to other 2G/3G networks.
  • the MME performs security procedures, terminal-to-network session handling, idle terminal location management, etc.
  • the SGSN handles all packet data such as mobility management and authentication of a user for other 3GPP networks (e.g., a GPRS network).
  • 3GPP networks e.g., a GPRS network
  • the ePDG serves as a security node for a non-3GPP network (e.g., an I-WLAN, a Wi-Fi hotspot, etc.).
  • a non-3GPP network e.g., an I-WLAN, a Wi-Fi hotspot, etc.
  • a terminal having IP capabilities may access an IP service network (e.g., an IMS) provided by an operator via various elements in the EPC not only based on 3GPP access but also based on non-3GPP access.
  • IP service network e.g., an IMS
  • FIG. 1 shows various reference points (e.g. S1-U, S1-MME, etc.).
  • a conceptual link connecting two functions of different functional entities of an E-UTRAN and an EPC is defined as a reference point.
  • Table 1 is a list of the reference points shown in FIG. 1 .
  • Various reference points may be present in addition to the reference points in Table 1 according to network structures.
  • TABLE 1 Reference point Description S1-MME Reference point for the control plane protocol between E-UTRAN and MME S1-U Reference point between E-UTRAN and Serving GW for the per bearer user plane tunneling and inter eNodeB path switching during handover S3 It enables user and bearer information exchange for inter 3GPP access network mobility in idle and/or active state.
  • This reference point can be used intra-PLMN or inter-PLMN (e.g. in the case of Inter-PLMN HO).
  • S4 It provides related control and mobility support between GPRS Core and the 3GPP Anchor function of Serving GW. In addition, if Direct Tunnel is not established, it provides the user plane tunneling.
  • S5 It provides user plane tunneling and tunnel management between Serving GW and PDN GW. It is used for Serving GW relocation due to UE mobility and if the Serving GW needs to connect to a non-collocated PDN GW for the required PDN connectivity.
  • S11 Reference point between an MME and an SGW SGi It is the reference point between the PDN GW and the packet data network. Packet data network may be an operator external public or private packet data network or an intra operator packet data network, e.g. for provision of IMS services. This reference point corresponds to Gi for 3GPP accesses.
  • S2a and S2b correspond to non-3GPP interfaces.
  • S2a is a reference point which provides reliable non-3GPP access and related control and mobility support between PDN GWs to a user plane.
  • S2b is a reference point which provides related control and mobility support between the ePDG and the PDN GW to the user plane.
  • FIG. 2 is a diagram exemplarily illustrating architectures of a typical E-UTRAN and EPC.
  • an eNodeB may perform routing to a gateway, scheduling transmission of a paging message, scheduling and transmission of a broadcast channel (BCH), dynamic allocation of resources to a UE on uplink and downlink, configuration and provision of eNodeB measurement, radio bearer control, radio admission control, and connection mobility control.
  • RRC radio resource control
  • BCH broadcast channel
  • paging generation LTE_IDLE state management
  • ciphering of the user plane ciphering of the user plane
  • SAE bearer control and ciphering and integrity protection of NAS signaling.
  • FIG. 3 is a diagram exemplarily illustrating the structure of a radio interface protocol in a control plane between a UE and a base station
  • FIG. 4 is a diagram exemplarily illustrating the structure of a radio interface protocol in a user plane between the UE and the base station.
  • the radio interface protocol is based on the 3GPP wireless access network standard.
  • the radio interface protocol horizontally includes a physical layer, a data link layer, and a networking layer.
  • the radio interface protocol is divided into a user plane for transmission of data information and a control plane for delivering control signaling which are arranged vertically.
  • the protocol layers may be classified into a first layer (L1), a second layer (L2), and a third layer (L3) based on the three sublayers of the open system interconnection (OSI) model that is well known in the communication system.
  • OSI open system interconnection
  • the physical layer which is the first layer, provides an information transfer service using a physical channel.
  • the physical channel layer is connected to a medium access control (MAC) layer, which is a higher layer of the physical layer, through a transport channel.
  • MAC medium access control
  • Data is transferred between the physical layer and the MAC layer through the transport channel. Transfer of data between different physical layers, i.e., a physical layer of a transmitter and a physical layer of a receiver is performed through the physical channel.
  • the physical channel consists of a plurality of subframes in the time domain and a plurality of subcarriers in the frequency domain.
  • One subframe consists of a plurality of symbols in the time domain and a plurality of subcarriers.
  • One subframe consists of a plurality of resource blocks.
  • One resource block consists of a plurality of symbols and a plurality of subcarriers.
  • a Transmission Time Interval (TTI) a unit time for data transmission, is 1 ms, which corresponds to one subframe.
  • the physical channels present in the physical layers of the transmitter and the receiver may be divided into data channels corresponding to Physical Downlink Shared Channel (PDSCH) and Physical Uplink Shared Channel (PUSCH) and control channels corresponding to Physical Downlink Control Channel (PDCCH), Physical Control Format Indicator Channel (PCFICH), Physical Hybrid-ARQ Indicator Channel (PHICH) and Physical Uplink Control Channel (PUCCH).
  • PDSCH Physical Downlink Shared Channel
  • PUSCH Physical Uplink Shared Channel
  • PCFICH Physical Control Format Indicator Channel
  • PHICH Physical Hybrid-ARQ Indicator Channel
  • PUCCH Physical Uplink Control Channel
  • the second layer includes various layers.
  • the MAC layer in the second layer serves to map various logical channels to various transport channels and also serves to map various logical channels to one transport channel.
  • the MAC layer is connected with an RLC layer, which is a higher layer, through a logical channel.
  • the logical channel is broadly divided into a control channel for transmission of information of the control plane and a traffic channel for transmission of information of the user plane according to the types of transmitted information.
  • the radio link control (RLC) layer in the second layer serves to segment and concatenate data received from a higher layer to adjust the size of data such that the size is suitable for a lower layer to transmit the data in a radio interval.
  • RLC radio link control
  • the Packet Data Convergence Protocol (PDCP) layer in the second layer performs a header compression function of reducing the size of an IP packet header which has a relatively large size and contains unnecessary control information, in order to efficiently transmit an IP packet such as an IPv4 or IPv6 packet in a radio interval having a narrow bandwidth.
  • the PDCP layer also performs a security function, which consists of ciphering for preventing a third party from monitoring data and integrity protection for preventing data manipulation by a third party.
  • the Radio Resource Control (RRC) layer which is located at the uppermost part of the third layer, is defined only in the control plane, and serves to configure radio bearers (RBs) and control a logical channel, a transport channel, and a physical channel in relation to reconfiguration and release operations.
  • the RB represents a service provided by the second layer to ensure data transfer between a UE and the E-UTRAN.
  • the UE If an RRC connection is established between the RRC layer of the UE and the RRC layer of a wireless network, the UE is in the RRC Connected mode. Otherwise, the UE is in the RRC Idle mode.
  • the RRC state refers to a state in which the RRC of the UE is or is not logically connected with the RRC of the E-UTRAN.
  • the RRC state of the UE having logical connection with the RRC of the E-UTRAN is referred to as an RRC_CONNECTED state.
  • the RRC state of the UE which does not have logical connection with the RRC of the E-UTRAN is referred to as an RRC_IDLE state.
  • a UE in the RRC_CONNECTED state has RRC connection, and thus the E-UTRAN may recognize presence of the UE in a cell unit. Accordingly, the UE may be efficiently controlled.
  • the E-UTRAN cannot recognize presence of a UE which is in the RRC_IDLE state.
  • the UE in the RRC_IDLE state is managed by a core network in a tracking area (TA) which is an area unit larger than the cell. That is, for the UE in the RRC_IDLE state, only presence or absence of the UE is recognized in an area unit larger than the cell.
  • TA tracking area
  • a TA is distinguished from another TA by a tracking area identity (TAI) thereof.
  • a UE may configure the TAI through a tracking area code (TAC), which is information broadcast from a cell.
  • TAI tracking area identity
  • the UE When the user initially turns on the UE, the UE searches for a proper cell first. Then, the UE establishes RRC connection in the cell and registers information thereabout in the core network. Thereafter, the UE stays in the RRC_IDLE state. When necessary, the UE staying in the RRC_IDLE state selects a cell (again) and checks system information or paging information. This operation is called camping on a cell. Only when the UE staying in the RRC_IDLE state needs to establish RRC connection, does the UE establish RRC connection with the RRC layer of the E-UTRAN through the RRC connection procedure and transition to the RRC_CONNECTED state. The UE staying in the RRC_IDLE state needs to establish RRC connection in many cases. For example, the cases may include an attempt of a user to make a phone call, an attempt to transmit data, or transmission of a response message after reception of a paging message from the E-UTRAN.
  • the non-access stratum (NAS) layer positioned over the RRC layer performs functions such as session management and mobility management.
  • the eSM evolved Session Management
  • the eSM belongs to the NAS layer performs functions such as default bearer management and dedicated bearer management to control a UE to use a PS service from a network.
  • the UE is assigned a default bearer resource by a specific packet data network (PDN) when the UE initially accesses the PDN.
  • PDN packet data network
  • the network allocates an available IP to the UE to allow the UE to use a data service.
  • the network also allocates QoS of a default bearer to the UE.
  • LTE supports two kinds of bearers.
  • One bearer is a bearer having characteristics of guaranteed bit rate (GBR) QoS for guaranteeing a specific bandwidth for transmission and reception of data
  • the other bearer is a non-GBR bearer which has characteristics of best effort QoS without guaranteeing a bandwidth.
  • the default bearer is assigned to a non-GBR bearer.
  • the dedicated bearer may be assigned a bearer having QoS characteristics of GBR or non-GBR.
  • a bearer allocated to the UE by the network is referred to as an evolved packet service (EPS) bearer.
  • EPS evolved packet service
  • the network assigns one ID. This ID is called an EPS bearer ID.
  • One EPS bearer has QoS characteristics of a maximum bit rate (MBR) and/or a guaranteed bit rate (GBR).
  • FIG. 5 is a flowchart illustrating a random access procedure in 3GPP LTE.
  • the random access procedure is used for a UE to obtain UL synchronization with an eNB or to be assigned a UL radio resource.
  • the UE receives a root index and a physical random access channel (PRACH) configuration index from an eNodeB.
  • PRACH physical random access channel
  • Each cell has 64 candidate random access preambles defined by a Zadoff-Chu (ZC) sequence.
  • the root index is a logical index used for the UE to generate 64 candidate random access preambles.
  • Transmission of a random access preamble is limited to a specific time and frequency resources for each cell.
  • the PRACH configuration index indicates a specific subframe and preamble format in which transmission of the random access preamble is possible.
  • the UE transmits a randomly selected random access preamble to the eNodeB.
  • the UE selects a random access preamble from among 64 candidate random access preambles and the UE selects a subframe corresponding to the PRACH configuration index.
  • the UE transmits the selected random access preamble in the selected subframe.
  • the eNodeB Upon receiving the random access preamble, the eNodeB sends a random access response (RAR) to the UE.
  • the RAR is detected in two steps. First, the UE detects a PDCCH masked with a random access (RA)-RNTI. The UE receives an RAR in a MAC (medium access control) PDU (protocol data unit) on a PDSCH indicated by the detected PDCCH.
  • RA random access
  • FIG. 6 illustrates a connection procedure in a radio resource control (RRC) layer.
  • RRC radio resource control
  • the RRC state is set according to whether or not RRC connection is established.
  • An RRC state indicates whether or not an entity of the RRC layer of a UE has logical connection with an entity of the RRC layer of an eNodeB.
  • An RRC state in which the entity of the RRC layer of the UE is logically connected with the entity of the RRC layer of the eNodeB is called an RRC connected state.
  • An RRC state in which the entity of the RRC layer of the UE is not logically connected with the entity of the RRC layer of the eNodeB is called an RRC idle state.
  • a UE in the Connected state has RRC connection, and thus the E-UTRAN may recognize presence of the UE in a cell unit. Accordingly, the UE may be efficiently controlled.
  • the E-UTRAN cannot recognize presence of a UE which is in the idle state.
  • the UE in the idle state is managed by the core network in a tracking area unit which is an area unit larger than the cell.
  • the tracking area is a unit of a set of cells. That is, for the UE which is in the idle state, only presence or absence of the UE is recognized in a larger area unit.
  • the UE in the idle state In order for the UE in the idle state to be provided with a usual mobile communication service such as a voice service and a data service, the UE should transition to the connected state.
  • the UE When the user initially turns on the UE, the UE searches for a proper cell first, and then stays in the idle state. Only when the UE staying in the idle state needs to establish RRC connection, the UE establishes RRC connection with the RRC layer of the eNodeB through the RRC connection procedure and then performs transition to the RRC connected state.
  • the UE staying in the idle state needs to establish RRC connection in many cases.
  • the cases may include an attempt of a user to make a phone call, an attempt to transmit data, or transmission of a response message after reception of a paging message from the E-UTRAN.
  • the RRC connection procedure is broadly divided into transmission of an RRC connection request message from the UE to the eNodeB, transmission of an RRC connection setup message from the eNodeB to the UE, and transmission of an RRC connection setup complete message from the UE to eNodeB, which are described in detail below with reference to FIG. 6 .
  • the UE When the UE in the idle state desires to establish RRC connection for reasons such as an attempt to make a call, a data transmission attempt, or a response of the eNodeB to paging, the UE transmits an RRC connection request message to the eNodeB first.
  • the ENB Upon receiving the RRC connection request message from the UE, the ENB accepts the RRC connection request of the UE when the radio resources are sufficient, and then transmits an RRC connection setup message, which is a response message, to the UE.
  • the UE Upon receiving the RRC connection setup message, the UE transmits an RRC connection setup complete message to the eNodeB. Only when the UE successfully transmits the RRC connection setup message, does the UE establish RRC connection with the eNode B and transition to the RRC connected mode.
  • the MME in the conventional EPC is divided into an Access and Mobility Management Function (AMF) and a Session Management Function (SMF) in the next generation system (or 5G Core Network (CN)). Accordingly, the NAS interaction with the UE and the mobility management (MM) are performed by the AMF, and the session management (SM) is performed by the SMF.
  • the SMF manages a User Plane Function (UPF), which is a gateway that has a user-plane function, that is, a gateway for routing user traffic.
  • UPF User Plane Function
  • the SMF is responsible for the control plane portion of the S-GW and the P-GW and the UPF is responsible for the user-plane portion.
  • UPFs may be provided between the RAN and the Data Network (DN) for the routing of user traffic. That is, in the 5G system, the conventional EPC may be configured as illustrated in FIG. 7 .
  • a Protocol Data Unit (PDU) session is defined as a concept corresponding to PDN connection in the conventional EPS.
  • the PDU session refers to an association between a UE and a DN that provides PDU connectivity services of an Ethernet type or an unstructured type as well as an IP type.
  • UDM Unified Data Management
  • PCF Policy Control Function
  • PCF Policy Control Function
  • the functions may be provided in an extended form to meet the requirements of the 5G system.
  • functions, and interfaces refer to TS 23.501.
  • TS 23.501 Work on the 5G system is being carried out in TS 23.501, TS 23.502 and TS 23.503. Accordingly, in the present invention, the above standards are applied to the 5G system.
  • the more detailed architecture and contents related to NG-RAN comply with TS 38.300 and the like.
  • 5G system also supports non-3GPP access.
  • the architecture, network elements, and the like to support non-3GPP access are described in section 4.2.8 of TS 23.501, and procedures for supporting non-3GPP access are described in section 4.12 of TS 23.502.
  • a typical example of non-3GPP access is WLAN access, which may include both a trusted WLAN and an untrusted WLAN.
  • the AMF of the 5G system performs registration management (RM) and connection management (CM) for 3GPP access as well as non-3GPP access.
  • RM registration management
  • CM connection management
  • a single network function may integrally and efficiently support authentication, mobility management and even session management for UEs registered through two different accesses.
  • Section 4.2.3.3 of TS 23.502 describes an operation performed when downlink data (or downlink traffic) of the PDU session associated with non-3GPP access is generated in the case where a UE registered with the same PLMN for both 3GPP access and non-3GPP access is CM-IDLE in non-3GPP access.
  • the AMF may page the UE through 3GPP access (see step 4.2b.3 in section 4.2.3.3 of TS 23.502).
  • the 3GPP access is CM-CONNECTED
  • the AMF may send a NAS Notification message to the UE through 3GPP access (see step 4c in section 4.2.3.3 of TS 23.502).
  • activation of the user plane for a PDU session may be expressed as activation of user plane connection for the PDU session, N3 activation for the PDU session, N3 tunnel activation for the PDU session, and N3 tunnel activation for the PDU session, and activation of the PDU session.
  • deactivation of the user plane for the PDU session may be expressed as deactivation of user plane connection for the PDU session, N3 deactivation for the PDU session, N3 tunnel deactivation for the PDU session, and deactivation of the PDU session).
  • V2X In conventional LTE Release 14 V2X, when the UE transmits a V2X message over PC5, other UEs in the PC 5 range of the UE receive and decode the V2X message, and then forward the message to a corresponding V2X application if there are V2X services (e.g., PSID or ITS-AIDs of the V2X application) information mapped to the Destination Layer-2 ID of the message.
  • V2X services e.g., PSID or ITS-AIDs of the V2X application
  • TR 23.786 defines the agenda as shown in Table 2 below.
  • a UE may support multiple radio access technologies (RATs) over PC5 interface, including LTE and NR.
  • RATs radio access technologies
  • the most suitable 3GPP PC5 RAT(s) for V2X applications should be selected based on various criteria. For example, for the V2X application requiring low latency, the PC5 RAT that meets the required latency should be selected.
  • 3GPP PC5 RAT selection for each V2X application e.g. QoS parameters, RAN related parameters such as expected range of a RAT, operator policy, preferences for each V2X application, peer UE capabilities, etc.? -
  • 3GPP PC5 RAT selection is performed? Is the 3GPP PC5 RAT selected before sending/receiving each V2X message, or is the 3GPP PC5 RAT selected based on static configuration for each V2X application? - How can 3GPP system support the 3GPP PC5 RAT selection for the V2X application?
  • PC5 PHY format has been changed in LTE Release 15 to improve performance compared to LTE Release 14.
  • PC5 64QAM for transmission at a high data rate is also under discussion. Even if the PC5 RAT used to transmit a V2X message is LTE, a UE in the vicinity of the transmitting UE that performs a transmission in the LTE Release 15 PHY format cannot decode the received (data of) LTE Release 15 PHY format if the receiving UE is LTE Release 14 UE. This is because a UE which does not have the function of PC5 64QAM cannot decode a V2X message transmitted using this function.
  • the PC5 transmission schemes even when the PC5 RAT is LTE, there may be a case where a radio terminal receives a V2X message but cannot decode/interpret the received message. Furthermore, when NR is added to the PC5 RATs, the PC5 transmission schemes may be further diversified, and thus various types of UEs supporting various combinations of the PC5 transmission schemes may coexist.
  • the transmission may be meaningless if only UEs incapable of performing PC5 communication through NR are present around the certain UE.
  • the transmission may be meaningless and PC5 resources may be wasted if only UEs capable of PC5 communication through LTE but incapable of communication through LTE 64QAM are present around the certain UE.
  • the present invention proposes an optimized PC5 transmission method for V2X services.
  • V2X service and V2X application are used interchangeably.
  • FIG. 8 illustrates an embodiment of the present invention in relation to "V2X service oriented layer 2 link establishment.”
  • a first UE UE-1
  • the Direct Communication Request message can be sent by UE-1 with broadcast mechanism, i.e. by using a broadcast address associated with the application.
  • the information about V2X Service requesting L2 link establishment i.e. information about the announced V2X Service is included in the Direct Communication Request message to allow other UEs to determine whether to respond to the request.
  • the source L2 ID of this message should be the unicast L2 ID of the UE-1.
  • the broadcast Direct Communication Request message may be received by a plurality of UEs (UE-2, UE-3, UE-4, etc.).
  • a Direct Communication Accept message may be received in a unicast manner from the second UE receiving the Direct Communication Request message.
  • the Direct Communication Request message should be transmitted using default AS layer setting, e.g., broadcast setting, that can be understood by other UEs.
  • the reception of the Direct Communication Request message may mean that the message can be received and decoded by a radio terminal, or that the message is received by the radio terminal but cannot be decoded.
  • data of the V2X service may be unicast to the second UE.
  • the source Layer-2 ID included in the broadcast Direct Communication Request message may be used/configured as a destination Layer-2 ID of a Direct Communication Accept message for unicast reception of the data of the V2X service by the second UE.
  • the UEs that are interested in using the V2X Service announced by the Direct Communication Request message can respond to the request (UE-2 and UE-4 in Figure 8 ).
  • the UEs interested in the service may correspond to at least one of a UE that has determined to use the V2X service, a UE that has not determined to use the V2X service but intends to receive data of the V2X service and determine whether to use the V2X service, a UE that has determined to establish the L2 link for the V2X service with the first UE, or a UE that has determined to perform unicast communication with the first UE for the V2X service.
  • the UE uses the source L2 ID of the received Direct Communication Request message as destination L2 ID in the subsequent signaling to UE-1, and uses its own unicast L2 ID as the source L2 ID.
  • UE-1 obtains UE-2's L2 ID and UE-4's L2 ID for signaling for future communication and data traffic.
  • the Direct Communication Request message is transmitted for establishment of a layer 2 link (V2X service oriented layer 2 link) unlike a broadcast message transmitted by a conventional base station or the like.
  • the Direct Communication Request message includes information about the V2X service and a source Layer-2 ID, and the Direct Communication Accept message includes the ID of the second UE corresponding to the source Layer-2 ID.
  • the source Layer-2 ID included in the broadcast Direct Communication Request message is used/configured as a destination Layer-2 ID of the Direct Communication Accept message for unicast reception of the data of the V2X service by the second UE.
  • unicast transmission to a UE requiring a specific V2X service may be performed without using conventional signaling and resources required to establish a PC 5 link. Accordingly, the operation may be efficient.
  • the statement that the Direct Communication Request message or the Direct Communication Accept message includes the source Layer-2 ID may be interpreted as meaning that the message is transmitted using the source Layer-2 ID, rather than meaning that the ID is included in the message itself.
  • the Direct Communication Request message may include one or more of the following kinds of information.
  • This may take various forms such as a bitmap, a coded form, a table, a Tx profile, and an index, and may be coupled/combined with the information of 5). There may be multiple schemes, and prefer/prioritize information may be explicitly or implicitly indicated.
  • the information may indicate that transmission is performed using 64QAM in LTE.
  • the information may indicate transmission in “NR” and transmission in "LTE 64QAM", wherein the first one may have the highest priority.
  • Location information represents the location information about the UE. This information may be coordinate information, cell information, or the like. This information may be provided by the Application Layer and be included in the Direct Communication Request message in the form of a transparent container. In this case, various kinds of application layer information other than the location information may be included in the transparent container.
  • Information instructing that a response should be sent when the Direct Communication Request message is received a specific number of times or more for a specific time This is information indicating that a response for receiving V2X traffic (e.g., a Direct Communication Accept message/Service Announcement Ack message) will be transmitted only when a Direct Communication Request message is received from the same UE a certain number of times or more for a certain time.
  • This information includes time information (several milliseconds (ms), several seconds (sec), several minutes (min), etc.) and number-of-times information.
  • the number-of-times information may be represented as "repetition.”
  • a UE receiving the message When a Direct Communication Request message is transmitted, a UE receiving the message is present within the PC5 range of the UE transmitting the message, and thus transmits a response that it will receive V2X traffic. However, when V2X traffic is actually transmitted, the UE transmitting the response may move away (as it is, for example, e.g. a UE running in the opposite lane, a UE running along another branch at an intersection, etc.).
  • the above-described information is intended to prevent V2X traffic from being transmitted when there is no UE to receive the V2X traffic.
  • Reference number/ID/code (or random number/ID/code): Reference number for the Direct Communication Request message.
  • the reference number may be a serial number or a number generated at random. A new reference number may be generated when another Direct Communication Request message is transmitted after transmission of V2X traffic is completed.
  • Source L2 ID to use in transmitting V2X traffic A Source L2 ID that is to be actually used in transmitting V2X traffic.
  • Source IP address to use in transmitting V2X traffic A source IP address that is to be actually used in transmitting V2X traffic. This information is included when V2X traffic is to be transmitted in IP type.
  • the information in items 2) to 11) may not be configured as one piece per Direct Communication Request message, but as one piece per V2X service indicated by the Direct Communication Request message.
  • certain information of the information in items 2) to 11) may be configured as one piece per Direct Communication Request message and other information may be configured as one piece per V2X service indicated by the Direct Communication Request message.
  • Whether the Direct Communication Request message is transmitted from the same UE may be determined based on one or a combination of two or more of the information types in items 1) to 11).
  • a part of the above-described information may be included in a message header of a lower layer (which may be interpreted as an AS layer or a Layer 2 layer or a radio layer) transmitting the Direct Communication Request message rather than in the Direct Communication Request message itself.
  • a lower layer which may be interpreted as an AS layer or a Layer 2 layer or a radio layer
  • the PC5 RAT for the Direct Communication Request message may be defined as LTE and/or NR. It may also be defined as a PC5 discovery channel (aka PC5-D), a PC5 communication channel (aka PC5-U), or a specific PC5 channel for transmission of the Direct Communication Request message.
  • PC5-D PC5 discovery channel
  • PC5-U PC5 communication channel
  • PC5-U PC5 communication channel
  • the Direct Communication Accept message may be transmitted as V2X traffic to be transmitted by UE #1 can be received/decoded/understood.
  • the Direct Communication Accept message may be understood as being transmitted by a UE having a capability of receiving the message transmitted by UE #1.
  • a UE that has transmitted the Direct Communication Accept message may store information (typically L2 ID information, IP address information) necessary for receiving V2X traffic among the kinds of information included in the received Direct Communication Request message.
  • the location information corresponding to item 7) of the Direct Communication Request message may be included in the Direct Communication Request message or may be obtained through a basic V2X message (which may be a basic road safety message such as, for example, CAM, DENM, and BSM) transmitted by UE #1 if not included in the Direct Communication Request message.
  • a basic V2X message which may be a basic road safety message such as, for example, CAM, DENM, and BSM
  • the UE may determine to transmit a response message over PC5 in response to the message. For example, if the UE desires to receive the V2X service from a UE located ahead thereof but does not desire to receive the V2X service from a UE located behind, it may determine to transmit a response message only to the UE ahead.
  • the Direct Communication Request message may be included in the Direct Communication Request message or may be configured/provisioned in the UE. When this information is present, the UE transmits a Direct Communication Accept message based on the information when the condition is met. Alternatively, if the UE desires to receive the V2X service indicated by the Direct Communication Request message even when it receives the Direct Communication Request message once, the UE may determine to transmit a response message to the message over PC5.
  • the Direct Communication Accept message may include one or more of the following kinds of information. For details such as how to express the following information, refer to the description of the Direct Communication Request message:
  • the information of items a), b) and c) may be interpreted as meaning that the content (information) included in the Direct Communication Request message is applied. For example, if the information of item a) is not included, this may be interpreted as indicating that the UE desires to receive all V2X services indicated by the Direct Communication Request message. As another example, if the information of items b) and c) is not included, this may be interpreted as indicating that the V2X traffic can be received using a PC5 RAT and a transmission scheme indicated by the Direct Communication Request message.
  • the values thereof are used for the transmission. Otherwise (if they are not included in the Direct Communication Request message), values generated by the UE or set values are used.
  • the V2X traffic transmission scheme may be finally determined based on the information of items 5) and 6) included in Direct Communication Request message and/or the information of items b) and c) included or not included in Direct Communication Accept message. If multiple transmission schemes are available for a V2X service, a scheme available for reception by all UEs that have transmitted a Direct Communication Accept message should be selected. In addition, if there are multiple schemes available for reception by all UEs that have transmitted the Direct Communication Accept message, the best transmission scheme may be selected from among the multiple schemes.
  • the best transmission scheme may refer to a scheme that exhibits the best performance, a scheme having the highest priority, or a scheme having the highest preference.
  • Tx_Mechanism #1 For example, suppose that transmission schemes available for transmission of V2X traffic for a V2X service to be transmitted by UE #1 are Tx_Mechanism #1 and Tx_Mechanism #2, which have priorities in this order. In this case, if UE #3 has transmitted the two mechanisms in a Direct Communication Accept message and UE #4 has transmitted only Tx Mechanism #2 in a Direct Communication Accept message, UE #1 may select Tx_Mechanism #2 for transmission of V2X traffic.
  • FIG. 9 illustrates an embodiment similar to that described above with reference to FIG. 8 .
  • contents which are not described in detail in the description of FIG. 9 refer to the corresponding parts in the description of FIG. 8 .
  • UE #1 transmits, over PC5, a message for informing other UEs of a V2X service that can be transmitted to/shared with other UEs.
  • a message may be, for example, a Service Announcement message, a Service Advertisement message, a Direct Communication Request message (which may be interpreted as a message for requesting establishment of a PC5 session/link), or the like.
  • step S902 the Direct Communication Request message/Service Announcement message transmitted by UE #1 is received by neighboring UEs (which may be interpreted as UEs within the PC5 range or UEs within the reception range of the PC5 message transmitted by UE #1).
  • neighboring UEs which may be interpreted as UEs within the PC5 range or UEs within the reception range of the PC5 message transmitted by UE #1.
  • receiving the Direct Communication Request message/Service Announcement message may mean that a radio terminal receives the message and can decode the received message, or that a radio terminal receives the message but cannot decode the received message.
  • a UE that desires to receive the V2X service indicated by the Service Announcement message (which may refer to a UE capable of receiving the V2X service) transmits a response message to the message over PC5.
  • a message may be, for example, a Service Announcement Ack message, an Interest message, or a Direct Communication Accept message.
  • step S904 UE #1 transmits V2X traffic upon receiving the Direct Communication Accept message.
  • step S905 neighboring UEs (which may be interpreted as UEs within the PC5 range or UEs within the reception range of the PC5 message transmitted by UE #1) receive the V2X traffic transmitted by UE #1 over PC5.
  • receiving the V2X traffic may mean that a radio terminal receives the V2X traffic and can decode the received V2X traffic, or that a radio terminal receives the V2X traffic but cannot decode the received V2X traffic.
  • step S906 UE #3 and UE #4 decode the received V2X traffic. Thereafter, the V2X traffic may be further verified/filtered according to the L2 ID information and the IP address information stored in S9063. In case of UE #2, even if the V2X traffic is received by the radio terminal, it may not be decoded/interpreted.
  • Figure 3 refers to FIG. 12
  • Figure 6.11.3.1-1 refers to FIG. 13
  • Figure 6.11.3.1-2 refers to FIG. 14
  • Figure 6.11.3.1-3 refers to FIG. 15 .
  • Tables 8 to 11 below which are from contribution documents submitted to the 3GPP by the inventors of the present invention, are incorporated in and constitute a part of this application.
  • Figure 6.11.3.1-1a refers to FIG. 16
  • Figure 6.11.3.1-2a refers to FIG. 17
  • Figure 6.11.3.1-3a refers to FIG. 18 .
  • the PC 5 operation may be interpreted as including PC5 search (or D2D search, direct discovery, ProSe discovery, sidelink search, or direct search) as well as PC5 communication (or D2D communication, direct communication, ProSe communication, sidelink communication, or direct communication). In addition, it may be interpreted as including all operations using PC5.
  • the PC5 operations include, for example, transmitting and receiving a V2X message by a UE over PC5, transmitting and receiving, by a UE, various data generated by a V2X application over PC5, and transmitting and receiving, by a UE, various kinds of information associated with V2X over PC5, establishing, by a UE, a link or a one-to-one connection with another UE over PC5, and searching, by a UE, for another UE over PC5.
  • the interface name defined for D2D communication may not be PC5.
  • the present invention may be understood by applying an interface name newly defined for D2D communication.
  • various interfaces e.g., V1, V2, V3, etc.
  • V1, V2, V3, etc. conventionally defined in the EPS may be used in the 5G system in the same manner or all or a part thereof may be defined with new names. The invention should be understood considering this point.
  • a UE may be a vehicle UE, a pedestrian UE, or a UE-type RSU. That is, it includes all devices capable of operating as a UE type or performing the PC5 operation.
  • V2X service V2X message
  • V2X traffic V2X data
  • a method for efficiently providing a V2X service through the 5G System (5G mobile communication system, next generation mobile communication system) and the EPS as proposed in the present invention i.e., the optimized PC5 transmission method for the V2X service is configured by a combination of one or more of the following operations/configuration/steps.
  • the multicast transmission may be interpreted as groupcast transmission, one-shot transmission to multiple UEs, unicast L2 link with multicast traffic transmission, one-to-one L2 link with multicast traffic transmission, L2 link with multicast traffic transmission, or the like.
  • FIG. 19 is a diagram illustrating a wireless communication apparatus according to an embodiment of the present invention.
  • a wireless communication system may include a first device 9010 and a second device 9020.
  • the first device 9010 may be a base station, a network node, a transmitting terminal, a receiving terminal, a wireless device, a wireless communication device, a vehicle, a vehicle equipped with an autonomous travel function, a connected car, an unmanned aerial vehicle (UAV), an artificial intelligence (AI) module, a robot, an augmented reality (AR) device, a virtual reality (VR) device, an mixed reality (MR) device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a FinTech device (or financial device), a security device, a climate/environmental device, a device related to 5G services, or a device related to the 4th industrial revolution sector.
  • UAV unmanned aerial vehicle
  • AI artificial intelligence
  • AR augmented reality
  • VR virtual reality
  • MR mixed reality
  • hologram device a public safety device
  • MTC device an IoT device
  • medical device a FinTech device (or financial device)
  • security device a climate/environ
  • the second device 9020 may be a base station, a network node, a transmitting terminal, a receiving terminal, a wireless device, a wireless communication device, a vehicle, a vehicle equipped with an autonomous travel function, a connected car, an unmanned aerial vehicle (UAV), an artificial intelligence (AI) module, a robot, an augmented reality (AR) device, a virtual reality (VR) device, an mixed reality (MR) device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a FinTech device (or financial device), a security device, a climate/environmental device, a device related to 5G services, or a device related to the 4th industrial revolution sector.
  • UAV unmanned aerial vehicle
  • AI artificial intelligence
  • AR augmented reality
  • VR virtual reality
  • MR mixed reality
  • hologram device a public safety device
  • MTC device an IoT device
  • medical device a FinTech device (or financial device)
  • security device a climate/environ
  • UEs may include a cell phone, a smart phone, a laptop computer, a digital broadcasting terminal, personal digital assistants (PDA), a portable multimedia player (PMP), a navigation device, a slate PC, a tablet, an ultrabook, a wearable device (e.g., a smartwatch, a smart glass, a head mounted display (HMD), etc.).
  • the HMD may be a display device wearable on the head.
  • the HMD may be used to implement VR, AR, or MR.
  • the UAV may be an airborne vehicle that does not have a person aboard but is controlled to fly by a radio control signal.
  • the VR device may include a device that implements an object or background in a virtual world.
  • the AR device may include a device that implements an object or background of a virtual world by connecting the object or background of the virtual world to a real-world object or background.
  • the MR device may include a device that fuses an object or background of a virtual world with a real-world object or background.
  • the hologram device may include a device that implements a 360-degree stereoscopic image by recording and reproducing stereoscopic information by utilizing the effect of interference of light generated by two laser rays meeting with each other, which is called holography.
  • the public safety device may include a video relay device or a video device that may be worn by a user.
  • the MTC device and the IoT device may be devices that do not require direct human intervention or manipulation.
  • the MTC device and the IoT device may include a smart meter, a vending machine, a thermometer, a smart bulb, a door lock, or various sensors.
  • the medical device may be a device used for the purpose of diagnosing, treating, alleviating, treating, or preventing a disease.
  • the medical device may be a device used for the purpose of diagnosing, treating, alleviating, or correcting an injury or disorder.
  • the medical device may be a device used for the purpose of testing, replacing or modifying a structure or function.
  • the medical device may be a device used for the purpose of controlling pregnancy.
  • the medical device may include a treatment device, a surgical device, an (in vitro) diagnostic device, a hearing aid, or a procedural device.
  • the security device may be a device installed to prevent a risk that may occur and to maintain safety.
  • the security device may be a camera, a CCTV, a recorder, or a black box.
  • the FinTech device may be a device capable of providing financial services such as mobile payment.
  • the FinTech device may include a payment device or a point of sale (POS).
  • the climate/environmental device may include a device for monitoring or predicting the climate/environment.
  • the first device 9010 may include at least one processor, such as a processor 9011, at least one memory, such as a memory 9012, and at least one transceiver, such as a transceiver 9013.
  • the processor 9011 may perform the functions, procedures, and/or methods described above.
  • the processor 9011 may implement one or more protocols.
  • the processor 9011 may implement one or more layers of a wireless interface protocol.
  • the memory 9012 may be connected to the processor 9011 and store various types of information and/or instructions.
  • the transceiver 9013 may be connected to the processor 9011 and controlled to transmit and receive wireless signals.
  • the at least one processor of the first device broadcasts a Direct Communication Request message, and receives a Direct Communication Accept message unicast from a second UE that has received the Direct Communication Request message, and the source second UE unicasts data of a V2X service.
  • the source Layer-2 ID included in the broadcast Direct Communication Request message may be used as a destination Layer-2 ID of a Direct Communication Accept message for unicast reception of the data of the V2X service by the second UE.
  • the second device 9020 may include at least one processor, such as a processor 9021, at least one memory device, such as a memory 9022, and at least one transceiver, such as a transceiver 9023.
  • the processor 9021 may perform the functions, procedures, and/or methods described above.
  • the processor 9021 may implement one or more protocols.
  • the processor 9021 may implement one or more layers of a wireless interface protocol.
  • the memory 9022 may be connected to the processor 9021 and store various types of information and/or instructions.
  • the transceiver 9023 may be connected to the processor 9021 and controlled to transmit and receive wireless signals.
  • the at least one processor of the second device receives a Direct Communication Request message from the first UE in a broadcast manner.
  • the second UE unicasts a Direct Communication Accept message, and receives data of a V2X service from the first UE in a unicast manner.
  • the source Layer-2 ID included in the broadcast Direct Communication Request message may be used as a destination Layer-2 ID of the Direct Communication Accept message for unicast reception of the data of the V2X service by the second UE.
  • the memory 9012 and/or the memory 9022 may be internally or externally connected to the processor 9011 and/or the processor 9021, or may be connected to other processors through various techniques such as wired or wireless connection.
  • the first device 9010 and/or the second device 9020 may have one or more antennas.
  • an antenna 9014 and/or an antenna 9024 may be configured to transmit and receive wireless signals.
  • Configuration of first device 9010 and/or the second device 9020 may be implemented such that the details of various embodiments of the present invention described above can be independently applied or two or more of the embodiments can be simultaneously applied. For simplicity, redundant description is omitted.
  • the embodiments of the present invention may be implemented through various means.
  • the embodiments may be implemented by hardware, firmware, software, or a combination thereof.
  • a method according to embodiments of the present invention may be implemented by 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), one or more field programmable gate arrays (FPGAs), one or more processors, one or more controllers, one or more microcontrollers, one or more microprocessor, or the like.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGAs field programmable gate arrays
  • processors one or more controllers, one or more microcontrollers, one or more microprocessor, or the like.
  • a method according to embodiments of the present invention may be implemented by an apparatus, a procedure, or a function that performs the functions or operations described above.
  • Software code may be stored in a memory unit and executed by a processor.
  • the memory unit is located at the interior or exterior of the processor and may transmit and receive data to and from the processor via various known means.
  • the operation may be efficient.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Claims (13)

  1. Procédé de transmission, par un premier équipement utilisateur, UE, des données V2X dans un système de communication sans fil, le procédé consistant à :
    diffuser (801), par le premier UE, un message de demande de communication directe comprenant des informations ayant configuré qu'une réponse est transmise uniquement lorsque le message de demande de communication directe est reçu à un nombre spécifiques de fois ou plus dans un intervalle spécifique, les informations comprenant le nombre spécifique de fois et l'intervalle spécifique ;
    recevoir (802a), par diffusion individuelle, un message d'acceptation de communication directe en provenance du second UE recevant le message de demande de communication directe davantage que le nombre spécifique de fois dans l'intervalle spécifique ; et
    transmettre des données d'un service V2X au second UE par diffusion individuelle,
    dans lequel une identité de couche source 2, du premier UE dans le message de demande de communication directe de diffusion est utilisée par le second UE comme ID de couche de destination 2 du message d'acceptation de communication directe pour la transmission individuelle des données du service V2X.
  2. Procédé selon la revendication 1, dans lequel le message de demande de communication directe comprend des informations concernant le service V2X.
  3. Procédé selon la revendication 1, dans lequel le message de demande de communication directe est transmis pour établir une liaison de couche 2 orienté service V2X.
  4. Procédé selon la revendication 2, dans lequel le message de communication directe correspond à au moins l'un parmi un UE qui a déterminé d'utiliser le service V2X, un UE qui n'a pas déterminé d'utiliser le service V2X mais à l'intention de recevoir des données du service V2X et détermine s'il faut utiliser le service V2X, un UE qui a déterminé d'établir une liaison L2 pour le service V2X avec le premier UE, ou un UE qui a déterminé d'établir une communication de diffusion individuelle avec le premier UE pour le service V2X.
  5. Premier équipement utilisateur, UE, dans un système de communication sans fil, comprenant :
    une mémoire ; et
    au moins un processeur couplé à la mémoire,
    dans lequel l'au moins un processeur étant configuré pour :
    diffuser un message de demande de communication directe comprenant des informations ayant configuré qu'une réponse est transmise uniquement lorsque le message de demande de communication directe est reçu un nombre spécifiques de fois ou plus dans un intervalle spécifique, les informations comprenant le nombre spécifique de fois et l'intervalle spécifique ;
    recevoir, par diffusion individuelle, un message d'acceptation de communication directe en provenance du second UE recevant le message de demande de communication directe davantage de fois que le nombre spécifique de fois dans l'intervalle spécifique ; et
    transmettre des données d'un service V2X au second UE par diffusion individuelle,
    dans lequel une identité de couche source 2, ID, du premier UE incluse dans le message de demande de communication directe de diffusion est utilisée par le second UE comme ID de couche de destination 2 du message d'acceptation de communication directe pour la transmission individuelle des données du service V2X.
  6. Premier UE selon la revendication 5, dans lequel le message de demande de communication directe comprend des informations concernant le service V2X.
  7. Premier UE selon la revendication 5, dans lequel le message de demande de communication directe est transmis pour établir une liaison de couche 2 orienté service V2X.
  8. Procédé selon la revendication 2, dans lequel le message de communication directe correspond à au moins l'un parmi un UE qui a déterminé d'utiliser le service V2X, un UE qui n'a pas déterminé d'utiliser le service V2X mais à l'intention de recevoir des données du service V2X et détermine s'il faut utiliser le service V2X, un UE qui a déterminé d'établir une liaison L2 pour le service V2X avec le premier UE, ou un UE qui a déterminé d'établir une communication de diffusion individuelle avec le premier UE pour le service V2X.
  9. Procédé de réception de données V2X par un second équipement utilisateur, UE, dans un système de communication sans fil, le procédé consistant à :
    recevoir (801), par le second UE, un message de demande de communication directe comprenant des informations ayant configuré qu'une réponse est transmise uniquement lorsque le message de demande de communication directe est reçu à un nombre spécifiques de fois ou plus dans un intervalle spécifique provenant d'un premier UE par diffusion individuelle, les informations comprenant le nombre spécifique de fois et l'intervalle spécifique ;
    recevoir (802a), par le second UE, un message d'acceptation de communication directe par diffusion individuelle en fonction du fait que le second UE reçoit le message de demande de communication directe davantage que le nombre spécifique de fois dans l'intervalle spécifique ; et
    recevoir des données d'un service V2X en provenance du premier UE par diffusion individuelle,
    dans lequel une identité de couche source 2, du premier UE dans le message de demande de communication directe de diffusion est utilisée par le second UE comme ID de couche de destination 2 du message d'acceptation de communication directe pour la transmission individuelle des données du service V2X.
  10. Procédé selon la revendication 9, dans lequel le message de demande de communication directe comprend des informations concernant le service V2X.
  11. Procédé selon la revendication 9, dans lequel le message de demande de communication directe est transmis pour établir une liaison de couche 2 orienté service V2X.
  12. Procédé selon la revendication 2, dans lequel le message de communication directe correspond à au moins l'un parmi un UE qui a déterminé d'utiliser le service V2X, un UE qui n'a pas déterminé d'utiliser le service V2X mais à l'intention de recevoir des données du service V2X et détermine s'il faut utiliser le service V2X, un UE qui a déterminé d'établir une liaison L2 pour le service V2X avec le premier UE, ou un UE qui a déterminé d'établir une communication de diffusion individuelle avec le premier UE pour le service V2X.
  13. Second équipement utilisateur, UE, dans un système de communication sans fil, comprenant :
    une mémoire ; et
    au moins un processeur couplé à la mémoire,
    dans lequel l'au moins un processeur étant configuré pour :
    recevoir un message de demande de communication directe comprenant des informations ayant configuré qu'une réponse est transmise uniquement lorsque le message de demande de communication directe est reçu un nombre spécifique de fois ou plus dans un intervalle spécifique provenant d'un premier UE par diffusion individuelle, les informations comprenant le nombre spécifique de fois et l'intervalle spécifique ;
    transmettre un message d'acceptation de communication directe par diffusion individuelle en fonction du fait que le second UE reçoit le message de demande de communication directe davantage de fois que le nombre spécifique de fois dans l'intervalle spécifique ; et
    recevoir des données d'un service V2X en provenance du premier UE par diffusion individuelle,
    dans lequel une identité de couche source 2, du premier UE dans le message de demande de communication directe de diffusion est utilisée par le second UE comme ID de couche de destination 2 du message d'acceptation de communication directe pour la transmission individuelle des données du service V2X.
EP19799655.6A 2018-05-08 2019-05-08 Procédé de transmission de données v2x dans un système de communication sans fil et dispositif associé Active EP3780902B1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
KR20180052506 2018-05-08
KR20180116271 2018-09-28
KR20180142679 2018-11-19
PCT/KR2019/005497 WO2019216641A1 (fr) 2018-05-08 2019-05-08 Procédé de transmission de données v2x dans un système de communication sans fil et dispositif associé

Publications (3)

Publication Number Publication Date
EP3780902A1 EP3780902A1 (fr) 2021-02-17
EP3780902A4 EP3780902A4 (fr) 2021-04-07
EP3780902B1 true EP3780902B1 (fr) 2022-09-14

Family

ID=68464426

Family Applications (1)

Application Number Title Priority Date Filing Date
EP19799655.6A Active EP3780902B1 (fr) 2018-05-08 2019-05-08 Procédé de transmission de données v2x dans un système de communication sans fil et dispositif associé

Country Status (4)

Country Link
US (1) US11159925B2 (fr)
EP (1) EP3780902B1 (fr)
CN (1) CN112106440B (fr)
WO (1) WO2019216641A1 (fr)

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3352484B1 (fr) * 2015-09-18 2020-09-23 Nec Corporation Dispositif de station de base, terminal sans fil, et procédé associé
US11102839B2 (en) 2018-11-02 2021-08-24 Qualcomm Incorporated Unicast sidelink establishment
CN111148064B (zh) * 2018-11-06 2023-04-18 华硕电脑股份有限公司 用于改进无线通信中的一对一侧链路通信的方法和设备
US11464066B2 (en) 2019-04-05 2022-10-04 Qualcomm Incorporated Establishing radio bearers on millimeter wave frequencies for device-to-device communications
US11540106B2 (en) 2019-04-05 2022-12-27 Qualcomm Incorporated Beam sweeping on millimeter wave frequencies for device-to-device communications
WO2020223664A1 (fr) * 2019-05-01 2020-11-05 Apple Inc. Communication en monodiffusion sur liaison latérale
US11470017B2 (en) * 2019-07-30 2022-10-11 At&T Intellectual Property I, L.P. Immersive reality component management via a reduced competition core network component
EP3989675A4 (fr) * 2019-08-19 2022-08-24 LG Electronics Inc. Procédé de relais de trafic non structuré, et ue de relais
US11671315B2 (en) * 2020-02-07 2023-06-06 Qualcomm Incorporated Inter-vehicle wireless in-vehicle network interference management
EP3883328B1 (fr) 2020-03-18 2022-04-20 ASUSTek Computer Inc. Procédé et appareil pour effectuer une procédure de mise à jour des identitées de la couche 2
CN113453379B (zh) * 2020-03-24 2023-05-16 维沃移动通信有限公司 一种更新标识信息的方法、终端和网络设备
WO2021217376A1 (fr) * 2020-04-27 2021-11-04 华为技术有限公司 Procédé, appareil et système de communication
CN112235734B (zh) * 2020-10-14 2022-04-08 大唐高鸿智联科技(重庆)有限公司 广播模式下的单播业务实现方法、装置及设备
CN114697910A (zh) * 2020-12-25 2022-07-01 株式会社电装 用于车联网的单播通信方法和装置
CN114697911A (zh) * 2020-12-26 2022-07-01 华为技术有限公司 一种消息过滤方法及装置
CN113284144B (zh) * 2021-07-22 2021-11-30 深圳大学 一种基于无人机的隧道检测方法及装置
CN115915023A (zh) * 2021-08-17 2023-04-04 维沃移动通信有限公司 定位方法、装置及终端
WO2023097660A1 (fr) * 2021-12-03 2023-06-08 Lenovo (Beijing) Limited Procédé et appareil d'établissement de monodiffusion
WO2023245520A1 (fr) * 2022-06-22 2023-12-28 北京小米移动软件有限公司 Procédé et appareil de communication directe dans un service de localisation

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10111267B2 (en) 2013-06-28 2018-10-23 Samsung Electronics Co., Ltd. Method and apparatus for performing device-to-device communication
US9699153B2 (en) * 2015-01-19 2017-07-04 Intel IP Corporation Systems, methods and devices for direct communication
RU2694814C1 (ru) * 2015-06-23 2019-07-17 Интердиджитал Пейтент Холдингз, Инк. ОБРАБОТКА ПРИОРИТЕТОВ В СИСТЕМЕ СВЯЗИ ProSe
WO2017030348A1 (fr) * 2015-08-14 2017-02-23 엘지전자 주식회사 Procédé d'émission et de réception de message véhicule à tout (v2x) dans un système de communication sans fil, et appareil associé
WO2017052683A1 (fr) * 2015-09-23 2017-03-30 Intel Corporation Hébergement dynamique de services v2x dans des réseaux cellulaires
US20170093541A1 (en) * 2015-09-25 2017-03-30 Asustek Computer Inc. Method and apparatus for reducing signaling overhead in a wireless communication system
US10560915B2 (en) 2016-05-02 2020-02-11 Lg Electronics Inc. Method for performing location registration by remote UE in wireless communication system, and apparatus therefor
EP3273634A1 (fr) * 2016-07-18 2018-01-24 Panasonic Intellectual Property Corporation of America Support amélioré de la qualité de service pour des transmissions de type v2x
JP6159865B1 (ja) 2016-11-10 2017-07-05 伸和コントロールズ株式会社 加湿器及び空気調和装置
EP3604685B1 (fr) 2017-03-24 2021-12-01 Hitachi Construction Machinery Tierra Co., Ltd. Dispositif d'entraînement hydraulique pour engin de chantier
US10796501B2 (en) * 2017-06-19 2020-10-06 Qualcomm Incorporated Interactive sharing of vehicle sensor information
US10839617B2 (en) * 2018-03-13 2020-11-17 Ford Global Technologies, Llc Method and apparatus for crowd-assisted prognostics and diagnostics
EP3964021A1 (fr) * 2019-05-02 2022-03-09 Lenovo (Singapore) Pte. Ltd. Session de monodiffusion sur une liaison de communication directe

Also Published As

Publication number Publication date
US20190349730A1 (en) 2019-11-14
EP3780902A1 (fr) 2021-02-17
EP3780902A4 (fr) 2021-04-07
CN112106440B (zh) 2023-09-19
WO2019216641A1 (fr) 2019-11-14
CN112106440A (zh) 2020-12-18
US11159925B2 (en) 2021-10-26

Similar Documents

Publication Publication Date Title
EP3780902B1 (fr) Procédé de transmission de données v2x dans un système de communication sans fil et dispositif associé
US11418970B2 (en) Method for transmitting and receiving signals related to QOS prediction in a wireless communication system and apparatus therefor
CN113545113B (zh) 用于在无线通信系统中执行网络注册的方法及装置
US11917451B2 (en) Method by which NWDAF transmits and receives signal in wireless communication system, and device therefor
US20220078857A1 (en) Method for transmitting/receiving pdb-related signal in wireless communication system and device therefor
US11382012B2 (en) Method and apparatus for deprioritizing access on unlicensed band based on UE preference in wireless communication system
US11812289B2 (en) Method for dealing with network failure
US11553332B2 (en) Method and device for controlling data transmission state in wireless communication system
US20230156553A1 (en) Method for managing network failures
US20230171639A1 (en) Communication related to congestion control
EP4228319A1 (fr) Communication liée à une multidiffusion
US20230319514A1 (en) Multicast-related communication
US20220330115A1 (en) Method of operating a ue related to an rrc connection in a sidelink relay in a wireless communication system
US20220312509A1 (en) Qos-related operation method in wireless communication system and apparatus therefor
US20220182854A1 (en) Method for handling network failure
US20230345333A1 (en) Communication related to network slice
US20230309009A1 (en) Operating method related to selection of relay ue in wireless communication system
EP4156726A1 (fr) Communication liée à une multidiffusion
EP4057766A1 (fr) Procédé et dispositif de commande de configuration relative à une communication de liaison latérale dans un système de communication sans fil
US20230084683A1 (en) Pws service method in npn
EP4192059A1 (fr) Procédé de commande lié à une découverte de liaison latérale dans un système de communications sans fil
US20230071408A1 (en) Communication related to multi access pdu session
US20220361039A1 (en) Operation method related to sidelink transmission and reception of ue in wireless communication system, and device therefor
US11438958B2 (en) Method for transmitting signal relating to PDU in wireless communication system and device therefor
US20210160740A1 (en) Transmitting/receiving method for ensuring connectivity in wire-less communication system, and device therefor

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20201111

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

A4 Supplementary search report drawn up and despatched

Effective date: 20210309

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 84/00 20090101ALI20210302BHEP

Ipc: H04W 80/02 20090101ALI20210302BHEP

Ipc: H04L 29/12 20060101ALI20210302BHEP

Ipc: H04L 29/08 20060101ALI20210302BHEP

Ipc: H04W 4/06 20090101ALI20210302BHEP

Ipc: H04W 4/80 20180101ALI20210302BHEP

Ipc: H04W 28/06 20090101ALI20210302BHEP

Ipc: H04W 76/14 20180101ALI20210302BHEP

Ipc: H04L 29/06 20060101ALI20210302BHEP

Ipc: H04W 4/02 20180101ALI20210302BHEP

Ipc: H04W 92/18 20090101AFI20210302BHEP

Ipc: H04W 4/40 20180101ALI20210302BHEP

Ipc: H04W 28/02 20090101ALI20210302BHEP

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20211207

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602019019648

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04W0092180000

Ipc: H04L0067120000

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 4/80 20180101ALI20220509BHEP

Ipc: H04W 4/02 20180101ALI20220509BHEP

Ipc: H04W 4/06 20090101ALI20220509BHEP

Ipc: H04W 4/40 20180101ALI20220509BHEP

Ipc: H04W 76/14 20180101ALI20220509BHEP

Ipc: H04W 80/02 20090101ALI20220509BHEP

Ipc: H04W 84/00 20090101ALI20220509BHEP

Ipc: H04L 69/04 20220101ALI20220509BHEP

Ipc: H04L 61/5007 20220101ALI20220509BHEP

Ipc: H04L 67/12 20220101AFI20220509BHEP

INTG Intention to grant announced

Effective date: 20220609

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602019019648

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1519388

Country of ref document: AT

Kind code of ref document: T

Effective date: 20221015

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20220914

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220914

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220914

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221214

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220914

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220914

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220914

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1519388

Country of ref document: AT

Kind code of ref document: T

Effective date: 20220914

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220914

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221215

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220914

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220914

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230116

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220914

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220914

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220914

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220914

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220914

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230114

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220914

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602019019648

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220914

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220914

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220914

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20230405

Year of fee payment: 5

26N No opposition filed

Effective date: 20230615

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220914

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220914

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20230508

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20230531

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220914

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230508

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230531

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230531

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230508

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230508

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230508