KR20150024022A - Apparatus and method for configuring a link of a packet service in wireless communication system - Google Patents

Abstract

The present invention relates to an apparatus and to a method for configuring an internet protocol link for a packet service in a wireless communication system. According to the present invention, the terminal receives an interface ID of a predetermined length from a network for the packet service, maps and stores the interface ID received from the network and the interface ID of a link local address generated by the terminal, and converts the interface ID received from the network into the interface ID generated by the terminal when data for packet service is transmitted and received. Therefore, the present invention has an advantage of satisfying a determined standard of a communication system and using adaptively a link local address generated by a service.

Description

[0001] APPARATUS AND METHOD FOR CONFIGURING A LINK OF A PACKET SERVICE IN WIRELESS COMMUNICATION SYSTEM [0002]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a wireless communication system, and more particularly, to an apparatus and method for configuring a link for packet service in a wireless communication system.

Recently, LTE (Long Term Evolution) system, a next generation wireless communication system, has been commercialized in earnest. This LTE system is spreading more rapidly after recognizing the need to support high-quality services for voice services as well as high-capacity services for users' needs while ensuring the activity of terminal users. The LTE system provides low transmission delay, high data rate, system capacity and coverage improvement.

On the other hand, considering the needs of service providers providing services to users, LTE system can improve performance by improving existing radio access and network, (Universal Mobile Telecommunication System) based on a 2G communication system and a Wideband Code Division Multiple Access (W-CDMA) system, which are GSM (Global System for Mobile Communications) And is being developed in a form of maintaining or coexisting with the 3G communication system. In addition, the LTE system supporting packet-based services provides a data transmission rate that is five times higher than that of the existing wireless communication system due to the flexibility and efficiency based on Internet Protocol (IP).

In addition to the development of such communication systems, the demand for high-capacity / high-speed packet services of users is becoming more diverse. Particularly, IP-based packet services are being developed into various types of services.

Accordingly, there is a need for a more specific link setting method for supporting this. In particular, there is a need for a link setting method for satisfying the requirements of a communication standard of a wireless communication system supporting packet services.

SUMMARY OF THE INVENTION It is an object of the present invention to provide an apparatus and a method for configuring an internet protocol link in a wireless communication system.

It is another object of the present invention to provide an apparatus and method for configuring an Internet Protocol link local address in a wireless communication system.

It is another object of the present invention to provide an apparatus and method for converting an Internet Protocol address for supporting a packet data service in a wireless communication system.

It is another object of the present invention to provide an apparatus and method for actively using an interface ID for supporting a packet data service in a wireless communication system.

According to an aspect of the present invention, there is provided a method of configuring a link of a terminal for packet service in a wireless communication system, the method comprising: receiving an interface ID of a predetermined length from the network for the packet service; Mapping an interface ID of a link-local address generated by a terminal with an interface ID received from the network, converting the interface ID received from the network into an interface ID generated by the terminal, and transmitting and receiving the data .

According to another aspect of the present invention, there is provided a terminal apparatus for configuring a link for a packet service in a wireless communication system, the terminal apparatus comprising: a wireless processing unit for transmitting and receiving a wireless signal; Maps the interface ID of the link-local address generated by the network to the interface ID of the predetermined length received from the network, converts the interface ID received from the network into the interface ID generated by the terminal, And a processor for controlling transmission and reception of the data.

In an Internet protocol based communication system supporting a packet service, an interface ID of a predetermined length set by a network can be defined to adaptively generate a link-local address according to a support service of the terminal. Therefore, it satisfies the requirements defined in the communication system, and does not restrict the use of the predetermined interface ID. That is, it is possible to adaptively provide an Internet protocol based service.

1 is a diagram schematically illustrating a structure of a next generation wireless communication system to which the present invention is applied.
2 is a block diagram illustrating a radio protocol architecture for a user plane to which the present invention is applied.
3 is a block diagram illustrating a wireless protocol structure for a control plane to which the present invention is applied.
4 is a diagram illustrating a structure of a bearer service in a wireless communication system to which the present invention is applied.
5 is a signaling flowchart for setting up an IP link according to an example in a wireless communication system to which the present invention is applied.
6 is a signaling flowchart for setting up an IP link according to another example in a wireless communication system to which the present invention is applied.
7 is a diagram illustrating a signaling flow for establishing an IP link between a network and a terminal according to the present invention.
8 is a diagram illustrating a signaling flow for actively configuring a link local address in accordance with the present invention.
9 is a diagram illustrating a signaling flow supporting a packet service by configuring a link local address by a terminal according to the present invention.
10 is a diagram illustrating a signaling flow supporting a packet service by configuring a link local address by a terminal according to another embodiment of the present invention.
11 is a diagram schematically showing a structure of a wireless communication system according to the present invention.

Hereinafter, some embodiments will be described in detail with reference to exemplary drawings. It should be noted that, in adding reference numerals to the constituent elements of the drawings, the same constituent elements are denoted by the same reference symbols as possible even if they are shown in different drawings. In the following description of the embodiments of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present disclosure rather unclear.

The present invention will be described with reference to a communication network. The work performed in the communication network may be performed in a process of controlling the network and transmitting data by a system (e.g., a base station) that manages the communication network, The work can be done.

1 is a schematic view illustrating a structure of a next generation wireless communication system to which the present invention is applied. This discloses the network structure of an E-UMTS (Evolved-Universal Mobile Telecommunications System). The E-UMTS system is called a LTE (Long Term Evolution) or LTE-A (advanced) system and is a packet-based system for providing various communication services such as voice and packet data.

Referring to FIG. 1, an E-UTRAN includes a base station 20 (eNB) that provides a control plane and a user plane to a user equipment (UE) 10. The terminal 10 may be fixed or mobile and may be referred to by other terms such as a mobile station (MS), an advanced MS (MS), a user terminal (UT), a subscriber station (SS) .

The base station 20 generally refers to a station that communicates with the terminal 10 and includes a base station (BS), a base transceiver system (BTS), an access point, a femto-eNB, A pico-eNB, a home eNB, a relay, or the like. The base station 20 can provide services to the terminal through at least one cell. The cell may mean a geographical area where the base station 20 provides communication services, or may refer to a specific frequency band. A cell may denote a downlink frequency resource and an uplink frequency resource. Or a cell may mean a combination of a downlink frequency resource and an optional uplink frequency resource.

On the other hand, in the case of the LTE system, it is possible to provide the same effect as using a single large band band logically by bundling a plurality of physically continuous or non-continuous bands in the frequency domain, Transmission rate. Herein, a technique of grouping a plurality of bands and logically using one band of a large band is called a carrier aggregation (CA). Accordingly, the present invention can be applied to a wireless communication system that supports CA and is applicable.

The base stations 20 may be interconnected via an X2 interface. The base station 20 is connected to an S-GW (Serving Gateway) through an MME (Mobility Management Entity) and an S1-U through an EPC (Evolved Packet Core) 30, more specifically, an S1-MME through an S1 interface. The S1 interface exchanges OAM (Operation and Management) information to support the movement of the terminal 10 by exchanging signals with the MME.

The EPC 30 includes an MME, an S-GW, and a PDN-GW (Packet Data Network-Gateway). The MME has information on the connection information of the terminal 10 and the capability of the terminal 10. This information is mainly used for managing the mobility of the terminal 10. [ The S-GW is a gateway having an E-UTRAN as an end point, and the P-GW is a gateway having a PDN (Packet Data Network) as an end point.

The E-UTRAN and the EPC 30 may be combined to form an EPS (Evolved Packet System), and the traffic flow from the wireless link to the base station 20 to the PDN connecting the terminal 10 to the service entity Lt; / RTI >

The wireless interface between the terminal and the base station is called a Uu interface. The layers of the radio interface protocol between the UE and the network are classified into L1 (first layer), L1 (second layer), and the like based on the lower three layers of the Open System Interconnection (OSI) A physical layer belonging to a first layer provides an information transfer service using a physical channel, and a physical layer (physical layer) An RRC (Radio Resource Control) layer located at Layer 3 controls the radio resources between the UE and the network. To this end, the RRC layer exchanges RRC messages between the UE and the BS.

2 is a block diagram illustrating a radio protocol architecture for a user plane. 3 is a block diagram illustrating a wireless protocol structure for a control plane. The user plane is a protocol stack for transmitting user data, and the control plane is a protocol stack for transmitting control signals.

2 and 3, a physical layer (PHY) layer 210 provides an information transfer service to an upper layer using a physical channel. The physical layer is connected to a medium access control (MAC) layer, which is an upper layer, through a transport channel. Data is transferred between the MAC layer and the physical layer through the transport channel. The transport channel is classified according to how the data is transmitted through the air interface. Data is transferred between the different physical layers, that is, between the transmitter and the physical layer of the receiver through a physical channel. The physical channel can be modulated by an Orthogonal Frequency Division Multiplexing (OFDM) scheme, and uses time and frequency as radio resources. There are several physical control channels. The physical downlink control channel (PDCCH) informs the UE of resource allocation of a paging channel (PCH), a downlink shared channel (DL-SCH), and hybrid automatic repeat request (HARQ) information related to the DL-SCH. The PDCCH may carry an uplink scheduling grant informing the UE of the resource allocation of the uplink transmission. A physical control format indicator channel (PCFICH) informs the UE of the number of OFDM symbols used for PDCCHs and is transmitted every subframe. PHICH (Physical Hybrid ARQ Indicator Channel) carries HARQ ACK / NAK signal in response to uplink transmission. A physical uplink control channel (PUCCH) carries uplink control information such as HARQ ACK / NAK, scheduling request and CQI for downlink transmission. A physical uplink shared channel (PUSCH) carries an uplink shared channel (UL-SCH).

The function of the MAC layer 220 is to perform mapping / demultiplexing to a transport block provided on a physical channel on a transport channel of a MAC SDU (service data unit) belonging to a logical channel and a mapping between a logical channel and a transport channel . The MAC layer provides a service to a Radio Link Control (RLC) layer through a logical channel. The logical channel can be divided into a control channel for transferring control area information and a traffic channel for transferring user area information.

The function of the RLC layer 230 includes concatenation, segmentation and reassembly of the RLC SDUs. In order to guarantee various QoS (Quality of Service) required by a radio bearer (RB), the RLC layer includes Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode , And AM). AM RLC provides error correction via automatic repeat request (ARQ).

In general, transparent mode is used to set the initial connection. The unacknowledged mode is for data streaming or real-time data transmission such as Voice over Internet Protocol (VoIP), and is a speed-focused mode rather than a data reliability. On the other hand, the acknowledged mode is a mode that focuses on the reliability of data and is suitable for data transmission which is less sensitive to large data transmission or transmission delay. The base station determines the mode of the RLC in the RB corresponding to each EPS bearer based on the Quality of Service (QoS) information of each EPS bearer connected to the UE and configures the parameters in the RLC so as to satisfy the QoS.

The functions of the Packet Data Convergence Protocol (PDCP) layer 240 in the user plane include transmission of user data, header compression and ciphering. The function of the Packet Data Convergence Protocol (PDCP) layer in the user plane includes transmission of control plane data and encryption / integrity protection.

The RRC layer 250 of FIG. 3 performs functions such as broadcast, paging, RRC connection management, RB control, mobility, and UE measurement of system information related to the NAS / AS. In particular, temporary ID assignment and radio resource setting for RRC connection are performed for setting up, managing, and releasing RRC connection between UE and E-UTRAN. That is, it is responsible for the control of the logical channels, the transport channels and the physical channels in connection with the configuration, re-configuration and release of the RBs. RB means a logical path provided by a first layer (PHY layer) and a second layer (MAC layer, RLC layer, PDCP layer) for data transmission between a UE and a network. The configuration of the RB means a process of defining characteristics of a radio protocol layer and a channel to provide a specific service, and setting each specific parameter and an operation method.

The RB may be further classified into an SRB (Signaling RB) and a DRB (Data RB). The SRB is used as a path for transmitting the RRC message and the NAS (Non-Access Stratum) message in the control plane, and the DRB is used as a path for transmitting the user data in the user plane.

In addition, the RRC layer 250 may perform mobility measurement between UEs and RAT (Radio Access Technology), UE handover, UE cell selection and reselection, context transmission between eNBs, UE measurement report, .

The NAS layer 260 located at the top of the RRC layer performs functions such as session management and mobility management. When there is an RRC connection between the RRC layer of the UE and the RRC layer of the E-UTRAN, the UE is in an RRC connected state. Otherwise, the UE is in an RRC idle state do.

In order for a terminal to transmit user data (e.g., IP packet) to an external Internet network or receive user data from an external Internet network, mobile communication network entities existing between the terminal and the external Internet network Resources must be assigned to the various paths that exist between them. A path in which resources are allocated between mobile communication network entities and data transmission / reception is possible is called a bearer.

4 is a diagram illustrating a structure of a bearer service in a wireless communication system to which the present invention is applied.

Referring to FIG. 4, a path through which an end-to-end service 400 is provided between a terminal and an Internet network is illustrated. Here, the term end-to-end service refers to a service (EPS Bearer, 410), a P-GW and an external path (external bearer, 420) between the terminal and the P-GW for the Internet network and data service do. Here, the external path is a bearer between the P-GW and the Internet network.

When the UE transmits data to the external Internet network, the UE transmits data to the eNB through a radio bearer (RB) Then, the BS transmits the data received from the UE to the S-GW through the S1 bearer 460. The S-GW transmits the data received from the base station to the P-GW through the S5 / S8 bearer 440 and finally the data is transmitted to the P-GW and the destination existing in the external internet network through an external bearer . Likewise, in order for data to be transmitted from the external Internet network to the mobile station, the mobile station can transmit data to the mobile station via the bearers in the reverse direction. As described above, in the wireless communication system, each bearer is defined for each interface to ensure independence between interfaces. The bearer at each interface will be described in more detail as follows.

The bearer provided by the wireless communication system is collectively referred to as an evolved packet system (EPS) bearer 410. The EPS bearer 410 is a delivery path established between the UE and the P-GW to transmit IP traffic with a certain quality of service (QoS). The P-GW may receive IP flows from the Internet or may transmit IP flows over the Internet. Each EPS bearer is set with QoS decision parameters indicating the characteristics of the propagation path. The EPS bearer may be configured for one or more UEs, and one EPS bearer uniquely represents a concatenation of one E-RAB (E-UTRAN Radio Access Bearer) 430 and one S5 / S8 bearer .

The S5 / S8 bearer is the bearer of the S5 / S8 interface. Both S5 and S8 are bearers present at the interface between the S-GW and the P-GW. S5 interface exists when the S-GW and P-GW belong to the same service provider. The S8 interface belongs to the Visited PLMN roaming S-GW and the P- RTI ID = 0.0 > PLMN). ≪ / RTI >

The E-RAB uniquely represents the concatenation of the S1 bearer and its corresponding RB. When there is one E-RAB, a one-to-one mapping is established between the corresponding E-RAB and one EPS bearer. That is, one EPS bearer corresponds to one RB, S1 bearer, and S5 / S8 bearer, respectively. The S1 bearer is the bearer at the interface between the base station and the S-GW.

RB means two kinds of data RB (data radio bearer) and signaling RB (signaling radio bearer). However, in the present invention, RB is a DRB provided in a Uu interface to support a user service . Therefore, the RB that is expressed separately is distinguished from the SRB. RB is a path through which user plane data is transmitted, and SRB is a path through which control plane data such as an RRC layer and a NAS control message are transmitted. There is a one-to-one mapping between RB, E-RAB and EPS bearer.

EPS bearer types include a default bearer and a dedicated bearer. When the terminal accesses the wireless communication network, the terminal is allocated an IP address and generates a PDN connection and a default EPS bearer at the same time. That is, the default bearer is first created when a new PDN connection is created. If a user uses a service (eg, the Internet) via a default bearer and uses a service (eg, VoD, etc.) that is not properly provided with QoS as the default bearer, A dedicated bearer is created. In this case, the dedicated bearer can be set to a different QoS from the bearer that has already been set. The QoS decision parameters applied to the dedicated bearer are provided by the Policy and Charging Rule Function (PCRF). When generating the dedicated bearer, the PCRF can receive the subscription information of the user from the Subscriber Profile Repository (SPR) and determine QoS determination parameters.

As described above, when the terminal accesses the wireless communication network, the wireless communication system allocates an IP address and sets a default EPS bearer. When setting up the default bearer, the UE transmits an IPv4 (Internet Protocol version 4) address, IPv6 (IP version 6), or both versions to a Dynamic Host Configuration Protocol version 4 or 6 according to the version, . Here, the IPv6 obtains only information on a 64-bit prefix.

In the current 3GPP environment, when a terminal uses a 128-bit IPv6 link local address, that is, an interface ID corresponding to the lower 64 bits of the IPv6 link local address composed of 128 bits, the terminal must use only the value assigned by the network . However, currently most operating systems (OSs) are generating 128-bit IPv6 link-local addresses themselves and are restricted from modifying this value arbitrarily.

As a result, the UE can not use the interface ID corresponding to the lower 64 bits as the value assigned by the network, and thus the 3GPP spec requirement can not be satisfied. In this regard, FIG. 5 illustrates an IP address assignment scheme of the current wireless communication system.

5 is a diagram illustrating a signaling flow for establishing an IP link in a wireless communication system.

Referring to FIG. 5, a method for establishing a bearer for transmitting and receiving packet data between a terminal and a network can be distinguished from a method initialized by a terminal and a method initialized by a network.

First, when the MS is initialized by the MS (MS initiated PDP context), the MS includes information on a packet data protocol (PDP) type, that is, an activation PDP including an IP version type And transmits a context request message (Activate PDP context Request) to the network (510).

For example, a terminal capable of supporting IPv4 and IPv6 can set the PDN type to IPv4v6 when no IP address is allocated. Alternatively, if the IPv4 address is allocated, the PDN type may be set to IPv6 to request IPv6. Or if the IPv6 address is assigned, the PDN type may be set to IPv4 to request IPv4. A terminal capable of supporting only IPv4 can set the PDN type to IPv4, and a terminal capable of supporting only IPv6 can set the PDN type to IPv6.

The network confirms the PDN type of the request message received from the MS, configures an IP stack for the packet data service of the MS, and transmits a response message (520). For example, the network sets the PDN type to IPv6 or IPv4v6 and transmits an Activate PDP context Accept message including a 64-bit Interface ID to the UE.

If the PDP context is initialized by the network (network initiated PDP context), the network transmits a PDP context activation request message including a 64-bit interface identifier to the PDP address information, ). In response to the request message, the UE sets the PDN type to IPv6 according to its IP capability, and transmits an Activate PDP context request message including the PDP type request message to the network in operation 540.

After confirming the PDN type IPv6, the network transmits an Activate PDP context Accept message including a 64-bit Interface ID to the mobile station in operation 550. In this case, the UE can use the 64-bit interface ID for the link-local address in the PDN address information (if the network sets the PDN type to IPv6 or IPv4v6, the network shall include the ID link local address in the PDN address information). FIG. 5 illustrates a method of allocating an IP address in a 3GPP environment.

In addition, Fig. 6 is a diagram showing another example of signaling for establishing an IP link in a wireless communication system.

Referring to FIG. 6, the UE sets a supportable IP version type as a PDN type and transmits a PDN connectivity request message to the network (610). For example, the PDN type is set to IPv6 or IPv4 is set to IPv6.

Upon reception of the PDN connection request message, the network allocates an IP address in consideration of PDN type information (PDN type IE), and transmits the operator policies of the home / visitor network and data of the user , and the user's subscription data). The network transmits an Activate default EPS Bearer Context Request message including a 64-bit Interface ID to the UE. FIG. 6 illustrates a method of allocating an IP address in a 4GPP environment.

As described with reference to FIGS. 5 and 6, in the 3GPP environment, the UE generates a new PDN and a 64-bit interface ID is allocated from the network to use the IPv6 address in the PDN. However, since the actual UE can not use the 64-bit interface ID set by the network and uses the link-local address configured by the OS, in generating the actual EPS bearer, There is a problem that the requirements are not satisfied.

Accordingly, in order to solve the problem that the current communication requirement is not properly reflected, the present invention provides a method for actively configuring and managing a link local address. In particular, a method for actively generating an IPv6 link local address by a terminal considering a 64-bit link-local address allocated by a network is disclosed.

7 is a diagram illustrating a signaling flow for establishing an IP link between a network and a terminal according to the present invention. In particular, the present invention initiates a mapping operation between a link-local address generated by a network and a link-local address generated by a terminal, and an operation of converting an active link-local address according to the service.

Referring to FIG. 7, the terminal includes a link local converter, and compares, maps, and translates a 64-bit interface ID received from an upper network to 64 bits under a link-local address generated by the terminal Can be performed. In particular, the UE supports an address allocation scheme capable of satisfying the requirements of the network system for the 128-bit IPv6 link local address used by the UE in the 3GPP environment.

The network 705 and the terminal 700 perform a procedure for activating the PDP context for the packet data service (710). For example, in a system supporting 3G, a UE performs a primary PDP context action procedure with a network and a terminal supports a default bearer activation procedure . This includes all procedures for establishing a bearer for packet data network (PDN) and packet service, as a procedure for a connection for an IP-based packet service. For example, the terminal may provide information on its PDN type to the network. The UE can transmit a PDN type IE set to IPv4, IPv4, or IPv4v6 to the network according to its capability. It may also receive configuration parameters according to the corresponding PDN type for supporting packet services from the network.

The procedure for activating the PDP context for the packet data service is performed between the MS 701 and the upper network 705 by using an Evolved Packet System (EPS) Mobility Management Entity (MME) Mobility and session management, and the NAS layer (protocol) will be described as an example. In particular, the EPS session management protocol (ESM) 704 of the NAS layer handles an EPS bearer context for the packet service. This includes that used by the AS for bearer control, that is, for controlling the user plane bearer.

The UE receives the allocated 64-bit interface ID from the network through the Primary PDP context activation (3G) or the Default Bearer Activation (4G) operation and confirms it in step 720. The receiving terminal records the interface ID in the table for the link local address (730).

The table for the link local address may be recorded and managed by a processor of the terminal, in particular, by a link local address translator of the processor or a terminal separately provided from the processor. Table 1 below shows the mapping relationship of the link local address table.

Link-Local Address Mapping Table UE interface ID (64 bits) Network interface ID (64 bits) CC: BB: AA: 99: 88: 77 (hex)

In Table 1 above, the link local address table of the link local address translator is initially empty. After receiving a specific interface ID from the network, the terminal can record and store and control the specific interface ID. In the present invention, it is assumed that the interface ID by the PDN 1 is CC: BB: AA: 99: 88: 77. That is, in association with IPv6, a 64-bit interface ID set by the network is stored.

Here, the link-local address table is configured in the terminal to check the relationship between the interface ID allocated by the network and the interface ID generated by the application entity or the OS according to the specific packet service by the terminal. In particular, the terminal may configure the link local address table by mapping an interface ID allocated at the time of a new PDN connection for packet service and a link local address formed by the OS for the packet service generated by the terminal .

Figure 8 is a diagram illustrating a signaling scheme for actively translating a link-local address in accordance with the present invention. In particular, it illustrates the operation of translating the link-local address generated by the terminal in relation to the link-local address generated by the network.

Referring to FIG. 8, the link-local address translator 804 included in the UE checks an IPv6 packet transmitted first with an IPv6 link local address from an application entity of the UE, and transmits the IPv6 packet to the 64-bit interface ID is extracted (810). The format of the link local address of the initially transmitted IPv6 packet is shown in Table 2 below. The address is an IPv6 address used in the link-local category, has a length of 128 bits, and has the form of FE: 80: 00: 00: 00: 00 + Interface ID (64 bits).

10 bits 54 bits 64 bit 1111 1110 10 0 Interface ID

The terminal records and maintains the 64-bit interface ID extracted from the address of the IPv6 packet transmitted from the application entity in the link-local address mapping table of the PDN in operation 820. For example, if the address of the IPv6 packet transmitted from the application entity is FE80: 0 + 11: 22: 33: 44: 55; 66, the link local address mapping table of Table 1 is updated as shown in Table 3 below.

Link-Local Address Mapping Table UE interface ID (64 bits) Network interface ID (64 bits) 11: 22: 33: 44: 55: 66 (hex) CC: BB: AA: 99: 88: 77 (hex)

According to the present invention, the terminal manages one-to-one mapping between the interface ID assigned by the network and the interface ID generated according to the application, thereby effectively using the allocation ID of the network defined in the communication standard.

9 is a diagram illustrating a signaling flow supporting a packet service by configuring a link local address by a terminal according to the present invention.

9, when receiving a downlink IPv6 packet from an upper network, the UE confirms that the destination address of the corresponding packet is FE80: 0 + CC: BB: AA: 99: 88: 77 ).

The terminal converts the assigned interface ID from the network to the interface ID at a predetermined location of the link local address configured by the terminal through the link local converter 904 (915). For example, the link-local address 11: 22: 33: 44: 55 corresponding to CC: BB: AA: 99: 88: 77 among the destination addresses of the received downlink IPv6 packet; 66.

The link local translator 904 converts the predetermined interface ID allocated by the network according to an EPS protocol version that can be supported by the terminal for the EPS session corresponding to the packet service, One-to-one mapping with the interface ID corresponding to the EPS context configured for establishment, recording and storing, and performing conversion / updating as necessary.

The link local translator 904 transfers the downlink IPv6 packet including the converted interface ID to the corresponding application entity (920). At this time, the downlink IPv6 packet has a destination address of FE80: 0 + 11: 22: 33: 44: 55; 66.

In addition, for the uplink, when the source address, that is, the source address, is received from the application entity as a link local address (930), the link-local address converter transmits the lower 64 bits of the source link- Bit interface ID assigned by the network recorded in the mapping table (940).

Here, the link local address generated by the application entity is 128 bits, and is an address generated by the terminal for the packet service. In accordance with the present invention, the terminal checks the lower 64 bits of the 128 bits and replaces it with an interface ID supported by the network. For example, the source address FE80: 0 + 11: 22: 33: 44: 55; 66 interface ID to FE80: 0 + CC: BB: AA: 99: 88: 77 mapped thereto.

Accordingly, the UE transmits an uplink IPv6 packet including the FE 80: 0 + CC: BB: AA: 99: 88: 77 to the converted source address to the network (950).

That is, through the link-local address translation operation provided in the IP stack of the terminal, the network allocates a 64-bit interface ID in the same operation, while the terminal reflects the link- To support the packet service.

In the present invention, the interface ID is replaced, replaced, or converted by the link local address translator. However, the present invention is not limited to this, The replacement, substitution, and conversion of the interface ID may be performed by an intra-terminal processor, and the operations may be performed by specific software, or may be implemented with a specific module .

10 is a diagram illustrating a signaling flow for converting a link-local address according to another embodiment of the present invention.

Referring to FIG. 10, when a downlink IPv6 packet occurs, the network sets a 64-bit interface ID and transmits it to the terminal. The terminal receives the downlink IPv6 packet from the upper network and confirms the 64-bit interface ID determined by the network of the IPv6 packet. That is, it is confirmed that the destination address is set to FE80: 0 + CC: BB: AA: 99: 88: 77 (1010).

At this time, the terminal converts the interface ID allocated from the network to the ID configured by the terminal through the link-local address conversion scheme (1020). Here, the link-local address translator receives and transmits the IPv6 packet using the 128-bit link-local address through the protocol stack. The interface ID of the lower 64 bits of the link-local address generated by the UE and the 64- ID to each other. Meanwhile, if downlink data is received before having the 64-bit interface ID generated by the UE in the corresponding mapping table, the link local translator (or link local translator) transmits the destination address of the downlink IPv6 packet To FF: 02: 01. The FF: 02: 01 means that all entities within the link-local category can receive the downlink packet data.

Then, the downlink IPv6 packet including the converted ID is transmitted to the corresponding application entity (1030).

Therefore, according to the present invention, the UE is actively converting and supporting the link-local address assigned to the network in a predetermined length in the wireless communication system, and thus has the advantage of supporting the communication according to the standard specification of the 3GPP environment. In addition, the link-local address converter records and maintains a 64-bit interface ID assigned by the network and a 64-bit interface ID mapping table directly generated by the UE for each PDN, thereby accurately supporting the packet service for the corresponding application .

11 is a block diagram briefly showing the structure of a wireless communication system according to the present invention.

11, the UE 1100 includes a radio signal processing unit (RF unit) 1110, a memory 1120, and a processor 1130. The RF processor 1110 is connected to the processor 1130 and transmits / receives a radio signal.

The processor 1130 is an entity that performs functions, procedures, methods, and the like according to the present invention, and performs the operations of FIGS. 2 to 10 of the present invention. Particularly, the processor 1130 according to the present invention performs an operation of generating and converting a link-local address according to an IP-base related to a data flow from a wireless link to a PDN that connects to a service entity, do. In particular, the IP address allocation through NAS signaling is confirmed, that is, mapping and recording / maintenance are performed in consideration of the interface ID allocated from the network and the IP address generated by the terminal according to the service. In other words, an operation of identifying the interface ID of the terminal generated for the application entity and the interface ID generated by the network according to the service and mapping the interface ID generated by the network on a one-to-one basis, confirming the created one-to-one mapping table, And transfers the data to the corresponding service entity.

For example, it is determined whether the corresponding terminal can support IPv6, or IPv4, or a PDN type that can support both types, and reflects the link-local address determined by the network according to the IPv6, And to support the corresponding service in consideration of the mapping relation with the link local address.

The memory 1120 is connected to the processor 1130 and includes information for supporting all the operations of the processor 1130.

The network 1150 includes a wireless signal processing unit (RF unit) 1160, a processor 1180, and a memory 1170. The RF processor 1160 is connected to the processor 1180 and transmits / receives a radio signal. Here, the network may be configured such that some entities of the base station and some entities of the upper core network are partially supported according to their operations. That is, the processor 1180 of the network according to the present invention performs the operations of FIGS. 2 to 10 of the present invention as an entity for performing the functions, procedures and methods according to the present invention. In other words, the terminal 1100 is configured to check the PDN type set up to configure the IP stack, and to control parameters, channels, and procedures for servicing the requested packet of the terminal.

The memory 1170 is connected to the processor 1180 and includes information for supporting all the operations of the processor 1180.

The foregoing description is merely illustrative of the technical idea of the present invention, and various changes and modifications may be made by those skilled in the art without departing from the essential characteristics of the present invention. Therefore, the embodiments disclosed in the present invention are intended to illustrate rather than limit the scope of the present invention, and the scope of the technical idea of the present invention is not limited by these embodiments. The scope of protection of the present invention should be construed according to the following claims, and all technical ideas within the scope of equivalents should be construed as falling within the scope of the present invention.

Claims (15)

A method for configuring a link of a terminal for packet service in a wireless communication system,
Receiving an interface ID of a predetermined length from the network for the packet service;
Mapping an interface ID of a link local address generated by the terminal with an interface ID received from the network for the packet service;
And transmitting and receiving the data by converting an interface ID received from the network into an interface ID generated by the terminal.
The method of claim 1,
And a 64-bit interface ID for supporting Internet Protocol version 6.
The method as claimed in claim 1, wherein the step of receiving the interface ID comprises:
Receiving a 64-bit interface ID through a procedure for setting a default bearer between the terminal and a packet data network (PDN)
And storing the received 64-bit interface ID in a table for a link local address of the terminal.
2. The method of claim 1,
And mapping the interface ID received from the network to a lower-order 64-bit interface ID of a 128-bit link-local address generated by the terminal on a one-to-one basis. .
The method of claim 1, wherein the transmitting and receiving the data comprises:
Determining whether the uplink packet data is uplink packet data,
Converting an interface ID of a link local address generated by the terminal into an interface ID received from the network;
And transmitting Internet Protocol version 6 packet data having a source address including an ID of the converted interface to a packet data network (PDN). .
The method of claim 1, wherein the transmitting and receiving the data comprises:
Determining whether the downlink packet data is downlink packet data,
Converting an interface ID received from the network into an interface ID of a link local address generated by the terminal;
And transmitting, to the application entity, Internet Protocol version 6 packet data having a destination address including the ID of the converted interface, to the application entity.
The method of claim 6, wherein the transmitting /
Further comprising the step of converting an interface ID received from the network into an interface ID indicating that the downlink packet data can be received by all entities in the link local category. How to configure links for.
A terminal apparatus for configuring a link for a packet service in a wireless communication system,
A radio processing unit for transmitting and receiving a radio signal,
And mapping the interface ID of the link-local address generated by the terminal for the packet service with the interface ID of the predetermined length received from the network, and transmitting the interface ID received from the network to the terminal And converting the generated interface ID into the generated interface ID and transmitting / receiving data for the packet service.
9. The apparatus of claim 8,
And verifying that the interface ID of the predetermined length is a 64-bit interface ID for supporting the Internet Protocol version 6. The terminal apparatus of claim 1,
9. The apparatus of claim 8,
The 64-bit interface ID is received through a procedure for establishing a default bearer between the terminal and the packet data network (PDN), and the 64-bit interface ID is stored in a table for the link local address of the terminal And transmitting the packet service to the terminal device.
9. The apparatus of claim 8,
One-to-one mapping of interface IDs received from the network to lower-order 64-bit interface IDs of 128-bit link-local addresses generated by the terminal, and storing and managing the mapping in a table for link- The terminal apparatus comprising:
9. The apparatus of claim 8,
And transmits the interface ID of the link-local address generated by the terminal to the interface ID received from the network, and then transmits the converted interface to the interface having the source address including the ID And controlling the Internet Protocol version 6 packet data to be transmitted to the packet data network (PDN).
9. The apparatus of claim 8,
Determines whether the data is downlink packet data, converts an interface ID received from the network into an interface ID of a link local address generated by the terminal, and transmits a destination address including the ID to the converted interface Wherein the control unit controls the Internet Protocol version 6 packet data to be transmitted to the application entity.
14. The apparatus of claim 13,
Determining whether the downlink packet data is downlink packet data, converting an interface ID received from the network into an interface ID indicating that the downlink packet data can be received by all entities in the link-local category, Further comprising controlling to transmit Internet Protocol version 6 packet data having a destination address including an ID to all entities.
9. The apparatus of claim 8,
And a link-local address converter for converting an interface ID received from the network into an interface ID generated by the terminal.

Images