WO2015146910A1 - サーバ装置及び端末装置 - Google Patents
サーバ装置及び端末装置 Download PDFInfo
- Publication number
- WO2015146910A1 WO2015146910A1 PCT/JP2015/058735 JP2015058735W WO2015146910A1 WO 2015146910 A1 WO2015146910 A1 WO 2015146910A1 JP 2015058735 W JP2015058735 W JP 2015058735W WO 2015146910 A1 WO2015146910 A1 WO 2015146910A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- relay
- communication
- prose
- terminal device
- path
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/22—Parsing or analysis of headers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/74—Address processing for routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W40/00—Communication routing or communication path finding
- H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/04—Large scale networks; Deep hierarchical networks
- H04W84/042—Public Land Mobile systems, e.g. cellular systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/02—Terminal devices
- H04W88/04—Terminal devices adapted for relaying to or from another terminal or user
Definitions
- the present invention relates to a server device and the like.
- 3GPP The 3rd Generation Partnership Project
- EPS Evolved Packet System
- an access system connected to an EPS is considered including not only LTE but also a wireless LAN.
- 3GPP has a function for detecting the proximity between UEs (discovery) and a function for establishing direct communication between UEs without going through a core network or a base station in the specification of EPS (direct communication).
- EPS direct communication
- ProSe can communicate without going through the core network to which the base station or access network is connected, the concentration of the access network and core network can be avoided (confusion avoidance), and an offload effect can be expected.
- ProSe needs a service for searching for and detecting a communication target UE for direct communication in order to establish a direct communication path.
- ProSe is examining two methods as this detection method. The first is a method in which the UE directly detects (hereinafter “direct discovery”). The second is a method of detecting via an access network or a core network (hereinafter, “EPS discovery”).
- direct discovery a method in which the UE directly detects
- EPS discovery core network
- the ProSe service is provided by a mobile telecommunications carrier, and use of the ProSe service requires approval by the mobile telecommunications carrier. Therefore, in 3GPP, in order to realize the ProSe service, a ProSe server is required as a function unit that manages the ProSe service in the core network in the PDN (Packet Data Network) or the core network. That is, in ProSe, unlike tethering, a communication carrier is responsible for establishing a communication path for direct communication, authentication, and the like.
- ProSe it is considered to use two methods as a direct communication path between UEs.
- the first is a method using the LTE access technology.
- the second is a method using a wireless LAN (WLAN) access technology.
- WLAN wireless LAN
- non-public safety and public safety are defined.
- non-Public Safety a commercial service by a mobile communication carrier is assumed, and it can be used only when the UE is located in the LTE base station.
- public safety is expected to be used by disaster prevention radio and can be used not only when the UE is located in the LTE base station but also when the UE is not located in the LTE base station (eNB). it can.
- ProSe is also studying UE-to-Relay Network via Relay UE.
- the relay UE has established direct communication with at least one of the UEs, and can use communication via only the relay UE or from the relay UE via the access network or the core network.
- Direct communication between Relay UE and ProSe UE is switched based on whether the UE is within the coverage of the base station or other factors.
- 3GPP suggests that it is necessary to examine a service continuation method between ProSe direct communication and infrastructure communication via a conventional network.
- General Packet Radio Service (GPRS) enhancements Evolved Universal Universal Terrestrial Radio Access Network (E-UTRAN) access 3GPP TR23.703 Technical Specification Group Services and System Aspects, Study on architecture enhancements to support Proximity-based Services (ProSe)
- a UE terminal device establishes two types of communication paths: a path that directly communicates with at least one UE and a path that communicates via an infrastructure path such as EPC via a core network. Things need to be possible.
- the above two communication paths are switched depending on UE internal factors and external factors such as UE movement and environmental changes.
- the UE or the network needs to be able to determine path or communication path switching by detecting these factors.
- the present invention provides a terminal device or the like for the purpose of determining and executing switching of communication paths or paths of at least two terminal devices by a terminal device or server device Is to do.
- the server device of the present invention provides: Receiving a route information update request message transmitted from a second terminal device communicating with the first terminal device via a core network from the first terminal device;
- the route information request message includes at least identification information indicating that switching of communication is requested, Based on the identification information, select a third terminal device having a relay function, It is a response to the route information request message, transmits a route update instruction message including the information of the third terminal device to the first terminal device, and performs direct communication with the third terminal device using LTE. Instructing to communicate with the first terminal device, It is characterized by that.
- the server device of the present invention 1st communication which communicates via the core network of a 1st terminal device and a 2nd terminal device,
- the said 2nd terminal device communicates with a 3rd terminal device directly, and communicates with a 1st terminal device Led the switch to the second communication, Selecting the third terminal device having a relay function;
- a route update instruction message including information on the third terminal device is transmitted to the second terminal device to instruct switching to the second communication; It is characterized by that.
- the terminal device of the present invention A first terminal device that communicates with a second terminal device via a core network, By detecting a path switching trigger, a route information update request message including identification information indicating that at least communication switching is requested is transmitted to the server device. Receiving a route update instruction message including information of a third terminal device having a relay function selected by the server device from the server device; According to the route update instruction message, the third terminal device communicates with the second terminal device by performing direct communication using LTE, It is characterized by that.
- a server device or a terminal device can switch a path or a communication path between infrastructure communication via a network such as EPC and relay communication via direct communication with a relay UE, and can continue a service. Can do.
- FIG. 1 is a functional block diagram showing a schematic configuration example of a wireless communication system according to an embodiment of the present invention.
- a wireless communication system 1 shown in FIG. 1 is a network including an IP mobile communication network 3 and a PDN 5.
- a ProSe server 20 is connected to a PDN (Packet Data Network) 5, and a UE 10 is connected to the IP mobile communication network 3.
- PDN Packet Data Network
- the UE 10 in this embodiment is connected to a Relay UE (mobile station device, terminal device) 10A having a ProSe Relay function, a UE (mobile station device, terminal device) 10B and UE 10C having a ProSe function.
- a Relay UE mobile station device, terminal device
- UE mobile station device, terminal device
- UE 10C having a ProSe function.
- the PDN 5 and the UE 10 are connected via the IP mobile communication network 3.
- the relay UE 10A and the UE 10B may establish a communication path in ProSe direct communication.
- the Relay UE 10A can establish a direct communication channel with the UE 10C or another UE if the direct distance is sufficiently close.
- the ProSe server 20 is an authentication server for managing communication of the Relay UE 10A, UE 10B, and UE 10C.
- the ProSe server 20 is configured to be included in the PDN 5, but may be independent of the PDN 5.
- each UE 10 may be connected to the same mobile carrier network, may be connected to a different mobile carrier network, or may be a broadband network operated by a fixed carrier.
- the broadband network is an IP communication network operated by a telecommunications carrier that is connected by ADSL (Asymmetric Digital Subscriber Line) or the like and provides high-speed communication using a digital line such as an optical fiber.
- ADSL Asymmetric Digital Subscriber Line
- the network is not limited to these, and may be a network that performs wireless access using WiMAX (Worldwide Interoperability for Microwave Access) or the like.
- Each UE 10 (Relay UE 10A, UE 10B, UE 10C) is a communication terminal that is connected using an access system such as LTE or WLAN, and is equipped with a 3GPP LTE communication interface, a WLAN communication interface, or the like. It is possible to connect to an IP access network.
- the PDN 5 is a network that provides a network service that transmits and receives data in packets.
- the PDN 5 is a service network that provides a service based on the Internet or IMS.
- the PDN 5 is connected to the IP access network using a wired line or the like.
- a wired line or the like is constructed by ADSL or optical fiber.
- the present invention is not limited to this, and a wireless access network such as LTE, WLAN, or WiMAX (Worldwide Interoperability for Microwave Access) may be used.
- FIG. 2 is a detailed configuration example of the wireless communication system 1 shown in FIG.
- the configuration example of the wireless communication system 1 illustrated in FIG. 2 includes a UE 10 (any one of Relay UE 10A, UE 10B, and UE 10C), an IP mobile communication network 3, and a PDN 5. It goes without saying that a plurality of UEs can be connected to the IP mobile communication network 3 in addition to the UEs 10 described in this specification.
- the IP mobile communication network 3 includes a core network 9 and radio access networks (for example, LTE AN7c, WLAN ANb7b, WLAN ANa7a).
- the core network 9 includes an HSS (Home Subscriber Server) 32, an AAA (Authentication, Authorization, Accounting) 36, a PCRF (Policy and charging rules function) 34, a PGW (Packet Data Network Gateway) 38, and an ePDG (enhanced Packet Data Gateway) 40. , SGW (Serving Gateway) 42, and MME (Mobile Management Entity) 44.
- HSS Home Subscriber Server
- AAA Authentication, Authorization, Accounting
- PCRF Policy and charging rules function
- PGW Packet Data Network Gateway
- ePDG enhanced Packet Data Gateway
- SGW Serving Gateway
- MME Mobile Management Entity
- the radio access network may be composed of a plurality of different access networks. Each access network is connected to the core network 9. Furthermore, each UE 10 can be wirelessly connected to the radio access network.
- an LTE access network (LTE AN7c) that can be connected by an LTE access system and an access network (WLAN AN7a, 7b) that can be connected by a WLAN access system can be configured.
- LTE AN7c LTE access network
- WLAN AN7a, 7b WLAN access system
- the access network connectable by the WLAN access system includes a WLAN access network b (WLAN ANb7b) for connecting the ePDG 40 as a connection device to the core network 9, and a WLAN access network a (WLAN for connecting the PGW 38, the PCRF 34, and the AAA 36).
- WLAN access network b WLAN access network for connecting the PGW 38, the PCRF 34, and the AAA 36.
- ANa 7a can be configured.
- each device in the IP mobile communication network 3 is configured in the same manner as a conventional device in a mobile communication system using EPS, detailed description is omitted. Hereinafter, each device will be briefly described.
- the PGW 38 is connected to the PDN 5, SGW 42, ePDG 40, WLAN ANa 7 a, PCRF 34 and AAA 36, and delivers user data as a gateway device between the PDN 5 and the core network 9.
- the SGW 42 is connected to the PGW 38, the MME 44, and the LTE AN 7c, and performs user data delivery as a gateway device between the core network 9 and the LTE AN 7c.
- the MME 44 is connected to the SGW 42, the LTE AN 7c, and the HSS 32, and is an access control device that performs access control of the UE 10 via the LTE AN 7c.
- the HSS 32 is connected to the MME 44 and the AAA 36 and is a management node that manages subscriber information.
- the subscriber information of the HSS 32 is referred to when the access control of the MME 44 is performed, for example.
- the AAA 36 is connected to the PGW 38, the HSS 32, the PCRF 34, and the WLAN ANa 7a, and performs access control of the UE 10 connected via the WLAN ANa 7a.
- the PCRF 34 is connected to the PGW 38, the WLAN ANa 7a, the AAA 36, and the PDN 5, and performs QoS management for data delivery.
- the ePDG 40 is connected to the PGW 38 and the WLAN ANb 7b, and delivers user data as a gateway device between the core network 9 and the WLAN ANb 7b.
- each radio access network includes a device (for example, a base station device or an access point device) to which the UE 10 is actually connected.
- a device used for connection a device adapted to a radio access network can be considered.
- the LTE AN 7c includes the eNB 52.
- the eNB 52 is a radio base station to which the UE 10 is connected in the LTE access system, and the LTE AN 7c may be configured to include one or a plurality of radio base stations.
- the WLAN ANa 7a includes a WLAN APa 56 and a GW (Gateway) 58.
- the WLAN APa 56 is a radio base station to which the UE 10 is connected in a WLAN access system that is reliable to the operator operating the core network 9, and the WLAN ANa 7a includes one or more radio base stations. Good.
- the GW 58 is a gateway device of the core network 9 and the WLAN ANa 7a. Further, the WLAN APa 56 and the GW 58 may be configured by a single device.
- the WLAN ANb7b includes the WLAN APb54.
- the WLAN APb 54 is a radio base station to which the UE 1 is connected in the WLAN access system when a trust relationship is not established with the operator operating the core network 9, and the WLAN ANb 7b has one or more radio base stations. It may be configured to be included.
- the WLAN ANb 7b is connected to the core network 9 using the ePDG 40, which is a device included in the core network 9, as a gateway.
- the ePDG 40 has a security function for ensuring safety.
- the fact that the UE 10 is connected to each radio access network means that the UE 10 is connected to a base station apparatus, an access point, etc. included in each radio access network. Also via a base station device or access point.
- UE10B and UE10C correspond.
- These UEs only need to be wireless communication terminals including a ProSe function, and may be mobile phone terminals that transmit and receive data by wireless communication using the LTE access method, or devices in a form called machine-to-machine. Terminal devices that exchange information with each other may be used.
- FIG. 3 shows a functional configuration of the UE 10B in the present embodiment. Note that the functional configuration of the UE 10C is the same as that of the UE 10B, and thus description thereof is omitted.
- the UE 10B includes a control unit 100, a first transmission / reception unit 110 to which a transmission / reception antenna 112 is connected, a second transmission / reception unit 120 to which a transmission / reception antenna 122 is connected, and a storage unit 130.
- the control unit 100 is a functional unit for controlling the UE 10B.
- the control unit 100 is a functional unit that reads and executes various programs stored in the storage unit 130.
- it is constituted by a CPU or the like.
- the first transmission / reception unit 110 and the second transmission / reception unit 120 are functional units for performing wireless communication with an external terminal device or a base station device.
- the first transmission / reception unit 110 is a functional unit that transmits / receives wireless communication data using the LTE access method.
- the first transmission / reception unit 110 includes a transmission unit and a reception unit.
- the transmission unit can transmit control information via the LTE base station, and the reception unit transmits data and control information via the LTE base station. I can do things.
- the 2nd transmission / reception part 120 is a function part which can communicate directly with another UE with data, control information, etc. without going through an LTE base station.
- the second transmission / reception unit 120 includes a transmission unit and a reception unit. The transmission unit can transmit data and control information without going through an LTE base station.
- the transmission / reception unit 120 may be configured as one transmission / reception unit.
- the storage unit 130 is a functional unit that stores programs and data necessary for each operation of the UE 10B.
- the storage unit 130 includes, for example, a semiconductor memory, an HDD (Hard Disk Drive), or the like.
- the storage unit 130 stores a ProSe ID management table 132, an IP address management table 134, an outer IP address management table 136, a DCM state table 138, a path information table 142, and an In coverage flag 144.
- FIG. 4 shows an example of each information element stored in the storage unit 130.
- a description will be given with reference to FIG.
- FIG. 4A shows an example of the ProSe ID management table 132 stored in the storage unit 130 of the UE 10B.
- the ProSe ID management table 132 specifically stores a ProSe ID as an identifier.
- an identifier for identifying the UE 10B (for example, “ProSe ID B”) or an identifier for identifying the UE 10A that exists in the vicinity and can perform direct communication (for example, “ProSe ID A”). ) Is managed.
- the identifier (ProSe ID C) of the UE 10C that is the communication partner is also managed.
- the ProSe ID may be an ID for identifying each UE, an ID for identifying an application, or an ID indicating that the ProSe server 20 has authenticated the UE.
- the UE 10B can store a plurality of ProSe IDs, the identifier “ProSe ID B” of the own terminal (UE 10B), the identifier “ProSe ID C” of the communication partner (UE 10C), and a terminal associated as a Relay UE (Relay UE 10A) identifier “ProSe ID A” and identifiers of other UEs as well as the own terminal can be stored.
- the ProSe ID may include not only information for identifying each UE (Relay UE10A, UE10B, UE10C, etc.) but also information for identifying an application, information for identifying a communication business and a country.
- the IP address management table 134 is a table for managing IP addresses. For example, the UE identifier and the IP address are managed in association with each other and stored.
- the IP address management table 134 stores an identifier of the US 10B (for example, “UE10B”) and an IP address of the UE 10B (for example, “IP @ B1”) assigned when attaching to the IP mobile communication network.
- UE10B an identifier of the US 10B
- IP @ B1 an IP address of the UE 10B assigned when attaching to the IP mobile communication network.
- IP address “IP @ C1” of the UE 10C that is the communication partner and the IP address “IP @ A1” of the Relay UE 10A that can perform direct communication may be stored.
- the outer IP address management table 136 is a table for managing and storing outer IP addresses.
- FIG. 4C an example of the data structure of the outer IP address management table 136 is shown in FIG.
- FIG. 4C an example of the outer IP address management table 136 stored in the storage unit 130 of the UE 10B for the UE that has established a direct communication path is shown.
- the outer IP address of communication partner Relay UE 10A for example, “IP @ A2”
- the outer IP address of own terminal UE 10B used for the communication for example, “IP @ B2”.
- the outer IP address is not managed in the UE 10C in the present embodiment.
- the DCM state table 138 is a table for managing the state of DCM (direct connected mode) of the UE 10B in relation to each terminal device. That is, the DCM state is managed for each other UE.
- the DCM state table 138 As shown in FIG.
- the DCM state is memorize
- the route information table 142 is a table in which route information in which a communication partner is associated with a path is stored.
- the identification information of the Relay UE may be further associated with the route information and stored.
- the path information is stored for each UE with which the UE 10B communicates.
- route information table 142 An example of the data configuration of the route information table 142 will be described with reference to FIG. Here, it is stored whether communication is performed with a communication partner using a direct communication path, communication using infrastructure communication, or UE-to-Network Relay communication is performed using a certain Relay UE. That is, as shown in FIG. 4 (e), the UE 10A is connected through a "direct communication" route.
- Relay UE when UE-to-Network Relay communication is performed, a configuration that also indicates a route (Relay UE) may be adopted.
- route (infrastructure communication or direct communication) to Relay UE can be memorize
- UE10B and UE10A are performing direct communication. Also, it can be seen that the UE 10C is connected in the “UE-to-Network Relay” mode.
- the In coverage flag 144 is an area that stores the In coverage flag of the terminal itself.
- the UE 10B is in a state of being out of network access coverage (Out of coverage).
- the network access coverage refers to being located in an area configured by the LTE base station eNB 52.
- the Relay UE 10A may be a wireless communication terminal including the ProSe function and the ProSe Relay function, and may be a mobile phone terminal that transmits and receives data by wireless communication using the LTE access method. It may be a terminal device in which devices exchange information with each other in a form called. In the specification, when the UE 10A is used as a relay function, it may be described as a relay UE for clarity.
- the ProSe Relay function has a function of relaying traffic between a UE having a ProSe function and a core network.
- a UE having a ProSe Relay function establishes a direct communication path based on LTE, receives user data transmitted from the directly connected UE, and further transfers the received user data to the core network.
- the IP packet including the user data is transmitted to the user data transmission destination via the core network.
- the UE having the ProSe Relay function receives user data transmitted from the core network to the UE directly connected by establishing a direct communication path based on LTE, and further to the UE directly connecting the received user data. Forward.
- FIG. 5 shows a functional configuration of the UE 10A in the present embodiment.
- the UE 10 ⁇ / b> A is configured by including a first transmission / reception unit 310 (transmission / reception antenna 312), a second transmission / reception unit 320 (transmission / reception antenna 314), a relay signal generation unit 315, and a storage unit 330 in the control unit 300.
- the control unit 300 is a functional unit for controlling the UE 10A.
- the control unit 300 is a functional unit that reads and executes various programs stored in the storage unit 330.
- it is constituted by a CPU or the like.
- the first transmission / reception unit 310 identifies a relay signal transmitted via the LTE base station, outputs the relay signal to the relay signal generation unit 315, and the relay signal This is a functional unit having a function of inputting a signal output from the generation unit 315.
- the second transmitter / receiver 320 decapsulates a signal transmitted via LTE and transfers the signal to the relay signal generator 315, and the relay signal generator This is a functional unit having a function of encapsulating the signal input from 315 by the second transmitting / receiving unit 320.
- the relay signal generation unit 315 processes data input from the second transmission / reception unit 320 or the first transmission / reception unit 310 based on the control of the control unit 300, and the second transmission / reception unit 320 or the first transmission / reception unit 310. Output to.
- the signal received by the UE 10A is output to the second transmitting / receiving unit 320.
- the data input to the second transmission / reception unit 320 is decapsulated and output to the relay signal generation unit 315.
- the signal input to the Relay signal generation unit 315 executes processing instructed by the control unit 300.
- the signal input to the Relay signal generation unit 315 is input to the first transmission / reception unit 310.
- the first transmission / reception unit 310, the relay signal generation unit 315, and the second transmission / reception unit 320 are described as different configurations, but may be configured as one transmission / reception unit.
- the storage unit 330 is a functional unit that stores programs and data necessary for each operation of the UE 10A.
- the storage unit 330 includes, for example, a semiconductor memory, an HDD (Hard Disk Drive), or the like.
- the storage unit 330 stores a ProSe ID management table 332, an IP address management table 334, an outer IP address management table 336, a DCM state table 338, and an In coverage flag 340.
- FIG. 6 shows an example of each information element stored in the storage unit 330.
- the stored content differs for each terminal, the content managed by each table is the same as the table described in the UE 10B.
- the ProSe ID management table 332 shown in FIG. 6A is the ProSe ID management table 132
- the IP address management table 334 shown in FIG. 6B is the IP address management table 134
- the IP address management table 336 stores the outer IP address management table 136
- the DCM state table 338 shown in FIG. 6D stores the DCM state table 138
- the In coverage flag 340 shown in FIG. 6E stores the In coverage flag 144. Since the contents to be performed are the same, detailed description thereof is omitted.
- the ProSe ID management table 332 illustrated in FIG. 6A stores the identifiers of a plurality of UEs including the Relay UE 10A
- the IP address management table 334 illustrated in FIG. 6B includes the Relay UE 10A.
- the IP addresses of a plurality of UEs are stored, and the outer IP address management table 336 illustrated in FIG. 6C stores the outer IP addresses for direct communication for each UE, and the DCM state illustrated in FIG.
- the table 338 stores the DCM state between each UE and the Relay UE 10A, and the In coverage flag 340 shown in FIG. 6E stores the In coverage flag of the own terminal (Relay UE 10A).
- the ProSe server 20 is an authentication server managed by a mobile communication carrier that performs proximity detection by ProSe and communication by ProSe.
- the ProSe server 20 includes a control unit 200, a communication unit 210, and a storage unit 220.
- the control unit 200 is a functional unit for controlling the ProSe server 20.
- the control unit 200 is a functional unit that reads and executes various programs stored in the storage unit 220.
- the communication unit 210 is a functional unit for the ProSe server 20 to communicate. In this embodiment, it is an IP mobile communication network interface unit for connecting to the IP mobile communication network 3.
- the storage unit 220 is a functional unit that stores programs, data, and the like necessary for various operations of the ProSe server 20.
- the storage unit 220 includes, for example, a semiconductor memory, an HDD (Hard Disk Drive), or the like.
- the storage unit 220 stores a ProSe ID management table 222, an In coverage flag 224, and a UE location information management table 226.
- FIG. 8 shows an example of each information element stored in the storage unit 220.
- the stored contents differ for each terminal, but the contents of the ProSe ID management table 222 and the In coverage flag 224 are the same as the tables described in the UE 10B.
- the ProSe ID management table 222 shown in FIG. 8A is the same as the ProSe ID management table 132 and the In coverage flag 224 shown in FIG. 8B is the same as the In coverage flag 144, detailed description thereof is omitted. To do.
- the ProSe ID management table 222 shown in FIG. 8A stores the identifier of the UE registered as a UE having the ProSe function in the ProSe server 20, and the In coverage flag 224 shown in FIG. 8B. Stores the In coverage flag of the UE registered as a UE having the ProSe function in the ProSe server 20.
- the UE location information management table 226 is a table for managing UE location information registered in the ProSe server 20 as a UE that can use ProSe. As shown in FIG. 8C, the location information of the UE 10A and the UE 10B is “location information ID A”, and the location information of the UE 10C is “location information ID C”.
- the UE 10A and the UE 10B are in the vicinity, and direct communication is possible.
- the location information ID may be any ID that indicates location information of each UE 10 (Relay UE 10A, UE 10B, UE 10C) registered as a UE having the ProSe function in the ProSe server 20, and may be an eNB ID for identifying a base station, , TAI (Tracking Area ID) or cell ID may be used.
- the location information ID may be ECGI (E-UTRAN Cell Global ID).
- ECGI is an ID combining a PLMN (Public Land Mobile Network) ID and a cell ID, and represents location information of the UE.
- the ProSe server 20 acquires the ECGI from the MME when the PDN connection with the UE is established.
- FIG. 9 illustrates a conceptual diagram of path switching, communication path switching, and path or communication path selection executed in the present embodiment.
- Infrastructure communication refers to communication performed via a network such as EPC.
- infrastructure communication means communication for selecting a PGW as a GW to the PDN and establishing a PDN connection with the PDN.
- UE-to-Network Relay communication is communication performed via direct communication or infrastructure communication with the Relay UE 10A.
- the path is switched to the UE-to-Network Relay communication via the direct communication T901 between the UE 10B and the Relay UE 10A and the Relay communication T903 between the Relay UE 10A and the UE 10C while the service is continued, or the communication path Switch or select a path or channel.
- Relay communication is infrastructure communication for the purpose of UE-to-Network Relay communication, and the path is equivalent to conventional infrastructure communication, and is transmitted and received via a network such as EPC.
- the infrastructure communication between the UE 10B and the UE 10C is the relay communication by the infrastructure communication via the direct communication T901 between the UE 10B and the Relay UE 10A, and the relay UE 10A and the UE 10C, but the UE 10C and the Relay UE 10A. If the distance is sufficiently close, Relay communication may be performed by direct communication.
- FIG. 10A illustrates infrastructure communication between the UE 10B and the UE 10C.
- the UE 10B transmits data to the UE 10C using the path T1003 by infrastructure communication. That is, the UE 10C receives data from the UE 10B using the path T1003 through infrastructure communication.
- the UE 10C transmits data to the UE 10B by using the path T1005 by infrastructure communication. That is, the UE 10B receives data from the UE 10C using the path T1005 by infrastructure communication.
- the UE 10B is assigned and acquired the IP address “IP @ B1” from the core network 9 during the initial attach procedure.
- the core network 9 assigns “IP @ B1” to the UE 10B and notifies the IP address assigned to the UE 10B.
- the UE 10C is assigned and acquired the IP address “IP @ C1” from the core network 9 during the initial attach procedure.
- the core network 9 assigns “IP @ C1” to the UE 10C and notifies the IP address assigned to the UE 10C.
- FIG. 10B is a diagram illustrating UE-to-Network Relay communication between the UE 10B and the UE 10C.
- the UE 10B transmits data to the Relay UE 10A by direct communication using the path T1007. Further, the Relay UE 10A transmits data to the UE 10B by direct communication using the path T1013.
- the Relay UE 10A receives data using the path T1007 by direct communication from the UE 10B.
- the UE 10B receives data using the path T1013 through direct communication from the Relay UE 10A.
- Relay UE 10A and UE 10B use the IP address “IP @ A2” and IP address “IP @ B2” assigned by Relay UE 10A for direct communication as an outer IP to perform direct communication.
- the Relay UE 10A transmits data to the UE 10C by using the path T1009 by Relay communication via the network.
- the UE 10C transmits data to the Relay UE 10A using the path T1011 by Relay communication via the network.
- the UE 10C receives data from the relay UE 10A using the path T1009 by relay communication via the network.
- the Relay UE 10A receives data from the UE 10C using the path T1011 through Relay communication via the network.
- the Relay UE 10A, UE 10B, and UE 10C are attached to the network via the same EPC (T1001), but they may be connected via different EPCs.
- FIG. 11 shows an IP packet including specific user data transmitted and received by each UE (Relay UE 10A, UE 10B, UE 10C) on each path shown in FIG.
- FIG. 11A is an example of an IP packet that the UE 10B shown in FIG. 10A transmits to the UE 10C using the path T1003 by infrastructure communication. That is, this is an example of an IP packet that the UE 10C receives from the UE 10B using the path T1003 by infrastructure communication.
- the IP packet shown in FIG. 11A includes an IP header P1100 and a payload (PL) P1101 indicating that this IP packet is information from the UE 10B to the UE 10C.
- PL payload
- the payload is originally transmitted data excluding the header portion, and the payload portion includes user data that is application data.
- FIG.11 (b) is an example of the IP packet which UE10C shown to Fig.10 (a) transmits to UE10B using path T1005 by infrastructure communication. That is, it is an example of an IP packet that the UE 10B receives from the UE 10C using the path T1005 by infrastructure communication.
- the IP packet shown in FIG. 11B includes an IP header P1103 and a payload (PL) P1105 indicating that this IP packet is information from the UE 10C to the UE 10B.
- FIG.11 (c) is an example of the IP packet which UE10B shown in FIG.10 (b) transmits to Relay UE10A using the path
- the IP packet in FIG. 11C includes an outer IP header P1107 indicating that this IP packet is information from the UE 10B to the Relay UE 10A, an IP header P1100 indicating that the packet is transmitted from the UE 10B to the UE 10C, and a payload. P1101.
- the IP packet shown in FIG. 11 (c) is obtained by adding the outer IP header P1107 to the head of the IP packet that the UE 10B shown in FIG. 11 (a) transmits to the UE 10C by infrastructure communication.
- FIG. 11D is an example of an IP packet that the Relay UE 10A illustrated in FIG. 10B transmits to the UE 10C using the path T1009 by the Relay communication via the network. That is, this is an example of an IP packet that the UE 10C receives from the relay UE 10A using the path T1009 by relay communication via the network.
- the IP packet in FIG. 11D includes an outer IP header P1109 indicating that this IP packet is information from the Relay UE 10A to the UE 10C, an IP header P1100 indicating that the packet is transmitted from the UE 10B to the UE 10C, and a payload. P1101.
- the one obtained by removing the outer IP header P1109 is the same as that shown in FIG.
- FIG. 11E is an example of an IP packet that is transmitted from the UE 10C illustrated in FIG. 10B to the Relay UE 10A using the path T1011 by the Relay communication via the network.
- the Relay UE 10A is an example of a packet that is received from the UE 10C using the path T1011 by Relay communication via the network.
- FIG. 11 (e) is obtained by adding an outer IP header P1111 indicating that it is information transmitted by relay communication from the UE 10C to the relay UE 10A via the network, at the head of the packet of FIG. 11 (b).
- FIG.11 (f) is an example of the IP packet which UE10A shown in FIG.10 (b) transmits to UE10B using path
- FIG. 11 (f) is a diagram obtained by removing the outer IP header P1113 indicating that direct communication is performed from the Relay UE 10A to the UE 10B and the outer IP header P1111 of FIG. It is comprised by.
- the packet output from the UE 10B changes from FIG. 11 (a) to FIG. 11 (c). That is, the transmission information from the UE 10B to the UE 10C can update the route information from the infrastructure communication to the UE-to-Network Relay communication via the direct communication by adding the outer IP header P1107.
- the packet output from the UE 10C changes from FIG. 11 (b) to FIG. 11 (e). That is, the transmission information from the UE 10C to the UE 10B can update the path information from the infrastructure communication to the UE-to-Network Relay communication via the direct communication by adding the outer IP header P1111.
- FIG. 12 shows an IP packet including specific user data transmitted and received by each UE (Relay UE 10A, UE 10B, UE 10C) on each path shown in FIG.
- FIG. 12A is an example of an IP packet that the UE 10B shown in FIG. 10A transmits to the UE 10C using the path T1003 by infrastructure communication. That is, this is an example of an IP packet that the UE 10C receives from the UE 10B using the path T1003 by infrastructure communication.
- the IP packet in FIG. 12A includes an IP header P1200 and a payload P1201 indicating that this IP packet is information from the UE 10B to the UE 10C.
- FIG. 12B is an example of an IP packet transmitted from the UE 10C illustrated in FIG. 10A to the UE 10B using the path T1005 by infrastructure communication. That is, it is an example of an IP packet that the UE 10B receives from the UE 10C using the path T1005 by infrastructure communication.
- the IP packet shown in FIG. 12B includes an IP header P1203 and a payload P1205 indicating that this IP packet is information from the UE 10C to the UE 10B.
- FIG. 12C is an example of an IP packet that the UE 10B shown in FIG. 10B transmits to the Relay UE 10A by direct communication using the path T1007. That is, the Relay UE 10A is an example of an IP packet received using the path T1007 by direct communication from the UE 10B.
- the IP packet in FIG. 12C includes an outer IP header P1207 indicating that this IP packet is information from the UE 10B to the Relay UE 10A, an IP header P1200 indicating that the packet is a packet transmitted from the UE 10B to the UE 10C, and a payload. P1201.
- the IP packet shown in FIG. 12C is obtained by adding the outer IP header P1207 to the head of the IP packet that the UE 10B shown in FIG. 12A transmits to the UE 10C.
- FIG. 12D is an example of an IP packet that the Relay UE 10A illustrated in FIG. 10B transmits to the UE 10C using the path T1009 by Relay communication via the network. That is, this is an example of an IP packet that the UE 10C receives from the relay UE 10A using the path T1009 by relay communication via the network.
- FIG. 12D is configured by removing the outer IP from FIG. 12C (equivalent to FIG. 12A).
- FIG. 12E shows an example of an IP packet that the UE 10C shown in FIG. 10B transmits to the Relay UE 10A using the path T1011 by Relay communication via the network.
- the Relay UE 10A is an example of a packet that is received from the UE 10C using the path T1011 by Relay communication via the network.
- FIG. 12 (e) is obtained by adding an outer IP header P1209 indicating that the information is transmitted by relay communication from the UE 10C to the relay UE 10A via the network, at the head of the packet in FIG. 12 (b).
- FIG. 12F is an example of an IP packet that the UE 10A illustrated in FIG. 10B transmits to the UE 10B by direct communication using the path T1013. That is, it is an example of a packet that the UE 10B receives from the Relay UE 10A using the path T1013 through direct communication.
- the Relay UE 10A that has received the packet of FIG. 12 (e) from the UE 10B outputs the packet of FIG. 12 (f).
- FIG. 12 (f) is obtained by removing the outer IP header P 1211 indicating direct communication from the UE 10 ⁇ / b> A to the UE 10 ⁇ / b> B and the outer IP header P ⁇ b> 1209 of FIG. It is configured.
- the packet output from the UE 10B changes from FIG. 12 (a) to FIG. 12 (c). That is, the transmission information from the UE 10B to the UE 10C can update the route information from the infrastructure communication to the UE-to-Network Relay communication via the direct communication by adding the outer IP header P1207.
- the packet output from the UE 10C changes from FIG. 12 (b) to FIG. 12 (e). That is, the transmission information from the UE 10C to the UE 10B can update the route information from the infrastructure communication to the UE-to-Network Relay communication via the direct communication by adding the outer IP header P1209.
- FIG. 13 shows an example of an IP packet including specific user data that is transmitted / received and processed by each UE (Relay UE 10A, UE 10B, UE 10C) in each path shown in FIG.
- FIG. 13A is an example of an IP packet transmitted from the UE 10B illustrated in FIG. 10A to the UE 10C using the path T1003 by infrastructure communication. That is, this is an example of an IP packet that the UE 10C receives from the UE 10B using the path T1003 by infrastructure communication.
- the IP packet in FIG. 13A includes an IP header P1300 and a payload P1301 indicating that this IP packet is information from the UE 10B to the UE 10C.
- the IP header P1300 and the payload P1301 are the same as the IP header P1100 and the payload P1101 in FIG.
- FIG.13 (b) is an example of the IP packet which UE10C shown to Fig.10 (a) transmits to UE10B using path T1005 by infrastructure communication. That is, it is an example of an IP packet that the UE 10B receives from the UE 10C using the path T1005 by infrastructure communication.
- the IP packet in FIG. 13B is configured by an IP header P1303 and a payload P1305 indicating that this IP packet is information from the UE 10C to the UE 10B. Note that the IP header P1303 and the payload P1305 are the same as the IP header P1103 and the payload P1105 in FIG.
- FIG. 13C is an example of an IP packet that is transmitted from the UE 10B illustrated in FIG. 10B to the Relay UE 10A by direct communication using the path T1007. That is, the Relay UE 10A is an example of an IP packet received using the path T1007 by direct communication from the UE 10B.
- the IP packet in FIG. 13C is an outer IP header P1307 indicating that this IP packet is direct communication from the UE 10B to the Relay UE 10A, and an IP header P1300 indicating that the packet is a packet transmitted from the UE 10B to the UE 10C. It is composed of a payload P1301. That is, the outer IP header P1307 is added to the head of the packet in FIG.
- FIG.13 (d) is a packet which Relay UE10A produces in Relay UE10A, when FIG.13 (c) is received from UE10B.
- FIG. 13D removes the outer IP header P1307 from FIG. 13C and adds a path control header P1309 between the IP header P1300 and the payload P1301.
- the route control header P1309 is used to specify a Relay UE used in Relay communication.
- FIG. 13E is an example of an IP packet that is transmitted from the Relay UE 10A illustrated in FIG. 10B to the UE 10C using the path T1009 by Relay communication via the network. That is, this is an example of an IP packet that the UE 10C receives from the relay UE 10A using the path T1009 by relay communication via the network.
- the Relay UE 10A converts FIG. 13 (d) to FIG. 13 (e) immediately before transmission.
- FIG. 13E includes an IP header P1313 indicating that the packet is from the Relay UE 10A to the UE 10C, a path control header P1311, and a payload P1301.
- the route control header P1311 indicates that the actual transmission source is the UE 10B.
- the Relay UE 10A transmits the IP packet shown in FIG. 13 (e) to the UE 10C after converting FIG. 13 (d) into FIG. 13 (e).
- FIG. 13 (f) shows a packet generated in the UE 10C when the transmission from the UE 10C to the UE 10B is switched from the infrastructure communication to the UE-to-Network Relay communication.
- FIG. 13F includes an IP header P1303 indicating that the information is from the UE 10C to the UE 10B, an end point option header P1315, and a payload P1305.
- FIG. 13F shows an end point option header P1315 inserted between the IP header P1303 and the payload P1305 in FIG.
- the end point option header P1315 is a header for indicating an end point entity, but here, the IP address of the UE 10A which is a Relay UE is included instead.
- FIG. 13G is an example of an IP packet that the UE 10C illustrated in FIG. 10B transmits to the Relay UE 10A using the path T1011 by Relay communication via the network.
- the Relay UE 10A is an example of a packet that is received from the UE 10C using the path T1011 by Relay communication via the network.
- FIG. 13G is an example of an IP packet including specific user data of the path T1011 in FIG.
- FIG. 13G includes an IP header P1319 indicating that the information is from the UE 10C to the Relay UE 10A, an end point option header P1317, and a payload P1305.
- FIG. 13H is an example of an IP packet that the UE 10A illustrated in FIG. 10B transmits to the UE 10B by direct communication using the path T1013. That is, it is an example of a packet that the UE 10B receives from the Relay UE 10A using the path T1013 through direct communication.
- FIG. 13 (h) is an example of an IP packet including the specific user data of FIG. 10 (b).
- the Relay UE 10A that has received the packet of FIG. 13 (g) from the UE 10C outputs the packet of FIG. 13 (h).
- FIG. 13H includes an outer IP header P1321 indicating direct communication from the UE 10A to the UE 10B, an IP header P1303 indicating information from the UE 10C to the UE 10B, and a payload P1305.
- the ProSe server 20 needs to register and manage each UE (Relay UE 10A, UE 10B, UE 10C) as a UE having the ProSe function for the purpose of the service authentication of each UE by the ProSe server 20. is there. Further, when each UE 10 (Relay UE 10A, UE 10B, UE 10C) is registered in the ProSe server 20, the core network 9 needs to assign a ProSe ID to each UE 10.
- the ProSe ID here may be authentication information indicating that the ProSe server 20 has authenticated the UE.
- FIG. 14 shows an example of processing until the UE 10A is registered as a ProSe UE in the ProSe server 20 and acquires the ProSe ID from the ProSe server 20. Note that the procedure in which the UE 10B and the UE 10C register with the ProSe server 20 as a ProSe UE and acquire the ProSe ID from the ProSe server 20 is the same as that in the UE 10A, and thus the description thereof is omitted.
- the UE 10A performs an initial attach procedure (S1002). More specifically, the UE 10A transmits an attach request message to the MME 44 to start an attach procedure, and the UE 10A is a communication path used for infrastructure communication with the PGW 38 selected by the MME 44 based on the attach request message. Establish a PDN connection. Furthermore, the UE 10 ⁇ / b> A acquires an IP address used for infrastructure communication from the core network 9. In other words, the core network 9 assigns an IP address to the UE 10A based on the attach request message transmitted by the UE 10A.
- the UE 10A sends a registration request as a ProSe UE to the ProSe server 20 (S1004).
- the ProSe server 20 assigns a ProSe ID to the UE 10A (S1006).
- the ProSe server 20 transmits a ProSe registration response to the UE 10A including the ProSe ID (ProSe ID A) assigned to the UE 10A (S1008).
- the UE 10A receives the ProSe registration response from the ProSe server 20, and acquires the ProSe ID (ProSe ID A) assigned to the UE 10A. After acquiring the ProSe ID, the UE 10A may store the ProSe ID in the ProSe ID management table 332 in the storage unit 330.
- the registration request transmitted from the UE 10A to the ProSe server 20 may request authentication for receiving a service related to ProSe. Further, the ProSe server 20 may confirm that the service can be provided to the UE 10A, and may notify the UE 10A of the authentication by transmitting a ProSe registration response.
- the ProSe server 20 may assign a ProSe ID by authenticating the service, and the UE 10A and the ProSe server 20 may use the ProSe ID as authentication information indicating that the service has been authenticated.
- FIG. 15 is a diagram for explaining the service continuation procedure procedure.
- the UE 10B indicates a process of switching the path or communication path from the infrastructure communication T905 to the UE-to-Network Relay communication via the direct communication T901 and the Relay communication T903 by detecting the trigger.
- description is made using only the components used for the description of the processing, and for example, description of other devices (such as PGW) is omitted.
- each function when each function wants to give an operation instruction or a request to a communication partner, it is described as adding a flag called an indication flag.
- information indicating that the function is requested is identified by a flag.
- the request may be made by transmitting a route information update request message, for example, by defining a route information update request message. More specifically, a device that gives a request or an instruction may transmit a request message including a message type for requesting route information update to the requesting partner.
- Indication flag1 An information element indicating an instruction or a request included in a signal transmitted from the UE 10B to the ProSe server 20.
- Indication flag 2 An information element indicating an instruction or a request included in a signal transmitted from the ProSe server 20 to the UE 10B.
- Indication flag3 An information element indicating an instruction or a request included in a signal transmitted from the ProSe server 20 to the UE 10C.
- “indication flag 1” is designated from the communication path of infrastructure communication T905 to the communication path of UE-to-Network Relay communication or from the communication path of UE-to-Network Relay communication to infrastructure communication T905. It may be a flag indicating that permission for switching communication between UEs is requested.
- the UE 10B transmits information including “indication flag 1” to the ProSe server 20, so that the UE 10B switches the communication path between the UE 10B and the UE 10C from the infrastructure communication T905 to the UE-to-Network Relay communication to the ProSe server 20. You may ask for permission.
- “indication flag 1” requests that permission to switch communication between UEs designated as a UE-to-Network Relay communication channel with the designated UE as a Relay UE from the communication channel of the infrastructure communication T905. It may be a flag to indicate.
- the UE 10B transmits a route information update request including “indication flag 1” to the ProSe server 20, so that the UE 10B communicates the communication path between the UE 10B and the UE 10C to the ProSe server 20 from the infrastructure communication T905 via the relay UE 10A.
- You may request permission to switch to UE-to-Network Relay communication.
- “indication flag 1” may be a flag indicating that selection of a Relay UE to be connected is instructed. That is, the UE 10B may request the ProSe server 20 to select a Relay UE to which the UE 10B is connected by transmitting information including the “indication flag 1” to the ProSe server 20.
- “indication flag 1” instructs to select a relay UE to be connected and to notify the selected relay UE to other UEs such as a transmission source UE of “indication flag 1” and a communication partner of the transmission source UE.
- the flag shown may be used. That is, by transmitting information including “indication flag 1” to the ProSe server 20, the UE 10B selects the Relay UE to which the UE 10B is connected to the ProSe server 20, and selects the selected Relay UE as another UE such as the UE 10B or the UE 10C. You may request to notify the UE.
- “indication flag 1” instructs to select a relay UE to be connected and to instruct other UEs such as a transmission source UE and a communication partner of the transmission source UE to establish a communication path to the selected relay UE.
- the flag shown may be used.
- the UE 10B transmits information including “indication flag 1” to the ProSe server 20, the UE 10B selects the Relay UE to which the UE 10B is connected to the ProSe server 20, and the other UEs such as the UE 10B and the UE 10C receive the Relay UE. It may be requested to instruct the establishment of a direct communication channel.
- “indication flag 1” may indicate a meaning obtained by combining the requests and instructions described so far.
- “indication flag 2” may be a flag indicating that the infrastructure communication T905 is requested to switch to UE-to-Network Relay communication via the Relay UE 10A.
- the ProSe server 20 transmits a route information update instruction including “Indication flag 2” to the UE 10B, so that the ProSe server 20 communicates with the UE 10B from the infrastructure communication T905 to the relay UE 10A through direct communication with the UE 10B.
- Update of route information may be requested for UE-to-Network Relay communication, or update of route information may be requested for UE-to-Network Relay communication via infrastructure communication with Relay UE 10A.
- “Indication flag 2” may be a flag indicating a request for confirming the DCM state with the Relay UE. That is, the ProSe server 20 transmits a route information update instruction including “indication flag 2” and the identifier (ProSe ID A) of the relay UE 10A to the UE 10B, so that the ProSe server 20 transmits a DCM (Direct Connection) between the UE 10B and the relay UE 10A to the UE 10B. Confirmation of the state of “Management” may be requested.
- “Indication flag 2” confirms the DCM status with the Relay UE, and if the DCM status is in idle mode, instructs the establishment of a communication path. If it is in connected mode, the processing is not particularly required.
- the flag shown may be used. For example, when the ProSe server 20 transmits a route information update instruction including “indication flag 2” to the UE 10B, the ProSe server 20 confirms the DCM state with the Relay UE 10A to the UE 10B, and the Relay UE 10A when the DCM state is the idle state. The establishment of a direct communication path may be requested.
- the DCM state is a connection state of a direct communication path between UEs, and there are an idle mode and a connected mode.
- the idle mode is a state in which a direct connection by a NAS (Non-Access-Stratum) signal is not established between UEs
- the connected mode is a state in which a NAS signal connection is established.
- “indication flag 2” may indicate a meaning obtained by combining the requests and instructions described so far.
- “indication flag 3” requests switching from infrastructure communication T905 to UE-to-Network Relay communication via Relay UE 10A, or switching from UE-to-Network Relay communication to infrastructure communication T905. It may be a flag indicating what to do.
- the ProSe server 20 transmits a route information update instruction including “indication flag 3” to the UE 10C, so that the ProSe server 20 communicates with the UE 10B from the infrastructure communication T905 to the relay UE 10A via the direct communication with the UE 10C.
- Update of route information may be requested for UE-to-Network Relay communication, or update of route information may be requested for UE-to-Network Relay communication via infrastructure communication with Relay UE 10A.
- “indication flag 1” includes a request to switch a path or a communication path, a request to select a Relay UE connected to the UE 10B, and a request to notify the UE 10B and the UE 10C of the Relay UE.
- the flag indicates a request for instructing the UE 10B to establish a communication path to the Relay UE.
- “indication flag 2” in FIG. 15 is a request for confirming the DCM state to UE 10B, a request for establishing a direct communication path when the result of DCM state confirmation is idle mode, and relay UE 10A from infrastructure communication T905. This is a flag indicating a request for an instruction to update route information in UE-to-Network Relay communication via direct communication T901.
- the UE 10B and the UE 10C transmit and receive data via the infrastructure communication T905 as shown in FIG. 10A (S1502). At this time, it is assumed that UE 10B and UE 10C are within the coverage of network access.
- the network access coverage means being located in an area configured by the LTE base station eNB 52.
- the packets shown in FIGS. 11A and 11B are transmitted and received.
- the UE 10B detects a path switching trigger (S1504).
- the trigger for switching the path to UE-to-Network Relay communication is not particularly limited, and for example, the UE 10B may detect that its own terminal has gone out of the network coverage.
- the UE 10B sends a route information update permission request to the ProSe server 20 triggered by S1504 (S1506).
- the route information update permission request in S1506 may include “ProSe ID B” that identifies the UE 10B, may include “ProSe ID C” that identifies the UE 10C of the communication partner, and “location information of the UE 10B” "May be included,” indication flag1 "may be included, and a plurality of these information elements may be included.
- the ProSe server 20 When the ProSe server 20 receives the route information update permission request from the UE 10B, the ProSe server 20 receives the route information update permission request including the location information of the UE 10B, whereby the UE 10B managed by the ProSe server 20 The UE location information management table 226 is updated.
- the ProSe server 20 When the ProSe server 20 receives a route information update permission request including “indication flag 1” or receives a message including the request, the UE 10B performs infrastructure communication based on “indication flag 1” or based on the request. It may be authenticated from T905 that the communication is switched to UE-to-Network Relay communication.
- the ProSe server 20 receives a route information update permission request including “indication flag 1” or receives a message including the request
- the UE 10B connects based on “indication flag 1” or based on the request.
- the Relay UE to be selected is selected (S1508).
- the selection method of Relay UE10A is not specifically limited, For example, you may select UE which is near to UE10B from the positional information on each UE memorize
- the ProSe server 20 transmits a route information update instruction for notifying the selected Relay UE to the UE 10B based on S1508 or S1506 (S1510). If the Relay UE cannot be selected in S1508, S1510 and subsequent steps are not executed.
- the route information update instruction transmitted in S1510 may include the ProSe ID A of the Relay UE 10A selected as the Relay UE, or may include the ProSe ID C of the UE 10C as the transmission destination for updating the route information.
- “Indication flag 2” may be included, and a plurality of these information elements may be included.
- ProSe server 20 When the ProSe server 20 receives a route information update permission request including “indication flag 1” or selects a Relay UE (S1508), or when the ProSe server 20 transmits a route information update instruction (S1510), ProSe The server 20 transmits a route information update instruction to the UE 10C (S1512).
- the route information update instruction in S1512 may be performed at the same time as S1506 or at any timing after S1506. In this embodiment, it is assumed that after S1506, the process waits until a timing at which a rejection response may be returned.
- the route information update instruction in S1512 may include the ProSe ID B of the UE 10B, may include the ProSe ID A of the Relay UE 10A selected as the Relay UE, and may include “indication flag 3”. Multiple information elements may be included.
- the UE 10B receives the route information update instruction from ProSe server 20 (S1510).
- the indication information update instruction received by the UE 10B from the ProSe server 20 includes “indication flag 2”, or when a message including a request is received, the UE 10B may communicate with the UE 10B based on the “indication flag 2” or based on the request.
- a DCM (Direct Connection Management) state between the UEs 10A is confirmed (S1514).
- UE10B confirms the DCM state between UE10A, and performs the process (S1515) in idle mode. Note that the UE 10B and the UE 10A are in idle mode, and the UE 10B can reject direct communication with the UE 10A. In that case, the UE 10B transmits a rejection signal to the ProSe server 20.
- S1515 includes S1516 and S1518.
- the UE 10B When the UE 10B determines that the DCM state between the UE 10B and the UE 10A is the idle mode in S1514, the UE 10B first transmits a communication request directly to the UE 10A (S1516).
- Relay UE10A receives a direct communication request from UE10B and transmits a direct communication approval to UE10B (S1518).
- S1518 may include an outer IP address (IP @ A2, IP @ B2) assigned to each UE (UE10A and UE10B) by Relay UE10A, and identifier ProSe ID (ProSe ID A, ProSe ID of UE10A and UE10B). B) may be included, and a plurality thereof may be included.
- IP @ A2 and IP @ B2 The outer IP addresses (IP @ A2 and IP @ B2) between the UE 10A and the UE 10B are used by each UE (UE 10A and UE 10B) to encapsulate the IP packet in order for the UE 10A and UE 10B to communicate directly.
- the UE 10B confirms the DCM status of the UE 10A and the UE 10B (S1514), and updates the route information table 142 of the UE 10B based on the DCM status or based on the reception of the direct communication approval (S1518) from the Relay UE 10A (S1522). ).
- the route information table 142 By updating the route information table 142, the signal output from the UE 10B is switched from FIG. 11 (a) to FIG. 11 (c) or from FIG. 13 (a) to FIG. 13 (c).
- the UE 10C when receiving the route information update instruction from the ProSe server 20 (S1512), the UE 10C updates the route information table 142 of the UE 10C (S1520). By updating the route information table 142, the signal output from the UE 10C is switched from FIG. 11 (b) to FIG. 11 (e) or from FIG. 13 (b) to FIG. 13 (g).
- the communication between the UE 10B and the UE 10C can be switched from the infrastructure communication to the UE-to-Network Relay communication via the UE 10A (S1524).
- UE 10B and UE 10C are performing infrastructure communication as an initial state (S1502).
- the packets shown in FIGS. 11A and 11B are transmitted and received.
- the ProSe server 20 detects a trigger for requesting switching of a path or a communication path from the infrastructure communication T905 (S1602). For example, the ProSe server 20 may detect that the UE 10B is out of the network access coverage.
- the ProSe server 20 selects an optimal Relay UE for the UE 10B (S1508).
- the selection method of Relay UE is not specifically limited, For example, selecting from UE location information registered in the Proe server is conceivable.
- the steps after S1508 are the same as those after S1508 in FIG.
- FIG. 17 shows an example of a flowchart of the UE 10B that realizes the sequences of FIGS.
- the UE 10B waits to detect any trigger that switches from infrastructure communication to UE-to-Network Relay communication (step S102).
- step S102 When a path switching trigger is detected in step S102 (step S102; Yes), the UE 10B transmits a route information update permission request (including flag1) to the ProSe server 20 (step S104).
- step S104 After executing step S104 or when no path switching trigger is detected in step S102 (step S102; No), the UE 10B waits to receive a route information update instruction (including flag2) from the ProSe server 20 (step S106).
- a route information update instruction including flag2
- the UE 10B determines that the path switching permission is not granted to the ProSe server 20, and returns to step S102.
- step S106 when the UE 10B receives the route information update instruction from the ProSe server 20 (step S106; Yes), the UE 10B determines the DCM state with the designated UE 10A (step S108). When the DCM state with the UE 10A is the idle mode (step S108; idle), the UE 10B determines whether to implement direct communication with the Relay UE 10A (step S110).
- step S110 If the UE 10B permits the direct communication in step S110 (step S110; permission), the UE 10B establishes a direct communication channel between the UE 10A and the UE 10B (step S112).
- step S110 When the UE 10B refuses to communicate directly in step S110 (step S110; rejection), the UE 10B transmits a rejection signal to the ProSe server 20 (step S116). Then, the process returns to step S106 and processing is performed.
- step S112 After step S112 is completed, or when the DCM state between the relay UE 10A is in connected mode in step S108 (step S108; connected), the UE 10B starts from the infrastructure communication T905 to the UE via the direct communication T901 with the relay UE 10A.
- the communication path is switched to -to-Network Relay communication, and the path information is updated (step S114).
- FIG. 18 shows an example of a flowchart of the Relay UE 10A that realizes the sequences of FIGS.
- Relay UE10A receives a direct communication request from UE10B (step S202). Based on step S202, Relay UE10A determines whether the request
- step S203 when the UE 10A rejects the direct communication request from the UE 10B (step S203; No), the UE 10A ends the process. In addition, when step S203 is No, you may complete
- the Relay UE 10A transmits a communication approval directly to the UE 10B (Step S206).
- the determination as to whether the Relay UE 10A permits the request from the UE 10B may be made based on whether or not service authentication has been completed by ProSe Registration. For example, you may determine based on authentication information, such as ProSe ID which UE10B transmits. Or you may determine by the presence or absence of authentication information. Further, the determination may be made based on the state of resources in the network, the state of the confusion, the setting by the user, and the terminal policy generated from various factors.
- FIG. 19 shows an example of a flowchart of the ProSe server 20 that realizes the sequences of FIGS.
- the ProSe server 20 waits to detect a path switching trigger or waits to receive a route information update permission request from a UE registered in the ProSe server 20 (step S302).
- step S302 when one of the two types of triggers is detected (step S302; Yes), the ProSe server 20 determines whether to permit a route information update request (step S303).
- the determination as to whether the ProSe server 20 permits the route information update request may be made based on whether or not the UE 10B has completed the service authentication by ProSe Registration.
- the determination may be made based on authentication information such as ProSe ID transmitted by the UE 10B. Or you may determine by the presence or absence of authentication information. Further, the determination may be made based on a resource state in the network, a state of the confusion, a setting by the user, and an operator policy generated from various factors.
- authentication information such as ProSe ID transmitted by the UE 10B. Or you may determine by the presence or absence of authentication information. Further, the determination may be made based on a resource state in the network, a state of the confusion, a setting by the user, and an operator policy generated from various factors.
- step S303 when the update of the route information is permitted (step S303; Yes), the ProSe server 20 selects the Relay UE (step S304).
- the selection method of the Relay UE is not specified, for example, the UE having the Relay function at the shortest distance is selected.
- step S303 when the ProSe server 20 rejects the route information update (step S303; No), the ProSe server 20 ends this process.
- the rejection is determined in step S303 (step S303; No)
- the process may be terminated after a message indicating the rejection notification is transmitted to the transmission source of the route information permission request.
- a route information update instruction (including flag 2) is transmitted to the ProSe server 20 (step S306). If step S306 is completed, it will be confirmed whether the rejection signal was received from UE10B (step S308).
- the ProSe server 20 selects the Relay UE again (Step S304).
- Step S308 when the rejection signal is not received from the UE 10B in Step S308 (Step S308; No), the ProSe server 20 transmits a route information update instruction (including flag3) to the UE 10C (Step S310).
- the flags indicating the instruction or request included in the signal transmitted from the UE 10B to the ProSe server 20 are “indication flag1-1” and “indication flag1-2”.
- flags indicating an instruction or a request included in a signal transmitted from the ProSe server 20 to the UE 10B are “indication flag 2-1” and “indication flag 2-2”.
- the flag indicating the instruction or request included in the signal transmitted from the ProSe server 20 to the UE 10C is “indication flag 3” as in FIGS.
- “Indication flag1-1” and “indication flag1-2” have a part of the function of “indication flag1” in FIG. Specifically, in FIG. 20, “indication flag 1-1” requests the ProSe server 20 to select a Relay UE used for direct communication for updating route information, and requests to respond to the selected Relay UE. This flag requests a DCM state confirmation instruction.
- “Indication flag 1-2” is a flag requesting the ProSe server 20 for permission to update the route information and requesting confirmation of the DCM state.
- “indication flag 2-1” and “indication flag 2-2” also have some functions of “indication flag 2” in FIGS. 15 and 16 in the same manner as “indication flag 1-1” and “indication flag 1-2”. Prepare.
- the “indication flag 2-1” notifies the UE 10B of the selected Relay UE and requests to confirm the DCM status with the selected Relay UE, and the DCM status is set to the connected mode. It is a flag requesting notification of the event.
- the “indication flag 2-2” is a flag that requests the UE 10B to switch the route information from infrastructure communication to UE-to-Network Relay communication via the relay UE 10A via direct communication.
- FIG. 20 illustrates a process in which the ProSe server 20 authenticates path switching after establishing a communication path between the UE 10B and the Relay UE 10A that perform direct communication.
- the UE 10B and the UE 10C first perform infrastructure communication as an initial state (S1702).
- the packets shown in FIGS. 11A and 11B may be transmitted and received.
- the UE 10B detects a path switching trigger (S1704).
- the trigger for switching the path in S1704 is not particularly limited.
- the UE 10B may be out of the network access coverage.
- S1704 is the same processing as S1504 in FIG.
- the UE 10B When the UE 10B detects the trigger in S1704, the UE 10B transmits a route information update permission request for notifying path switching to the ProSe server 20 (S1706).
- the route information update permission request in S1706 may include an ID (ProSe ID B) for identifying the source UE 10B, and the identifier (ProSe ID C) of the UE 10C with which the UE 10B is currently communicating with the infrastructure. ) May be included, the location information ID of the UE 10B may be included, “indication flag1-1” may be included, and a plurality of information elements may be included.
- the ProSe server 20 receives the route information update permission request from the UE 10B, and when “indication flag1-1” is included, or when a message including the request is received, based on “indication flag1-1”, or Based on the request, the Relay UE to which the UE 10B is connected is selected (S1708).
- the selection method of Relay UE is not specifically limited, For example, selecting from UE location information registered in the ProSe server is conceivable.
- Step S1708 is the same as S1508 in FIG.
- the ProSe server 20 transmits a Relay UE notification to the UE 10B based on “indication flag1-1” or S1708 (S1710).
- a message notifying the failure or refusal of selecting the Relay UE may be transmitted to the UE 10B that has transmitted the route information update permission request.
- the Relay UE notification in S1710 may include the identifier (ProSe ID C) of the communication partner UE 10C of the UE 10B, may include the identifier of the Relay UE 10A selected as the Relay UE (ProSe ID A), and "indication flag2 -1 "may be included, and a plurality of information elements may be included.
- the UE 10B When the UE 10B receives the Relay UE notification including the “indication flag 2-1” from the ProSe server 20, the UE 10B confirms the DCM state between the UE 10B and the UE 10A based on the “indication flag 2-1” or based on the request ( S1712).
- the UE 10B does not particularly need to perform any processing.
- the route information update permission request in S1706 may be retransmitted to the ProSe server 20.
- S1713 includes S1714 and S1716.
- the UE 10B sends a communication request directly to the Relay UE 10A (S1714).
- S1714 includes the identifier of UE 10A (ProSe ID A) and the identifier of UE 10B (ProSe ID B).
- the relay UE 10A When the relay UE 10A receives a direct communication request from the UE 10B, the relay UE 10A transmits a direct communication approval to the UE 10B (S1716). In the direct communication approval of S1716, the relay UE 10A realizes the direct communication between the UE 10B, the outer IP (IP @ A2, IP @ B2) assigned to the UE 10A and the UE 10B, and the identifier (ProSe) of the Relay UE 10A and the UE 10B. ID A, ProSe ID B). The UE 10B receives the communication approval directly from the Relay UE 10A.
- the UE 10B transmits a route information update permission request to the ProSe server 20 based on the received direct communication approval or based on the confirmation result in S1712 being connected mode or based on the request (S1718). .
- the route information update permission request in S1718 may include the identifier (ProSe ID B) of the UE 10B, may include the identifier of the UE 10C (ProSe ID C), may include the location information of the UE 10B, and “indication flag1 -2 "or a plurality of information elements.
- the ProSe server 20 When the ProSe server 20 receives a route information update permission request including the “indication flag1-2” from the UE 10B, or receives a message including the request, the ProSe server 20 is based on the “indication flag1-2” or based on the request.
- the ProSe server 20 authenticates switching of a path, switching of a communication path, or selection of a path or a communication path (S1720).
- the ProSe server 20 When the ProSe server 20 authenticates the path switching, it sends a route information update instruction to the UE 10B and the UE 10C (S1722, S1724).
- the route information update instruction (S1722) from the ProSe server 20 to the UE 10B may include the identifier of the UE 10C (ProSe ID C), or the identifier of the Relay UE 10A selected as the Relay UE (ProSe ID A). “Indication flag 2-2” may be included, and a plurality of information elements may be included.
- the route information update instruction (S1724) from the ProSe server 20 to the UE 10C is the same as S1512 in FIG.
- the UE 10B When the UE 10B receives the route information update instruction from the ProSe server 20 or receives a message including the request, the UE 10B updates the route information based on “indication flag 2-2” or based on the request (S1728). As a result, when information to be transmitted from the UE 10B to the UE 10C is generated, the route information is updated so as to change from FIG. 11A to FIG. 11C or from FIG. 13A to FIG. 13C. .
- the UE 10C When the UE 10C receives the route information update instruction in S1724, the UE 10C updates the route information based on “indication flag3” or based on the request (S1726). Thus, when information from the UE 10C to the UE 10B is generated, the information changes from FIG. 11 (b) to FIG. 11 (e) or from FIG. 13 (b) to FIG. 13 (g).
- the UE 10B and the UE 10C first perform infrastructure communication (S1802).
- the packets shown in FIGS. 11A and 11B are transmitted and received.
- the ProSe server 20 detects a trigger for switching a path from infrastructure communication (S1804).
- S1804 may be any trigger.
- the UE 10B may be out of network access coverage.
- the ProSe server 20 selects the Relay UE as the UE 10B (S1708).
- FIG. 22 shows an example of a flowchart of the UE 10B that realizes the sequences of FIGS.
- the UE 10B waits to detect any path switching trigger (step S402).
- step S402 When a trigger is detected in step S402 (step S402; Yes), the UE 10B transmits a route information update permission request (including flag 1-1) to the ProSe server 20 (step S404).
- step S404 the UE 10B confirms reception of the Relay UE notification (flag 2-1) from the ProSe server 20 (step S406).
- the process returns to Step S402 (Step S406; No).
- the UE 10B determines the DCM state between the relay UE and the UE 10B based on the flag 2-1 (step S408). ).
- step S410 When the UE mode is in idle mode (step S408; idle), the UE 10B confirms whether to reject the Relay UE specified in the ProSe server 20 (step S410). When there is rejection (step S410; Yes), the UE 10B transmits a rejection signal to the ProSe server 20 (step S420). Thereafter, the process proceeds to step S406.
- step S410 when there is no rejection in step S410 (step S410; No), the UE 10B starts a direct communication path establishment process (step S412).
- step S408 if the UE is in connected mode (step S408; connected), or if a communication path is established in step S412, the UE 10B sends a route information update permission request (flag1-2) to the ProSe server 20. Transmit (step S414).
- the UE 10B confirms that it receives a route information update instruction (including flag 2-2) from the ProSe server 20 (step S416).
- step S416 When the UE 10B does not receive the route information update instruction in step S416 (step S416; No), the process returns to the first step (step S402).
- step S416 when the UE 10B receives a route information update instruction including “indication flag 2-2” in step S416 (step S416; Yes), the UE 10B updates the route information (step S418).
- FIG. 23 shows an example of a flowchart of the ProSe server 20 that realizes the sequences of FIGS.
- the ProSe server 20 waits for detection of any path switching trigger or reception of a route information update permission request (including flag 1-1) from the UE 10B (step S502).
- step S502 when any of the above triggers is detected (S502; Yes), the ProSe server 20 determines whether to permit a route information update request (step S503).
- the determination as to whether the ProSe server 20 permits the route information update request may be made based on whether or not the UE 10B has completed the service authentication by ProSe Registration.
- the determination may be made based on authentication information such as ProSe ID transmitted by the UE 10B. Or you may determine by the presence or absence of authentication information. Further, the determination may be made based on a resource state in the network, a state of the confusion, a setting by the user, and an operator policy generated from various factors.
- authentication information such as ProSe ID transmitted by the UE 10B. Or you may determine by the presence or absence of authentication information. Further, the determination may be made based on a resource state in the network, a state of the confusion, a setting by the user, and an operator policy generated from various factors.
- step S503 when the update of the route information is permitted (step S503; Yes), the ProSe server 20 selects a Relay UE that directly communicates with the UE 10B (step S504).
- the selection method of Relay UE is not particularly specified, for example, the UE having the Relay function at the shortest distance is selected.
- the ProSe server 20 rejects the route information update in step S503 (step S503; No)
- the ProSe server 20 ends this process. If the rejection is determined in step S503 (step S503; No), the process may be terminated after a message indicating notification of rejection is transmitted to the transmission source of the route information permission request.
- the ProSe server 20 transmits a Relay UE notification (including flag 2-1) to the UE 10B (step S506).
- the ProSe server 20 receives a route information update permission request including “indication flag1-2” from the UE 10B (step S508).
- the ProSe server 20 determines to approve path switching based on flag 1-2 or based on the request in step S508 (step S510).
- whether the ProSe server 20 permits the route information update request in step S508 may be determined based on whether or not the UE 10B has completed service authentication by ProSe Registration. For example, you may determine based on authentication information, such as ProSe ID which UE10B transmits.
- the determination may be made based on the presence or absence of authentication information. Further, the determination may be made based on a resource state in the network, a state of the confusion, a setting by the user, and an operator policy generated from various factors.
- step S510 based on the approval, the ProSe server 20 transmits a route information update instruction (flag2-2) to the UE 10B (step S512).
- step S510 If the path switching is rejected in step S510 (step S510; No), the process is terminated.
- step S512 it is confirmed whether or not a rejection signal is received from the UE 10B in step S512 (step S514).
- step S514 when a rejection signal is received from the UE 10B (step S514; Yes), the ProSe server 20 returns to selecting a relay UE (step S504).
- step S514 If no rejection signal is received from the UE 10B in step S514 (step S514; No), the ProSe server 20 transmits a route information update instruction (including flag3) to the UE 10C (step S516).
- the communication between the UE 10B and the UE 10C can be switched from the infrastructure communication to the UE-to-Network Relay communication via the Relay UE 10A, the communication path can be switched, or the path or the communication path can be selected. .
- the configuration of the mobile communication system shown in FIG. 1 can be used, and detailed description thereof is omitted.
- the configuration of the UE and the configuration of the ProSe server 20 in the mobile communication system are the same, detailed description is omitted.
- FIG. 24 is a diagram for explaining the service continuation procedure procedure.
- the UE 10B detects the Relay UE detection trigger, and the UE 10B detects a Relay UE that can communicate directly with the UE 10B (discovery), establishes a communication path, and then requests the ProSe server 20 for authentication.
- each function when each function wants to give an operation instruction or a request to a communication partner, it is described as adding a flag called an indication flag.
- information indicating that the function is requested is identified by a flag.
- the request may be made by transmitting a route information update request message, for example, by defining a route information update request message. More specifically, a device that gives a request or an instruction may transmit a request message including a message type for requesting route information update to the requesting partner.
- an information element indicating an instruction or a request included in the signal transmitted from the UE 10B to the ProSe server 20 is “indication flag 1”, and is included in the signal transmitted from the ProSe server 20 to the UE 10B.
- the information element indicating the instruction or request is “indication flag 2”, and the information element indicating the instruction or request included in the signal transmitted from the ProSe server 20 to the UE 10C is “indication flag 3”.
- the function of “indication flag 1” in FIG. 24 requests permission to switch communication between the UE 10B and the UE 10C from infrastructure communication to UE-to-Network Relay communication via the Relay UE 10A.
- UE 10B and UE 10C are performing infrastructure communication (S1502).
- the UE 10B detects a certain Relay UE detection trigger (S2502).
- the Relay UE detection trigger is a trigger for starting detection of a UE that becomes a Relay UE with the network, and is not particularly limited. For example, it is conceivable that the UE is about to go out of network coverage.
- the UE 10B and the Relay UE 10A are detected (S2504), and the Relay UE 10A assigns an IP address for direct communication to the UE 10B and notifies the UE 10B (S2506).
- the UE 10B detects a path switching trigger (S2508).
- the path switching trigger is not particularly limited, for example, it is conceivable that the UE 10B has come out of the coverage of the network.
- the UE 10B When the UE 10B detects a path switching trigger, the UE 10B transmits a route information update permission request to the ProSe server 20 (S2510).
- the route information update permission request in S2510 may include ProSe ID B, may include ProSe ID C, may include ProSe ID A, may include UE location information ID, and may include indication flag1. It may be included, and a plurality of information elements may be included among the information elements. Thereby, the ProSe server 20 can select the designated Relay UE (S1508).
- symbol is attached
- the UE 10B can specify the Relay UE and request the ProSe server 20 for permission to switch the path.
- FIG. 25 shows that the communication between the UE 10B and the UE 10C is directly passed from the infrastructure communication T905 to the UE-to-Network Relay communication via the communication T901 and the relay communication T903 by detecting the trigger of path switching. The process which switches a path
- each function when each function wants to give an operation instruction or a request to a communication partner, it is described as adding a flag called an indication flag.
- information indicating that the function is requested is identified by a flag.
- the request may be made by transmitting a route information update request message, for example, by defining a route information update request message. More specifically, a device that gives a request or an instruction may transmit a request message including a message type for requesting route information update to the requesting partner.
- the information element indicating the instruction or request included in the signal transmitted from the UE 10B to the ProSe server 20 is “indication flag 1”, and the instruction included in the signal transmitted from the ProSe server 20 to the UE 10C.
- the information element indicating the request is “indication flag 3”
- the instruction element included in the signal transmitted from the ProSe server 20 to the Relay UE 10A is “indication flag 4”
- An information element indicating an instruction or a request included in is indicated as “indication flag5”.
- “Indication flag 4” is a flag for requesting to function as a Relay UE between designated UEs.
- the ProSe server 20 transmits a route information update instruction including “indication flag 4” to the Relay UE 10A, and the ProSe server 20 requests the Relay UE 10A to function as a Relay UE for communication between the UE 10B and the UE 10C. can do.
- “indication flag 4” is a flag indicating a request for confirming the DCM state between the designated UE and the own terminal. That is, the ProSe server 20 can request the Relay UE 10A to check the DCM state between the UEs 10B by transmitting the route information update instruction including “indication flag 4” to the Relay UE 10A.
- “indication flag 4” confirms the DCM state with the UE 10B, indicates that the communication state is established when the DCM state is the idle mode, and indicates that the processing is not particularly required when the connected mode is the connected mode. Flag.
- the ProSe server 20 when the ProSe server 20 sends a route information update instruction including “indication flag 4” to the Relay UE 10A, the ProSe server 20 confirms the DCM state with the UE 10B to the Relay UE 10A, and UE 10B when the DCM state is idle mode. And requesting the establishment of a direct communication path.
- “indication flag 4” is a flag that requests transmission of a route information update instruction to a designated UE when a communication path between the designated UEs is established. That is, the ProSe server 20 transmits a route update instruction including “indication flag 4” to the Relay UE 10A, so that the ProSe server 20 establishes a communication path with the Relay UE 10A or confirms that it is in the connected mode, and then routes to the UE 10B. An information update instruction can be requested to be transmitted.
- “indication flag 4” may indicate a meaning obtained by combining the requests and instructions described so far.
- “indication flag 5” is a flag indicating that the infrastructure communication T905 is requested to switch to UE-to-Network Relay communication via the Relay UE 10A. Note that “indication flag5” may be a flag indicating that switching from UE-to-Network Relay communication to infrastructure communication T905 is requested.
- the relay UE 10A when the relay UE 10A transmits a route information update instruction including “indication flag 5” to the UE 10B, the relay UE 10A transmits communication to the UE 10B from the infrastructure communication T905 to the UE UE 10A via direct communication with the relay UE 10A. It is also possible to request to update route information to to-Network Relay communication, and to request to update route information to UE-to-Network Relay communication via infrastructure communication with Relay UE 10A.
- the “indication flag 5” may be a flag that instructs the ProSe server 20 to request permission to switch from infrastructure communication T905 to UE-to-Network Relay communication via Relay UE 10A.
- “indication flag 5” may be a flag indicating that the ProSe server 20 is requested to permit switching from the UE-to-Network Relay communication to the infrastructure communication T905.
- the Relay UE 10A sends a route information update instruction including “indication flag 5” to the UE 10B, so that the Relay UE 10A switches from the infrastructure communication to the UE 10B via the Relay UE 10A to the UE-to-Network Relay communication. You may request permission from the ProSe server 20.
- “indication flag 5” may indicate a meaning obtained by combining the requests and instructions described so far.
- “indication flag 1” is a request to switch a path or a communication path, a request to select a Relay UE connected to the UE 10B, and a request to notify the Relay UE 10A and the UE 10C of the Relay UE. And a flag indicating a request to instruct the Relay UE 10A to establish a communication path between the Relay UE and the UE 10B.
- “indication flag 3” instructs the UE 10C to update the route information from the infrastructure communication T905 to the UE-to-Network Relay communication via the relay communication T903 with the Relay UE 10A for communication between the UE 10C and the UE 10B. This flag indicates a request.
- “indication flag 4” is used to request the relay UE 10A to confirm the DCM state between the UE 10B and the Relay UE 10A, and the UE-to-Network Relay communication via the infrastructure communication T905 to the relay UE 10A via the direct communication T901.
- a flag indicating that a signal indicating a route information update instruction is transmitted to the UE 10B.
- “indication flag 5” is a flag that requests the UE 10B to update the communication path from infrastructure communication to UE-to-Network Relay communication via the Relay UE 10A.
- S1902 may be equal to S1502, S1702, and S1802.
- the UE 10B detects a path switching trigger (S1904).
- the trigger for switching the communication path to the UE-to-Network Relay is not particularly limited.
- the UE 10B may detect that the UE 10B has detected that it has gone out of the network access coverage.
- the UE 10B sends a route information update permission request to the ProSe server 20 triggered by S1904 (S1906).
- the route information update permission request in S1906 may include ProSe ID B that identifies UE 10B, may include ProSe ID C that identifies UE 10C of the communication partner, and may include location information of UE 10B.
- the indication flag 1 may be included, and a plurality of information elements may be included among the information elements described above.
- the ProSe server 20 When the ProSe server 20 receives a route information update permission request including “indication flag 1” from the UE 10B or receives a message including the request, the ProSe server 20 selects a Relay UE connected to the UE 10B based on the indication flag 1 or based on the request. Select (S1908).
- the ProSe server 20 transmits a route information update instruction to the Relay UE 10A based on “indication flag 1” included in the route information update permission request received from the UE 10B, based on the request of S1906, or based on the selection of the Relay UE. (S1910).
- the route information update instruction in S1910 may include ProSe ID A that identifies Relay UE 10A, may include ProSe ID B that identifies UE 10B, and may include ProSe ID C that identifies UE 10C of the communication partner.
- the location information of the UE 10B may be included, “indication flag 4” may be included, and a plurality of the information elements described above may be included.
- the ProSe server 20 sends a route information update instruction to the UE 10C at the same time as or after S1910 based on the “indication flag 1”. It transmits (S1912).
- S1912 is performed based on, for example, a request from another device, a selection result of Relay UE selection (S1908), a route information update instruction transmitted from the ProSe server 20 to the Relay UE 10A (S1910), and the like. It may be broken.
- the route information update instruction transmitted from the ProSe server 20 in S1912 is the same as S1512 described in the first embodiment, and a description thereof is omitted.
- the relay UE 10A When the relay UE 10A receives a route information update instruction from the ProSe server 20 or receives a message including a request, the relay UE 10A checks the DCM state between the relay UE 10A and the UE 10B based on the “indication flag 4” of S1910 or based on the request. (S1914).
- the Relay UE 10A can reject direct communication between the UEs 10B. In that case, the Relay UE 10A transmits a rejection signal to the ProSe server 20.
- S1915 is executed as a process.
- the Relay UE 10A transmits a communication request directly to the UE 10B (S1916).
- the direct communication request in S1916 includes a ProSe ID A that identifies the Relay UE and a ProSe ID B that identifies the UE 10B.
- One of the identifiers of ProSe ID A and ProSe ID B may be included.
- the UE 10B receives the direct communication request from the UE 10A, authenticates the direct communication based on the list of the Relay UE 10A identifier stored in the storage unit 130, and transmits a direct communication approval to the Relay UE 10A (S1918).
- the direct communication approval of S1918 includes an identifier ProSe ID A of Relay UE 10A and an identifier ProSe ID B of UE 10B.
- One of the identifiers of ProSe ID A and ProSe ID B may be included.
- the Relay UE 10A When receiving the direct communication authentication from the UE 10B, the Relay UE 10A establishes a direct communication path between the Relay UE 10A and the UE 10B.
- the UE 10A assigns the outer IP address IP @ A2 of the Relay UE 10A and the outer IP address IP @ B2 of the UE 10B, which are used as the outer IP in direct communication.
- the Relay UE 10A transmits an outer IP address notification for notifying the UE 10B of the IP address assignment for direct communication based on S1916 (S1919).
- the outer IP address notification includes the outer IP address IP @ A2 assigned to the Relay UE 10A and the outer IP address IP @ B2 assigned to the UE 10B.
- the outer IP address notification may include the identifier ProSe ID A of the Relay UE 10A, or may include the identifier ProSe ID B of the UE 10B.
- the Relay UE 10A between the Relay UE 10A and the UE 10B transmits a route information update instruction to the UE 10B (S1920).
- the route information update in S1920 includes ProSe ID A that identifies Relay UE 10A, ProSe ID B that identifies UE 10B, and “indication flag 5”.
- the UE 10B updates the route information from infrastructure communication to UE-to-Network Relay communication via direct communication with the Relay UE 10A triggered by S1921 (S1922).
- UE10C updates the route information triggered by S1912 (S1924).
- the UE 10B can detect the trigger and switch the path or communication path from the infrastructure communication T905 to the UE-to-Network Relay communication via the Relay UE 10A (S1926).
- FIG. 26 of the second processing example is a processing example different from FIG. 25 of the first processing example.
- FIG. 26 is an example of a method in which the ProSe server detects a trigger for switching a communication path or a path path between the UE 10B and the UE 10C.
- S2002 may be the same as S1502, S1702, and 1902.
- the ProSe server 20 detects a trigger for switching a path from infrastructure communication (S2004). For example, the ProSe server 20 may detect that the UE 10B is out of the network coverage.
- S2004 infrastructure communication
- the ProSe server 20 selects an optimal Relay UE for the UE 10B (S1908).
- the selection method of Relay UE is not specifically limited, For example, selecting from UE location information registered in the Proe server is conceivable.
- the steps after S1908 are the same as those after S1908 in FIG.
- FIG. 27 shows an example of a flowchart of the UE 10B that realizes the sequences of FIGS.
- the UE 10B waits for detection of some trigger for starting path switching from the infrastructure communication to the UE-to-Network Relay communication for communication with the UE 10C (step S602). If a path switching trigger is detected (step S602; Yes), the UE 10B transmits a route information update permission request (including flag1) to the ProSe server 20 (step S604).
- step S604 the UE 10B waits to receive a route information update instruction from the relay UE 10A (step S606).
- step S606 the UE 10B determines that the path switching permission is not granted to the ProSe server 20, and returns to step S602.
- Step S606 when the UE 10B receives the route information update instruction from the Relay UE 10A in Step S606 (Step S606; Yes), the UE 10B updates the route information (Step S608).
- FIG. 28 shows an example of a flowchart of the Relay UE 10A that realizes the sequences of FIGS.
- the Relay UE 10A receives a route information update instruction from the ProSe server 20 (step S702).
- Relay UE10A determines the DCM state between UE10B based on "indication flag4" or a request (step S704).
- the UE 10A confirms whether there is a rejection of communication with the UE 10B (step S706).
- the determination as to whether the Relay UE 10A permits the request is determined based on the resource status in the network, the state of the confusion, the setting by the user, and the terminal policy generated from various factors. Also good.
- step S706 If there is a rejection of direct communication with the UE 10B in step S706 (step S706; Yes), the Relay UE 10A transmits a rejection signal to the ProSe server 20 (step S714).
- step S706 If there is no rejection in direct communication with the UE 10B in step S706 (step S706; No), the Relay UE 10A establishes a direct communication path (step S708).
- the Relay UE 10A assigns an outer IP to the Relay UE 10A and the UE 10B (Step S710).
- step S710 or when it is determined in step S704 that the DCM state between the UEs is connected mode (step S704; connected), the Relay UE 10A transmits a route information update instruction to the UE 10B (step S712).
- the fifth embodiment is a modification of the fourth embodiment, and the ProSe server performs UE-to-Network Relay communication in which the UE 10B communicates with the UE 10C by directly communicating with the Relay UE 10A from the infrastructure communication between the UE 10B and the UE 10A.
- the ProSe server performs UE-to-Network Relay communication in which the UE 10B communicates with the UE 10C by directly communicating with the Relay UE 10A from the infrastructure communication between the UE 10B and the UE 10A.
- switching of a path or a communication path is led and a route information update instruction is sent from the ProSe server 20 to the Relay UE 10A and the UE 10C after the direct communication path is established.
- FIG. 29 is a sequence diagram in the present embodiment.
- flags indicating an instruction or a request included in a signal transmitted from the UE 10B to the ProSe server 20 are “indication flag 1-1” and “indication flag 1-2”.
- a flag indicating an instruction or a request included in a signal transmitted from the ProSe server 20 to the UE 10B is “indication flag 2”.
- the flag indicating the instruction or request included in the signal transmitted from the ProSe server 20 to the UE 10C is “indication flag 3” as in FIGS. 15 and 16, and is included in the signal transmitted from the ProSe server 20 to the Relay UE 10A.
- An information element indicating an instruction or request is “indication flag 4”
- an information element indicating an instruction or request included in a signal transmitted from the Relay UE 10A to the UE 10B is “indication flag 5”.
- “indication flag 1-1” requests the ProSe server 20 to select a Relay UE to be used for direct communication for route information update, requests to respond to the selected Relay UE, and confirms the DCM state. This flag requests an instruction.
- “indication flag1-2” is a flag requesting the ProSe server 20 for permission to update route information and requesting confirmation of the DCM state.
- “indication flag 2” is a flag that requests the UE 10B to switch the route information from infrastructure communication to UE-to-Network Relay communication via the relay UE 10A via direct communication.
- “indication flag 4” in FIG. 29 indicates to the Relay UE 10A a request for confirmation of the DCM state between the UE 10B and the Relay UE 10A, and when the DCM state is in idle mode, This flag is used to request that a communication path establishment notification be instructed.
- “indication flag 5” is a flag for requesting permission from the ProSe server 20 to update the communication path from infrastructure communication to UE 10B to UE-to-Network Relay communication via Relay UE 10A.
- the UE 10B and the UE 10C first perform infrastructure communication (S2102).
- the packets shown in FIGS. 11A and 11B may be transmitted and received.
- the UE 10B detects a path switching trigger (S2104).
- the trigger for switching the path in S2104 is not particularly limited.
- the UE 10B may be triggered by coming out of the network coverage.
- S2104 may be the same processing as S1904 in FIG.
- the UE 10B When the UE 10B detects a path switching trigger in S2104, the UE 10B transmits a Relay UE selection request to notify the ProSe server 20 of the path switching (S2106).
- the Relay UE selection request in S2106 may include an ID for identifying the source UE 10B (ProSe ID B), and the identifier of the UE 10C with which the UE 10B is currently communicating with the infrastructure (ProSe ID C) May be included, the location information ID of the UE 10B may be included, “indication flag1-1” may be included, and a plurality of information elements may be included among the information elements.
- the ProSe server 20 receives a Relay UE selection request from the UE 10B in S2106. At this time, if “indication flag1-1” is included in the received Relay UE selection request, the ProSe server 20 selects a Relay UE to which the UE 10B is connected based on “indication flag1-1” (S2108). Although the selection method of Relay UE is not specifically limited, For example, you may select from the positional information on UE registered into the ProSe server. If the ProSe server 20 determines that the Relay UE cannot be selected, the process may be terminated.
- the ProSe server 20 receives a Relay UE selection request including “indication flag 1-1” or a message including a request, the ProSe server 20 is based on “indication flag 1-1” or based on the request.
- the ProSe server 20 transmits a route information update instruction to the Relay UE 10A (S2110).
- the route information update instruction in S2110 may include the identifier of UE 10B (ProSe ID B), may include the identifier of UE 10B's communication partner UE 10C (ProSe ID C), may include indication flag 4, and A plurality of information elements may be included among the information elements.
- the Relay UE 10A When the relay UE 10A receives the route information update instruction including the “indication flag 4” from the ProSe server 20, the Relay UE 10A confirms the DCM state between the UE 10B and the UE 10A based on the “indication flag 4” or based on the request (S2112).
- the Relay UE 10A may end the process.
- S2113 includes S2114, S2116, and S2117.
- the Relay UE 10A transmits a communication request directly to the UE 10B (S2114).
- the direct communication request in S2114 may include an identifier (ProSe ID A) of the source UE 10A, may include an identifier (ProSe ID B) of the UE 10B, and may include a plurality of information elements.
- the UE 10B receives a direct communication request from the Relay UE 10A, and transmits a direct communication approval to the Relay UE 10A (S2116).
- the direct communication approval of S2116 includes the identifier of UE 10A (ProSe ID A) and the identifier of UE 10B (ProSe ID B).
- the Relay UE 10A receives the direct communication approval from the UE 10B, and based on the direct communication approval, the UE 10A uses the outer IP address IP @ A2 of the Relay UE 10A and the outer IP address IP @ B2 of the UE 10B to be used as the outer IP in direct communication. Assign.
- the UE 10A transmits an outer IP address notification to the UE 10B (step S2117).
- the outer IP address notification includes the outer IP address IP @ A2 assigned to the Relay UE 10A and the outer IP address IP @ B2 assigned to the UE 10B.
- the outer IP address notification may include the identifier ProSe ID A of the Relay UE 10A, or may include the identifier ProSe ID B of the UE 10B.
- the Relay UE 10A transmits a communication path establishment notification to the UE 10B (S2118).
- the communication path establishment notification in S2118 may include the identifier of Relay UE 10A (ProSe ID A), may include the identifier of UE 10B (ProSe ID B), may include "indication flag 5", and these May be included.
- the UE 10B updates the outer IP address management table 136 in the storage unit 130 based on the direct communication IP address assignment received from the Relay UE 10A in S2117 and the communication path establishment notification received in S2118, and the ProSe server.
- a route information update permission request is transmitted to 20 (S2120).
- the route information update permission request may include the UE 10B identifier (ProSe ID B), the UE 10C identifier (ProSe ID C), or the Relay UE 10A identifier (ProSe ID A).
- the location information of the UE 10B may be included, “indication flag 1-2” may be included, or a plurality of these information elements may be included.
- the ProSe server 20 receives the route information update permission request from the UE 10B, and when the route information update permission request includes “indication flag1-2” or when a message including the request is received, the “indication flag1-2” Or based on the request, the ProSe server 20 authenticates path switching (S2122).
- the ProSe server 20 transmits a route information update instruction to the UE 10B and the UE 10C based on “indication flag 1-2” or based on path switching authentication (S2124, S2126).
- S2124 and S2126 may be performed simultaneously, or one of them may be a trigger for either one.
- the route information update instruction may be transmitted from the ProSe server 20 to the UE 10B (S2124), and the ProSe server 20 may transmit the route information update instruction to the UE 10C (S2126).
- the route information update instruction in S2124 may include the identifier of UE 10C (ProSe ID C), may include the identifier of Relay UE 10A (ProSe ID A), may include “indication flag 2”, and the plurality of pieces of information. It may contain elements.
- the route information update instruction in S2126 may include the identifier of UE 10B (ProSe ID B), may include the identifier of Relay UE 10A (ProSe ID A), may include "indication flag 3", and include these multiple information elements. May be included.
- the UE 10B Upon receiving the route information update instruction from the ProSe server 20 (S2124), the UE 10B updates the route information to the UE 10C from infrastructure communication to UE-to-Network Relay communication via direct communication with the Relay UE 10A ( S2128).
- the UE 10C receives the route information update instruction from the ProSe server 20 (S2126), and the route information to the UE 10B is transmitted from the infrastructure communication to the relay UE 10A and the UE-to-Network Relay communication via the infrastructure communication. (S2130).
- transmission / reception is performed between the UE 10B and the UE 10C by UE-to-Network Relay communication (S2132).
- FIG. 30 is a processing example different from the processing of FIG.
- FIG. 30 is an example of a method in which the ProSe server detects a trigger for switching a communication path or a path path between the UE 10B and the UE 10C.
- S2202 may be equal to S1502, S1702, S1902, S2002, and S2102.
- the ProSe server 20 detects a path switching trigger (S2204). For example, the ProSe server 20 may detect that the UE 10B is out of the network coverage.
- the ProSe server 20 selects a Relay UE that is optimal for the UE 10B (S2108).
- the selection method of Relay UE is not specifically limited, For example, selecting from UE location information registered in the ProSe server is conceivable.
- the steps after S2108 are the same as those after S2108 in FIG.
- FIG. 31 shows an example of a flowchart of the UE 10B that realizes the sequences of FIG. 29 and FIG.
- the UE 10B waits to detect any trigger that switches communication with the UE 10C from infrastructure communication to UE-to-Network Relay communication (step S802).
- a path switching trigger is detected in step S802 (step S802; Yes)
- the UE 10B transmits a Relay UE selection request (including flag 1-1) to the ProSe server 20 (step S804).
- step S804 After execution of step S804 or when a path switching trigger is not detected in step S802 (step S802; No), it waits to receive a communication path establishment notification from the relay UE (step S806).
- step S806 when the communication path establishment notification is received from the Relay UE (step S806; Yes), the UE 10B transmits a path information update permission request (flag1-2) to the ProSe server 20 (step S808).
- step S806 When the communication path establishment notification is not received from the Relay UE 10A in step S806 (step S806; No), the process returns to step S802.
- step S806 the UE 10B waits to receive a route information update instruction (including flag 2) from the ProSe server 20 (step S810).
- a route information update instruction including flag 2
- step S810 the UE 10B returns to step S802, assuming that the routing information update is rejected.
- step S810 when a route update instruction is received from the ProSe server 20 (step S810; Yes), the UE 10B updates the route information (step S812), and the process ends.
- FIG. 32 shows an example of a flowchart of the ProSe server 20 that realizes the sequences of FIGS.
- the ProSe server 20 waits for detection of a path switching trigger or reception of a Relay UE selection request (step S902).
- step S902 when a path switching trigger is detected or a Relay UE selection request (including flag1-1) is received from the UE 10B (step S902; Yes), the ProSe server 20 determines route information update of the UE (step S903). ).
- the determination as to whether the ProSe server 20 permits the route information update request may be made based on whether or not the UE 10B has completed the service authentication by ProSe Registration. For example, you may determine based on authentication information, such as ProSe ID which UE10B transmits. Or you may determine by the presence or absence of authentication information. Further, the determination may be made based on a resource state in the network, a state of the confusion, a setting by the user, and an operator policy generated from various factors.
- step S903 when updating of route information is permitted (step S903; Yes), the ProSe server 20 selects a Relay UE with which the UE 10B communicates directly (step S904).
- the selection method of the Relay UE is not specified, for example, the UE having the Relay function at the shortest distance is selected.
- the ProSe server 20 rejects the route information update in step S903 (step S903; No)
- the ProSe server 20 ends this process.
- the rejection is determined in step S903 (step S903; No)
- the process may be terminated after a message indicating notification of rejection is transmitted to the transmission source of the route information permission request.
- the ProSe server 20 transmits a route information update instruction (including flag 4) to the Relay UE (step S906). This instructs Relay UE 10A to establish a communication path with UE 10B.
- the ProSe server 20 confirms whether or not a rejection signal is received from the UE 10A (step S908).
- a rejection signal is received in step S908 (step S908; Yes)
- the ProSe server 20 starts processing again from the selection of the Relay UE in step S904.
- the ProSe server 20 receives a route information update permission request (including flag 1-2) from the UE 10B (step S910).
- the ProSe server 20 approves path switching based on the flag 1-2 included in the route information update permission request in step S910 (step S912).
- the ProSe server 20 transmits a route information update instruction to the UE 10B and the UE 10C (Steps S914 and S916).
- the communication between the UE 10B and the UE 10C is switched from the infrastructure communication to the UE-to-Network Relay communication via the direct communication with the Relay UE 10A, or the path or the communication path is selected. I can do it.
- a neighboring UE is directly connected as a Relay UE, and a path or a communication path is switched from a UE-to-Network Relay communication to an infrastructure communication via a network, or a path or a communication path is selected.
- the communication system will be described below with reference to the drawings.
- the configuration of the mobile communication system of FIG. 1 can be used, and detailed description thereof is omitted.
- the configuration of the UE and the configuration of the ProSe server in the mobile communication system are the same, detailed description is omitted.
- FIG. 33 illustrates a conceptual diagram of path switching, communication path switching, and path or communication path selection executed in the present embodiment.
- the UE 10B and the UE 10C communicate with each other by UE-to-Network Relay communication (solid line) T903 via the Relay UE 10A.
- the UE 10B and the Relay UE 10A communicate with each other by direct communication T901.
- the path or the communication path is switched to the infrastructure communication (broken line) T905, or the path or the communication path is selected.
- FIGS. 10 to 14 can be used, and detailed description thereof is omitted.
- FIG. 34 shows an example of a process in which the UE 10B detects a trigger for requesting switching from UE-to-Network Relay communication to infrastructure communication, and switches a path or a communication path.
- each function when each function wants to give an operation instruction or a request to a communication partner, it is described as adding a flag called an indication flag.
- information indicating that the function is requested is identified by a flag.
- the request may be made by transmitting a route information update request message, for example, by defining a route information update request message. More specifically, a device that gives a request or an instruction may transmit a request message including a message type for requesting route information update to the requesting partner.
- an information element indicating an instruction or a request included in the signal transmitted from the UE 10B to the ProSe server 20 is “indication flag 1”, and is included in the signal transmitted from the ProSe server 20 to the UE 10C.
- the information element indicating the instruction or request is “indication flag 3”.
- “indication flag 1” is a flag for requesting permission to switch from UE-to-Network Relay communication to infrastructure communication via Relay UE 10A.
- “indication flag 3” is a flag that requests the UE 10C to switch the communication path from the UE-to-Network Relay communication via the Relay UE 10A to the infrastructure communication.
- the initial state of FIG. 34 is a state in which UE-to-Network Relay communication is performed between the UE 10B and the UE 10C via the Relay UE 10A (S2402).
- S2402 may be equal to S1524, S1730, S1926, or S2132.
- UE10B detects the trigger which requests
- the trigger which UE10B detects by S2404 is not specifically limited, For example, it may be triggered that UE10B detected that it entered into the coverage of the network.
- UE10B attaches to MME44 based on S2404 (S2406).
- the UE 10B executes a radio resource control process on the PGW 38 (S2408).
- the PGW 38 can assign a new IP address to the UE 10B, but the UE 10B can request the PGW 38 to assign a designated IP address.
- the UE 10B uses IP @ B2 as the transmission source IP address in the inner IP header. Therefore, when switching to infrastructure communication, the UE 10B can assign the IP @ B2 as the IP address, thereby removing the outer IP header 1107 of FIG. 11C and transmitting FIG. 11A. is there.
- S2406 and S2408 may be executed based on detecting a trigger for requesting path switching, but may be executed based on detecting that the UE 10B has entered the network coverage area.
- the route information update permission request of S2410 may include the identifier (ProSe ID B) of the UE 10B, may include the identifier of the UE 10C (ProSe ID C), may include “indication flag 1”, or a plurality of these.
- the information element may be included.
- the ProSe server 20 When the ProSe server 20 receives an information element including “indication flag 1” in S2410, or receives a message indicating a request, the ProSe server 20 permits route information update based on “indication flag 1” or based on the request. (S2412).
- the ProSe server 20 transmits a route information update instruction to the UE 10B and the UE 10C (S2414, S2416).
- the route information update instruction in S2414 may include ProSe ID B, may include ProSe ID C, may include “indication flag 2”, and may include a plurality of these information elements.
- the route information update instruction in S2416 may include ProSe ID B, may include ProSe ID C, may include “indication flag3”, and may include a plurality of these information elements.
- the UE 10B updates the route information from the UE-to-Network Relay communication to the infrastructure communication based on “indication flag 2” included in the route information update instruction in S2414.
- the UE 10C updates the route information from the UE-to-Network Relay communication to the infrastructure communication based on “indication flag 3” included in the route information update instruction in S2416.
- UE 10B updates route information based on S2404 or based on S2414 (S2430). For example, when the UE 10B updates the route information based on S2414, the route information to the UE 10C recorded in the route information table 142 of the storage unit 130 of the UE 10B is changed from Relay (UE 10A route) to infrastructure communication.
- Relay UE 10A route
- UE 10C updates the route information based on S2416 (S2428). For example, when the UE 10C updates the route information based on S2416, the route information to the UE 10B recorded in the route information table 142 of the storage unit 130 of the UE 10C is changed to infrastructure communication.
- the packet transmitted from the UE 10C may change from FIG. 11 (e) to FIG. 11 (b) or from FIG. 13 (g) to FIG. 13 (b) by updating the route information in S2428.
- the path or communication path can be switched from the UE-to-Network Relay communication to the infrastructure communication, or the path or communication path can be selected (S2202).
- the seventh embodiment is a process in which the UE 10B detects the Relay 10A and updates the route information.
- symbol is attached
- the Relay UE that can be selected by the UE 10B is selected (S2602).
- the selectable Relay UE 10A it is confirmed whether or not direct communication is possible (S1514 to S1518).
- the UE 10B updates the route information based on the Relay UE 10A capable of direct communication (S1522). Further, the updated result is transmitted to the ProSe server 20 as a route information update notification (S2604).
- the order of the processing of S1522 and S2604 is not particularly specified.
- the UE 10B may execute S2604 after S1522, may execute S1522 after S2604, or may execute these simultaneously.
- the route update information notification includes at least the ProSe ID A of the selected Relay UE 10A.
- the ProSe server 20 detects that the route of the UE 10B has been changed, and transmits a route information update instruction to the UE 10C (S1512).
- a program that operates in each device is a program that controls a CPU or the like (a program that causes a computer to function) so as to realize the functions of the above-described embodiments.
- Information handled by these devices is temporarily stored in a temporary storage device (for example, RAM) at the time of processing, then stored in various ROM or HDD storage devices, and read and corrected by the CPU as necessary. • Writing is performed.
- a recording medium for storing the program a semiconductor medium (for example, ROM, a non-volatile memory card, etc.), an optical recording medium / a magneto-optical recording medium (for example, DVD (Digital Versatile Disc), MO (Magneto Optical) Disc), MD (Mini Disc), CD (Compact Disc), BD, etc.), magnetic recording medium (eg, magnetic tape, flexible disk, etc.), etc.
- a semiconductor medium for example, ROM, a non-volatile memory card, etc.
- an optical recording medium / a magneto-optical recording medium for example, DVD (Digital Versatile Disc), MO (Magneto Optical) Disc), MD (Mini Disc), CD (Compact Disc), BD, etc.
- magnetic recording medium eg, magnetic tape, flexible disk, etc.
- the program when distributing to the market, can be stored in a portable recording medium for distribution, or transferred to a server computer connected via a network such as the Internet.
- a server computer connected via a network such as the Internet.
- the storage device of the server computer is also included in the present invention.
- each device in the above-described embodiments may be realized as an LSI (Large Scale Integration) that is typically an integrated circuit.
- LSI Large Scale Integration
- Each functional block of each device may be individually formed as a chip, or a part or all of them may be integrated into a chip.
- the method of circuit integration is not limited to LSI, and may be realized by a dedicated circuit or a general-purpose processor.
- integrated circuit technology that replaces LSI appears due to progress in semiconductor technology, it is of course possible to use an integrated circuit based on this technology.
- LTE and WLAN are described as examples of the radio access network, but they may be connected by WiMAX instead of WLAN.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
第1の端末装置とコアネットワークを介して通信を行う第2の端末装置が送信する経路情報更新要求メッセージを第1の端末装置から受信し、
前記経路情報要求メッセージには、少なくとも通信の切り替えを要求することを示す識別情報が含まれており、
前記識別情報に基づいて、リレー機能を有する第3の端末装置を選択し、
前記経路情報要求メッセージの応答であり、前記第3の端末装置の情報を含む経路更新指示メッセージを前記第1の端末装置に送信し、前記第3の端末装置とLTEを用いた直接通信を行って前記第1の端末装置と通信することを指示する、
ことを特徴とする。
第1の端末装置と第2の端末装置のコアネットワークを介して通信する第1の通信と、前記第2の端末装置が第3の端末装置と直接通信を行って第1の端末装置と通信する第2の通信との切り替えを主導し、
リレー機能を有する前記第3の端末装置を選択し、
前記第3の端末装置の情報を含む経路更新指示メッセージを前記第2の端末装置に送信し、前記第2の通信への切り替えを指示する、
ことを特徴とする。
第2の端末装置と、コアネットワークを介して通信を行う第1の端末装置であって、
パス切り替えトリガーを検知することにより、少なくとも通信の切り替えを要求することを示す識別情報が含まれている経路情報更新要求メッセージをサーバ装置に送信し、
前記サーバ装置から、サーバ装置が選択したリレー機能を有する第3の端末装置の情報を含む経路更新指示メッセージを受信し、
前記経路更新指示メッセージに従って、前記第3の端末装置とLTEを用いた直接通信を行って前記第2の端末装置と通信する、
ことを特徴とする。
以下、図面を参照しながら本発明の実施形態による無線通信技術について詳細に説明する。
図1は本発明の実施形態による無線通信システムの概略構成例を示す機能ブロック図である。
続いて、本実施形態における各装置の機能構成について説明する。ここでは、図1のUE10A、UE10B、UE10C及びProSeサーバ20の装置構成について説明する。
まず、Relay UE以外の一般的なUEの構成について、図3を用いて説明する。本実施形態においては、UE10B、UE10Cが該当する。これらのUEは、ProSe機能を含む無線通信端末であれば良く、LTEアクセス方式により、無線通信によるデータの送受信を行う携帯電話端末であっても良いし、マシーンツーマシーンと呼ばれるような形態で機器同士が相互に情報交換する端末装置であっても良い。
続いて、UE10の中でも、Relay UEとして機能する場合のUE10Aについて、機能構成を説明する。Relay UE10Aは、ProSe機能と、ProSeのRelay機能を含む、無線通信端末であれば良く、LTEアクセス方式により、無線通信によるデータの送受信を行う携帯電話端末であっても良いし、マシーンツーマシーンと呼ばれるような形態で機器同士が相互に情報交換する端末装置であっても良い。なお、明細書中でUE10Aのことを、Relay機能として利用している場合は明確にするためにRelay UEと記載する場合がある。
本実施形態におけるProSeサーバ20の機能構成について、図7を用いて説明する。ProSeサーバ20とは、ProSeによる近隣検出やProSeによる通信を行う移動通信事業者により管理される認証サーバである。
以下に、本実施形態で説明する通信に関しての概要を説明する。図9は、本実施形態で実行されるパスの切り替え、及び通信路の切り替え及び、パスまたは通信路の選択の概念図を説明する。
本実施形態の初期状態は、UE10BとUE10Cがインフラストラクチャー通信T905(実線)で通信を行っている。インフラストラクチャー通信とは、EPCなどネットワークを介して行う通信の事を言う。また、インフラストラクチャー通信とはPDNへのGWとしてPGWを選択し、PDNとのPDNコネクションを確立する通信のことを意味する。
図10(a)は、UE10BとUE10C間のインフラストラクチャー通信を表わす図である。UE10Bは、インフラストラクチャー通信によりUE10Cへ、パスT1003を用いてデータを送信する。つまり、UE10Cは、UE10Bからインフラストラクチャー通信により、パスT1003を用いてデータを受信する。
以下、図11~図13を用いて、本実施形態で使用される可能性がある3種類のIPパケットのカプセル化の手法について説明する。
図11では図10に示す各パスで各UE(Relay UE10A、UE10B、UE10C)が送受信する具体的なユーザデータを含んだIPパケットを示す。
図11(a)は、図10(a)に示すUE10Bがインフラストラクチャー通信によりUE10CへパスT1003を用いて送信するIPパケットの一例である。つまり、UE10CがUE10Bからインフラストラクチャー通信によりパスT1003を用いて受信するIPパケットの一例である。図11(a)のIPパケットは、このIPパケットがUE10BからUE10Cへの情報である事を示すIPヘッダP1100とペイロード(PL)P1101により構成される。
図11(b)は、図10(a)に示すUE10Cがインフラストラクチャー通信によりUE10BへパスT1005を用いて送信するIPパケットの一例である。つまり、UE10BがUE10Cからインフラストラクチャー通信によりパスT1005を用いて受信するIPパケットの一例である。図11(b)のIPパケットは、このIPパケットがUE10CからUE10Bへの情報である事を示すIPヘッダP1103とペイロード(PL)P1105により構成される。
図11(c)は、図10(b)に示すUE10Bが直接通信によりRelay UE10AへパスT1007を用いて送信するIPパケットの一例である。つまり、Relay UE10AがUE10Bから直接通信によりパスT1007を用いて受信するIPパケットの一例である。図11(c)のIPパケットは、このIPパケットがUE10BからRelay UE10Aへの情報である事を示すアウターIPヘッダP1107と、UE10BからUE10Cへ送信したパケットであることを示すIPヘッダP1100と、ペイロードP1101により構成される。
図11(d)は、図10(b)に示すRelay UE10Aがネットワークを介したRelay通信によりUE10CへパスT1009を用いて送信するIPパケットの一例である。つまり、UE10CがRelay UE10Aからネットワークを介したRelay通信によりパスT1009を用いて受信するIPパケットの一例である。
図11(e)は、図10(b)に示すUE10Cがネットワークを介したRelay通信によりRelay UE10AへパスT1011を用いて送信するIPパケットの一例である。つまり、Relay UE10AがUE10Cからネットワークを介したRelay通信によりパスT1011を用いて受信するパケットの一例である。
図11(f)は、図10(b)に示すUE10Aが直接通信によりUE10BへパスT1013を用いて送信するIPパケットの一例である。つまり、UE10BがRelay UE10Aから直接通信によりパスT1013を用いて受信するパケットの一例である。
図12は、図10に示す各パスで各UE(Relay UE10A、UE10B、UE10C)が送受信する具体的なユーザデータを含んだIPパケットを示す。
図12(a)は、図10(a)に示すUE10Bがインフラストラクチャー通信によりUE10CへパスT1003を用いて送信するIPパケットの一例である。つまり、UE10CがUE10Bからインフラストラクチャー通信によりパスT1003を用いて受信するIPパケットの一例である。図12(a)のIPパケットは、このIPパケットがUE10BからUE10Cへの情報である事を示すIPヘッダP1200とペイロードP1201により構成される。
図12(b)は、図10(a)に示すUE10Cがインフラストラクチャー通信によりUE10BへパスT1005を用いて送信するIPパケットの一例である。つまり、UE10BがUE10Cからインフラストラクチャー通信によりパスT1005を用いて受信するIPパケットの一例である。図12(b)のIPパケットは、このIPパケットがUE10CからUE10Bへの情報である事を示すIPヘッダP1203とペイロードP1205により構成される。
図12(c)は、図10(b)に示すUE10Bが直接通信によりRelay UE10AへパスT1007を用いて送信するIPパケットの一例である。つまり、Relay UE10AがUE10Bから直接通信によりパスT1007を用いて受信するIPパケットの一例である。図12(c)のIPパケットは、このIPパケットがUE10BからRelay UE10Aへの情報である事を示すアウターIPヘッダP1207と、UE10BからUE10Cへ送信したパケットであることを示すIPヘッダP1200と、ペイロードP1201により構成される。
図12(d)は、図10(b)に示すRelay UE10Aがネットワークを介したRelay通信によりUE10CへパスT1009を用いて送信するIPパケットの一例である。つまり、UE10CがRelay UE10Aからネットワークを介したRelay通信によりパスT1009を用いて受信するIPパケットの一例である。図12(d)は、図12(c)からアウターIPを取り除いたもの(図12(a)と等しい)により構成されている。
図12(e)は、図10(b)に示すUE10Cがネットワークを介したRelay通信によりRelay UE10AへパスT1011を用いて送信するIPパケットの一例である。つまり、Relay UE10AがUE10Cからネットワークを介したRelay通信によりパスT1011を用いて受信するパケットの一例である。
図12(f)は、図10(b)に示すUE10Aが直接通信によりUE10BへパスT1013を用いて送信するIPパケットの一例である。つまり、UE10BがRelay UE10Aから直接通信によりパスT1013を用いて受信するパケットの一例である。
図13は、図10に示す各パスで各UE(Relay UE10A、UE10B、UE10C)が送受信及び処理する具体的なユーザデータを含んだIPパケットの一例を示す。
図13(a)は、図10(a)に示すUE10Bがインフラストラクチャー通信によりUE10CへパスT1003を用いて送信するIPパケットの一例である。つまり、UE10CがUE10Bからインフラストラクチャー通信によりパスT1003を用いて受信するIPパケットの一例である。図13(a)のIPパケットは、このIPパケットがUE10BからUE10Cへの情報である事を示すIPヘッダP1300とペイロードP1301により構成される。なお、IPヘッダP1300とペイロードP1301は、図11のIPヘッダP1100とペイロードP1101と等しい。
図13(b)は、図10(a)に示すUE10Cがインフラストラクチャー通信によりUE10BへパスT1005を用いて送信するIPパケットの一例である。つまり、UE10BがUE10Cからインフラストラクチャー通信によりパスT1005を用いて受信するIPパケットの一例である。図13(b)のIPパケットは、このIPパケットがUE10CからUE10Bへの情報である事を示すIPヘッダP1303とペイロードP1305により構成される。なお、IPヘッダP1303とペイロードP1305は、図11のIPヘッダP1103とペイロードP1105と等しい。
図13(c)は、図10(b)に示すUE10Bが直接通信によりRelay UE10AへパスT1007を用いて送信するIPパケットの一例である。つまり、Relay UE10AがUE10Bから直接通信によりパスT1007を用いて受信するIPパケットの一例である。図13(c)のIPパケットは、このIPパケットがUE10BからRelay UE10Aへの直接通信である事を示すアウターIPヘッダP1307と、UE10BからUE10Cへ送信したパケットであることを示すIPヘッダP1300と、ペイロードP1301により構成される。すなわち、アウターIPヘッダP1307を図13(a)のパケットの先頭に付加したものである。
図13(d)はRelay UE10Aが、図13(c)をUE10Bから受信した場合に、Relay UE10A内で作成するパケットである。図13(d)は、図13(c)からアウターIPヘッダP1307を取り除き、IPヘッダP1300とペイロードP1301の間に経路制御ヘッダP1309を付加する。経路制御ヘッダP1309は、Relay通信で使用するRelay UEを指定する為にある。
図13(e)は、図10(b)に示すRelay UE10Aがネットワークを介したRelay通信によりUE10CへパスT1009を用いて送信するIPパケットの一例である。つまり、UE10CがRelay UE10Aからネットワークを介したRelay通信によりパスT1009を用いて受信するIPパケットの一例である。
図13(f)は、UE10CからUE10Bへの送信をインフラストラクチャー通信から、UE-to-Network Relay通信に切り替える際に、UE10C内で生成するパケットである。図13(f)は、UE10Cから、UE10Bへの情報である事を示すIPヘッダP1303と、終点オプションヘッダP1315とペイロードP1305により構成される。図13(f)は、図13(b)のIPヘッダP1303とペイロードP1305の間に、終点オプションヘッダP1315を入れたものである。終点オプションヘッダP1315は終点エンティティを示す為のヘッダであるが、ここでは代りにRelay UEであるUE10AのIPアドレスが含まれる。
図13(g)は、図10(b)に示すUE10Cがネットワークを介したRelay通信によりRelay UE10AへパスT1011を用いて送信するIPパケットの一例である。つまり、Relay UE10AがUE10Cからネットワークを介したRelay通信によりパスT1011を用いて受信するパケットの一例である。
図13(h)は、図10(b)に示すUE10Aが直接通信によりUE10BへパスT1013を用いて送信するIPパケットの一例である。つまり、UE10BがRelay UE10Aから直接通信によりパスT1013を用いて受信するパケットの一例である。
続いて、本実施形態における処理について、以下図を用いて説明する。なお、本十時形態において説明するシーケンス図、動作フローは一例であり、動作の影響にない範囲で、処理の順序等が前後しても本発明を実現するのに影響は無い。
本実施形態では、ProSeサーバ20が各UEをサービス認証することを目的として、ProSeサーバ20が、各UE(Relay UE10A、UE10B、UE10C)を、ProSe機能を持つUEとして登録し、管理する必要がある。また、各UE10(Relay UE10A、UE10B、UE10C)がProSeサーバ20に登録される際に、コアネットワーク9は各UE10にProSe IDを割り当てる必要がある。ここでのProSe IDは、ProSeサーバ20がUEを認証したこと示す認証情報でもあってもよい。
図15は、サービス継続手続きprocedureについて説明する図である。UE10Bがトリガーを検出する事で、UE10BとUE10C間の通信をインフラストラクチャー通信T905から直接通信T901とRelay通信T903を介したUE-to-Network Relay通信にパス、または通信路を切り替える処理を示す。なお、本実施形態においては、処理の説明に用いる構成要素のみを利用して説明しており、例えば、他の装置(PGW等)の記載は省略している。
次に、図15の第1処理例とは異なる処理例として第2処理例を説明する。インフラストラクチャー通信からUE-to-Network Relay通信に切り替えを要求するトリガーがUE10BではなくProSeサーバ20で検知されて、ProSeサーバが通信路の切り替え処理を主導する場合について図16を用いて説明する。
[1.5.1 UE10Bの動作フロー]
図17に、図15、16のシーケンスを実現するUE10Bのフローチャート図の一例を示す。UE10Bは、インフラストラクチャー通信からUE-to-Network Relay通信に切り替える、何かしらのトリガーを検知するのを待機する(ステップS102)。ステップS102でパスの切り替えトリガーを検知した場合(ステップS102;Yes)、UE10BはProSeサーバ20に経路情報更新許可要求(flag1を含む)を送信する(ステップS104)。
図18に、図15、16のシーケンスを実現するRelay UE10Aのフローチャート図の一例を示す。Relay UE10AはUE10Bから直接通信要求を受信する(ステップS202)。ステップS202に基づいて、Relay UE10Aは、UE10Bからの要求を許可するかを判定する(ステップS203)。ステップS203で通信路の確立要求を許可した場合(ステップS203;Yes)、Relay UE10Aは、Relay UE10AとUE10BとにアウターIPを割り当てる(ステップS204)。
次に、図19に、図15、16のシーケンスを実現するProSeサーバ20のフローチャート図の一例を示す。ProSeサーバ20はパスの切り替えトリガーを検知するのを待機する、またはProSeサーバ20に登録されているUEから経路情報更新許可要求を受信するのを待機する(ステップS302)。
続いて第2実施形態について説明する。第2実施形態は、第1実施形態のシステムの機能構成は同様であり、第1実施形態と異なる処理フロー、動作フローを中心に説明する。
[2.1.1 第1処理例]
第2実施形態として、UE10BとRelay UE10A間の直接通信の通信路確立後にProSeサーバ20からUE10BとUE10Cに経路情報更新の指示が送られる場合の第1処理例について図20を用いて説明する。
次に、図20の異なる処理例として、パス切り替えのトリガーをUE10BではなくProSeサーバ20が検知し、ProSeサーバ20がパスまたは通信路の切り替えを主導する場合について図21を用いて説明する。なお、図20と同一の処理については同一の符号を付し、説明を省略する。
[2.2.1 UE10Bの動作フロー]
図22に図20、21のシーケンスを実現するUE10Bのフローチャート図の一例を示す。UE10Bは、何かしらのパスの切り替えのトリガーを検知する事を待機する(ステップS402)。
また、図23に、図20、21のシーケンスを実現するProSeサーバ20のフローチャート図の一例を示す。
続いて第3実施形態について説明する。本実施形態では、第1実施形態と同様に、ネットワークを介したインフラストラクチャー通信から、近隣UEをRelay1 UEとしたUE-to-Network Relay通信に切り替える為の通信システムについて、以下図面を用いながら説明する。
本実施形態では、図9のパスの切り替えの概念も利用する事ができ、詳細な説明は省略する。また、IPヘッダカプセル化によるRelayデータの流れや、ProSe registrationについても詳細な説明は省略する。
続いて、第3実施形態について説明する。本実施形態では、第3実施形態と同様に、ネットワークを介したインフラストラクチャー通信から、近隣UEをRelay UEとしたUE-to-Network Relayに切り替える為の通信システムについて、以下図面を用いながら説明する。
本実施形態では、図9のパスの切り替えの概念も利用する事ができ、詳細な説明は省略する。また、IPヘッダカプセル化によるRelayデータの流れや、ProSe registrationについても詳細な説明は省略する。
まず、本実施形態の第1処理例について説明する。図25は、UE10Bがパス切り替えのトリガーを検出する事で、UE10BとUE10C間の通信をインフラストラクチャー通信T905から直接通信T901とRelay通信T903を介したUE-to-Network Relay通信にパス、または通信路を切り替える処理を示す。
続いて、本実施形態の第2処理例について図26を用いて説明する。第2処理例の図26は、第1処理例の図25と異なる処理例である。図26は、ProSeサーバがUE10BとUE10C間の通信路またはパス経路の切り替えのトリガーを検知する方式の一例である。
続いて、各装置の動作フローについて説明する。
まず、図25、26のシーケンスを実現するUE10Bのフローチャート図の一例を図27に示す。UE10Bは、UE10Cとの通信を、インフラストラクチャー通信からUE-to-Network Relay通信へのパス切り替えを開始するための何かしらのトリガーを検知するのを待機する(ステップS602)。ここでパスの切り替えトリガーを検知した場合(ステップS602;Yes)、UE10BはProSeサーバ20に経路情報更新許可要求(flag1を含む)を送信する(ステップS604)。
次に、図28に、図25、26のシーケンスを実現するRelay UE10Aのフローチャート図の一例を示す。まず、Relay UE10AはProSeサーバ20から経路情報更新指示を受信する(ステップS702)。
続いて、第5実施形態について説明する。第5実施形態は、第4実施形態を変形した処理であり、ProSeサーバがUE10BとUE10Aのインフラストラクチャー通信から、UE10BがRelay UE10Aと直接通信を行ってUE10Cと通信するUE-to-Network Relay通信に、パスまたは通信路の切り替えを主導し、直接通信路確立後にProSeサーバ20からRelay UE10AとUE10Cとに経路情報更新の指示が送られる場合について説明する。
[5.1.1 第1処理例]
図29は、本実施形態におけるシーケンス図である。図29では、UE10BからProSeサーバ20に送信する信号に含まれる、指示または要求を示すフラグは「indication flag1-1」と「indication flag1-2」とする。
続いて、第2処理例について説明する。図30は図29の処理の異なる処理例である。図30は、ProSeサーバがUE10BとUE10C間の通信路またはパス経路の切り替えのトリガーを検知する方式の一例である。
[5.2.1 UE10Bの動作フロー]
図31に、図29と図30とのシーケンスを実現するUE10Bのフローチャート図の一例を示す。
また、図32に、図29、30のシーケンスを実現するProSeサーバ20のフローチャート図の一例を示す。
続いて、第6実施形態を説明する。本実施形態では、近隣UEをRelay UEとして直接通信で接続する、UE-to-Network Relay通信から、ネットワークを介したインフラストラクチャー通信に、パスまたは通信路を切り替える、またはパスまたは通信路を選択する通信システムについて、以下図面を用いながら説明する。
以下に、本実施形態で説明する処理の概要について説明する。図33は、本実施形態で実行されるパスの切り替え、及び通信路の切り替え及び、パスまたは通信路の選択の概念図を説明する。本実施形態の初期状態は、UE10BとUE10CがRelay UE10Aを介したUE-to-Network Relay通信(実線)T903で通信を行っている。なお、図33から分かる様に、UE10BとRelay UE10Aは直接通信T901で通信が行われている。
IPヘッダカプセル化によるRelayデータの流れや、ProSe registrationに関しては、図10~図14を利用する事ができ、詳細な説明は省略する。
続いて、第6実施形態におけるサービス継続手続きprocedureの処理の例について説明する。図34は、UE10Bが、UE-to-Network Relay通信からインフラストラクチャー通信への切り替えを要求するトリガーを検知し、パスまたは通信路を切り替える処理の一例を示す。
続いて第7実施形態について図35を用いて説明する。第7実施形態は、UE10BがRelay 10Aを検出し、経路情報を更新する処理である。なお、第1実施形態の図15と同一の処理には同一の符号を付して、詳細な説明を省略する。
UE10Bは、直接通信可能なRelay UE10Aに基づいて経路情報を更新する(S1522)。また、更新した結果を経路情報更新通知として、ProSeサーバ20に送信する(S2604)。
S1522とS2604の処理の順番は特に規定しない。UE10Bは、S1522の後にS2604を実行してもよいし、S2604の後にS1522を実行してもよいし、またはこれらを同時に実行してもよい。
以上、この発明の実施形態について図面を参照して詳述してきたが、具体的な構成はこの実施形態に限られるものではなく、この発明の要旨を逸脱しない範囲の設計等も特許請求の範囲に含まれる。
別にチップ化してもよいし、一部、または全部を集積してチップ化してもよい。また、集積回路化の手法はLSIに限らず専用回路、または汎用プロセッサで実現しても良い。また、半導体技術の進歩によりLSIに代替する集積回路化の技術が出現した場合、当該技術による集積回路を用いることも可能であることは勿論である。
3 IP移動通信ネットワーク
9 コアネットワーク
10、10A、10B、10C UE
20 ProSeサーバ
100 制御部
110 第1送受信部
112 送受信アンテナ
120 第2送受信部
122 送受信アンテナ
130 記憶部
132 ProSe ID管理テーブル
134 IPアドレス管理テーブル
136 アウターIPアドレス管理テーブル
138 DCM状態テーブル
142 経路情報テーブル
144 In coverageフラグ
200 制御部
210 通信部
220 記憶部
222 ProSe ID管理テーブル
224 In coverageフラグ
226 UE位置情報管理テーブル
300 制御部
310 第1送受信部
312 送受信アンテナ
315 Relay信号生成部
320 第2送受信部
314 送受信アンテナ
330 記憶部
332 ProSe ID管理テーブル
334 IPアドレス管理テーブル
336 アウターIPアドレス管理テーブル
338 DCM状態テーブル
340 In coverageフラグ
Claims (5)
- 第1の端末装置とコアネットワークを介して通信を行う第2の端末装置が送信する経路情報更新要求メッセージを第1の端末装置から受信し、
前記経路情報更新要求メッセージには、少なくとも通信の切り替えを要求することを示す識別情報が含まれており、
前記識別情報に基づいて、リレー機能を有する第3の端末装置を選択し、
前記経路情報更新要求メッセージの応答であり、前記第3の端末装置の情報を含む経路更新指示メッセージを前記第1の端末装置に送信し、前記第3の端末装置とLTEを用いた直接通信を行って前記第1の端末装置と通信することを指示する、
ことを特徴とするサーバ装置。 - 経路更新指示メッセージを前記第2の端末装置に送信し、前記第3の端末装置とLTEを用いた直接通信を行う前記第2の端末装置と通信することを更に指示する、ことを特徴とする請求項1に記載のサーバ装置。
- 第1の端末装置と第2の端末装置のコアネットワークを介して通信する第1の通信と、前記第2の端末装置が第3の端末装置と直接通信を行って第1の端末装置と通信する第2の通信との切り替えを主導し、
リレー機能を有する前記第3の端末装置を選択し、
前記第3の端末装置の情報を含む経路更新指示メッセージを前記第2の端末装置に送信し、前記第2の通信への切り替えを指示する、
ことを特徴とするサーバ装置。 - 前記経路更新指示メッセージを前記第1の端末装置に送信し、前記第3の端末とLTEを用いた直接通信を行う前記第2の端末装置と通信することを更に指示する、ことを特徴とする請求項3に記載のサーバ装置。
- 第2の端末装置と、コアネットワークを介して通信を行う第1の端末装置であって、
パス切り替えトリガーを検知することにより、少なくとも通信の切り替えを要求することを示す識別情報が含まれている経路情報更新要求メッセージをサーバ装置に送信し、
前記サーバ装置から、サーバ装置が選択したリレー機能を有する第3の端末装置の情報を含む経路更新指示メッセージを受信し、
前記経路更新指示メッセージに従って、前記第3の端末装置とLTEを用いた直接通信を行って前記第2の端末装置と通信する、
ことを特徴とする第1の端末装置。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP15768330.1A EP3125613A4 (en) | 2014-03-24 | 2015-03-23 | Server device and terminal device |
US15/128,568 US20170111273A1 (en) | 2014-03-24 | 2015-03-23 | Server device and terminal device |
JP2016510347A JPWO2015146910A1 (ja) | 2014-03-24 | 2015-03-23 | サーバ装置及び端末装置 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2014060625 | 2014-03-24 | ||
JP2014-060625 | 2014-03-24 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2015146910A1 true WO2015146910A1 (ja) | 2015-10-01 |
Family
ID=54195423
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2015/058735 WO2015146910A1 (ja) | 2014-03-24 | 2015-03-23 | サーバ装置及び端末装置 |
Country Status (4)
Country | Link |
---|---|
US (1) | US20170111273A1 (ja) |
EP (1) | EP3125613A4 (ja) |
JP (2) | JPWO2015146910A1 (ja) |
WO (1) | WO2015146910A1 (ja) |
Families Citing this family (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11284337B2 (en) * | 2015-03-27 | 2022-03-22 | Qualcomm Incorporated | Selection of proximity services relay |
US20180176851A1 (en) * | 2015-04-30 | 2018-06-21 | Lg Electronics Inc. | Method and device for transmitting/receiving data in mesh network using bluetooth |
US9723543B2 (en) * | 2015-07-08 | 2017-08-01 | Blackberry Limited | Systems and methods for managing a UE-to-network relay |
WO2017026791A1 (en) * | 2015-08-12 | 2017-02-16 | Lg Electronics Inc. | Method for discoveering relay ue via d2d link at ue in wireless communication system and apparatus therefor |
US10945179B2 (en) * | 2017-01-10 | 2021-03-09 | Huawei Technologies Co., Ltd. | Communication path switching method and device |
CN109561429B (zh) * | 2017-09-25 | 2020-11-17 | 华为技术有限公司 | 一种鉴权方法及设备 |
US20240080730A1 (en) * | 2020-12-22 | 2024-03-07 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for relay selection |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2006332862A (ja) * | 2005-05-24 | 2006-12-07 | Mitsubishi Electric Corp | 通信装置 |
JP2011029990A (ja) * | 2009-07-27 | 2011-02-10 | Fujitsu Ltd | 通信制御装置、移動端末装置および無線通信方法 |
JP2011049929A (ja) * | 2009-08-28 | 2011-03-10 | Advanced Telecommunication Research Institute International | 端末装置およびそれを備えた通信ネットワークシステム |
JP2012249002A (ja) * | 2011-05-26 | 2012-12-13 | Panasonic Corp | 通信システム、通信端末装置及び通信方法 |
WO2013112465A1 (en) * | 2012-01-27 | 2013-08-01 | Intel Corporation | Centralized control of intra-cell device-to-device communication |
Family Cites Families (24)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
TW569603B (en) * | 2002-10-01 | 2004-01-01 | Quanta Comp Inc | Serving radio network controller relocation in radio telecommunication system |
US8131281B1 (en) * | 2007-09-12 | 2012-03-06 | Oceans' Edge, Inc. | Mobile device monitoring and control system |
US9648493B2 (en) * | 2007-11-16 | 2017-05-09 | Qualcomm Incorporated | Using identifiers to establish communication |
US9072060B2 (en) * | 2008-06-03 | 2015-06-30 | Nokia Technologies Oy | Method, apparatus and computer program for power control to mitigate interference |
JP2013520100A (ja) * | 2010-02-12 | 2013-05-30 | インターデイジタル パテント ホールディングス インコーポレイテッド | マシン間通信におけるアクセス制御および輻輳制御 |
US8738745B1 (en) * | 2010-03-31 | 2014-05-27 | Amazon Technologies, Inc. | Managing use of intermediate destination hardware devices for provided computer networks |
WO2012050841A1 (en) * | 2010-09-28 | 2012-04-19 | Research In Motion Corporation | Method and apparatus for releasing connection with local gw when ue moves out of the residential/enterprise network coverage |
EP2509345A1 (en) * | 2011-04-05 | 2012-10-10 | Panasonic Corporation | Improved small data transmissions for machine-type-communication (MTC) devices |
JP5898334B2 (ja) * | 2011-12-08 | 2016-04-06 | インターデイジタル パテント ホールディングス インコーポレイテッド | クロスリンク確立を制御するための方法および装置 |
WO2013131234A1 (en) * | 2012-03-05 | 2013-09-12 | Renesas Mobile Corporation | Methods, apparatuses, and computer-readable storage media for relaying traffic in d2d communications |
JPWO2014024342A1 (ja) * | 2012-08-06 | 2016-07-25 | 日本電気株式会社 | 通信装置、通信方法、プログラム、及び配信サーバ |
US9672527B2 (en) * | 2013-01-21 | 2017-06-06 | Tejas Networks Limited | Associating and consolidating MME bearer management functions |
US20140244765A1 (en) * | 2013-02-28 | 2014-08-28 | Stanley Benjamin Smith | System and method for messaging and notification. |
KR20150139602A (ko) * | 2013-04-05 | 2015-12-11 | 인터디지탈 패튼 홀딩스, 인크 | 보안화 피어-투-피어 및 그룹 통신들 |
GB2514580B (en) * | 2013-05-29 | 2015-09-23 | Broadcom Corp | Method and apparatus for providing routing |
US9622035B2 (en) * | 2013-07-04 | 2017-04-11 | Lg Electronics Inc. | Relay control method for proximity service and device therefor |
US9713072B2 (en) * | 2013-07-29 | 2017-07-18 | Htc Corporation | Method of relay discovery and communication in a wireless communications system |
CN103634812B (zh) * | 2013-11-27 | 2017-03-15 | 西安电子科技大学 | 一种基于用户设备中继同小区设备到设备直传通信的方法 |
CN106165524B (zh) * | 2014-01-29 | 2020-01-07 | 交互数字专利控股公司 | 用于设备到设备发现或通信的资源选择 |
JP6313477B2 (ja) * | 2014-02-10 | 2018-04-18 | テレフオンアクチーボラゲット エルエム エリクソン(パブル) | タイミング測定に基づくデバイスツーデバイス通信のための送信構成適合 |
GB2523328A (en) * | 2014-02-19 | 2015-08-26 | Nec Corp | Communication system |
US10080185B2 (en) * | 2015-04-10 | 2018-09-18 | Qualcomm Incorporated | Method and apparatus for securing structured proximity service codes for restricted discovery |
WO2017007949A1 (en) * | 2015-07-07 | 2017-01-12 | M87, Inc. | Network methods and apparatus |
US20170257751A1 (en) * | 2016-03-05 | 2017-09-07 | Ofinno Technologies, Llc | Off-Network Wireless Mission Critical Session Initiation |
-
2015
- 2015-03-23 EP EP15768330.1A patent/EP3125613A4/en not_active Withdrawn
- 2015-03-23 WO PCT/JP2015/058735 patent/WO2015146910A1/ja active Application Filing
- 2015-03-23 US US15/128,568 patent/US20170111273A1/en not_active Abandoned
- 2015-03-23 JP JP2016510347A patent/JPWO2015146910A1/ja not_active Ceased
-
2019
- 2019-09-13 JP JP2019167523A patent/JP2020010385A/ja active Pending
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2006332862A (ja) * | 2005-05-24 | 2006-12-07 | Mitsubishi Electric Corp | 通信装置 |
JP2011029990A (ja) * | 2009-07-27 | 2011-02-10 | Fujitsu Ltd | 通信制御装置、移動端末装置および無線通信方法 |
JP2011049929A (ja) * | 2009-08-28 | 2011-03-10 | Advanced Telecommunication Research Institute International | 端末装置およびそれを備えた通信ネットワークシステム |
JP2012249002A (ja) * | 2011-05-26 | 2012-12-13 | Panasonic Corp | 通信システム、通信端末装置及び通信方法 |
WO2013112465A1 (en) * | 2012-01-27 | 2013-08-01 | Intel Corporation | Centralized control of intra-cell device-to-device communication |
Non-Patent Citations (1)
Title |
---|
See also references of EP3125613A4 * |
Also Published As
Publication number | Publication date |
---|---|
EP3125613A4 (en) | 2017-09-20 |
JPWO2015146910A1 (ja) | 2017-04-13 |
US20170111273A1 (en) | 2017-04-20 |
JP2020010385A (ja) | 2020-01-16 |
EP3125613A1 (en) | 2017-02-01 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2015146910A1 (ja) | サーバ装置及び端末装置 | |
US20220369215A1 (en) | Relay selection in cellular sliced networks | |
EP3499965B1 (en) | Communication system, communication device, and program | |
JP7503625B2 (ja) | ルーティングおよびベアラマッピング構成のための方法およびデバイス | |
WO2015068731A1 (ja) | 端末装置、リレー端末装置および通信制御方法 | |
JP6407859B2 (ja) | Ue、サーバ装置及び通信方法 | |
JP6728436B2 (ja) | UE、UEの通信方法、ProSeサーバ及びProSeサーバの通信方法 | |
JP5784572B2 (ja) | 無線通信システムおよび制御方法 | |
US9504074B2 (en) | Method of providing proximity service communication between terminals supporting proximity service communications | |
JP6356118B2 (ja) | Ue、制御装置及び通信方法 | |
WO2014148257A1 (ja) | 端末装置、基地局装置および制御装置 | |
WO2014163054A1 (ja) | 端末装置、基地局装置および制御装置 | |
WO2015170690A1 (ja) | 通信制御方法、端末装置、サーバ装置および通信システム | |
WO2018129807A1 (zh) | 通信方法、网络开放功能网元和控制面网元 | |
WO2022171017A1 (zh) | 一种通信方法、装置及*** | |
Shetty | 5G Mobile Core Network | |
WO2017168999A1 (ja) | 無線通信装置、サーバ及び方法 | |
EP3282722A1 (en) | Terminal device, pgw, and mme | |
WO2014156663A1 (ja) | 端末装置、基地局装置および制御装置 | |
CN107431873B (zh) | 终端装置、分组数据网络网关及可信无线区域网络接入网关 | |
CN114902726B (zh) | 一种数据处理方法、通信装置和通信*** | |
JP6632947B2 (ja) | 端末装置、無線通信システム、及び通信方法 | |
CN116584150A (zh) | 一种中继通信方法及装置 | |
WO2008072565A1 (ja) | QoS早期確立方法、その方法で用いられる移動端末、その方法で用いられるアクセスルータ、その方法で用いられる通信装置 | |
KR20190127305A (ko) | 엑스홀 네트워크를 포함하는 통신 시스템에서 경로 설정 방법 및 장치 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 15768330 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2016510347 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 15128568 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REEP | Request for entry into the european phase |
Ref document number: 2015768330 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2015768330 Country of ref document: EP |