WO2017171514A1 - Procédé de gestion de connexion d'ue pour l'émission et la réception d'un message v2x dans un système de communication sans fil, et appareil associé - Google Patents

Procédé de gestion de connexion d'ue pour l'émission et la réception d'un message v2x dans un système de communication sans fil, et appareil associé Download PDF

Info

Publication number
WO2017171514A1
WO2017171514A1 PCT/KR2017/003620 KR2017003620W WO2017171514A1 WO 2017171514 A1 WO2017171514 A1 WO 2017171514A1 KR 2017003620 W KR2017003620 W KR 2017003620W WO 2017171514 A1 WO2017171514 A1 WO 2017171514A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
network node
information
enb
network
Prior art date
Application number
PCT/KR2017/003620
Other languages
English (en)
Korean (ko)
Inventor
김래영
김동수
김태훈
Original Assignee
엘지전자 주식회사
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 엘지전자 주식회사 filed Critical 엘지전자 주식회사
Priority to EP17775938.8A priority Critical patent/EP3425993B1/fr
Priority to US16/090,558 priority patent/US11259359B2/en
Publication of WO2017171514A1 publication Critical patent/WO2017171514A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/34—Selective release of ongoing connections
    • 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
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/51—Allocation or scheduling criteria for wireless resources based on terminal or device properties
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/23—Manipulation of direct-mode connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/005—Moving wireless networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices

Definitions

  • the following description relates to a wireless communication system, and more particularly, to a method and apparatus for managing a connection of a UE for transmitting and receiving V2X messages.
  • 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
  • D2D communication establishes a direct link between user equipments (UEs), and directly communicates voice and data between terminals without passing through an evolved NodeB (eNB).
  • UEs user equipments
  • eNB evolved NodeB
  • the D2D communication may include a scheme such as UE-to-UE communication, Peer-to-Peer communication, and the like.
  • the D2D communication scheme may be applied to machine-to-machine (M2M) communication, machine type communication (MTC), and the like.
  • M2M machine-to-machine
  • MTC machine type communication
  • D2D communication has been considered as a way to solve the burden on the base station due to the rapidly increasing data traffic.
  • the D2D communication unlike the conventional wireless communication system, since the data is exchanged between devices without passing through a base station, the network can be overloaded.
  • the D2D communication it is possible to expect the effect of reducing the procedure of the base station, the power consumption of the devices participating in the D2D, increase the data transmission speed, increase the capacity of the network, load balancing, cell coverage expansion.
  • V2X vehicle to everything
  • the present invention provides a method for efficiently managing the connection (connection) of the V2X UEs performing only the PC5 operation.
  • An embodiment of the present invention provides a method for managing a connection of a UE that transmits and receives a V2X message of a first network node in a wireless communication system, wherein the first network node maintains a UE performing only PC5 operation in an ECM_CONNECTED state. Determining; And transmitting, by the first network node, the request to release a portion of a packet data network (PDN) connection to the second network node after the determination.
  • PDN packet data network
  • An embodiment of the present invention provides a first network node device for managing a connection of a UE for transmitting and receiving a V2X message in a wireless communication system, comprising: a transmitting and receiving device; And a processor, wherein the processor determines to keep the UE performing only the PC5 operation in the ECM_CONNECTED state, and transmits the information to the transmitting and receiving apparatus for requesting to release a portion of a packet data network (PDN) connection to a second network node.
  • PDN packet data network
  • Some of the packet data network (PDN) connections may be S1 bearers.
  • the first network node may receive a Release Access Bearers Response message from the second network node that deletes information on the eNB of the UE.
  • the method may further include receiving, by the first network node, an S1 UE context release request message from an eNB that the UE recognizes to perform only PC5 operation.
  • the eNB provides information that the UE intends to receive V2X service, information that the UE intends to perform direct communication, information indicating that the UE is a vehicle UE, information that the UE does not need an S1 bearer, and that the UE It can be appreciated that the UE performs only PC5 operation based on one or more of information indicating that no S1 bearer is used and information that the UE has been authored for V2X service.
  • the first network node may transmit an S1 UE context release command message to the eNB in response to the S1 UE context release request message.
  • the method may further comprise the first network node recognizing that the UE performs only PC5 operation.
  • the first network node may recognize that the UE performs only PC5 operation by receiving an S1 UE status report message from the eNB.
  • the S1 UE status report message may be a message indicating that the UE has requested a PC5 resource.
  • the message indicating that the PC5 resource is requested includes information indicating that the UE is to receive V2X service, information that the UE intends to perform direct communication, information indicating that the UE is a vehicle UE, and the UE is an S1 bearer May be transmitted by the eNB when one or more of information indicating that the UE does not use, information indicating that the UE does not use the S1 bearer, and information indicating that the UE is authored for V2X service.
  • the first network node may transmit an S1 UE context release command message to the eNB in response to the S1 UE status report message.
  • the first network node may be an MME, and the second network node may be a serving gateway (S-GW).
  • S-GW serving gateway
  • the present invention it is possible to efficiently manage the connection of the UE by preventing the occurrence and transmission of unnecessary handover signaling through some release of the PDN connection of the V2X UEs performing only PC5 operation.
  • 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. 8 illustrates an architecture reference model usable in a 5G system.
  • FIG 9 illustrates a possible scenario when the UE is served from one or more network slices.
  • FIG. 10 illustrates V2X message transmission and reception of a V2X UE using PC5.
  • FIG. 13 shows a structure of a PDN connection.
  • 16 is a diagram illustrating a configuration of a node device according to an embodiment of the present invention.
  • 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 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 relation to at least one of the Institute of Electrical and Electronics Engineers (IEEE) 802 series system, 3GPP system, 3GPP LTE and LTE-A system, and 3GPP2 system. That is, steps or parts which are not described to clearly reveal the technical spirit of the present invention among the embodiments of the present invention may be supported by the above documents. In addition, all terms disclosed in the present document can be described by the above standard document.
  • IEEE Institute of Electrical and Electronics Engineers
  • 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 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
  • Non-Access Stratum Upper stratum of the control plane between the UE and the MME.
  • Packet Data Network A network in which a server supporting a specific service (eg, a Multimedia Messaging Service (MMS) server, a Wireless Application Protocol (WAP) server, etc.) is located.
  • a server supporting a specific service eg, a Multimedia Messaging Service (MMS) server, a Wireless Application Protocol (WAP) server, etc.
  • MMS Multimedia Messaging Service
  • WAP Wireless Application Protocol
  • PDN connection A logical connection between the UE and the PDN, represented by one IP address (one IPv4 address and / or one IPv6 prefix).
  • RAN Radio Access Network: a unit including a NodeB, an eNodeB and a Radio Network Controller (RNC) controlling them in a 3GPP network. It exists between UEs and provides a connection to the core network.
  • RNC Radio Network Controller
  • HLR Home Location Register
  • HSS Home Subscriber Server
  • PLMN Public Land Mobile Network
  • Proximity Service (or ProSe Service or Proximity based Service): A service that enables discovery and direct communication between physically close devices or communication through a base station or through a third party device. In this case, user plane data is exchanged through a direct data path without passing through a 3GPP core network (eg, EPC).
  • EPC 3GPP core network
  • EPC Evolved Packet Core
  • 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 an IP service network provided by an operator (ie, an operator) via various elements in the EPC, based on 3GPP access as well as non-3GPP access. (Eg, IMS).
  • FIG. 1 illustrates various reference points (eg, S1-U, S1-MME, etc.).
  • a conceptual link defining two functions existing in different functional entities of E-UTRAN and EPC is defined as a reference point.
  • Table 1 below summarizes the reference points shown in FIG. 1.
  • This reference point can be used in PLMN-to-PLMN-to-PLMN-to-for example (for PLMN-to-PLMN handover).
  • This reference point can be used intra-PLMN or inter-PLMN (eg in the case of Inter-PLMN HO).)
  • S4 Reference point between SGW and SGSN that provides related control and mobility support between the GPRS core and SGW's 3GPP anchor functionality.It also provides user plane tunneling if no direct tunnel is established.
  • 3GPP Anchor function of Serving GW In addition, if Direct Tunnel is not established, it provides the user plane tunnelling.
  • S5 Reference point providing user plane tunneling and tunnel management between the SGW and the PDN GW.
  • 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.
  • an eNodeB can route to a gateway, schedule and send paging messages, schedule and send broadcaster channels (BCHs), and resources in uplink and downlink while an RRC (Radio Resource Control) connection is active.
  • BCHs broadcaster channels
  • RRC Radio Resource Control
  • paging can occur, LTE_IDLE state management, user plane can perform 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 sub-carriers on the frequency axis.
  • one subframe includes a plurality of 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 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 channel multiplexing to map several logical channels to one transport channel. (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 RRC) layer located at the top of the third layer is defined only in the control plane, and the configuration and resetting of radio bearers (abbreviated as RBs) 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.
  • RRC connection If there is an RRC connection (RRC connection) between the RRC of the terminal and the RRC layer of the wireless network, the terminal is in the RRC connected mode (Connected Mode), otherwise it is in the RRC idle mode (Idle Mode).
  • RRC connection If there is an RRC connection (RRC connection) between the RRC of the terminal and the RRC layer of the wireless network, the terminal is in the RRC connected mode (Connected Mode), otherwise it is in the RRC idle mode (Idle Mode).
  • the RRC state refers to whether or not the RRC of the UE is in a logical connection with the RRC of the E-UTRAN. If the RRC state is connected, the RRC_CONNECTED state is called, and the RRC_IDLE state is not connected. Since the UE in the RRC_CONNECTED state has an RRC connection, the E-UTRAN can grasp the existence of the UE in units of cells, and thus can effectively control the UE. On the other hand, the UE in the RRC_IDLE state cannot identify the existence of the UE by the E-UTRAN, and the core network manages the unit in a larger tracking area (TA) unit than the cell.
  • TA tracking area
  • each TA is identified by a tracking area identity (TAI).
  • TAI tracking area identity
  • the terminal may configure a TAI through a tracking area code (TAC), which is information broadcast in a cell.
  • TAC tracking area code
  • the terminal When the user first turns on the power of the terminal, the terminal first searches for an appropriate cell, then establishes an RRC connection in the cell, and registers the terminal's information in the core network. Thereafter, the terminal stays in the RRC_IDLE state. The terminal staying in the RRC_IDLE state (re) selects a cell as needed and looks at system information or paging information. This is called camping on the cell.
  • the UE staying in the RRC_IDLE state makes an RRC connection with the RRC of the E-UTRAN through an RRC connection procedure and transitions to the RRC_CONNECTED state.
  • RRC_CONNECTED state There are several cases in which a UE in RRC_IDLE state needs to establish an RRC connection. For example, a user's call attempt, a data transmission attempt, etc. are required or a paging message is received from E-UTRAN. Reply message transmission, and the like.
  • a non-access stratum (NAS) layer located above the RRC layer performs functions such as session management and mobility management.
  • NAS non-access stratum
  • ESM evolved Session Management
  • the NAS layer performs functions such as default bearer management and dedicated bearer management, and is responsible for controlling the terminal to use the PS service from the network.
  • the default bearer resource is characterized in that it is allocated from the network when it is connected to the network when it first accesses a specific Packet Data Network (PDN).
  • PDN Packet Data Network
  • the network allocates an IP address usable by the terminal so that the terminal can use the data service, and also allocates QoS of the default bearer.
  • LTE supports two types of bearer having a guaranteed bit rate (GBR) QoS characteristic that guarantees a specific bandwidth for data transmission and reception, and a non-GBR bearer having a best effort QoS characteristic without guaranteeing bandwidth.
  • GBR guaranteed bit rate
  • Non-GBR bearer is assigned.
  • the bearer allocated to the terminal in the network is called an evolved packet service (EPS) bearer, and when the EPS bearer is allocated, the network allocates one ID. This is called EPS Bearer ID.
  • EPS bearer ID One EPS bearer has a QoS characteristic of a maximum bit rate (MBR) or / and a guaranteed bit rate (GBR).
  • 5 is a flowchart illustrating a random access procedure in 3GPP LTE.
  • the random access procedure is used for the UE to get 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 the entity of the RRC layer of the eNodeB.
  • the RRC state is called an RRC connected state.
  • the non-state is called the RRC idle mode.
  • the E-UTRAN may determine the existence of the corresponding UE in units of cells, and thus may effectively control the UE.
  • the UE in the idle state can not be identified by the eNodeB, the core network (core network) is managed by the tracking area (Tracking Area) unit larger than the cell unit.
  • the tracking area is a collection unit of cells. That is, the idle state (UE) is determined only in the presence of the UE in a large area, and in order to receive a normal mobile communication service such as voice or data, the UE must transition to the connected state (connected state).
  • the UE When a user first powers up a UE, the UE first searches for an appropriate cell and then stays in an idle state in that cell. When the UE staying in the idle state needs to establish an RRC connection, the UE establishes an RRC connection with the RRC layer of the eNodeB through an RRC connection procedure and transitions to an RRC connected state. .
  • the UE in the idle state needs to establish an RRC connection. For example, a user's call attempt or uplink data transmission is required, or a paging message is received from EUTRAN. In this case, the response message may be transmitted.
  • the RRC connection process is largely a process in which a UE sends an RRC connection request message to an eNodeB, an eNodeB sends an RRC connection setup message to the UE, and a UE completes RRC connection setup to the eNodeB. (RRC connection setup complete) message is sent. This process will be described in more detail with reference to FIG. 6 as follows.
  • the eNB When the RRC connection request message is received from the UE, the eNB accepts the RRC connection request of the UE when the radio resources are sufficient, and transmits an RRC connection setup message, which is a response message, to the UE. .
  • the UE When the UE receives the RRC connection setup message, it transmits an RRC connection setup complete message to the eNodeB. When the UE successfully transmits an RRC connection establishment message, the UE establishes an RRC connection with the eNodeB and transitions to the RRC connected mode.
  • network slicing may include three layers, a service instance layer, a network slice instance layer, and a resource layer.
  • the service instance layer represents the service to be supported (end user service or business service). Each of these services may be represented by a service instance.
  • the service instance may represent an operator service or a third party provided service.
  • Network slice instances provide the network characteristics required for service instances. Network slice instances can be shared among multiple service instances provided by network operators.
  • the UE may be provided with service from one or more network slices as illustrated in FIG.
  • the UE may be provided with services from multiple slices, and may send and receive traffic through several slices at the same time, but may also exchange traffic through only one slice at a time.
  • the UE when Service # 1 is provided with Slice # 1 and Service # 2 is provided with Slice # 2, the UE generates mobile originated (MO) traffic for Service # 1. Can be sent through.
  • MO mobile originated traffic for Service # 1.
  • Another example is when there is no traffic transmitted and received by the UE (in a mobile communication system such as EPS, the UE may be in the IDLE state in this case) and mobile terminated (MT) traffic for Service # 2 occurs. This can be delivered via Slice # 2.
  • MME has been divided into Core Access and Mobility Management Function (AMF) and Session Management Function (SMF) in 5G CN (Core Network).
  • AMF Core Access and Mobility Management Function
  • SMF Session Management Function
  • the NAS interaction and mobility management (MM) with the UE are performed by the AMF, and the session management (SM) is performed by the SMF.
  • the SMF manages a user plane function (UPF), which has a user-plane function, that is, a gateway through which user traffic is routed.
  • the user-plane part can be considered to be in charge of the UPF.
  • a PDU (Protocol Data Unit) session is defined in 5G system.
  • the PDU session refers to an association between the UE and the DN providing the PDU connectivity service of the Ethernet type or the unstructured type as well as the IP type.
  • UDM Unified Data Management
  • PCF Policy Control Function
  • the functions can be provided in an expanded form to satisfy the requirements of the 5G system. For details on the 5G system architecture, each function and each interface, TS 23.501 is applicable.
  • a periodic message type CAM (Cooperative Awareness Message) message, an event triggered message type DENM message, or the like may be transmitted.
  • the CAM may include basic vehicle information such as dynamic state information of the vehicle such as direction and speed, vehicle static data such as dimensions, exterior lighting state, and route details.
  • the size of the CAM message may be 50-300 bytes.
  • the DENM may be a message generated in a sudden situation such as a vehicle breakdown or accident.
  • the size of the DENM can be less than 3000 bytes, and any vehicle within the transmission range can receive the message.
  • the DENM may have a higher priority than the CAM, and in this case, having a high priority may mean transmitting a higher priority when a simultaneous transmission occurs from one UE perspective, or priority among a plurality of messages. May attempt to send a higher message in time priority. In many UEs, a higher priority message may be less interference than a lower priority message, thereby reducing the probability of reception error. In the case of a security overhead, CAM can have a larger message size than otherwise.
  • the message for the V2X service includes a message periodically transmitted by the UE and a message generated by a specific event. See TR 22.885 for use case and characteristics for these messages.
  • ETSI defines various use cases related to ITS and V2X message transmission. Tables 2-3 below are a summary thereof (3GPP S1-150140). See ETSI TS 302 637-2, TS 302 637-3, TR 102 638 for details.
  • ETSI ITS Message Category Message Name Message TypeCAM TX Mode MIN Frequency (Hz) MAX Latency (ms) From To Vehicle type warnings
  • Emergency Vehicle Warning CAM Broadcast 10 100 V V Slow Vehicle Indication CAM Broadcast 2 100 V V Motorcycle Approaching Indication CAM Broadcast 2 100 V V / I Vulnerable road user Warning CAM Broadcast One 100 I / P V Dynamic vehicle warnings Overtaking vehicle warning CAM Broadcast 10 100 V V Lane change assistance CAM Broadcast 10 100 V V Co-operative glare reduction CAM Broadcast 2 100 V V Collision Risk Warning Across traffic turn collision risk warning CAM Broadcast 10 100 V V Merging Traffic Turn Collision Risk Warning CAM Broadcast 10 100 V V Co-operative merging assistance CAM Broadcast 10 100 V V / I Intersection Collision Warning CAM Broadcast 10 100 V V V Traffic light optimal speed advisory CAM Broadcast 2 100 I V Traffic information and recommended itinerary CAM Broadcast 1-10 500 I V Enhanced route guidance and navigation (RSU Capability) CAM Broadcast
  • Reference point V1 is the reference point between the V2X application and the V2X application server.
  • V2 is the reference point between V2X applications and V2X control functions in the carrier network.
  • V2X applications can connect to V2X control functions belonging to multiple PLMNs.
  • V3 is the reference point between the V2X-enabled UE and the V2X control of the operator's network.
  • V4 is the reference point between HSS and V2X control functions in the operator network, and V5 is the reference point between V2X applications.
  • LTE-Uu is a reference point between V2X-enabled UEs and E-UTRAN
  • PC5 is a reference point between V2X-enabled UEs for V2V, V2I and V2P services.
  • FIG. 10 illustrates V2X message transmission and reception of a V2X UE using PC5.
  • FIG. 10 (a) shows a case where the service is provided by the E-UTRAN
  • FIG. 10 (b) shows V2X message transmission and reception through the PC5 when the UE is not provided by the E-UTRAN.
  • V2X message transmission for V2V and V2P services can be done using PC5.
  • the V2X message over PC5 needs to be broadcast so that all UEs supporting V2V and / or V2P services in the vicinity of the V2X message transmitting UE can receive the message regardless of roaming and serving PLMN.
  • 1 to All ProSe Direct Communication is applicable when the UE is served by the E-UTRAN and when the UE is not served by the E-UTRAN.
  • One-to-one all ProSe direct communication features for V2X include:
  • the radio layer provides a user plane communication service for transmitting IP packets between UEs in direct communication.
  • IPv6 is used for IP packet transmission of V2X messages.
  • Each UE has a layer 2 ID for all ProSe Direct Communication included in the source layer 2 ID field of every frame transmitted through the layer 2 link.
  • the UE assigns itself a Layer-2 ID for 1 to All ProSe Direct Communication.
  • the UE automatically configures link-local IPv6 addresses according to the procedure defined in RFC 4862. This address can be used as the source IP address for 1 to All ProSe Direct Communication.
  • the source Layer-2 ID and source IP address can change over time to prevent the vehicle from being tracked or identified by vehicles other than the short time required by the application.
  • the UE In order to perform one-to-one All ProSe Direct Communication, the UE sets up relevant information on one-to-one All ProSe Direct Communication.
  • the one-to-many ProSe direct communication transfer procedure described in section 5.4.2 of TS 23.303 is a one-to-all ProSe direct communication for V2X message transfer for V2V / P services using PC5 with the following differences: Applies to
  • the source Layer-2 ID is set to the Layer-2 ID described above.
  • the destination IP address and destination Layer-2 ID are set to a well-known broadcast IP address and a well-known Layer-2 ID, respectively.
  • the one-to-many ProSe direct communication reception procedure described in Section 5.4.3 of TS 23.303 applies to one-to-one ProSe Direct Communication for V2X message reception for V2V / P services using PC5.
  • a UE operating in mode 1 When a UE operating in mode 1 (ie, scheduled resource allocation) performs a PC5 operation, it sends a Buffer Status Report (BSR) to the eNB in order to receive PC5 resources from the eNB.
  • BSR Buffer Status Report
  • the UE must maintain the RRC_CONNECTED state (ie, ECM_CONNECTED state) while using the scheduled resource allocation scheme.
  • RRC_CONNECTED state ie, ECM_CONNECTED state
  • TS 36.300 TS 36.321, etc. for details.
  • For V2X communication direct or sidelink communication with a scheduled resource allocation scheme similar to mode 1, called mode 3, is defined (see Section 23.14.1.1 (Support for V2X sidelink communication) of TS 36.300).
  • the UE in a scheduled resource allocation scheme (mode 3 sidelink communication), the UE should be in RRC_CONNECTED state for data transmission.
  • the UE requests transmission resources from the eNB, and the eNB schedules transmission resources necessary for sidelink control information and data transmission of the UE.
  • the UE selects a resource from resource pools and transmits sidelink control information and data. If mapping of V2X sidelink transmission resource pools and zones information is configured, the UE selects a V2X sidelink resource pool based on the zone in which it is located.
  • the UE must maintain the RRC_CONNECTED state (ie, ECM_CONNECTED state) while using the scheduled resource allocation scheme of mode 3. This is because the UE needs to request the PC5 resource for sidelink transmission from the eNB to operate in mode 3.
  • the UE needs to send a Buffer Status Report (BSR) to the eNB in order to be allocated PC5 resources from the eNB.
  • BSR Buffer Status Report
  • FIG. 11 shows a sidelink BSR.
  • Section 6.1.3.1a Segment BSR MAC Control Elements
  • a UE forms a PDN connection when transmitting and receiving data through a network
  • the PDN connection is actually a data radio bearer s between the UE and the eNB, and an S1 bearer s between the eNB and the S-GW (ie, S1-U tunnel), and the S5 bearer (s) between the S-GW and the P-GW (i.e., two GWs belong to the same PLMN as the S5 tunnel) or S8 bearer (s) (i.e., two GWs differ from each other by the S8 tunnel). Belonging to a PLMN). If a handover occurs, the UE must not only generate a new DRB (s) with the target eNB, but also need to newly generate the S-GW and the S1 bearer (s).
  • connection management method of a UE for transmitting / receiving a V2X message will be described based on the above description.
  • the following description focuses on the first network node (network node / function performing MME function in MME or 5G) and the second network node (node / function performing SGW function in SGW or 5G).
  • the first network node may determine to keep the UE performing only the PC5 operation in the ECM_CONNECTED state, and thereafter, may transmit information requesting to release some of the packet data network (PDN) connections to the second network node.
  • Some of the packet data network (PDN) connections are S1 bearers.
  • the UE when the UE performs only the PC5 operation, the UE decides to keep the UE in the ECM_CONNECTED state and requests the release of the S1 bearer from the second network node.
  • the above-described PC5 message transmission and reception may be performed to prevent a congestion situation in which numerous V2X UEs that do not need S1-U management transmit and receive signaling related to handover.
  • the information requesting to release some of the PDN connections may be a Release Access Bearers Request message.
  • the first network node After transmitting the Release Access Bearers Request message, the first network node receives a Release Access Bearers Response message from the second network node that deletes information on the eNB of the UE. That is, upon receiving the Release Access Bearers Request message, the second network node deletes the context for the eNB of the UE to release the S1 bearer.
  • the eNB or the MME may recognize that the UE performs only the PC5 operation.
  • the eNB informs that the UE intends to receive V2X service, information that the UE intends to perform direct communication, information indicating that the UE is a vehicle UE. Based on one or more of information obtained from the UE, such as information that the UE does not need an S1 bearer, information that the UE does not use the S1 bearer, and information that the UE has been authored for V2X service. Recognizes to perform only PC5 operations.
  • the time point at which the MME provides information to the eNB may be when the UE performs an operation such as Attach, TAU, Service Request, and the like.
  • the first network node receives the S1 UE context release request message from the eNB that recognizes that the UE performs only the PC5 operation.
  • the first network node After receiving the Release Access Bearers Response message from the second network node, the first network node transmits an S1 UE context release command message to the eNB in response to the S1 UE context release request message. Additional details and specific details not mentioned in this regard will be described later in Example 1-1.
  • the first network node i.e., the MME
  • the first network node may recognize that the UE performs only PC5 operation by receiving an S1 UE status report message from the eNB.
  • the S1 UE status report message is a message indicating that the UE has requested a PC5 resource.
  • the message indicating that the PC5 resource has been requested includes information indicating that the UE intends to receive V2X service, information that the UE intends to perform direct communication, information indicating that the UE is a vehicle UE, information that the UE does not need an S1 bearer, If the UE corresponds to one or more of information obtained from the UE, such as information that the UE does not use the S1 bearer, and information obtained from the MME, such as information that the UE is authored for V2X service, the eNB transmits the information.
  • the time point at which the MME provides information to the eNB may be when the UE performs an operation such as Attach, TAU, Service Request, and the like.
  • the first network node After receiving the Release Access Bearers Response message from the second network node, the first network node transmits an S1 UE context release command message to the eNB in response to the S1 UE status report message.
  • Embodiment 1-1 relates to a case where the eNB recognizes that the UE performs only PC5 operation.
  • a UE transmits a BSR to an eNB to be allocated a PC5 resource. This may be because the UE operates in mode 3.
  • step S1402 the eNB recognizes that the UE performs only PC5 operation. This may be interpreted as recognizing that the UE no longer needs to perform service over the network, that is, traffic transmission / reception over the network. This may be interpreted as recognizing that an S1 bearer for the UE (which is specifically an S1-U bearer) and / or a Data Radio bearer is no longer needed. Such recognition may be based on one or more of the following i), ii) information.
  • Information obtained from the UE this can be obtained, for example, in step S1401.
  • Such information may be information such that the UE wants to receive V2X service, the UE intends to perform direct communication, the UE is a vehicle UE, or does not need / not use an S1 bearer.
  • Information obtained from the MME This can be obtained from the MME, for example, when the UE performs an operation such as Attach, TAU, or Service Request. This information may be information that the UE is authorized for the V2X service.
  • the eNB sends a message requesting to release the S1 bearer to the MME.
  • This may be used by extending the conventional S1 message as shown (S1 UE context release request message), or may define and use a new S1 message.
  • the message is a message for releasing only the S1 bearer between the S-GW and the eNB and maintaining the UE in the ECM_CONNECTED state.
  • the conventional S1 message when the conventional S1 message is used, information for achieving the above object may be explicitly or implicitly included.
  • the message itself may indicate the purpose, or else it may explicitly or implicitly include information to achieve the purpose.
  • Step S1402 may be performed before or after the eNB allocates PC5 resources to the UE.
  • step S1403 the MME determines to keep the UE in the ECM_CONNECTED state.
  • a release Access bearers Request message is transmitted to the S-GW to release the S1 bearer.
  • the message may be used as it is, or may include information indicating that the UE is in the ECM_CONNECTED state or the S1 bearer is released.
  • step S1404 the S-GW deletes information about the eNB.
  • the release access bearers response message is transmitted to the MME.
  • step S1405 the MME sends a response message for step S1402 to the eNB.
  • This may be used by extending the conventional S1 message as shown (S1 UE context release command message), or may define and use a new S1 message.
  • the message is for the purpose of responding to the request received from the eNB through step S1402.
  • the conventional S1 message when used, information for achieving the above object may be explicitly or implicitly included.
  • the message itself may indicate the purpose, or else it may explicitly or implicitly include information to achieve the purpose.
  • step S1406 the eNB may perform an operation of releasing a Data Radio Bearer (DRB) to the UE. (This action may be an optional action)
  • DRB Data Radio Bearer
  • step S1407 the eNB may send a confirm message for step S1405 to the MME. (This action may be an optional action)
  • This may be used by extending the conventional S1 message as shown, or may be used to define a new S1 message.
  • the message is for confirming a response received from the MME through step S1405.
  • information for achieving the above object may be explicitly or implicitly included.
  • the message itself may indicate the purpose, or else it may explicitly or implicitly include information to achieve the purpose.
  • Embodiments 1-2 relate to the case where the MME recognizes that the UE performs only PC5 operation.
  • a UE transmits a BSR to an eNB to be allocated a PC5 resource. This may be because the UE operates in mode 3.
  • step S1502 the eNB sends a message (eg, (S1 UE status report message)) indicating that the UE has requested the PC5 resource to the MME.
  • a message eg, (S1 UE status report message)
  • the eNB sends a message (eg, (S1 UE status report message)) indicating that the UE has requested the PC5 resource to the MME.
  • a message eg, (S1 UE status report message)
  • iii) may be used as a reason for determining the transmission of such a message.
  • Information obtained from the UE this can be obtained, for example, in step S1501.
  • Such information may be information such that the UE wants to receive V2X service, the UE intends to perform direct communication, the UE is a vehicle UE, or does not need / not use an S1 bearer.
  • Information obtained from the MME This can be obtained from the MME, for example, when the UE performs an operation such as Attach, TAU, or Service Request. This information may be information that the UE is authorized for the V2X service. And / or the MME requested the eNB to report when the UE requests the PC5 resource.
  • the message transmitted to the MME may be used by defining a new S1 message as shown (S1 UE status report message), or may be used by extending a conventional S1 message.
  • Step S1502 may be performed before or after the eNB allocates PC5 resources to the UE.
  • step S1503 the MME recognizes that the UE performs only PC5 operation. This may be interpreted as recognizing that the UE no longer needs to perform service over the network, that is, traffic transmission / reception over the network. This may be interpreted as recognizing that an S1 bearer for the UE (which is specifically an S1-U bearer) and / or a Data Radio bearer is no longer needed.
  • the MME determines to keep the UE in the ECM_CONNECTED state.
  • a release Access bearers Request message is transmitted to the S-GW to release the S1 bearer.
  • the message may be used as it is, or may include information indicating that the UE is in the ECM_CONNECTED state or the S1 bearer is released.
  • step S1504 the S-GW deletes information about the eNB.
  • the release access bearers response message is transmitted to the MME.
  • step S1505 the MME requests the eNB to release the S1 bearer or transmits a message indicating that the S1 bearer is released.
  • This may be used by extending the conventional S1 message as shown (S1 UE context release command message), or may define and use a new S1 message.
  • the message is for the purpose of informing the eNB that the UE remains in the ECM_CONNECTED state (or RRC_CONNECTED state) but the S1 bearer is released. And / or requesting the eNB to release the DRB.
  • the conventional S1 message when the conventional S1 message is used, information for achieving the above object may be explicitly or implicitly included.
  • the message itself may indicate the purpose, or else it may explicitly or implicitly include information to achieve the purpose.
  • step S1506 the eNB may perform an operation of releasing a DRB to the UE. (This action may be an optional action)
  • step S1507 the eNB sends a response message for step S1505 to the MME.
  • This may be used by extending the conventional S1 message as shown, or may be used to define a new S1 message.
  • the message is for the purpose of responding to the request received from the MME in step S1505.
  • information for achieving the above object may be explicitly or implicitly included.
  • the message itself may indicate the purpose, or else it may explicitly or implicitly include information to achieve the purpose.
  • Embodiments 1-3 are the same as in Embodiments 1-1 except that the UE transmits a Sidelink UE Information message instead of transmitting the BSR in step S1401.
  • a Sidelink UE Information message instead of transmitting a Sidelink UE Information message, an RRC message or a MAC message defined for the present invention may be transmitted.
  • Embodiment 1-4 is the same as Embodiment 1-2, except that in step S1501, the UE transmits a Sidelink UE Information message instead of transmitting a BSR.
  • a Sidelink UE Information message instead of transmitting a Sidelink UE Information message, an RRC message or a MAC message defined for the present invention may be transmitted.
  • 16 is a diagram showing the configuration of a preferred embodiment of a terminal device and a network node device according to an example of the present invention.
  • 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.
  • 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 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 processor 120 may be configured to perform a terminal operation proposed in the present invention.
  • 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 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 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 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 processor 220 may be configured to perform the network node operation proposed in the present invention. Specifically, the processor 220 determines that the processor keeps the UE performing only the PC5 operation in the ECM_CONNECTED state, and transmits and receives information requesting to release a portion of a packet data network (PDN) connection to a second network node. Can be sent via the device.
  • PDN packet data network
  • the specific configuration of the terminal device 100 and the network device 200 as described above may be implemented so that the above-described matters described in various embodiments of the present invention can be applied independently or two or more embodiments are applied at the same time, overlapping The description is omitted for clarity.
  • Embodiments of the present invention described above may be implemented through various means.
  • embodiments of the present invention may be implemented by hardware, firmware, software, or a combination thereof.
  • a method according to embodiments of the present invention may include one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), and Programmable Logic Devices (PLDs). It may be implemented by field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, and the like.
  • ASICs Application Specific Integrated Circuits
  • DSPs Digital Signal Processors
  • DSPDs Digital Signal Processing Devices
  • PLDs Programmable Logic Devices
  • FPGAs field programmable gate arrays
  • processors controllers, microcontrollers, microprocessors, and the like.
  • the method according to the embodiments of the present invention may be implemented in the form of an apparatus, procedure, or function for performing the functions or operations described above.
  • the software code may be stored in a memory unit and driven by a processor.
  • the memory unit may be located inside or outside the processor, and may exchange data with the processor by various known means.

Landscapes

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

Abstract

L'invention concerne, dans un mode de réalisation, un procédé de gestion d'une connexion d'un UE pour l'émission et la réception d'un message V2X d'un premier noeud de réseau dans un système de communication sans fil. Le procédé consiste: à permettre à un premier noeud de réseau de déterminer qu'un UE utilisé pour effectuer uniquement une opération PC5 sera maintenu dans l'état ECM_CONNECTED; et, après cette détermination, à permettre au premier noeud de réseau de transmettre à un second noeud de réseau des informations demandant la libération d'une partie d'une connexion de réseau de données par paquets (PDN).
PCT/KR2017/003620 2016-04-01 2017-04-03 Procédé de gestion de connexion d'ue pour l'émission et la réception d'un message v2x dans un système de communication sans fil, et appareil associé WO2017171514A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP17775938.8A EP3425993B1 (fr) 2016-04-01 2017-04-03 Procédé de gestion de connexion d'ue pour l'émission et la réception d'un message v2x dans un système de communication sans fil, et appareil associé
US16/090,558 US11259359B2 (en) 2016-04-01 2017-04-03 Method for managing connection of UE for transmitting and receiving V2X message in wireless communication system, and apparatus therefor

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201662316588P 2016-04-01 2016-04-01
US62/316,588 2016-04-01
US201662317653P 2016-04-04 2016-04-04
US62/317,653 2016-04-04

Publications (1)

Publication Number Publication Date
WO2017171514A1 true WO2017171514A1 (fr) 2017-10-05

Family

ID=59966057

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2017/003620 WO2017171514A1 (fr) 2016-04-01 2017-04-03 Procédé de gestion de connexion d'ue pour l'émission et la réception d'un message v2x dans un système de communication sans fil, et appareil associé

Country Status (3)

Country Link
US (1) US11259359B2 (fr)
EP (1) EP3425993B1 (fr)
WO (1) WO2017171514A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3474625A1 (fr) * 2017-10-20 2019-04-24 Comcast Cable Communications LLC Informations de capacité de strate de non-accès
WO2019083340A1 (fr) * 2017-10-27 2019-05-02 엘지전자 주식회사 Procédé de transmission de message dans un système de communication sans fil, et appareil correspondant
WO2020171534A1 (fr) * 2019-02-19 2020-08-27 삼성전자 주식회사 Procédé et dispositif d'identification d'un terminal pour une transmission de message dans un système de communications mobiles
US10938583B2 (en) 2017-10-09 2021-03-02 Comcast Cable Communications, Llc Ethernet type packet data unit session communications
US11432215B2 (en) 2017-10-17 2022-08-30 Telefonaktiebolaget Lm Ericsson (Publ) PDN and PDU session type mapping and capability discovery

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2555784A (en) * 2016-11-04 2018-05-16 Nec Corp Communication system
CN110859005B (zh) * 2018-08-23 2023-04-21 华为技术有限公司 一种通信方法及相关设备
CN111436160B (zh) * 2019-01-15 2022-04-29 华为技术有限公司 一种局域网通信方法、装置及系统
US20220210624A1 (en) * 2019-02-13 2022-06-30 Nokia Technologies Oy Service based architecture management
CN111010745B (zh) * 2020-01-06 2021-11-05 杭州迪普信息技术有限公司 控制隧道处理方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150105089A1 (en) * 2012-06-28 2015-04-16 Huawei Technologies Co., Ltd. Downlink Data Transmission Method, Base Station, and Serving Gateway on LTE Network
US20150327327A1 (en) * 2014-05-08 2015-11-12 Puneet Jain Mobility management entity, user equipment and methods for machine type communication
WO2016035987A1 (fr) * 2014-09-04 2016-03-10 Lg Electronics Inc. Procédé pour configurer un nouveau temporisateur de rapport d'état de mémoire tampon de prohibition dans un système de communication d2d, et dispositif associé

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9131424B2 (en) * 2011-03-25 2015-09-08 Lg Electronics Inc. Method and apparatus for releasing user equipment context in wireless communication system
GB2496153B (en) * 2011-11-02 2014-07-02 Broadcom Corp Device-to-device communications
US9516691B2 (en) * 2012-01-16 2016-12-06 Lg Electronics Inc. Method and apparatus for providing proximity service in wireless communication system
US9609680B2 (en) * 2014-03-18 2017-03-28 Qualcomm Incorporated Signaling flows and buffer status report for a group in device-to-device broadcast communication
JP2018523322A (ja) * 2015-06-24 2018-08-16 インテル アイピー コーポレーション Ｖｅｈｉｃｌｅ‐ｔｏ‐ａｎｙｔｈｉｎｇ（ｖ２ｘ）通信の拡張サポート
EP3314959B1 (fr) * 2015-06-25 2020-05-13 INTEL Corporation Enregistrement pour des communications de véhicule sans fil
US20170150490A1 (en) * 2015-11-19 2017-05-25 Asustek Computer Inc. Method and apparatus for switching communication interface in a wireless communication system
WO2017173072A1 (fr) * 2016-03-30 2017-10-05 Interdigital Patent Holdings, Inc. Procédé et unité sans fil pour une communication de véhicule à infrastructure routière (v2x)

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150105089A1 (en) * 2012-06-28 2015-04-16 Huawei Technologies Co., Ltd. Downlink Data Transmission Method, Base Station, and Serving Gateway on LTE Network
US20150327327A1 (en) * 2014-05-08 2015-11-12 Puneet Jain Mobility management entity, user equipment and methods for machine type communication
WO2016035987A1 (fr) * 2014-09-04 2016-03-10 Lg Electronics Inc. Procédé pour configurer un nouveau temporisateur de rapport d'état de mémoire tampon de prohibition dans un système de communication d2d, et dispositif associé

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI: "Introduction of NB-IomicronT", R2-162068, 3GPP TSG-RAN WG2 MEETING #9 3, 7 March 2016 (2016-03-07), St. Julian's, Malta, pages 1 - 289, XP051081859 *
See also references of EP3425993A4 *
ZAYAS, ALMUDENA DIAZ ET AL.: "Third-Generation Partnership Project Standards: for Delivery of Critical Communications for Railways", IEEE VEHICULAR TECHNOLOGY MAGAZINE, vol. 9, no. 2, 2 May 2014 (2014-05-02), pages 58 - 68, XP011549834 *

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10938583B2 (en) 2017-10-09 2021-03-02 Comcast Cable Communications, Llc Ethernet type packet data unit session communications
US11743061B2 (en) 2017-10-09 2023-08-29 Comcast Cable Communications, Llc Ethernet type packet data unit session communications
US10951427B2 (en) 2017-10-09 2021-03-16 Comcast Cable Communications, Llc Ethernet type packet data unit session communications
US11849364B2 (en) 2017-10-17 2023-12-19 Telefonaktiebolaget Lm Ericsson (Publ) PDN and PDU session type mapping and capability discovery
US11432215B2 (en) 2017-10-17 2022-08-30 Telefonaktiebolaget Lm Ericsson (Publ) PDN and PDU session type mapping and capability discovery
US10812629B2 (en) 2017-10-20 2020-10-20 Comcast Cable Communications, Llc Radio resource control capability information
US10855814B2 (en) 2017-10-20 2020-12-01 Comcast Cable Communications, Llc Non-access stratum capability information
EP4024826A1 (fr) * 2017-10-20 2022-07-06 Comcast Cable Communications, LLC Informations de capacité de strate de non-accès
EP3474625A1 (fr) * 2017-10-20 2019-04-24 Comcast Cable Communications LLC Informations de capacité de strate de non-accès
US11582330B2 (en) 2017-10-20 2023-02-14 Comcast Cable Communications, Llc Wireless device capability information
US11849009B2 (en) 2017-10-20 2023-12-19 Comcast Cable Communications, Llc Wireless device capability information
WO2019083340A1 (fr) * 2017-10-27 2019-05-02 엘지전자 주식회사 Procédé de transmission de message dans un système de communication sans fil, et appareil correspondant
WO2020171534A1 (fr) * 2019-02-19 2020-08-27 삼성전자 주식회사 Procédé et dispositif d'identification d'un terminal pour une transmission de message dans un système de communications mobiles

Also Published As

Publication number Publication date
EP3425993B1 (fr) 2020-09-02
US11259359B2 (en) 2022-02-22
EP3425993A1 (fr) 2019-01-09
US20200396791A1 (en) 2020-12-17
EP3425993A4 (fr) 2019-09-04

Similar Documents

Publication Publication Date Title
WO2017171514A1 (fr) Procédé de gestion de connexion d'ue pour l'émission et la réception d'un message v2x dans un système de communication sans fil, et appareil associé
WO2017030348A1 (fr) Procédé d'émission et de réception de message véhicule à tout (v2x) dans un système de communication sans fil, et appareil associé
WO2017142362A1 (fr) Procédé d'émission/réception de message associé à l'enregistrement de position dans un système de communication sans fil et appareil approprié
WO2017126948A1 (fr) Procédé d'émission et de réception de message véhicule à tout (v2x) dans un réseau local au sein d'un système de communication sans fil et appareil associé
WO2019160376A1 (fr) Procédé d'émission et de réception de signal par smf dans un système de communication sans fil et dispositif associé
WO2018084635A1 (fr) Procédé de passage d'un ngs à un eps dans un système de communication sans fil et appareil associé
WO2017191973A1 (fr) Procédé pour réaliser un enregistrement de localisation par l'intermédiaire d'un ue à distance dans un système de communication sans fil, et appareil associé
WO2018155934A1 (fr) Procédé de réception de données relatives à un accès non-3gpp par l'intermédiaire d'un accès 3gpp dans un système de communication sans fil, et dispositif associé
WO2016144147A1 (fr) Procédé de communication d'équipement d'utilisateur installé dans un véhicule dans un système de communication v2x et équipement d'utilisateur
WO2016190672A1 (fr) Procédé et terminal d'exécution d'une procédure de rattachement pour une connectivité sponsorisée dans un système de communications sans fil
WO2017052335A1 (fr) Procédé de réalisation d'une communication directe de dispositif à dispositif dans un système de communication sans fil et dispositif associé
WO2016024773A1 (fr) Procédé et dispositif de sélection de relais dans un système de communication sans fil
WO2016200184A1 (fr) Procédé de communication destiné à un équipement utilisateur dans un système de communication v2x, et équipement utilisateur
WO2015174702A1 (fr) Procédé et appareil pour une émission et une réception de signal de hss/mme dans un système de communication sans fil
WO2019022442A9 (fr) Procédé de prise en charge de transmission de sms pour un équipement d'utilisateur pouvant recevoir un service à partir d'un système 5g 3gpp et d'eps dans un système de communication sans fil, et appareil associé
WO2017026872A1 (fr) Procédé de transmission et de réception de signal par ue à distance dans un système de communication sans fil et dispositif associé
WO2017086618A1 (fr) Procédé de communication directe de dispositif à dispositif dans un système de communication sans fil et dispositif correspondant
WO2016153327A2 (fr) Procédé de réception et de transmission d'un signal lié à un psm sans tau dans un système de communication sans fil, et appareil associé
WO2018008922A2 (fr) Procédé permettant de prendre en charge une signalisation nas par une station de base dans un système de communication sans fil, et appareil s'y rapportant
WO2016111603A1 (fr) Procédé de transmission et de réception de signaux associés à une récupération de connexion pdn dans un système de communication sans fil, et dispositif associé
WO2016056815A1 (fr) Procédé d'émission/réception d'un signal relatif à une mobilité nbifom dans un système de communication sans fil, et appareil associé
WO2017023129A1 (fr) Procédé de communication utilisant des informations de contexte de terminal dans un système de communication sans fil, et station de base
WO2016163635A1 (fr) Procédé de sélection d'un plmn d'un terminal dans un système de communication sans fil, et appareil associé
WO2018009025A1 (fr) Procédé permettant de transmettre et de recevoir des signaux se rapportant à une connexion au réseau de données par paquets (pdn) dans un système de communication sans fil et dispositif s'y rapportant
WO2016003199A1 (fr) Procédé de réalisation d'une communication d2d dans un système de communication sans fil et dispositif associé

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2017775938

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2017775938

Country of ref document: EP

Effective date: 20181004

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17775938

Country of ref document: EP

Kind code of ref document: A1