RADIO TERMINAL, CONTROL DEVICE, AND METHOD THEREFOR

Abstract

A radio terminal (1) communicates with a controlling entity (9) through a first cell (32S) managed by a first radio access network entity (31S) located in a radio access network (RAN) (3) and also through a core network connected to the RAN (3) in order to establish ProSe communication with a second radio terminal (2), and then starts the ProSe communication (103) with the second radio terminal (2) in the first cell (32S). The radio terminal (1) transmits or receives, to or from the controlling entity (9), first control information about a handover of the first and second radio terminals (1, 2) from the first cell (32S) to a second cell (32T) managed by a second radio access network entity (31T) located in the RAN (3). This contributes to improvement in an inter-base station handover of a radio terminal that is performing inter-terminal direct communication.

Claims

1. A method performed by a first radio terminal, the method comprising: communicating with a controlling entity through a first cell managed by a first radio access network entity located in a radio access network and through a core network connected to the radio access network, in order to establish Proximity Service (ProSe) communication with a second radio terminal; starting the ProSe communication with the second radio terminal in the first cell; and transmitting or receiving, to or from the controlling entity, first control information about a handover of the first and second radio terminals from the first cell to a second cell managed by a second radio access network entity located in the radio access network.

2-30. (canceled)

31. A first radio terminal comprising: at least one memory that stores a set of instructions; and at least one processor configured to execute the set of instructions to: communicate with a controlling entity through a first cell managed by a first radio access network entity located in a radio access network and through a core network connected to the radio access network, in order to establish Proximity Service (ProSe) communication with a second radio terminal; start the ProSe communication with the second radio terminal in the first cell; and transmit or receive, to or from the controlling entity, first control information about a handover of the first and second radio terminals from the first cell to a second cell managed by a second radio access network entity located in the radio access network.

32. The first radio terminal according to claim 31, wherein the set of instructions causes the at least one processor to receive the first control information from the controlling entity before initiation of the handover, or after initiation of the handover but before completion of the handover.

33. The first radio terminal according to claim 31, wherein the set of instructions causes the at least one processor to transmit the first control information to the controlling entity before initiation of the handover.

34. The first radio terminal according to claim 31, wherein the set of instructions causes the at least one processor to transmit the first control information to the controlling entity after initiation of the handover but before completion of the handover.

35. The first radio terminal according to claim 31, wherein the set of instructions causes the at least one processor to transmit the first control information to the controlling entity in response to detecting a change in a state of the ProSe communication in the first cell.

36. The first radio terminal according to claim 35, wherein the change in the state of the ProSe communication relates to a distance between the first and second radio terminals or to communication quality of the ProSe communication in the first radio terminal.

37. The first radio terminal according to claim 31, wherein the set of instructions causes the at least one processor to transmit the first control information to the controlling entity after completion of the handover.

38. The first radio terminal according to claim 33, wherein the first control information includes: an indication indicating an advance notice of the handover; an indication indicating an initiation of the handover; an indication indicating completion of the handover; or an indication indicating the second cell.

39. The first radio terminal according to claim 33, wherein the set of instructions further causes the at least one processor to receive second control information indicating a change in configuration for the ProSe communication, the second control information being transmitted from the controlling entity in response to the first control information.

40. The first radio terminal according to claim 39, wherein the second control information indicates preservation, modification, or deletion of the configuration for the ProSe communication.

41. A controlling entity comprising: at least one memory; and at least one processor configured to execute the set of instructions to: communicate with a first radio terminal through a first cell managed by a first radio access network entity located in a radio access network and through a core network connected to the radio access network, in order to establish Proximity Service (ProSe) communication between the first radio terminal and a second radio terminal; and transmit or receive, to or from at least one of the first and second radio terminals, first control information about a handover of the first and second radio terminals from the first cell to a second cell managed by a second radio access network entity located in the radio access network.

42. The controlling entity according to claim 41, wherein the set of instructions causes the at least one processor to transmit the first control information to at least one of the first and second radio terminals before initiation of the handover, or after initiation of the handover but before completion of the handover.

43. The controlling entity according to claim 41, wherein the set of instructions causes the at least one processor to receive the first control information from at least one of the first and second radio terminals before initiation of the handover.

44. The controlling entity according to claim 41, wherein the set of instructions causes the at least one processor to receive the first control information from at least one of the first and second radio terminals after initiation of the handover but before completion of the handover.

45. The controlling entity according to claim 41, wherein the set of instructions causes the at least one processor to receive the first control information, the first control information being transmitted in response to detection, by at least one of the first and second radio terminals, of a change in a state of the ProSe communication in the first cell.

46. The controlling entity according to claim 45, wherein the change in the state of the ProSe communication relates to a distance between the first and second radio terminals or to communication quality of the ProSe communication in the first radio terminal.

47. The controlling entity according to claim 41, wherein the set of instructions causes the at least one processor to receive the first control information from at least one of the first and second radio terminals after completion of the handover.

48. The controlling entity according to claim 43, wherein the first control information includes: an indication indicating an advance notice of the handover; an indication indicating an initiation of the handover; an indication indicating completion of the handover; or an indication indicating the second cell.

49. The controlling entity according to claim 43, wherein the set of instructions further causes the at least one processor to transmit to at least one of the first and second radio terminals, in response to the first control information, second control information indicating a change in configuration for the ProSe communication.

50-52. (canceled)

Description

BRIEF DESCRIPTION OF DRAWINGS

[0021] FIG. 1 shows a configuration example of a radio communication system according to some embodiments;

[0022] FIG. 2 shows a configuration example of a radio communication system according to some embodiments;

[0023] FIG. 3 is a flowchart showing an operation example of a radio terminal that is performed when radio terminals performing ProSe communication are handed over between base stations according to a first embodiment;

[0024] FIG. 4 is a flowchart showing an operation example of a ProSe function entity that is performed when radio terminals performing ProSe communication are handed over between base stations according to the first embodiment;

[0025] FIG. 5 is a sequence diagram showing an example of processes that are performed when radio terminals performing ProSe communication are handed over between base stations according to a second embodiment;

[0026] FIG. 6 is a sequence diagram showing an example of processes that are performed when radio terminals performing ProSe communication are handed over between base stations according to a third embodiment;

[0027] FIG. 7 is a sequence diagram showing an example of processes that are performed when radio terminals performing ProSe communication are handed over between base stations according to a fourth embodiment;

[0028] FIG. 8 is a sequence diagram showing an example of processes that are performed when radio terminals performing ProSe communication are handed over between base stations according to a fifth embodiment;

[0029] FIG. 9 is a sequence diagram showing an example of processes that are performed when radio terminals performing ProSe communication are handed over between base stations according to a sixth embodiment;

[0030] FIG. 10 is Block diagram showing a configuration example of a radio terminal; and

[0031] FIG. 11 is Block diagram showing a configuration example of a ProSe function entity.

DESCRIPTION OF EMBODIMENTS

[0032] Specific embodiments are explained hereinafter in detail with reference to the drawings. The same or corresponding elements are denoted by the same symbols throughout the drawings, and duplicated explanations are omitted as necessary for the sake of clarity.

[0033] Embodiments described below will be explained mainly using specific examples with regard to an Evolved Packet System (EPS). However, these embodiments are not limited to being applied to the EPS and may also be applied to other mobile communication networks or systems such as a 3GPP Universal Mobile Telecommunications System (UMTS), a 3GPP2 CDMA2000 system (1RTT, HRPD (High Rate Packet Data)), a Global System for Mobile communications (GSM (Registered Trademark))/General packet radio service (GPRS) system, and a WiMAX system.

First Embodiment

[0034] FIGS. 1 and 2 show a configuration example of a radio communication system according to this embodiment. Both a UE 1 and a UE 2 are radio terminals capable of performing ProSe (i.e., ProSe-enabled UEs), and they can establish a ProSe communication path 103 and perform ProSe direct communication (or ProSe communication, inter-terminal direct communication, or D2D communication) between them. The ProSe direct communication between the UEs 1 and 2 may be performed by using a radio communication technology that is also used to access a base station (eNodeB) (i.e., E-UTRA technology) or by using a WLAN radio technology (IEEE 802.11 radio technology).

[0035] Both an eNodeB 31S and an eNodeB 31T are entities located in a radio access network (i.e., E-UTRAN) 3, manage cells 32S and 32T, and are able to perform communication (101 and 102) with the UE 1 and the UE 2 on frequencies licensed to the E-UTRAN 3 by using the E-UTRA technology. Note that in this embodiment, an inter-cell handover (inter-base station handover) of the UEs 1 and 2 from the cell 32S managed by the eNodeB 31S to the cell 32T managed by the eNodeB 31T is explained. Accordingly, the eNodeBs 31S and 31T are referred to as a source eNodeB and a target eNodeB, respectively, and the cells 32S and 32T are referred to as a source cell and a target cell, respectively.

[0036] A core network (i.e., EPC) 4 includes a plurality of user-plane entities (e.g., a Serving Gateway (S-GW) 41 and a Packet Data Network Gateway (P-GW) shown in FIG. 2) and a plurality of control-plane entities (e.g., a Mobility Management Entity (MME) 43 and a Home Subscriber Server (HSS) 44 shown in FIG. 2). The user-plane entities relay user data of the UEs 1 and 2 between the E-UTRAN 3 and an external network (Packet Data Network (PDN)). The control-plane entities perform various types of control for the UEs 1 and 2 including mobility management, session management (bearer management), and billing management.

[0037] In order to start ProSe direct communication (103) in the source cell 32S, each of the UE 1 and the UE 2 attaches to the core network (i.e., EPC) 4 through the source eNodeB 31T, establishes a Packet Data Network (PDN) connection for communicating with a ProSe function entity 9, and transmits and receives ProSe control signaling to and from the ProSe function entity 9 through the E-UTRAN 3 and the EPC 4. The UEs 1 and 2 may use a ProSe discovery service provided by the ProSe function entity 9. The UEs 1 and 2 may receive from the ProSe function entity 9 a message indicating permission for the UEs 1 and 2 to activate ProSe discovery or ProSe direct communication. The UEs 1 and 2 may receive, from the ProSe function entity 9, configuration information (e.g., designation of radio resources and transmission power) for ProSe discovery or ProSe direct communication in the source cell 32S. Note that an interface (PC3 reference point) between the ProSe function and each of the UEs 1 and 2 depends on the user plane of the E-UTRAN 3 and the EPC 4, and accordingly the ProSe control signaling is transferred on this user plane. Therefore, as shown in FIG. 2, the ProSe function entity 9 communicates with the EPC 4 (i.e., the P-GW 42) through the SGi reference point, which is a reference point between a PDN Gateway (P-GW) 42 and a PDN.

[0038] The following provides an example of processes that are performed by the UEs 1 and 2 and the ProSe function entity 9 in relation to a handover of the UEs 1 and 2 from the source cell 32S to the target cell 32T. FIG. 3 is a flowchart showing an example of processes (300) performed by the UE 1. Note that the processes 300 shown in FIG. 3 may be performed by the UE 2 or by both of the UEs 1 and 2. In Block 301, the UE 1 communicates with the ProSe function entity 9 through a first cell (source cell 32S) and also through the EPC 4 in order to establish ProSe communication with another UE (UE 2). In Block 302, the UE 1 starts ProSe communication with the other UE (UE 2) in the first cell (source cell 32S). In Block 303, the UE 1 transmits or receives, to or from the ProSe function entity 9, control information about a handover from the first cell (source cell 32S) to a second cell (target cell 32T).

[0039] FIG. 4 is a flowchart showing an example of processes (400) performed by the ProSe function entity 9. In Block 401, the ProSe function entity 9 communicates with the first UE (UE 1) through the first cell (source cell 32S) and also through the EPC 4 in order to establish ProSe communication between the first and second UEs (UEs 1 and 2) in the first cell (source cell 32S). In Block 401, the ProSe function entity 9 may communicate with the UE 2 or may communicate with both of the UEs 1 and 2.

[0040] In Block 402, the ProSe function entity 9 transmits or receives, to or from at least one of the first and second UEs (UEs 1 and 2), control information about a handover of the first and second UEs (UEs 1 and 2) from the first cell (source cell 32S) to the second cell (target cell 32T). The control information about the handover transmitted from the ProSe function entity 9 to one of the first and second UEs (e.g., UE 1) may be forwarded to the other UE (e.g., UE 2) through the ProSe communication path 103. One of the first and second UEs (e.g., UE 1) may receive the control information about the handover from the other UE (e.g., UE 2) through the ProSe communication path 103 and transmit the received control information to the ProSe function entity 9.

[0041] Next, several examples of the content and transmission timing of the control information about the handover explained above with reference to FIGS. 3 and 4 are explained. In a first example, the control information about the handover may be transmitted from the ProSe function entity 9 to at least one of the UEs 1 and 2. In this case, the control information may indicate whether ProSe communication after the handover in the target cell 32T is permitted, or may indicate whether a handover to the target cell 32T while maintaining ProSe communication (i.e., a handover to the target cell 32T without stopping ProSe communication) is permitted. Additionally or alternatively, the control information may include configuration information for ProSe communication to be performed in the target cell 32T after the handover. This configuration information for the ProSe communication may indicate radio resources that can be used for the ProSe communication in the target cell 32T.

[0042] In this first example, the ProSe function entity 9 may transmit the control information about the handover to at least one of the UEs 1 and 2 before initiation of the handover. For example, the ProSe function entity 9 may transmit the control information when the configuration for the ProSe communication in the source cell 32S is performed (i.e., in Block 301 in FIG. 3), or when the configuration for the ProSe communication in the source cell 32S is updated. The ProSe function entity 9 may transmit the control information about the handover to at least one of the UEs 1 and 2 in response to receiving from at least one of the UEs 1 and 2 a request for the control information about the handover. In this first example, it is possible to prepare, before the handover, for the ProSe communication in the target cell 32T to be performed after the handover, and hence to prevent a delay in the handover which would otherwise be caused when the preparation of the ProSe communication in the target cell 32T is performed during the execution of the handover procedure.

[0043] In a second example, the control information about the handover may be transmitted from at least one of the UEs 1 and 2 to the ProSe function entity 9 before initiation of the handover. In this case, the control information may include an indication indicating an advance notice of the handover. Additionally or alternatively, the control information may include an indication indicating the target cell 32T or the target eNodeB 31T. Additionally or alternatively, the control information may indicate a state of the ProSe communication in the source cell 32S (e.g., used radio resources, communication quality, or throughput). Additionally or alternatively, the control information may include configuration information for the ProSe communication to be performed in the target cell 32T after the handover (e.g., an indication of radio resources that can be used for the ProSe communication in the target cell 32T). Note that the UE 1, the UE 2, or both may transmit the control information about the handover in response to detecting a change in the state of ProSe communication in the source cell 32S. The change in the state of the ProSe communication relates, for example, to the distance between the UE 1 and the UE 2 or to communication quality (e.g., reception power) of the ProSe communication in the UE 1 or the UE 2. In this second example, it is possible to prepare, before the handover, for the ProSe communication in the target cell 32T to be performed after the handover, and hence to prevent a delay in the handover which would otherwise be caused when the preparation of the ProSe communication in the target cell 32T is performed during the execution of the handover procedure.

[0044] In a third example, the control information about the handover may be transmitted from at least one of the UEs 1 and 2 to the ProSe function entity 9 after initiation of the handover but before completion of the handover. In this case, the control information may include an indication indicating the initiation of the handover. Additionally or alternatively, the control information may include an indication indicating the target cell 32T or the target eNodeB 31T. Additionally or alternatively, the control information may indicate a state of the ProSe communication in the source cell 32S (e.g., used radio resources, communication quality, or throughput). Additionally or alternatively, the control information may include configuration information for the ProSe communication to be performed in the target cell 32T after the handover (e.g., an indication of radio resources that can be used for the ProSe communication in the target cell 32T). In this third example, the ProSe function entity 9 can manage changes in the state (or in the configuration) of the ProSe communication caused by the handover and it is hence possible to prevent an occurrence of a mismatch between the configuration information regarding the ProSe communication held by the ProSe function entity 9 and the configuration regarding the ProSe communication in the UEs 1 and 2.

[0045] In a fourth example, the control information about the handover may be transmitted from at least one of the UEs 1 and 2 to the ProSe function entity 9 after completion of the handover. In this case, the control information may include an indication indicating the completion of the handover. Additionally or alternatively, the control information may include an indication indicating the target cell 32T or the target eNodeB 31T. Additionally or alternatively, the control information may indicate a state of the ProSe communication in the target cell 32T (e.g., used radio resources, communication quality, or throughput). Additionally or alternatively, the control information may include configuration information for the ProSe communication performed after the handover in the target cell 32T (e.g., an indication of radio resources that can be used for the ProSe communication in the target cell 32T). In this fourth example, the ProSe function entity 9 can manage changes in the state (or in the configuration) of the ProSe communication caused by the handover and it is hence possible to prevent an occurrence of a mismatch between the configuration information regarding the ProSe communication held by the ProSe function entity 9 and the configuration regarding the ProSe communication in the UEs 1 and 2.

Second Embodiment

[0046] This embodiment provides a specific example of the processes that are performed in relation to a handover of the UEs 1 and 2 from the source cell 32S to the target cell 32T explained in the first embodiment. Specifically, an example in which the ProSe function entity 9 transmits to at least one of the UEs 1 and 2, before initiation of the handover, control information about the handover is explained. A configuration example of a radio communication system according to this embodiment is similar to that shown in FIGS. 1 and 2.

[0047] FIG. 5 is a sequence diagram showing processes 500 according to this embodiment. In Blocks 501 and 502, the UEs 1 and 2 communicate with the ProSe function entity 9 through the source eNodeB 31S and the EPC 4 to start ProSe communication. In Block 509, the UEs 1 and 2 perform the ProSe communication in the source cell 32S. In Blocks 504 and 505, the ProSe function entity 9 transmits, before the handover, the control information about the handover. This control information may include, for example, an indication indicating whether the ProSe communication in the target cell 32T is permitted, or an indication indicating whether the handover to the target cell 32T while maintaining the ProSe communication is permitted. Additionally or alternatively, this control information may include configuration information for the ProSe communication in the target cell 32T.

[0048] In Blocks 506 and 507, each of the UE 1 and the UE 2 transmits a measurement report (UE measurement report) to the source eNodeB 31S. These measurement reports can be used for the source eNodeB 31S to determine whether the handover should be initiated. The condition for transmitting the measurement reports is configured in the UEs 1 and 2 by the source eNodeB 31S. The condition for transmitting the measurement report in the E-UTRA is, for example, an Event A3 (Neighbor becomes offset better than serving).

[0049] Block 508 corresponds to a handover preparation phase and Block 512 corresponds to a handover execution phase. Note that, in this specification, a handover (or a handover procedure) includes a handover preparation phase (block 508) and a handover execution phase (block 512). Therefore, an expression before a handover in this specification means before a handover preparation phase (block 508).

[0050] In the handover preparation phase (block 508), the source eNodeB 31S determines the initiation of the handover of the UEs 1 and 2 based on the measurement reports (block 509). In Block 510, the source eNodeB 31S sends a handover request (Handover Request) message to the target eNodeB 31T through an X2 interface (X2 reference point). The handover request may include an indication indicating that the UEs 1 and 2 are performing ProSe communication, or include configuration information for the ProSe communication. Upon receiving the handover request, the target eNodeB 31T prepares resources for the UEs 1 and 2 (e.g., bearer resources for E-UTRA communication (101 and 102 in FIGS. 1 and 2), Radio Resource Control (RRC) resources, and ProSe communication resources in the target cell 32T), and sends a handover acknowledgement message (Handover Request Ack) to the source eNodeB 31S (block 511). The handover acknowledgement message may indicate that the UEs 1 and 2 are permitted to perform the ProSe communication in the target cell 32T and indicate ProSe communication resources in the target cell 32T.

[0051] In the handover execution phase (block 512), the source eNodeB 31S sends handover command (Handover Command) messages to the UEs 1 and 2 (Blocks 513 and 514). The handover command messages may indicate radio resources for ProSe communication in the target cell 32T. Upon receiving the handover command messages, the UEs 1 and 2 synchronize with the target eNodeB 31T, access the target eNodeB 31T, and send a handover confirmation message (Handover Confirm) to the target eNodeB 31T (Blocks 515 and 516).

[0052] In Block 517, the UEs 1 and 2 start ProSe communication in the target cell 32T. The ProSe communication in Block 517 may be initiated when the control information about the handover received in Blocks 504 and 505 indicates the permission for the ProSe communication in the target cell. On the other hand, when the control information in Blocks 504 and 505 indicates that the ProSe communication in the target cell is not permitted or indicates that the handover to the target cell 32T while maintaining the ProSe communication is not permitted, the UEs 1 and 2 may stop the ProSe communication before or during the handover procedure (Blocks 508 and 512).

[0053] Although FIG. 5 shows an X2 handover based on direct X2 signaling between the eNodeB 31S and the eNodeB 31T, the handover of the UEs 1 and 2 may be an S1 handover based on S1-MME signaling between the EPC 4 (MME 43) and both of the eNodeBs 31S and 31T.

[0054] In this embodiment, it is possible to prepare, before the handover, for the ProSe communication to be performed in the target cell 32T after the handover, and hence to prevent a delay in the handover which would otherwise be caused when the preparation of the ProSe communication in the target cell 32T is performed during the execution of the handover procedure.

Third Embodiment

[0055] This embodiment provides a specific example of the processes that are performed in relation to a handover of the UEs 1 and 2 from the source cell 32S to the target cell 32T explained in the first embodiment. Specifically, an example in which the ProSe function entity 9 transmits to at least one of the UEs 1 and 2, in response to a request from the UE 1 or the UE 2, control information about the handover is explained. A configuration example of a radio communication system according to this embodiment is similar to that shown in FIGS. 1 and 2.

[0056] FIG. 6 is a sequence diagram showing processes 600 according to this embodiment. Processes in Blocks 601 to 603 are similar to those in Blocks 501 to 503 in FIG. 5. In Block 604, the UE 1 transmits a transmission request for the control information about the handover to the ProSe function entity 9 through the source eNodeB 31S (source cell 32S) and the EPC 4. The UE 1 may transmit this request in response to detecting a change in the state of the ProSe communication in the source cell 32S. The ProSe function entity 9 transmits the control information about the handover to the UE 1 in response to this request from the UE 1. The ProSe function entity 9 may also transmit the control information to the UE 2 in response to the request from the UE 1. Processes in Blocks 607 to 609 are similar to those in Blocks 506 to 517 in FIG. 5.

[0057] In this embodiment, it is possible to prepare, before the handover, for the ProSe communication to be performed after the handover in the target cell 32T, and hence to prevent a delay in the handover which would otherwise be caused when the preparation of the ProSe communication in the target cell 32T is performed during the execution of the handover procedure.

Fourth Embodiment

[0058] This embodiment provides a specific example of the processes that are performed in relation to a handover of the UEs 1 and 2 from the source cell 32S to the target cell 32T explained in the first embodiment. Specifically, an example in which at least one of the UEs 1 and 2 transmits to the ProSe function entity 9, before initiation of the handover, control information about the handover is explained. A configuration example of a radio communication system according to this embodiment is similar to that shown in FIGS. 1 and 2.

[0059] FIG. 7 is a sequence diagram showing processes 700 according to this embodiment. Processes in Blocks 701 to 703 are similar to those in Blocks 501 to 503 in FIG. 5. In Block 704, the UE 1 transmits, before the handover, the control information about the handover to the ProSe function entity 9. This control information may include, for example, at least one of an indication indicating an advance notice of the handover, an indication indicating the target cell 32T or the target eNodeB 31T, an indication indicating the state of the ProSe communication in the source cell 32S, and configuration information for the ProSe communication in the target cell 32T.

[0060] In Block 705, upon receiving the control information about the handover from the UE 1, the ProSe function entity 9 may transmit a configuration update massage for the ProSe communication to the UE 1 or to both of the UEs 1 and 2. The configuration update massage for the ProSe communication indicates preservation, modification (e.g., a change in a radio resource), or deletion (i.e., a stop of the ProSe communication) of the configuration for the ProSe communication between the UEs 1 and 2. The process in Block 705 may be omitted. Processes in Blocks 706 to 710 are similar to those in Blocks 506 to 517 in FIG. 5.

[0061] In this embodiment, it is possible to prepare, before the handover, for the ProSe communication to be performed in the target cell 32T after the handover, and hence to prevent a delay in the handover which would otherwise be caused when the preparation of the ProSe communication in the target cell 32T is performed during the execution of the handover procedure.

Fifth Embodiment

[0062] This embodiment provides a specific example of the processes that are performed in relation to a handover of the UEs 1 and 2 from the source cell 32S to the target cell 32T explained in the first embodiment. Specifically, an example in which at least one of the UEs 1 and 2 transmits control information about the handover to the ProSe function entity 9 after initiation of the handover but before completion of the handover is explained. A configuration example of a radio communication system according to this embodiment is similar to that shown in FIGS. 1 and 2.

[0063] FIG. 8 is a sequence diagram showing processes 800 according to this embodiment. Processes in Blocks 801 to 812 are similar to those in Blocks 501 to 503 and 506 to 514 in FIG. 5. In Block 813, in response to receiving a handover command message (Handover Command) from the source eNodeB 31S, the UE 1 transmits the control information about the handover to the ProSe function entity 9 through the source cell 32S and the EPC 4. This control information may include, for example, at least one of an indication indicating an initiation or execution of the handover, an indication indicating the target cell 32T or the target eNodeB 31T, and configuration information for the ProSe communication in the target cell 32T.

[0064] In Block 814, upon receiving the control information about the handover from the UE 1, the ProSe function entity 9 may transmit a configuration update massage for the ProSe communication to the UE 1 or to both of the UEs 1 and 2. The configuration update massage for the ProSe communication indicates preservation, modification (e.g., a change in a radio resource), or deletion (i.e., a stop of the ProSe communication) of the configuration for the ProSe communication between the UEs 1 and 2. The process in Block 814 may be omitted. Processes in Blocks 815 to 817 are similar to those in Blocks 515 to 517 in FIG. 5.

[0065] Although FIG. 8 shows an X2 handover based on direct X2 signaling between the eNodeB 31S and the eNodeB 31T, the handover of the UEs 1 and 2 may be an S1 handover based on S1-MME signaling between the EPC 4 (MME 43) and both of the eNodeBs 31S and 31T.

[0066] In this embodiment, the ProSe function entity 9 can manage changes in the state (or the configuration) of the ProSe communication caused by the handover, and it is hence possible to prevent an occurrence of a mismatch between the configuration information regarding the ProSe communication held by the ProSe function entity 9 and the configuration regarding the ProSe communication in the UEs 1 and 2.

[0067] Note that the UE 1 may transmit the control information about the handover after the transmission of the measurement report (block 804) and before the reception of the handover command message (block 811). However, transmitting by the UE 1 of the control information in response to reception of the handover command message as shown in FIG. 8 has the following advantage: the UE 1 can inform the ProSe function entity 9 of information about the target cell 32T that has been sent to the UE 1 by the handover command message (e.g., indication of the target eNodeB 31T, indication of the target cell 32T, information regarding permission for the ProSe communication in the target cell, and configuration for the ProSe communication in the target cell 32T).

Sixth Embodiment

[0068] This embodiment provides a specific example of the processes that are performed in relation to a handover of the UEs 1 and 2 from the source cell 32S to the target cell 32T explained in the first embodiment. Specifically, an example in which at least one of the UEs 1 and 2 transmits control information about the handover to the ProSe function entity 9 after completion of the handover is explained. A configuration example of a radio communication system according to this embodiment is similar to that shown in FIGS. 1 and 2.

[0069] FIG. 9 is a sequence diagram showing processes 900 according to this embodiment. Processes in Blocks 901 to 908 are similar to those in Blocks 501 to 503 and 506 to 517 in FIG. 5. In Block 909, after completion of the handover from the source cell 32S to the target cell 32T, the UE 1 transmits the control information about the handover to the ProSe function entity 9 through the source cell 32S and the EPC 4. This control information may include, for example, at least one of an indication indicating the completion of the handover, an indication indicating the target cell 32T or the target eNodeB 31T, and configuration information for the ProSe communication in the target cell 32T.

[0070] In Block 910, upon receiving the control information about the handover from the UE 1, the ProSe function entity 9 may transmit a configuration update massage for the ProSe communication to the UE 1 or to both of the UEs 1 and 2. The configuration update massage for the ProSe communication indicates preservation, modification (e.g., a change in a radio resource), or deletion (i.e., a stop of the ProSe communication) of the configuration for the ProSe communication between the UEs 1 and 2. The process in Block 910 may be omitted.

[0071] In this embodiment, the ProSe function entity 9 can manage changes in the state (or the configuration) of the ProSe communication caused by the handover, and it is hence possible to prevent an occurrence of a mismatch between the configuration information regarding the ProSe communication held by the ProSe function entity 9 and the configuration regarding the ProSe communication in the UEs 1 and 2.

[0072] Lastly, configuration examples of the UEs 1 and 2 and the ProSe function entity 9 according to the above-described embodiments are explained. FIG. 10 shows a configuration example of the UE 1. The UE 2 may have a configuration similar to that of the UE 1. Referring to FIG. 10, the UE 1 includes a wireless transceiver (or radio transceiver) 11, a processor 12, and a memory 13. The wireless transceiver 11 is used for communication (101 in FIGS. 1 and 2) with the E-UTRAN 3 (eNodeBs 31S and 31S) and also for the ProSe communication (103 in FIGS. 1 and 2). The wireless transceiver 11 may include a plurality of transceivers, for example, an E-UTRA (Long Term Evolution (LTE)) transceiver and a WLAN transceiver.

[0073] The processor 12 loads software (computer program) from the memory 13 and executes these loaded software, and thereby performs processes of the UE 1 related to the processes 300, 500, 600, 700, 800 or 900 explained in the above-described embodiments. The processor 12 may be, for example, a microprocessor, a Micro Processing Unit (MPU), or a Central Processing Unit (CPU). The processor 12 may include a plurality of processors.

[0074] The memory 13 consists of a combination of a volatile memory and a nonvolatile memory. The volatile memory is, for example, a Static Random Access Memory (SRAM), a Dynamic RAM (DRAM), or a combination of them. The nonvolatile memory is, for example, a Mask Read Only Memory (MROM), a Programmable ROM (PROM), a flash memory, a hard disk drive, or any combination of them. The memory 13 may include a storage that is remotely arranged from the processor 12. In this case, the processor 12 may access the memory 13 through an I/O interface (not shown).

[0075] In the example shown in FIG. 10, the memory 13 is used to store software modules including a ProSe module 14. The ProSe module 14 includes instructions and data necessary for performing processes of the UE 1 related to the processes 300, 500, 600, 700, 800 or 900 explained in the above-described embodiments. The processor 12 loads software modules including the ProSe module 14 from the memory 13 and executes these loaded modules, and thereby performing the processes of the UE 1 explained in the above-described embodiments.

[0076] FIG. 11 shows a configuration example of the ProSe function entity 9. Referring to FIG. 11, the ProSe function entity 9 includes a network interface 91, a processor 92, and a memory 93. The network interface 91 is used to communicate with a network node (e.g., P-GW 42 and HSS 44). The network interface 91 may include, for example, a Network Interface Card (NIC) conforming to the IEEE 802.3 series.

[0077] The processor 92 loads software (computer program) from the memory 93 and executes these loaded software, and thereby performs processes of the ProSe function entity 9 related to the processes 400, 500, 600, 700, 800 or 900 explained in the above-described embodiments. The processor 92 may be, for example, a microprocessor, an MPU, or a CPU. The processor 92 may include a plurality of processors.

[0078] The memory 93 consists of a combination of a volatile memory and a nonvolatile memory. The volatile memory is, for example, an SRAM, a DRAM, or a combination of them. The nonvolatile memory is, for example, an MROM, a PROM, a flash memory, a hard disk drive, or any combination of them. The memory 93 may include a storage that is located physically apart from the processor 92. In this case, the processor 92 may access the memory 93 through the network interface 91 or other I/O interfaces (not shown).

[0079] In the example shown in FIG. 11, the memory 93 is used to store software modules including a ProSe module 94. The ProSe module 94 includes instructions and data necessary for performing processes of the ProSe function entity 9 related to the processes 400, 500, 600, 700, 800 or 900 explained in the above-described embodiments. The processor 92 loads software modules including the ProSe module 94 from the memory 93 and executes these loaded modules, and thereby performing processes of the ProSe function entity 9 explained in the above-described embodiments.

[0080] As explained above with reference to FIGS. 10 and 11, each of the processors included in the UEs 1 and 2 and the ProSe function entity 9 according to the above-described embodiments executes one or more programs including instructions to cause a computer to perform an algorithm explained with reference to the drawings. These programs may be stored in various types of non-transitory computer readable media and thereby supplied to computers. The non-transitory computer readable media includes various types of tangible storage media. Examples of the non-transitory computer readable media include a magnetic recording medium (such as a flexible disk, a magnetic tape, and a hard disk drive), a magneto-optic recording medium (such as a magneto-optic disk), a Compact Disc Read Only Memory (CD-ROM), CD-R, CD-R/W, and a semiconductor memory (such as a mask ROM, a Programmable ROM (PROM), an Erasable PROM (EPROM), a flash ROM, and a Random Access Memory (RAM)). These programs may be supplied to computers by using various types of transitory computer readable media. Examples of the transitory computer readable media include an electrical signal, an optical signal, and an electromagnetic wave. The transitory computer readable media can be used to supply programs to a computer through a wire communication path such as an electrical wire and an optical fiber, or wireless communication path.

Other Embodiments

[0081] Each of the above-described embodiments may be used individually, or two or more of the embodiments may be appropriately combined with one another.

[0082] The above-described embodiments are explained by using specific examples mainly related to the EPS. However, these embodiments may be applied to other mobile communication systems such as a Universal Mobile Telecommunications System (UMTS), a 3GPP2 CDMA2000 system (1RTT, High Rate Packet Data (HRPD)), a Global System for Mobile communications (GSM)/General packet radio service (GPRS) system, and a mobile WiMAX system.

[0083] Further, the above-described illustrative embodiments are merely examples of applications of the technical ideas obtained by the inventor. Needless to say, these technical ideas are not limited to the above-described embodiments and various modifications can be made thereto.

[0084] This application is based upon and claims the benefit of priority from Japanese patent application No. 2014-206188, filed on Oct. 7, 2014, the disclosure of which is incorporated herein in its entirety by reference.

REFERENCE SIGNS LIST

[0085] 1 UE [0086] 2 UE [0087] 3 E-UTRAN [0088] 4 EPC [0089] 9 ProSe FUNCTION ENTITY [0090] 31S SOURCE eNodeB [0091] 31T TARGET eNodeB [0092] 32S SOURCE CELL [0093] 32T TARGET CELL [0094] 103 ProSe COMMUNICATION PATH