WO2017074012A1 - 무선 통신 시스템에서 단말 간의 직접 통신을 방법 및 이를 위한 장치 - Google Patents
무선 통신 시스템에서 단말 간의 직접 통신을 방법 및 이를 위한 장치 Download PDFInfo
- Publication number
- WO2017074012A1 WO2017074012A1 PCT/KR2016/012071 KR2016012071W WO2017074012A1 WO 2017074012 A1 WO2017074012 A1 WO 2017074012A1 KR 2016012071 W KR2016012071 W KR 2016012071W WO 2017074012 A1 WO2017074012 A1 WO 2017074012A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- remote
- direct communication
- message
- maximum
- timer
- Prior art date
Links
- 230000006854 communication Effects 0.000 title claims abstract description 262
- 238000004891 communication Methods 0.000 title claims abstract description 261
- 238000000034 method Methods 0.000 title claims abstract description 183
- 230000005540 biological transmission Effects 0.000 claims abstract description 65
- 230000011664 signaling Effects 0.000 claims abstract description 56
- 230000008569 process Effects 0.000 claims abstract description 52
- 230000009849 deactivation Effects 0.000 claims description 34
- 230000000977 initiatory effect Effects 0.000 description 50
- 239000010410 layer Substances 0.000 description 47
- 230000006870 function Effects 0.000 description 30
- 230000004044 response Effects 0.000 description 30
- 238000007726 management method Methods 0.000 description 25
- 238000010586 diagram Methods 0.000 description 13
- 238000010295 mobile communication Methods 0.000 description 10
- 230000007704 transition Effects 0.000 description 5
- 238000007600 charging Methods 0.000 description 4
- 230000000694 effects Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 230000005641 tunneling Effects 0.000 description 4
- 239000002699 waste material Substances 0.000 description 4
- 238000012545 processing Methods 0.000 description 3
- 238000013459 approach Methods 0.000 description 2
- 238000012790 confirmation Methods 0.000 description 2
- 238000001914 filtration Methods 0.000 description 2
- 230000008054 signal transmission Effects 0.000 description 2
- 108020001568 subdomains Proteins 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 235000005224 Eucalyptus bridgesiana Nutrition 0.000 description 1
- 244000239638 Eucalyptus bridgesiana Species 0.000 description 1
- 230000002159 abnormal effect Effects 0.000 description 1
- 206010000210 abortion Diseases 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000003139 buffering effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 238000013480 data collection Methods 0.000 description 1
- 239000002346 layers by function Substances 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 230000001151 other effect Effects 0.000 description 1
- 229920001690 polydopamine Polymers 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 238000012216 screening Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/30—Connection release
- H04W76/38—Connection release triggered by timers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
- H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/16—Discovering, processing access restriction or access information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/14—Direct-mode setup
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/27—Transitions between radio resource control [RRC] states
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/30—Connection release
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/18—Management of setup rejection or failure
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Definitions
- the following description relates to a wireless communication system, and more particularly, to a direct communication method and apparatus between terminals for improving communication efficiency in a direct communication between terminals (eg, ProSe communication) environment.
- a direct communication between terminals eg, ProSe communication
- 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 is to reduce the radio resources and unnecessary power waste of the terminal in the ProSe communication process.
- a method for performing direct communication includes receiving a direct communication request message including information on a maximum inactivity period from a remote UE in a process of establishing a direct connection with a remote UE; Starting a timer corresponding to the maximum deactivation interval when data transmission or signaling through a direct connection with the remote UE is completed, and if no message is received from the remote UE until the timer expires, Locally releasing the direct connection.
- the relay UE may stop the timer and set it to an initial value.
- the maximum deactivation interval may be determined in consideration of the transmission period, the retransmission time interval, and the maximum number of retransmission allowances of the direct communication keepalive message transmitted by the remote UE.
- the maximum inactivity interval is determined by the following equation, where [Inactivity timerkeep] ⁇ 'transmission period of keepalive message' + 'retransmission time interval' * 'maximum number of allowed retransmissions' 'Transmission period of keepalive message' indicates the transmission period of the direct communication keepalive message, 'retransmission time interval' indicates the retransmission time interval of the direct communication keepalive message, and 'maximumm number of allowed retransmissions' May indicate the maximum number of retransmission allowances of the direct communication keepalive message.
- the timer When receiving the direct communication keepalive message including the information on the new maximum deactivation interval from the remote UE after receiving the direct communication request message, the timer may be set according to the information on the new maximum deactivation interval.
- the maximum deactivation interval is related to a transmission pattern of the direct communication keepalive message transmitted by the remote UE, and the transmission pattern of the direct communication keepalive message includes at least one of mobility, reporting type, and message transmission pattern of the remote UE. It may be determined in consideration of one.
- the relay 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 includes: a maximum inactivity interval from the remote UE in a process of establishing a direct connection with the remote UE; Receiving a direct communication request message including information on a period, and when signaling through a direct connection with the remote UE is completed, start a timer corresponding to the maximum inactivity period, and until the timer expires If no message is received from the UE, it locally releases the direct connection with the remote UE.
- the communication efficiency is improved by specifically proposing parts not defined in the procedure and signaling of the conventional direct communication between terminals.
- the conventional communication scheme can be improved by proposing various embodiments of the overall procedures of the direct communication between terminals.
- 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
- FIG. 7 shows a basic path for two UEs to communicate in EPS.
- FIG. 9 illustrates a communication path through an eNodeB between two UEs based on a process.
- 11 is a diagram illustrating communication through a ProSe UE-to-Network Relay.
- 12 is a diagram illustrating media traffic of group communication.
- FIG. 13 shows a procedure of a remote UE performing direct communication through a UE-to-network relay.
- 14 to 16 are diagrams illustrating direct communication signaling procedures between terminals associated with the proposed embodiment.
- 17 to 20 are diagrams illustrating a direct communication method between terminals according to a proposed embodiment.
- 21 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. .
- PCRF Policy and Charging Rule Function
- -OMA DM Open Mobile Alliance Device Management: A protocol designed for the management of mobile devices such as mobile phones, PDAs, portable computers, etc., including device configuration, firmware upgrade, error report, etc. Performs the function of.
- OAM Operaation Administration and Maintenance
- a group of network management functions that provides network fault indication, performance information, and data and diagnostics.
- Non-Access Stratum Upper stratum of the control plane between the UE and the MME.
- NAS Non-Access Stratum
- AS Access-Stratum: Includes protocol stack between UE and radio (or access) network, and is in charge of data and network control signal transmission.
- MO Management object
- 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).
- APN Access Point Name: A string indicating or identifying a PDN. In order to access the requested service or network, it goes through a specific P-GW, which means a predefined name (string) in the network to find this P-GW. (For example, internet.mnc012.mcc345.gprs)
- 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
- 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.
- 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 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 ProSe communication path between two or more ProSe capable terminals. Unless specifically stated otherwise, ProSe communication means one of ProSe E-UTRA communication, ProSe-assisted WLAN direct communication between two terminals, ProSe group communication, or ProSe broadcast communication.
- 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 ProSe-enabled public safety terminal acting as a communication relay between ProSe-enabled network using E-UTRA and ProSe-enabled public safety terminal
- Remote UE ProSe-enabled public safety that is connected to the EPC network via ProSe UE-to-Network Relay, ie provided with PDN connection, without being serviced by E-UTRAN in UE-to-Network Relay operation. Terminal.
- 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.
- 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-for example (for PLMN-to-PLMN handovers) (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 (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.
- the 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.
- the PDN may be an operator external public or private PDN or, for example, an in-operator PDN for the provision of IMS services.
- 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 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 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 that is 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.
- the ProSe service refers to a service capable of discovery and direct communication between physically adjacent devices, communication through a base station, or communication through a third device.
- FIG. 7 illustrates a default data path through which two UEs communicate in EPS. This basic route goes through the operator's base station (eNodeB) and the core network (ie, EPC). In the present invention, such a path will be referred to as an infrastructure data path (or EPC path). In addition, communication through such an infrastructure data path will be referred to as infrastructure communication.
- eNodeB operator's base station
- EPC core network
- FIG. 8 shows a direct mode data path between two UEs based on a process. This direct mode communication path does not go through an eNodeB and a core network (ie, EPC) operated by an operator.
- FIG. 8 (a) illustrates a case where UE-1 and UE-2 camp on different eNodeBs while transmitting and receiving data through a direct mode communication path.
- FIG. 8 (b) illustrates camping on the same eNodeB.
- FIG. 2 illustrates a case in which two UEs that are on exchange data via a direct mode communication path.
- FIG. 9 shows a locally-routed data path through an eNodeB between two UEs based on a process.
- the communication path through the eNodeB does not go through the core network (ie, EPC) operated by the operator.
- EPC core network
- the EPC may perform an EPC-level ProSe discovery procedure for determining whether proximity between two UEs and informing the UE of this.
- ProSe Function is to determine whether two UEs are in close proximity and to inform the UE.
- the ProSe function retrievals and stores process associated subscriber data and / or processor associated subscriber data from the HSS, and performs EPC level process discovery and EPC secondary WLAN direct discovery, authentication and configuration for communication. Can be. It can also operate as a location service client to enable EPC level discovery and provide the UE with information to assist in WLAN direct discovery and communication. Handles EPC ProSe User IDs and Application Layer User IDs, and exchanges signals with 3rd party application servers for application registration identifier mapping. It exchanges signals with ProSe functions of other PLMNs for transmission of proximity requests, proximity alerts, and location reporting. In addition, the ProSe Function provisions various parameters required by the UE for ProSe discovery and ProSe communication. For details on ProSe Function, apply 3GPP TS 23.303.
- the remote UE may be provided with connectivity to the EPC through the UE-to-Network Relay to communicate with an application server (AS) or participate in group communication.
- AS application server
- 12 shows an example in which a remote UE participates in group communication.
- UEs 1 to 6 which are UEs belonging to the same group, may receive downlink traffic through unicast or MBMS for a specific media constituting group communication.
- the remote UE although not in E-UTRAN coverage, sends media traffic to other group members (i.e., generates directional link traffic) by participating in a group communication via UE-to-Network Relay, or by another group member.
- One media traffic can be received.
- a GCS AS Group Communication Service Application Server
- GC1 Global System for Mobile Communications
- ii) reception of uplink data from a UE in unicast and iii) for all UEs in a group, using Unicast / MBMS delivery.
- Data delivery iv) transmission of application level session information through the Rx interface to the PCRF, v) support for service continuity procedures for UEs switching between Unicast Delivery and MBMS Delivery.
- GCS AS, Public Safety AS, GCSE AS Group Communication Service Enabler Application Server
- GCS AS, Public Safety AS, GCSE AS Group Communication Service Enabler Application Server
- the details of group communication shall apply mutatis mutandis to TS 23.468.
- FIG. 13 illustrates a procedure in which a remote UE not served by the E-UTRAN performs direct communication through the UE-to-network relay.
- a UE capable of operating as a ProSe UE-to-Network Relay may connect to the network and create a PDN connection to provide relay traffic to the remote UE.
- a PDN connection supporting UE-to-Network Relay is used only for supporting relay traffic to a remote UE.
- the relay UE creates a PDN connection through an initial connection to the E-UTRAN (S1310).
- the relay UE obtains an IPv6 prefix through a prefix delegation function.
- the relay UE performs a discovery procedure with the UE according to the model A or the model B with the remote UE (S1320).
- the remote UE selects the relay UE found by the discovery procedure and establishes a one-to-one direct connection (S1330). If there is no PDN connection according to the relay UE ID or additional PDN connection is required for relay operation, the relay UE initiates a new PDN connection procedure (S1340).
- an IPv6 prefix or an IPv4 address is assigned to the remote UE (S1350), and thus an uplink / downlink relay operation is started.
- an IPv6 stateless address auto-configuration procedure is performed, which consists of signaling a router solicitation from the remote UE to the relay UE and signaling a router advertisement from the relay UE to the remote UE.
- DHCPv4 discovery signaling from remote UE to relay UE
- DHCPv4 offer signaling from relay UE to remote UE
- DHCPv4 request signaling from remote UE to relay UE
- IPv4 address allocation using DHCPv4 process consisting of ACK signaling (from relay UE to remote UE) is performed.
- the relay UE performs a remote UE reporting procedure informing the MME that the remote UE is connected to it (S1360).
- the MME notifies that the new remote UE is connected by performing a remote UE report notification procedure for the SGW and the PGW (S1370).
- the remote UE communicates with the network through the relay UE (S1380).
- TS 23.303 shall apply mutatis mutandis.
- FIGS. 14 to 16 are diagrams illustrating direct communication signaling procedures between terminals associated with the proposed embodiment.
- 14 shows a process of establishing a direct connection between a remote UE and a relay UE and signaling messages used
- FIG. 15 shows a process after a direct connection between a remote UE and a relay UE is established and a signaling message used
- 16 illustrates a process in which a direct connection between a remote UE and a relay UE is released and a signaling message used.
- an initiating UE which initiates direct connection establishment, sends a direct communication request message to the target UE. (S1410, S1430). If the target UE can establish a direct connection with the initiating UE, the target UE responds and transmits a direct communication accept message (S1420). On the other hand, if the direct connection cannot be established, the target UE transmits a direct communication reject message (S1440). In the above-described process, the initiating UE can start the timer T4100 with the transmission of the direct connection request message. The timer T4100 is stopped as a response from the target UE is received. If the response is not received before the timer expires, the initiating UE may retransmit the message to the target UE.
- FIG. 15 is demonstrated.
- two UEs eg, a remote UE and a relay UE
- a direct communication keepalive message may be transmitted and received between two terminals to confirm that the direct connection is valid and maintain the direct connection.
- a requesting UE transmits a direct communication keepalive message to a peer UE (S1510), and a timer T4101 may be started with the transmission.
- the peer UE Upon receiving the keepalive message, transmits a direct communication keepalive ACK message to the UE requesting the keepalive message (S1520).
- T4101 is a timer for determining whether to retransmit the previously transmitted direct communication keepalive message
- T4102 is a timer for determining when to transmit a new direct communication keepalive.
- the 16 shows a procedure for releasing a direct connection.
- the UE which has decided to release the direct connection, becomes a releasing UE and transmits a direct communication release message to a peer UE (S1610 and S1630).
- the peer UE transmits a direct communication release accept message to the release UE in response to the message received from the release UE (S1620).
- the timer T4103 may be started with the transmission of the direct communication release message, and the timer T4103 is stopped with the reception of the direct communication release acknowledgment message.
- an operation when an initiating UE (UE) starting in a direct connection establishment process receives a rejection message.
- a relay UE making a direct connection with one or more remote UEs continues to send a discovery message.
- the third remote UE receiving the discovery message may transmit a direct communication request message to the relay UE, and the relay UE transmits a direct communication rejection message because it does not want to communicate with the third remote UE.
- the rejection message includes a reject cause, which may be problematic due to the specific operation of the initiating UE receiving the rejection message.
- a process of not selecting the relay UE again is required.
- the initiating UE sends a direct communication request message to the target UE, it may be a problem that a new relay is discovered before an acknowledgment or rejection response is received from the target UE.
- the initiating UE starts the timer T4100 while transmitting a direct communication request message, as described above with reference to FIG. 14.
- the discovery procedure may be operated simultaneously with the direct connection establishment procedure in operation. Before the initiating UE receives a response to the direct communication request message, the discovery procedure may be performed by a new discovery procedure to provide a better relay UE (ie, a target UE). If found, the action needs to be specifically defined.
- a problem may occur in the direct disconnection process after the direct connection is established. There is a problem because there is no specific definition for the direct disconnect message of the remote UE that has received the direct disconnect message transmitted by the relay UE. When a release cause is transmitted with a direct disconnect message, the specific operation of the remote UE that receives it needs to be defined, especially in terms of preventing the remote UE from reselecting the relay UE. It is true. In addition, similar to that described in the first problem above, the operation of the remote UE according to the temporary release reason and the permanent release reason needs to be distinguished.
- the subject that transmits the direct communication keep-alize message will be a problem.
- a requesting UE simply transmits a direct communication keep-alive message, but it does not describe in detail which UE will serve as the requesting UE.
- both UEs may transmit a keepalive message. In this case, not only signaling overhead may occur, leading to unnecessary waste of radio resources, but also a burden of coordinating transmission timing between two UEs.
- the problem of the case where the requesting UE (requesting UE) does not receive a response after the transmission of the direct communication keepalive message should also be solved.
- This problem may similarly occur even if the initiating UE, which sent the direct communication request message, has not received a response.
- a UE / requesting UE that starts after the expiration of a timer that starts with the transmission of two messages retransmits the message, which may be problematic because there is no specific definition for after retransmission up to the maximum number of retransmission repetitions. If the response is not received despite repeated retransmissions, it may be because the quality of the communication connection is poor, and the problem of continuing to occupy the wireless channel even though it is not necessary to maintain the communication connection needs to be solved.
- a case in which a releasing UE described with reference to FIG. 16 does not receive a response from a peer UE after transmitting a direct disconnection message may be considered.
- the release UE repeatedly retransmits the release message until it receives a release acknowledgment message from the peer UE. Accordingly, there is a problem that unnecessary signaling may be repeatedly performed.
- a problem may occur with respect to a triggering condition and a process of selecting a candidate of a target UE in a relay selection / reselection process of a remote UE. That is, in TS 24.334, a problem may occur because the triggering conditions of the relay selection / reselection procedure and which UE are selected as candidates of the target UE are not defined in detail.
- FIG. 17 to 20 are diagrams illustrating a direct communication method between terminals according to a proposed embodiment.
- FIG. 17 describes an embodiment of the first and second problems described above
- FIG. 18 illustrates the third problem described above
- FIG. 19 illustrates the fourth embodiment.
- the fifth problem FIG. 20 describes embodiments for solving the sixth problem
- the embodiment of the seventh problem is collectively described.
- the term 'back-off timer' or 'timer' is used in various embodiments, and although the name of a specific timer is not defined or explained, according to each embodiment and the application to which it is applied. It can mean another kind of timer.
- the initiating UE may operate in two ways. First, the target UE which has transmitted the direct communication rejection message is included in the forbidden UE list for link setup. UEs included in the list may be excluded from the connection establishment process, and may be excluded together in the discovery procedure.
- the initiating UE starts a predetermined backoff timer upon receiving a reject message.
- the backoff timer value may be sent to the initiating UE included in the direct communication rejection message and may be already configured in the initiating UE, but instead of the value already set if it is included in the message and sent to the initiating UE The received value is used.
- the UE initiating while the backoff timer is in operation does not proceed with the connection establishment process for the UE that has transmitted the rejection message and excludes the UE from the discovery procedure.
- the initiating UE adds the target UE to the forbidden UE list and starts a timer upon receiving the rejection message. Until the timer expires, the target UE is added to the prohibited UE list, and the target UE may be deleted from the prohibited UE list when the timer expires.
- two or more reasons for rejection may be utilized to distinguish whether the restriction of the reselection of the target UE is permanent or temporary, or to inform the UE of explicitly initiating the reselection.
- one reason for rejection (for example, reason # 1) is used when permanently restricting the reselection of the target UE, and the UE receiving the rejection message including the reason for rejection is The connection setup or discovery procedure may not be performed to the target UE.
- the method of adding the above-described target UE to the prohibited UE list may be utilized.
- the reason for refusal when permanently restricting reselection is "# 1: direct communication to target UE not allowed and retransmission. not allowed) ". If reselection of the target UE is prohibited, the transmission of all messages, including PC5 signaling messages to the target UE, is also prohibited.
- Another reason for rejection is "direct communication to target UE not allowed but retransmission allowed” or "reason # 4: direct communication to target UE.”
- "Direct communication to target UE temporarily not allowed” may be newly defined. This reason for rejection is distinguished from the reason for rejection for the permanent restriction described above, and the initiating UE receiving this may retransmit a communication request message directly to the target UE. That is, 'retransmission' described in the reason for rejection means that the direct communication request message is retransmitted to the same target UE that has transmitted the direct communication rejection message.
- a timer may be utilized similar to that described above. That is, when a timer is previously set in a UE that is received or started with a timer included in the reject message, the corresponding timer value may be utilized to temporarily limit reselection of the target UE. If the timer is applied, the initiating UE may wait for the expiration of the timer to perform retransmission to the target UE, and the connection establishment procedure or discovery procedure should also be performed after the expiration of the corresponding timer. On the other hand, if the timer is not applied, the initiating UE may proceed with retransmission immediately after receiving the rejection message as necessary.
- the initiating UE that has received the rejection message including the reason # 1 described above cannot perform the reselection procedure to find a new target UE since it cannot permanently reselect the target UE.
- the initiating UE receiving the rejection message including reason # 4 may retransmit the direct communication request message as soon as connection establishment is required. That is, even without a timer, by using two or more reasons for rejection, it is possible to prevent permanent / temporary reselection of the target UE.
- the proposed UE transmits a direct communication request message to the target UE (ie, a relay UE) (S1710) and receives a direct communication rejection message.
- the target UE ie, a relay UE
- the initiating UE performs the reselection procedure except for the target UE which transmitted the rejection message (S1730).
- the reason for rejection included in the rejection message is the temporary reason for rejection (S1740)
- the initiating UE performs the reselection procedure except for the target UE while the timer is running (S1750). If the timer is not used, even if a temporary reason for rejection is received, the initiating UE may immediately retransmit the direct communication request message or perform a reselection procedure for the target UE.
- the target UE is reselected and the timer value may be included in the direct communication rejection message and transmitted to the initiating UE.
- Table 2 shows an example in which a direct communication rejection message indicates whether a target UE is reselected, and Tables 3 and 4 indicate an 'extended PC5 signaling cause' IE (Information Element) indicating the reason. Shows an example in which is implemented in bits.
- E-UTRAN allowed value (octet 1, bit 1) Bit 1 0 reselection allowed (or, retransmission allowed) One reselection not allowed (or, retransmission not allowed) Bit 2 to 4 of octet 1 are spare and shall be coded as zero
- Table 5 shows an example in which the direct communication rejection message includes a timer value for temporarily limiting reselection of the target UE, and Tables 6 and 7 show actual implementation examples of the timer value.
- Timer value (octet 2) Bit 5 to 1 represent the binary coded timer value.
- Bit 6 to 8 defines the timer value unit for T4xxx as follows: Bit 8 Bit 7 Bit 6 0 0 0 value is incremented in multiples of 2 seconds 0 0 One value is incremented in multiples of 1 minute 0 One 0 value is incremented in multiples of decihours One One One value indicates that the timer is deactivated Other values shall be interpreted as multiples of 1 minute in this version of the porotocol.
- the initiating UE starts the timer T4100 and waits for a response from the target UE while transmitting a direct communication request message according to the direct connection establishment procedure.
- the initiating UE may proceed with the discovery process separately from the ongoing direct connection establishment procedure, and the discovery procedure may be performed simultaneously with the direct connection establishment procedure.
- the discovery procedure may be a UE-to-network relay discovery operation, in which a relay discovery addition for which UE-to-network relay discovery announces Temporary Mobile Group Identity (TMGI) related information that can be received and forwarded by the UE-to-network relay discovery. It may also be an operation of transmitting relay discovery additional information.
- TMGI Temporary Mobile Group Identity
- the operation of the initiating UE will be described when the initiating UE finds / selects a target UE having a better quality of the wireless connection through the above-described discovery procedure before receiving the response from the target UE.
- the UE while the timer T4100 is in operation, the UE cannot transmit a new direct communication request message to the same target UE. This means that it is possible to send a communication request message directly to the new target UE.
- the initiating UE may stop the timer T4100 and start a new connection establishment procedure. That is, the initiating UE may stop the timer in operation to terminate the direct connection establishment procedure and start the connection establishment procedure with the new target UE. In this case, even if the initiating UE receives a direct communication grant message from the previous target UE, the initiating UE does not use the direct connection and performs the direct disconnection procedure for the previous target UE.
- the initiating UE may start a new direct connection establishment procedure without stopping the running timer. Even in this case, even if the initiating UE receives a direct communication grant message from the previous target UE, the initiating UE does not use the direct connection and performs the direct disconnection procedure for the previous target UE.
- the third embodiment proposes an operation of a remote UE for a direct communication release message.
- the releasing UE may transmit a direct communication release message to the peer UE (peer UE, or remote UE).
- This direct communication release message can include information indicating "reason # 1: communication to peer UE no longer needed” as the reason for the release.
- this release reason may not clearly express the intention of the UE to release. That is, when the communication through the direct connection between the relay UE and the remote UE is normally terminated, such a release reason is not a problem, but the connection is released for abnormal reasons (for example, when the wireless connection quality is unexpectedly degraded). In this case, a new release reason needs to be defined to prevent reselection of the relay UE.
- the reason described in the first embodiment may be similarly used in that it is for the purpose of preventing reselection of the releasing UE. That is, "direct communication to target UE not allowed" proposed as the reason for rejection may be used as a reason for release or a newly defined reason for release may be used.
- the peer UE may operate in two ways.
- the UE for releasing the communication release message is included in the forbidden UE list for link setup. UEs included in the list may be excluded from the connection establishment process, and may be excluded together in the discovery procedure.
- the peer UE starts a predetermined backoff timer upon receiving the release message.
- the backoff timer value may be included in the direct communication release message and sent to the peer UE, or may be already configured in the peer UE, but if included in the message and sent to the peer UE, the value received instead of the already set value This is used. While the backoff timer is in operation, the peer UE does not proceed with the connection establishment process for the releasing UE that has sent the release message, and excludes the releasing UE from the discovery procedure.
- the two approaches can be applied together. That is, when the peer UE receives the release message, the peer UE adds the de-targeting UE to the prohibited UE list and starts a timer. Until the timer expires, the canceling UE list is added to the prohibited UE list, and when the timer expires, the canceling UE list may be deleted.
- one release reason (for example, reason # 1) is used when permanently restricting the reselection of a UE that releases, and the peer receiving the release message including the release reason.
- the UE may not proceed with connection establishment or discovery procedure to the releasing UE.
- the method of adding the canceling UE described above to the prohibited UE list may be utilized.
- the release reason when permanently restricting the reselection is "# 1: direct communication to the target UE not allowed and retransmission is prohibited (direct communication to target UE not allowed and retransmission). not allowed) ". If reselection of the releasing UE is prohibited, the transmission of all messages, including PC5 signaling messages, to the releasing UE is also prohibited.
- a timer may be utilized similar to that described above. That is, when the timer is included in the release message or the timer is preset in the peer UE, the timer value may be utilized to limit the reselection of the UE temporarily releasing. If the timer is applied, the peer UE may perform retransmission to the UE that waits for the expiration of the timer, and a connection establishment procedure or discovery procedure should also be performed after waiting for the expiration of the corresponding timer. On the other hand, if the timer is not applied, the peer UE may proceed with retransmission immediately after receiving the release message as needed.
- the peer UE receiving the release message including the above-described reason # 1 cannot perform a reselection procedure for finding a new relay UE since the peer UE cannot permanently reselect the canceling UE.
- the peer UE receiving the release message including reason # 4 may retransmit the communication request message directly. That is, even if there is no timer, it is possible to prevent permanent / temporary reselection of the releasing UE by utilizing two or more reasons for rejection.
- the proposed UE transmits a communication release message directly to a peer UE (ie, a remote UE) (S1810 and S1830).
- the peer UE performs the reselection procedure except for the release UE transmitting the release message (S1820).
- the release reason included in the release message is the temporary release reason (S1830)
- the peer UE performs the reselection procedure except for the UE which releases while the timer is running (S1840). If the timer is not used, even if a temporary reason for rejection is received, the peer UE may immediately perform a reselection procedure for the UE that retransmits or releases the direct communication request message.
- whether to deselect the UE to be released and the timer value may be included in the direct communication release message and transmitted to the peer UE.
- Table 8 below shows an example in which a direct communication release message indicates whether or not a UE is reselected, and Tables 9 and 10 indicate an 'extended PC5 signaling cause' IE (Information Element) indicating the reason. ) Shows an example in which bits are implemented.
- E-UTRAN allowed value (octet 1, bit 1) Bit 1 0 reselection allowed (or, retransmission allowed) One reselection not allowed (or, retransmission not allowed) Bit 2 to 4 of octet 1 are spare and shall be coded as zero
- Table 11 shows an example in which the direct communication release message includes a timer value for temporarily limiting the reselection of the UE to release, and Tables 12 and 13 show examples of actual implementation of the timer value.
- Timer value (octet 2) Bit 5 to 1 represent the binary coded timer value.
- Bit 6 to 8 defines the timer value unit for T4xxx as follows: Bit 8 Bit 7 Bit 6 0 0 0 value is incremented in multiples of 2 seconds 0 0 One value is incremented in multiples of 1 minute 0 One 0 value is incremented in multiples of decihours One One One value indicates that the timer is deactivated Other values shall be interpreted as multiples of 1 minute in this version of the porotocol.
- the third embodiment described above may be applied to the case of checking the quality of the wireless connection through the discovery message and transmitting a direct communication release message because the quality of the wireless connection drops below a certain level.
- UE will be a subject that transmits a direct communication keepalive message between a remote UE and a relay UE.
- TS 24.334 defines a UE that transmits a direct communication keepalive message as a 'requesting UE'.
- Three ways can be considered for selecting the 'requesting UE'. First, it may be determined as a UE requesting a UE that is a subject for transmitting a specific message. For example, the UE sending the direct communication request message or the UE sending the direct communication grant message can be determined as the 'requesting UE' which then sends the keepalive message. On the contrary, the direct communication request message or the direct communication approval message can recognize that the other party becomes the requesting UE and the peer UE that is the other node.
- a method of selecting a specific UE as a requesting UE That is, in TS 23.303, a remote UE and a relay UE establishing one-to-one communication are defined, and in the relay scenario, the remote UE or the relay UE may be a requesting UE.
- the UE receiving the keep-alive message may recognize that the UE is a peer UE.
- a third method may also consider a method in which a specific UE has a decision to select a requesting UE.
- the UE-to-network relay UE may determine which of itself and the remote UE will be the requesting UE.
- the remote UE may select the requesting UE.
- the UE having the decision right decides the requesting UE and delivers it to the other UE.
- an indicator indicating which UE is determined as the requesting UE may be delivered to the counterpart UE, and the indicator may be included in a PC5 signaling message (eg, a direct communication request message or a direct communication acknowledgment message) to the counterpart UE.
- the indicator may inform the requesting UE by explicitly indicating to UE A or UE B, for example, bit '0' indicates that UE A is selected and bit '1' indicates that UE B has been selected as the requesting UE. Can be.
- the above-described UE A or UE B may be a relay UE or a remote UE.
- either UE may select the requesting UE in consideration of the situation of the two UEs. That is, the requesting UE may select the requesting UE in consideration of information about a state of each UE (for example, a load state, a battery state, a class of the terminal, etc.). Also, a UE having information of both UEs may compare information of two UEs to determine which UE is suitable for the requesting UE.
- a state of each UE for example, a load state, a battery state, a class of the terminal, etc.
- a UE having information of both UEs may compare information of two UEs to determine which UE is suitable for the requesting UE.
- the direct communication request message will be described.
- the initiating UE starts a timer T4100 with the transmission of the direct communication request message and resends the direct communication request message when the timer expires.
- retransmission may be made up to the maximum allowable retransmission number.
- the initiating UE if a direct communication request message is transmitted but no response is received from the target UE until the maximum number of retransmissions allowed, the initiating UE aborts the connection establishment procedure for the corresponding direct connection and discovers another target UE.
- the procedure may be performed (S1910, S1920).
- a connection establishment procedure with the corresponding UE may be performed.
- An initiating UE is no longer a target because no acknowledgment or rejection message has not been received in response to the direct communication request message until the maximum number of retransmissions may indicate that it is not already able to establish a direct connection with the target UE. There is no need to maintain or proceed with the connection establishment procedure with the UE. Accordingly, the initiating UE performs a relay reselection procedure for a new connection establishment procedure.
- the direct communication request message may be transmitted again to the target UE which has transmitted the direct communication request message in the reselection process.
- the initiating UE since it may be inefficient for the initiating UE to directly transmit a communication request message to the same target UE and proceed with the connection establishment procedure, the initiating UE may operate to enable retransmission after a certain time interval has elapsed.
- the initiating UE starts a backoff timer after stopping the connection establishment procedure and does not send a communication request message or perform a discovery procedure directly to the same target UE before the timer expires.
- the UE starting after the timer expires may retransmit the communication request message directly to the same target UE to proceed with the connection establishment procedure, perform a reselection procedure for the target UE, or proceed with the discovery procedure.
- the keep-alive confirmation message is not received after the keep-alive message is transmitted, it can be divided into two types. First, the requesting UE sent a keepalive message but the peer UE did not receive it. Second, the peer UE received a keepalive message and sent a keepalive confirmation message but the requesting UE did not receive it. In both cases, the requesting UE and the peer UE may determine that the current direct connection is no longer valid. The two UEs can then locally release the direct connection.
- the requesting UE ie, the remote UE
- the requesting UE retransmits the keepalive message after the timer T4101 started with the transmission of the direct communication keepalive message expires and repeats the retransmission up to the maximum number of retransmissions allowed (S1940). If no response is received from the peer UE in the attempt to retransmit for the maximum number of retransmission allowances (eg, a rejection response or an acknowledgment), the requesting UE determines that the current wireless connection quality is no longer valid. . Subsequently, the requesting UE stops the keepalive procedure and locally releases the radio connection (S1950).
- the method of locally releasing the radio connection may be performed by notifying the eNB via sidelink UE information that, in the case of Model 1 in E-UTRAN coverage, the communication with the peer UE is terminated. Upon receipt of this, the eNB stops allocating radio resources used for transmission to the peer UE. If it is model 2 or out of E-UTRAN coverage in E-UTRAN coverage, the requesting UE stops transmitting operations for the peer UE and stops using radio resources used for transmission.
- the UE that has released the wireless connection locally performs a discovery procedure to find another target UE. If another target UE is found, a direct connection establishment procedure with the target UE is performed and a reselection procedure for selecting a new target UE is performed. In this case, the discovery procedure or the direct connection establishment procedure for the same target UE may not proceed immediately, but may be performed after a predetermined time has been exceeded. Similar to the case of the direct communication request message described above, a scheme of using a backoff timer may also be considered. That is, the requesting UE starts a timer after stopping the keepalive procedure, and does not proceed with discovery or connection establishment procedure for the same peer UE before the timer expires. After the timer expires, the requesting UE may retransmit the communication request message directly to the same peer UE to proceed with the connection establishment procedure, perform a reselection procedure for the same peer UE, or proceed with the discovery procedure.
- the peer UE receives the communication keepalive message directly from the requesting UE and transmits it to the requesting UE.
- the peer UE may be a problem because there is no message retransmission operation that can determine the current wireless connection, such as the requesting UE.
- a requesting UE ie, a remote UE
- the peer UE starts the deactivation timer T4abcd when it is time for no communication or PC5 signaling to occur after the radio connection is established (i.e., the completion of the transmission of the data packet or just after the completion of the signaling).
- This timer T4abcd is a timer that operates for the maximum inactivity period described above, and is stopped again when any communication or PC5 signaling starts (that is, when data packet transmission starts) and is set to an initial value.
- the peer UE determines that the wireless connection with the requesting UE is no longer valid and releases the wireless connection locally (S1960).
- the timer T4abcd corresponding to the maximum inactivity interval should be set in consideration of the number of keepalive maximum retransmissions of the requesting UE.
- the maximum deactivation interval may be calculated in consideration of a transmission period in which the requesting UE transmits a keepalive message, a retransmission time interval of the keepalive message, and a maximum number of retransmissions. For example, the maximum deactivation interval may be calculated according to Equation 1 below.
- 'Inactivity timerkeep' is a parameter representing a maximum inactivity period
- 'transmission period of keepalive message' is a period in which the requesting UE transmits a keep-alive message
- 'retransmission time interval' is a keep-alive message in the requesting UE.
- the interval between retransmissions, 'maximumm number of allowed retransmissions' is a parameter indicating the maximum allowed number of times that the requesting UE can retransmit the keepalive message.
- the maximum deactivation interval calculated as described above may be received from the requesting UE through a direct communication request message in a connection establishment procedure.
- the maximum deactivation interval may be a value preset by itself to the peer UE, but when the value is included in the direct communication request message, the peer UE follows the received value.
- the maximum deactivation interval may be included in the direct communication keepalive message transmitted by the requesting UE and transmitted to the peer UE, and when the new maximum deactivation interval value is received, the peer UE replaces the previously stored value.
- the maximum deactivation interval may be set differently for each requesting UE. That is, the local configuration value may be different for each UE, since the retransmission interval or the maximum number of retransmission allowances of the keepalive message may be implemented differently for each UE. In particular, considering that mobility, reporting type, message transmission pattern, etc. are all different for each UE, a value corresponding to the maximum deactivation interval may be set differently for each UE.
- the peer UE when the timer T4abcd corresponding to the maximum deactivation interval expires, the peer UE locally releases the radio connection. In this process, the peer UE may send a release message to the requesting UE prior to locally releasing the wireless connection. That is, the peer UE may transmit a direct communication release message to the UE requesting a direct communication release message according to the expiration of the timer T4abcd corresponding to the maximum inactivity interval, and then may locally release the radio connection.
- a description will be given of a sixth embodiment, in which a UE dismissing sends a communication release message directly to a peer UE but does not receive a response.
- the description will be made in terms of a release UE (eg, a relay UE) and a peer UE (eg, a remote UE).
- the releasing UE sends a direct communication release message to the peer UE (S2010), and starts the timer T4103.
- the releasing UE may locally release the direct connection without retransmission of the release message.
- the releasing UE may retransmit the direct communication release message up to the maximum number of retransmissions allowed after expiration of the timer T4103, and may locally release the direct connection if the response is not received even up to the maximum number of retransmissions (S2030).
- whether or not to perform retransmission may vary depending on the situation of the UE which releases, for example, depending on the release reason included in the direct communication release message.
- the peer UE When the peer UE receives a direct communication release message from the releasing UE, the peer UE transmits to the UE releasing the direct communication release acknowledgment message.
- the peer UE may be a problem because there is no defined message retransmission operation that can determine the current wireless connection, such as the UE to release.
- a peer UE For a peer UE, an embodiment proposes that a peer UE defines a maximum inactivity period and releases a direct connection locally if no message is received during that period. Specifically, when the peer UE reaches a time when no communication occurs or PC5 signaling does not occur after the direct communication release acknowledgment message (that is, when the transmission of the data packet is completed or immediately after the completion of the transmission of signaling), Start the inactivity timer T4abcd.
- This timer T4abcd is a timer that operates for the maximum inactivity period described above, and is stopped again when any communication or PC5 signaling starts (that is, when data packet transmission starts) and is set to an initial value.
- the peer UE determines that the wireless connection with the releasing UE is no longer valid and releases the wireless connection locally (S2040).
- the timer T4abcd corresponding to this maximum deactivation interval should be set in consideration of the number of keep-alive maximum retransmissions of the releasing UE.
- the maximum deactivation interval may be calculated in consideration of a transmission period in which the deactivating UE transmits a keepalive message, a retransmission time interval of the keepalive message, and a maximum number of retransmissions. For example, the maximum deactivation interval may be calculated according to Equation 1 described above.
- the maximum deactivation interval according to the above may be calculated and stored by the peer UE, or may be any value set.
- the maximum deactivation interval calculated by the peer UE may be previously transmitted to the UE to release through a direct communication request message in the process of establishing direct connection with the UE to release (for example, S1930 of FIG. 19).
- this maximum deactivation interval may be set differently for each peer UE. That is, the local configuration value may be different for each UE, since the retransmission interval or the maximum number of retransmission allowances of the keepalive message may be implemented differently for each UE. In particular, considering that mobility, reporting type, message transmission pattern, etc. are all different for each UE, a value corresponding to the maximum deactivation interval may be set differently for each UE.
- the remote UE which receives the direct communication rejection message or the direct communication release message is set to not reselect the relay UE has been described. If a permanent rejection reason / release reason is received, the remote UE remembers the relay UE and excludes it from the relay UE selection / reselection process (or target UE selection / reselection process). Subsequently, a selection / reselection process for selecting a new relay UE is performed.
- the remote UE may send a direct communication request message directly to the same UE if connection establishment is required. Conversely, if a temporary rejection reason / release reason is received but the retransmission cannot be performed immediately (for example, if the timer value is not zero, not deactivated, or is not null), then a connection establishment is required.
- the remote UE may perform a relay UE selection / reselection process for the same UE, or wait for a predetermined time period (eg, an expiration time of a timer) and then send a direct communication request message directly to the same UE.
- relay UE selection / reselection may be triggered even when retransmission is attempted up to the maximum number of allowable times for retransmission of a specific message but no response is received from the counterpart node. That is, when a response to the direct communication rejection message is not received but direct connection establishment is required, the remote UE performs a relay UE selection / reselection procedure. Similarly, if the acknowledgment for the direct communication keepalive message is not received, the remote UE releases the direct connection locally and performs a relay UE selection / reselection procedure.
- a rejection reason / release reason or an indicator not allowing reselection for the UE may be received together.
- the initiating UE or peer UE should exclude the UE from selection or reselection of the target UE.
- UEs that transmit a rejection / release message in the process of selecting a candidate target UE for establishing a new direct connection are excluded. This process may be performed by adding a UE to the prohibited UE list, and the UE added to the prohibited UE list is excluded from the selection / reselection process of the new target UE.
- 21 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 above-described functions or operations.
- 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 direct communication method between terminals 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.
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.) |
IEI | Information Element | Type/Reference | Presence | Format | Length |
DIRECT_COMMUNICATION_REJECT message identity | PC5-SP Message Type12.x.1.1. | M | V | 1 | |
Sequence Number | Sequence Number12.x.1.2 | M | V | 2 | |
PC5 Signalling Cause Value | PC5 Signalling Cause Value12.x.1.7 | M | V | 1 | |
Extended PC5 Signalling cause | Extended PC5 Signalling cause11.a.b.c | O | TLV | 1 |
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | octet1 |
Extended PC5 Signalling Cause IEI | 0 | 0 | 0 | Reselection allowed | ||||
Spare |
E-UTRAN allowed value (octet 1, bit 1) | |
Bit 1 | |
0 | reselection allowed (or, retransmission allowed) |
1 | reselection not allowed (or, retransmission not allowed) |
Bit 2 to 4 of octet 1 are spare and shall be coded as zero |
IEI | Information Element | Type/Reference | Presence | Format | Length |
DIRECT_COMMUNICATION_REJECT message identity | PC5-SP Message Type12.x.1.1. | M | V | 1 | |
Sequence Number | Sequence Number12.x.1.2 | M | V | 2 | |
PC5 Signalling Cause Value | PC5 Signalling Cause Value12.x.1.7 | M | V | 1 | |
T4xxxx | T4xxxx | O | TLV | 3 |
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
T4xxxx IEI | octet1 | |||||||
Unit | Timer value | octet2 |
Timer value (octet 2) | |||
Bit 5 to 1 represent the binary coded timer value. | |||
Bit 6 to 8 defines the timer value unit for T4xxx as follows: | |||
Bit 8 | Bit 7 | Bit 6 | |
0 | 0 | 0 | value is incremented in multiples of 2 seconds |
0 | 0 | 1 | value is incremented in multiples of 1 minute |
0 | 1 | 0 | value is incremented in multiples of decihours |
1 | 1 | 1 | value indicates that the timer is deactivated |
Other values shall be interpreted as multiples of 1 minute in this version of the porotocol. |
IEI | Information Element | Type/Reference | Presence | Format | Length |
DIRECT_COMMUNICATION_REJECT message identity | PC5-SP Message Type12.x.1.1. | M | V | 1 | |
Sequence Number | Sequence Number12.x.1.2 | M | V | 2 | |
PC5 Signalling Cause Value | PC5 Signalling Cause Value12.x.1.7 | M | V | 1 | |
Extended PC5 Signalling cause | Extended PC5 Signalling cause11.a.b.c | O | TLV | 1 |
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | octet1 |
Extended PC5 Signalling Cause IEI | 0 | 0 | 0 | Reselection allowed | ||||
Spare |
E-UTRAN allowed value (octet 1, bit 1) | |
Bit 1 | |
0 | reselection allowed (or, retransmission allowed) |
1 | reselection not allowed (or, retransmission not allowed) |
Bit 2 to 4 of octet 1 are spare and shall be coded as zero |
IEI | Information Element | Type/Reference | Presence | Format | Length |
DIRECT_COMMUNICATION_REJECT message identity | PC5-SP Message Type12.x.1.1. | M | V | 1 | |
Sequence Number | Sequence Number12.x.1.2 | M | V | 2 | |
PC5 Signalling Cause Value | PC5 Signalling Cause Value12.x.1.7 | M | V | 1 | |
T4xxxx | T4xxxx | O | TLV | 3 |
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
T4xxxx IEI | octet1 | |||||||
Unit | Timer value | octet2 |
Timer value (octet 2) | |||
Bit 5 to 1 represent the binary coded timer value. | |||
Bit 6 to 8 defines the timer value unit for T4xxx as follows: | |||
Bit 8 | Bit 7 | Bit 6 | |
0 | 0 | 0 | value is incremented in multiples of 2 seconds |
0 | 0 | 1 | value is incremented in multiples of 1 minute |
0 | 1 | 0 | value is incremented in multiples of decihours |
1 | 1 | 1 | value indicates that the timer is deactivated |
Other values shall be interpreted as multiples of 1 minute in this version of the porotocol. |
Claims (14)
- 무선 통신 시스템에서 ProSe-enabled UE(Proximity Service-enabled User Equipment)인 릴레이 UE가 리모트 UE와의 직접 통신을 수행하는 방법에 있어서,상기 리모트 UE와의 직접 연결 설정 과정에서, 상기 리모트 UE로부터 최대 비활성화 구간(maximum inactivity period)에 대한 정보를 포함하는 직접 통신 요청(direct communication request) 메시지를 수신하는 단계;상기 리모트 UE와의 직접 연결을 통한 데이터 전송 또는 시그널링이 완료되면 상기 최대 비활성화 구간에 대응하는 타이머를 시작하는 단계; 및상기 타이머가 만료할 때까지 상기 리모트 UE로부터 어떠한 메시지도 수신되지 않는 경우, 상기 리모트 UE와의 직접 연결을 로컬 해제(locally release)하는 단계를 포함하는, 직접 통신 수행 방법.
- 제1항에 있어서,상기 타이머가 만료하기 전에 상기 리모트 UE로부터 데이터 전송 또는 시그널링 메시지가 수신되는 경우, 상기 릴레이 UE는 상기 타이머를 중지하고 초기 값으로 설정하는 것인, 직접 통신 수행 방법.
- 제1항에 있어서,상기 최대 비활성화 구간은 상기 리모트 UE가 전송하는 직접 통신 킵얼라이브(direct communication keepalive) 메시지의 전송 주기, 재전송 시간 간격 및 최대 재전송 허용 횟수를 고려하여 결정되는 것인, 직접 통신 수행 방법.
- 제3항에 있어서,상기 최대 비활성화 구간은 아래의 수학식에 따라 결정되며,[수학식]'Inactivity timerkeep' ≥ 'transmission period of keepalive message' + 'retransmission time interval' * 'maximum number of allowed retransmissions'상기 수학식에서 'Inactivity timerkeep'은 상기 최대 비활성화 구간을 나타내고, 상기 'transmission period of keepalive message'는 상기 직접 통신 킵얼라이브 메시지의 전송 주기를 나타내고, 상기 'retransmission time interval'은 상기 직접 통신 킵얼라이브 메시지의 재전송 시간 간격을 나타내고, 상기 'maximumm number of allowed retransmissions'은 상기 직접 통신 킵얼라이브 메시지의 최대 재전송 허용 횟수를 나타내는 것인, 직접 통신 수행 방법.
- 제1항에 있어서,상기 직접 통신 요청 메시지를 수신한 이후에 상기 리모트 UE로부터 새로운 최대 비활성화 구간에 대한 정보를 포함하는 직접 통신 킵얼라이브 메시지를 수신하는 경우, 상기 타이머는 상기 새로운 최대 비활성화 구간에 대한 정보에 따라 설정되는 것인, 직접 통신 수행 방법.
- 제1항에 있어서,상기 최대 비활성화 구간은 상기 리모트 UE가 전송하는 직접 통신 킵얼라이브 메시지의 전송 패턴과 관련되고, 상기 직접 통신 킵얼라이브 메시지의 전송 패턴은 상기 리모트 UE의 모빌리티(mobility), 리포팅 타입(reporting type) 및 메시지 전송 패턴 중 적어도 하나를 고려하여 결정되는 것인, 직접 통신 수행 방법.
- 제1항에 있어서,상기 릴레이 UE와 상기 리모트 UE 중에서 상기 리모트 UE만이 직접 통신 킵얼라이브 메시지를 전송하는 것인, 직접 통신 수행 방법.
- 무선 통신 시스템에서 ProSe-enabled UE(Proximity Service-enabled User Equipment)이고 리모트 UE와 직접 통신을 수행하는 릴레이 UE에 있어서,송신부;수신부; 및상기 송신부 및 상기 수신부와 연결되어 동작하는 프로세서를 포함하되,상기 프로세서는,상기 리모트 UE와의 직접 연결 설정 과정에서, 상기 리모트 UE로부터 최대 비활성화 구간(maximum inactivity period)에 대한 정보를 포함하는 직접 통신 요청(direct communication request) 메시지를 수신하고,상기 리모트 UE와의 직접 연결을 통한 데이터 전송 또는 시그널링이 완료되면 상기 최대 비활성화 구간에 대응하는 타이머를 시작하고,상기 타이머가 만료할 때까지 상기 리모트 UE로부터 어떠한 메시지도 수신되지 않는 경우, 상기 리모트 UE와의 직접 연결을 로컬 해제(locally release)하는 것인, 릴레이 UE.
- 제8항에 있어서,상기 타이머가 만료하기 전에 상기 리모트 UE로부터 데이터 전송 또는 시그널링 메시지가 수신되는 경우, 상기 릴레이 UE는 상기 타이머를 중지하고 초기 값으로 설정하는 것인, 릴레이 UE.
- 제8항에 있어서,상기 최대 비활성화 구간은 상기 리모트 UE가 전송하는 직접 통신 킵얼라이브(direct communication keepalive) 메시지의 전송 주기, 재전송 시간 간격 및 최대 재전송 허용 횟수를 고려하여 결정되는 것인, 릴레이 UE.
- 제10항에 있어서,상기 최대 비활성화 구간은 아래의 수학식에 따라 결정되며,[수학식]'Inactivity timerkeep' ≥ 'transmission period of keepalive message' + 'retransmission time interval' * 'maximum number of allowed retransmissions'상기 수학식에서 'Inactivity timerkeep'은 상기 최대 비활성화 구간을 나타내고, 상기 'transmission period of keepalive message'는 상기 직접 통신 킵얼라이브 메시지의 전송 주기를 나타내고, 상기 'retransmission time interval'은 상기 직접 통신 킵얼라이브 메시지의 재전송 시간 간격을 나타내고, 상기 'maximumm number of allowed retransmissions'은 상기 직접 통신 킵얼라이브 메시지의 최대 재전송 허용 횟수를 나타내는 것인, 릴레이 UE.
- 제8항에 있어서,상기 직접 통신 요청 메시지를 수신한 이후에 상기 리모트 UE로부터 새로운 최대 비활성화 구간에 대한 정보를 포함하는 직접 통신 킵얼라이브 메시지를 수신하는 경우, 상기 타이머는 상기 새로운 최대 비활성화 구간에 대한 정보에 따라 설정되는 것인, 릴레이 UE.
- 제8항에 있어서,상기 최대 비활성화 구간은 상기 리모트 UE가 전송하는 직접 통신 킵얼라이브 메시지의 전송 패턴과 관련되고, 상기 직접 통신 킵얼라이브 메시지의 전송 패턴은 상기 리모트 UE의 모빌리티(mobility), 리포팅 타입(reporting type) 및 메시지 전송 패턴 중 적어도 하나를 고려하여 결정되는 것인, 릴레이 UE.
- 제8항에 있어서,상기 릴레이 UE와 상기 리모트 UE 중에서 상기 리모트 UE만이 직접 통신 킵얼라이브 메시지를 전송하는 것인, 릴레이 UE.
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201680062507.7A CN108353448B (zh) | 2015-10-26 | 2016-10-26 | 在无线通信系统的终端之间的直接通信的方法及其设备 |
JP2018520101A JP6860560B2 (ja) | 2015-10-26 | 2016-10-26 | 無線通信システムにおいて端末間の直接通信方法及びそのための装置 |
KR1020187010457A KR102170107B1 (ko) | 2015-10-26 | 2016-10-26 | 무선 통신 시스템에서 단말 간의 직접 통신을 방법 및 이를 위한 장치 |
EP16860195.3A EP3370473B1 (en) | 2015-10-26 | 2016-10-26 | Method for direct communication between terminals in wireless communication system and device therefor |
US15/765,640 US10499452B2 (en) | 2015-10-26 | 2016-10-26 | Method for direct communication between terminals in wireless communication system and device therefor |
Applications Claiming Priority (10)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201562246136P | 2015-10-26 | 2015-10-26 | |
US62/246,136 | 2015-10-26 | ||
US201562249955P | 2015-11-03 | 2015-11-03 | |
US62/249,955 | 2015-11-03 | ||
US201562251017P | 2015-11-04 | 2015-11-04 | |
US62/251,017 | 2015-11-04 | ||
US201562252466P | 2015-11-07 | 2015-11-07 | |
US62/252,466 | 2015-11-07 | ||
US201562257725P | 2015-11-20 | 2015-11-20 | |
US62/257,725 | 2015-11-20 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2017074012A1 true WO2017074012A1 (ko) | 2017-05-04 |
Family
ID=58630595
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2016/012071 WO2017074012A1 (ko) | 2015-10-26 | 2016-10-26 | 무선 통신 시스템에서 단말 간의 직접 통신을 방법 및 이를 위한 장치 |
Country Status (6)
Country | Link |
---|---|
US (1) | US10499452B2 (ko) |
EP (1) | EP3370473B1 (ko) |
JP (1) | JP6860560B2 (ko) |
KR (1) | KR102170107B1 (ko) |
CN (1) | CN108353448B (ko) |
WO (1) | WO2017074012A1 (ko) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111034334A (zh) * | 2017-08-11 | 2020-04-17 | 华为技术有限公司 | 一种路径转换方法、相关装置及系统 |
WO2021201358A1 (ko) * | 2020-03-31 | 2021-10-07 | 엘지전자 주식회사 | V2x를 위한 보안 정책 처리 방법 및 단말 |
CN114513822B (zh) * | 2017-08-11 | 2024-05-03 | 华为技术有限公司 | 一种路径转换方法、相关装置及系统 |
Families Citing this family (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11553857B1 (en) | 2012-09-25 | 2023-01-17 | Micro Mobio Corporation | System and method for through window personal cloud transmission |
US11877842B1 (en) | 2012-09-25 | 2024-01-23 | Micro Mobio Corporation | Personal cloud with a plurality of modular capabilities |
US11272861B1 (en) * | 2012-09-25 | 2022-03-15 | Micro Mobio Corporation | Personal cloud with a plurality of modular capabilities |
WO2017201741A1 (zh) * | 2016-05-27 | 2017-11-30 | 华为技术有限公司 | 一种切换到中继节点的方法、相关设备及系统 |
WO2019066546A1 (en) * | 2017-09-28 | 2019-04-04 | Lg Electronics Inc. | METHOD AND APPARATUS FOR CONFIGURING A RELEASE CAUSE |
ES2949148T3 (es) * | 2018-07-30 | 2023-09-26 | Nagravision Sarl | Un método para transmitir mensajes entre un dispositivo y un servidor remoto |
CN110944306A (zh) * | 2018-09-25 | 2020-03-31 | 维沃移动通信有限公司 | 一种旁链路的链路释放方法及终端 |
CN111447545A (zh) * | 2018-12-29 | 2020-07-24 | 华为技术有限公司 | 一种通信方法及装置 |
CN111586765B (zh) * | 2019-02-15 | 2023-01-13 | 华为技术有限公司 | 中继通信的方法和装置 |
WO2021035439A1 (en) * | 2019-08-23 | 2021-03-04 | Lenovo (Beijing) Limited | Method and apparatus for core network registration and radio access network notification update |
US11528769B2 (en) * | 2019-12-20 | 2022-12-13 | Qualcomm Incorporated | Unicast link radio link failure detection and management |
EP4154670A1 (en) * | 2020-05-21 | 2023-03-29 | IDAC Holdings, Inc. | Methods and apparatuses directed to non-access stratum procedures in connection with layer 2 relaying |
US11477848B2 (en) * | 2020-06-29 | 2022-10-18 | At&T Intellectual Property I, L.P. | Disseminating alerts or other notifications using ProSe direct discovery signaling |
WO2022139488A1 (ko) * | 2020-12-23 | 2022-06-30 | 엘지전자 주식회사 | 무선 통신 시스템에서 릴레이 단말을 재선택하는 방법 및 장치 |
KR20240040114A (ko) * | 2021-08-05 | 2024-03-27 | 엘지전자 주식회사 | 무선통신시스템에서 path switching 및 측정 보고에 관련된 리모트 ue의 동작 방법. |
US20230082718A1 (en) * | 2021-09-16 | 2023-03-16 | Qualcomm Incorporated | Protocol data unit session management |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140133332A1 (en) * | 2012-11-13 | 2014-05-15 | Lg Electronics Inc. | Method and apparatus of supporting ue relay functions |
US20140269555A1 (en) * | 2013-03-15 | 2014-09-18 | Qualcomm Incorporated | Systems and methods for sharing context information in a neighbor aware network |
WO2015037956A1 (ko) * | 2013-09-15 | 2015-03-19 | 엘지전자 주식회사 | 무선 자원의 용도 변경을 지원하는 무선 통신 시스템에서 불연속 수신 지원 방법 및 이를 위한 장치 |
KR20150100205A (ko) * | 2014-02-25 | 2015-09-02 | 삼성전자주식회사 | 단말 간 직접 통신을 지원하는 무선 통신 시스템에서 단말의 전력 감소 방법 및 장치 |
Family Cites Families (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR100690740B1 (ko) * | 2004-11-24 | 2007-03-09 | 엘지전자 주식회사 | 이동 통신 단말기의 슬립 모드 전환 방법 |
US8005065B2 (en) | 2007-09-11 | 2011-08-23 | Qualcomm Incorporated | Keep-alive for wireless networks |
US9661683B2 (en) | 2008-09-05 | 2017-05-23 | Nokia Solutions And Networks Oy | Use of off period of DRX for direct peer to peer communication in a cell |
US20100124211A1 (en) * | 2008-11-17 | 2010-05-20 | Qualcomm Incorporated | Reducing an occurrence of a voip call on hold from being dropped in ev-do systems |
CN104472007B (zh) * | 2012-08-03 | 2019-04-09 | 英特尔公司 | 不连续接收(drx)重配置 |
US20150296411A1 (en) * | 2012-09-28 | 2015-10-15 | Telefonaktiebolaget L M Ericsson (Publ) | Cellular-Network Based Control of Vehicle-to-Vehicle Communication |
EP2915402B1 (en) * | 2012-11-01 | 2021-07-21 | Interdigital Patent Holdings, Inc. | Method for establishing direct wlan proximity service connectivity |
WO2014129960A1 (en) * | 2013-02-20 | 2014-08-28 | Telefonaktiebolaget L M Ericsson (Publ) | Methods for configuring and performing ul measurements accounting for low-activity state configuration of the transmitting node |
JP6159012B2 (ja) * | 2013-03-20 | 2017-07-05 | エルジー エレクトロニクス インコーポレイティド | 近接サービス提供方法及び装置 |
CN105453627B (zh) | 2013-08-06 | 2019-10-15 | 夏普株式会社 | 终端装置、通信方法以及集成电路 |
CN104796986B (zh) * | 2014-01-16 | 2019-02-19 | 电信科学技术研究院 | 一种d2d通信方法及设备 |
CN104811892B (zh) | 2014-01-29 | 2020-03-13 | 中兴通讯股份有限公司 | 一种资源分配方法、装置及系统 |
US9992744B2 (en) * | 2014-02-24 | 2018-06-05 | Intel Corporation | Mechanisms to optimize and align discontinuous reception configuration of device to-device capable user equipment |
US9661684B2 (en) * | 2014-08-11 | 2017-05-23 | Telefonaktiebolaget L M Ericsson (Publ) | Method of sharing a UE receiver between D2D and cellular operations based on activity |
JP6434616B2 (ja) * | 2014-09-24 | 2018-12-05 | エルジー エレクトロニクス インコーポレイティド | D2d信号の送信方法及びそのための端末 |
US10314094B2 (en) * | 2015-02-26 | 2019-06-04 | Nec Corporation | System and method for data communication |
EP3079436B1 (en) * | 2015-04-10 | 2018-09-19 | Panasonic Intellectual Property Corporation of America | Discontinuous reception operation for licensed-assisted access |
US9942917B2 (en) * | 2015-05-14 | 2018-04-10 | Blackberry Limited | Allocating resources for a device-to-device transmission |
WO2016200184A1 (ko) * | 2015-06-09 | 2016-12-15 | 엘지전자 주식회사 | V2x 통신 시스템에서 단말의 통신 방법 및 단말 |
WO2017204726A1 (en) * | 2016-05-24 | 2017-11-30 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods and apparatus for configuring a discontinuous reception mode in a wireless network |
-
2016
- 2016-10-26 JP JP2018520101A patent/JP6860560B2/ja active Active
- 2016-10-26 WO PCT/KR2016/012071 patent/WO2017074012A1/ko active Application Filing
- 2016-10-26 EP EP16860195.3A patent/EP3370473B1/en active Active
- 2016-10-26 KR KR1020187010457A patent/KR102170107B1/ko active IP Right Grant
- 2016-10-26 US US15/765,640 patent/US10499452B2/en active Active
- 2016-10-26 CN CN201680062507.7A patent/CN108353448B/zh active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140133332A1 (en) * | 2012-11-13 | 2014-05-15 | Lg Electronics Inc. | Method and apparatus of supporting ue relay functions |
US20140269555A1 (en) * | 2013-03-15 | 2014-09-18 | Qualcomm Incorporated | Systems and methods for sharing context information in a neighbor aware network |
WO2015037956A1 (ko) * | 2013-09-15 | 2015-03-19 | 엘지전자 주식회사 | 무선 자원의 용도 변경을 지원하는 무선 통신 시스템에서 불연속 수신 지원 방법 및 이를 위한 장치 |
KR20150100205A (ko) * | 2014-02-25 | 2015-09-02 | 삼성전자주식회사 | 단말 간 직접 통신을 지원하는 무선 통신 시스템에서 단말의 전력 감소 방법 및 장치 |
Non-Patent Citations (1)
Title |
---|
INTEL CORPORATION: "Considerations on UE-to-NW Relay for ProSe", R1-151111, 3GPP TSG RAN WG2 MEETING #89BIS, 11 April 2015 (2015-04-11), Bratislava, Slovakia, XP050936092 * |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111034334A (zh) * | 2017-08-11 | 2020-04-17 | 华为技术有限公司 | 一种路径转换方法、相关装置及系统 |
EP3637940A4 (en) * | 2017-08-11 | 2020-10-14 | Huawei Technologies Co., Ltd. | DISCONNECTING PROCEDURE, APPROPRIATE DEVICE AND SYSTEM |
CN111034334B (zh) * | 2017-08-11 | 2022-01-14 | 华为技术有限公司 | 一种路径转换方法、相关装置及系统 |
CN114513822A (zh) * | 2017-08-11 | 2022-05-17 | 华为技术有限公司 | 一种路径转换方法、相关装置及系统 |
US11419025B2 (en) | 2017-08-11 | 2022-08-16 | Huawei Technologies Co., Ltd. | Path switching method, apparatus and system |
CN114513822B (zh) * | 2017-08-11 | 2024-05-03 | 华为技术有限公司 | 一种路径转换方法、相关装置及系统 |
WO2021201358A1 (ko) * | 2020-03-31 | 2021-10-07 | 엘지전자 주식회사 | V2x를 위한 보안 정책 처리 방법 및 단말 |
Also Published As
Publication number | Publication date |
---|---|
EP3370473B1 (en) | 2021-01-27 |
JP2018535594A (ja) | 2018-11-29 |
JP6860560B2 (ja) | 2021-04-14 |
CN108353448A (zh) | 2018-07-31 |
EP3370473A4 (en) | 2019-07-10 |
US10499452B2 (en) | 2019-12-03 |
KR102170107B1 (ko) | 2020-10-26 |
US20190082495A1 (en) | 2019-03-14 |
EP3370473A1 (en) | 2018-09-05 |
CN108353448B (zh) | 2021-10-22 |
KR20180043379A (ko) | 2018-04-27 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2017074012A1 (ko) | 무선 통신 시스템에서 단말 간의 직접 통신을 방법 및 이를 위한 장치 | |
WO2017069430A1 (ko) | 무선 통신 시스템에서 단말 간의 직접 통신 방법 및 이를 위한 장치 | |
WO2017052335A1 (ko) | 무선 통신 시스템에서 단말 간의 직접 통신을 수행하는 방법 및 이를 위한 장치 | |
WO2018155934A1 (ko) | 무선 통신 시스템에서 3GPP access를 통해 non-3GPP에 관련된 데이터를 수신하는 방법 및 이를 위한 장치 | |
WO2018169343A1 (ko) | 페이징을 수행하는 방법 및 기지국, 페이징을 지원하는 방법 및 네트워크 엔티티 | |
WO2017146523A1 (ko) | 네트워크로의 연결 요청 방법 및 사용자기기 | |
WO2018066919A1 (ko) | 네트워크로의 연결 방법 및 사용자기기 | |
WO2019160376A1 (ko) | 무선 통신 시스템에서 smf의 신호 송수신 방법 및 이를 위한 장치 | |
WO2018199611A1 (ko) | 네트워크로의 등록 요청 전송 방법 및 사용자기기, 그리고 등록 요청 수신 방법 및 네트워크 기기 | |
WO2017043854A1 (ko) | 무선 통신 시스템에서 단말 간의 직접 통신을 지원하는 방법 및 이를 위한 장치 | |
WO2018088812A1 (ko) | 핸드오버 방법 및 사용자기기 | |
WO2017191973A1 (ko) | 무선 통신 시스템에서 리모트 ue의 위치 등록 수행 방법 및 이를 위한 장치 | |
WO2016105004A1 (ko) | 무선 통신 시스템에서 nbifom 캐퍼빌리티를 송수신하는 방법 및 이를 위한 장치 | |
WO2017171427A1 (ko) | 시스템 정보 전송 방법 및 기지국과 시스템 정보 수신 방법 및 사용자기기 | |
WO2018084635A1 (ko) | 무선 통신 시스템에서 ngs에서 eps로 이동 방법 및 이를 위한 장치 | |
WO2017142363A1 (ko) | 서비스 요청 전송 및 사용자기기, 그리고 서비스 요청 수신 및 기지국 | |
WO2018128519A1 (ko) | 무선 통신 시스템에서 리모트 ue와 연결을 가진 릴레이 ue가 네트워크와 연결 수행 방법 및 이를 위한 장치 | |
WO2017086618A1 (ko) | 무선 통신 시스템에서 단말 간의 직접 통신을 방법 및 이를 위한 장치 | |
WO2017007104A1 (ko) | V2x 통신 시스템에서 단말의 통신 방법 및 단말 | |
WO2017135779A1 (ko) | 무선 통신 시스템에서 rrc 연결 재개를 수행하는 방법 및 장치 | |
WO2017126948A1 (ko) | 무선 통신 시스템에서 로컬 네트워크에서 v2x 메시지 송수신 방법 및 이를 위한 장치 | |
WO2015002456A1 (ko) | 근접 서비스를 위해 중계기를 선택 또는 재선택하는 방법 | |
WO2018169281A1 (ko) | 보고 수신 방법 및 네트워크 장치, 그리고 보고 수행 방법 및 기지국 | |
WO2018221943A1 (ko) | 무선 통신 시스템에서 multi-homing 기반 psa 추가와 관련하여 신호를 송수신하는 방법 및 이를 위한 장치 | |
WO2016111603A1 (ko) | 무선 통신 시스템에서 pdn 연결 복구에 관련된 신호 송수신 방법 및 이를 위한 장치 |
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: 16860195 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 20187010457 Country of ref document: KR Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2018520101 Country of ref document: JP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2016860195 Country of ref document: EP |