WO2012114527A1 - Procédé pour attribuer une adresse ip à un dispositif relais - Google Patents

Procédé pour attribuer une adresse ip à un dispositif relais Download PDF

Info

Publication number
WO2012114527A1
WO2012114527A1 PCT/JP2011/054401 JP2011054401W WO2012114527A1 WO 2012114527 A1 WO2012114527 A1 WO 2012114527A1 JP 2011054401 W JP2011054401 W JP 2011054401W WO 2012114527 A1 WO2012114527 A1 WO 2012114527A1
Authority
WO
WIPO (PCT)
Prior art keywords
relay device
base station
address
relay node
relay
Prior art date
Application number
PCT/JP2011/054401
Other languages
English (en)
Japanese (ja)
Inventor
正則 橋本
Original Assignee
富士通株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 富士通株式会社 filed Critical 富士通株式会社
Priority to PCT/JP2011/054401 priority Critical patent/WO2012114527A1/fr
Publication of WO2012114527A1 publication Critical patent/WO2012114527A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5061—Pools of addresses
    • 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
    • H04W84/047—Public Land Mobile systems, e.g. cellular systems using dedicated repeater stations

Definitions

  • the present invention relates to a method for assigning an IP address to a relay device.
  • LTE Long Term Evolution
  • eNodeB eNodeB
  • UE User Equipment
  • a relay node Unlike a relay device called a repeater that amplifies radio waves received from a base station and expands a service area, a relay node once terminates various signals including control signals from the base station and wireless terminals, The signal is processed and sent to a wireless terminal or base station. In this way, the relay node operates more intelligently than the repeater.
  • the cell that is the communicable range between the relay node and the wireless terminal is served by the original base station (called “donor base station (Donor eNodeB)”) that the relay node relays (in the communicable range). It is greatly different from a repeater in that it is treated as a cell different from a cell (at least it appears as a different cell from a wireless terminal).
  • a mechanism for assigning an IP address to a relay node located under a relay node connected to a donor base station has not been sufficiently studied.
  • One aspect of the present invention provides a technique capable of efficiently assigning an IP address to a relay device positioned below another relay device in an environment where a plurality of relay devices are connected in multiple stages to a base station. With the goal.
  • One aspect of the present invention relates to a relay device that relays a radio interface between a base station and a radio terminal for providing a cellular phone service, and that can terminate control signals from the base station and the radio terminal.
  • An IP address assignment method The base station assigns a plurality of IP addresses to a first relay device located under the base station itself, The first relay device includes an IP address including assigning at least one of a plurality of IP addresses assigned from the base station to a second relay device located under the first relay device This is an allocation method.
  • an IP address can be efficiently allocated to a relay apparatus positioned below another relay apparatus.
  • FIG. 1 shows an example of an LTE network system, which is an example of a communication system according to an embodiment of the present invention.
  • FIG. 2 shows an operation example when the relay node attaches to the LTE network (relay node) in the LTE network as shown in FIG.
  • FIG. 3 shows a protocol stack related to the attachment of the lower relay node shown in FIG.
  • FIG. 4 is an explanatory diagram illustrating an example of assignment of IP address groups when another relay node is attached to a donor base station having a relay node under control.
  • FIG. 5 is a diagram for explaining an example of an IP address assignment operation when another relay node is attached to one of the relay nodes shown in FIG.
  • FIG. 6 shows an example of assignment of IPv4 IP address groups.
  • FIG. 1 shows an example of an LTE network system, which is an example of a communication system according to an embodiment of the present invention.
  • FIG. 2 shows an operation example when the relay node attaches to the LTE network (relay node) in the
  • FIG. 7A is a diagram for explaining interface settings between the donor base station and the MME and between the donor base station and the relay node, and is a diagram for explaining setting of the S1 and S11 interfaces between the relay node and the MME.
  • FIG. 7B is a diagram for describing setting of the S1 and S11 interfaces between the lower relay node and the MME when another relay node is attached to the lower level of the relay node.
  • FIG. 8 is a diagram illustrating an operation example when a radio terminal (UE) attaches as a subordinate of a relay node in the LTE network illustrated in FIG.
  • FIG. 9 shows a protocol stack for UE attachment.
  • FIG. 10 is a diagram illustrating a configuration example of a donor base station.
  • FIG. 11 shows functional blocks realized by executing firmware by the DSP of the baseband processing unit shown in FIG.
  • FIG. 12 shows functional blocks realized by program execution by the CPU of the control unit shown in FIG.
  • FIG. 13 is a flowchart illustrating a processing example of the reception unit in the donor base station.
  • FIG. 14 is a flowchart illustrating a processing example of the transmission unit in the donor base station.
  • FIG. 15 is a flowchart illustrating a processing example of the analysis unit in the donor base station.
  • FIG. 16 is a flowchart illustrating a processing example of the S11AP protocol processing unit included in each protocol processing unit in the donor base station.
  • FIG. 17 is a flowchart illustrating a processing example of the IP address assignment control unit in the donor base station.
  • FIG. 18 is a flowchart illustrating a processing example of the S1AP protocol processing unit included in each protocol processing unit in the donor base station.
  • FIG. 19 is a flowchart illustrating a processing example by the RRC protocol processing unit in each protocol processing unit corresponding to the processing illustrated in FIG.
  • FIG. 20 is a flowchart illustrating a processing example of DeNB-Relay connection management by the DeNB-Relay connection management control unit (DR control unit).
  • FIG. 21 is a flowchart illustrating a processing example of DeNB-UE connection management by the DeNB-UE connection management control unit (DU control unit).
  • FIG. 22 is a flowchart illustrating a processing example of donor base station traffic management by the traffic management unit.
  • FIG. 23 is a flowchart illustrating a processing example of donor base station traffic transfer by the traffic transfer unit.
  • FIG. 24 is a diagram illustrating a configuration example of a relay node.
  • FIG. 25 shows functional blocks realized by executing firmware by the DSP of the baseband processing unit shown in FIG.
  • FIG. 26 shows functional blocks realized by program execution by the CPU of the control unit shown in FIG.
  • FIG. 27 is a flowchart illustrating a processing example of the IP address assignment control unit corresponding to the S11 processing unit of the relay node 5.
  • FIG. 28 shows an example of IP address reception processing by the RRC processing unit.
  • FIG. 29 is a flowchart illustrating a processing example of the S1AP protocol processing unit included in each protocol processing unit of the relay node when another relay node is attached to the relay node.
  • FIG. 30 is a flowchart showing a processing example of the self-subordinate relay connection management control unit (lower control unit).
  • FIG. 31 is a flowchart illustrating a processing example of Relay-UE connection management by the Relay-UE connection management control unit (RU control unit).
  • FIG. 32 is a flowchart illustrating a processing example of the Relay-DeNB connection management control unit.
  • FIG. 33 is a flowchart showing an example of processing of the self-upper relay connection management control unit (upper control unit).
  • FIG. 34 is a flowchart illustrating an example of processing performed by the traffic management unit.
  • FIG. 35 is a flowchart illustrating an example of processing performed by the traffic transfer unit.
  • FIG. 36 is a flowchart illustrating a processing example of the MME 6.
  • FIG. 1 shows an example of an LTE network system, which is an example of a communication system according to an embodiment of the present invention.
  • the LTE network is an eUTRAN (Evolved Universal Terrestrial Radio Network, hereinafter referred to as “wireless network 1”) that is a radio network that accommodates radio terminals (UEs) and an EPC (Evolved Packet Core: LTE-Core, hereinafter) that is a core network (CN). "Core network 2").
  • the wireless network 1 has a plurality of base stations 3 called “eNodeB (eNB)” (two base stations 3 are illustrated in FIG. 1).
  • eNodeB eNodeB
  • a radio terminal (UE) 4 belonging to (located in) a communication range (cell) of each base station 3 is connected to the base station 3 via a radio link (for example, the base station 3A and the radio terminal in FIG. 1). See 4A).
  • the plurality of base stations 3 can include a donor base station (DeNB) 3 that accommodates a relay device called a relay node (RN) under the control of the base station 3 (see the donor base station 3B in FIG. 1).
  • the donor base station 3B can be directly connected to the wireless terminal 4 via a wireless link in the same manner as the normal base station 3 (3A) (see the wireless terminal 4D in FIG. 1).
  • the donor base station 3B has one or more relay nodes 5 under its control, and can be connected to the relay nodes 5 through a radio link.
  • the relay node 5 has a cell independent from the cell of the donor base station 3B, and can have one or more wireless terminals located in the cell of the relay node 5 under the control of the relay node 5.
  • the relay node 5 can have one or more other relay nodes under its control. Therefore, a multi-hop structure in which three or more relay nodes 5 are cascade-connected to the donor base station 3B can be applied. In other words, the plurality of relay nodes 5 connected in cascade can perform multi-stage relaying (multi-hop relay) between the radio terminal 4 and the donor base station 3B.
  • the relay node 5 is connected to a higher level device (donor base station, higher level relay node) and a lower level device (lower level relay node, wireless terminal) via a radio interface, and relays communication between the higher level device and the lower level device. can do.
  • a relay node 5B is connected to the donor base station 3B, a relay node 5A is connected to the relay node 5B, and a plurality of relay nodes are cascaded to the donor base station 3B.
  • a connected example is shown.
  • the relay node 5 can be connected in multiple stages to the donor base station 3B.
  • the donor base station 3B has the subordinate radio terminal 4 (4D)
  • the relay node 5B has the subordinate radio terminal 4 (4C)
  • the relay node 5A has the subordinate radio terminal 4 (4B). Is shown.
  • each of the donor base station 3B and the relay node 5 can have two or more relay nodes 5 at the same time. Therefore, although not shown, it is possible to form a topology in which a plurality of relay nodes 5 are connected in a tree shape or a tournament shape with the donor base station 3B as a vertex.
  • the relay node 5 can terminate the RRC (Radio Resource Control) protocol and can execute control independent of the donor base station 3B. For example, the relay node 5 can receive a signal to be communicated between the donor base station 3B and the subordinate radio terminal 4, process the received signal as necessary, and send it to the transmitting side. .
  • RRC Radio Resource Control
  • the relay node 5 is seen by the base station 3 when viewed from the wireless terminal 4. On the other hand, the relay node 5 executes an attach process that differs depending on whether the lower-level device is the relay node 5 or the wireless terminal 4.
  • the donor base station 3B can recognize the existence of the relay node 5A, and can also recognize whether the subordinate relay node 5 has another relay node 5 or not.
  • the relay node 5 Since the relay node 5 is installed at the outer edge of the cell of the donor base station 3B (position where the radio wave condition is not good) or outside the cell of the donor base station 3B, the radio terminal 4 is good with the relay node 5A.
  • the relay node 5 relays a signal from the wireless terminal 4 to the donor base station 3B, and the wireless terminal 4 can perform communication using the LTE network.
  • the service area of the donor base station 3B can be expanded, while the wireless quality between the wireless terminal 4 and the donor base station 3B can be improved.
  • Each base station 3 including the donor base station 3B is connected to the core network 2 via an interface called “S1 interface”.
  • the base stations 3 are connected to each other via an interface called “X2 interface”.
  • the core network 2 includes a mobility management entity (MME) 6, a serving gateway (Serving Gateway: SGW) 7, and a packet data network gateway (Packet data network: Gateway) (PGW) 8.
  • MME mobility management entity
  • SGW Serving Gateway
  • PGW packet data network gateway
  • the MME 6 is a control device that handles a network control C-plane.
  • the MME 6 is connected to the base station 3 via an S1-MME interface that is an S1 interface of the C plane.
  • the MME 6 is connected to a device called a home subscriber server (HSS) 9 that handles service control and subscriber data via a C plane interface (S6a).
  • HSS home subscriber server
  • the SGW 7 is a gateway device that handles a U plane (User plane) that is packet data of user data.
  • the SGW 7 is connected to the base station 3 via the S1-U interface that is the S1 interface of the U plane.
  • the SGW 7 is connected to the MME 6 via a C-plane interface called “S11 interface”.
  • the PGW 8 is a gateway device for connecting to an external network such as the Internet.
  • the PGW 8 is connected to the SGW 7 via a C-plane and U-plane interface (S5 GTP or the like).
  • the relay node 5 and the wireless terminal 4 can perform IP communication using an IP address lent (assigned) from the network side.
  • the relay node 5 is connected to the LTE network (the donor base station 3B or the upper relay node 5) through an attach process.
  • the first attach process First Attach
  • an IP address group is assigned to the relay node 5.
  • FIG. 2 shows an operation example when the relay node 5A attaches to the LTE network (relay node 5B) in the LTE network as shown in FIG.
  • the relay node 5A (Relay 1) includes a base station function 51 in which the relay node 5A behaves (functions) as a base station with respect to a wireless terminal (hereinafter also referred to as “UE”) 4;
  • the node 5A uses a UE function 52 that behaves (functions) as a UE with respect to the host device.
  • the relay node 5B located above the relay node 5A has a base station function 51 that functions as a base station for the subordinate relay node 5 (5A) and an S / PGW that functions as an S / PGW for the relay node 5A.
  • the PGW function 53 is used.
  • the donor base station 3B uses a proxy base station function 31 (P. eNB) and a proxy S / PGW function 32 (PS / PGW) that manage proxy transfer processing between the lower apparatus and the upper apparatus.
  • P. eNB proxy base station function
  • PS / PGW proxy S / PGW function 32
  • the sequence shown in FIG. 2 starts when the relay node 5A searches for and captures the cell of the relay node 5B, receives notification information from the relay node 5B, detects the relay node 5B, and starts the attach procedure. Is done. Further, at the start of the sequence of FIG. 2, the S1 interface (S1AP link) and the S11 interface (S11AP link) are already established among the relay node 5B, the donor base station 3B, and the MME 6.
  • the UE function 52 of the relay node 5A sets up an RRC connection with the base station function 51 of the relay node 5B (RRC Connection Setup) (S1).
  • the UE function 52 of the relay node 5A places the NAS (Non Access Stratum) layer attach request message “NAS: Attach A Request” on the “RRC:“ Initial Direct Transfer ”message that is an RRC outgoing message, and relay node 5B. (S2).
  • NAS Non Access Stratum
  • IMSI International Mobile Subscriber Identity
  • the base station function 51 of the relay node 5B uses the S1 interface set between the relay node 5B and the donor base station 3B to transmit “RRC: Attach Request” received from the relay node 5A to S1AP (S1
  • S1AP message “S1AP: Initial UE Message” based on “Application Protocol” is transferred to the donor base station 3 (S3).
  • the S1AP message “S1AP:“ Initial ”UE“ Message ”including“ RRC: “Attach” Request ”from the relay node 5B is received by the proxy base station function 31 of the donor base station 3.
  • the proxy base station function 31 transfers the S1AP message “S1AP:“ Initial ”UE Message” including “RRC:“ Attach ”Request” to the MME 6 using the proxy function (S4).
  • the MME 6 recognizes that it is First Attach when the IMSI is included in the S1AP message from the donor base station 3B, and starts the authentication procedure. At this time, the MME 6 inquires and acquires the contract information (subscriber data) of the terminal (terminal corresponding to IMSI) related to First Attach with respect to the HSS 9 (S5). Subsequently, the MME 6 performs an authentication process with the UE function 52 of the relay node 5A using the contract information (Authentication: S6).
  • ciphering / integrity is applied to the RRC between the relay node 5A and the relay node 5B and the NAS between the relay node 5A and the MME 6 according to the security start instruction. It is set (S7, S8). Also, ciphering is set in the U plane between the relay node 5A and the relay node 5B and between the relay node 5B and the donor base station 3B (S9). In addition, the location registration of the relay node 5A is performed (S10).
  • the MME 6 recognizes that the terminal related to First Attach is a relay node based on the contract information obtained from the HSS 9, and performs a default bearer establishment procedure for the S / PGW function 53 of the relay node 5B. To decide. At this time, the MME 6 transmits an S11AP message “S1AP: Create Session Request” to the donor base station 3B (S12).
  • the proxy S / PGW 32 of the donor base station 3B transfers “S1AP:“ Create Session ”Request” to the S / PGW function 53 of the relay node 5B by the proxy function (S13).
  • the S / PGW function 53 of the relay node 5B receives “S1AP:“ Create Session Request ”, and recognizes that the terminal related to First“ Attach ”is a relay node (RN) at this time. In this case, the S / PGW function 53 determines an IP address group to be assigned to the terminal related to First Attach by selecting from an IP address list (described later) of the relay node 5B (S14).
  • the S / PGW function 32 performs a response process of transmitting an S11AP message “S11AP:“ Create Session Response ”” including an IP address group to be allocated (S15). “S11AP:“ Create Session Response ”” is relayed by the proxy S / PGW 32 of the donor base station 3B and sent to the MME 6 (S16).
  • MME6 receives “S11AP: Create Session Response”. As a result, the MME 6 determines that the relay node 5B is ready to accept the relay node 5A, and the NAS message “NAS: ttaAttachceptAccept” indicating attachment permission is sent to the S1AP message “S1AP: Initial Context Setup Request” (initial context setting request) (S18). In the “S1AP: Initial Context Setup Request” message, an IP address group (IP address group for RN) assigned to the relay node 5A is placed (S17).
  • IP address group IP address group for RN
  • the base station function 51 constructs the context of the relay node 5A based on “S1AP:“ Initial Context ”Setup“ Request ”including“ NAS: “Attach” Accept ”. Further, the RRC message “RRC: RRC Connection Reconfiguration” carrying the received “NAS: Attach Accept” is transmitted to the relay node 5A (S20).
  • the UE function 52 of the relay node 5A that receives “RRC:“ RRC Connection Reconfiguration ”including“ NAS: “Attach” Accept ”obtains an IP address group included as a parameter in“ RRC: “RRC Connection Reconfiguration” (S21). Subsequently, the UE function 52 sends a response message “RRC: RRC Connection Reconfiguration ⁇ Complete” to the relay node 5B (S22). Since the NAS message cannot be put on this “RRC: RRC Connection Reconfiguration Complete”, the UE function 52 then sends the RRC message “RRC: UL Information Transfer” with the NAS message “NAS: Attach Complete” sent ( S23).
  • the base station function 51 of the relay node 5B transmits the S1AP message “S1AP:“ Initial Context Setup Response ”in response to the reception of“ RRC: “RRC” Connection “Reconfiguration” Complete ”(S24).
  • This “S1AP: Initial Context Setup Response” is proxy-transferred by the proxy base station function 31 of the donor base station 3B and reaches the MME 6 (S25). Thereby, the completion of context construction of the relay node 5A is notified to the MME 6.
  • the base station function 51 of the relay node 5B transmits the NAS message “NAS: Attach Complete” from the relay node 5A on the S1AP message “S1AP: Uplink NAS Transport” (S26).
  • S1AP:“ Uplink ”NAS“ Transport ”including this“ NAS: “Attach” Complete ” is proxy-relayed by the proxy base station function 31 of the donor base station 3B and reaches the MME 6 (S27).
  • the attachment process of the relay node 5A is completed.
  • the relay node 5A allocates one of the acquired IP addresses to the own device, thereby enabling the U-plane IP communication with the donor base station 3B (S30).
  • the relay node 5A can communicate with O & M (Operation & Maintenance) on the network, it requests the O & M to download a setting file and performs settings for operating as a relay node (Node / Configuration). : S28). As a result, the base station function 51 in the relay node 5A is activated.
  • O & M Operaation & Maintenance
  • the base station function 51 of the relay node 5A establishes the S1 interface for the wireless terminal 4 or other relay node 5 attached to the relay node 5A, so that the MME 6 is connected to the relay node 5A via the relay node 5B and the donor base station 3B.
  • An SCTP (Stream Control Transmission Protocol) link is established.
  • the base station function 51 of the relay node 5A sends an S1AP message “S1AP: S1 Setup Request” to the MME 6 to establish the S1 interface (S1 / X2 IF Setup: S29).
  • the relay node 5B terminates the S1 interface between the donor base station 3B and the relay node 5A once in the relay node 5B, transfers the message, and sends it to the other party.
  • the donor base station 3B activates the S1 proxy function in the donor base station 3B to proxy the S1 interface between the relay node 5A and the MME 6. As a result, the S1AP message transmitted / received between the relay node 5A and the MME 6 is transferred to the donor base station 3B.
  • FIG. 3 shows a protocol stack related to the attachment of the lower relay node shown in FIG.
  • the top row shows the protocol stack of the S1-MME interface between the relay node 5B and the MME 6.
  • the next level shows the protocol stack of the S11 interface between the relay node 5B and the MME 6.
  • the next level shows the protocol stack of the S1-MME interface between the relay node 5A and the MME 6.
  • the fourth and fifth stages from the top are the S1-MME interface between the other relay node 5 and the MME 6 and the S1-U interface when another relay node 5 that is a subordinate device of the relay node 5A is attached. Indicates the protocol stack. However, when there is no other relay node 5, there is no S1-MME interface between the donor base station 3B and the MME 6 related to the relay node 5 (see the broken line block, however, the setting is performed).
  • the upper layer of IP does not exist until it becomes necessary (see the dashed block).
  • FIG. 4 is an explanatory diagram showing an example of IP address group assignment when another relay node 5D (Relay A2) is attached to a donor base station (DeNB) 3B having a relay node 5C (Relay A1) under control. It is. Relay nodes 5C and 5D correspond to relay node 5B shown in FIG.
  • the donor base station 3B includes an IP address list 35 in which a plurality of IP address groups to be allocated to relay nodes under the control of the donor base station 3B are pooled.
  • the address list 35 includes a first group consisting of IP address groups “IP-A1 to An” (n is a natural number excluding 0), and a first group consisting of IP address groups “IP-B1 to Bn”. A third group of two groups and IP addresses “IP-C1 to Cn” is registered. The assignment state (assigned or unassigned) of each group can be recorded in the IP address list 35.
  • the IP address group “IP-A1 to An” of the first group has already been assigned to the relay node 5C, whereas the second group and thereafter are in an unassigned state. .
  • the relay node 5C can assign one of the IP address groups “IP-A1 to An” assigned to the relay node 5C itself as the IP address of the relay node 5C itself. For example, a representative address (for example, “IP-A1 (IP-AA1)” at the head of the IP address group) can be assigned to the relay node 5C. The remaining IP address group “IP-A2 to An” can be assigned to the relay node 5 located under the relay node 50C itself.
  • the relay node 5C divides the IP address group “IP-A1 to An” to generate a plurality of IP address groups that can be assigned to the subordinate relay node 5.
  • the IP address group “IP-A1 to An” is divided into “IP-AA1 to AAm”, “IP-AB1 to ABm”, “IP-AC1 to ACm”,.
  • IP-AA1 to AAm One of “IP-AA1 to AAm” obtained by dividing “IP-A1” (the leading “IP-AA1”) is used as the IP address of the relay node 5C itself as described above.
  • the relay node 5C stores a plurality of IP address groups obtained by the division in the subordinate relay IP address list 35A (FIG. 5) for assigning the subordinate relay nodes.
  • NAS:“ Attach ”Request” including the IMSI of the relay node 5D is transmitted to the donor base station 3B so that the relay node 5D performs the first attach.
  • “NAS: Attach Request” is transferred to the MME 6 by the method described with reference to FIG. 2 ( ⁇ 1> in FIG. 4).
  • the MME 6 inquires the HSS 9 for information (contract information, etc.) corresponding to the IMSI in “NAS:“ Attach ”Request” ( ⁇ 2> in FIG. 4) and obtains the corresponding information ( ⁇ 3> in FIG. 4).
  • the MME 6 When the information obtained from the HSS 9 includes information that the IMSI related to the inquiry is the IMSI for the relay node (when the MME 6 obtains a reply that the IMSI is for the relay node), the MME 6 , It decides to transmit a bearer setting request (“S11AP:“ Create Session Request ”) to the S / PGW function (S / PGW) 33 (FIG. 3) for the relay UE provided in the donor base station 3B ( ⁇ 4>). Then, the MME 6 sends “S11AP:“ Create Session Request ”to the donor base station 3B ( ⁇ 5> in FIG. 4).
  • S11AP “ Create Session Request
  • the S / PGW function 33 for the relay UE of the donor base station 3B receives “S11AP:“ Create Session ”Request”, it refers to the IP address list 35 and selects an unassigned IP address group. For example, the IP address group “IP-B1 to Bn” of the second group is selected. At this time, the assignment state for the second group is changed to assigned.
  • the S / PGW function 33 for the relay UE transmits a message “S11AP:“ Create ”session” Response ”including the selected IP address group to the MME 6 ( ⁇ 6> in FIG. 4).
  • the MME 6 transmits a response message “NAS: Attach Accept” including the IP address group (second group) to the relay node 5D, for example, on the S1AP message “S1AP: Initial Context Setup Request” ( ⁇ 7> in FIG. As a result, the relay node 5D can receive (acquire) the IP address group.
  • NAS Attach Accept
  • S1AP Initial Context Setup Request
  • the relay node 5D itself uses one of the IP address groups “IP-B1 to Bn” (for example, the top address “IP-B1 (IP-BA1)” in the IP address group) as a representative address. ( ⁇ 8> in FIG. 4). Subsequently, the IP address group is divided ( ⁇ 9> in FIG. 4). In the example of FIG. 5, the IP address group “IP-B1 to Bn” is divided into “IP-BA1 to BAm”, “IP-BB1 to BBm”, “IP-BC1 to BCm”,.
  • the relay node 5D uses one of the IP addresses (IP-BA1 to BAn) obtained by dividing the IP address group (IP-B1) assigned to itself (for example, “IP-BA1” at the head) as its own IP address. Can be set as The relay node 5D registers a plurality of IP address groups obtained by the division in the subordinate relay IP address list 35A.
  • an IP address group is assigned to the relay node 5 in consideration of the multi-stage connection of the relay node 5.
  • the relay node 5 having acquired the IP address group can select an IP address to be used by the relay node 5 itself from one of the IP address groups and set it as the IP address of the relay node 5 itself.
  • the remaining IP addresses are pooled in the IP address list 35A to be assigned to relay nodes connected in a lower order.
  • an IP address group assigned to the relay node 5 connected in a lower order can be arranged.
  • FIG. 5 is a diagram for explaining an IP address assignment operation example when the relay node 5E (RelayReB1: equivalent to the relay node 5A in FIG. 2) is attached to the relay node 5C (Relay A1) shown in FIG. It is.
  • the relay node 5E transmits a message “NAS:“ Attach ”Request” including the IMSI of the relay node 5E using the UE function 51 of the relay node 5E in the first attach.
  • “NAS: Attach Request” reaches the MME 6 via the relay node 5C and the donor base station 3B ( ⁇ 1> in FIG. 5).
  • the MME 6 inquires the HSS 9 for information (contract information or the like) corresponding to the IMSI ( ⁇ 2> in FIG. 5), and obtains the corresponding information ( ⁇ 3> in FIG. 5).
  • the MME 6 recognizes from the information obtained from the HSS 9 that the relay node 5E to be attached is the relay node 5 and is located under the relay node 5C, and sets a bearer for assigning an IP address to the relay node 5E.
  • a request message “S11AP:“ Create ”Session“ Request ” is transmitted ( ⁇ 5> in FIG. 5).
  • “S11AP: Create Session Request” is relayed by the proxy S / PGW function 32 of the donor base station 3B ( ⁇ 6> in FIG. 5) and sent to the S / PGW function 53 for the relay UE of the relay node 5C (FIG. 5). ⁇ 7> of 5).
  • the IP address group to be assigned to the relay node 5E is selected from the IP address list 35A provided in the relay node 5C.
  • the IP address group “IP-AB1 to ABn” is selected from the IP address list 35A.
  • the allocation state for the IP address group “IP-AB1 to ABn” is changed to “allocated”.
  • the S / PGW function 53 sends a message “S11AP:“ Create Session Response ”including the selected IP address group to the donor base station 3B ( ⁇ 8> in FIG. 5).
  • the donor base station 3B relays “S11AP:“ Create Session Response ”” and sends it to the MME 6 ( ⁇ 9> in FIG. 5).
  • the MME 6 transmits a response message “NAS: Attach Accept” including the IP address group obtained from “S11AP: Create Session Response” in the S1AP message “S1AP: Initial Context Setup Request”, for example. .
  • “NAS: Attach Accept” reaches the relay node 5E via the donor base station 3B and the relay node 5C ( ⁇ 7> in FIG. 5). As a result, the relay node 5E can receive (acquire) the IP address group “IP-AB1 to ABn”.
  • one of the IP address groups is set as the IP address of the relay node 5E itself. Further, the IP address group is further divided and registered in the IP address list 35A.
  • the relay node 5E performs the same processing as the relay node 5C, the relay node 5C relays the message, and the donor base stations 3B, MME6, and HSS9.
  • a predetermined IP address or a group of IP addresses can be allocated to another relay node from the group of IP addresses allocated to the relay node 5E.
  • FIG. 6 shows an example of assignment of IPv4 IP address groups.
  • the donor base station 3B (its IP address list) has 4096 IP addresses, and 16 IP address groups G1 to G1 each consisting of 256 IP addresses from these IP addresses. G16 is formed.
  • IP address group G2 allocated from donor base station 3B is further divided into 16 IP address groups including 16 IP addresses.
  • One of the 16 IP address groups (G1) is assigned to the relay node 5C.
  • FIG. 6 shows an example in which the IP address group G2 is assigned to the second relay hop (relay node 5E) among the IP address groups G2 to G16 of the relay node 5C.
  • the relay node 5E for example, the head address in the IP address group G2 can be assigned to the relay node 5E, and the rest can be assigned to the relay nodes under its control.
  • the maximum number of relay nodes 5 that can be cascade-connected (multistage connection) to the donor base station 3B is three.
  • the number of cascade connections can be increased by increasing the IP address space (number of IP addresses) registered in the IP address list of the donor base station 3B or by adopting IPv6 addresses.
  • ⁇ S11 interface settings> In the LTE network according to the present embodiment, when the relay node under the donor base station 3B sets the S1 interface for the lower relay node, the MME and the MME are used to control the S / PGW function in the relay node. S11 interface is set.
  • FIG. 7A is a diagram for explaining interface settings between the donor base station and the MME and between the donor base station and the relay node.
  • FIG. 7A shows various interfaces for connecting the relay node 5 to the MME 6 via the donor base station 3B.
  • the donor base station 3B in order to exchange a NAS signal (NAS message) between the relay node 5 and the MME 6, the donor base station 3B has an RRC connection on the relay node side, while an S1 interface based on S1AP on the MME 6 side. have.
  • the S1 interface (S1AP layer) between the donor base station 3B and the MME 6 is connected by an STCP (Stream Control Transmission Protocol) link.
  • STCP Stream Control Transmission Protocol
  • the SME interface for the relay node 5 is connected between the MME 6 and the relay node 5.
  • DRB Data ⁇ ⁇ ⁇ Radio Bearer
  • An SCTP link is established on this DRB, and an S1AP session is established between the relay node 5 and the donor base station 3B. Thereby, the S1 interface is established.
  • the S1 interface (SCTP link) between the donor base station 3B and the MME 6 is used so that this S1 interface is extended to the MME 6.
  • the DRB setting described above can be started when the donor base station 3B receives the attach completion message “Attach Complete” from the relay node in the attach procedure of the relay node 5.
  • the S1 interface of the donor base station 3B and the S1 interface for the relay node 5 are identified by using different identification IDs (for example, eNB / MME S1AP ID) between the donor base station 3B and the relay node 5. This is performed by the MME 6 using the ID to distinguish the source of the S1AP message. With the identification ID, the donor base station 3B and one or more relay nodes 5 can be uniquely identified. Further, by using the same type of ID as the UE identification ID as the base station / relay node identification ID, the MME 6 uniquely distinguishes the donor base station, relay node, and UE that are the message transmission source. It may be adopted.
  • identification IDs for example, eNB / MME S1AP ID
  • a proxy function (P.eNB, PS / PGW) is provided to perform proxy (proxy) transfer processing of the S1AP message between the relay node 5 and the MME 6.
  • the following configuration is adopted. That is, between the donor base station 3B and the MME 6, an S11 interface that connects the S / PGW function of the donor base station 3B and the MME 6 is established by UDP (User Datagram Protocol).
  • UDP User Datagram Protocol
  • the S11 interface is set between the relay node 5 and the donor base station 3B so that the S11 interface is extended to the relay node 5.
  • the UDP port is set using the DRB used for the construction of the S1 interface between the relay node 5 and the donor base station 3B, and the S11AP identifier S11AP-TEID is transmitted and received.
  • the S11 interface can be set.
  • Such setting of the S11 interface can be performed simultaneously with the setting of the S1 interface beginning with the above-described DRB setting.
  • the S / PGW function in the relay node 5 can communicate with the MME 6 via the donor base station 3B using the constructed S11 interface.
  • an IP address assignment instruction is issued from the MME 6.
  • the relay node 5 can receive an IP address assignment instruction and can assign an IP address to a subordinate relay node.
  • the donor base station 3B can relay the S11AP message between the relay node 5 and the MME 6 using the proxy transfer function.
  • FIG. 7B is a diagram for explaining the setting of the S1 interface and the S11 interface with the MME 6 when the relay node 5A is attached under the relay node 5B.
  • an RRC link for NAS connection between the relay node 5A and the MME 6 is set between the relay node 5A and the relay node 5B.
  • the relay node 5B receives the attach completion message “Attach Complete” transmitted from the relay node 5A to the MME 6, the setting of the S1 and S11 interfaces between the relay node 5B and the relay node 5A is started. .
  • the relay node 5B performs DRB setting (setting of DRB2 in FIG. 7B) for the default U plane bearer, and notifies the relay node 5A of the completion of DRB setting. Subsequently, the relay node 5A and the relay node 5B establish an SCTP link on the DRB 2 and set a UDP port.
  • the relay node 5B associates the SCTP link between the relay nodes 5A-5B and the upper SCTP link (the SCTP link on the DRB 1 between the relay node 5B and the donor base station 3B).
  • the relay node 5A transmits an “S1 Setup Request” which is an S1AP message to the relay node 5B, and establishes an S1AP session between the two.
  • an S1AP route is established between the relay nodes 5A and 5B.
  • the relay node 5A transmits and receives TE11 for S11AP to and from the relay node 5B. As a result, the S11 interface is set between them. Furthermore, the relay node 5B associates the S1AP route between the relay nodes 5A and 5B with the upper S1AP route. As a result, the S1AP route (S1 interface) from the relay node 5A to the MME 6 is established.
  • FIG. 8 is a diagram for explaining an operation example when the radio terminal (UE) 4 attaches (UE attach) under the control of the relay node 5A in the LTE network as shown in FIG.
  • the relay node 5A (Relay 1) uses a base station function 51 and a UE function 52 provided therein. Further, the relay node 5B (Relay2) uses the proxy base station function 54 provided therein. The donor base station 3B uses the proxy base station function 31 and the S / PGW function 33.
  • the sequence shown in FIG. 8 is started when the UE 4 enters the cell of the relay node 5A, detects the relay node 5A, and starts the attach process.
  • the UE 4 sets an RRC connection with the base station function 51 of the relay node 5A (RRC Connection Setup) (S51). Subsequently, the UE 4 transmits the NAS message “NAS:“ Attach ”Request” to the RRC message “RRC:“ Initial ”Direct“ Transfer ”and transmits it to the relay node 5A (S52). Since the attach process of UE4 at this time corresponds to first attach, the IMSI of UE4 is set in “RRC: Attach Request”.
  • the base station function 51 of the relay node 5A uses the S1 interface set between the relay node 5A and the relay node 5A to send “RRC: Attach Request” received from the UE4 to the S1AP message “S1AP: Initial. It is transferred to “UE Message” and sent to the relay node 5B (S53).
  • the proxy base station function 54 of the relay node 5B transfers all the S1 messages (S1AP messages) from the subordinate relay node 5A to the SCTP link / S1 interface to the donor base station 3B and transfers them (S54).
  • the proxy base station function 31 of the donor base station 3B recognizes the S1 (S1AP) message from the relay node 5A that has arrived via the relay node 5B, and transfers the S1 message to the MME 6 by the proxy function (S55).
  • the MME 6 starts an authentication procedure according to the content of “RRC:“ Attach ”Request” in the S1 message. For example, the MME 6 inquires and acquires the contract information (subscriber data) of the terminal (terminal corresponding to the IMSI) related to Attach IV to the HSS 9 (S56). Subsequently, the MME 6 performs an authentication process with the UE function 52 of the relay node 5A using the contract information (Authentication: S57).
  • NAS encryption (ciphering) and integrity protection are set in the S1AP between the MME 6 and the donor base station 3B according to the security start instruction (S58). Also, encryption is set for the S1AP and PDCP U-plane (PDCP-UP) between the donor base station 3B and the relay node 5B, and S1AP and PDCP-UP between the relay node 5B and the relay node 5A. (S59, S60). Further, encryption and integrity protection are set in the PDCP-C plane (PDCP-CP) between the relay node 5A and the UE 4 (S61). Furthermore, location registration is performed from the MME 6 to the HSS 9 (S62).
  • the MME 6 Based on the contract information obtained from the HSS 9, the MME 6 recognizes that the end of the attachment is UE 4, determines SGW 7 and PGW 8 (S / PGW) that serve this UE 4, and establishes a default bearer (Default Bearer) establishment procedure. / PGW is determined to be performed (S63). Then, the MME 6 transmits an S11AP message “S11AP: Create Session Request” to the S / PGW (S64).
  • the S / PGW Upon receiving “S11AP: Create Session Request”, the S / PGW transmits a response message “S11AP: Create Session Response” including the IP address assigned to the UE 4 (S65).
  • the MME 6 receives “S11AP: Create Session Response” and confirms that the default bearer preparation is complete. Then, “NAS: Attach Accept” is put on “S1-AP: Initial Context Setup Request” and transmitted to the donor base station 3B. “S1-AP: Initial Context Setup Request” including “NAS: Attach Accept” includes the IP address for the UE.
  • S1-AP Initial Context Setup Request
  • NAS Attach Accept
  • S67, S68 Received by the base station function 51 of the relay node 5A.
  • the base station function 51 constructs a context for UE4.
  • the base station function 51 transmits “RRC: RRC Connection Reconfiguration” carrying “NAS: AttachAAccept” to the UE 4 (S69).
  • UE4 receives “NAS: Attach Accept / RRC: RRC Connection Reconfiguration”, acquires the IP address that is a parameter in this message, and sets the IP address as the IP address of UE4 itself (S70).
  • the UE 4 sends a response message “RRC: RRC Connection Reconfiguration Complete” (S71). Since it is impossible to put a NAS message on this “RRC: RRC Connection Reconfiguration Complete”, the UE 4 then sends a “NAS: Attach Complete” message with “RRC: UL Information Transfer” (S71).
  • the relay node 5A When the relay node 5A receives “RRC: RRC Connection Reconfiguration Complete”, the relay node 5A notifies the MME of the completion of the Context construction of the UE 4 with the S1AP message “S1-AP: Initial Context Setup Response”. “S1AP: Initial Context Setup Response” reaches the MME 6 from the relay node 5A via the relay node 5B and the donor base station 3B (S71, S72, S73).
  • the relay node 5A transmits “NAS: Attach Complete” transmitted from the UE 4 by “RRC: UL Information Transfer” to “S1-AP: Uplink NAS Transport” (S74).
  • S1-AP Uplink NAS Transport
  • S75, S76 MME 6
  • the MME 6 receives “NAS: Attach Complete” following “S1AP: Initial Context Setup Response”. Then, the MME 6 sends a message “S1AP: Modify Bearer Request” for instructing the S / PGW to construct the default bearer of the U plane of the UE 4 (S77). When the response message “S11AP:“ Modify ”Bearer” Response ”from the S / PGW is received by the MME 6 (S78). A U-plane default bearer of UE4 is constructed.
  • GTP-U tunnels are set up respectively.
  • PDCP-UP encryption is set between the UE 4 and the relay node 5A, between the relay node 5A and the relay node 5B, and between the relay node 5B and the donor base station 3B.
  • FIG. 9 shows a protocol stack related to UE attachment. Due to the UE attachment, the difference from FIG. 3 is that in the UE attachment, the protocol stack of the S1-MME interface for the UE and the S1-U interface for the UE is shown.
  • RRC is applied between the UE 4 and the relay node 5A for exchanging NAS messages between the UE 4 and the MME 6, and the relay node 5A, the relay node 5B, the donor base station 3B, and the MME 6 S1AP is applied in between.
  • the relay node 5B and the donor base station 3B except for the lowest relay node 5A transfer the NAS message by the proxy base station function.
  • the UE 4 and S / PGW (SGW 7 and PGW 8) are connected by IP, and a GTP-U tunnel is constructed.
  • the donor base station 3B has the S / PGW function 53, and the S / PGW function 53 assigns an UP address to the relay node 5 in units of IP addresses.
  • the IP address group is formed of two or more IP addresses. By assigning the IP address group to the relay node 5, when another relay node 5 is attached under the relay node 5, one of the IP addresses assigned to the relay node 5 is assigned to the other relay node. 5 can be assigned.
  • the relay node 5 creates a subdivided IP address group based on the assigned IP address group, and assigns one of the IP address groups when the lower relay node 5 is attached.
  • the lower relay node 5 can assign an IP address group or an IP address to the lower relay node 5.
  • the S11 interface is also set up with the relay node 5 in order to control the S / PGW function of the relay node 5. Set.
  • the overhead can be reduced as compared with the case where the S11 interface is set when the UE is attached to the relay node 5.
  • the relay node 5 can distinguish S1 messages to lower nodes and distribute S1 messages to corresponding lower nodes.
  • the S1 message from the lower node can be distinguished and transferred to the upper node.
  • FIG. 10 is a diagram illustrating a configuration example of the donor base station 3B.
  • FIG. 10 shows a hardware configuration example of the donor base station 3B.
  • the donor base station 3B includes a transmission path interface 131, an L2 switch (L2SW) 132, a control unit 133, a baseband processing unit 134, and a radio interface 135.
  • L2SW L2 switch
  • Each of these units is realized by one or more hardware or hardware chips such as an electric / electronic circuit, an IC, an LSI, and an ASIC.
  • the wireless interface 135 includes an antenna 136, a broadband amplifier 137, an analog-digital converter (A / D) and a digital-analog converter (D / A) 138, an input / output port (I / O) 139, and the like.
  • the radio interface 135 receives a radio signal from the UE 4 or the relay node 5 located in the cell of the donor base station 3B by the antenna 136, converts it to a digital signal by the A / D converter 138, and passes through the input / output port 139. Input to the L2 switch 132.
  • the radio interface 135 D / A converts the signal from the L2 switch 132, amplifies the signal by the broadband amplifier 137, and radiates it from the antenna 136, thereby transmitting the radio signal to the UE 4 and the relay node 5 in the cell. Can do.
  • the L2 switch 132 performs a switching process of a signal (message) transmitted between the control unit 133, the wireless interface 135, the baseband processing unit 134, and the transmission path interface 131.
  • the baseband processing unit 134 includes a processor such as a digital signal processor (DSP) 134A, and a memory (MEM) 134B that is a storage medium (storage) in which programs and data executed by the DSP 134A are stored, and the DSP 134A includes a memory 134B.
  • DSP digital signal processor
  • MEM memory
  • the baseband processing of the signal input from the L2 switch 132 is performed by executing the program (firmware) stored in the, and the processed signal is output to the L2 switch 132.
  • the transmission path interface 131 is connected to the MME 6 and S / PGW (not shown) via the S1 interface on the IP network 10, and includes other base stations 3 (including the donor base station 3B) via the X2 interface. ) And exchange signals with them.
  • the control unit 133 includes a processor (microprocessor) such as a central processing unit (CPU) 133A and a memory (MEM) 133B that is a storage medium (storage) in which programs and data executed by the CPU 133A are stored. Executes various programs such as message processing, call processing, connection management between devices, and monitoring processing by executing programs stored in the memory 133B.
  • processor microprocessor
  • CPU central processing unit
  • MEM memory
  • the donor base station 3B illustrated in FIG. 10 includes three systems of the radio interface 135 and the baseband processing unit 134, but the number of systems can be set as appropriate with one or more.
  • FIG. 11 shows functional blocks realized by executing firmware by the DSP 134A of the baseband processing unit 134 shown in FIG.
  • the execution of the firmware causes the control unit communication unit 141 that manages communication processing with the control unit 133, the traffic management unit (GTP management unit) 142, and the traffic transfer processing unit (GTP transfer processing unit) 143. Realized.
  • the traffic management unit 142 and the traffic transfer processing unit 143 manage traffic relay (GTP-U tunnel-radio bearer) pair processing between the relay node 5 and the MME 6.
  • a traffic monitoring / cell state monitoring unit 144 that monitors traffic and cell state by executing firmware, a secret setting / release unit 145 that performs secret setting and release setting of information, and a radio that performs processing related to the radio layer
  • the layer processing unit 146 is realized.
  • FIG. 12 shows functional blocks realized by program execution by the CPU 133A of the control unit 133 shown in FIG.
  • the control unit 133 functions as an apparatus including a message processing unit 151 including a reception unit 161, a transmission unit 162, an analysis unit 163, and each protocol processing unit 164.
  • the control unit 133 includes a call processing unit 152 that performs call processing for the UE 4 and the relay node 5, an IP address allocation control unit 153 that performs IP address allocation control for the relay node 5, and an IP address group. And functions as a device having an IP address pool 154 corresponding to the IP address list 35.
  • the control unit 133 causes the resource management unit 155, the DeNB-UE connection management control unit 156 to perform connection management and control between the donor base station 3B and the UE 4, the donor base station 3B, and the relay node 5 It functions as a device including a DeNB-Relay connection management control unit 157 that performs connection management and control with each other, and each device processing unit monitoring control unit 158.
  • FIGS. 11 and 12 can be realized using one or more general-purpose or dedicated hardware chips.
  • FIG. 13 is a flowchart illustrating a processing example of the reception unit 161.
  • the processing of the reception unit 161 illustrated in FIG. 13 is started after the initial setting in the donor base station 3B, for example. However, the processing of the receiving unit 161 may be started by another trigger.
  • the receiving unit 161 checks the head of a reception queue (not shown) (step S101).
  • the data received by the wireless interface 135 and the transmission path interface 131 (FIG. 10) is stored (attached) in the reception queue.
  • Data stored in the reception queue is subjected to processing such as transport layer header removal, or processing such as assigning an interface ID attached to the reception queue, and has a message format.
  • the reception unit 161 determines whether or not data (message) is stored at the head of the reception queue (step S102). At this time, if there is no message (N in S102), the process returns to step S101. On the other hand, if there is a message (Y in S102), the process proceeds to the next step S103.
  • step S103 the message is extracted from the head of the reception queue and transferred to the analysis unit 163 (step S104). Thereafter, the process returns to step S101.
  • FIG. 14 is a flowchart illustrating a processing example of the transmission unit 162.
  • the processing of the transmission unit 162 illustrated in FIG. 14 is started after the initial setting in the donor base station 3B, for example. But the process of the transmission part 162 may be started by another trigger.
  • the transmission unit 162 checks the head of a transmission queue (not shown) (step S111).
  • messages from the analysis unit 163 and each protocol processing unit 164 are stored (attached) in the transmission queue.
  • the message includes an identifier (ID) that can distinguish the destination interface (transmission path interface 131, wireless interface (wireless bearer) 135).
  • the transmission unit 162 determines whether or not a message is stored at the head of the transmission queue (step S112). At this time, if there is no message (N in S112), the process returns to step S111. On the other hand, if there is a message, the process proceeds to the next step S113.
  • step S113 the transmission unit 162 takes out the message from the head of the transmission queue and transfers the message to the interface corresponding to the ID included in the message (step S114). Thereafter, the process returns to step S111.
  • FIG. 15 is a flowchart illustrating a processing example of the analysis unit 163. The process illustrated in FIG. 15 is started after the initial setting in the donor base station 3B, for example. However, the process of FIG. 15 may be started by another trigger.
  • the analysis unit 163 receives a message from the reception unit 161 (step S121). Next, the analysis unit 163 analyzes the message protocol (step S122). Next, the analysis unit 163 determines the protocol type of the message (step S123).
  • step S124 If “S1AP”, the process proceeds to step S125. If “S1AP”, the process proceeds to step S130.
  • step S124 when the protocol type is RRC, the RRC protocol process is executed by each protocol processing unit 164 (FIG. 15). Thereafter, the process returns to step S121.
  • the analysis unit 163 extracts the session ID in the S1AP message from the message.
  • the session ID is an identifier (ID) for distinguishing S1AP sessions, and is a unique identifier for each donor base station.
  • the analysis unit 163 determines whether or not the session ID is a relay target (step S126). At this time, if the session ID is not a relay target (N in S126), the S1AP protocol process is executed by each protocol processing unit 164 (step S127). Thereafter, the process returns to step S121.
  • the analysis unit 163 refers to a transfer conversion table (not shown) and rewrites the message according to the setting contents in the transfer conversion table (step S128). Thereafter, the analysis unit 163 attaches (stores) the rewritten message to the transmission queue (step S129), and returns the process to step S121.
  • GTP-TEID is an identifier (ID) for distinguishing S11AP sessions, and is a unique identifier for each donor base station.
  • the analysis unit 163 determines whether the GTP-TEID is a relay target (step S131). At this time, if the GTP-TEID is not a relay target (N in S131), the S11AP protocol process is executed by each protocol processing unit 164 (step S132). Thereafter, the process returns to step S121.
  • the analysis unit 163 refers to a transfer conversion table (not shown) and rewrites the message according to the setting contents in the transfer conversion table (step S133). Thereafter, the analysis unit 163 attaches (stores) the rewritten message to the transmission queue (step S134), and returns the process to step S121.
  • the analysis unit 163 determines the protocol type, and determines whether the S1AP message and the S11AP message are to be relayed based on the session ID or GTP-TEID. And is stored in the transmission queue.
  • the transfer conversion table describes the conversion contents of messages corresponding to session IDs and GTP-TEIDs.
  • FIG. 16 is a flowchart showing an example of processing (subroutine of S132 (FIG. 15)) of the S11AP protocol processing unit (S11 processing unit) included in each protocol processing unit 164 (FIG. 12).
  • the protocol processing unit receives a message and analyzes the message (step S141) to determine the message type (step S142).
  • step S147 If the message is “Create Session Request”, the process proceeds to step S143. If the message is other than “Create Session Request”, other message processing is executed (step S147).
  • step S143 the S11AP protocol processing unit determines whether “Create Session Request” includes an IP address request. At this time, if the IP address request is not included (N in S143), the process proceeds to Step SS146.
  • the S11AP protocol processing unit requests an IP address group from the IP address allocation control unit 153 (FIG. 12) (step S144). That is, the S11AP protocol processing unit sends an IP address group acquisition request message to the IP address allocation control unit 153.
  • the S11AP protocol processing unit receives the IP address group from the IP address assignment control unit 153 (step S145), and performs processing for other parameters in the message (step S146).
  • the S11AP protocol processing unit determines whether or not there is an error relating to the message or processing for the message (step S148).
  • the S11AP protocol processing unit If there is no error (N in S148), the S11AP protocol processing unit generates a normal response message “Create Session Response” (step S149). At this time, the S11AP protocol processing unit adds a parameter including an IP address group to the response message.
  • the S11AP protocol processing unit attaches (stores) the response message “Create Session Response” to the transmission queue of the transmission unit 162, and returns the process to step S141.
  • step S148 if it is determined in step S148 that there is an error (Y in S148), the S11AP protocol processing unit generates an error response message “Create Session Reject” (step S151) and sends it to the IP address allocation control unit 153. Cancel is transmitted (step S152). Then, the S11AP protocol processing unit stores “Create Session Reject” in the transmission queue, and returns the process to step S141.
  • the S11AP protocol processing unit determines whether or not an IP address request is included in the S11AP message, and if included, obtains an IP address group from the IP address assignment control unit, and obtains this IP address. Attach a reply message containing a group to the send queue.
  • FIG. 17 is a flowchart showing a processing example of the IP address assignment control unit 153 (FIG. 12).
  • the IP address assignment control unit 153 creates an IP address pool 154 (IP address list 35) (step S161).
  • IP address pool 154 IP address list 35
  • a plurality of IP addresses that are initially registered in the IP address pool 154 are determined in advance.
  • the IP addresses of a plurality of IPs in the initial state are held as initial data in the IP address pool 154.
  • the IP address allocation control unit 153 determines the number of IP addresses to be allocated (IP address allocation number) in response to one IP address request.
  • the number of IP addresses is determined in advance, and the IP address assignment control unit 153 can determine the number by adopting the predetermined (set) number of IP addresses.
  • the IP address assignment control unit 153 generates a plurality of IP address groups from the plurality of IP addresses by dividing the plurality of IP addresses in the initial state by the number of IP address assignments (step S162).
  • the number of divisions for a plurality of IP addresses in the initial state may be set in advance, and the IP address assignment control unit 153 may generate a plurality of IP address groups from the plurality of IP addresses based on the number of divisions.
  • the IP address assignment control unit 153 assigns an unassigned flag to all IP addresses in the IP address pool 154 (step S163).
  • the unassigned flag may be assigned for each IP address or may be assigned for each IP address group.
  • “unassigned” is indicated when the flag is off, and “allocated” is indicated when the flag is on.
  • the reverse may be possible.
  • steps S161 to S163 described above are processes at the time of initial setting of the IP address pool 154.
  • step S163 ends, the IP address allocation control unit 153 transitions to a state of waiting for a message from the S11AP protocol processing unit.
  • step S164 the IP address allocation control unit 153 analyzes the message received from the S11AP protocol processing unit, and determines the message type (step S165). At this time, if the message type is an IP address group acquisition request, the process proceeds to step S166, and if the message type is an IP address group cancel, the process proceeds to step S168.
  • step S166 the IP address allocation control unit 153 acquires one of the IP addresses that are not allocated from the IP address pool 154. Subsequently, the IP address allocation control unit 153 sets a flag for the acquired IP address group to ON (allocated) (step S167). Thereafter, the process returns to step S164 to enter a standby state for the next message.
  • step S168 the IP address assignment control unit 153 sets the flags corresponding to all the IP addresses to be canceled to OFF (unassigned). Thereafter, the process returns to step S164 to enter a standby state for the next message.
  • FIG. 18 shows an S1AP protocol processing unit (hereinafter referred to as an S1 processing unit) included in each protocol processing unit 164 (FIG. 12) of the donor base station 3B when the relay node 5 is attached to the donor base station 3B. It is a flowchart which shows the example of the process (The subroutine (FIG. 15) of step S127).
  • the S1 processing unit is in a message waiting state, performs analysis when receiving a message (step S171), and determines a message type (step S172). At this time, if the message type is “Initial Context Setup Request”, the S1 processing unit advances the process to step S173. On the other hand, if the message type is a message other than “Initial Context Setup Request”, processing for other messages is executed (step S178).
  • step S173 the S1 processing unit instructs the context construction by transmitting the relay node related parameter to the DeNB-Relay connection management control unit 157 (denoted as DR control unit 157 in FIG. 12).
  • step S174 the S1 processing unit receives a completion response from the DR control unit 157. Then, the S1 processing unit transfers the NAS message “Attach Accept” to the RRC protocol processing unit (also referred to as RRC processing unit) in each protocol processing unit 164 (step S175).
  • RRC protocol processing unit also referred to as RRC processing unit
  • the S1 processing unit waits for a message from the RRC processing unit (step S176). Note that the actual processing of step S176 is processed as a response of “Initial Context Setup Setup Request” determined through message reception and analysis processing in steps S171 and S172.
  • the S1 processing unit determines whether there is an error in processing related to the message content and the message (step S179). At this time, if there is no error (N in S179), the S1 processing unit creates a response message “Initial Context Setup Setup Response” to “Initial Context Setup Request” (step S180) and stores it in the transmission queue of the transmission unit 162. (Step S181). Thereafter, the process returns to step S171.
  • the S1 processing unit determines whether there is an error (Y in S179). If there is an error (Y in S179), the S1 processing unit generates an error response message “Initial Context Setup Reject” (step S182) and stores it in the transmission queue (step S181).
  • FIG. 18 shows processing when the relay node 5 is attached (at the time of relay attachment).
  • the process in which the relay node related parameter is transmitted to the DR control unit 157 in step S173 is the same as the DeNB-UE connection management control unit 156 (also referred to as the DU control unit 156). )
  • the process of instructing context construction is the same as the processing at the time of relay attachment.
  • FIG. 19 is a flowchart showing a processing example by the RRC protocol processing unit (RRC processing unit) in each protocol processing unit corresponding to the processing shown in FIG.
  • RRC processing unit RRC protocol processing unit
  • the RRC processing unit is in a message waiting state, performs analysis when receiving a message (step S191), and determines a message type (step S192). At this time, if the message is not a NAS message from the S1AP processing unit, other message processing is performed (step S199).
  • the RRC processing unit shall transmit“ Attach Request ”with the RRC message“ RRC Connection Reconfiguration ”from the related parameters included therein. Is determined (step S193).
  • the RRC processing unit creates “RRC Connection Reconfiguration” carrying “Attach Request” (step S194), and attaches the message to the transmission queue of the transmission unit 162 (step S195).
  • the RRC processing unit waits to receive “RRC Connection Reconfiguration Complete”, which is a response message of “RRC Connection Reconfiguration” (step S196). Actually, it is performed by waiting for the reception of “RRC Connection Reconfiguration Complete” to be determined by the message reception and analysis processing in step S191 and the message type determination processing (step S192).
  • step S197 When “RRC Connection Reconfiguration Complete” is received (step S197), the RRC processing unit notifies the S1 processing unit that RRC Connection Reconfiguration has been completed along with the parameters in “RRC Connection Reconfiguration Complete” (step S197). S198). Thereafter, the process returns to step S191.
  • step S176 when the error response message “RRC Connection Reconfiguration Failure” is received, the RRC processing unit notifies the S1 processing unit of the error.
  • FIG. 20 is a flowchart illustrating a processing example of DeNB-Relay connection management performed by the DeNB-Relay connection management control unit (DR control unit) 156.
  • DR control unit DeNB-Relay connection management control unit
  • the process shown in FIG. 20 is started when the DR control unit 156 receives a context creation parameter from the S1 processing unit (step S201).
  • the DR control unit 156 creates a context for the relay node. Subsequently, the DR control unit 156 creates a transfer conversion table for the S1AP message (step S203). Furthermore, the DR control unit 156 also creates a transfer conversion table for the S11AP message (step S204).
  • the DR control unit 156 transmits the U plane related parameters to the traffic management unit 142 (FIG. 11) (step S205), and ends the process.
  • FIG. 21 is a flowchart illustrating a processing example of DeNB-UE connection management by the DeNB-UE connection management control unit (DU control unit) 157.
  • DU control unit DeNB-UE connection management control unit
  • the process shown in FIG. 21 is started when the DU control unit 157 receives a context creation parameter from the S1 processing unit (step S211).
  • the DU control unit 157 creates a context for the UE. Then, the DU control unit 157 transmits the U plane related parameters to the traffic management unit 142 (FIG. 11) (step S213), and ends the process.
  • FIG. 22 is a flowchart showing a processing example of donor base station traffic management by the traffic management unit 142 (FIG. 11).
  • the traffic management unit 142 starts processing by receiving the U-plane related parameter from the DR control unit 157 (step S221).
  • the traffic management unit 142 creates a transfer conversion table for U-plane traffic (GTP-U) (step S222). Thereafter, the process ends.
  • FIG. 23 is a flowchart showing a processing example of donor base station traffic transfer by the traffic transfer unit.
  • the processing in FIG. 23 is started when the traffic transfer unit 143 receives U-plane traffic (step S231).
  • the traffic transfer unit 143 performs, for the received U-plane traffic, a header replacement process for data (packets) in the traffic based on the transfer conversion table created by the traffic management unit 142 (step S232). Then, the U plane traffic whose header has been replaced is transmitted (step S233). As a result, the U-plane traffic can be transferred to a desired destination.
  • FIG. 24 is a diagram illustrating a configuration example of the relay node 5.
  • FIG. 24 shows a hardware configuration example of the relay node 5.
  • the relay node 5 includes an L2 switch (L2SW) 202, a control unit 204, a baseband processing unit 203, and a wireless interface 201.
  • L2SW L2 switch
  • the relay node 5 includes an L2 switch (L2SW) 202, a control unit 204, a baseband processing unit 203, and a wireless interface 201.
  • L2SW L2 switch
  • the wireless interface 201 includes an antenna 206, a broadband amplifier 207, an analog-digital converter (A / D) and a digital-analog converter (D / A) 208, an input / output port (I / O) 209, and the like.
  • the radio interface 201 receives a radio signal from the UE 4, another relay node 5, and the donor base station 3 ⁇ / b> B located in the cell of the relay node 5 by the antenna 206, converts the radio signal to a digital signal by the A / D converter 208, The data is input to the L2 switch 202 via the input / output port 209.
  • the radio interface 201 performs D / A conversion on the signal from the L2 switch 202, amplifies the signal by the broadband amplifier 207, and radiates it from the antenna 206, whereby the radio signal is transmitted to the UE 4, the relay node 5, the donor base station in the cell. Can be sent to 3B.
  • the L2 switch 202 performs switching processing of signals transmitted between the control unit 204, the wireless interface 201, the baseband processing unit 203, and the transmission path interface 131.
  • the baseband processing unit 203 includes a processor such as the DSP 203A and a memory (MEM) 203B that is a storage medium (storage) in which a program and data executed by the DSP 203A are stored, and a program (DSP) stored in the memory 203B ( Firmware) is executed, baseband processing of the signal input from the L2 switch 202 is performed, and the processed signal is output to the L2 switch 202.
  • a processor such as the DSP 203A and a memory (MEM) 203B that is a storage medium (storage) in which a program and data executed by the DSP 203A are stored, and a program (DSP) stored in the memory 203B ( Firmware) is executed, baseband processing of the signal input from the L2 switch 202 is performed, and the processed signal is output to the L2 switch 202.
  • MEM memory
  • the control unit 204 includes a processor (microprocessor) such as a central processing unit (CPU) 204A, and a memory (MEM) 204B that is a storage medium (storage) in which programs and data executed by the CPU 204A are stored. Executes various programs such as message processing, call processing, connection management between devices, and monitoring processing by executing programs stored in the memory 204B.
  • the control unit 204 is connected to a USIM card (Universal Subscriber Identity Module Card) 205 in which the IMSI is stored.
  • USIM card Universal Subscriber Identity Module Card
  • FIG. 25 shows functional blocks realized by executing firmware by the DSP 203A of the baseband processing unit 203 shown in FIG.
  • FIG. 25 as a block that controls the terminal (UE) function of the relay node 5, a control unit communication unit 211 (211A) that controls communication processing with the control unit 133, a traffic monitoring and cell state monitoring unit 214 (214A), and A cell search control unit 215 that controls cell search, a secret setting / cancellation unit 216 (216A) that performs secret setting and setting cancellation of information, and a radio layer processing unit 217 (217A) that controls radio layer processing. It has been.
  • control unit communication unit 211 (211B), the traffic management (GTP management) unit 212, and the traffic transfer (GTP transfer processing) unit 213 are used as blocks that control the base station function and the S / PGW function of the relay node 5.
  • a traffic monitoring and cell state monitoring unit 214 (214A), a concealment setting / releasing unit 216 (216B), and a wireless layer processing unit 217 (217B) are provided.
  • FIG. 26 shows functional blocks realized by executing a program (software) by the CPU of the control unit shown in FIG.
  • the functional blocks realized by the control unit 204 can also be divided into a block group that manages a terminal (UE) function and a block group that manages a base station function and an S / PGW function.
  • UE terminal
  • S / PGW S / PGW
  • a connection management control unit (also referred to as a host control unit) 232 and an apparatus processing unit monitoring control unit 233 are provided.
  • the message processing unit 221 (221B), the call processing unit 227, the IP address allocation control unit 228, and the IP address pool 229 are grouped as blocks that control the base station function and the S / PGW function.
  • the message processing unit 221 (221A, 221B) includes a reception unit 223, a transmission unit 224, an analysis unit 225, and each protocol processing unit 226.
  • the blocks 221, 227, 230, 231 and 234, 232 and 235, and 233 connected by a double line are actually integrated functions.
  • FIGS. 25 and 26 can be realized using one or more general-purpose or dedicated hardware chips.
  • IP address group assignment processing by relay node 5 ⁇ IP address group assignment processing by relay node 5 will be described.
  • the processing of the S11 processing unit relating to the assignment of the IP address group shown in FIG. 16 is the same as the S11 processing unit in each protocol processing unit 226 (226B) in the base station function and S / PGW function of the relay node 5 shown in FIG. It is the same as the process. Therefore, the description is omitted.
  • FIG. 27 is a flowchart showing a processing example of the IP address assignment control unit 228 (FIG. 26) corresponding to the S11 processing unit of the relay node 5.
  • the IP address assignment control unit 228 is assigned from the RRC protocol processing unit (RRC processing unit) in each protocol processing unit 226B from the IP address group (donor base station 3B or upper relay node 5). IP address group) is received (step S251).
  • the IP address allocation control unit 228 determines the number of IP addresses to be allocated (IP address allocation number) in response to one IP address request.
  • the number of IP addresses can be determined by adopting an IP address determined in advance.
  • the IP address assignment control unit 228 generates a plurality of IP address groups by dividing the plurality of IP addresses forming the received IP address group by the number of IP address assignments (step S252).
  • the division number for the received IP address group may be set in advance, and the IP address assignment control unit 228 may generate a plurality of IP address groups from the IP address group by the division number.
  • the IP address assignment control unit 228 registers a plurality of IP address groups in the IP address pool 229 (IP address list 35A), and assigns an unassigned flag to all the registered IP addresses (step S253). At this time, the unassigned flag may be assigned for each IP address or may be assigned for each IP address group. In the present embodiment, “unassigned” is indicated when the flag is off, and “allocated” is indicated when the flag is on. However, the reverse may be possible.
  • steps S251 to S253 described above are processes at the time of initial setting of the IP address pool 229 accompanying the first attachment of the relay node 5.
  • step S253 ends, the IP address allocation control unit 228 transitions to a state of waiting for a message from the S11 processing unit.
  • step S254 the IP address allocation control unit 228 analyzes the message received from the S11 processing unit, and determines the message type (step S255). At this time, if the message type is an IP address group acquisition request, the process proceeds to step S256, and if the message type is an IP address group cancel, the process proceeds to step S258.
  • step S256 the IP address allocation control unit 228 acquires one of the IP addresses that are not allocated from the IP address pool 229. Subsequently, the IP address allocation control unit 228 sets a flag for the acquired IP address group to ON (allocated) (step S257). Thereafter, the process returns to step S254 to enter a standby state for the next message.
  • step S258 the IP address assignment control unit 228 sets off (unassigned) flags corresponding to all the IP addresses to be canceled. Thereafter, the process returns to step S257 to enter a standby state for the next message.
  • the relay node 5 can assign an IP address group to the other relay nodes 5 under its control.
  • the number of IP addresses included in each IP address group may be 1. In this case, only the IP address used by the subordinate relay node 5 may be transmitted to the subordinate relay node 5.
  • IP address reception processing Next, an IP address reception process for receiving an IP address from the donor base station 3B or the upper relay node 5 will be described.
  • the IP address reception process is performed by the RRC protocol processing unit (RRC processing unit) included in each protocol processing unit 226B in the relay node 5.
  • RRC processing unit included in each protocol processing unit 226B in the relay node 5.
  • FIG. 28 shows an example of IP address reception processing by the RRC processing unit.
  • the RRC processing unit when receiving the message, analyzes the message (step S261) and determines the message type (step S262).
  • step S263 If the message is “RRC Connection Reconfiguration”, the process proceeds to step S263, and if it is any other message, the process corresponding to the message is executed (step S271).
  • the RRC processing unit extracts an IP address group included in “RRC Connection Reconfiguration”.
  • a flag is assigned to one of the IP address groups (for example, the head IP address) included in “RRC ⁇ ConnectionIPReconfiguration”.
  • the IP address to which the flag is assigned indicates that the IP address group is determined to be the IP address to be used by the subordinate relay node 5 itself, which is determined by the assignment source of the IP address group (donor base station 3B or upper relay node 5). For this reason, the RRC processing unit sets the IP address to which the flag is assigned as the IP address of the relay node 5 itself.
  • the RRC processing unit transmits the remaining IP address to the IP address allocation control unit 228 (step S264).
  • the remaining IP addresses are used for assignment to other relay nodes 5 located below the relay node 5.
  • the RRC processing unit transfers the NAS message “Attach Accept” to the NAS protocol processing unit (included in each protocol processing unit 226B) (step S265).
  • the RRC processing unit performs processing related to other parameters included in “RRC Connection Reconfiguration” (step S266).
  • the RRC processing unit determines whether or not there is an error related to the message and message processing (step S267). If there is no error (N in S267), the RRC processing unit generates a normal response message “RRC Connection Reconfiguration Complete” (step S268) and attaches (stores) it to the transmission queue of the transmission unit 224 (step S269). .
  • step S270 the RRC processing unit generates an error response message “RRC Connection Reconfiguration Failure” (step S270) and stores it in the transmission queue (step S269). After step S269 ends, the process returns to step S261.
  • the relay node 5 sets one of the IP addresses received from the donor base station 3B or the relay node 5 which is a higher-level device as the IP address of the relay node 5 itself, and the rest is the subordinate relay node 5 This is sent to the IP address assignment control unit 228 to register it in the IP address pool 229 for assignment to the IP address pool.
  • FIG. 29 shows each protocol processing unit 226B (FIG. 29) of the relay node 5B when another relay node 5 (eg, the relay node 5A in FIG. 3) is attached to the relay node 5 (eg, the relay node 5B in FIG. 3).
  • S1AP protocol process part S1 process part
  • step S173A is provided instead of step S173 of FIG.
  • the S1 processing unit instructs the context construction by transmitting the relay node related parameters to the self-relay Relay connection management control unit (lower control unit) 234.
  • step S173A is the same as the processing in FIG. Also, the processing by the RRC processing unit is executed in accordance with the processing of step S175 in FIG. 29, but the content of the processing is the same as the processing of the RRC processing unit shown in FIG.
  • FIG. 29 also shows processing in the relay node 5B when the relay node 5A is attached.
  • the process in step S173A sends a related parameter of UE4 to the Relay-UE connection management control unit (RU control unit) 235 to instruct the context construction. Except for this point, the process at the time of UE attachment is the same as the process at the time of relay attachment.
  • RU control unit Relay-UE connection management control unit
  • FIG. 30 is a flowchart showing a processing example of the own-relay Relay connection management control unit (lower control unit) 234 (FIG. 26).
  • step S281 the lower-level control unit 234 receives a context creation parameter from the S1AP protocol processing unit (S1 processing unit) (step S281).
  • the lower control unit 234 creates a context for the lower relay node 5. Subsequently, the lower-level control unit 234 creates an S1AP message transfer conversion table (step S283). Further, the lower-level control unit 234 also creates a transfer conversion table for the S11AP message (step S284).
  • the lower control unit 234 transmits the U plane related parameters to the traffic management unit 212 (FIG. 25) (step S285), and ends the process.
  • FIG. 31 is a flowchart showing a processing example of Relay-UE connection management by the Relay-UE connection management control unit (RU control unit) 235 (FIG. 26).
  • RU control unit Relay-UE connection management control unit
  • the processing shown in FIG. 31 is started when the RU control unit 235 receives a context creation parameter from the S1AP protocol processing unit (S1 processing unit) (step S291).
  • the RU control unit 235 creates a context for the UE (related parameters for U plane management). Then, the RU control unit 235 transmits the U plane related parameters to the traffic management unit 212 (FIG. 25) (step S293), and ends the process.
  • FIG. 32 is a flowchart showing a processing example of the Relay-DeNB connection management control unit (RD control unit) 231 (FIG. 26).
  • RD control unit Relay-DeNB connection management control unit
  • an attach procedure (relay attach procedure) to the donor base station 3B in a format in which the relay node 5 is UE is executed.
  • the RD control unit 231 manages each radio bearer by recognizing the higher level apparatus as the donor base station 3B by relay attachment (step S302).
  • FIG. 33 is a flowchart showing a processing example of the self-upper relay connection management control unit (upper control unit) 232 (FIG. 26).
  • an attach procedure (relay attach procedure) to the higher-order relay node 5 in a format in which the relay node 5 is set to UE is executed.
  • the host controller 232 recognizes the relay device 5 as a relay node 5 by relay attachment, and manages each radio bearer (step S312).
  • FIG. 34 is a flowchart illustrating an example of processing performed by the traffic management unit 212 (FIG. 25).
  • the traffic management unit 212 starts the processing by receiving the U-plane related parameter from the lower control unit 234 (step S321).
  • the traffic management unit 212 creates a transfer conversion table for U-plane traffic (GTP-U) (step S322). Thereafter, the process ends.
  • FIG. 35 is a flowchart showing a processing example of relay node traffic transfer by the traffic transfer unit 213. The processing in FIG. 35 is started when the traffic transfer unit 213 receives U-plane traffic (step S331).
  • the traffic transfer unit 213 performs a header replacement process on the data (packet) in the traffic based on the transfer conversion table created by the traffic management unit 212 for the received U-plane traffic (step S332). Then, the U plane traffic whose header has been replaced is transmitted (step S333). As a result, the U-plane traffic can be transferred to a desired destination.
  • FIG. 36 is a flowchart showing a processing example of the MME 6 when the relay node 5 is attached. The process in FIG. 36 is started when the MME 6 receives the NAS message “Attach Request” (step S341).
  • the MME 6 takes out the device identification ID included in the “Attach Request” (step S342), and determines whether the device identification ID is IMSI (step S343). If the device identification ID is not IMSI (N in S343), it is recognized that the attached device is not the first attach, and the existing terminal attach process is executed (step S356).
  • step S343 an IMSI inquiry is transmitted to the HSS 9 (FIGS. 1 and 10) (step S344).
  • the MME 6 determines whether the device having the IMSI is the relay node 5 (step S346). For this determination, information (for example, device type information) indicating whether the device having the IMSI is the relay node 5 or the UE 4 included in the IMSI correspondence information can be used.
  • step S346 If the device having the IMSI is not the relay node 5 (N in S346), the process proceeds to step S356. On the other hand, when the device having the IMSI is the relay node 5 (Y in S346), the existing terminal authentication and security-related processing is executed (step S347). As a result, the processing relating to S5 to S10 shown in FIG. 3 is executed.
  • the MME 6 transmits a bearer setting request message “Create Session Request” to the donor base station 3B that relayed the “Attach Request” (step S348).
  • the MME 6 receives a response message “Create Session Response” including the IP address group from the donor base station 3B (Step S349), and assigns a flag to one of the received IP address groups, thereby changing the IP address group.
  • the IP address used by the receiving relay node 5 is clearly indicated (step S350).
  • the MME 6 puts the IP address group, “Attach Accept”, S1AP-ID (S1AP interface identifier), and GTP-TEID (S11AP interface identifier) in the S1AP message “Initial Context Setup Request”. It transmits to 3B (step S351).
  • the MME 6 receives a response message “Initial Context Setup Response” from the donor base station 3B (step S352), and further receives a response message “Attach Accept” of “Attach Accept” (step S353).
  • the MME 6 receives “S1 Setup Request” from the relay node 5 (step S354). Then, the MME 6 registers the relay node 5 in the device management table held by itself (step S355). Identification information (IP address, S1AP-ID and GTP-TEID) related to the relay node 5 and the like are registered in the device management table. Identification information related to the donor base station 3B is also registered in the device management table.
  • the MME 6 can recognize the donor base station 3B and the relay node 5. Further, when the information of the relay node 5 under the control of the donor base station 3B is included in the device management table, the MME 6 can also recognize the topology of the relay node 5 below the donor base station 3B.
  • relay node 5 (relay node 5B) under the control of the donor base station 3B and the relay node 5A under the control of the relay node 5B have the same configuration.
  • the relay node 5 under the control of another relay node 5 has a configuration for having the relay node 5 under its own control.
  • the relay node 5 that is located at the end and is not assigned an IP address to be assigned from the upper relay node 5 to the subordinate relay node 5 (For example, a configuration related to S11 interface setting for receiving an IP address assignment instruction from the MME 6).
  • the upper relay node 5 receives a notification that the lower relay node 5 is a relay node 5 that cannot be subordinate to the lower relay node 5.
  • a single IP address may be assigned.
  • the S11AP link setting between relay nodes may be omitted.
  • Wireless network eUTRAN 2 ... Core network 3A ... Base station (eNodeB) 3B ... Donor-eNodeB (base station) 4 ... Wireless terminal (UE) 5.
  • Relay node (RN) (relay device) 6 ... MME (high-level device, control device) 7 ... SGW 8 ... PGW 9 ... HSS 31 ... Donor base station proxy base station function 32 ... Donor base station proxy S / PGW function 33 ... Donor base station S / PGW function 35, 35A ... IP address list 51 ... Relay node base station function 52 ... Relay node UE function 53 ... Relay node S / PGW function 54 ... Relay node proxy S / PGW functions 164, 226 ... Each protocol processing unit 153 228... IP address allocation control unit 154, 229... IP address pool

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention se rapporte à un procédé adapté pour attribuer une adresse IP à un dispositif relais. L'attribution de cette adresse IP a pour but de relayer une interface sans fil entre un terminal sans fil et une station de base pour fournir un service de téléphonie cellulaire. D'autre part, le dispositif relais est apte à terminer un signal de commande entre la station de base et le terminal sans fil. Le procédé selon l'invention comprend les étapes suivantes : la station de base attribue une pluralité d'adresses IP à un premier dispositif relais placé sous le contrôle de la station de base ; et le premier dispositif relais attribue, à un second dispositif relais placé sous le contrôle du premier dispositif relais, au moins l'une des adresses IP attribuées par la station de base.
PCT/JP2011/054401 2011-02-25 2011-02-25 Procédé pour attribuer une adresse ip à un dispositif relais WO2012114527A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2011/054401 WO2012114527A1 (fr) 2011-02-25 2011-02-25 Procédé pour attribuer une adresse ip à un dispositif relais

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2011/054401 WO2012114527A1 (fr) 2011-02-25 2011-02-25 Procédé pour attribuer une adresse ip à un dispositif relais

Publications (1)

Publication Number Publication Date
WO2012114527A1 true WO2012114527A1 (fr) 2012-08-30

Family

ID=46720341

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2011/054401 WO2012114527A1 (fr) 2011-02-25 2011-02-25 Procédé pour attribuer une adresse ip à un dispositif relais

Country Status (1)

Country Link
WO (1) WO2012114527A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110475267A (zh) * 2018-05-11 2019-11-19 华为技术有限公司 一种配置方法、数据传输方法和装置
JP2020202415A (ja) * 2019-06-05 2020-12-17 日本無線株式会社 無線通信ユニット及びそれを用いた無線ネットワークシステム
US11239898B1 (en) * 2019-11-19 2022-02-01 T-Mobile Innovations Llc Relaying data to multiple access points

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2004147344A (ja) * 2003-12-15 2004-05-20 Toshiba Corp 通信装置
JP2004146988A (ja) * 2002-10-23 2004-05-20 Sony Corp 通信処理装置、およびアドレス設定方法、並びにコンピュータ・プログラム
JP2006191570A (ja) * 2004-12-30 2006-07-20 Lg Electronics Inc 移動通信網に接続できない無線端末機へのｉｐ割り当て方法及び該方法を実現できる移動通信端末機

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2004146988A (ja) * 2002-10-23 2004-05-20 Sony Corp 通信処理装置、およびアドレス設定方法、並びにコンピュータ・プログラム
JP2004147344A (ja) * 2003-12-15 2004-05-20 Toshiba Corp 通信装置
JP2006191570A (ja) * 2004-12-30 2006-07-20 Lg Electronics Inc 移動通信網に接続できない無線端末機へのｉｐ割り当て方法及び該方法を実現できる移動通信端末機

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110475267A (zh) * 2018-05-11 2019-11-19 华为技术有限公司 一种配置方法、数据传输方法和装置
CN110475267B (zh) * 2018-05-11 2021-09-17 华为技术有限公司 一种配置方法、数据传输方法和装置
US11510131B2 (en) 2018-05-11 2022-11-22 Huawei Technologies Co., Ltd. Configuration method, data transmission method, and apparatus
JP2020202415A (ja) * 2019-06-05 2020-12-17 日本無線株式会社 無線通信ユニット及びそれを用いた無線ネットワークシステム
JP7341735B2 (ja) 2019-06-05 2023-09-11 日本無線株式会社 無線通信ユニット及びそれを用いた無線ネットワークシステム
US11239898B1 (en) * 2019-11-19 2022-02-01 T-Mobile Innovations Llc Relaying data to multiple access points

Similar Documents

Publication Publication Date Title
JP5088091B2 (ja) 基地局装置、通信方法及び移動通信システム
KR102252271B1 (ko) 프런트홀 인터페이스 수립 방법, 사용자 장치에 대한 액세스 수행 방법, 사용자 장치에 대한 핸드오버 수행 방법 및 장치, 데이터 전달 방법, 사용자 장치 및 기지국
US9124510B2 (en) Configuring relay cell identities in cellular networks
JP6785346B2 (ja) データ・オフロードのためのパスを確立する方法及び装置
CN110048758B (zh) 节点和通信方法
JP7483898B2 (ja) 通信方法及び装置
JP7455984B2 (ja) アクセスバックホール統合ネットワーク内のドナー間トポロジ適合
JP2022550751A (ja) ルーティングおよびベアラマッピング構成のための方法およびデバイス
US20230239940A1 (en) Data transmission method and apparatus
JP2019511154A (ja) セキュリティパラメータ伝送方法及び関係するデバイス
CN113973399A (zh) 报文转发方法、装置及系统
JP5878134B2 (ja) 上位基地局、下位基地局、および無線通信システム
CN110662297B (zh) 一种信令处理方法、节点及装置
WO2012114527A1 (fr) Procédé pour attribuer une adresse ip à un dispositif relais
US20220248479A1 (en) Data Transmission Method and Apparatus
DK3262864T3 (en) Establishing an X2 connection using virtual terminals
JP7254093B2 (ja) システム、制御プレーン機器、ユーザプレーン機器、及びプログラム
CN112469077B (zh) 一种业务数据包转发的方法及装置
US10873874B2 (en) Base station, radio relay station, and communication method for cancelling a connection to a base station during an overload condition
CN116326168A (zh) 无线通信中的信令交换方案
RU2806798C1 (ru) Способ и устройство связи
RU2780823C2 (ru) Устройство и способ обработки беспроводной связи по транзитному соединению
EP4216594A1 (fr) Procédé de commande de communication
US10873890B2 (en) Base station, radio relay station, communication method for cancelling a connection to a base station during an overload condition
EP4272511A1 (fr) Gestion de connexions à de multiples unités centralisées

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: 11859341

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11859341

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP