WO2014129453A1 - 移動通信システム、ユーザ端末及び基地局 - Google Patents
移動通信システム、ユーザ端末及び基地局 Download PDFInfo
- Publication number
- WO2014129453A1 WO2014129453A1 PCT/JP2014/053743 JP2014053743W WO2014129453A1 WO 2014129453 A1 WO2014129453 A1 WO 2014129453A1 JP 2014053743 W JP2014053743 W JP 2014053743W WO 2014129453 A1 WO2014129453 A1 WO 2014129453A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- communication
- spreading code
- user terminal
- network
- communication system
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/14—Direct-mode setup
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/24—Accounting or billing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/005—Discovery of network devices, e.g. terminals
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/16—Interfaces between hierarchically similar devices
- H04W92/18—Interfaces between hierarchically similar devices between terminal devices
Definitions
- the present invention relates to a mobile communication system, a user terminal, and a base station that support D2D communication.
- D2D communication a plurality of adjacent user terminals perform direct communication without going through a network. That is, the data path of D2D communication does not go through the network.
- the data path of normal communication (cellular communication) of the mobile communication system passes through the network.
- the communication status in cellular communication can be easily managed by the network.
- the present invention provides a mobile communication system, a user terminal, and a base station that can facilitate the operation for D2D communication.
- the mobile communication system supports cellular communication in which a data path passes through a network and D2D communication in which a data path does not pass through the network and is direct inter-terminal communication.
- a frequency division multiplexing scheme is applied to the cellular communication, and a code division multiplexing scheme is applied to the D2D communication.
- the network allocates a spreading code having orthogonality to the user terminal in response to a request from the user terminal.
- the user terminal performs the D2D communication using the spreading code assigned from the network.
- FIG. 1 is a configuration diagram of an LTE system.
- FIG. 2 is a block diagram of the UE.
- FIG. 3 is a block diagram of the eNB.
- FIG. 4 is a protocol stack diagram of a radio interface in the LTE system.
- FIG. 5 is a configuration diagram of a radio frame used in the LTE system.
- FIG. 6 is a diagram for explaining a direct communication mode in D2D communication.
- FIG. 7 is a diagram for explaining frequency allocation according to the first embodiment.
- FIG. 8 is a diagram for explaining the operating environment according to the first embodiment.
- FIG. 9 is a sequence diagram according to the first embodiment.
- FIG. 10 is a sequence diagram according to the first modification of the first embodiment.
- FIG. 11 is a sequence diagram according to the second modification of the first embodiment.
- FIG. 10 is a sequence diagram according to the first modification of the first embodiment.
- FIG. 11 is a sequence diagram according to the second modification of the first embodiment.
- FIG. 12 is a partial modification of the sequence diagram of FIG.
- FIG. 13 is a sequence diagram according to the third modification of the first embodiment.
- FIG. 14 is a diagram for explaining the data transmission method according to the fourth modification of the first embodiment.
- FIG. 15 is a diagram illustrating a transmission data format according to Modification 6 of the first embodiment.
- FIG. 16 is a flowchart according to Modification 7 of the first embodiment.
- FIG. 17 is a sequence diagram according to the eighth modification of the first embodiment.
- FIG. 18 is a partial modification of the sequence diagram of FIG.
- FIG. 19 is a sequence diagram according to the second embodiment.
- FIG. 20 is a sequence diagram according to Modification 1 of the second embodiment.
- FIG. 21 is a sequence diagram according to the second modification of the second embodiment.
- FIG. 22 is a sequence diagram according to the third modification of the second embodiment.
- FIG. 23 is a diagram for explaining the outline of the operation according to the third embodiment.
- FIG. 24 is a sequence diagram according to the third embodiment.
- FIG. 25 is a diagram for explaining the outline of the operation according to the fourth embodiment.
- FIG. 26 is a sequence diagram according to the fourth embodiment.
- FIG. 27 is a diagram for explaining an operation outline according to the first modification of the fourth embodiment.
- FIG. 28 is a sequence diagram according to the first modification of the fourth embodiment.
- FIG. 29 is a partial modification of the sequence diagram of FIG.
- FIG. 30 is a diagram for explaining an operation outline according to the second modification of the fourth embodiment.
- FIG. 31 is a sequence diagram according to the second modification of the fourth embodiment.
- FIG. 32 is a diagram for explaining an operation outline according to the third modification of the fourth embodiment.
- FIG. 33 is a sequence diagram according to the fifth embodiment.
- FIG. 34 is a diagram for explaining an operation according to the first modification of the fifth embodiment.
- FIG. 35 is a sequence diagram according to the second modification of the fifth embodiment.
- FIG. 36 is a sequence diagram when the number of UEs included in the D2D UE group increases according to the sixth embodiment.
- FIG. 37 is a sequence diagram when the number of UEs included in the D2D UE group decreases according to the sixth embodiment.
- FIG. 38 is a diagram for explaining an operation according to the seventh embodiment (part 1).
- FIG. 39 is a diagram for explaining an operation according to the seventh embodiment (No. 2).
- FIG. 40 is a diagram for explaining an operation according to the seventh embodiment (part 3).
- FIG. 41 is a diagram for explaining the operating environment according to the eighth embodiment.
- the mobile communication system supports cellular communication in which a data path passes through a network and D2D communication that is direct terminal-to-terminal communication in which a data path does not pass through the network.
- a frequency division multiplexing scheme is applied to the cellular communication, and a code division multiplexing scheme is applied to the D2D communication.
- the network allocates a spreading code having orthogonality to the user terminal in response to a request from the user terminal.
- the user terminal performs the D2D communication using the spreading code assigned from the network.
- the network charges for the use of the spreading code by the user terminal.
- an effective time is set for the spreading code.
- the user terminal assigned with the spreading code requests the network to reassign the spreading code in order to continue the D2D communication.
- the network includes at least one of an elapsed time of the D2D communication by the user terminal, an application used by the user terminal for the D2D communication, a charging contract of the user terminal, and a moving speed of the user terminal.
- the effective time is controlled on the basis of the above.
- the user terminal requests the network to reallocate the spreading code in response to detecting the deterioration of the communication quality of the D2D communication even before the valid time expires.
- the user terminal notifies the network of the end of the D2D communication when the D2D communication is ended before the valid time expires.
- the network assigns a spreading code different from the spreading code before the reassignment to the user terminal.
- the network assigns the spreading code for transmission in the D2D communication and the spreading code for reception in the D2D communication to the user terminal.
- the network is connected to the user terminal based on at least one of the communication quality of the D2D communication in the user terminal and the number of user terminals performing the D2D communication in a cell to which the user terminal belongs.
- the code length of the spreading code to be assigned is controlled.
- the network instructs the user terminal to switch from the D2D communication to the cellular communication when it is determined that the code length of the spreading code assigned to the user terminal exceeds a predetermined length.
- the user terminal holds an initial spreading code having no orthogonality.
- the user terminal performs the D2D communication using the initial spreading code even when the spreading code is not assigned from the network.
- the user terminal that performs the D2D communication using the initial spreading code requests the network to assign the spreading code in response to detecting the deterioration of the communication quality of the D2D communication.
- the network when the network determines that the communication quality is improved by assigning the spreading code, the network assigns the spreading code to the user terminal.
- the user terminal that performs the D2D communication using the initial spreading code performs transmission in the D2D communication based on a result of monitoring an interference wave signal.
- the network assigns the spreading code to a user terminal group including the user terminal and another user terminal that should perform the D2D communication with the user terminal.
- the network controls the number of spreading codes assigned to the user terminal group based on the number of user terminals included in the user terminal group.
- the network controls the number of spreading codes assigned to the user terminal group based on the number of user terminals included in the user terminal group.
- the network rejects the assignment of the spreading code to the user terminal group when the user terminal of the accounting contract that does not allow the D2D communication is included in the user terminal group.
- the network notifies the user terminal of transmission / reception start timing of the D2D communication based on the timing of the cellular communication.
- the network includes a plurality of cells.
- Each of the plurality of cells notifies the neighboring cell of the allocation status of the spreading code in its own cell.
- the network assigns the spreading code to the user terminal based on an identifier associated with the user terminal.
- the user terminal that performs the D2D communication using the spreading code applies the spreading code to each of a plurality of subcarriers to perform transmission.
- the user terminal performing the D2D communication when transmitting the data, adds information indicating an application corresponding to the data to the data and transmits the data.
- the network broadcasts information indicating a spreading code to be used for discovery processing for discovering a nearby terminal to be a communication partner in the D2D communication.
- the network includes a server device that is shared by a plurality of communication carriers and that assigns the spreading code.
- the user terminal is used in a mobile communication system that supports cellular communication in which a data path passes through a network and D2D communication in which a data path does not pass through the network and is direct inter-terminal communication.
- the user terminal includes a control unit that performs the D2D communication using a spreading code assigned from the network and having orthogonality.
- a frequency division multiplexing scheme is applied to the cellular communication, and a code division multiplexing scheme is applied to the D2D communication.
- the base station is used in a mobile communication system that supports cellular communication in which a data path passes through a network and D2D communication that is direct terminal-to-terminal communication in which a data path does not pass through the network.
- the base station includes a control unit that assigns orthogonal spreading codes to the user terminal for the D2D communication in response to a request from the user terminal.
- a frequency division multiplexing scheme is applied to the cellular communication, and a code division multiplexing scheme is applied to the D2D communication.
- FIG. 1 is a configuration diagram of an LTE system according to the first embodiment.
- the LTE system includes a plurality of UEs (User Equipment) 1A to 1C, an E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) 10, and an EPC (Evolved Packet Core) 20.
- the E-UTRAN 10 corresponds to a radio access network
- the EPC 20 corresponds to a core network.
- the E-UTRAN 10 and the EPC 20 constitute an LTE system network.
- UE1 is a mobile communication device and performs wireless communication with a connection destination cell (serving cell).
- UE1 corresponds to a user terminal.
- the E-UTRAN 10 includes a plurality of eNBs (evolved Node-B) 2A to 2C.
- eNB2 corresponds to a base station.
- the eNB 2 manages one or a plurality of cells and performs radio communication with the UE 1 that has established a connection with the own cell.
- “cell” is used as a term indicating a minimum unit of a radio communication area, and is also used as a term indicating a function of performing radio communication with the UE 1.
- ENB 2 has, for example, a radio resource management (RRM) function, a user data routing function, and a measurement control function for mobility control and scheduling.
- RRM radio resource management
- the EPC 20 includes a plurality of MME (Mobility Management Entity) / S-GW (Serving-Gateway) 3A and 3B, and a billing server 4.
- MME Mobility Management Entity
- S-GW Serving-Gateway
- the MME is a network node that performs various types of mobility control for the UE 1 and corresponds to a control station.
- the S-GW is a network node that performs transfer control of user data, and corresponds to an exchange.
- the billing server 4 is a network node that manages billing for the UE1. Although details will be described later, the charging server 4 not only charges for cellular communication but also charges for D2D communication.
- ENB2 is connected to each other via the X2 interface. Moreover, eNB2 is connected with EPC20 via S1 interface.
- FIG. 2 is a block diagram of UE1.
- the UE 1 includes an antenna 101, a radio transceiver 110, a user interface 120, a GNSS (Global Navigation Satellite System) receiver 130, a battery 140, a memory 150, and a processor 160.
- the memory 150 and the processor 160 constitute a control unit.
- UE1 may not have the GNSS receiver 130.
- the memory 150 may be integrated with the processor 160, and this set (that is, a chip set) may be used as the processor 160 '.
- the antenna 101 and the wireless transceiver 110 are used for transmitting and receiving wireless signals.
- the antenna 101 includes a plurality of antenna elements.
- the radio transceiver 110 converts the baseband signal output from the processor 160 into a radio signal and transmits it from the antenna 101. Further, the radio transceiver 110 converts a radio signal received by the antenna 101 into a baseband signal and outputs the baseband signal to the processor 160.
- the user interface 120 is an interface with a user who owns the UE 1 and includes, for example, a display, a microphone, a speaker, and various buttons.
- the user interface 120 receives an operation from the user and outputs a signal indicating the content of the operation to the processor 160.
- the GNSS receiver 130 receives a GNSS signal and outputs the received signal to the processor 160 in order to obtain location information indicating the geographical location of the UE 1.
- the battery 140 stores power to be supplied to each block of the UE1.
- the memory 150 stores a program executed by the processor 160 and information used for processing by the processor 160.
- the processor 160 includes a baseband processor that modulates / demodulates and encodes / decodes a baseband signal, and a CPU (Central Processing Unit) that executes programs stored in the memory 150 and performs various processes. .
- the processor 160 may further include a codec that performs encoding / decoding of an audio / video signal.
- the processor 160 executes various processes and various communication protocols described later.
- FIG. 3 is a block diagram of eNB2. As illustrated in FIG. 3, the eNB 2 includes an antenna 201, a radio transceiver 210, a network interface 220, a memory 230, and a processor 240. The memory 230 and the processor 240 constitute a control unit.
- the antenna 201 and the wireless transceiver 210 are used for transmitting and receiving wireless signals.
- the antenna 201 includes a plurality of antenna elements.
- the wireless transceiver 210 converts the baseband signal output from the processor 240 into a wireless signal and transmits it from the antenna 201.
- the radio transceiver 210 converts a radio signal received by the antenna 201 into a baseband signal and outputs the baseband signal to the processor 240.
- the network interface 220 is connected to the neighboring eNB 2 via the X2 interface and is connected to the MME / S-GW via the S1 interface.
- the network interface 220 is used for communication performed on the X2 interface and communication performed on the S1 interface.
- the memory 230 stores a program executed by the processor 240 and information used for processing by the processor 240.
- the processor 240 includes a baseband processor that performs modulation / demodulation and encoding / decoding of a baseband signal, and a CPU that executes a program stored in the memory 230 and performs various processes.
- the processor 240 executes various processes and various communication protocols described later.
- FIG. 4 is a protocol stack diagram of a radio interface in the LTE system. As shown in FIG. 4, the radio interface protocol is divided into layers 1 to 3 of the OSI reference model, and layer 1 is a physical (PHY) layer. Layer 2 includes a MAC (Media Access Control) layer, an RLC (Radio Link Control) layer, and a PDCP (Packet Data Convergence Protocol) layer. Layer 3 includes an RRC (Radio Resource Control) layer.
- PHY Physical
- Layer 2 includes a MAC (Media Access Control) layer, an RLC (Radio Link Control) layer, and a PDCP (Packet Data Convergence Protocol) layer.
- Layer 3 includes an RRC (Radio Resource Control) layer.
- RRC Radio Resource Control
- the physical layer performs encoding / decoding, modulation / demodulation, antenna mapping / demapping, and resource mapping / demapping. Data is transmitted through a physical channel between the physical layer of UE1 and the physical layer of eNB2.
- the MAC layer performs data priority control, retransmission processing by hybrid ARQ (HARQ), and the like. Data is transmitted via the transport channel between the MAC layer of UE1 and the MAC layer of eNB2.
- the MAC layer of the eNB 2 includes a scheduler that determines uplink / downlink transport formats (transport block size, modulation / coding scheme (MCS)) and allocated resource blocks.
- MCS modulation / coding scheme
- the RLC layer transmits data to the RLC layer on the receiving side using the functions of the MAC layer and the physical layer. Between the RLC layer of UE1 and the RLC layer of eNB2, data is transmitted via a logical channel.
- the PDCP layer performs header compression / decompression and encryption / decryption.
- the RRC layer is defined only in the control plane. Control (RRC) for various settings is transmitted between the RRC layer of UE1 and the RRC layer of eNB2.
- the RRC layer controls the logical channel, the transport channel, and the physical channel according to establishment, re-establishment, and release of the radio bearer. If there is an RRC connection between the RRC of UE1 and the RRC of eNB2, UE1 is in a connected state (RRC connected state), otherwise UE1 is in an idle state (RRC idle state).
- the NAS (Non-Access Stratum) layer located above the RRC layer performs session management and mobility management.
- FIG. 5 is a configuration diagram of a radio frame used in the LTE system.
- a frequency division multiplexing system is applied to the LTE system. Specifically, OFDMA (Orthogonal Frequency Division Multiplexing Access) is applied to the downlink, and SC-FDMA (Single Carrier Frequency Multiple Access) is applied to the uplink.
- OFDMA Orthogonal Frequency Division Multiplexing Access
- SC-FDMA Single Carrier Frequency Multiple Access
- the radio frame is composed of 10 subframes arranged in the time direction, and each subframe is composed of two slots arranged in the time direction.
- the length of each subframe is 1 ms, and the length of each slot is 0.5 ms.
- Each subframe includes a plurality of resource blocks (RB) in the frequency direction and includes a plurality of symbols in the time direction.
- the resource block includes a plurality of subcarriers in the frequency direction.
- the section of the first few symbols of each subframe is a control region used mainly as a physical downlink control channel (PDCCH) for transmitting a control signal.
- the remaining section of each subframe is an area that can be used as a physical downlink shared channel (PDSCH) mainly for transmitting user data.
- PDSCH physical downlink shared channel
- both ends in the frequency direction in each subframe are control regions mainly used as a physical uplink control channel (PUCCH) for transmitting a control signal.
- the central portion in the frequency direction in each subframe is an area that can be used as a physical uplink shared channel (PUSCH) mainly for transmitting user data.
- PUSCH physical uplink shared channel
- the LTE system according to the first embodiment supports D2D communication that is direct UE-to-UE communication.
- D2D communication will be described in comparison with normal communication (cellular communication) of the LTE system.
- the data path passes through the core network EPC 20.
- a data path is a communication path for user data (user plane).
- D2D communication a data path set between UEs does not pass through the EPC 20. Therefore, the traffic load of the EPC 20 can be reduced.
- the UE1 discovers another UE1 existing in the vicinity and starts D2D communication.
- the D2D communication includes a direct communication mode and a local relay mode (Locally Routed mode).
- FIG. 6 is a diagram for explaining a direct communication mode in D2D communication.
- the data path does not pass through the eNB2.
- UE1A and UE1B that are close to each other perform radio communication directly with low transmission power in the cell of eNB2. Therefore, it is possible to obtain merits such as reduction of power consumption of the UE 1 and reduction of interference with adjacent cells.
- UE1A and UE1B are D2D UEs (D2D terminals) that perform D2D communication in the direct communication mode in the cell of eNB2.
- UE1A and UE1B in the connected state perform D2D communication using radio resources allocated from eNB2.
- UE1A and UE1B transmit / receive user data to / from each other, and transmit / receive control signals to / from eNB2.
- control of D2D communication is performed by eNB2 initiative.
- UE1C is a cellular UE (cellular terminal) that performs cellular communication in the cell of eNB2.
- UE1C in a connection state performs cellular communication using the radio
- UE1C transmits / receives user data and a control signal with eNB2.
- the data path between the UEs passes through the eNB 2, but the data path does not pass through the EPC 20. That is, in the local relay mode, UE1A and UE1B perform radio communication via eNB2 without passing through EPC20.
- the local relay mode can reduce the traffic load of the EPC 20, but has less merit than the direct communication mode. Therefore, in the first embodiment, the direct communication mode is mainly assumed.
- D2D communication is performed within the frequency band (license band) of the LTE system.
- FIG. 7 is a diagram for explaining frequency allocation according to the first embodiment. As shown in FIG. 7, the frequency band of the LTE system is divided into a frequency band for cellular communication and a frequency band for D2D communication. Such frequency allocation can avoid interference between cellular communication and D2D communication.
- frequency division multiplexing is applied to cellular communication
- code division multiplexing is applied to D2D communication. That is, for the cellular UE, multiplexing is realized by assigning different frequency resources (resource blocks). For D2D UEs, multiplexing is realized by assigning different spreading codes.
- FIG. 8 is a diagram for explaining the operating environment according to the first embodiment. As shown in FIG. 8, a plurality of UEs 1A to 1D are located in the cell of eNB2. Each of the plurality of UEs 1A to 1D holds an initial spreading code (for example, all 1) that does not have orthogonality.
- an initial spreading code for example, all 1
- UE1B discovers UE1A by the discovery process of discovering a nearby UE that should be a communication partner of D2D communication, and starts D2D communication with UE1A.
- UE1A and 1B perform D2D communication (guaranteed D2D communication) using the spreading code allocated from eNB2. Guaranteed D2D communication is subject to billing by the billing server 4. Since the spreading code assigned from the eNB 2 has orthogonality, good communication quality and high confidentiality are guaranteed in the guaranteed D2D communication.
- Non-guaranteed D2D communication is not charged by the charging server 4, that is, is free of charge.
- Non-guaranteed D2D communication can be used free of charge, but communication quality and confidentiality are not guaranteed.
- FIG. 9 is a sequence diagram according to the first embodiment. Here, after UE1A and 1B complete a discovery process, the operation
- UE1B in the connected state in the cell of eNB2 transmits a D2D request for requesting allocation for D2D communication to eNB2 (S1).
- the D2D request includes an identifier of each UE1 (UE1A and 1B) that requests allocation.
- UE1A and 1B identifiers of UE1A, UE1B,... are appropriately expressed as “UE1A”, “UE1B”,.
- the eNB 2 that has received the D2D request calculates a spreading code having orthogonality according to the D2D request (S2).
- a spreading code having orthogonality for example, a Walsh code can be used.
- the eNB 2 knows the spreading code being allocated in the neighboring eNB (described later in the seventh embodiment), it is preferable to calculate a spreading code that does not overlap with the spreading code being allocated in the neighboring eNB.
- eNB2 transmits D2D permission for permitting D2D communication to UE1A and 1B (S3, S4).
- the D2D permission includes code information indicating the calculated spreading code (assignment spreading code) and an identifier of each UE1 (UE1A and 1B) that is permitted to perform D2D communication. Thereby, a spreading code is assigned to UE1A and 1B.
- the eNB 2 that assigned the spreading codes to the UEs 1A and 1B transmits D2D charging information for charging the use of the spreading codes by the UEs 1A and 1B to the charging server 4 (S8).
- the D2D charging information includes an identifier of each charging target UE1 (UE1A and 1B).
- the charging server 4 charges each UE 1 (UE 1A and 1B) corresponding to the identifier included in the D2D charging (S9).
- the UEs 1A and 1B that have received the D2D permission from the eNB 2 set spreading codes corresponding to the code information (here, code1) included in the D2D permission (S5, S6). And UE1A and 1B perform D2D communication using the set spreading code (S7).
- the network eNB 2 and charging server 4
- the network can appropriately charge D2D communication by charging for the use of the spreading code.
- UE1C and 1D which perform non-guaranteed D2D communication cannot guarantee communication quality and confidentiality, they can use D2D communication.
- One of the UE 1A and the UE 1B may be a UE that can control the other UE in the D2D communication (hereinafter referred to as “anchor UE”).
- anchor UE a UE that can control the other UE in the D2D communication
- the other UE (communication partner UE) can transmit / receive the anchor UE to / from the anchor UE without transmitting / receiving the control signal to / from the eNB 2.
- FIG. 10 is a sequence diagram according to the first modification of the first embodiment. Here, the case where UE1B is an anchor UE is demonstrated.
- the eNB 2 transmits D2D permission only to the UE 1B (S3). That is, eNB2 notifies the assigned spreading code only to UE1B.
- signaling between the eNB and the UE can be reduced by notifying the UE 1A of the assigned spreading code via the UE 1B.
- UE1A and UE1B are not limited to being located in the same cell, but may be located in different cells.
- FIG. 11 is a sequence diagram according to the second modification of the first embodiment.
- UE1B is located in the cell of eNB2A and UE1A is located in the cell of eNB2B will be described.
- the eNB 2A that has calculated the spreading code (S2) transmits a D2D permission to the UE 1B (S3), and transmits a D2D permission to the eNB 2B (S3 ').
- the UE 1A and the UE 1B can perform D2D communication even if they are located in different cells.
- FIG. 12 is a partial modification of the sequence diagram of FIG. As shown in FIG. 12, when UE1A and UE1B are located in different cells, UE1B operates as an anchor UE. UE1B which received D2D permission from eNB2A transfers D2D permission to UE1A (S4).
- FIG. 13 is a sequence diagram according to the third modification of the first embodiment.
- UE1A and 1B set a spreading code (S5, S6), and then try D2D communication using the spreading code (S11, S12).
- the UEs 1A and 1B transmit a D2D permission reply indicating the trial success to the eNB 2 (S13, S14), and start D2D communication (S7).
- the eNB 2 transmits D2D charging information to the charging server 4 when receiving a D2D permission reply indicating a successful trial (S8).
- the billing server 4 that has received the D2D billing information charges the UEs 1A and 1B (S9).
- the UE 1B when the UE 1B detects a trial failure, the UE 1B transmits a D2D permission reply indicating the trial failure to the eNB 2 (S15).
- UE1A detects a successful trial and transmits a D2D permission reply to that effect to eNB2 (S16).
- the eNB 2 that has received the D2D permission reply indicating the failed trial from the UE 1B instructs the UE 1A and 1B to perform cellular communication (S17, S18).
- indication initialize the set spreading code (S19, S20), and transfer to cellular communication.
- the continuity of communication can be ensured by switching to the cellular communication when the trial of the assigned spreading code fails. Moreover, if the UE 1A and 1B do not succeed in trying the assigned spreading code, the UE 1A and 1B are not charged, so that it is possible to prevent charging even though the D2D communication cannot be performed.
- FIG. 14 is a diagram for explaining the data transmission method according to the fourth modification of the first embodiment.
- UE1 that performs D2D communication applies a spreading code to each of a plurality of subcarriers to perform transmission.
- transmission data is subjected to S / P (serial / parallel) conversion in accordance with a plurality of subcarriers included in a transmission / reception frequency band of D2D communication, and transmission data for each subcarrier is encoded (spread) with a spreading code. Then send.
- FIG. 14A shows a case where the timing of data D is shifted between subcarriers
- FIG. 14B shows a case where the timing of data D is aligned between subcarriers.
- the communication speed of D2D communication can be improved by transmitting data in parallel with a plurality of subcarriers.
- the eNB 2 specifies the transmission / reception start timing (encoding start point) of D2D communication.
- ENB2 broadcasts information indicating an encoding start point based on the timing of cellular communication.
- the encoding start point means a timing at which encoding using one spreading code is started.
- each piece of data Dx shown in FIG. 14 corresponds to a period of a plurality of subframes, and therefore it is necessary to specify an encoding start point that is a start point (start timing) of the period.
- the eNB 2 indicates the encoding start point by broadcast information such as a system information block (SIB) or a master information block (MIB).
- SIB system information block
- MIB master information block
- the designation of the encoding start point for example, the following T STEP and T OFFSET are designated by including in broadcast information.
- SFN is a radio frame number
- subframe is a subframe number.
- UE1 which performs D2D communication specifies an encoding start point using said calculation formula based on T STEP and T OFFSET .
- transmission in D2D communication is either timing synchronized with downlink reception timing of cellular communication or timing synchronized with timing advanced (TA) correction within the cell.
- the synchronization here is synchronization in units of one subframe.
- UE1 which performs D2D communication adds the information (application information) which shows the application corresponding to the said data, and transmits, when transmitting data.
- FIG. 15 is a diagram illustrating a transmission data format according to Modification 6 of the first embodiment. As shown in FIG. 15, this format includes fields for application information, a data start flag, a data end flag, a sequence number, and a data length, in addition to fields for storing data.
- the application information may be an identifier indicating the application, the type of application, QoS required for the application, bearer identification information, or the like.
- the reception side by adding the application information to the transmission data in the D2D communication, the reception side can determine which application the received data belongs to. Then it can be deciphered. This makes it possible to start communication without following the connection procedure between UEs that perform D2D communication.
- Modification 7 of the first embodiment In Modification 7 of the first embodiment, UE1 (UE1C and 1D in FIG. 8) that performs D2D communication using an initial spreading code performs D2D based on the result of monitoring (that is, carrier sense) the interference wave signal. Send in communication.
- UE1 (UE1C and 1D in FIG. 8) that performs D2D communication using an initial spreading code performs D2D based on the result of monitoring (that is, carrier sense) the interference wave signal. Send in communication.
- FIG. 16 is a flowchart according to Modification 7 of the first embodiment.
- UE1 sets an initial spreading code (S1001), and performs carrier sense when performing D2D communication (S1002). Here, it is confirmed whether or not an interference wave signal is received in the transmission / reception frequency band of D2D communication (S1003). UE1 performs transmission after confirming that no interference wave signal is received (S1004).
- interference in non-guaranteed D2D communication can be suppressed by performing carrier sense.
- Modification 8 of the first embodiment In Modification 8 of the first embodiment, UE1 (UE1C and 1D in FIG. 8) that performs D2D communication using the initial spreading code detects the spread of the communication code of D2D communication in response to detecting the deterioration of the communication quality of D2D communication. Request allocation to eNB2.
- FIG. 17 is a sequence diagram according to Modification 8 of the first embodiment.
- UE1D performs D2D communication using an initial spreading code (S0)
- UE1D detects a deterioration in communication quality of D2D communication, it requests eNB2 to assign a spreading code. (S1).
- S1 initial spreading code
- the UE 1D detects deterioration in communication quality of D2D communication based on information (error level information) such as channel information, interference power, path loss, or (average) number of retransmissions.
- error level information such as channel information, interference power, path loss, or (average) number of retransmissions.
- the error level information can be calculated based on a reference signal whose transmission power and timing are known and transmitted / received in D2D communication.
- D2D communication can be continued by guaranteed D2D communication even if the communication quality in non-guaranteed D2D communication deteriorates.
- FIG. 18 is a partial modification of the sequence diagram of FIG.
- UE1D detects the deterioration of the communication quality of D2D communication, and requests
- UE1D requests cellular communication from eNB2 (S81), and eNB2 causes UE1C and 1D to start cellular communication (S82, S83).
- the second embodiment is different from the first embodiment in that an effective time is set for the spreading code assigned by the eNB 2.
- UE1 to which the spreading code is assigned from eNB2 requests eNB2 to reassign the spreading code in order to continue D2D communication.
- FIG. 19 is a sequence diagram according to the second embodiment. As illustrated in FIG. 19, the eNB 2 further transmits effective time information indicating the effective time of the assigned spreading code in the D2D permission (S3, S4). UE1A and 1B which received D2D permission set the spreading code shown by the code information contained in D2D permission (S5, S6).
- the UEs 1A and 1B set two types of timers (timer 1 and timer 2) based on the valid time information included in the D2D permission (S21, S22).
- the timer 1 is set to a time obtained by subtracting a predetermined time ( ⁇ t) from the effective time indicated by the effective time information. That is, the timer 1 is set to expire at a time point before the original valid time expires.
- the predetermined time ( ⁇ t) is preferably equal to or longer than the time required for the spreading code reassignment procedure.
- the timer 2 is set with an effective time indicated by the effective time information.
- UE1A and 1B perform D2D communication using the set spreading code (S7).
- UE1A and 1B When UE1A and 1B are continuing D2D communication when the timer 1 expires, UE1A and 1B start the spreading code reassignment procedure. UE1B transmits D2D request
- the eNB 2 that has received the D2D request calculates a new spreading code having orthogonality according to the D2D request (S2 ′).
- the eNB 2 assigns new spreading codes to the UEs 1A and 1B (S3 ', S4').
- the effective time is also set for the new spreading code.
- UE1A and 1B set a new spreading code (S5 ', S6'), and set two types of timers (timer 1, timer 2) (S21 ', S22'). UE1A and 1B continue D2D communication using the set spreading code (S7 ').
- the eNB 2 that has assigned new spreading codes to the UEs 1A and 1B transmits charging information to the charging server 4 (S8 ').
- the charging server 4 performs additional charging for the UEs 1A and 1B (S9 ').
- the UEs 1A and 1B initialize the set spreading code (S23, S24).
- the second embodiment it is possible to charge according to the D2D communication time by setting the effective time for the spreading code for D2D communication and charging each time the spreading code is reassigned. Therefore, the billing can be increased as the D2D communication time becomes longer.
- the eNB 2 assigns a spreading code different from the spreading code before the reassignment (previous code) in the reassignment of the spreading code.
- FIG. 20 is a sequence diagram according to Modification 1 of the second embodiment. As shown in FIG. 20, in the spreading code reassignment procedure, the operation when the new spreading code (selected code) calculated by eNB 2 (S2 ′) is different from the previous code is the same as that in the second embodiment described above. is there.
- the eNB 2 changes the code length of the spreading code (S71).
- the operation when the spreading code (selected code) is different from the previous code is the same as that in the second embodiment described above (S72).
- the code length is changed, if the spreading code (selected code) is the same as the previous code, the code length is changed again (S73).
- the eNB 2 instructs the UE 1A and 1B to switch to the cellular communication (S74, S75).
- the case where the code length of the spreading code cannot be changed is a case where all the spreading codes have been assigned, or a case where the required bandwidth (requested data rate) cannot be satisfied by increasing the code length. The latter case will be described in Modification 3 of the fifth embodiment.
- the secrecy of D2D communication can be ensured by assigning a spreading code different from the spreading code before reassignment (previous code).
- FIG. 21 is a sequence diagram according to the second modification of the second embodiment.
- UE1A and 1B set only one type of timer corresponding to the effective time of a spreading code (S21, S22).
- UE1A and 1B initialize a spreading code (S23, S24), and start the spreading code reassignment procedure.
- the UEs 1A and 1B perform non-guaranteed D2D communication using the initial spreading code or stop data communication from when the timer expires until the spreading code is reassigned.
- the spreading code is initialized without starting the spreading code reassignment procedure (S23 ', S24').
- the timer management in the UE 1A and 1B can be simplified.
- FIG. 22 is a sequence diagram according to the third modification of the second embodiment.
- the eNB 2 when UEs 1A and 1B end D2D communication, and the effective time of the spreading code has not expired at that time (end time of D2D communication), e1 (S61, S62). Further, the eNB 2 notifies the charging server 4 of the end of the D2D communication by the UEs 1A and 1B (S63). At that time, the eNB 2 measures the usage time of the assigned spreading code, and measures the actual usage time (specifically, from the assignment of the spreading code until the end of D2D communication is notified (S61, S62). Usage time) is notified to the billing server 4. The billing server 4 reduces the billing according to the unused portion (spread code valid time-actual use time).
- each of UE1A and 1B also notifies the measured usage time when notifying eNB2 of the end of D2D communication (S61, S62) To do.
- the eNB 2 notifies the charging server 4 of the actual usage time measured by each of the UEs 1A and 1B.
- the charging server 4 selects the longer usage time of the usage times measured by each of the UEs 1A and 1B as the actual usage time, and charges according to the unused portion (spread code effective time-actual usage time). Reduce the amount.
- the eNB 2 assigns one type of spreading code to the UEs 1A and 1B.
- the UE1A and 1B it is necessary to set it as the half duplex communication which switches transmission / reception by a time division.
- full-duplex D2D communication is realized by assigning two types of spreading codes.
- FIG. 23 is a diagram for explaining an operation outline according to the third embodiment.
- require full-duplex communication (full type)
- eNB2 allocates two types of spreading codes (for transmission, for reception) to UE1A and 1B.
- require half duplex communication (half type)
- eNB2 allocates one type of spreading code to UE1A and 1B.
- FIG. 24 is a sequence diagram according to the third embodiment.
- an example in which only one type of timer is used will be described.
- the UE 1B transmits a D2D request including information indicating which of full-duplex communication and half-duplex communication is requested to the eNB 2 (S1).
- the eNB 2 calculates two types of spreading codes (S2) and assigns the calculated spreading codes to the UEs 1A and 1B (S3, S4).
- UE1A and 1B set two types of spreading codes (S5, S6).
- UE1A and 1B set a timer (S21, S22), and perform full duplex D2D communication using the set spreading code (S7A, S7B).
- the eNB 2 calculates one type of spreading code (S2 ') and assigns the calculated spreading code to the UEs 1A and 1B (S3', S4 ').
- the UEs 1A and 1B set one type of spreading code (S5 ', S6').
- the UEs 1A and 1B set timers (S21 ', S22'), and perform half-duplex D2D communication using the set spreading codes (S7A ', S7B').
- the eNB 2 notifies the charging server 4 of the number of assigned spreading codes (S8, S8 '), and the charging server 4 charges according to the number of assigned spreading codes (S9, S9').
- the full-duplex communication charge (costA) is higher than the half-duplex communication charge (costB).
- full-duplex D2D communication can be realized. Further, charging can be made different between full-duplex D2D communication and half-duplex D2D communication.
- FIG. 25 is a diagram for explaining the outline of the operation according to the fourth embodiment.
- the eNB 2 increases the effective time of the spreading code every time the spreading code is reassigned (updated). Therefore, the update interval of the spread code is short at first, and gradually increases.
- FIG. 26 is a sequence diagram according to the fourth embodiment.
- spreading code assignment and D2D communication procedures (S1 to S7) using the spreading code are the same as in the modification of the embodiment described above.
- the eNB 2 sets an effective time corresponding to the elapsed time from when the UEs 1A and 1B start D2D communication for the spreading code.
- ENB2 notifies the billing server 4 of the effective time of the spreading code in response to assigning the spreading code to the UEs 1A and 1B (S8).
- the billing server 4 performs billing according to the notified valid time.
- the eNB 2 may notify the charging server 4 of the elapsed time of D2D communication instead of notifying the charging server 4 of the effective time of the spreading code.
- the accounting server 4 performs accounting according to the notified elapsed time.
- the processing load and signaling can be reduced by increasing the time interval (that is, the update interval) of the reassignment of spreading codes as the D2D communication time elapses.
- the eNB 2 controls the effective time of the spreading code based on an application (hereinafter, used application) used by the UEs 1A and 1B for D2D communication.
- FIG. 27 is a diagram for explaining an operation outline according to the first modification of the fourth embodiment.
- the eNB 2 optimizes the spread code update interval for the application to be used by varying the effective time of the spread code according to the application to be used. For example, the update interval is increased for application 1 (communication game, call, etc.) that communicates continuously, and the update interval for application 2 (competition game (shogi, go), chat, etc.) that communicates intermittently. To shorten.
- FIG. 28 is a sequence diagram according to Modification 1 of the fourth embodiment.
- UE1B transmits D2D request
- the application information includes an identifier indicating the application, the type of application, QoS required for the application, bearer identification information, and the like.
- ENB2 calculates a spreading code and calculates an effective time according to the application used (S2). And eNB2 notifies UE1A and 1B of the effective time according to a use application, when assigning the calculated spreading code to UE1A and 1B (S3, S4). Further, the eNB 2 notifies the billing server 4 of the use application (S8). The billing server 4 performs billing according to the notified use application (S9).
- the spreading code update interval can be optimized for the application to be used.
- FIG. 29 is a partial modification of the sequence diagram of FIG.
- the UE 1B transmits to the eNB 2 a D2D request including application information related to the application used (S1).
- the eNB 2 inquires of the application management server 5 whether the application in use is suitable for full-duplex communication or half-duplex communication (S31, S32).
- the application management server 5 is provided in the EPC 20, for example.
- the eNB 2 calculates two types of spreading codes (S2), and assigns the calculated spreading codes to the UEs 1A and 1B (S3, S4).
- UE1A and 1B set two types of spreading codes (S5, S6).
- UE1A and 1B set a timer (S21, S22), and perform full duplex D2D communication using the set spreading code (S7A, S7B).
- the eNB 2 calculates one type of spreading code (S2 ′) and assigns the calculated spreading code to the UEs 1A and 1B (S3 ′, S4). ').
- the UEs 1A and 1B set one type of spreading code (S5 ', S6').
- the UEs 1A and 1B set timers (S21 ', S22'), and perform half-duplex D2D communication using the set spreading codes (S7A ', S7B').
- the eNB 2 controls the effective time of the spreading code based on the charging contracts of the UE 1A and 1B.
- the billing contract may be a billing contract for both cellular communication and D2D communication, or may be a billing contract for only D2D communication.
- FIG. 30 is a diagram for explaining an operation outline according to the second modification of the fourth embodiment.
- the eNB 2 optimizes the spreading code update interval to the charging contract by varying the effective time of the spreading code according to the charging contract of the UE 1A and 1B. For example, the update interval is lengthened for fixed-rate billing, and the update interval is shortened for pay-per-use billing.
- FIG. 31 is a sequence diagram according to the second modification of the fourth embodiment.
- the eNB 2 that has received the D2D request inquires the charging server 4 about the charging contract settings of the UEs 1A and 1B (S41, S42). Then, the eNB 2 calculates the spreading code and calculates the valid time according to the charging contract (S2). When assigning the calculated spreading code to the UEs 1A and 1B (S3, S4), the eNB 2 notifies the UEs 1A and 1B of the valid time corresponding to the charging contract.
- the accounting server 4 performs accounting according to the accounting contracts of the UEs 1A and 1B (S9).
- the spreading code update interval can be optimized for a billing contract.
- the eNB 2 controls the effective time of the spreading code based on the moving speeds of the UEs 1A and 1B.
- the method itself for determining the moving speed is well known, description of the method is omitted.
- FIG. 32 is a diagram for explaining an operation outline according to the third modification of the fourth embodiment.
- the eNB 2 optimizes the spreading code update interval to the moving speed by changing the effective time of the spreading code according to the moving speed of the UEs 1A and 1B. For example, the update interval is shortened as the moving speed increases.
- eNB2 makes UE1A and 1B perform cellular communication instead of D2D communication, when UE1A and / or 1B move at a fixed speed or more (namely, high-speed movement).
- the eNB 2 preferably sets a time equal to or shorter than the time during which the UEs 1A and 1B stay in the coverage of the own cell as the effective time of the spreading code based on the moving speed. Therefore, since the valid time also depends on the cell size, the eNB 2 may adjust the valid time according to the size of the own cell. For example, in the case of a picocell, femtocell, etc., the effective time is shortened.
- the spreading code update interval can be optimized to the moving speed.
- eNB2 controls the code length of the spreading code allocated to UE1A and 1B based on the communication quality of D2D communication.
- FIG. 33 is a sequence diagram according to the fifth embodiment. As illustrated in FIG. 33, the UE 1B transmits a D2D request including error level information indicating communication quality in D2D communication to the eNB 2 (S1).
- ENB2 calculates a spreading code having an appropriate code length based on the error level information included in the D2D request (S2).
- the error level information is information such as channel information, interference power, path loss, or (average) number of retransmissions.
- the eNB 2 increases the code length of the spreading code in order to increase orthogonality when the path loss is small but the interference power is high (or there are many retransmissions).
- eNB2 allocates the calculated spreading code to UE1A and 1B (S3, S4).
- changing the code length of the spreading code assigned to UE1A and 1B may require changing the code length of the spreading code assigned to other UE1 (UE1E, UE1F).
- the eNB 2 assigns a new spreading code to the other UE 1 (UE 1E, UE 1F) (S3 ', S4').
- the communication quality of D2D communication can be improved by changing the code length of the spreading code.
- the code length of the spreading code is controlled based on the number of UEs 1 located in the cell of the eNB 2 (specifically, the number of UEs 1 performing D2D communication).
- FIG. 34 is a diagram for explaining the operation according to the first modification of the fifth embodiment.
- the eNB 2 increases the code length of the spreading code in order to increase orthogonality as the number of UEs 1 performing D2D communication in the own cell increases.
- the UEs 1A and 1B perform the reassignment of the spreading code in response to detecting the deterioration of the communication quality of the D2D communication even before the effective time of the spreading code expires.
- Request to eNB2. Based on the request, the eNB 2 assigns a spreading code having a code length longer than the spreading code to the UEs 1A and 1B.
- FIG. 35 is a sequence diagram according to Modification 2 of the fifth embodiment.
- the UE 1B detects a deterioration in communication quality in D2D communication before the effective time of the spreading code expires (that is, before the timer expires).
- the UE 1B detects deterioration in communication quality of D2D communication based on information (error level information) such as channel information, interference power, path loss, or (average) number of retransmissions.
- the error level information can be calculated based on a reference signal whose transmission power and timing are known and transmitted / received in D2D communication.
- the UE1B detects the deterioration of the communication quality of the D2D communication and requests the eNB2 to reallocate the spreading code when it is determined that the communication quality is improved by the allocation of the spreading code (S1 ′′). For example, when the reception power of the reference signal from the UE 1A is sufficient (that is, the path loss is small) but the interference power is high (or there are many retransmissions), the UE 1B performs communication quality by reassigning the spreading code. Will be improved. In this case, the UE 1B transmits to the eNB 2 a D2D request including error level information indicating communication quality in D2D communication.
- the eNB 2 calculates a spreading code having an appropriate code length based on the error level information included in the D2D request (S2 ′′). Here, the eNB 2 calculates a spreading code having a longer code length than the previously assigned spreading code. Then, the eNB 2 assigns the calculated spreading code to the UEs 1A and 1B (S3 ′′, S4 ′′).
- the UE 1B when the UE 1B detects the deterioration of the communication quality of the D2D communication and determines that the communication quality is not improved by the assignment of the spreading code, the UE 1B requests the eNB 2 to switch to the cellular communication (S51). For example, when the reception power of the reference signal from the UE 1A is low (that is, the path loss is large), the UE 1B determines that there is no possibility of improvement even by reassigning the spreading code. In this case, the eNB 2 instructs the UE 1A and 1B to switch to the cellular communication in response to the request to switch to the cellular communication (S52, S53).
- the communication quality of the D2D communication can be improved by changing the code length of the spreading code.
- the communication speed decreases as the code length of the spread code is increased. Therefore, when the communication speed becomes lower than the predetermined speed by increasing the code length of the spreading code, the eNB 2 or the UE 1 may perform control to switch from D2D communication to cellular communication.
- the predetermined speed may be a communication speed required for a use application.
- UE1 which performs D2D communication transmits the allocation request
- FIG. 36 is a sequence diagram when the number of UEs included in the D2D UE group increases.
- UE1C is added to the D2D UE group after D2D communication is started (S7) with the D2D UE group including UE1A and 1B.
- UE1C transmits a Discovery signal (S91, S92).
- the Discovery signal is a signal used for discovery processing of a nearby UE that should be a communication partner of D2D communication.
- UE1A and 1B receive the Discovery signal from UE1C, and transmit the response with respect to a Discovery signal to UE1C (S93, S94).
- UE1B transmits a D2D request for adding UE1C to the D2D UE group to eNB2 (S1 ').
- the eNB 2 calculates a spreading code (S2 ') and assigns the spreading code to the UEs 1A to 1C (S3', S4 ', S95). Thereby, D2D communication by UE1A thru
- FIG. 37 is a sequence diagram when the number of UEs included in the D2D UE group decreases.
- UE1A leaves the D2D UE group after D2D communication by UE1A to 1C is started.
- finishes D2D communication notifies that to UE1B, 1C, and eNB2 (S100, S101, S103).
- the UE 1A may notify the eNB 2 of the spreading code that has been used.
- the eNB 2 notifies the charging server 4 that the UE 1A ends the D2D communication (and the use time of the spreading code) (S104).
- the billing server 4 finishes billing for the UE 1A (and reduces the unused portion) (S105).
- D2D communication by UE1B and 1C is performed.
- spreading codes can be appropriately assigned according to the increase or decrease of the number of UEs included in the D2D UE group.
- the allocation of spreading codes is controlled by eNB2 in accordance with the increase or decrease in the number of UEs included in the D2D UE group. For example, when the number of UEs included in the D2D UE group increases, it is necessary to increase the allocation of spreading codes in order to perform full duplex communication between the UEs. In such a case, eNB2 increases the allocation of spreading codes to the D2D UE group by its own determination. When increasing the allocation of spreading codes, the charging server 4 may divide the usage fee of the spreading code among all UEs included in the D2D UE group, and divide the usage fee of the spreading code for each UE that uses the spreading code for transmission. May be.
- the eNB 2 rejects the allocation of the spreading code based on the charging contract of each UE included in the D2D UE group to which the UE 1 requesting the allocation of the spreading code belongs. Specifically, the eNB 2 rejects assignment of a spreading code to the D2D UE group when a UE with a charging contract (for example, pay-per-use charging) that does not allow D2D communication is included in the D2D UE group.
- the billing contract can be grasped by inquiring the billing server 4. Further, when refusing the allocation of the spreading code, the eNB 2 may notify the refusal target UE of the refusal reason (for example, pay-per-use).
- the eNB 2A stores the spreading code (code 1) assigned to the UEs 1A and 1B as its assigned spreading code (hereinafter, distributed code).
- the eNB 2A notifies its own distribution code (code 1) to each of the eNBs 2B and 2C adjacent to the eNB 2A.
- Each of the eNB 2B and 2C stores the distribution code (code 1) of the eNB 2A.
- eNB2D has memorize
- the eNB 2D notifies its own distribution code (code 1) to each of the eNBs 2B and 2C adjacent to the eNB 2D.
- Each of the eNB 2B and 2C stores the distribution code (code 1) of the eNB 2D.
- the eNB 2C assigns a spreading code (code 3) to the UEs 1E and 1F.
- the eNB 2C stores the spreading code (code 3) assigned to the UE 1E and 1F as its distribution code.
- the eNB 2C notifies its own distribution code (code 3) to each of the eNBs 2A, 2B, and 2D adjacent to the eNB 2C.
- Each of the eNBs 2A, 2B, and 2D stores the distribution code (code 3) of the eNB 2C.
- the eNB 2A reassigns the spreading code (code 2) to the UEs 1A and 1B.
- the eNB 2A updates its distribution code to the spreading code (code 2) assigned to the UEs 1A and 1B.
- the eNB 2A notifies the distribution code (code 1) whose allocation has been released and the newly assigned distribution code (code 2) to each of the eNBs 2B and 2C adjacent to the eNB 2A.
- Each of the eNB 2B and 2C deletes the distribution code (code1) released by the eNB 2A as the distribution code of the eNB 2A, and stores the distribution code (code 2) newly assigned by the eNB 2A.
- each eNB2 grasps
- the eNB 2 assigns the spreading code.
- a spreading code is assigned by a network node shared by a plurality of communication carriers (carriers).
- FIG. 41 is a diagram for explaining the operating environment according to the eighth embodiment.
- UE1A, eNB2A, and accounting server 4A belong to communication carrier A.
- UE1B, eNB2B, and accounting server 4B belong to communication carrier B.
- D2D communication is performed by the UEs 1A and 1B, it is difficult for the eNBs 2A and 2B to coordinately assign spreading codes to the UEs 1A and 1B.
- the assignment management server 6 shared by the communication carriers A and B assigns spreading codes to the UEs 1A and 1B.
- the UEs 1A and 1B notify the allocation management server 6 of the D2D request, and the allocation management server 6 notifies the allocation spreading code to the UEs 1A and 1B.
- the allocation management server 6 notifies the charging servers 4A and 4B of the spreading code allocation status.
- the allocation management server 6 also manages billing and provides billing information to the carriers A and B.
- D2D communication can be performed across communication carriers (carriers).
- the eNB 2 may assign a spreading code to the UE 1 based on an identifier associated with the UE 1.
- the identifier associated with UE1 is the IP address of UE1, an ID assigned by an application, and the like.
- the eNB 2 or the allocation management server 6 may allocate at least a part of such UE-specific values to the UE 1 as a spreading code.
- another spreading code associated one-to-one with at least a part of such UE-specific values may be assigned to UE1.
- a code division multiplexing scheme may be applied to the Discovery signal.
- the eNB 2 broadcasts information indicating a spreading code to be used for the discovery process.
- UE1 applies the spreading code indicated by the broadcast information to the Discovery signal, and transmits the Discovery signal.
- the frequency band of the LTE system is divided into a frequency band for cellular communication and a frequency band for D2D communication.
- a frequency band for cellular communication is divided into a frequency band for cellular communication and a frequency band for D2D communication.
- at least a part of the frequency band for cellular communication and the frequency band for D2D communication may overlap.
- the direct communication mode in D2D communication has been mainly described, but the local relay mode may be applied instead of the direct communication mode.
- the present invention is not limited to the LTE system, and the present invention may be applied to a system other than the LTE system.
- a mobile communication system a user terminal, and a base station that can facilitate the operation of D2D communication.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Databases & Information Systems (AREA)
- Mobile Radio Communication Systems (AREA)
- Meter Arrangements (AREA)
- Telephone Function (AREA)
- Telephonic Communication Services (AREA)
Abstract
Description
実施形態に係る移動通信システムは、データパスがネットワークを経由するセルラ通信と、データパスが前記ネットワークを経由しない直接的な端末間通信であるD2D通信と、をサポートする。前記セルラ通信には周波数分割多重方式が適用され、かつ、前記D2D通信には符号分割多重方式が適用される。前記ネットワークは、ユーザ端末からの要求に応じて、直交性を有する拡散符号を前記ユーザ端末に割り当てる。前記ユーザ端末は、前記ネットワークから割り当てられた前記拡散符号を使用して、前記D2D通信を行う。
以下、図面を参照して、3GPP規格に準拠して構成される移動通信システム(LTEシステム)にD2D通信を導入する場合の実施形態を説明する。なお、以下の図面の記載において、同一又は類似の部分には、同一又は類似の符号を付している。
図1は、第1実施形態に係るLTEシステムの構成図である。図1に示すように、LTEシステムは、複数のUE(User Equipment)1A乃至1Cと、E-UTRAN(Evolved-UMTS Terrestrial Radio Access Network)10と、EPC(Evolved Packet Core)20と、を含む。E-UTRAN10は無線アクセスネットワークに相当し、EPC20はコアネットワークに相当する。E-UTRAN10及びEPC20は、LTEシステムのネットワークを構成する。
次に、第1実施形態に係る動作について説明する。第1実施形態に係るLTEシステムは、直接的なUE間通信であるD2D通信をサポートする。ここでは、D2D通信を、LTEシステムの通常の通信(セルラ通信)と比較して説明する。
UE1A及びUE1Bのうち何れか一方のUEは、D2D通信において他方のUEを制御可能なUE(以下、「アンカーUE」)であってもよい。アンカーUEが存在する場合、他方のUE(通信相手UE)は、制御信号をeNB2と送受信せずにアンカーUEと送受信できる。
UE1A及びUE1Bは、同一セルに在圏する場合に限らず、異なるセルに在圏していてもよい。
第1実施形態の変更例3では、UE1A及び1Bは、割当拡散符号の試行を行った上で使用する。図13は、第1実施形態の変更例3に係るシーケンス図である。
第1実施形態の変更例4では、D2D通信にマルチキャリア符号分割多重方式を適用する。図14は、第1実施形態の変更例4に係るデータ送信方法を説明するための図である。
第1実施形態の変更例5では、eNB2は、D2D通信の送受信開始タイミング(符号化開始ポイント)を指定する。
第1実施形態の変更例6では、D2D通信を行うUE1は、データを送信する際に、当該データに対応するアプリケーションを示す情報(アプリケーション情報)をデータに付加して送信する。
第1実施形態の変更例7では、初期拡散符号を使用してD2D通信を行うUE1(図8のUE1C及び1D)は、干渉波信号をモニタリング(すなわち、キャリアセンス)した結果に基づいて、D2D通信における送信を行う。
第1実施形態の変更例8では、初期拡散符号を使用してD2D通信を行うUE1(図8のUE1C及び1D)は、D2D通信の通信品質の悪化を検知したことに応じて、拡散符号の割り当てをeNB2に要求する。
次に、第2実施形態について、第1実施形態との相違点を説明する。第2実施形態は、eNB2が割り当てる拡散符号に対して有効時間が設定される点で第1実施形態とは異なる。eNB2から拡散符号が割り当てられたUE1は、D2D通信を継続するために、拡散符号の再割り当てをeNB2に要求する。
第2実施形態の変更例1では、eNB2は、拡散符号の再割り当てにおいて、再割り当て前の拡散符号(前回符号)とは異なる拡散符号を割り当てる。
第2実施形態の変更例2では、タイマを1種類のみ使用する。図21は、第2実施形態の変更例2に係るシーケンス図である。
第2実施形態の変更例3では、UE1A及び1Bは、拡散符号の有効時間が満了する前にD2D通信を終了する場合に、D2D通信の終了をeNB2に通知する。図22は、第2実施形態の変更例3に係るシーケンス図である。
次に、第3実施形態について、上述した第1実施形態及び第2実施形態との相違点を説明する。上述した第1実施形態及び第2実施形態では、eNB2は、UE1A及び1Bに対して1種類の拡散符号を割り当てていた。この場合、UE1A及び1Bが双方向のD2D通信を行うためには、送受信を時分割で切り替える半二重通信とする必要がある。第3実施形態では、2種類の拡散符号を割り当てることにより、全二重のD2D通信を実現する。
次に、第4実施形態について、上述した第1実施形態乃至第3実施形態との相違点を説明する。上述した実施形態では、eNB2が割り当てる拡散符号の有効時間は一定であることを想定していた。第4実施形態では、eNB2は、UE1A及び1BがD2D通信を開始してからの経過時間に基づいて、拡散符号の有効時間を制御する。
第4実施形態の変更例1では、eNB2は、UE1A及び1BがD2D通信に使用するアプリケーション(以下、使用アプリケーション)に基づいて、拡散符号の有効時間を制御する。図27は、第4実施形態の変更例1に係る動作概要を説明するための図である。
第4実施形態の変更例2では、eNB2は、UE1A及び1Bの課金契約に基づいて、拡散符号の有効時間を制御する。課金契約とは、セルラ通信及びD2D通信の両方についての課金契約であってもよく、D2D通信のみについての課金契約であってもよい。図30は、第4実施形態の変更例2に係る動作概要を説明するための図である。
第4実施形態の変更例3では、eNB2は、UE1A及び1Bの移動速度に基づいて、拡散符号の有効時間を制御する。なお、移動速度を求める方法自体は周知であるため、当該方法についての説明は省略する。
次に、第5実施形態について、上述した第1実施形態乃至第4実施形態との相違点を説明する。第5実施形態では、eNB2は、D2D通信の通信品質に基づいて、UE1A及び1Bに割り当てる拡散符号の符号長を制御する。
第5実施形態の変更例1では、eNB2のセルに在圏するUE1の数(具体的には、D2D通信を行うUE1の数)に基づいて拡散符号の符号長を制御する。
第5実施形態の変更例2では、UE1A及び1Bは、拡散符号の有効時間が満了する前であっても、D2D通信の通信品質の悪化を検知したことに応じて、拡散符号の再割り当てをeNB2に要求する。eNB2は、当該要求に基づいて、当該拡散符号よりも符号長の長い拡散符号をUE1A及び1Bに割り当てる。
上述した第5実施形態及びその変形例において、拡散符号の符号長を長くするに従って通信速度(データレート)は低くなる。よって、拡散符号の符号長を長くすることにより通信速度が所定速度よりも低くなる場合には、eNB2又はUE1は、D2D通信からセルラ通信に切り替える制御を行ってもよい。ここで所定速度とは、使用アプリケーションに要求される通信速度であってもよい。
次に、第6実施形態について、上述した第1実施形態乃至第5実施形態との相違点を説明する。第6実施形態では、D2D通信を行うUE1は、UE1が属するD2D UE群に含まれるUE数の増減に基づいて、拡散符号の割り当て要求をeNB2に送信する。
第6実施形態の変更例1では、D2D UE群に含まれるUE数の増減に応じて、eNB2主導で拡散符号の割り当てを制御する。例えば、D2D UE群に含まれるUE数が増加すると、UE間で全二重通信を行うために拡散符号の割り当てを増やす必要がある。このような場合、eNB2は、自身の判断でD2D UE群に拡散符号の割り当てを増やす。拡散符号の割り当てを増やす場合、課金サーバ4は、D2D UE群に含まれる全UEで拡散符号の使用料金を分けてもよく、拡散符号を送信に使用する各UEで拡散符号の使用料金を分けてもよい。
第6実施形態の変更例2では、eNB2は、拡散符号の割り当てを要求するUE1が属するD2D UE群に含まれる各UEの課金契約に基づいて、拡散符号の割り当てを拒否する。具体的には、eNB2は、D2D通信が許容されない課金契約(例えば、従量課金)のUEがD2D UE群に含まれる場合に、当該D2D UE群に対する拡散符号の割り当てを拒否する。課金契約については、課金サーバ4に問い合せることにより把握できる。また、eNB2は、拡散符号の割り当てを拒否する場合に、拒否対象のUEに対して、拒否の理由(例えば、従量課金である旨)を通知してもよい。
次に、第7実施形態について、上述した第1実施形態乃至第6実施形態との相違点を説明する。第7実施形態では、拡散符号の割当状況を隣接セル間で共有する。
次に、第8実施形態について、上述した第1実施形態乃至第7実施形態との相違点を説明する。上述した実施形態では、拡散符号の割り当てをeNB2が行っていた。第8実施形態では、拡散符号の割り当てを、複数の通信事業者(キャリア)で共用されるネットワークノードが行う。
例えば、eNB2は、UE1に関連付けられた識別子に基づいて、拡散符号をUE1に割り当ててもよい。UE1に関連付けられた識別子とは、UE1のIPアドレス、アプリケーションで割り当てられたIDなどである。eNB2又は割当管理サーバ6は、このようなUE固有の値の少なくとも一部を拡散符号としてUE1に割り当ててもよい。或いは、このようなUE固有の値の少なくとも一部と1対1で対応付けられた別の拡散符号が、UE1に割り当てられてもよい。
Claims (27)
- データパスがネットワークを経由するセルラ通信と、データパスが前記ネットワークを経由しない直接的な端末間通信であるD2D通信と、をサポートする移動通信システムであって、
前記セルラ通信には周波数分割多重方式が適用され、かつ、前記D2D通信には符号分割多重方式が適用されており、
前記ネットワークは、ユーザ端末からの要求に応じて、直交性を有する拡散符号を前記ユーザ端末に割り当て、
前記ユーザ端末は、前記ネットワークから割り当てられた前記拡散符号を使用して、前記D2D通信を行うことを特徴とする移動通信システム。 - 前記ネットワークは、前記ユーザ端末による前記拡散符号の使用について課金を行うことを特徴とする請求項1に記載の移動通信システム。
- 前記拡散符号には、有効時間が設定されており、
前記拡散符号が割り当てられた前記ユーザ端末は、前記D2D通信を継続するために前記拡散符号の再割り当てを前記ネットワークに要求することを特徴とする請求項1に記載の移動通信システム。 - 前記ネットワークは、前記ユーザ端末による前記D2D通信の経過時間、前記ユーザ端末が前記D2D通信に使用するアプリケーション、前記ユーザ端末の課金契約、及び前記ユーザ端末の移動速度のうち、少なくとも1つに基づいて、前記有効時間を制御することを特徴とする請求項3に記載の移動通信システム。
- 前記ユーザ端末は、前記有効時間が満了する前であっても、前記D2D通信の通信品質の悪化を検知したことに応じて、前記拡散符号の再割り当てを前記ネットワークに要求することを特徴とする請求項3に記載の移動通信システム。
- 前記ユーザ端末は、前記有効時間が満了する前に前記D2D通信を終了する場合に、前記D2D通信の終了を前記ネットワークに通知することを特徴とする請求項3に記載の移動通信システム。
- 前記ネットワークは、前記拡散符号の再割り当てにおいて、再割り当て前の拡散符号とは異なる拡散符号を前記ユーザ端末に割り当てることを特徴とする請求項3に記載の移動通信システム。
- 前記ネットワークは、前記D2D通信における送信用の前記拡散符号と、前記D2D通信における受信用の前記拡散符号と、を前記ユーザ端末に割り当てることを特徴とする請求項1に記載の移動通信システム。
- 前記ネットワークは、前記ユーザ端末における前記D2D通信の通信品質、及び、前記ユーザ端末が属するセルにおいて前記D2D通信を行うユーザ端末数のうち、少なくとも1つに基づいて、前記ユーザ端末に割り当てる前記拡散符号の符号長を制御することを特徴とする請求項1に記載の移動通信システム。
- 前記ネットワークは、前記ユーザ端末に割り当てる前記拡散符号の符号長が所定長を超えると判断した場合に、前記D2D通信から前記セルラ通信に切り替えるよう前記ユーザ端末に指示することを特徴とする請求項9に記載の移動通信システム。
- 前記ユーザ端末は、直交性を有しない初期拡散符号を保持しており、
前記ユーザ端末は、前記ネットワークから前記拡散符号が割り当てられない場合でも、前記初期拡散符号を使用して前記D2D通信を行うことを特徴とする請求項1に記載の移動通信システム。 - 前記初期拡散符号を使用して前記D2D通信を行う前記ユーザ端末は、前記D2D通信の通信品質の悪化を検知したことに応じて、前記拡散符号の割り当てを前記ネットワークに要求することを特徴とする請求項11に記載の移動通信システム。
- 前記ネットワークは、前記拡散符号を割り当てることで前記通信品質が改善すると判断した場合に、前記拡散符号を前記ユーザ端末に割り当てることを特徴とする請求項12に記載の移動通信システム。
- 前記初期拡散符号を使用して前記D2D通信を行う前記ユーザ端末は、干渉波信号をモニタリングした結果に基づいて、前記D2D通信における送信を行うことを特徴とする請求項11に記載の移動通信システム。
- 前記ネットワークは、前記ユーザ端末と、前記ユーザ端末との前記D2D通信を行うべき他のユーザ端末と、からなるユーザ端末群に対して、前記拡散符号を割り当てることを特徴とする請求項1に記載の移動通信システム。
- 前記ユーザ端末は、前記ユーザ端末群に含まれるユーザ端末数の増減に基づいて、前記要求を前記ネットワークに送信することを特徴とする請求項15に記載の移動通信システム。
- 前記ネットワークは、前記ユーザ端末群に含まれるユーザ端末数に基づいて、前記ユーザ端末群に割り当てる拡散符号数を制御することを特徴とする請求項15に記載の移動通信システム。
- 前記ネットワークは、前記D2D通信が許容されない課金契約のユーザ端末が前記ユーザ端末群に含まれる場合に、前記ユーザ端末群に対する前記拡散符号の割り当てを拒否することを特徴とする請求項15に記載の移動通信システム。
- 前記ネットワークは、前記セルラ通信のタイミングを基準として前記D2D通信の送受信開始タイミングを前記ユーザ端末に通知することを特徴とする請求項1に記載の移動通信システム。
- 前記ネットワークは、複数のセルを含み、
前記複数のセルのそれぞれは、自セルにおける前記拡散符号の割当状況を隣接セルに通知することを特徴とする請求項1に記載の移動通信システム。 - 前記ネットワークは、前記ユーザ端末に関連付けられた識別子に基づいて、前記拡散符号を前記ユーザ端末に割り当てることを特徴とする請求項1に記載の移動通信システム。
- 前記拡散符号を使用して前記D2D通信を行う前記ユーザ端末は、前記拡散符号を複数のサブキャリアのそれぞれに適用して送信を行うことを特徴とする請求項1に記載の移動通信システム。
- 前記D2D通信を行う前記ユーザ端末は、データを送信する際に、前記データに対応するアプリケーションを示す情報を前記データに付加して送信することを特徴とする請求項1に記載の移動通信システム。
- 前記ネットワークは、前記D2D通信における通信相手とすべき近傍端末を発見するための発見処理に使用すべき拡散符号を示す情報を報知することを特徴とする請求項1に記載の移動通信システム。
- 前記ネットワークは、複数の通信事業者で共用され、かつ前記拡散符号の割り当てを行うサーバ装置を含むことを特徴とする請求項1に記載の移動通信システム。
- データパスがネットワークを経由するセルラ通信と、データパスが前記ネットワークを経由しない直接的な端末間通信であるD2D通信と、をサポートする移動通信システムにおいて用いられるユーザ端末であって、
前記ネットワークから割り当てられ、かつ直交性を有する拡散符号を使用して、前記D2D通信を行う制御部を有し、
前記セルラ通信には周波数分割多重方式が適用され、かつ、前記D2D通信には符号分割多重方式が適用されることを特徴とするユーザ端末。 - データパスがネットワークを経由するセルラ通信と、データパスが前記ネットワークを経由しない直接的な端末間通信であるD2D通信と、をサポートする移動通信システムにおいて用いられる基地局であって、
ユーザ端末からの要求に応じて、直交性を有する拡散符号を前記D2D通信のために前記ユーザ端末に割り当てる制御部を有し、
前記セルラ通信には周波数分割多重方式が適用され、かつ、前記D2D通信には符号分割多重方式が適用されることを特徴とする基地局。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP14754928.1A EP2961234A4 (en) | 2013-02-19 | 2014-02-18 | MOBILE COMMUNICATION SYSTEM, USER TERMINALS AND BASE STATIONS |
JP2015501456A JP5922298B2 (ja) | 2013-02-19 | 2014-02-18 | 移動通信システム、ユーザ端末及び基地局 |
US14/769,061 US9832799B2 (en) | 2013-02-19 | 2014-02-18 | Mobile communication system, user terminal, and base station |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201361766518P | 2013-02-19 | 2013-02-19 | |
US61/766,518 | 2013-02-19 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2014129453A1 true WO2014129453A1 (ja) | 2014-08-28 |
Family
ID=51391243
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2014/053743 WO2014129453A1 (ja) | 2013-02-19 | 2014-02-18 | 移動通信システム、ユーザ端末及び基地局 |
Country Status (4)
Country | Link |
---|---|
US (1) | US9832799B2 (ja) |
EP (1) | EP2961234A4 (ja) |
JP (1) | JP5922298B2 (ja) |
WO (1) | WO2014129453A1 (ja) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107211489A (zh) * | 2015-01-13 | 2017-09-26 | 富士通株式会社 | 无线通信***、控制站和终端 |
JP2017532879A (ja) * | 2014-09-19 | 2017-11-02 | 華為技術有限公司Huawei Technologies Co.,Ltd. | 発見信号とセルラー信号とのための共存装置、方法、およびシステム |
JP2018082403A (ja) * | 2016-11-18 | 2018-05-24 | パナソニックIpマネジメント株式会社 | 無線中継装置、プログラム、無線通信システム及び無線通信方法 |
JP2018527860A (ja) * | 2015-09-15 | 2018-09-20 | 華為技術有限公司Huawei Technologies Co.,Ltd. | アプリケーション層パラメータ情報を送信する方法、アプリケーション層パラメータ情報を受信する方法、及び装置 |
Families Citing this family (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9609144B2 (en) * | 2013-05-03 | 2017-03-28 | Qualcomm Incorporated | Method for policy control and charging for D2D services |
US10897786B2 (en) | 2014-02-28 | 2021-01-19 | Sony Corporation | Telecommunications apparatus and methods |
WO2015141734A1 (ja) * | 2014-03-18 | 2015-09-24 | シャープ株式会社 | 通信制御方法、端末装置、サーバ装置および通信システム |
EP3243358B1 (en) * | 2015-01-08 | 2020-06-24 | Telefonaktiebolaget LM Ericsson (publ) | A network node, a wireless device and methods therein for selecting a communication mode in a wireless communications network |
CN105897478B (zh) * | 2016-04-12 | 2019-02-05 | 腾讯科技(深圳)有限公司 | 一种链路决策的方法及决策设备 |
US10531313B2 (en) * | 2016-07-15 | 2020-01-07 | Huawei Technologies Co., Ltd. | Method and system for generating and processing user-equipment-to-user-equipment probe signal |
WO2019173961A1 (en) * | 2018-03-13 | 2019-09-19 | Qualcomm Incorporated | Sequence selection techniques for non-orthogonal multiple access (noma) |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2002159050A (ja) * | 2000-11-16 | 2002-05-31 | Yamatake Corp | 無線装置 |
JP2008193666A (ja) * | 2007-01-10 | 2008-08-21 | Matsushita Electric Ind Co Ltd | 基地局装置及び無線通信装置 |
JP2008258817A (ja) * | 2007-04-03 | 2008-10-23 | Mitsubishi Electric Corp | 通信装置 |
WO2011116017A1 (en) * | 2010-03-17 | 2011-09-22 | Qualcomm Incorporated | Method and apparatus for establishing and maintaining peer-to-peer (p2p) communication on unlicensed spectrum |
JP2012119827A (ja) * | 2010-11-30 | 2012-06-21 | Ntt Docomo Inc | 移動通信方法、無線基地局及び移動局 |
JP2012213206A (ja) * | 2006-02-03 | 2012-11-01 | Panasonic Corp | 移動通信システムにおけるアップリンクリソースの割当て |
Family Cites Families (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3437524B2 (ja) * | 2000-03-30 | 2003-08-18 | 松下電器産業株式会社 | 無線通信装置および無線通信方法 |
US8264965B2 (en) * | 2008-03-21 | 2012-09-11 | Alcatel Lucent | In-band DPI application awareness propagation enhancements |
US9072060B2 (en) * | 2008-06-03 | 2015-06-30 | Nokia Technologies Oy | Method, apparatus and computer program for power control to mitigate interference |
US9320067B2 (en) | 2008-11-24 | 2016-04-19 | Qualcomm Incorporated | Configuration of user equipment for peer-to-peer communication |
US8885507B2 (en) * | 2009-12-11 | 2014-11-11 | Nokia Corporation | Method, apparatus and computer program product for allocating resources in wireless communication network |
US9276708B2 (en) | 2009-12-21 | 2016-03-01 | Nokia Technologies Oy | Secondary system usage in multicarrier networks |
US9198210B2 (en) * | 2010-04-20 | 2015-11-24 | Nokia Solutions And Networks Oy | D2D communications considering different network operators |
JP2012085113A (ja) * | 2010-10-12 | 2012-04-26 | Panasonic Corp | 通信装置、通信システム、および通信方法 |
KR20130053650A (ko) * | 2011-11-15 | 2013-05-24 | 삼성전자주식회사 | 디바이스간 직접 통신 서비스 시스템에서 데이터 송신 방법 및 장치 |
US9036546B2 (en) * | 2012-01-04 | 2015-05-19 | Futurewei Technologies, Inc. | System and method for device discovery for device-to-device communication in a cellular network |
US9002281B2 (en) * | 2012-04-30 | 2015-04-07 | Intel Corporation | Apparatus and method to enable device-to-device (D2D) communication in cellular networks |
US9591679B2 (en) * | 2012-09-17 | 2017-03-07 | Blackberry Limited | Initiation of inter-device communication in wireless communication systems |
US9143291B2 (en) * | 2012-12-27 | 2015-09-22 | Google Technology Holdings LLC | Method and apparatus for device-to-device communication |
-
2014
- 2014-02-18 JP JP2015501456A patent/JP5922298B2/ja active Active
- 2014-02-18 US US14/769,061 patent/US9832799B2/en active Active
- 2014-02-18 EP EP14754928.1A patent/EP2961234A4/en not_active Withdrawn
- 2014-02-18 WO PCT/JP2014/053743 patent/WO2014129453A1/ja active Application Filing
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2002159050A (ja) * | 2000-11-16 | 2002-05-31 | Yamatake Corp | 無線装置 |
JP2012213206A (ja) * | 2006-02-03 | 2012-11-01 | Panasonic Corp | 移動通信システムにおけるアップリンクリソースの割当て |
JP2008193666A (ja) * | 2007-01-10 | 2008-08-21 | Matsushita Electric Ind Co Ltd | 基地局装置及び無線通信装置 |
JP2008258817A (ja) * | 2007-04-03 | 2008-10-23 | Mitsubishi Electric Corp | 通信装置 |
WO2011116017A1 (en) * | 2010-03-17 | 2011-09-22 | Qualcomm Incorporated | Method and apparatus for establishing and maintaining peer-to-peer (p2p) communication on unlicensed spectrum |
JP2012119827A (ja) * | 2010-11-30 | 2012-06-21 | Ntt Docomo Inc | 移動通信方法、無線基地局及び移動局 |
Non-Patent Citations (2)
Title |
---|
"TR 22.803 V2.0.0", 3GPP TECHNICAL REPORT, November 2012 (2012-11-01) |
See also references of EP2961234A4 |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2017532879A (ja) * | 2014-09-19 | 2017-11-02 | 華為技術有限公司Huawei Technologies Co.,Ltd. | 発見信号とセルラー信号とのための共存装置、方法、およびシステム |
CN107211489A (zh) * | 2015-01-13 | 2017-09-26 | 富士通株式会社 | 无线通信***、控制站和终端 |
JP2018527860A (ja) * | 2015-09-15 | 2018-09-20 | 華為技術有限公司Huawei Technologies Co.,Ltd. | アプリケーション層パラメータ情報を送信する方法、アプリケーション層パラメータ情報を受信する方法、及び装置 |
JP2018082403A (ja) * | 2016-11-18 | 2018-05-24 | パナソニックIpマネジメント株式会社 | 無線中継装置、プログラム、無線通信システム及び無線通信方法 |
WO2018092412A1 (ja) * | 2016-11-18 | 2018-05-24 | パナソニックIpマネジメント株式会社 | 無線通信システム、無線中継装置及び無線通信方法 |
US11044769B2 (en) | 2016-11-18 | 2021-06-22 | Panasonic Intellectual Property Management Co., Ltd. | Wireless communication system, wireless relay device and wireless communication method |
Also Published As
Publication number | Publication date |
---|---|
EP2961234A4 (en) | 2016-10-12 |
JPWO2014129453A1 (ja) | 2017-02-02 |
EP2961234A1 (en) | 2015-12-30 |
US9832799B2 (en) | 2017-11-28 |
US20150382392A1 (en) | 2015-12-31 |
JP5922298B2 (ja) | 2016-05-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP5922298B2 (ja) | 移動通信システム、ユーザ端末及び基地局 | |
JP6306753B2 (ja) | 制御方法、ユーザ端末、プロセッサ、及び基地局 | |
JP6687452B2 (ja) | 移動通信システム、ユーザ端末、プロセッサ、記憶媒体及びプログラム | |
JP6062088B2 (ja) | ユーザ端末、及びプロセッサ | |
JP6282705B2 (ja) | ユーザ端末、プロセッサ及び通信制御方法 | |
WO2016072469A1 (ja) | 基地局及びユーザ端末 | |
JP6132840B2 (ja) | 通信制御方法、ユーザ端末、プロセッサ、及び記憶媒体 | |
WO2014129465A1 (ja) | 通信制御方法、ユーザ端末及び基地局 | |
WO2014157398A1 (ja) | 通信制御方法及びプロセッサ | |
JP5905575B2 (ja) | 通信制御方法及び基地局 | |
WO2014192629A1 (ja) | ユーザ端末、基地局及びプロセッサ | |
WO2014181829A1 (ja) | ユーザ端末、セルラ基地局、及びプロセッサ | |
JP6140013B2 (ja) | 移動通信システム、ユーザ端末、ネットワーク装置及びプロセッサ | |
WO2016163474A1 (ja) | ユーザ端末 | |
WO2016021701A1 (ja) | 基地局及びユーザ端末 | |
JP6212239B2 (ja) | ユーザ端末及びプロセッサ | |
JP6144442B1 (ja) | 通信制御方法及び基地局 | |
WO2014181831A1 (ja) | ユーザ端末及びプロセッサ |
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: 14754928 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2015501456 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14769061 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2014754928 Country of ref document: EP |