KR102112610B1 - Method and apparatus for device to device communication - Google Patents

Abstract

The present specification relates to a device-to-device communication (D2D communication) and a support method and device of a terminal, wherein the device-to-device communication method according to an embodiment of the present specification uses the terminal or the terminal user used for D2D communication. Obtaining a proximity service identifier (Proximity Service ID; ProSe ID), generating an expression using the ProSe ID, broadcasting the generated expression, between devices from other terminals through a core network The method may include receiving a direct connection request message, transmitting a direct connection allowance message for the direct connection request message, and performing communication between the other terminal and the device using the ProSe ID. According to one embodiment of the present specification, communication between devices may be conveniently performed.

Description

METHOD AND APPARATUS FOR DEVICE TO DEVICE COMMUNICATION}

At least some embodiments of the present specification relate to device-to-device communication (D2D communication) based on a wireless cellular communication system.

D2D communication is a method of directly communicating data without using a cellular network (network) when a terminal communicates with an adjacent terminal. Each D2D terminal uses its own information to inform other terminals of its own information. Inform. In this case, the own information used by the terminal to inform other terminals of its own information may include, for example, the identifier of the terminal or the identifier of the terminal user (hereinafter referred to as Proximity Service ID, ProSe ID or D2D ID). . On the other hand, the terminal acquires information about the counterpart terminals through an expression received from neighboring terminals and attempts D2D communication when it finds the counterpart terminal of interest from this information.

On the other hand, communication providers are attempting to generate profit by providing D2D communication by utilizing radio resources that are not allocated in a licensed frequency band or a cellular network that they are not using. Accordingly, a method for providing D2D communication and controlling a D2D service based on a cellular network is being sought.

Therefore, in order to control paging of the corresponding terminal in the cellular network, an identifier assigned in the cellular network from the identifier of the terminal used in D2D communication or the identifier of the terminal user (for example, ProSe ID) (for example, GUTI; Globally Unique) Temporary UE Identity) is needed.

An object of at least some embodiments of the present specification is to provide a device and method for communicating between devices that can effectively perform device-to-device communication.

A communication method between devices according to an embodiment of the present disclosure includes obtaining a Proximity Service ID (ProSe ID) of the terminal or a terminal user used for D2D communication, and expression using the ProSe ID Generating, broadcasting the generated expression, receiving a direct connection request message between devices from another terminal through a core network, transmitting a direct connection allowance message for the direct connection request message, and It may include the step of performing communication between the other terminal and the device.

A communication method between devices of a terminal according to an embodiment of the present disclosure includes receiving an expression broadcast by another terminal, and a proximity service ID (Proximity Service ID) of the other terminal or terminal user from the expression ID), transmitting a direct connection request message between devices to the other terminal through the core network, receiving a direct connection allowance message for the direct connection request message, and using the ProSe ID It may include the step of performing communication between the terminal and the device.

A method for supporting communication between devices of a communication entity according to an embodiment of the present disclosure includes receiving a direct connection request message requesting a connection to a second terminal from a first terminal, and transmitting paging to the second terminal , After the second terminal is connected, transmitting the direct connection request message to the second terminal, receiving a direct connection allowance message for the direct connection message from the second terminal and the direct connection And transmitting an allowance message to the first terminal.

According to at least some embodiments of the present specification, communication between devices may be effectively performed.

1 is a structural diagram of D2D communication based on an EPC network.
2 is a block diagram of Expression according to an embodiment of the present specification.
3A and 3B are flowcharts of a D2D communication process according to an embodiment of the present specification.
4A and 4B are flowcharts of a D2D communication process according to another embodiment of the present specification.
5 is a flowchart of a ProSe ID delivery process according to an embodiment of the present specification.
6 is a flowchart of a ProSe ID delivery process according to another embodiment of the present specification.

Hereinafter, exemplary embodiments of the present specification will be described in detail with reference to the accompanying drawings. At this time, detailed descriptions of well-known functions and configurations that may obscure the subject matter of the present specification will be omitted. In addition, although an example of an EPC (Evolved Packet Core) network, that is, an LTE network is described as an example of a cellular network in the present specification, embodiments of the present specification may be applied to a wireless data communication network other than the LTE network.

In this specification, a user terminal (UE: User Equipment, hereinafter referred to as a 'UE' terminal) discovers another terminal in the short distance and paging the counterpart terminal through a cellular network to perform D2D communication with the terminal to establish a data connection. It relates to a method and apparatus for D2D communication. In addition, the present specification relates to a method and apparatus for configuring the terminal's own expression (hereinafter referred to as an expression) broadcast by the terminal in order to find the counterpart terminal through a cellular network. In addition, the present specification is to control authorization, including whether D2D communication is possible when the terminal attempts to establish a data connection with the counterpart terminal or a cellular network in order to perform D2D communication with the counterpart terminal. It relates to a method and apparatus for. In addition, this specification relates to a method and apparatus for transmitting its own identifier (Proximity Service ID, ProSe ID or D2D ID) used in D2D communication to a cellular network.

In the embodiment of the present specification to be described below, a method of performing D2D communication based on an EPC network will be described. Although EPC networks are mainly exemplified in this specification, other types of cores of cellular-based networks may take over the role of EPCs.

1 is a structural diagram of D2D communication based on an EPC network. Evolved Packet Core 1 (EPC1) 103 includes a Home Subscriber Server (HSS) 105, a Serving Gateway (S-GW) 106, and a Packet Data Network Gateway (PDN). -GW; P-GW) 107 and Mobility Management Entity (MME) 104. UE1 101 is connected to EPC1 103 through evolved Node B 1 (eNB1) 102. EPC2 114 includes HSS 111, S-GW 112, P-GW 113 and MME 110. UE2 109 is connected to EPC2 114 through eNB2 109. The two MMEs 104 and 110 may be connected 116 to each other, or the two EPCs 103 and 114 may share the same MME.

UE1 101 and UE2 108 are terminals connected to EPC1 103 and EPC2 114, respectively. Both UE1 101 and UE2 108 may perform D2D communication. Each terminal broadcasts an expression corresponding to the terminal itself through a discovery channel so that adjacent terminals can receive (listen). Here, UE1 (101) broadcasts its expression (118).

The terminal UE2 108 receiving the broadcast expression 118 finds the ProSe ID (or other identifier) of the UE1 101 through the expression 118. When the UE2 108 wants to perform D2D communication with the UE1 101, it performs an operation to find the UE1 101 in the cellular network. For example, UE2 108 searches for UE1 101 by passing information about UE1 101 such as ProSe ID to EPC2 114 through eNB2 109 (117) and EPC2 114. The search request may be delivered to EPC1 103 through EPC2 114. EPC1 103 finds the identifier in EPC1 103 for UE1 101. The EPC1 103 notifies the UE1 101 through the eNB1 102 (115) that the D2D communication request from the UE2 108 has arrived. When the UE1 101 permits D2D communication, a notification regarding such permission is sent back to the UE2 108 to establish a D2D data connection context, etc. between the UE1 101 and the UE2 108. Based on this, UE2 (108) performs D2D data communication (120) after performing D2D RRC configuration (119) with UE1 (101).

2 is a block diagram of expression according to an embodiment of the present specification.

According to an embodiment of the present disclosure, the terminal receives permission for D2D communication and may generate and broadcast an expression of the configuration shown in FIG. 2 through a discovery channel for D2D communication.

Referring to FIG. 2, expression includes an identification information field 201, an EPC information field 202, and a user preference field 203.

The terminal contains ProSe ID information as a value created by using the ProSe ID assigned to it and the authentication key received when obtaining authentication for the use of D2D communication service and information disclosed to other terminals (to the public). The identification information field 201 may be generated. The UE may also generate an EPC information field 202 that includes information related to the EPC to which the UE is connected and a user preference field 203 that includes information about the preference or situation of the UE user. Expression may include the above-described fields 201, 202, and 203.

The identification information field 201 may be generated using a hash function for security of the ProSe ID. In this case, the terminal receiving the expression can generate identification information using the hash function in the same way for the ProSe ID in its friend list. The ProSe ID corresponding to the same identification information as the received identification information is the ProSe ID of the opposite terminal that sent the expression received by the terminal.

Meanwhile, the EPC information field 202 including information related to the EPC network to which the terminal is connected may include an identifier of a group or network equipment to which the terminal is connected. For example, the EPC information field 202 may include at least one or more of E-UTRAN Cell Global Identifier (ECGI), Tracking Area Identity (TAI), Globally Unique MME Identity (GUMMEI), or all of them. Alternatively, the EPC information field 202 may include only a part of any one of the identifiers. For example, it may include only a public land mobile network identifier (PLMN ID).

On the other hand, the EPC information field 202 may include the identifier of the terminal allocated from the EPC network to which the terminal is connected, instead of the identifier of the group or network equipment to which the terminal is connected. For example, the EPC information field 202 may include ECGI and Cell-Radio Network Temporary Identifier (CRNTI). Alternatively, the EPC information field 202 may include at least one of SE TM (SAE Temporary Mobile Subscriber Identity), Globally Unique Temporary UE Identity (GUTI), and International Mobile Subscriber Identity (IMSI). Alternatively, the EPC information field 202 may include only a part of any one of the identifiers.

The EPC information field 202 including information related to the EPC network to which the terminal is connected and the user preference field 203 containing user information use a shared encryption key through an authentication process for security. It can also be encrypted. The authentication process will be described with reference to step 356 of FIG. 3A or step 456 of FIG. 4A described later.

In addition, if the EPC information field 202 including information related to the EPC network to which the terminal is connected includes a terminal identifier assigned from the EPC network to which the terminal is connected, another method for security may be used. Of the EPC information field 202 including information related to the EPC network, a part corresponding to the identifier of the terminal excluding the identifier of the group or network equipment to which the terminal is connected (for example, M-TMSI part GUTIEI except for the GUMMEI part) ) May be encrypted or may include an authentication code. The encryption key shared between the terminal and the EPC network (for example, a NAS security key) may be used for the terminal to access the EPC network for encryption process or authentication code generation. When the encrypted information or authentication code is used, security or integrity of the contents included in the EPC information field 202 can be checked.

In addition, as another embodiment of the present specification, the terminal accesses the EPC network, authenticates the D2D communication service, generates an expression as described in the above embodiment, and refers to the expression received from the opposite terminal, and the ProSe of the opposite terminal The process of establishing paging and data connection through the cellular network in a relationship with the counterpart terminal by obtaining the ID and obtaining the identifier of the cellular network of the counterpart terminal corresponding to the ProSe ID will be described.

3A and 3B are flowcharts of a D2D communication process according to an embodiment of the present specification. Hereinafter, FIG. 3A and FIG. 3B are collectively referred to as FIG. 3. The embodiment of FIG. 3 relates to a case where the EPC information field 202 of Expression includes an identifier of a group or network equipment.

Since the process of generating the expression through the process of the terminal authentication by the terminal UE1 320 and the terminal UE2 330 accessing the EPC1 300 and the EPC2 350, respectively, and through the process of Prose authentication, the terminals 320 and 330 follow the same process. The procedure of UE2 330 will be mainly described.

In step 352, the UE2 330 transmits an attach request message to the EPC2 network 350 through the eNB2 340 to access the EPC2 350. The attach request message includes a Prose Capability Indication indicating that the terminal 330 supports D2D communication.

In step 353, the MME of the EPC2 350 performs authentication for the UE2 330 based on subscription information received from the HSS. In this process, the MME may receive ProSe_ID2 (the D2D identifier of UE2 330) from the HSS, and store and manage mapping information of the identifier in EPC2 350 and ProSe_ID2. Of course, the mapping information may be stored and managed in network equipment other than the MME. The method of obtaining the mapping information in the EPC2 network such as MME will be described later.

If authentication is successful in step 353, in step 354, EPC2 350 transmits an attach accept message to terminal UE2 330. The attach permission message includes a ProSe Permission Notification indicating a result of performing authentication for D2D communication based on subscription information. Upon receiving the attach permission message, the UE2 330 transmits an attach complete message to the EPC2 350 in step 355. The network entry procedure of UE2 330 is completed according to the operation of step 355. The UE2 330 may set for D2D communication in step 356 or perform an authentication procedure for the D2D communication service.

Then, as mentioned in the embodiment with reference to FIG. 2, UE2 330 generates an expression in step 358. In the authentication process for the D2D communication service, the UE2 330 may receive an authentication key that the UE2 330 can use when generating the expression, and the terminal UE2 330 may receive a part of the expression. An encryption key used for encryption or an upper encryption key for generating the encryption key may be received.

In step 351, UE1 320 enters the EPC1 300 network. Since the procedure in step 351 corresponds to the procedure in steps 352 to 356, detailed description is omitted here.

In step 357, the UE1 320 generates an expression using information such as its D2D identifier ProSe_ID1 and EPC information (EPC info_UE1). UE1 320 starts broadcasting the expression generated in step 359.

In step 360, the UE2 330 receives an expression broadcast by the UE1 320, and acquires Prose_ID1 from the received expression. That is, it can be confirmed that the D2D identifier of the sender terminal of the corresponding expression is Prose_ID1. The UE2 330 acquires the identifier of the connected equipment in the EPC1 300 for the corresponding terminal 320 from the received expression, for example, GUMMEI, and determines to perform D2D communication with the terminal using ProSe_ID2.

The UE2 330 does not yet know the identifier in the EPC of the UE using ProSe_ID2. Accordingly, in step 361, UE2 330 sends a direct connection setup request message to EPC2 350 through eNB2 340 in order to make a D2D connection with ProSe_ID2 user. The direct connection setup request message may include information obtained by the UE2 330, that is, ProSe_ID1 and EPC info_UE1. It may also include its own ProSe_ID2 and EPC info_UE2. In step 362, the MME of the EPC2 350 uses the information of the EPC info_UE1 to determine whether D2D communication between the ProSe_ID1 terminal and the ProSe_ID2 terminal in its network is possible, such as a service agreement between operators, or other conditions. You can also check based.

If it is determined that D2D communication is possible, in step 363, EPC2 350 forwards the direct connection setup request message to EPC1 300 according to the information of EPC info_UE1. In step 364, EPC1 300 uses the information of ProSe_ID1 and EPC info_UE1 included in the delivered direct connection setup request message 363 to find the terminal identifier in EPC1 300 mapped to ProSe_ID1. For example, the search process may be performed by the MME of the EPC1 300.

In addition, the EPC1 300 may check whether the corresponding terminal, that is, the UE1 320 can perform D2D communication, based on the terminal identifier in the EPC1 300 corresponding to the obtained ProSE_ID1.

If it is determined that the terminal UE1 320 is in the idle mode, in step 365, the MME of the EPC1 300 transmits a paging request to the eNB1 310. The eNB1 310 transmits paging to UE1 320 in step 366. Subsequently, in step 367, the UE1 320 performs a process for switching to a connected mode.

Subsequently, the EPC1 300 transmits the direct connection setup request message received through the eNB1 310 to the UE1 320 in the connection mode in steps 368 and 369.

In step 368, the EPC1 300 sends an S1-AP message informing the eNB1 310 of a direct connection setup request, and the eNB1 310 receiving the S1-AP message is resource allocation information for direct connection setup. Prepare your back. The S1-AP message and the RRC reconfiguration message of steps 368 and 369 may include a direct connection setup request message.

 The EPC1 300 may transmit a message including information on ProSe_ID2 and EPC info_UE2 separately generated by the MME to the UE1 320 instead of the direct connection setup request message. Upon receiving the direct connection setup request message, UE1 320 accepts a D2D communication request from the terminal of ProSe_ID2 in step 370. Accordingly, UE1 320 transmits an acceptance message for the D2D communication request in steps 371 and 372, that is, a Direct Connection Setup Accept message to EPC1 300 through eNB1 310.

In step 371, the eNB1 310 receiving the RRC reconfiguration message in step 372 transmits resource allocation information for the prepared direct connection setup to the eNB2 340 connected to the other terminal UE2 330. The S1-AP message and steps 373 and 374 may be used. Alternatively, according to a modified example, the eNB1 310 may directly transmit resource allocation information for the prepared direct connection setup to the other eNB2 340.

 In step 373, EPC1 300 transmits a direct connection setup allowance message to EPC2 350. In steps 374 and 375, EPC2 350 transmits a direct connection setup allowance message to UE2 330.

In step 374, the EPC2 350 sends an S1-AP message informing the eNB2 340 of a direct connection setup request, and the S1-AP message includes resource allocation information for direct connection setup.

The S1-AP message and the RRC reconfiguration message of steps 374 and 375 may include a direct connection setup allowance message.

Thereafter, a process of setting up a direct connection radio bearer (D2D radio bearer) is performed using resources allocated by the eNB1 310 and the eNB2 340. For example, in step 376, the UE2 330 sends a direct RRC connection request message to establish a radio resource control (RRC) connection with the UE1 320. Directly to UE1 (320). In step 377, UE1 320 transmits a direct RRC connection setup message to UE2 330. In step 378, UE2 330 transmits a direct RRC connection complete message to UE1 320. Accordingly, a radio bearer is generated. In step 379, UE1 320 and UE2 330 perform D2D communication through the radio bearer.

4A and 4B are flowcharts of a D2D communication process according to another embodiment of the present specification. Hereinafter, FIGS. 4A and 4B are collectively referred to as FIG. 4. The embodiment of FIG. 4 particularly relates to a case where the EPC information field 202 of Expression includes an identifier of a terminal allocated from the EPC.

Since the process of generating the expression after the UE UE 420 and the UE UE 430 access the EPC1 400 and the EPC2 450 respectively and undergoes a Prose authentication process, the two UEs 420 and 430 follow the same process. The procedure of UE2 430 will be mainly described.

In step 452, the UE2 430 transmits an attach request message to the EPC2 network 450 through the eNB2 440 to access the EPC2 450. The attach request message includes a Prose Capability Indication indicating that the terminal 430 supports D2D communication.

In step 453, the MME of the EPC2 450 performs authentication for the UE2 430 based on subscription information received from the HSS. In this process, the MME may receive ProSe_ID2 (the D2D identifier of UE2 430) from the HSS, and store and manage the mapping information of the identifier in EPC2 and ProSe_ID2. Of course, the mapping information may be stored and managed in network equipment other than the MME. The method of obtaining the mapping information in the EPC2 network such as MME will be described later.

If authentication is successful in step 453, an attach permission message is transmitted to terminal UE2 430 in step 454. The attach permission message includes a ProSe Permission Notification indicating a result of performing authentication for D2D communication based on subscription information. Upon receiving the attach permission message, UE2 430 transmits an attach completion message to EPC2 450 in step 455. The network entry procedure of UE2 430 is completed according to the operation of step 455. In step 456, the UE2 430 may set for D2D communication or perform an authentication procedure for the D2D communication service.

Then, in step 458, UE2 430 generates an expression as mentioned in the embodiment with reference to FIG. 2 above. It starts broadcasting. In the authentication process for the D2D communication service, the UE2 430 may receive an authentication key that the UE2 430 can use when generating the expression, and the UE2 430 encrypts a part of the expression. In order to do so, the encryption key used or the upper encryption key for generating the encryption key may be received.

In step 451, UE1 420 enters the EPC1 400 network. Since the procedure in step 451 corresponds to the procedure in steps 452 to 456, detailed description is omitted here.

In step 457, the UE1 420 generates an expression using information such as ProSe_ID1 and EPC info_UE1, which are its D2D identifiers. In step 459, UE1 420 starts broadcasting the generated expression.

In step 460, the UE2 430 receives the expression broadcast by the UE1 420, and acquires Prose_ID1 from the received expression. That is, it can be confirmed that the D2D identifier of the sender terminal of the corresponding expression is Prose_ID1. The UE2 430 acquires a terminal identifier (EPC ID_UE1) assigned from the EPC1 400 for the corresponding terminal 320 from the received expression, for example, GUTI, and determines to perform D2D communication with a terminal using ProSe_ID2.

The UE2 430 sends a direct connection setup request message to the EPC2 450 through the eNB2 440 in step 461 to make a D2D connection with the UE using ProSe_ID2. The direct connection setup request message may include information obtained by the UE2 430, that is, ProSe_ID1, EPC ID_UE1, and may further include its own ProSe_ID2 and EPC ID_UE2. In step 462, the MME of the EPC2 450 uses the information of the EPC ID_UE1 to check whether D2D communication between the terminal of the ProSe_ID1 and the ProSe_ID2 terminal in its network is possible based on a service agreement between operators. It might be.

If it is determined that D2D communication is possible, in step 463, EPC2 450 forwards the direct connection setup request message to EPC1 400 according to the information of EPC ID_UE1. In step 464, the EPC1 400 may use the information of the EPC ID_UE1 included in the transmitted direct connection setup request message to check whether D2D communication of the corresponding terminal, that is, UE1 420, is possible.

If it is determined that the UE1 420 is in the idle mode, in step 465, the MME of the EPC1 400 transmits a paging request to the eNB1 410. The eNB1 410 transmits paging to the UE1 320 in step 466. In step 467, the terminal UE1 420 performs a process 467 for switching to a connected mode.

Subsequently, the EPC1 400 delivers the received direct connection setup request message through the eNB1 410 to the UE1 420 in the connection mode in steps 468 and 469.

In step 468, the EPC1 400 sends an S1-AP message informing the eNB1 410 of a direct connection setup request, and the eNB1 410 receiving the S1-AP message sends resource allocation information for direct connection setup, etc. To prepare. The S1-AP message and the RRC reconfiguration message of steps 468 and 469 may include a direct connection setup request message.

 The EPC1 400 may transmit a message including information on ProSe_ID2 and EPC ID_UE2 separately generated by the MME to the UE1 420 instead of the direct connection setup request message. Upon receiving the direct connection setup request message, UE1 420 accepts a D2D communication request from the terminal of ProSe_ID2 in step 470. Accordingly, in step 471 and 472, UE1 420 transmits an acceptance message for the D2D communication request, that is, a direct connection setup allowance message, to EPC1 400.

In step 471, the eNB1 410 receiving the RRC reconfiguration message transmits resource allocation information, etc. for the prepared direct connection setup to eNB2 440, which is accessed by the other terminal UE2 430, in step 472. The S1-AP message and steps 473 and 474 can be used. Alternatively, according to a modified example, the eNB1 410 receiving the RRC reconfiguration message in step 471 may directly transmit resource allocation information for the prepared direct connection setup to the other eNB2 440.

In step 473, EPC1 400 sends a direct connection setup allowance message to EPC2 450. In step 474, the EPC2 450 sends an S1-AP message informing the eNB2 440 of a direct connection setup request, and the S1-AP message may include resource allocation information for direct connection setup.

The S1-AP message of step 474 and step 475 and the RRC reconfiguration message may include a direct connection setup allowance message.

 In steps 474 and 475, EPC2 450 transmits a direct connection setup allowance message to UE2 430. In step 474, the EPC2 450 sends an S1-AP message informing the eNB2 440 of the direct connection setup request, and the S1-AP message may include resource allocation information for direct connection setup.

The S1-AP message of step 474 and step 475 and the RRC reconfiguration message may include a direct connection setup allowance message.

Thereafter, a process of setting up a direct connection radio bearer using a resource allocated by the eNB1 410 and the eNB2 440 is performed. For example, in step 476, the UE2 430 directly transmits a direct RRC connection request message to the UE1 420 to establish a radio resource control (RRC) connection with the UE1 420. 420). In step 477, UE1 420 transmits a direct RRC connection setup message to UE2 430. In step 478, UE2 430 transmits a direct RRC connection complete message to UE1 420. Accordingly, a radio bearer is generated. In step 479, UE1 420 and UE2 430 perform D2D communication through the radio bearer.

In addition, as another embodiment of the present specification, a process of transmitting a ProSe ID to an EPC device (for example, MME) in charge of mapping the ProSe ID of the EPC network to an identifier allocated from the EPC network will be described.

The ProSe ID information for the terminal will be transmitted in the process of updating location information to the HSS and receiving subscription information for the terminal in the process of entering the network as described in steps 453 of FIGS. 3 and 353 and 4. Can be. In this case, the ProSe ID already stored in the HSS may be transmitted in a manner that is allocated to the EPC equipment (eg, MME) in charge of mapping.

5 is a flowchart of a ProSe ID delivery process according to an embodiment of the present specification. The eNB 510 is located between the UE 500 and the EPC 520. EPC 520 may include, for example, MME, S-GW, P-GW, HSS. In step 521, the terminal 500 accesses the EPC network. In step 522, Prose configuration and Prose authentication are performed. At this time, the terminal 500 acquires a ProSe ID. In step 523, the terminal 500 transmits a separate Network Access Stratum (NAS) message, that is, a ProSeID registration request message to the EPC 520. The ProSeID registration request message includes the obtained ProSe ID. In step 524, the EPC 520 transmits a ProseID registration completion message to the UE 500 in response to the ProSeID registration request message. The ProseID registration completion message includes the ProSe ID. The EPC 520 delivers the ProSe ID to the EPC device (eg, MME) responsible for mapping the received ProSe ID and the identifier assigned by the UE 500 from the EPC 520, and the device receives the delivered ProSe ID. The mapping relationship between the ProSe ID and the identifier assigned by the UE 500 from the EPC 520 is stored. That is, the ProSe ID of the UE 500 and the identifier allocated by the EPC 520 by the UE 500 are connected to each other and stored.

6 is a flowchart of a ProSe ID delivery process according to another embodiment of the present specification.

The eNB 610 is located between the UE 600 and the EPC 620. EPC 620 may include, for example, MME, S-GW, P-GW, HSS. In step 621, the terminal 600 transmits an Attach Request message to the EPC 620. The attach request message includes a ProSe performance indicator. In step 622, the EPC 620 transmits an attach accept message to the UE 600 in response to the attach request message. In step 632, the UE 600 determines whether it has a valid ProSe_ID. In step 624, the UE 600 transmits an attach complete message to the EPC 620. If the UE 600 already has a valid ProSe_ID, the UE 600 includes the valid ProSe_ID in the attach complete message. The ProSe_ID is transmitted to the EPC device (for example, MME) responsible for mapping the ProSe_ID of the EPC 620 and the recognizer assigned from the EPC network. In step 625, the device stores a mapping relationship between the received ProSe ID and the assigned identifier in the EPC network. That is, the ProSe ID of the UE 500 and the identifier allocated by the EPC 520 by the UE 500 are connected to each other and stored.

Devices used in the embodiments of the present specification, that is, configuration entities of the terminal, the eNB and the EPC, for example, MME, S-GW, P-GW and HSS, respectively, may include a communication unit and a control unit. The communication unit of the configuration entities of the terminal, the eNB and the EPC transmits and receives a signal to perform an operation according to any one of the above-described embodiments. The control unit of the configuration entities of the terminal, the eNB and the EPC controls each device to operate according to any one of the above-described embodiments.

Claims (14)

In the method of device to device communication (D2D communication) of the first terminal,
Obtaining a proximity service identifier (Proximity Service ID; ProSe ID) of the first terminal or a user of the first terminal, used for D2D communication;
Generating an expression using the ProSe ID and an identifier of a first core network for the first terminal;
Broadcasting the representation including the ProSe ID and an identifier of the first core network;
Receiving a direct connection request message between devices from the second terminal through the second core network for the first core network and the second terminal;
Transmitting a direct connection permission message to the second terminal through the first core network and the second core network in response to the direct connection request message between the devices; And
And performing communication between the second terminal and the device,
The identifier of the first core network, the second terminal is used to identify the first core network to transmit a direct connection request message between the devices.
The communication method of claim 1, wherein the expression further comprises an identifier assigned by the first terminal to the first core network.
 The communication method according to claim 1, wherein the expression further comprises an identifier of an entity storing a mapping relationship between the ProSe ID and an identifier assigned by the first terminal to the first core network. In the method of device to device communication (D2D communication) of the second terminal,
Receiving an expression broadcast by the first terminal;
Obtaining a proximity service identifier (Proximity Service ID) of the first terminal or a user of the first terminal from the expression, and an identifier of a first core network for the first terminal;
Identifying the first core network to transmit a direct connection request message between devices based on the identifier of the first core network;
Transmitting a direct connection request message between the devices to the first terminal through the second core network for the first core network and the second terminal;
Receiving a direct connection permission message from the first terminal through the first core network and the second core network in response to the direct connection request message between the devices; And
And performing communication between the first terminal and the device using the ProSe ID.

The communication method of claim 4, wherein the expression further comprises an identifier assigned by the first terminal to the first core network.

The communication method of claim 4, wherein the expression further comprises an identifier of an entity storing a mapping relationship between a ProSe ID of the first terminal and an identifier assigned by the first terminal to the first core network.
A method for supporting device-to-device communication (D2D communication) of a communication entity in a first core network,
Receiving a direct connection request message between devices requesting a connection between a first terminal associated with the first core network and a second terminal associated with the second core network through the second core network;
Transmitting the direct connection request message between the devices to the first terminal after the first terminal is connected;
Receiving a direct connection permission message from the first terminal in response to a direct connection request message between the devices; And
And transmitting the direct connection permission message to the second terminal through the second core network,
The proximity service identifier (Proximity Service ID) of the first terminal and an expression including the identifier of the first core network are transmitted from the first terminal to the second terminal,
The identifier of the first core network, the second terminal is a communication support method, characterized in that used to identify the first core network to send a direct connection request message between the devices.

In the first terminal to perform a device to device communication (Device to Device Communication; D2D communication),
Transceiver; And
Acquiring a Proximity Service ID (ProSe ID) of the first terminal or a user of the first terminal, used for D2D communication, obtains the ProSe ID and the identifier of the first core network for the first terminal To generate an expression, broadcast the expression including the ProSe ID and the identifier of the first core network, and transmit the expression through the second core network to the first core network and the second terminal. 2 receives a direct connection request message between devices from the terminal, transmits a direct connection allowance message to the second terminal through the first core network and the second core network in response to the direct connection request message between the devices, and It includes a control unit for performing communication between the second terminal and the device,
The identifier of the first core network, the first terminal is characterized in that the second terminal is used to identify the first core network to transmit a direct connection request message between the devices.
The first terminal of claim 8, wherein the expression further includes an identifier assigned by the first terminal to the first core network.
The first terminal of claim 8, wherein the expression further comprises an identifier of an entity storing a mapping relationship between the ProSe ID and an identifier assigned by the first terminal to the first core network.
In the second terminal to perform a device to device communication (Device to Device Communication; D2D communication),
Transceiver; And
A first terminal receives an expression that is broadcast, and from the expression, a proximity service identifier (Proximity Service ID; ProSe ID) of the user of the first terminal or the first terminal, and a first terminal for the first terminal Acquire the identifier of the first core network, identify the first core network to transmit a direct connection request message between devices based on the identifier of the first core network, for the first core network and the second terminal A direct connection request message between the devices is transmitted to the first terminal through a second core network, and from the first terminal through the first core network and the second core network in response to the direct connection request message between the devices. Includes a control unit that receives a direct connection allowance message and performs communication between the first terminal and the device using the ProSe ID A second terminal, characterized in that.
The second terminal of claim 11, wherein the expression further comprises an identifier assigned by the first terminal to the first core network.
The second terminal of claim 11, wherein the expression further comprises an identifier of an entity storing a mapping relationship between a ProSe ID of the first terminal and an identifier assigned by the first terminal to the first core network.
A communication entity belonging to the first core network and supporting communication between devices of a communication entity (Device to Device Communication; D2D communication),
Transceiver; And
A direct connection request message between devices requesting connection between the first terminal associated with the first core network and the second terminal associated with the second core network is received through the second core network, and the first terminal is connected After that, the direct connection request message between the devices is transmitted to the first terminal, and a direct connection permission message is received from the first terminal in response to the direct connection request message between the devices, and the direct connection permission message is transmitted to the first terminal. It includes a control unit for transmitting to the second terminal through a two-core network,
The proximity service identifier (Proximity Service ID) of the first terminal and an expression including the identifier of the first core network are transmitted from the first terminal to the second terminal,
The identifier of the first core network, the communication entity characterized in that the second terminal is used to identify the first core network to transmit a direct connection request message between the devices.

Images