WO2016072742A1 - Procédé de transmission et réception de signal associé à une nbifom dans un système de communication sans fil, et dispositif associé - Google Patents

Procédé de transmission et réception de signal associé à une nbifom dans un système de communication sans fil, et dispositif associé Download PDF

Info

Publication number
WO2016072742A1
WO2016072742A1 PCT/KR2015/011791 KR2015011791W WO2016072742A1 WO 2016072742 A1 WO2016072742 A1 WO 2016072742A1 KR 2015011791 W KR2015011791 W KR 2015011791W WO 2016072742 A1 WO2016072742 A1 WO 2016072742A1
Authority
WO
WIPO (PCT)
Prior art keywords
access
type access
nbifom
type
network
Prior art date
Application number
PCT/KR2015/011791
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 엘지전자 주식회사
Publication of WO2016072742A1 publication Critical patent/WO2016072742A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions

Definitions

  • the following description relates to a wireless communication system, and more particularly, to a method and apparatus for transmitting and receiving signals related to network based IP flow mobility (NBIFOM).
  • NBIFOM network based IP flow mobility
  • Wireless communication systems are widely deployed to provide various kinds of communication services such as voice and data.
  • a wireless communication system is a multiple access system capable of supporting communication with multiple users by sharing available system resources (bandwidth, transmission power, etc.).
  • multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, and single carrier frequency (SC-FDMA).
  • CDMA code division multiple access
  • FDMA frequency division multiple access
  • TDMA time division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single carrier frequency division multiple access
  • MCD division multiple access
  • MCDMA multi-carrier frequency division multiple access
  • MC-FDMA multi-carrier frequency division multiple access
  • the present invention proposes a mechanism for efficiently providing IP flow mobility between a 3GPP access network and a WLAN access network in a mobile communication system such as a 3GPP EPS (Evolved Packet System).
  • 3GPP EPS Evolved Packet System
  • a method for transmitting / receiving a signal related to NBIFOM (network based IP flow mobility) of a terminal in a wireless communication system receiving a redirect packet in which a time to live (TTL) is set to 1 through a second type access Doing; And determining whether to change a first type access to the second type access, wherein if it is determined to reject the change of the first type access to the second type access, P- over the first type access.
  • a predetermined message is transmitted to a packet data network-gateway (GW), and the predetermined message is a NBIFOM related signal transmission / reception method including the cause of rejection.
  • GW packet data network-gateway
  • the reasons for the rejection are 3GPP access loss, WLAN access loss, low signal strength of 3GPP access, low signal strength of WLAN access, rule conflict, forbidden access, usage exceeded ( usage exceeded).
  • the reason information of the rejection may be transmitted on a field next to the checksum field of the message.
  • the predetermined message may be an Internet Control Message Protocol (ICMP).
  • ICMP Internet Control Message Protocol
  • the ICMP may have a type value of 11.
  • the packet may be transmitted to the P-GW through the second type access.
  • the first type access and the second type access may be one of a 3GPP access and a WLAN access, and the first type access and the second type access may be different from each other.
  • a packet data network-gateway (P-GW) related to network based IP flow mobility (NBIFOM) in a wireless communication system TTL (Time To Live) through a second type access
  • P-GW packet data network-gateway
  • N Network based IP flow mobility
  • Receiving a redirect packet with N 1 set to 1;
  • a predetermined message is transmitted, wherein the predetermined message is a NBIFOM related signal transmission / reception method including the cause of rejection (cause) information.
  • the reasons for the rejection are 3GPP access loss, WLAN access loss, low signal strength of 3GPP access, low signal strength of WLAN access, rule conflict, forbidden access, usage exceeded ( usage exceeded).
  • the reason information of the rejection may be transmitted on a field next to the checksum field of the message.
  • the predetermined message may be an Internet Control Message Protocol (ICMP).
  • ICMP Internet Control Message Protocol
  • the ICMP may have a type value of 11.
  • the packet may be transmitted to the terminal through the second type access.
  • the first type access and the second type access may be one of a 3GPP access and a WLAN access, and the first type access and the second type access may be different from each other.
  • 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
  • 7 and 8 are examples of a structure in which a WLAN is connected to an EPC.
  • 9 is an exemplary view showing an example of IFOM technology.
  • 10 (a) and 10 (b) show a network control entity for access network selection.
  • 11 to 12 are diagrams for explaining an embodiment of the present invention.
  • FIG. 13 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) / 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
  • 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
  • -ANDSF Access Network Discovery and Selection Function: Provides a policy that enables a terminal to discover and select available access as a network entity.
  • ISRP Inter-System Routing Policy
  • IFOM IP Flow Mobility
  • MAPCON Multi Access PDN Connectivity
  • NSWO non-seamless WLAN offload
  • IP Flow Mobility (IFOM) rule This rule prioritizes the access technology / access networks that should be used by the UE when it is able to route traffic that matches a particular IP traffic filter on a particular APN or any APN. It's a list. In addition, this rule may specify for which wireless access the traffic that matches a particular IP traffic filter on a particular APN or any APN is restricted.
  • IOM IP Flow Mobility
  • MAPCON Multi Access PDN Connectivity
  • This rule is a list of prioritized access technologies / access networks that should be used by the UE when it is possible to route PDN connections to a particular APN.
  • this rule may specify to which radio access the PDN connection to a particular APN should be restricted.
  • Non-seamless WLAN offload (NSWO) rule This rule specifies which traffic should be bypassed to the WLAN or not.
  • ISMP Inter-System Mobility Policy: A set of rules defined by an operator to influence intersystem mobility decisions performed by a UE. When the UE can route IP traffic on a single radio access interface, the UE can use ISMP to select the most appropriate access technology type or access network at a given time.
  • RAN rule A rule received from the network, also called Radio Access Network (RAN) support information.
  • the RAN rule is also referred to as WLAN interworking supported by the RAN used without ANDSF ISRP / ISMP.
  • the AS (Access Stratum) layer of the UE carries the move-traffic-to-WLAN indication and WLAN identifier together to the upper layer of the UE.
  • the AS (Access Stratum) layer of the UE delivers the move-traffic-from-WLAN indication and the WLAN identifier together to the upper layer of the UE.
  • TS 23.401 For a detailed description of the RAN rule, refer to 3GPP TS 23.401, TS 23.060, TS 23.402, TS 36.300, TS 36.304, TS 36.331, TS 25.304 and TS 25.331.
  • Local Operating Environment Information This is a set of implementation specific parameters which describe the local environment in which the UE is operating.
  • NBIFOM Network-Based IP Flow Mobility
  • NBIFOM UE-initiated NBIFOM in which UE initiates IP flow mobility
  • NBIFOM Network-initiated NBIFOM
  • Multi-access PDN connection PDN connection through which traffic can be routed via 3GPP access or WLAN access or both accesses. However, each IP flow is only routed through one access at a time.
  • Routing filter A set of IP header parameter values / ranges of a packet flow used to identify an IP flow for routing purposes.
  • Routing access type A type of access (3GPP access or WLAN access) that routes a set of IP flows of a PDN connection.
  • Routing Rule A set of information that enables the association of routing filters with routing access types.
  • -ICMP Internet Control Message Protocol
  • 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-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. It is the reference point between the PDN GW and the packet data network.
  • Packet data network may be an operator external public or private packet data network or an intra operator packet data network, eg for provision of IMS services.This reference point corresponds to Gi for 3GPP accesses.
  • S2a and S2b correspond to non-3GPP interfaces.
  • S2a is a reference point that provides the user plane with associated control and mobility support between trusted non-3GPP access and PDN GW.
  • S2b is a reference point that provides the user plane with relevant control and mobility support between the ePDG and PDN GW.
  • FIG. 2 is an exemplary view showing the architecture of a general E-UTRAN and EPC.
  • 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 an entity of the RRC layer of the eNodeB.
  • the RRC state is referred to as an RRC connected state.
  • the non-state is called the RRC idle state.
  • the E-UTRAN may determine the existence of the corresponding UE in units of cells, and thus may effectively control the UE.
  • the UE in the idle state can not be identified by the eNodeB, the core network (core network) is managed by the tracking area (Tracking Area) unit 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.
  • FIG. 7 and 8 illustrate an example of a structure in which a WLAN is connected to an EPC.
  • FIG. 7 shows an architecture where a WLAN is connected to a P-GW via an S2a interface (see 3GPP TS 23.402).
  • the WLAN access network is connected to the P-GW via the S2a interface (in particular, the S2a interface is a Trusted WLAN access network because it is an interface that connects trusted non-3GPP access with the EPC).
  • TWAN Trusted WLAN Access Network
  • WLAN 8 is an illustration of an architecture in which a WLAN is connected to a P-GW via an S2b interface.
  • the WLAN access network is an untrusted WLAN access network (especially, in the case of the S2b interface, which connects untrusted non-3GPP access with the EPC). It is connected to P-GW through Packet Data Gateway.
  • a trusted WLAN and an untrusted WLAN may be referred to as WLAN without distinction.
  • Data of the user terminal may be offloaded to WLAN access without going through 3GPP access.
  • technologies for supporting such multiple radio accesses there are IP Flow Mobility and Seamless Offload (IFOM), Multi Access PDN Connectivity (MAPCON), and the like.
  • IFOM IP Flow Mobility and Seamless Offload
  • MAPCON transmits data with 3GPP access and Wi-Fi access as separate PDN connections
  • IFOM transmits data by binding 3GPP access and Wi-Fi access to a single PDN or P-GW.
  • IFOM 9 is an exemplary view showing an example of IFOM technology.
  • the IFOM may provide the same PDN connection through different accesses at the same time. This IFOM provides seamless transmission and reception by bypassing the WLAN.
  • IFOM can carry the IP flow of the same PDN connection from one access to another. As such, thanks to the technology that can divert the traffic of the UE to a wireless LAN, it can reduce the congestion of cellular access of the mobile operator.
  • an access network discovery and selection function (ANDSF) based on 3GPP may provide a policy related to a wireless LAN.
  • the ANDSF may exist in a home public land mobile network (HPLMN) of a UE.
  • the ANDSF may also exist in a visited public land mobile network (VPLMN) of the UE.
  • H-ANDSF when the ANDSF is located in the home network, it may be called H-ANDSF, and when the ANDSF is located in the visited network, it may be called V-ANDSF.
  • H-ANDSF when the ANDSF is located in the home network, it may be called H-ANDSF, and when the ANDSF is located in the visited network, it may be called V-ANDSF.
  • ANDSF is used as a concept that includes both H-ANDSF and V-ANDSF.
  • the ANDSF can provide routing rules, such as information about inter-system mobility policy (ISMP), information for access network discovery, and information about inter-system routing policy (ISRP). have.
  • ISMP inter-system mobility policy
  • ISRP inter-system routing policy
  • IFOM is performed by the initiative decision of the UE.
  • a terminal capable of simultaneously using the 3GPP access network and the WLAN access network may perform IP flow mobility between the two access networks.
  • IFOM uses DSMIP (Dual Stack Mobile IP), a host-based mobility protocol.
  • IP flow mobility was performed only by initiation of the UE. Since then, it has evolved into NBIFOM (network based IP flow mobility), an IFOM technology based on GTP or PMIP, which is a network-based mobility protocol.
  • NBIFOM network based IP flow mobility
  • IP flow mobility may be performed not only by IP flow mobility by UE initiation but also by initiative and decision-making of the network.
  • the NBIFOM may be classified into NBIFOM (UE Initiated NBIFOM) initiated by the UE and NBIFOM (Network Initiated NBIFOM) initiated by the network, depending on who triggers the determination of IP flow mobility.
  • NBIFOM UE Initiated NBIFOM
  • NBIFOM Network Initiated NBIFOM
  • only one mode is used for one PDN connection.
  • the multiple access PDN connection may operate in the UE initiated mode or the network initiated mode. That is, mode selection is performed when the PDN connection is established and remains in the same mode as long as the PDN connection remains active.
  • NBIFOM can be divided into NBIFOM solution based on control-plane signaling and NBIFOM solution based on user-plane signaling.
  • control messages eg, NAS messages, WLAN Control Protocol (WLCP) messages, etc.
  • WLCP WLAN Control Protocol
  • Section 7.6 of TR 23.861v1.10.1 describes an NBIFOM solution based on user-plane signaling.
  • solution 1 describes the routing rules for NBIFOM by the UE or P-GW in the control message on the control plane. It describes how to create and send a redirect packet to target access instead of sending it. This will be described with reference to FIG. 11.
  • the method illustrated in FIG. 11 may be applied to an S2a interface (GTP or PMIPv6) or S2b (GTP or PMIPv6) interface for WLAN interworking, and does not affect network nodes other than P-GW and PCRF.
  • the P-GW may receive the extended PCC rule through Gx.
  • the extended PCC rule may include a preferred access type for a particular service data flow.
  • the P-GW may request NW-initiated IP flow mobility without receiving assistance information from the terminal.
  • Extended PCC rules in the P-GW can be used to determine when NW-initiated IP flow mobility should be requested.
  • the UE or P-GW may request an IP flow transfer from source access to target access while maintaining the PDN connection without changing routing rules.
  • the UE or P-GW may request an IP flow transfer from source access to target access while maintaining a PDN connection by sending a redirection packet through the target access.
  • the P-GW handles this packet according to the IPv4 / v6 procedure. However, the P-GW interprets the redirection packet as a request for moving IP flow # 1 from 3GPP access to WLAN access. The network does not charge for this redirect packet.
  • the P-GW or the UE When the P-GW or the UE receives the redirect packet, it determines whether to accept or reject the IP flow mobility request. Here the refusal is performed in an implicit way, without sending any explicit refusal indication. If the P-GW accepts moving the IP flow to the target network, the P-GW sends subsequent downlink packets over the target access. This informs the UE that the request has been accepted, and the UE also sends subsequent packets over the target access. If the UE accepts to move the IP flow to the target network, the UE sends a subsequent uplink packet through the target access. This tells the P-GW that the request has been accepted, and the P-GW also sends subsequent packets over the target access.
  • Both the UE and the P-GW maintain a Flow Binding Table indicating the access to which the IP flow should be routed.
  • the UE and the Flow Binding Table in the P-GW are synchronized so that packets of the IP flow are transmitted through the same access type.
  • the flow binding table may include information such as Record # 1: IP flow A-> 3GPP access, Record # 2: IP flow B-> WLAN access.
  • the terminal or the P-GW receives a redirect packet in which a time to live (TTL) is set to 1 through a second type access (ie, a target access of IP flow movement), and receives a redirect packet having a first type access (ie, for IP flow routing). It is possible to determine whether to change the source access) to the second type access with the access currently in use. If it is decided to change the first type access to the second type access, the packet may be transmitted to the P-GW through the second type access.
  • the first type access and the second type access are one of 3GPP access and WLAN access, wherein the first type access and the second type access are different from each other.
  • the predetermined message may be transmitted through the first type access, and the predetermined message may include information on the reason for rejection. It may include.
  • the terminal or the P-GW transmits a redirection packet as described above, but the redirection packet includes a reason for rejection.
  • the reasons for the rejection are 3GPP access loss, WLAN access loss, low signal strength of 3GPP access, low signal strength of WLAN access, rule conflict, forbidden access, overuse ( usage exceeded). Or, instead of subdividing the reason for rejection, you can define a value that represents the rejection itself. Alternatively, the rejection itself and the reason for rejection may be defined and used together, which may be collectively referred to as reason information for rejection.
  • the terminal or the P-GW rejects the access transfer request for the redirect packet
  • the entity transmitting the redirect packet may not know why the access transfer request is rejected.
  • the reason why the access transfer request was rejected is 3GPP access loss, WLAN access loss, low signal strength of 3GPP access, low signal strength of WLAN access, rule conflict, forbidden access ), Usage exceeded, etc., even if a redirect packet is sent again later, the same rejection will occur for a considerable time.
  • the UE received a redirect packet instructing the UE to transmit a packet from the 3GPP access to the WLAN access for the IP flow # 1 from the P-GW, and the signal strength of the WLAN access is very weak, so that the IP flow # 1 to the WLAN access. If you do not want to send a message, or if there is a conflict with an ANDSF rule (for example, active ISRP for IFOM rules) for the IP flow # 1 of the UE (that is, the ANDSF rule specifies that the packet is sent with 3GPP access for IP flow # 1).
  • an ANDSF rule for example, active ISRP for IFOM rules
  • P-GW / PCRF may reinitiate the same type of network-initiated NBIFOM unless the UE provides this reason to the P-GW (the PCRF that ultimately initiates the network-initiated NBIFOM). . In this case, the UE again rejects the redirection packet received from the P-GW, and as this is repeated, an unnecessary redirection packet is generated / transmitted. As another example, the P-GW has received a redirect packet from the UE to transmit a packet from the 3GPP access to the WLAN access for IP flow # 2, which may be rejected by the P-GW / PCRF based on subscriber information or status. .
  • the UE may reinitiate the same type of UE-initiated NBIFOM if the P-GW does not provide the UE with a reason for rejection. have.
  • the P-GW / PCRF again rejects the redirection packet received from the UE, and as this is repeated, an unnecessary redirection packet is generated / transmitted. If, according to the above-described embodiment of the present invention, the terminal or the P-GW can know the reason for the rejection of the redirection packet, it may not be necessary to repeatedly generate and transmit the redirection packet, thus unnecessary It is possible to prevent the repetitive generation, transmission, and use of network resources.
  • the predetermined message may be an Internet Control Message Protocol (ICMP) having a type value of 11.
  • ICMP Internet Control Message Protocol
  • the reason information of rejection may be transmitted on the field following the checksum field of the message.
  • An example of ICMP is shown in FIG. As illustrated in FIG. 12, an ICMP having a type value of 11 may include reason information of rejection through a next field (a portion marked Unused) of the checksum field.
  • the code field may be sent with a rejection reason value, and a field other than the code field may indicate the reason for rejection.
  • another conventional ICMP message may be used, or a new ICMP message may be defined and used.
  • the rejection reason information may be included in the IP header portion while transmitting the redirection packet.
  • the UE or the P-GW may transmit a redirect message including the rejection reason information in the IP header part to the P-GW.
  • the rejection reason information may be included in the TCP or UDP header portion while transmitting the redirection packet.
  • the UE may transmit a redirect message including the rejection reason information in the TCP or UDP header part to the P-GW.
  • the P-GW may transmit a redirect message including the rejection reason information in the TCP or UDP header part to the UE.
  • the rejection reason value may be defined in the source port field or the destination port field of the TCP header or the UDP header, or the rejection reason value may be defined in the other fields.
  • the UE or the P-GW when the UE or the P-GW receives the reason information of the rejection from the counterpart, it may not transmit a redirect packet of the same type / purpose as the redirected packet that has been rejected for a predetermined time or for the IP flow in the future. . Alternatively, it can be used as a factor to be considered when initiating NBIFOM operation in the future.
  • the access is different from the target access used by the other party to send the redirect packet for NBIFOM (i.e., WLAN access if target access is 3GPP access and WLAN access and target access is WLAN access). 3GPP access).
  • the UE receives a redirect packet for NBIFOM from the P-GW, it sends a conventional ICMP message to the P-GW.
  • the P-GW may transmit using a different access than the target access used to transmit the redirect packet for the NBIFOM. If the P-GW receives a redirect packet for NBIFOM from the UE, it transmits a conventional ICMP message to the UE.
  • the UE may transmit using a different access than the target access used to transmit the redirection packet for the NBIFOM.
  • the UE or P-GW may not include a detailed reason for rejection, but it is considered to express an explicit rejection by sending an ICMP message through an access different from the access that received the redirect packet.
  • -GW can recognize / manage differently from conventional implicit rejection.
  • the UE or the P-GW may use the ICMP Time-Exceeded packet as a conventional ICMP message used to inform rejection.
  • FIG. 13 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 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 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.

Landscapes

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

Abstract

Un mode de réalisation de la présente invention concerne un procédé de transmission et réception d'un signal associé à une mobilité de flux IP basée sur le réseau (NBIFOM) d'un terminal dans un système de communication sans fil. Le procédé de transmission et réception d'un signal associé à une NBIFOM comprend les étapes consistant à : recevoir, via un second type d'accès, un paquet de redirection dans lequel la durée de vie (TTL) est définie à 1 ; et déterminer s'il faut ou non remplacer un premier type d'accès par le second type d'accès. Lorsqu'il est déterminé que le remplacement du premier type d'accès par le second type d'accès est refusé, un message prédéterminé est transmis à une passerelle de réseau de données par paquets (P-GW) via le premier type d'accès, le message prédéterminé contenant des informations expliquant le refus.
PCT/KR2015/011791 2014-11-04 2015-11-04 Procédé de transmission et réception de signal associé à une nbifom dans un système de communication sans fil, et dispositif associé WO2016072742A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201462074660P 2014-11-04 2014-11-04
US62/074,660 2014-11-04
US201462077145P 2014-11-07 2014-11-07
US62/077,145 2014-11-07

Publications (1)

Publication Number Publication Date
WO2016072742A1 true WO2016072742A1 (fr) 2016-05-12

Family

ID=55909393

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2015/011791 WO2016072742A1 (fr) 2014-11-04 2015-11-04 Procédé de transmission et réception de signal associé à une nbifom dans un système de communication sans fil, et dispositif associé

Country Status (1)

Country Link
WO (1) WO2016072742A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013154375A1 (fr) * 2012-04-12 2013-10-17 엘지전자 주식회사 Procédé et appareil de transfert de service à commutation de paquets dans un système de communications sans fil
WO2013187672A1 (fr) * 2012-06-11 2013-12-19 삼성전자 주식회사 Procédé et appareil de commande de redirection entre systèmes hétérogènes de communications pour mobiles
WO2014074364A1 (fr) * 2012-11-07 2014-05-15 Interdigital Patent Holdings, Inc. Virtualisation de piles de réseau
US20140321328A1 (en) * 2011-11-29 2014-10-30 Interdigital Patent Holdings, Inc. Methods For IP Mobility Management

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140321328A1 (en) * 2011-11-29 2014-10-30 Interdigital Patent Holdings, Inc. Methods For IP Mobility Management
WO2013154375A1 (fr) * 2012-04-12 2013-10-17 엘지전자 주식회사 Procédé et appareil de transfert de service à commutation de paquets dans un système de communications sans fil
WO2013187672A1 (fr) * 2012-06-11 2013-12-19 삼성전자 주식회사 Procédé et appareil de commande de redirection entre systèmes hétérogènes de communications pour mobiles
WO2014074364A1 (fr) * 2012-11-07 2014-05-15 Interdigital Patent Holdings, Inc. Virtualisation de piles de réseau

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3GPP; TSG-SA; Network based IP flow mobility (Release 13)", 3GPP TR 23.861 V1.10.1, 3 November 2014 (2014-11-03), Retrieved from the Internet <URL:http://www.3gpp.org/DynaReport/23861.htm> *

Similar Documents

Publication Publication Date Title
WO2018084635A1 (fr) Procédé de passage d&#39;un ngs à un eps dans un système de communication sans fil et appareil associé
WO2016190670A1 (fr) Procédé et terminal de transmission de trafic de données dans un système de communication sans fil
WO2018155934A1 (fr) Procédé de réception de données relatives à un accès non-3gpp par l&#39;intermédiaire d&#39;un accès 3gpp dans un système de communication sans fil, et dispositif associé
WO2019066544A1 (fr) Procédé de transmission et de réception de signaux associés à un transfert d&#39;un système 5gs à un système eps dans un système de communication sans fil, et dispositif 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&#39;y rapportant
WO2017126948A1 (fr) Procédé d&#39;émission et de réception de message véhicule à tout (v2x) dans un réseau local au sein d&#39;un système de communication sans fil et appareil associé
WO2014129794A1 (fr) Procédé et terminal permettant de déterminer un accès sur la base d&#39;une politique
WO2016105004A1 (fr) Procédé d&#39;émission et de réception de capacité de nbifom dans un système de communication sans fil ainsi que dispositif associé
WO2016144009A1 (fr) Procédé et terminal de régulation de trafic réseau dans un système de communication sans fil
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é
WO2016126092A1 (fr) Procédé de sélection du réseau mobile terrestre public par un terminal dans un système de communication sans fil et appareil associé
WO2016186414A1 (fr) Procédé de fourniture d&#39;un service de diffusion dans un système de communications sans fil, et appareil associé
WO2019022442A9 (fr) Procédé de prise en charge de transmission de sms pour un équipement d&#39;utilisateur pouvant recevoir un service à partir d&#39;un système 5g 3gpp et d&#39;eps dans un système de communication sans fil, et appareil associé
WO2016056815A1 (fr) Procédé d&#39;émission/réception d&#39;un signal relatif à une mobilité nbifom dans un système de communication sans fil, et appareil associé
WO2017086618A1 (fr) Procédé de communication directe de dispositif à dispositif dans un système de communication sans fil et dispositif correspondant
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&#39;y rapportant
WO2016163635A1 (fr) Procédé de sélection d&#39;un plmn d&#39;un terminal dans un système de communication sans fil, et appareil associé
WO2018221943A1 (fr) Procédé d&#39;émission-réception de signal en association avec un ajout de psa multiconnexion dans un système de communication sans fil, et appareil associé
WO2019059740A1 (fr) Procédé de transmission/réception d&#39;un signal associé à une prise en charge de voix d&#39;un ims par un ng-ran dans un système de communication sans fil, et appareil associé
WO2016003199A1 (fr) Procédé de réalisation d&#39;une communication d2d dans un système de communication sans fil et dispositif associé
WO2017131481A1 (fr) Procédé de transmission de données, station de base, procédé de transmission de données et nœud central
WO2017086617A1 (fr) Procédé de fonctionnement pour un terminal fonctionnant en situation de congestion de réseau dans un système de communication sans fil et appareil pour celui-ci
WO2019194537A1 (fr) Procédé pour émettre/recevoir un signal associé à un message court dans un système de communication sans fil et dispositif associé
WO2017164686A1 (fr) Procédé de réalisation d&#39;opération liée à une transmission de message v2x dans un système de communication sans fil, et dispositif associé
WO2015174803A1 (fr) Procédé de connexion de réseau de données par paquet dans un système de communication sans fil, et appareil connexe

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: 15858003

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15858003

Country of ref document: EP

Kind code of ref document: A1