WO2017007104A1 - V2x 통신 시스템에서 단말의 통신 방법 및 단말 - Google Patents
V2x 통신 시스템에서 단말의 통신 방법 및 단말 Download PDFInfo
- Publication number
- WO2017007104A1 WO2017007104A1 PCT/KR2016/001381 KR2016001381W WO2017007104A1 WO 2017007104 A1 WO2017007104 A1 WO 2017007104A1 KR 2016001381 W KR2016001381 W KR 2016001381W WO 2017007104 A1 WO2017007104 A1 WO 2017007104A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- rsu
- communication
- relay node
- node
- base station
- Prior art date
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
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/08—Testing, supervising or monitoring using real traffic
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/50—Allocation or scheduling criteria for wireless resources
- H04W72/51—Allocation or scheduling criteria for wireless resources based on terminal or device properties
-
- 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
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/04—Interfaces between hierarchically different network devices
- H04W92/10—Interfaces between hierarchically different network devices between terminal device and access point, i.e. wireless air interface
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/16—Interfaces between hierarchically similar devices
- H04W92/18—Interfaces between hierarchically similar devices between terminal devices
-
- 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
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- 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/50—Network services
- H04L67/52—Network services specially adapted for the location of the user terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/005—Discovery of network devices, e.g. terminals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks
-
- 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/04—Terminal devices adapted for relaying to or from another terminal or user
Definitions
- the following description relates to a wireless communication system, and more particularly, to a communication method and a terminal of a terminal in a V2X communication system.
- Wireless communication systems are widely deployed to provide various kinds of communication services such as voice and data.
- a wireless communication system is a multiple access system capable of supporting communication with multiple users by sharing available system resources (bandwidth, transmission power, etc.).
- multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, and single carrier frequency (SC-FDMA).
- 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
- MCD division multiple access
- MCDMA multi-carrier frequency division multiple access
- MC-FDMA multi-carrier frequency division multiple access
- the present invention proposes a communication mechanism between a base station of a terminal and another terminal in a vehicle to everything (V2X) communication system.
- V2X vehicle to everything
- Another object of the present invention is to control the terminal to communicate in a different way according to the needs of the operator.
- Another object of the present invention is to efficiently design an infrastructure for providing a V2X communication service.
- the communication method for solving the technical problem includes a first capability including capability information indicating that the RSU (Road Side Unit) for providing a V2X service and the relay node for relaying a communication service can be operated.
- a first capability including capability information indicating that the RSU (Road Side Unit) for providing a V2X service and the relay node for relaying a communication service can be operated.
- Sending a message to a network entity receiving a second message from the base station instructing it to act as an RSU or relay node, and acting as an RSU or relay node in accordance with the second message, thereby communicating with the base station and other UEs. Performing the steps.
- the second message may further include information on an interface to be used in the process of operating as an RSU or a relay node.
- the information on the interface includes information on the interface to be used for communication with the base station and information on the interface to be used for communication with other UEs.
- the interface is related to the Uu interface, the Un interface, the PC5 interface, and the dedicated Shiort Range Communications (DSRC). It may be any one of the interfaces.
- the communication method may further include receiving an identifier indicating that the V2X service can operate as an RSU or a relay node, and accessing the base station using the identifier.
- the access may be allowed preferentially to the UE not using the identifier.
- the UE which is recognized by the network entity to be able to operate as an RSU or relay node, may be preferentially assigned radio resources from the base station.
- Receiving the second message and performing the communication may be performed through an application that is temporarily installed when the UE is charging using an external power source.
- the network entity may be a base station or a mobility management entity (MME).
- MME mobility management entity
- the user equipment (UE) for solving the technical problem includes a transmitter, a receiver, and a processor connected to the transmitter and the receiver to operate, wherein the processor includes a road side unit (RSU) and a communication service for providing a V2X service.
- RSU road side unit
- Control the transmitter to send a first message including capability information indicating the capability to operate as a relay node for relaying to the network entity, and receive a second message indicating to operate as an RSU or relay node.
- the receiver is controlled to receive from the base station, and acts as an RSU or relay node according to the second message, thereby communicating with the base station and other UEs.
- Another communication method for solving the above technical problem includes capability information indicating that the RSU (Road Side Unit) for providing a V2X service and the relay node for relaying a communication service can be operated.
- An interface to be used in the process of operating as an RSU or a relay node may also be set for the triggering condition.
- the triggering condition may be set to operate as an RSU when the number of vehicles located in the area managed by the UE is greater than or equal to the first threshold and to operate as a relay node when the number of vehicles is less than the second threshold.
- Another UE for solving the technical problem includes a transmitter, a receiver, and a processor operating in connection with the transmitter and the receiver, wherein the processor is configured to relay a Road Side Unit (RSU) and a communication service for providing a V2X service.
- RSU Road Side Unit
- Control the transmitter to send a message to the network entity that includes the capability information indicating that it can act as a relay node for the network node, set a triggering condition for initiating an operation with the RSU or the relay node, and triggering condition As this is satisfied, it acts as an RSU or relay node to communicate with the base station and other UEs.
- RSU Road Side Unit
- a terminal can communicate with other network entities in an efficient manner.
- the operator can remotely control the terminal, thereby facilitating management of network traffic and communication yield.
- FIG. 1 is a diagram illustrating a schematic structure of an EPS (Evolved Packet System) including an Evolved Packet Core (EPC).
- EPS Evolved Packet System
- EPC Evolved Packet Core
- FIG. 2 is an exemplary view showing the architecture of a general E-UTRAN and EPC.
- 3 is an exemplary view showing the structure of a radio interface protocol in a control plane.
- FIG. 4 is an exemplary view showing the structure of a radio interface protocol in a user plane.
- 5 is a flowchart illustrating a random access procedure.
- RRC radio resource control
- V2X vehicle to everything
- FIG. 8 is a diagram illustrating an infrastructure structure to which the proposed communication method is applied.
- FIG. 9 is a diagram illustrating another infrastructure to which the proposed communication method is applied.
- FIG 10 illustrates another infrastructure to which the proposed communication method is applied.
- FIG 11 illustrates another infrastructure to which the proposed communication method is applied.
- FIG. 13 is a diagram showing another infrastructure to which the proposed communication method is applied.
- FIG 16 illustrates another infrastructure to which the proposed communication method is applied.
- 17 is a flowchart illustrating a communication method according to an exemplary embodiment.
- FIG. 18 is a flowchart illustrating a communication method according to another exemplary embodiment.
- 19 illustrates another infrastructure to which the proposed communication method is applied.
- 21 is a flowchart illustrating a communication method according to another exemplary embodiment.
- 22 is a flowchart illustrating a communication method according to another exemplary embodiment.
- 23 is a flowchart illustrating a communication method according to another embodiment.
- FIG. 24 is a diagram illustrating a configuration of a node device according to an exemplary embodiment.
- each component or feature may be considered to be optional unless otherwise stated.
- Each component or feature may be embodied in a form that is not combined with other components or features.
- some of the components and / or features may be combined to form an embodiment of the present invention.
- the order of the operations described in the embodiments of the present invention may be changed. Some components or features of one embodiment may be included in another embodiment, or may be replaced with corresponding components or features of another embodiment.
- Embodiments of the present invention may be supported by standard documents disclosed in at least one of the wireless access systems IEEE 802.xx system, 3GPP system, 3GPP LTE system and 3GPP2 system. That is, obvious steps or parts which are not described among the embodiments of the present invention may be described with reference to the above documents.
- UMTS Universal Mobile Telecommunications System
- GSM Global System for Mobile Communication
- Evolved Packet System A network system composed of an Evolved Packet Core (EPC), which is a packet switched (PS) core network based on Internet Protocol (IP), and an access network such as LTE / UTRAN.
- EPC Evolved Packet Core
- PS packet switched
- IP Internet Protocol
- UMTS is an evolutionary network.
- NodeB base station of GERAN / UTRAN. It is installed outdoors and its coverage is macro cell size.
- eNodeB base station of E-UTRAN. It is installed outdoors and its coverage is macro cell size.
- UE User Equipment
- the UE may be referred to in terms of terminal, mobile equipment (ME), mobile station (MS), and the like.
- the UE may be a portable device such as a laptop, a mobile phone, a personal digital assistant (PDA), a smart phone, a multimedia device, or the like, or may be a non-portable device such as a personal computer (PC) or a vehicle-mounted device.
- the term UE or UE may refer to an MTC device.
- HNB Home NodeB
- HeNB Home eNodeB: A base station of an EPS network, which is installed indoors and its coverage is micro cell size.
- Mobility Management Entity A network node of an EPS network that performs mobility management (MM) and session management (SM) functions.
- Packet Data Network-Gateway (PDN-GW) / PGW / P-GW A network node of an EPS network that performs UE IP address assignment, packet screening and filtering, charging data collection, and the like.
- SGW Serving Gateway
- S-GW network node of EPS network performing mobility anchor, packet routing, idle mode packet buffering, triggering MME to page UE, etc. .
- Non-Access Stratum Upper stratum of the control plane between the UE and the MME.
- Packet Data Network A network in which a server supporting a specific service (eg, a Multimedia Messaging Service (MMS) server, a Wireless Application Protocol (WAP) server, etc.) is located.
- a server supporting a specific service eg, a Multimedia Messaging Service (MMS) server, a Wireless Application Protocol (WAP) server, etc.
- MMS Multimedia Messaging Service
- WAP Wireless Application Protocol
- PDN connection A logical connection between the UE and the PDN, represented by one IP address (one IPv4 address and / or one IPv6 prefix).
- RAN Radio Access Network: a unit including a NodeB, an eNodeB and a Radio Network Controller (RNC) controlling them in a 3GPP network. It exists between UEs and provides a connection to the core network.
- RNC Radio Network Controller
- HLR Home Location Register
- HSS Home Subscriber Server
- PLMN Public Land Mobile Network
- Proximity Service (or ProSe Service or Proximity based Service): A service that enables discovery and direct communication between physically close devices or communication through a base station or through a third party device. In this case, user plane data is exchanged through a direct data path without passing through a 3GPP core network (eg, EPC).
- EPC 3GPP core network
- ProSe communication Means communication through a ProSe communication path between two or more ProSe capable terminals. Unless specifically stated otherwise, ProSe communication may mean one of ProSe E-UTRA communication, ProSe-assisted WLAN direct communication between two terminals, ProSe group communication, or ProSe broadcast communication.
- ProSe E-UTRA communication ProSe communication using the ProSe E-UTRA communication path.
- ProSe-assisted WLAN direct communication ProSe communication using a direct communication path.
- ProSe communication path As a communication path supporting ProSe communication, a ProSe E-UTRA communication path may be established between ProSe-enabled UEs or through a local eNB using E-UTRA. ProSe-assisted WLAN direct communication path can be established directly between ProSe-enabled UEs using WLAN.
- EPC path (or infrastructure data path): User plane communication path through EPC.
- ProSe Discovery A process of identifying / verifying a nearby ProSe-enabled terminal using E-UTRA.
- ProSe Group Communication One-to-many ProSe communication using a common communication path between two or more ProSe-enabled terminals in close proximity.
- ProSe UE-to-Network Relay A ProSe-enabled public safety terminal operating as a communication relay between a ProSe-enabled network using E-UTRA and a ProSe-enabled public safety terminal.
- ProSe UE-to-UE Relay A ProSe-enabled public safety terminal operating as a ProSe communication relay between two or more ProSe-enabled public safety terminals.
- -Remote UE In the UE-to-Network Relay operation, a ProSe-enabled public safety terminal that is connected to the EPC network through ProSe UE-to-Network Relay without receiving service by E-UTRAN, that is, provides a PDN connection, and is a UE.
- a ProSe-enabled public safety terminal In -to-UE Relay operation, a ProSe-enabled public safety terminal that communicates with other ProSe-enabled public safety terminals through a ProSe UE-to-UE Relay.
- ProSe-enabled Network A network that supports ProSe Discovery, ProSe Communication, and / or ProSe-assisted WLAN direct communication.
- the ProSe-enabled Network may be referred to simply as a network.
- ProSe-enabled UE a terminal supporting ProSe discovery, ProSe communication and / or ProSe-assisted WLAN direct communication.
- the ProSe-enabled UE and the ProSe-enabled Public Safety UE may be called terminals.
- Proximity Satisfying proximity criteria defined in discovery and communication, respectively.
- SLP SULP Location Platform
- SLP An entity that manages Location Service Management and Position Determination.
- SLP includes a SPL (SUPL Location Center) function and a SPC (SUPL Positioning Center) function.
- SPL SUPL Location Center
- SPC SUPL Positioning Center
- OMA Open Mobile Alliance
- the application / service layer includes Temporary Mobile Group Identity (TMGI) for each MBMS service, session start and end time, frequencies, MBMS service area identities (MBMS SAIs) information belonging to the MBMS service area. To put in USD to the terminal. See 3GPP TS 23.246 for details.
- TMGI Temporary Mobile Group Identity
- MBMS SAIs MBMS service area identities
- ISR Interle mode Signaling Reduction
- Mission Critical Push To Talk Group communication service that provides fast setup time, the ability to handle large groups, powerful security, and priority handling.
- ANDSF Access Network Discovery and Selection Function: Provides a policy that allows a terminal to discover and select available access on an operator basis as a network entity.
- ISRP Inter-System Routing Policy
- IFOM IP Flow Mobility
- MAPCON Multi Access PDN Connectivity
- NSWO non-seamless WLAN offload
- IP Flow Mobility (IFOM) rule This rule prioritizes the access technology / access networks that should be used by the UE when it is able to route traffic that matches a particular IP traffic filter on a particular APN or any APN. It's a list. In addition, this rule may specify for which wireless access the traffic that matches a particular IP traffic filter on a particular APN or any APN is restricted.
- IOM IP Flow Mobility
- MAPCON Multi Access PDN Connectivity
- This rule is a list of prioritized access technologies / access networks that should be used by the UE when it is possible to route PDN connections to a particular APN.
- this rule may specify to which radio access the PDN connection to a particular APN should be restricted.
- Non-seamless WLAN offload (NSWO) rule This rule specifies which traffic should be bypassed to the WLAN or not.
- ISMP Inter-System Mobility Policy: A set of rules defined by an operator to influence intersystem mobility decisions performed by a UE. When the UE can route IP traffic on a single radio access interface, the UE can use ISMP to select the most appropriate access technology type or access network at a given time.
- RAN rule A rule received from the network, also called Radio Access Network (RAN) support information.
- the RAN rule is also referred to as WLAN interworking supported by the RAN used without ANDSF ISRP / ISMP.
- the AS (Access Stratum) layer of the UE carries the move-traffic-to-WLAN indication and WLAN identifier together to the upper layer of the UE.
- the AS (Access Stratum) layer of the UE delivers the move-traffic-from-WLAN indication and the WLAN identifier together to the upper layer of the UE.
- TS 23.401 For a detailed description of the RAN rule, refer to 3GPP TS 23.401, TS 23.060, TS 23.402, TS 36.300, TS 36.304, TS 36.331, TS 25.304 and TS 25.331.
- Local Operating Environment Information This is a set of implementation specific parameters which describe the local environment in which the UE is operating.
- NBIFOM Network-Based IP Flow Mobility
- NBIFOM UE-initiated NBIFOM in which the UE initiates IP flow mobility.
- NBIFOM Network-initiated NBIFOM
- Multi-access PDN connection PDN connection through which traffic can be routed via 3GPP access or WLAN access or both accesses. However, each IP flow is only routed through one access at a time.
- Routing filter A set of IP header parameter values / ranges of a packet flow used to identify an IP flow for routing purposes.
- Routing access type Type of access (3GPP access or WLAN access) that routes the set of IP flows of the PDN connection.
- Routing Rule A set of information that allows the association of routing filters with routing access types.
- FIG. 1 is a diagram illustrating a schematic structure of an EPS (Evolved Packet System) including an Evolved Packet Core (EPC).
- EPS Evolved Packet System
- EPC Evolved Packet Core
- SAE System Architecture Evolution
- SAE is a research project to determine network structure supporting mobility between various kinds of networks.
- SAE aims to provide an optimized packet-based system, for example, supporting various radio access technologies on an IP basis and providing enhanced data transfer capabilities.
- the EPC is a core network of an IP mobile communication system for a 3GPP LTE system and may support packet-based real-time and non-real-time services.
- a conventional mobile communication system i.e., a second generation or third generation mobile communication system
- the core network is divided into two distinct sub-domains of circuit-switched (CS) for voice and packet-switched (PS) for data.
- CS circuit-switched
- PS packet-switched
- the function has been implemented.
- the sub-domains of CS and PS have been unified into one IP domain.
- EPC IP Multimedia Subsystem
- the EPC may include various components, and in FIG. 1, some of them correspond to a serving gateway (SGW), a packet data network gateway (PDN GW), a mobility management entity (MME), and a serving general packet (SGRS) Radio Service (Supporting Node) and Enhanced Packet Data Gateway (ePDG) are shown.
- SGW serving gateway
- PDN GW packet data network gateway
- MME mobility management entity
- SGRS serving general packet
- Radio Service Upporting Node
- ePDG Enhanced Packet Data Gateway
- the SGW acts as a boundary point between the radio access network (RAN) and the core network, and is an element that functions to maintain a data path between the eNodeB and the PDN GW.
- the SGW serves as a local mobility anchor point. That is, packets may be routed through the SGW for mobility in the E-UTRAN (Universal Mobile Telecommunications System (Evolved-UMTS) Terrestrial Radio Access Network defined in 3GPP Release-8 or later).
- E-UTRAN Universal Mobile Telecommunications System (Evolved-UMTS) Terrestrial Radio Access Network defined in 3GPP Release-8 or later.
- SGW also provides mobility with other 3GPP networks (RANs defined before 3GPP Release-8, such as UTRAN or GERAN (Global System for Mobile Communication (GSM) / Enhanced Data rates for Global Evolution (EDGE) Radio Access Network). It can also function as an anchor point.
- RANs defined before 3GPP Release-8 such as UTRAN or GERAN (Global System for Mobile Communication (GSM) / Enhanced Data rates for Global Evolution (EDGE) Radio Access Network). It can also function as an anchor point.
- GSM Global System for Mobile Communication
- EDGE Enhanced Data rates for Global Evolution
- the PDN GW corresponds to the termination point of the data interface towards the packet data network.
- the PDN GW may support policy enforcement features, packet filtering, charging support, and the like.
- mobility management between 3GPP networks and non-3GPP networks for example, untrusted networks such as Interworking Wireless Local Area Networks (I-WLANs), code-division multiple access (CDMA) networks, or trusted networks such as WiMax) Can serve as an anchor point for.
- untrusted networks such as Interworking Wireless Local Area Networks (I-WLANs), code-division multiple access (CDMA) networks, or trusted networks such as WiMax
- I-WLANs Interworking Wireless Local Area Networks
- CDMA code-division multiple access
- WiMax trusted networks
- FIG. 1 shows that the SGW and the PDN GW are configured as separate gateways, two gateways may be implemented according to a single gateway configuration option.
- the MME is an element that performs signaling and control functions to support access to the network connection of the UE, allocation of network resources, tracking, paging, roaming and handover, and the like.
- the MME controls control plane functions related to subscriber and session management.
- the MME manages a number of eNodeBs and performs signaling for the selection of a conventional gateway for handover to other 2G / 3G networks.
- the MME also performs functions such as security procedures, terminal-to-network session handling, and idle terminal location management.
- SGSN handles all packet data, such as user's mobility management and authentication to other 3GPP networks (eg GPRS networks).
- 3GPP networks eg GPRS networks.
- the ePDG acts as a secure node for untrusted non-3GPP networks (eg, I-WLAN, WiFi hotspots, etc.).
- untrusted non-3GPP networks eg, I-WLAN, WiFi hotspots, etc.
- a terminal having IP capability is provided by an operator (ie, an operator) via various elements in the EPC, based on 3GPP access as well as non-3GPP access.
- Access to an IP service network eg, IMS.
- FIG. 1 also shows various reference points (eg, S1-U, S1-MME, etc.).
- reference points eg, S1-U, S1-MME, etc.
- Table 1 summarizes the reference points shown in FIG. 1.
- This reference point can be used in PLMN-to-PLMN-to-PLMN-to-for example (for PLMN-to-PLMN handover).
- This reference point can be used intra-PLMN or inter-PLMN (eg in the case of Inter-PLMN HO).)
- S4 Reference point between SGW and SGSN that provides related control and mobility support between the GPRS core and SGW's 3GPP anchor functionality.It also provides user plane tunneling if no direct tunnel is established.
- 3GPP Anchor function of Serving GW In addition, if Direct Tunnel is not established, it provides the user plane tunnelling.
- S5 Reference point providing user plane tunneling and tunnel management between the SGW and the PDN GW. It provides user plane tunneling and tunnel management between Serving GW and PDN GW.
- the PDN may be an operator external public or private PDN or, for example, an in-operator PDN for the provision of IMS services. 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, eg 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 that provides the user plane with associated control and mobility support between trusted non-3GPP access and PDN GW.
- S2b is a reference point that provides the user plane with relevant control and mobility support between the ePDG and PDN GW.
- FIG. 2 is an exemplary view showing the architecture of a general E-UTRAN and EPC.
- the eNodeB routes resources to the gateway, scheduling and sending paging messages, scheduling and sending broadcast channels (BCHs), and uplink and downlink resources while the Radio Resource Control (RRC) connection is active.
- Functions such as dynamic allocation to UE, configuration and provision for measurement of eNodeB, radio bearer control, radio admission control, and connection mobility control may be performed.
- paging can be generated, LTE_IDLE state management, user plane encryption, SAE bearer control, NAS signaling encryption and integrity protection.
- FIG. 3 is an exemplary diagram illustrating a structure of a radio interface protocol in a control plane between a terminal and a base station
- FIG. 4 is an exemplary diagram illustrating a structure of a radio interface protocol in a user plane between a terminal and a base station. .
- the air interface protocol is based on the 3GPP radio access network standard.
- the air interface protocol is composed of a physical layer, a data link layer, and a network layer horizontally, and a user plane and control for data information transmission vertically. It is divided into a control plane for signal transmission.
- the protocol layers are based on the lower three layers of the Open System Interconnection (OSI) reference model, which is widely known in communication systems, and includes L1 (first layer), L2 (second layer), and L3 (third layer). ) Can be separated.
- OSI Open System Interconnection
- the physical layer which is the first layer, provides an information transfer service using a physical channel.
- the physical layer is connected to a medium access control layer on the upper side through a transport channel, and data between the medium access control layer and the physical layer is transmitted through the transport channel.
- data is transferred between different physical layers, that is, between physical layers of a transmitting side and a receiving side through a physical channel.
- the physical channel is composed of several subframes on the time axis and several subcarriers on the frequency axis.
- one subframe is composed of a plurality of OFDM symbols and a plurality of subcarriers on the time axis.
- One subframe consists of a plurality of resource blocks, and one resource block consists of a plurality of OFDM symbols and a plurality of subcarriers.
- the transmission time interval (TTI) which is a unit time for transmitting data, is 1 ms corresponding to one subframe.
- the physical channels existing in the physical layer of the transmitting side and the receiving side are physical downlink shared channel (PDSCH), physical uplink shared channel (PUSCH) and physical downlink control channel (PDCCH), which are control channels, It may be divided into a Physical Control Format Indicator Channel (PCFICH), a Physical Hybrid-ARQ Indicator Channel (PHICH), and a Physical Uplink Control Channel (PUCCH).
- PCFICH Physical Control Format Indicator Channel
- PHICH Physical Hybrid-ARQ Indicator Channel
- PUCCH Physical Uplink Control Channel
- the medium access control (MAC) layer of the second layer serves to map various logical channels to various transport channels, and also logical channels to map several logical channels to one transport channel. Perform the role of multiplexing.
- the MAC layer is connected to the upper layer RLC layer by a logical channel, and the logical channel includes a control channel for transmitting information of a control plane according to the type of information to be transmitted. It is divided into a traffic channel that transmits user plane information.
- the Radio Link Control (RLC) layer of the second layer adjusts the data size so that the lower layer is suitable for transmitting data to the radio section by segmenting and concatenating data received from the upper layer. It plays a role.
- RLC Radio Link Control
- the Packet Data Convergence Protocol (PDCP) layer of the second layer is an IP containing relatively large and unnecessary control information for efficient transmission in a wireless bandwidth where bandwidth is small when transmitting an IP packet such as IPv4 or IPv6. Performs Header Compression which reduces the packet header size.
- the PDCP layer also performs a security function, which is composed of encryption (Ciphering) to prevent third-party data interception and integrity protection (Integrity protection) to prevent third-party data manipulation.
- the radio resource control layer (hereinafter abbreviated as RRC) layer located at the top of the third layer is defined only in the control plane, and the configuration and reconfiguration of radio bearers (abbreviated as RB) are performed. It is responsible for the control of logical channels, transport channels and physical channels in relation to configuration and release.
- RB means a service provided by the second layer for data transmission between the terminal and the E-UTRAN.
- the UE If an RRC connection is established between the RRC of the UE and the RRC layer of the wireless network, the UE is in an RRC connected mode, otherwise it is in an RRC idle mode. .
- the RRC state refers to whether or not the RRC of the UE is in a logical connection with the RRC of the E-UTRAN. If the RRC state is connected, the RRC_CONNECTED state is called, and the RRC_IDLE state is not connected. Since the UE in the RRC_CONNECTED state has an RRC connection, the E-UTRAN can grasp the existence of the UE in units of cells, and thus can effectively control the UE. On the other hand, the UE in the RRC_IDLE state cannot identify the existence of the UE by the E-UTRAN, and the core network manages the unit in a larger tracking area (TA) unit than the cell.
- TA tracking area
- each TA is identified by a tracking area identity (TAI).
- TAI tracking area identity
- the terminal may configure a TAI through a tracking area code (TAC), which is information broadcast in a cell.
- TAC tracking area code
- the terminal When the user first turns on the power of the terminal, the terminal first searches for an appropriate cell, then establishes an RRC connection in the cell, and registers the terminal's information in the core network. Thereafter, the terminal stays in the RRC_IDLE state. The terminal staying in the RRC_IDLE state (re) selects a cell as needed and looks at system information or paging information. This is called camping on the cell.
- the UE staying in the RRC_IDLE state makes an RRC connection with the RRC of the E-UTRAN through an RRC connection procedure and transitions to the RRC_CONNECTED state.
- RRC_CONNECTED state There are several cases in which a UE in RRC_IDLE state needs to establish an RRC connection. For example, a user's call attempt, a data transmission attempt, etc. are required or a paging message is received from E-UTRAN. Reply message transmission, and the like.
- a non-access stratum (NAS) layer located above the RRC layer performs functions such as session management and mobility management.
- NAS non-access stratum
- ESM evolved Session Management
- the NAS layer performs functions such as default bearer management and dedicated bearer management, and is responsible for controlling the terminal to use the PS service from the network.
- the default bearer resource is characterized in that it is allocated from the network when it is connected to the network when it first accesses a specific Packet Data Network (PDN).
- PDN Packet Data Network
- the network allocates an IP address usable by the terminal so that the terminal can use the data service, and also allocates QoS of the default bearer.
- LTE supports two types of bearer having a guaranteed bit rate (GBR) QoS characteristic that guarantees a specific bandwidth for data transmission and reception, and a non-GBR bearer having a best effort QoS characteristic without guaranteeing bandwidth.
- GBR guaranteed bit rate
- Non-GBR bearer is assigned.
- the bearer allocated to the terminal in the network is called an evolved packet service (EPS) bearer, and when the EPS bearer is allocated, the network allocates one ID. This is called EPS Bearer ID.
- EPS bearer ID One EPS bearer has a QoS characteristic of a maximum bit rate (MBR) or / and a guaranteed bit rate (GBR).
- 5 is a flowchart illustrating a random access procedure in 3GPP LTE.
- the random access procedure is performed for the UE to obtain UL synchronization with the base station or to be allocated UL radio resources.
- the UE receives a root index and a physical random access channel (PRACH) configuration index from the eNodeB.
- PRACH physical random access channel
- Each cell has 64 candidate random access preambles defined by a Zadoff-Chu (ZC) sequence, and the root index is a logical index for the UE to generate 64 candidate random access preambles.
- ZC Zadoff-Chu
- the PRACH configuration index indicates a specific subframe and a preamble format capable of transmitting the random access preamble.
- the UE sends the randomly selected random access preamble to the eNodeB.
- the UE selects one of the 64 candidate random access preambles.
- the corresponding subframe is selected by 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.
- RAR random access response
- the random access response is detected in two steps. First, the UE detects a PDCCH masked with random access-RNTI (RA-RNTI). The UE receives a random access response in a medium access control (MAC) protocol data unit (PDU) on the PDSCH indicated by the detected PDCCH.
- MAC medium access control
- RRC 6 shows a connection process in a radio resource control (RRC) layer.
- RRC radio resource control
- the RRC state is shown depending on whether the RRC is connected.
- the RRC state refers to whether or not an entity of the RRC layer of the UE is in a logical connection with an entity of the RRC layer of the eNodeB.
- the RRC state is referred to as an RRC connected state.
- the non-state is called the RRC idle state.
- the E-UTRAN may determine the existence of the corresponding UE in units of cells, and thus may effectively control the UE.
- the UE in the idle state can not be identified by the eNodeB, the core network (core network) is managed by the tracking area (Tracking Area) unit larger than the cell unit.
- the tracking area is a collection unit of cells. That is, the idle state (UE) is determined only in the presence of the UE in a large area, and in order to receive a normal mobile communication service such as voice or data, the UE must transition to the connected state (connected state).
- the UE When a user first powers up a UE, the UE first searches for an appropriate cell and then stays in an idle state in that cell. When the UE staying in the idle state needs to establish an RRC connection, the UE establishes an RRC connection with the RRC layer of the eNodeB through an RRC connection procedure and transitions to an RRC connected state. .
- the UE in the idle state needs to establish an RRC connection. For example, a user's call attempt or uplink data transmission is required, or a paging message is received from EUTRAN. In this case, the response message may be transmitted.
- the RRC connection process is largely a process in which a UE sends an RRC connection request message to an eNodeB, an eNodeB sends an RRC connection setup message to the UE, and a UE completes RRC connection setup to the eNodeB. (RRC connection setup complete) message is sent. This process will be described in more detail with reference to FIG. 6 as follows.
- the eNB When the RRC connection request message is received from the UE, the eNB accepts the RRC connection request of the UE when the radio resources are sufficient, and transmits an RRC connection setup message, which is a response message, to the UE. .
- the UE When the UE receives the RRC connection setup message, it transmits an RRC connection setup complete message to the eNodeB. When the UE successfully transmits an RRC connection establishment message, the UE establishes an RRC connection with the eNodeB and transitions to the RRC connected mode.
- V2X vehicle to everything
- V2X LTE-based vehicle-to-everything
- IT Informatin Technology
- V2V vehicle-to-infrastructure
- V2I vehicle-to-infrastructure
- V2P vehicle-to-pedestrian
- V2N vehicle-to-network
- the vehicle continuously broadcasts information about its position, speed, direction, and the like.
- the surrounding vehicle that receives the broadcasted information recognizes the movement of the vehicles around itself and utilizes it for accident prevention.
- each vehicle similarly to an individual having a terminal having a form of a smart phone or a smart watch, each vehicle also installs a specific type of terminal (or user equipment (UE)).
- the UE installed in the vehicle refers to a device that receives the actual communication service in the communication network.
- the UE installed in the vehicle may be connected to the eNB in the E-UTRAN to receive the communication service.
- V2X communication there are many things to consider when implementing V2X communication in a vehicle. This is because astronomical costs are required for the installation of traffic safety infrastructure such as V2X base stations. That is, to support V2X communication on all roads where the vehicle can move, more than hundreds of thousands of V2X base stations need to be installed. In addition, since each network node is connected to the Internet or a central control server using a wired network as a base for stable communication with a server, the installation maintenance cost of the wired network is also high.
- RSU Raad Side Unit
- An entity supporting V2I communication and means an entity capable of transmitting to and receiving from a UE using a V2I application.
- the RSU may be implemented in an eNB or a UE (especially a stationary UE).
- An eNB or UE operating as an RSU collects traffic safety related information (e.g., traffic light information, traffic volume information, etc.) and / or information about surrounding vehicle movements, and transmits the information to other UEs subject to V2I communication. Transmit or receive information from another UE.
- traffic safety related information e.g., traffic light information, traffic volume information, etc.
- V2I communication In one type of V2X communication, a UE and an RSU using a V2I application become the subject of communication.
- V2N communication In one type of V2X communication, a UE and a serving entity using a V2N application become a subject of communication, and the UE and the serving entity communicate with each other through an LTE network entity.
- V2P communication In one type of V2X communication, two UEs using a V2P application become the subject of communication.
- V2V communication In one type of V2X communication, two UEs using a V2V application become the subject of communication. What is distinguished from V2P communication is that in V2P communication, any one terminal becomes a terminal of a pedestrian, whereas in V2V communication, either terminal becomes a terminal of a vehicle.
- Uu interface means an interface between a UE and an eNB defined in LTE / LTE-A. In a relay node, this may mean an interface between the relay node and the UE.
- Un interface means an interface between a relay node and an eNB.
- MBSFN Multimedia Broadcast / Multicast Services
- MBSFN Single Frequency Network
- PC5 interface means an interface used for direct communication between two UEs, and is an interface used for communication between devices supporting ProSE (Proximity Service).
- ProSE Proximity Service
- DSRC Dedicated Shiort Range Communications
- FIG. 8 is a diagram illustrating an infrastructure structure to which the proposed communication method is applied.
- an operator or an institution that wants to provide a service based on V2X communication constructs an infrastructure using a UE instead of an eNB.
- an eNB When constructing a V2X-based infrastructure using the eNB, it is expensive to install due to the nature of the eNB to manage a large number of UEs, configure and control radio resources, and configure a backbone using a wired network.
- the UE when constructing a V2X-based infrastructure using the UE, the UE can be miniaturized and can be easily installed anywhere. For example, simply attaching and connecting a UE to a traffic light allows the traffic light to be used as a V2X infrastructure (eg, RSU).
- a V2X infrastructure eg, RSU
- the UE since the UE is basically connected to the cellular network, the user can conveniently control the V2X infrastructure wirelessly without installing the backbone of the wired network.
- Operators or organizations that build a V2X infrastructure using the UE may configure the UE to operate as an RSU for V2X communication or to provide a communication relay service by remotely controlling the UE or performing configuration through wireless. .
- the above-described UE may operate to perform the function of the RSU, and may simultaneously or selectively operate to perform the relay function as a relay node.
- the relay function refers to a function of the UE providing an internet connectivity to other UEs in the vicinity.
- the UE again accesses a node such as an eNB or an AP according to a wireless communication service standard such as 3G / 4G / 5G or WiFi.
- a wireless communication service standard such as 3G / 4G / 5G or WiFi.
- the UE supporting the Internet connection can connect to a communication network using a 3G / 4G / 5G or WiFi wireless communication service, and at the same time, relay and provide an Internet service to a smartphone connected to the UE.
- Operators / organizations that build and operate V2X infrastructures can monitor the situation in areas where UEs that provide Internet connectivity are installed. The operator / agency then decides whether to use the UE as an RSU or a relay node according to its own criteria. The determined content is communicated to the UE using a predetermined communication protocol, and the UE operates as an RSU or a relay node according to the instruction.
- the above-described monitoring process, decision process, and instruction to the UE may be performed according to a user's instruction, or may be implemented by software and automated.
- the UE may determine the interface specification to be used by the UE. That is, the operator / organization may determine the interface specification to be used with the function to operate the UE and instruct the UE. For example, when the UE operates as an RSU, the UE may operate as a Uu interface in communication with the eNB in consideration of the indicated interface specification, and operate as a PC5 interface in communication with another UE. In another example, when the UE operates as a relay node (for example, a relay node according to the 3GPP standard standard), the UE operates as an Un interface in the process of communicating with the eNB according to the indicated interface standard and with another UE.
- the UE may determine the interface specification to be used by the UE. That is, the operator / organization may determine the interface specification to be used with the function to operate the UE and instruct the UE. For example, when the UE operates as an RSU, the UE may operate as a Uu interface in communication with the eNB in consideration of the indicated interface specification, and operate as
- a UE operating as an RSU may communicate with an eNB over a PC5 interface.
- a UE operating as a relay node (UE-to-Network Relay (Layer-3 Relay or Application Layer Relay) of 3GPP standard) may communicate with an eNB via a Uu interface. If a function and interface supported by the UE match, the operator / organization simply informs the UE whether to perform the RSU or the relay node, and the interface is automatically determined. However, when the UE supports a plurality of interfaces, the operator / organization may select and inform any one of the plurality of interfaces with the function to operate.
- the operator / organization efficiently constructs the V2X infrastructure using the UE and dynamically controls the UE according to the change of the communication environment.
- the operator / organization can use the UE as an infrastructure such as an RSU or a relay node, thereby increasing the capacity of the communication network. It is possible to increase the supply of small cells.
- Node 11 Represents a base station, and may correspond to, for example, an eNB of an E-UTRAN.
- Node 12 Represents a Core Network (CN), for example MME, S-GW, P-GW, or other providing V2X services (service authorization, provisioning, identity management, etc.) It can be an entity.
- CN Core Network
- Node 13 Represents a node for a terminal, device, server, IP Multimedia System (IMS), or PCR Charging Resource Function (PCRF) of an administrator network.
- IMS and / or PCRF may be implemented to be included in node 12.
- an administrator may send a command directly to the UE, or the command may be automatically sent to the UE by a software program written by the administrator.
- the node 13 may transmit a command determined based on the information received from each node.
- the command generated by the node 13 may be transmitted to the nodes 21, 22, 23, 24, etc. via the node 12, the node 11.
- node 13 may delegate to node 11 or node 12 the function of determining and controlling the command, depending on how it is implemented.
- the node 11 (eNB) managing radio resources may configure which modes the nodes 21, 22, 23, and 24 operate, and each of the nodes 21, 22, 23, and 24 operates according to the configuration of the node 11. can do.
- the mode indicates whether each node operates to perform an RSU function (RSU mode) or a relay function (relay node).
- node 13 may instruct which node (eg, Uu, Un, PC5, DSRC, etc.) each node communicates with other nodes connected to it. Nodes that receive the set information from node 13 operate according to the setting.
- the node 13 may receive traffic information related to V2X communication from other lower nodes, and may receive and reprocess ITS related information from an intelligent transport system (ITS) related server and transmit the same to the lower nodes or the ITS server.
- ITS intelligent transport system
- Node 21 This node performs the function of the RSU. That is, it is a node operating in the RSU mode.
- the communication connection service is provided from the node 11 through the Un interface 101, and the communication connection service is provided to other terminals (or nodes).
- Node 21 may provide V2X related services to other nodes.
- node 21 provides a communication connection service to node 22 via Uu interface 201.
- Node 21 may simply be installed in facilities such as power poles, cradles, traffic lights, etc., and when installed in traffic-related equipment, it may exchange information with traffic-related facilities.
- node 21 may be implemented as a UE (especially a fixed UE).
- Node 22 Another node that performs the function of the RSU.
- the communication connection service is provided from the node 11 through the Uu interface 102, and provides V2X related services to other terminals or nodes.
- Node 22 supports multiple V2X services based on different communication technologies.
- a node 22 implemented as a UE having both a communication module supporting the DSRC and an LTE communication module can support both the V2X service supporting the LTE-based PC5 interface and the VRC-based V2X service. Accordingly, the node 22 may transmit the V2X service information received using the DSRC using the LTE V2X service and perform the reverse operation.
- node 22 receives V2X information from node 34 operating via DSRC 305 and reprocesses the received information in the application to node 33 via LTE-based V2X communication using PC5 interface 304. send.
- the node 22 may receive V2X information from the node 33 operating through the LTE-based V2X communication using the PC5 interface 304, and may transmit the V2X information to the node 34 through the DSRC 305-based V2X communication.
- the node 22 may transmit traffic related information received from V2X terminals (nodes 33 and 34) managed by the node 22 or traffic related information collected from other devices to nodes 11, 12, and 13 which are higher nodes.
- the node 22 may transfer the information generated and received at the node 11, the node 12, and the node 13 to the node 33 and the node 34.
- Node 23 This node performs the function of a relay node. That is, it is a node operating in the relay mode.
- the node 23 receives the communication connection service from the node 11 through the Uu interface 103, and provides the communication connection service using the PC5 interface 306 to node 35, which is another terminal. That is, the node 23 is not only a terminal accessing a broadband communication network but also provides a communication service to other terminals.
- node 23 may use the Uu interface to provide communication service to node 35. That is, node 23 is connected to node 12 and node 13 through node 11, and if the administrator's setting determines which interface to use for communication with node 11 and communication with node 35, node 23 operates according to the setting. do. In this process, the node 23 may determine whether to operate to perform the function of the RSU, continue to operate as a relay node, perform both operations, or not perform both operations depending on the configuration.
- Node 24 A node that performs the function of a relay node, that is, operates in a relay mode. Node 24 receives service from node 11 via Un interface 104 and provides service to node 36 using Uu interface 307. That is, the node 24 is a terminal accessing the broadband communication network and also provides a communication service to other nodes.
- the above nodes 21 to 24 may be implemented by the UE as described above.
- Node 31 A terminal such as a smartphone. V2X related services are provided from node 21 or node 22 performing RSU functions.
- Node 32 A terminal installed in a vehicle.
- the node 32 exchanges V2X related information with a node 31 supporting the V2X function or a node 33 installed in another vehicle.
- the PC5 interface may be used in this transmission and reception process.
- the node 32 may transmit and receive V2X related information with the node 22 operating in the RSU mode.
- Node 33 A terminal installed in a vehicle. It exchanges V2X information with node 32, which is a terminal installed in another vehicle, and exchanges V2X information with node 22 operating in RSU mode. If node 33 supports only LTE-based V2X services, node 33 cannot receive V2X-related data directly from node 34 supporting DSRC-based V2X services, and supports multiple V2X service protocols such as node 22. Receive V2X data from a node. In addition to the V2X related module, the node 33 may further include a module for collecting sensing information from a sensor installed in a vehicle, and a module for integrating and processing the information received through the V2X.
- Node 34 A terminal installed in a vehicle, which communicates with and receives information from terminals installed in another vehicle. In addition, information is received from a node that supports the RSU function, such as node 22. If node 34 supports only DSRC-based V2X service, node 34 cannot receive V2X data directly from terminal 33 supporting LTE-based V2X service and relays V2X data through node 22.
- Node 35 A terminal such as a smartphone, and receives communication connection service from node 23.
- Node 36 A terminal, such as a smartphone, supported by a communication connection service from Node 24.
- the nodes 21, 22, 23, 24 may be located in a good communication environment, that is, a high zone and observable everywhere.
- nodes 21, 22, 23, and 24 operate as RSUs and transmit traffic information around, or act as relay nodes, and provide communication connection services, nodes 21, nodes 22, 23, and 24 need to be connected prior to other terminals. There is. Therefore, in order for a terminal operating as an RSU or a relay node to be preferentially allocated radio resources in the illustrated infrastructure, the terminal operating as an RSU or a relay node should first request a radio resource from the node 11.
- the UE accessing the E-UTRAN when the UE accessing the E-UTRAN operates as an RSU or a relay node, the UE may operate or operate as an RSU or a relay node in an RRC connection request (ie, a capability ( capability)).
- a terminal operating as an RSU or a relay node may operate or operate as an RSU or a relay node in a service request, attach procedure, or tracking area update (TAU) procedure of a NAS layer.
- TAU tracking area update
- the network may preferentially allocate radio resources to a terminal to operate as an RSU or relay node in response to a request from the terminal.
- whether the UE operates as one of two functions or both can be stored in the subscriber information.
- the network may determine whether to allocate radio resources to the terminal in consideration of information received from the terminal and subscriber information.
- the network may also determine whether to allocate radio resources to the terminal in consideration of previously stored subscriber information.
- the node 13 transmits the determined information to the node 12 or the node 11, and the node 11 may preferentially allocate radio resources to the node 21.
- nodes 21, 22, 23, and 24 should operate normally without failure. If a problem occurs in these nodes, a quick recovery must be made, so it is required to quickly recognize abnormal behavior of the nodes.
- a terminal operating as an RSU or a relay node should periodically exchange information with one or more of the nodes 11, 12, and 13. That is, the node 11, the node 12, and / or the node 13 may set the node 21 to the node 24 to inform whether the node operates normally at predetermined time intervals. Accordingly, the nodes 21 to 24 may periodically notify the nodes 11 to 13 of their status. This operation may be implemented through a periodic TAU procedure.
- the ITS operator may install an RSU implemented as a UE to provide the ITS service. Based on the UE, it is possible to transmit information or provide ITS services to terminals related to vehicles or traffic using the Uu interface and the PC5 interface.
- the ITS operator may switch the configuration of some of the UE-based RSUs to the relay node by using the ITS network composed of the UE-based RSUs established. Can be. Accordingly, the number of cells increases, and the capacity of the mobile data service is easily increased.
- an operator providing a mobile data service may install a UE-based relay node in advance to establish a network, and then, when the V2X service (ie, the ITS service) is activated, change the configuration of the previously installed relay node to the ITS infrastructure equipment. It can be used as an RSU for transmitting V2X information.
- V2X service ie, the ITS service
- the operator who builds a communication network or V2X network using the UE can be installed after the implementation to support a plurality of communication standards and a plurality of interfaces to the UE in advance.
- the UE may be installed after the UE is implemented to operate according to various interfaces and functions such as the Uu interface, the Un interface, the PC5 interface, the DSRC function, and the 802.11p function defined by the IEEE. Accordingly, by remotely transmitting the configuration information to the UE, it is possible to simply inform what function and interface the UE will operate.
- the V2X infrastructure shown in FIG. 8 may be variously changed as shown in FIGS. 9 to 10 below according to the design change of the operator. That is, changes (or resets) such as changing the function that node 21 or node 22 operates, changing the communication interface between node 11 and node 21, or changing the interface between node 22 and node 32, node 33, node 34, and so on. Is possible.
- FIG. 9 and 10 are diagrams illustrating another infrastructure to which the proposed communication method is applied.
- FIG. 9 is an embodiment in which the function of node 21 is changed in the infrastructure shown in FIG. 8, and
- FIG. 10 is an interface 101, 102, 201, 301, 302, 303, 304 is changed in the infrastructure shown in FIG. Each embodiment is illustrated.
- the operation mode of the UE constituting the V2X infrastructure may be determined by one or more of the nodes 11, 12, and 13.
- the determined operating mode (or operating mode and interface) of the UE is communicated to node 21, node 22, node 23, node 24.
- the nodes 21 to 24 perform a matching function when the triggering condition is satisfied (that is, matched). Mode) or perform communication using a matching interface.
- the node 22 may preset the triggering condition when the number of vehicles becomes less than or equal to a predetermined number within a region of a predetermined size managed by the node 22.
- the node 22 detects that the number of vehicles satisfies the triggering condition (that is, when the number of surrounding vehicles increases by more than a certain number or decreases by a certain number)
- the node 22 performs an operation matched with the triggering condition.
- the node 22 may change the interface from the PC5 to the Uu interface from the node 32 to the node 34 as the triggering condition is satisfied.
- the node 21 may set another triggering condition when the number of nodes for which the communication service is desired is greater than or equal to a certain number.
- the node 21 when the node 21 which is operating while performing the RSU function detects that the triggering condition is satisfied, the node 21 may stop the operation of the RSU function and start the operation as the relay node (21 in FIG. 9).
- the operation matching with the setting of the triggering condition is performed according to the settings of the node 21 and the node 22 itself, or the node 21 and the node 22 receive information about their own situation and surrounding situation that the triggering condition is satisfied. Node 12, node 13).
- a UE operating as an RSU or relay node may be implemented in various ways.
- the UE may be provided with a communication connection service through the Un interface with the eNB (104 of FIG. 10), and may provide communication service through the Uu interface to another UE connected to the UE (307 of FIG. 10).
- the UE is to perform the role of a relay node.
- the UE may perform the role of UE-to-Network, in which case the UE is provided with a communication connection service using the eNB and the Uu interface (103 in FIG. 10), and the other connected to itself.
- the UE may provide a communication connection service through the PC5 interface (306 of FIG. 10).
- FIG. 11 illustrates another infrastructure to which the proposed communication method is applied.
- FIG. 11 illustrates an embodiment in which a connection between an eNB and a node 21, a node 22, a node 23, and a node 24 is implemented as a Uu interface.
- FIG. 11 illustrates a construction form when nodes 21 to 24 are UEs that do not support the Un interface with the eNB, that is, when they are not relay nodes.
- Nodes 21 to 24 must support MBSFN related functions defined in 3GPP in order to perform communication using an eNB and an Un interface.
- MBSFN-related functions an additional cost is required for product implementation compared to a terminal that does not support the Un interface. Therefore, the nodes 21 to 24 may be implemented to communicate only with the eNB and the Uu interface.
- 12 illustrates another infrastructure to which the proposed communication method is applied. 12 illustrates an embodiment in which nodes 21 to 24 operate as relay nodes supporting the MBSFN function of 3GPP.
- the nodes 21 to 24 may be implemented to communicate with the eNB according to the MBSFN function.
- 12 illustrates a scenario when nodes 21 to 24 all operate as relay nodes in accordance with MBSFN functionality.
- 13 to 15 are diagrams illustrating another infrastructure to which the proposed communication method is applied.
- FIG. 13 illustrates an embodiment in which nodes 21, 22, 23, and 24 all operate as relay nodes
- FIGS. 14 and 15 illustrate embodiments in which all nodes 21, 22, 23, and 24 operate as RSUs.
- Nodes 21 to 24 implemented as a UE operate according to a scheme set by a network operator or V2X operators, and the operator may collectively change the operation mode during the operation of the nodes.
- the network or V2X operator may change and set nodes 21 to 24 to operate as RSUs collectively as shown in FIG. 13.
- the network or V2X operator may change the interface together with the operation mode of the nodes.
- nodes 21 to 24 communicate with eNBs and other terminals via the Uu interface and PC5 interface, respectively, while nodes 21 to 24 in FIG. 15 use the Uu interface to communicate with other terminals. Perform communication.
- the nodes implemented as the UE change the operation mode
- information indicating that the mode is changed, information about the mode to be changed, etc. may be transmitted to one or more of the nodes 11, 12, and 13.
- Various kinds of system information required for the changed operation mode may be provided when the operation mode is instructed to be changed from the upper node.
- 16 illustrates another infrastructure to which the proposed communication method is applied. 16 shows examples of various infrastructures in which a node that performs an RSU function is implemented.
- FIG. 16 illustrates examples in which a UE is installed in various roadside facilities such as a traffic light, a power pole, and a street lamp (1600). That is, the UE is installed in facilities around the road and operates as an RSU, thus forming a part of the V2X communication network. UEs can be easily installed in multiple locations due to their small size, low installation cost and maintenance costs.
- UEs are managed remotely by V2X / ITS operators or network managers.
- a UE performs a function of which interface is used to access a cellular network or an Internet service network, which interface is used to provide services to neighboring terminals, and which RSU and a relay node are. Remote control such as to operate.
- the UE may operate with a specific function and interface according to a triggering condition that is determined in consideration of changes in the surrounding environment, and may operate with a new setting indicated by the manager / operator even during a predetermined operation.
- 17 is a flowchart illustrating a communication method according to an exemplary embodiment.
- a management unit represents a provider or manager of a core network and corresponds to node 12 or node 13 of FIGS. 8 to 15.
- Operator Network Nodes is a communication network connecting the core network and the UE, and may represent a backbone network composed of an eNB or an MME, and corresponds to node 11 of FIGS. 8 to 15.
- the controlled UE of FIG. 17 indicates a UE installed by an operator / manager and operating as an RSU or a relay node, and corresponds to nodes 21, 22, 23, and 24 of FIGS. 8 to 15.
- the serviced UE indicates a terminal that receives a service by accessing an RSU or a relay node, and corresponds to a node 31, a node 32, a node 33, a node 34, a node 35, and a node 36 of FIGS. 8 to 15.
- FIG. 17 illustrates an embodiment of remotely controlling or setting an operation of a UE installed to build a V2X network.
- the management unit is an entity that transmits a command remotely and may be controlled by a user or implemented as a designated software operation. As shown in the example of FIG. 17, the management entity transmits a message S1710 initiating the RSU mode or a message S1740 initiating the communication relay mode to the installed UE.
- the command from the management entity is delivered to the (Controlled) UE, for example via Operator Network Nodes such as EPC, E-UTRAN, etc. of 3GPP.
- the command from this management entity may not only include information indicating the RSU mode or the relay mode, but also may further include information indicating the interface to be used for each mode.
- the UE Upon receiving the control command, the UE operates in an RSU mode that performs an RSU function (S1720) as provided, and provides a V2X service to surrounding terminals (S1730), or operates in a relay mode that performs a communication relay function (S1730).
- a communication service may be provided to surrounding terminals.
- the UE may change the operation mode and the set interface as indicated by the new command. That is, when a UE operating as an RSU is instructed to operate as a relay node by a network, the UE starts operation as a relay node and simultaneously provides a communication relay function to neighboring terminals using a newly set interface. It works as
- FIG. 18 is a flowchart illustrating a communication method according to another exemplary embodiment.
- FIG. 18 illustrates a process in which an operator preferentially grants access to UEs installed for the purpose of network construction compared to other UEs.
- a radio resource may be allocated to a UE (Controlled UE) that is installed for network construction first, and a UE that is installed for network construction when access is simultaneously requested from several types of terminals. May be preferentially granted access.
- UE Controlled UE
- the controlled UE may be assigned an identifier that is distinguished from other general UEs. That is, the management entity may allocate an identifier that is distinguished from other UEs to a UE that is directly installed, or inform that the UE is a special type of UE (S1810). On the other hand, the management entity may transmit configuration information to the network node (eNB, MME, etc.) indicating that the UE installed for network construction should be processed first to another UE (S1820).
- the network node eNB, MME, etc.
- the UE may inform the assigned identifier together or inform that it is a UE of a type for network establishment (S1840).
- the network node receives the access request from the UE, when the request includes a special identifier or indicates that the request is for a special type of UE, the network node preferentially grants access to the UE (S1850).
- the information indicating that the UE is a special type of UE may be information indicating a UE operating as an RSU or a UE operating as a relay node.
- network nodes received from the management entity that the UE permitted to access the UE for network establishment may allocate radio resources to UEs allowed to access in preference to other general UEs.
- the nodes of the network may perform priority handling for preferentially allocating radio resources to the UE installed for network construction or preferentially allowing access.
- 19 and 20 are diagrams illustrating another infrastructure to which the proposed communication method is applied.
- FIG. 19 shows another embodiment of building a V2X network using UEs.
- the difference between the UEs illustrated in FIG. 19 and FIG. 16 is that, for example, UEs directly used by users, such as a smartphone, may be installed in facilities around a road to configure a V2X network.
- the operator / manager does not need to newly design and produce a UE for operating as an RSU or a relay node, and commercially available terminals may be utilized for network construction.
- smartphones that are connected to an eNB and receive services are installed in traffic lights, power poles, street lights, and the like, they are utilized as an infrastructure of V2X communication, a communication repeater, and a communication base station (FIG. 19).
- the manager / operator who installed the smartphone is a smartphone.
- This can be removed and reused as a general terminal (for example, a user's personal smartphone).
- a pedestrian / user carries a smart phone, it operates as its own personal smart phone, and when installed in a specific place and remotely controlled from a management entity, an infrastructure structure for constructing a part of the network as an RSU or a relay node. It will be operated as (Fig. 20).
- the UE when the UE is installed in traffic lights, street lights, power poles, etc., the UE is required to install software for power connection and communication connection.
- the UE installed through this process is remotely controlled and managed by the V2X / ITS provider or network manager.
- the installed UE remotely controls which interface to access the cellular or Internet service network, which interface will provide services to neighboring terminals, and which functions to perform the functions of the RSU and the relay node. Receive.
- the UE may set a new operation and operate according to surrounding conditions and preset criteria or according to user intervention even during operation.
- the pedestrian can leave his smartphone at the battery charging spot for a while and charge the battery free of charge. While the mobile phone is being charged, the pedestrian's smartphone can operate as an RSU or relay node under control commands from the management entity. In order to be controlled by the management entity, the smartphone to be charged may be temporarily installed with some software. The temporarily installed software is deleted when charging is completed, a pedestrian wants to find his smartphone, or a predetermined time elapses.
- the manager / operator can obtain an effect of improving the communication network without installing an additional UE.
- the pedestrian charging the smartphone can charge the battery free of charge, so there is no burden in providing the smartphone for a predetermined time, so that both the manager / operator and the pedestrian gain.
- 21 through 23 are flowcharts illustrating a communication method, according to another exemplary embodiment.
- the process of notifying network nodes of information related to the capability that the UE may operate as an RSU or a relay node has been briefly described.
- 21 to 23 the above-described capability transmission and reception process will be described in detail.
- FIG. 21 illustrates a method of transmitting and receiving a capability of a UE in an RRC connection request process.
- the UE operable as an RSU or relay node transmits an RRC connection request message to the eNB to establish an RRC connection with the eNB (S2110).
- the eNB transmits an RRC connection establishment message to the UE in response to the received RRC connection request message (S2120).
- the UE that receives the RRC connection establishment message is a UE capable of operating as an RSU or a relay node
- the UE sets up RRC connection information for information indicating that it can operate as an RSU or relay node (ie, capability information). Included in the complete message and transmitted to the eNB (S2130).
- the eNB Upon receiving the capability information, the eNB includes the received capability information in the S1 UE context information message and delivers it to the MME (S2140).
- the MME recognizes that a UE connected through the eNB may serve as an RSU or a relay node. Done.
- the MME transmits a registration request message to transmit the capability information of the UE to the management server of the operator (S2150), and in response, the management server of the operator transmits a registration confirmation message to the MME (S2160).
- the MME recognizes that registration of the UE is completed, the MME transmits an S1 UE context confirmation message to inform the eNB that the capability information of the UE has been confirmed (S2170).
- the eNB informs the UE that the capability information of the UE has been updated through the RRC message (S2180).
- the management server of the eNB, the MME, and the operator acquires information about which UE is connected and whether the connected UE can serve as an RSU or a relay node. Thereafter, the operator's management server (or the core network) remotely controls and operates only the UEs that transmit the capability information that may serve as the RSU or the relay node.
- FIG. 22 illustrates a method for transmitting and receiving capabilities of a UE in an attach request process. 22 illustrates an embodiment of using a NAS message instead of RRC connection setting.
- a UE capable of operating as an RSU or relay node first establishes an RRC connection with the eNB. If the RRC connection is established, the UE transmits a connection request message to the MME (S2210).
- the connection request message may include capability information indicating that the UE may operate as an RSU or a relay node.
- the MME transfers the received capability information to the management server of the operator (S2220), and receives an acknowledgment message from the management server of the operator that stores the capability information of the UE (S2230). As the acknowledgment is received, the MME transmits an access grant message indicating that the capability information has been registered / updated to the UE (S2240).
- the UE may be implemented to transmit its capability information each time the UE connects to the network, but may also be implemented in a manner that utilizes the capability information of the UE stored in the network.
- 23 illustrates a method of transmitting and receiving capabilities initiated by a network.
- the UE After establishing the RRC connection with the eNB, the UE transmits an access request message to the MME (S2310).
- the MME requests the context information of the UE to the HSS using the identifier of the UE that transmitted the access request message (S2320).
- the HSS requested from the MME transmits context information of the UE to the MME (S2330), and the context information of the UE includes subscriber information of the UE, and includes capability information indicating that the UE may operate as an RSU or a relay node. Can be.
- the MME identifies the capability information of the UE according to the information received from the HSS, and the MME notifies the operator management server that the UE capable of acting as an RSU or relay node has connected to the network and requests registration (S2340). If the registration of the UE is confirmed from the management server of the operator (S2350), the MME transmits an access approval message indicating that the access procedure has been successfully completed (S2360).
- step S2320 when the operator management server holds the identifier and capability information for UEs installed in advance, the MME may request information on the capability of the UE directly from the operator management server, not the HSS. In this case, the procedure of S2340 to S2350 can be omitted.
- FIG. 24 is a diagram illustrating a configuration of a node device according to an exemplary embodiment.
- the terminal device 100 may include a transceiver 110, a processor 120, and a memory 130.
- the transceiver 110 may be configured to transmit various signals, data and information to an external device, and to receive various signals, data and information to an external device. Alternatively, the transceiver 110 may be implemented by being separated into a transmitter and a receiver.
- the terminal device 100 may be connected to an external device by wire and / or wirelessly.
- the processor 120 may control the overall operation of the terminal device 100, and may be configured to perform a function of the terminal device 100 to process and process information to be transmitted and received with an external device.
- the processor 120 may be configured to perform a terminal operation proposed in the present invention.
- the memory 130 may store the processed information for a predetermined time and may be replaced with a component such as a buffer (not shown).
- the network node device 200 may include a transceiver 210, a processor 220, and a memory 230.
- the transceiver 210 may be configured to transmit various signals, data and information to an external device, and to receive various signals, data and information to an external device.
- the network node device 200 may be connected to an external device by wire and / or wirelessly.
- the transceiver 210 may be implemented by being separated into a transmitter and a receiver.
- the processor 220 may control the overall operation of the network node device 200, and may be configured to perform a function of calculating and processing information to be transmitted / received with an external device.
- the processor 220 may be configured to perform the network node operation proposed in the present invention.
- the memory 230 may store the processed information for a predetermined time and may be replaced with a component such as a buffer (not shown).
- the specific configuration of the terminal device 100 and the network device 200 as described above may be implemented so that the above-described matters described in various embodiments of the present invention can be applied independently or two or more embodiments are applied at the same time, overlapping The description is omitted for clarity.
- Embodiments of the present invention described above may be implemented through various means.
- embodiments of the present invention may be implemented by hardware, firmware, software, or a combination thereof.
- a method according to embodiments of the present invention may include one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), and Programmable Logic Devices (PLDs). It may be implemented by field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, and 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 controllers, microcontrollers, microprocessors, and the like.
- the method according to the embodiments of the present invention may be implemented in the form of an apparatus, procedure, or function for performing the functions or operations described above.
- the software code may be stored in a memory unit and driven by a processor.
- the memory unit may be located inside or outside the processor, and may exchange data with the processor by various known means.
- the V2X communication method as described above can be applied to various wireless communication systems including not only 3GPP systems but also IEEE 802.16x and 802.11x systems. Furthermore, the proposed method can be applied to mmWave communication system using ultra high frequency band.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
레퍼런스 포인트 | 설명 |
S1-MME | E-UTRAN와 MME 간의 제어 플레인 프로토콜에 대한 레퍼런스 포인트(Reference point for the control plane protocol between E-UTRAN and MME) |
S1-U | 핸드오버 동안 eNB 간 경로 스위칭 및 베어러 당 사용자 플레인 터널링에 대한 E-UTRAN와 SGW 간의 레퍼런스 포인트(Reference point between E-UTRAN and Serving GW for the per bearer user plane tunnelling and inter eNodeB path switching during handover) |
S3 | 유휴(idle) 및/또는 활성화 상태에서 3GPP 액세스 네트워크 간 이동성에 대한 사용자 및 베어러 정보 교환을 제공하는 MME와 SGSN 간의 레퍼런스 포인트. 이 레퍼런스 포인트는 PLMN-내 또는 PLMN-간(예를 들어, PLMN-간 핸드오버의 경우)에 사용될 수 있음) (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 | (GPRS 코어와 SGW의 3GPP 앵커 기능 간의 관련 제어 및 이동성 지원을 제공하는 SGW와 SGSN 간의 레퍼런스 포인트. 또한, 직접 터널이 수립되지 않으면, 사용자 플레인 터널링을 제공함(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 tunnelling.) |
S5 | SGW와 PDN GW 간의 사용자 플레인 터널링 및 터널 관리를 제공하는 레퍼런스 포인트. 단말 이동성으로 인해, 그리고 요구되는 PDN 연결성을 위해서 SGW가 함께 위치하지 않은 PDN GW로의 연결이 필요한 경우, SGW 재배치를 위해서 사용됨(It provides user plane tunnelling 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 | MME와 SGW 간의 레퍼런스 포인트 |
SGi | PDN GW와 PDN 간의 레퍼런스 포인트. PDN은, 오퍼레이터 외부 공용 또는 사설 PDN이거나 예를 들어, IMS 서비스의 제공을 위한 오퍼레이터-내 PDN일 수 있음. 이 레퍼런스 포인트는 3GPP 액세스의 Gi에 해당함(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.) |
Claims (15)
- V2X(Vehicle to Everything) 통신 환경에서 UE(User Equipment)가 네트워크 노드들과 통신하는 방법에 있어서,V2X 서비스를 제공하기 위한 RSU(Road Side Unit) 및 통신 서비스를 중계하기 위한 중계 노드로 동작할 수 있음을 나타내는 캐퍼빌리티(capability) 정보를 포함하는 제1 메시지를 네트워크 엔티티에 전송하는 단계;상기 RSU 또는 상기 중계 노드로 동작할 것을 지시하는 제2 메시지를 기지국으로부터 수신하는 단계; 및상기 제2 메시지에 따라 상기 RSU 또는 상기 중계 노드로 동작함으로써, 상기 기지국 및 다른 UE와 통신을 수행하는 단계를 포함하는, 통신 방법.
- 제1항에 있어서,상기 제2 메시지는 상기 RSU 또는 상기 중계 노드로 동작하는 과정에서 사용할 인터페이스에 대한 정보를 더 포함하는 것인, 통신 방법.
- 제2항에 있어서,상기 인터페이스에 대한 정보는 상기 기지국과의 통신에 사용할 인터페이스에 대한 정보 및 상기 다른 UE와의 통신에 사용할 인터페이스에 대한 정보를 각각 포함하며,상기 인터페이스는 Uu 인터페이스, Un 인터페이스, PC5 인터페이스, DSRC(Dedicated Shiort Range Communications) 관련 인터페이스 중 어느 하나인 것인, 통신 방법.
- 제1항에 있어서,상기 통신 방법은 상기 V2X 서비스를 관리하는 엔티티로부터 상기 RSU 또는 상기 중계 노드로 동작할 수 있음을 나타내는 식별자를 설정받는 단계; 및상기 식별자를 이용하여 상기 기지국에 접속하는 단계를 더 포함하는 것인, 통신 방법.
- 제4항에 있어서,상기 식별자를 이용하여 상기 기지국에 접속하는 경우, 상기 식별자를 이용하지 않은 UE 보다 우선적으로 접속이 허용되는 것인, 통신 방법.
- 제1항에 있어서,상기 네트워크 엔티티에 의해 상기 RSU 또는 상기 중계 노드로 동작할 수 있다고 인지된 상기 UE는 상기 기지국으로부터 무선 자원을 우선적으로 할당받는 것인, 통신 방법.
- 제1항에 있어서,상기 제2 메시지를 수신하는 단계 및 상기 통신을 수행하는 단계는, 상기 UE가 외부 전원을 이용하여 충전 중인 경우에 임시로 설치되는 어플리케이션을 통해 수행되는 것인, 통신 방법.
- 제1항에 있어서,상기 네트워크 엔티티는 상기 기지국 또는 MME(Mobility Management Entity)인 것인, 통신 방법.
- V2X(Vehicle to Everything) 통신 환경에서 네트워크 노드들과 통신하는 UE에 있어서,송신부;수신부; 및상기 송신부 및 상기 수신부와 연결되어 동작하는 프로세서를 포함하되,상기 프로세서는,V2X 서비스를 제공하기 위한 RSU(Road Side Unit) 및 통신 서비스를 중계하기 위한 중계 노드로 동작할 수 있음을 나타내는 캐퍼빌리티(capability) 정보를 포함하는 제1 메시지를 네트워크 엔티티에 전송하도록 상기 송신부를 제어하고,상기 RSU 또는 상기 중계 노드로 동작할 것을 지시하는 제2 메시지를 기지국으로부터 수신하도록 상기 수신부를 제어하고,상기 제2 메시지에 따라 상기 RSU 또는 상기 중계 노드로 동작함으로써, 상기 기지국 및 다른 UE와 통신을 수행하는 것인, UE.
- V2X(Vehicle to Everything) 통신 환경에서 UE(User Equipment)가 네트워크 노드들과 통신하는 방법에 있어서,V2X 서비스를 제공하기 위한 RSU(Road Side Unit) 및 통신 서비스를 중계하기 위한 중계 노드로 동작할 수 있음을 나타내는 캐퍼빌리티(capability) 정보를 포함하는 메시지를 네트워크 엔티티에 전송하는 단계;상기 RSU 또는 상기 중계 노드로의 동작을 개시하기 위한 트리거링 조건을 설정하는 단계; 및상기 트리거링 조건이 만족함에 따라, 상기 RSU 또는 상기 중계 노드로 동작함으로써 기지국 및 다른 UE와 통신을 수행하는 단계를 포함하는, 통신 방법.
- 제10항에 있어서,상기 트리거링 조건에 대하여 상기 RSU 또는 상기 중계 노드로 동작하는 과정에서 사용할 인터페이스도 함께 설정되는 것인, 통신 방법.
- 제10항에 있어서,상기 트리거링 조건은 상기 UE가 관리하는 영역 내에 위치하는 차량의 수가 제1 임계값 이상인 경우 상기 RSU로 동작하고, 상기 차량의 수가 제2 임계값 미만인 경우 상기 중계 노드로 동작하도록 설정되는 것인, 통신 방법.
- V2X(Vehicle to Everything) 통신 환경에서 네트워크 노드들과 통신하는 UE에 있어서,송신부;수신부; 및상기 송신부 및 상기 수신부와 연결되어 동작하는 프로세서를 포함하되,상기 프로세서는,V2X 서비스를 제공하기 위한 RSU(Road Side Unit) 및 통신 서비스를 중계하기 위한 중계 노드로 동작할 수 있음을 나타내는 캐퍼빌리티(capability) 정보를 포함하는 메시지를 네트워크 엔티티에 전송하도록 상기 송신부를 제어하고,상기 RSU 또는 상기 중계 노드로의 동작을 개시하기 위한 트리거링 조건을 설정하고,상기 트리거링 조건이 만족함에 따라, 상기 RSU 또는 상기 중계 노드로 동작함으로써 기지국 및 다른 UE와 통신을 수행하는 것인, UE.
- V2X(Vehicle to Everything) 통신 환경에서 UE(User Equipment)가 네트워크 노드들과 통신하는 방법에 있어서,V2X 서비스를 제공하기 위한 RSU(Road Side Unit) 및 통신 서비스를 중계하기 위한 중계 노드로 동작할 수 있음을 나타내는 캐퍼빌리티(capability) 정보를 포함하는 제1 메시지를 네트워크 엔티티에 전송하는 단계;상기 RSU 또는 상기 중계 노드로 동작할 것을 지시하는 제2 메시지를 기지국으로부터 수신하는 단계; 및상기 제2 메시지에 따라 상기 RSU 또는 상기 중계 노드로 동작함으로써, 상기 기지국 및 다른 UE와 통신을 수행하는 단계를 포함하고,상기 기지국과 통신하는 단계는, 상기 V2X 서비스를 관리하는 엔티티로부터 상기 RSU 또는 상기 중계 노드로 동작할 수 있음을 나타내는 식별자가 설정되면, 상기 식별자를 이용하여 상기 기지국에 접속하는 단계를 포함하고,상기 식별자를 이용하여 상기 기지국에 접속하는 경우, 상기 식별자를 이용하지 않은 UE 보다 우선적으로 접속이 허용되는 것인, 통신 방법.
- V2X(Vehicle to Everything) 통신 환경에서 네트워크 노드들과 통신하는 UE에 있어서,송신부;수신부; 및상기 송신부 및 상기 수신부와 연결되어 동작하는 프로세서를 포함하되,상기 프로세서는,V2X 서비스를 제공하기 위한 RSU(Road Side Unit) 및 통신 서비스를 중계하기 위한 중계 노드로 동작할 수 있음을 나타내는 캐퍼빌리티(capability) 정보를 포함하는 제1 메시지를 네트워크 엔티티에 전송하도록 상기 송신부를 제어하고,상기 RSU 또는 상기 중계 노드로 동작할 것을 지시하는 제2 메시지를 기지국으로부터 수신하도록 상기 수신부를 제어하고,상기 제2 메시지에 따라 상기 RSU 또는 상기 중계 노드로 동작함으로써, 상기 기지국 및 다른 UE와 통신을 수행하고,상기 V2X 서비스를 관리하는 엔티티로부터 상기 RSU 또는 상기 중계 노드로 동작할 수 있음을 나타내는 식별자가 설정되면, 상기 식별자를 이용하여 상기 기지국에 접속하며,상기 식별자를 이용하여 상기 기지국에 접속하는 경우, 상기 식별자를 이용하지 않은 UE 보다 우선적으로 접속이 허용되는 것인, UE.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2017566634A JP6449491B2 (ja) | 2015-07-07 | 2016-02-11 | V2x通信システムにおける端末の通信方法及び端末 |
US15/737,646 US10506394B2 (en) | 2015-07-07 | 2016-02-11 | Communication method of terminal in V2X communication system, and terminal |
Applications Claiming Priority (8)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201562189217P | 2015-07-07 | 2015-07-07 | |
US62/189,217 | 2015-07-07 | ||
US201562190259P | 2015-07-09 | 2015-07-09 | |
US62/190,259 | 2015-07-09 | ||
US201562192080P | 2015-07-14 | 2015-07-14 | |
US62/192,080 | 2015-07-14 | ||
US201562193038P | 2015-07-15 | 2015-07-15 | |
US62/193,038 | 2015-07-15 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2017007104A1 true WO2017007104A1 (ko) | 2017-01-12 |
Family
ID=57684864
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2016/001381 WO2017007104A1 (ko) | 2015-07-07 | 2016-02-11 | V2x 통신 시스템에서 단말의 통신 방법 및 단말 |
Country Status (3)
Country | Link |
---|---|
US (1) | US10506394B2 (ko) |
JP (1) | JP6449491B2 (ko) |
WO (1) | WO2017007104A1 (ko) |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108683986A (zh) * | 2018-05-07 | 2018-10-19 | 南京邮电大学 | 车队通信方法、计算机可读存储介质和终端 |
CN109035760A (zh) * | 2018-06-22 | 2018-12-18 | 东华大学 | 车载自组织网中不同rsu场景下的路网信息收集方法 |
WO2019035753A1 (en) * | 2017-08-14 | 2019-02-21 | Telefonaktiebolaget Lm Ericsson (Publ) | DUAL MODE VEHICLE VEHICLE COMMUNICATIONS |
WO2019177783A1 (en) * | 2018-03-16 | 2019-09-19 | At&T Intellectual Property I, L.P. | Wireless radio user equipment as local manager for integrating access backhaul and sidelink |
US10764918B2 (en) | 2018-06-11 | 2020-09-01 | At&T Intellectual Property I, L.P. | Wireless communication framework for multiple user equipment |
US10892858B2 (en) | 2018-09-28 | 2021-01-12 | At&T Intellectual Property I, L.P. | Chain broadcasting in vehicle-to-everything (V2X) communications |
US10951362B2 (en) | 2018-08-10 | 2021-03-16 | At&T Intellectual Property I, L.P. | Hybrid automatic repeat request and scheduling for wireless cellular systems with local traffic managers |
US10972958B1 (en) | 2020-03-05 | 2021-04-06 | At&T Intellectual Property I, L.P. | Location-based route management for vehicle-to-everything relay communications |
US11039422B2 (en) | 2019-01-11 | 2021-06-15 | At&T Intellectual Property I, L.P. | Load manager performance management for 5G or other next generation network |
US11234251B2 (en) | 2018-08-17 | 2022-01-25 | At&T Intellectual Property I, L.P. | Generic control channel configuration for new radio sidelink |
TWI786198B (zh) * | 2017-10-06 | 2022-12-11 | 美商高通公司 | 車聯網(v2x)無線電存取技術(rat)特徵協商及控制 |
Families Citing this family (31)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2017030348A1 (ko) * | 2015-08-14 | 2017-02-23 | 엘지전자 주식회사 | 무선 통신 시스템에서 v2x 메시지 송수신 방법 및 이를 위한 장치 |
US10595157B2 (en) * | 2015-09-18 | 2020-03-17 | Nec Corporation | RSU apparatus, base station apparatus, control node, and methods therein |
KR20170034023A (ko) * | 2015-09-18 | 2017-03-28 | 삼성전자주식회사 | V2x 통신을 위한 자원할당 방법 및 장치 |
CN106559877B (zh) * | 2015-09-24 | 2019-02-26 | 中兴通讯股份有限公司 | 车联网业务的发送方法及装置、资源配置方法及装置 |
EP3354058B1 (en) * | 2015-09-24 | 2022-02-16 | Nokia Technologies Oy | Method of ue autonomous measurement related actions upon implicit triggers |
CN106658352B (zh) * | 2015-11-02 | 2019-03-22 | 中兴通讯股份有限公司 | 车联网v2x业务的转发方法及装置 |
WO2017147904A1 (zh) * | 2016-03-04 | 2017-09-08 | 华为技术有限公司 | 消息发送方法和装置 |
JP6586515B2 (ja) * | 2016-04-26 | 2019-10-02 | 京セラ株式会社 | リレーノード及び無線端末 |
US20170330457A1 (en) * | 2016-05-10 | 2017-11-16 | Zte Corporation | Techniques for vehicle based message transmission and reception |
WO2017222437A1 (en) * | 2016-06-23 | 2017-12-28 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods identifying vehicles and related systems, controllers, and vehicles |
WO2018059506A1 (en) * | 2016-09-30 | 2018-04-05 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods and apparatuses for network selection |
KR102304709B1 (ko) | 2017-03-03 | 2021-09-23 | 현대자동차주식회사 | V2x 통신 메시지에 대하여 적응적 보안 레벨을 적용하는 방법 및 장치 |
JP6988124B2 (ja) * | 2017-03-27 | 2022-01-05 | カシオ計算機株式会社 | 通信装置、電子時計、通信方法、及びプログラム |
EP3646650B1 (en) * | 2017-06-29 | 2021-08-18 | Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V. | Apparatus, base station and methods allowing reliable wireless communication |
KR102367053B1 (ko) * | 2017-07-13 | 2022-02-24 | 삼성전자주식회사 | 외부 전자 장치와 통신을 수행하기 위한 전자 장치 |
EP3484189B1 (en) * | 2017-11-13 | 2023-01-11 | Robert Bosch GmbH | Road-side network node and method to operate the road-side network node |
US11088750B2 (en) * | 2018-02-16 | 2021-08-10 | Qualcomm Incorporated | Feedback of beam switch time capability |
US11330410B2 (en) | 2018-04-03 | 2022-05-10 | Corning Research & Development Corporation | Pathside communication relay (PCR) for collecting and distributing pathside data among client devices |
WO2020011346A1 (en) * | 2018-07-11 | 2020-01-16 | Huawei Technologies Co., Ltd. | Device for transmitting and/or receiving a message in a combined assisted and ad-hoc mode |
EP3813472B1 (en) * | 2018-07-19 | 2022-11-30 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Information transmission method and device, and computer storage medium |
US11017670B2 (en) * | 2018-08-03 | 2021-05-25 | Toyota Motor Engineering & Manufacturing North America, Inc. | Intermediate vehicle repeater for out of range vehicles |
US11284376B2 (en) | 2018-08-17 | 2022-03-22 | At&T Intellectual Property I, L.P. | Distributed control information for multiple party communications for 5G or other next generation network |
KR102494617B1 (ko) * | 2018-10-08 | 2023-02-06 | 텔레호낙티에볼라게트 엘엠 에릭슨(피유비엘) | 지능형 교통 시스템(its) 메시지 분배를 위한 방법, 장치 및 컴퓨터 판독 가능 매체 |
JP7109579B2 (ja) | 2018-11-13 | 2022-07-29 | 三菱電機株式会社 | V2x車載器およびv2x中継器 |
US10716167B2 (en) * | 2018-11-29 | 2020-07-14 | Toyota Motor North America, Inc. | Cellular network coverage using a vehicle-based data transmission extender |
US11190927B2 (en) * | 2019-07-08 | 2021-11-30 | Research & Business Foundation Sungkyunkwan University | Vehicular neighbor discovery for IP-based vehicular networks |
US11440560B2 (en) * | 2019-07-10 | 2022-09-13 | Valerann Ltd. | System and method for automatic configuration of a road sensor unit |
CN113395298B (zh) * | 2020-03-11 | 2023-07-04 | 沃尔沃汽车公司 | 用于车载通讯的信息集和信息传递方法 |
KR20230002811A (ko) * | 2020-04-28 | 2023-01-05 | 엘지전자 주식회사 | 사이드링크를 지원하는 무선통신시스템에서 제1 장치가 제1 메시지를 전송하는 방법 및 이를 위한 장치 |
US11997642B2 (en) * | 2020-11-23 | 2024-05-28 | Asustek Computer Inc. | Method and apparatus for acquiring system information and paging via UE-to-network relay in a wireless communication system |
US11752889B2 (en) | 2021-01-20 | 2023-09-12 | Toyota Motor North America, Inc. | Fractional energy retrieval |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR101096375B1 (ko) * | 2009-07-27 | 2011-12-20 | 주식회사 팬택 | 다중 홉 릴레이 시스템에서 링크 식별자 할당 방법 및 할당 장치 |
KR20140057723A (ko) * | 2012-11-02 | 2014-05-14 | 에스케이플래닛 주식회사 | 네트워크 접속 제어 시스템 및 방법 |
WO2014073748A1 (ko) * | 2012-11-09 | 2014-05-15 | 에릭슨 엘지 주식회사 | 이동체에서의 릴레이 시스템 |
WO2015026111A1 (ko) * | 2013-08-18 | 2015-02-26 | 엘지전자 주식회사 | 무선 통신 시스템에서 중계기 동작 방법 및 장치 |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9942879B2 (en) * | 2014-05-19 | 2018-04-10 | Samsung Electronics Co., Ltd. | Method and apparatus for avoiding resource collision in mobile communication system |
US20160105539A1 (en) * | 2014-10-14 | 2016-04-14 | The Regents Of The University Of Michigan | Vehicle interface docking system for dsrc-equipped user devices in a vehicle |
WO2016141983A1 (en) * | 2015-03-11 | 2016-09-15 | Nokia Solutions And Networks Oy | Method and apparatus for resource allocation in v2v communications system |
US10554708B2 (en) * | 2015-03-27 | 2020-02-04 | Qualcomm Incorporated | Point-to-multipoint broadcast assisted vehicle-to-X broadcast |
KR102415672B1 (ko) * | 2015-04-09 | 2022-07-04 | 삼성전자주식회사 | 디바이스 간 메시지 송수신 방법 및 장치 |
US10743235B2 (en) * | 2015-06-11 | 2020-08-11 | Nokia Technologies Oy | Support for minimization of service interruption with device-to-device based user-equipment-to-network relay |
EP3314959B1 (en) * | 2015-06-25 | 2020-05-13 | INTEL Corporation | Registration for wireless vehicular communications |
KR20180017893A (ko) * | 2016-08-11 | 2018-02-21 | 남정길 | V2x를 위한 준영구적 스케줄링 방법 및 장치 |
-
2016
- 2016-02-11 WO PCT/KR2016/001381 patent/WO2017007104A1/ko active Application Filing
- 2016-02-11 US US15/737,646 patent/US10506394B2/en active Active
- 2016-02-11 JP JP2017566634A patent/JP6449491B2/ja active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR101096375B1 (ko) * | 2009-07-27 | 2011-12-20 | 주식회사 팬택 | 다중 홉 릴레이 시스템에서 링크 식별자 할당 방법 및 할당 장치 |
KR20140057723A (ko) * | 2012-11-02 | 2014-05-14 | 에스케이플래닛 주식회사 | 네트워크 접속 제어 시스템 및 방법 |
WO2014073748A1 (ko) * | 2012-11-09 | 2014-05-15 | 에릭슨 엘지 주식회사 | 이동체에서의 릴레이 시스템 |
WO2015026111A1 (ko) * | 2013-08-18 | 2015-02-26 | 엘지전자 주식회사 | 무선 통신 시스템에서 중계기 동작 방법 및 장치 |
Non-Patent Citations (1)
Title |
---|
QUALCOMM INCORPORATED: "V2X Communication in 3GPP", 3GPP TSG-SA WG1 MEETING #68, S1-144374, 5 November 2014 (2014-11-05), pages 1 - 144374, XP050880094, Retrieved from the Internet <URL:http:/www.3gpp.org/ftp/tsg_sa/wgl_serv/TSGS1_68_SanFrancisco/docs/ S 1-144374 .zip> * |
Cited By (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2019035753A1 (en) * | 2017-08-14 | 2019-02-21 | Telefonaktiebolaget Lm Ericsson (Publ) | DUAL MODE VEHICLE VEHICLE COMMUNICATIONS |
EP3669505A1 (en) * | 2017-08-14 | 2020-06-24 | Telefonaktiebolaget LM Ericsson (Publ) | Dual mode vehicle to vehicle communications |
US11706831B2 (en) | 2017-08-14 | 2023-07-18 | Telefonaktiebolaget Lm Ericsson (Publ) | Dual mode vehicle to vehicle communications |
TWI786198B (zh) * | 2017-10-06 | 2022-12-11 | 美商高通公司 | 車聯網(v2x)無線電存取技術(rat)特徵協商及控制 |
WO2019177783A1 (en) * | 2018-03-16 | 2019-09-19 | At&T Intellectual Property I, L.P. | Wireless radio user equipment as local manager for integrating access backhaul and sidelink |
CN108683986B (zh) * | 2018-05-07 | 2021-03-02 | 南京邮电大学 | 车队通信方法、计算机可读存储介质和终端 |
CN108683986A (zh) * | 2018-05-07 | 2018-10-19 | 南京邮电大学 | 车队通信方法、计算机可读存储介质和终端 |
US10764918B2 (en) | 2018-06-11 | 2020-09-01 | At&T Intellectual Property I, L.P. | Wireless communication framework for multiple user equipment |
US11497048B2 (en) | 2018-06-11 | 2022-11-08 | At&T Intellectual Property I, L.P. | Wireless communication framework for multiple user equipment |
CN109035760B (zh) * | 2018-06-22 | 2021-11-02 | 东华大学 | 车载自组织网中不同rsu场景下的路网信息收集方法 |
CN109035760A (zh) * | 2018-06-22 | 2018-12-18 | 东华大学 | 车载自组织网中不同rsu场景下的路网信息收集方法 |
US11451342B2 (en) | 2018-08-10 | 2022-09-20 | At&T Intellectual Property I, L.P. | Hybrid automatic repeat request and scheduling for wireless cellular systems with local traffic managers |
US10951362B2 (en) | 2018-08-10 | 2021-03-16 | At&T Intellectual Property I, L.P. | Hybrid automatic repeat request and scheduling for wireless cellular systems with local traffic managers |
US11234251B2 (en) | 2018-08-17 | 2022-01-25 | At&T Intellectual Property I, L.P. | Generic control channel configuration for new radio sidelink |
US11343025B2 (en) | 2018-09-28 | 2022-05-24 | At&T Intellectual Property I, L.P. | Chain broadcasting in vehicle-to-everything (V2X) communications |
US10892858B2 (en) | 2018-09-28 | 2021-01-12 | At&T Intellectual Property I, L.P. | Chain broadcasting in vehicle-to-everything (V2X) communications |
US11039422B2 (en) | 2019-01-11 | 2021-06-15 | At&T Intellectual Property I, L.P. | Load manager performance management for 5G or other next generation network |
US11350337B2 (en) | 2020-03-05 | 2022-05-31 | At&T Intellectual Property I, L.P. | Location-based route management for vehicle-to-everything relay communications |
US10972958B1 (en) | 2020-03-05 | 2021-04-06 | At&T Intellectual Property I, L.P. | Location-based route management for vehicle-to-everything relay communications |
US11576103B2 (en) | 2020-03-05 | 2023-02-07 | At&T Intellectual Property I, L.P. | Location-based route management for vehicle-to-everything relay communications |
Also Published As
Publication number | Publication date |
---|---|
US10506394B2 (en) | 2019-12-10 |
JP2018518913A (ja) | 2018-07-12 |
JP6449491B2 (ja) | 2019-01-09 |
US20180184270A1 (en) | 2018-06-28 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2017007104A1 (ko) | V2x 통신 시스템에서 단말의 통신 방법 및 단말 | |
WO2016200184A1 (ko) | V2x 통신 시스템에서 단말의 통신 방법 및 단말 | |
WO2016144147A1 (ko) | V2x 통신 시스템에서 차량에 설치된 단말의 통신 방법 및 단말 | |
WO2017003230A1 (ko) | V2x 통신 시스템에서 단말의 v2x 통신 방법 및 단말 | |
WO2017164641A2 (ko) | 데이터 유닛을 전송하는 방법 및 사용자기기와, 데이터 유닛을 수신하는 방법 및 사용자기기 | |
WO2016148399A1 (ko) | V2x 통신 시스템에서 단말의 통신 방법 및 단말 | |
WO2017052335A1 (ko) | 무선 통신 시스템에서 단말 간의 직접 통신을 수행하는 방법 및 이를 위한 장치 | |
WO2018155934A1 (ko) | 무선 통신 시스템에서 3GPP access를 통해 non-3GPP에 관련된 데이터를 수신하는 방법 및 이를 위한 장치 | |
WO2016190672A1 (ko) | 무선 통신 시스템에서 후원 연결을 위한 접속 절차를 수행하는 방법 및 단말 | |
WO2016105004A1 (ko) | 무선 통신 시스템에서 nbifom 캐퍼빌리티를 송수신하는 방법 및 이를 위한 장치 | |
WO2018169343A1 (ko) | 페이징을 수행하는 방법 및 기지국, 페이징을 지원하는 방법 및 네트워크 엔티티 | |
WO2017069430A1 (ko) | 무선 통신 시스템에서 단말 간의 직접 통신 방법 및 이를 위한 장치 | |
WO2017146523A1 (ko) | 네트워크로의 연결 요청 방법 및 사용자기기 | |
WO2018128519A1 (ko) | 무선 통신 시스템에서 리모트 ue와 연결을 가진 릴레이 ue가 네트워크와 연결 수행 방법 및 이를 위한 장치 | |
WO2018199611A1 (ko) | 네트워크로의 등록 요청 전송 방법 및 사용자기기, 그리고 등록 요청 수신 방법 및 네트워크 기기 | |
WO2017142362A1 (ko) | 무선 통신 시스템에서 위치 등록 관련 메시지 송수신 방법 및 이를 위한 장치 | |
WO2018230928A1 (ko) | 무선 통신 시스템에서 사용자 기기의 위치 정보를 리포팅하는 방법 및 장치 | |
WO2017135779A1 (ko) | 무선 통신 시스템에서 rrc 연결 재개를 수행하는 방법 및 장치 | |
WO2017030348A1 (ko) | 무선 통신 시스템에서 v2x 메시지 송수신 방법 및 이를 위한 장치 | |
WO2018066919A1 (ko) | 네트워크로의 연결 방법 및 사용자기기 | |
WO2017074012A1 (ko) | 무선 통신 시스템에서 단말 간의 직접 통신을 방법 및 이를 위한 장치 | |
WO2017191973A1 (ko) | 무선 통신 시스템에서 리모트 ue의 위치 등록 수행 방법 및 이를 위한 장치 | |
WO2017126948A1 (ko) | 무선 통신 시스템에서 로컬 네트워크에서 v2x 메시지 송수신 방법 및 이를 위한 장치 | |
WO2017119778A1 (ko) | 사용자기기 및 데이터 전송 방법과, 네트워크 노드 및 데이터 전송 방법 | |
WO2016024773A1 (ko) | 무선 통신 시스템에서 릴레이 선택 방법 및 이를 위한 장치 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 16821510 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 15737646 Country of ref document: US |
|
ENP | Entry into the national phase |
Ref document number: 2017566634 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 16821510 Country of ref document: EP Kind code of ref document: A1 |