WO2012118449A2 - Dispositifs de communication et procédés de communication - Google Patents

Dispositifs de communication et procédés de communication Download PDF

Info

Publication number
WO2012118449A2
WO2012118449A2 PCT/SG2012/000068 SG2012000068W WO2012118449A2 WO 2012118449 A2 WO2012118449 A2 WO 2012118449A2 SG 2012000068 W SG2012000068 W SG 2012000068W WO 2012118449 A2 WO2012118449 A2 WO 2012118449A2
Authority
WO
WIPO (PCT)
Prior art keywords
station
flow
local forwarding
infrastructure
dsa
Prior art date
Application number
PCT/SG2012/000068
Other languages
English (en)
Other versions
WO2012118449A3 (fr
Inventor
Shoukang ZHENG
Haiguang Wang
Choong Hock MAR
Jaya Shankar S/O Pathmasuntharam
Anh Tuan Hoang
Wai Leong YEOW
Original Assignee
Agency For Science, Technology And Research
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 Agency For Science, Technology And Research filed Critical Agency For Science, Technology And Research
Publication of WO2012118449A2 publication Critical patent/WO2012118449A2/fr
Publication of WO2012118449A3 publication Critical patent/WO2012118449A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/22—Communication route or path selection, e.g. power-based or shortest path routing using selective relaying for reaching a BTS [Base Transceiver Station] or an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/38—Flow based routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/23—Manipulation of direct-mode connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/16—Multipoint routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/04—Reselecting a cell layer in multi-layered cells
    • 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

  • Embodiments of the invention generally relate to a communication terminal and a method for performing communication.
  • the IEEE 802.16 ⁇ System Requirements Document specifies a requirement for High Reliability (HR) network.
  • HR High Reliability
  • one of the requirements is for the mobile stations (HR-MSs) to communicate directly with each other in the event of network failure.
  • the HR-MS to HR-MS direct communications scenario could for example occur in the event of a disaster where the backbone network is destroyed.
  • the rescue teams e.g. firemen and police officers
  • an infrastructure station for performing direct local forwarding in a cellular mobile communication system which includes a core network.
  • the infrastructure station includes a transceiver, a detector, a binder, and a forwarder.
  • the detector is configured to detect a local forwarding opportunity between at least two mobile stations under the control of the infrastructure station based on received transmissions.
  • the binder is configured to bind an uplink flow and a downlink flow together into a data flow route between the at least two mobile stations.
  • the uplink flow and the downlink flow are identified by uniquely identifiable station flow identifiers.
  • station flow identifiers are unique service flow identifiers, a composition of at least a uniquely identifiable station identifier and a uniquely identifiable flow identifier or connection identifiers.
  • the forwarder is configured to forward received data from the at least two mobile stations by employing a station flow identifier provided in received data transmissions to determine the data route flow.
  • a method for performing direct local forwarding in a cellular mobile communication system which includes a core network.
  • the method includes detecting a local forwarding opportunity between at least two mobile stations under the control of an infrastructure station based on received transmissions, binding an uplink flow and a downlink flow together into a data flow route between the at least two mobile stations, and forwarding received data from the at least two mobile stations by employing the station flow identifier provided in received data transmissions to determine the data route flow.
  • the uplink flow and the downlink flow are identified by uniquely identifiable station flow identifiers. These station flow identifiers are unique service flow identifiers, a composition of at least a uniquely identifiable station identifier and a uniquely identifiable flow identifier, or connection identifiers.
  • FIG. 1 shows communication flow arrangements according to embodiments.
  • FIG. 2 shows a flow diagram according to an embodiment.
  • FIGs. 3-4 show message flow diagrams according to embodiments.
  • FIGs. 5-6 show communication flow arrangements according to embodiments.
  • FIG. 7 shows a flow diagram according to an embodiment.
  • FIG. 8 shows a communication flow arrangement according to an embodiment.
  • FIGs. 9-10 show message flow diagrams according to embodiments.
  • FIG. 1 shows communication flow arrangements according to embodiments.
  • FIG. 1A shows paths for a 802.16m network without local forwarding
  • FIG. IB shows paths for a 802.16 ⁇ network with local forwarding.
  • the IEEE 802.16 standard family specifies a Media Access Control (MAC) and Physical layer communication protocols for cellular-based wireless communications.
  • the IEEE 802.16 working group has created a new task group, IEEE 802.16 ⁇ , to investigate a few new features, of which local forwarding is desired. It is desired that a high reliability (HR) network, such as for example 802.16 ⁇ , be capable of providing local forwarding.
  • HR high reliability
  • Local forwarding is a mechanism that allows one high reliability mobile station (HR-MS) to communicate to one or more HR-MSs via an infrastructure station without going through a backhaul.
  • Infrastructure stations include, for example, high reliability base stations (HR-BS) and high reliability relay stations (HR-RS).
  • HR-BS high reliability base stations
  • HR-RS high reliability relay stations
  • a HR- Network be capable of providing optimized MAC protocols for unicast and multicast transmissions to support applications of two-way communications services among a group of HR-MSs. For instance, Push to Talk (PTT) services may be served on such transmission networks and provide audio, video, still images, formatted text, non- formatted text, and file transfer applications.
  • PTT Push to Talk
  • FIG. 1 Two HR-MSs 9, 11 start communication via infrastructure stations HR-RS 7 and HR-BS 5 in FIG. 1A and via HR-RS 7 performing local forwarding in FIG. IB.
  • solid lines indicate links between the nodes 5, 7, 9, 11 and the dash lines 1, 2, 3, 4 indicate the communication data paths.
  • the bandwidth of the downlink and uplink from HR-BS 5 to HR- RS 7 for the communication between HR-MS 9 and HR-MS 11 could be conserved to improve the efficiency as compared to FIG. 1A.
  • communication paths 2, 3, 4 in FIG. 1A are collapsed into communication paths 2, 3 in FIG. IB.
  • communication paths 2, 3, 4, as shown FIG. 1A may be further collapsed into just communication path 2.
  • FIG. 2 shows a flow diagram according to an embodiment.
  • a method for performing direct local forwarding in a cellular mobile communication system which includes a core network is provided.
  • the method for instance may implemented with an infrastructure station for performing direct local forwarding in a cellular mobile communication system which includes a core network.
  • the infrastructure station may include a transceiver, a detector, a binder, and a forwarder.
  • the detector is configured to detect 13 a local forwarding opportunity between at least two mobile stations under the control of the infrastructure station based on received transmissions.
  • the binder is configured to bind 15 an uplink flow and a downlink flow together into a data flow route between the at least two mobile stations.
  • the uplink flow and the downlink flow are identified by uniquely identifiable station flow identifiers.
  • station flow identifiers are unique service flow identifiers (SFIDs), a composition of at least a uniquely identifiable station identifier (STID) and a uniquely identifiable flow identifier (FID) or connection identifiers (CIDs).
  • SFIDs unique service flow identifiers
  • TID uniquely identifiable station identifier
  • FID uniquely identifiable flow identifier
  • CIDs connection identifiers
  • FIGs. 3-4 show message flow diagrams according to various embodiments.
  • both HR-MSs 9, 11 are associated with the same HR-RS 7.
  • control messages and data flow of a BS-initiated local forwarding scheme is shown.
  • HR-BS 5 is capable of obtaining and maintaining a table of HR-MS unique identifications (IDs).
  • IDs Such uniquely identifiable station identifiers may, for example, be media access control (MAC) addresses, mobile numbers and/or IP addresses.
  • HR-BS 5 is further capable of obtaining and maintaining in the table uniquely identifiable station flow IDs.
  • a station flow ID may be a SFID, a composition of a STID and a FID or a connection identifier (CID).
  • HR- MSs 9, 11 are assigned IP addresses and station IDs (STIDs) during registration by HR- RS 7 so that HR-BS 5 can obtain the information of mobile station (MS) unique IDs, such as IP addresses or MAC address, and STIDs through the message from HR-RS 7.
  • MS mobile station
  • STIDs through the message from HR-RS 7.
  • HR-MS 9 starts an uplink connection setup request with DSA REQ/DSC REQ control messages for a flow ID (FID)
  • the source and destination IP addresses can be provided in the DSA_REQ/DSC_REQ control messages so that HR-BS 5 can obtain the information to setup the table and the binding if local forwarding is applicable. If the uplink or downlink connection setup after handover is known by HR-BS 5, it should be able to setup the table and the binding as well.
  • the detector for detecting a local forwarding opportunity between at least two mobile stations under the control of the infrastructure station based on received transmissions is configured to receive a DSC/DSA-REQ transmission, decode a source and a destination encoded in the transmission, detect that the source and the destination are both under the control of the base station, and respond to the DSC/DSA-REQ and initiate a new DSC/DSA-REQ for local forwarding.
  • HR-MS 9 sends DSA-REQ 19 to HR-RS 7.
  • HR-RS 7 sends control messages to core networks (ASN) to setup data path (not shown), and sends control messages DSC-REQ 21 (or DSA-REQ) to HR-BS 5 to complete the setup for the uplink flow of HR-MS 9 after HR-RS 7 receives DSA-REQ 19 from HR-MS 9.
  • HR-BS 5 receives DSC-REQ 21 from HR-RS 7
  • HR-BS 5 decodes the information of the destination, HR-MS 11, from DSC-REQ 21 message and detects 23 both HR-MS 9 and HR-MS 11 are under the control of the same relay station, namely HR-RS 7.
  • HR-BS 5 sends DSC-RSP 25 to HR-RS 7 to indicate that it optionally requests to setup the uplink flow from HR-RS 7 to HR-BS 5 itself.
  • HR-RS 7 also indicates to HR- BS 5 that it can complete the setup of uplink flow from HR-RS 7 to HR-BS 5 if requested by HR-BS 5, replying with DSA-ACK 27.
  • HR-BS 5 the proceeds to send control messages DSA-REQ 29 (or DSC-REQ) to HR-RS 7.
  • DSA-REQ 31, or other control messages can be used to indicate to HR-RS 7 that local forwarding is feasible for the unicast flow.
  • HR-RS 7 sends control message DSA-RSP 31 to the HR-BS 5 and HR-BS 5 replies with DSA-ACK 33.
  • the above control message sent to HR-RS 7 can be used to indicate that there will be local forwarding so that HR-RS 7 can bind two flows together. If HR-RS 7 is permitted to do local forwarding after admission control, HR-RS 7 sends DSA-REQ 35 to HR-MS 11 to indicate a downlink FID will be setup by HR-RS 7. This is followed by the control messages of DSA-RSP 37 from HR-MS 11 to HR-RS 7 and of DSA-ACK 39 from HR- RS 7 to HR-MS 11 to complete the downlink flow setup.
  • HR-RS 7 sends DSA-RSP 43 to HR-MS 9 and HR-MS 9 replies with DSA-ACK 45 to HR-RS 7 to complete the setup of the uplink flow and HR-RS 7 assigns a FID for HR-MS 9.
  • HR-RS 7 then proceeds to bind the uplink FID from HR-MS 9 to HR-RS 7 and the downlink FID from RS to MS 11 together so that HR-RS 7 is capable of routing data flow from HR-MS 9 to HR-MS 11 without going through HR-BS 5.
  • HR-MS 9 may send data with the assigned FID to HR-RS 7.
  • HR-RS 7 forwards the received data 49 from HR-MS 9 to HR-MS 11 by employing the newly created binding and may also send data 51, if required, from HR-MS 9 to HR- BS 5.
  • HR-MS 9 sends DSD-REQ 53 to HR-RS 7.
  • HR-RS 7 replies with DSD- RSP 55.
  • HR-MS 9 sends DSD-ACK 57 back to HR-RS 7.
  • HR-RS 7 continues by sending DSD-REQ 59 to HR-BS 5, requesting the release of uplink flow and indicating the end of the connection between HR-MS 9 and HR-MS 11.
  • HR-BS 5 replies with DSD- RSP 61 and HR-RS 5 sends DSD-ACK 63 to HR-BS 5.
  • HR-BS 5 deletes the binding of two flows.
  • HR-RS 5 further sends DSD-REQ 65 to HR-MS 11, indicating the end of the connection between HR-MS 9 and HR-MS 11.
  • HR-MS 11 replies with DSD-RSP 67 and HR-RS 5 sends DSD-ACK 69 back to HR-MS 1 1.
  • HR-RS 5 finishes by removing the binding of the uplink flow from HR-MS 9 to HR-RS 7 and the downlink flow from HR- RS 5 to HR-MS 1 1.
  • HR-RS 7 is capable of obtaining and maintaining a table of HR-MS unique identifications (IDs).
  • IDs may, for example, be media access control (MAC) addresses, mobile numbers and/or IP addresses.
  • HR-RS 7 is further capable of obtaining and maintaining in the table uniquely identifiable station flow IDs.
  • a station flow ID may be a SFID, a composition of a STID and a FID or a connection identifier (CID).
  • HR-MS 9 starts an uplink connection setup request with DSA REQ/DSC REQ control messages for a flow ID (FID)
  • the source and destination IP addresses can be provided in the DSA REQ/DSC REQ control messages so that HR-RS 7 can obtain the information to setup the table and the binding if local forwarding is applicable. If the uplink or downlink connection setup after handover is known by HR-RS 7, it should be able to setup the table and the binding as well.
  • the detector for detecting a local forwarding opportunity between at least two mobile stations under the control of the infrastructure station based on received transmissions is configured to receive a DSC/DSA-REQ transmission, decode a source and a destination encoded in the transmission, detect that the source and the destination are both under the control of the relay station, transmit a control message to the core network to setup a data path, a new DSC/DSA-REQ for local forwarding, and a query whether to setup an uplink form the relay station to the base station, and receive a DSC/DSA-RSP and initiate a new DSC/DSA-REQ for local forwarding.
  • HR-MS 9 sends DSA-REQ 19 to HR-RS 7.
  • HR-RS 7 decodes the information of the destination HR-MS 11 from DSA- REQ 19 message and detects that both HR-MS 9 and HR-MS 11 are under the control of the same relay station, namely HR-RS 7.
  • HR-RS 7 sends control messages to core networks (ASN) to setup a data path (not shown) and also sends a DSA-REQ 21 (or DSC-REQ) to HR-BS 5, requesting to perform local forwarding for HR-MS 9 and querying HR-BS 5 whether to setup the uplink from HR-RS 7 to HR-BS 5 for the flow.
  • ASN core networks
  • DSA-REQ 21 or DSC-REQ
  • HR-BS 5 determines whether to allow HR-RS 7 to do local forwarding for HR-MS 9.
  • HR-BS 5 confirms HR-RS 7 can perform local forwarding
  • HR-BS 5 by replying with DSA-RSP 25 which also indicates whether HR- RS 7 should setup an uplink flow for HR-BS 5.
  • HR-RS 7 responds with DSA-ACK 27. Once HR-RS 7 has been instructed to perform local forwarding, setting up RS-initiated local forwarding will proceed similar to the BS-initiated local forwarding described with reference to FIG. 3.
  • HR-MS 9 sends DSD-REQ 75 to HR-RS 7.
  • HR-RS 7 replies with DSD- RSP 77.
  • HR-MS 9 sends DSD-ACK 79 back to HR-RS 7.
  • HR-RS 5 continues by sending DSD-REQ 81 to HR-MS 11, indicating the end of the connection between HR- MS 9 and HR-MS 11.
  • HR-MS 1 1 replies with DSD-RSP 83 and HR-RS 5 sends DSD- ACK 85 back to HR-MS 11.
  • HR-RS 7 continues by sending DSD-REQ 87 to HR-BS 5, requesting the release of uplink flow and indicating the end of the connection between HR-MS 9 and HR-MS 11.
  • HR-BS 5 replies with DSD-RSP 89 and HR-RS 5 sends DSD-ACK 91 to HR-BS 5.
  • HR-BS 5 deletes the binding of two flows.
  • HR-RS 5 finishes by removing the binding of the uplink flow from HR-MS 9 to HR-RS 7 and the downlink flow from HR- RS 5 to HR-MS 11.
  • the above methods can be extended to multi-hop relay networks, for example an 802.16j network, such that an infrastructure station is configured to forward data from more than one hop away.
  • the source MS will send a DSA-REQ to a BS.
  • the BS will then send a DSA-REQ to the nodes along the path until access is made to a RS for admission control for the source MS. If it is admitted by all the intermediate RSs and the access RS along the path, the access RS replies with a DSA-RSP to the BS.
  • the BS then sends DSA-RSP to the source MS, assigning a flow ID to it, and meanwhile sends DSA- ACK to all the RSs along the path to the source MS.
  • the BS can detect this flow can be done by local forwarding by sending DSA-REQ to the access RS for downlink admission control of the destination MS and also sending DSA-REQ to establish the service flow between the access RS and the destination MS.
  • the binding of the two flows for local forwarding is performed at the common upstream RS rather than the access RS, unless the access RS is the common upstream RS.
  • the binding can be instructed by the BS through a DSA-REQ control messages to the common upstream RS that will do local forwarding.
  • the BS will send a DSA-REQ to the access RS of the destination MS to check whether it can be admitted, and thus expect the access RS to send a DSA-RSP to itself so that it can reply with a DSA-ACK to complete the service flow setup between BS and access RS.
  • the DSA-REQ should be issued by the BS to the destination MS to establish the flow between the access RS and the destination MS.
  • FIGs. 5-6 show communication flow arrangements according to embodiments.
  • Scenario may arise where data packets of a HR-MS 95 need to be multicasted to a group of HR-MSs 97 under the control of the same HR-RS 7.
  • a PTT (Push-To-Talk) service is a possible application of such a scenario.
  • the data flow for the normal operation of a PTT service is inefficient because of repeated data retransmissions from the HR-RS to PTT server 99 and back again to HR-RS 7.
  • a MAC protocol optimized for PTT service is provided by allowing local forwarding of multicast packets as shown in FIGs. 5-6 such that an infrastructure station further includes a multicaster configured to maintain a table that stores source and destination address pairs for a plurality of downlink connections in a detected multicast packet.
  • the binder is configured to bind a downlink multicast flow, with an uplink unicast flow, and the station flow IDs are service flow IDs, a composition of at least a uniquely identifiable multicast group identifier and a uniquely identifiable flow identifier, or connection IDs .
  • a PTT group has a source component HR-MS 95 with an uplink unicast connection 1 provided by HR-BS 5, and a multicast group of k destination MSs HR-MS 97 with a downlink multicast connection 2 provided by HR-BS 5.
  • HR-BS 5 can obtain and maintain a table of HR-MS unique IDs and station flow IDs.
  • HR-BS 5 is the coordinator of the local forwarding. Once the service has been created, any changes are accomplished using a DSC-REQ. Once the service is no more needed, it can be deleted using a DSD-REQ.
  • the formation of the PTT group, the request and grant of Right-to-Speak in the PTT group, and any other control signaling between the PTT server and group may be handled by upper layer communications.
  • FIG. 7 shows a flow diagram according to an embodiment.
  • HR-BS 5 creates a downlink unicast connection to HR-MS 95 using a DSA message and transmitting the right-to-transmit 101 packet.
  • HR-MS 95 requests an uplink unicast connection and specifies the source and destination IP address, namely the PTT server, in the MS initiated DSA-REQ 103 message.
  • HR-BS 5 creates a table that stores 107 the source and destination IP addresses pair for each uplink connection.
  • a PTT flag may be included in the DSA-REQ message for the uplink connection so that only the uplink connection that is created as part of the PTT service is stored in the table. After receiving the first data packet from the PTT server.
  • HR-BS 5 identifies 119 that the packet is a multicast packet, specifically a multicast destination with IP addresses.
  • HR-BS 5 uses the source IP address of the IP packet to search for a match of the destination IP address in the table that contains the active uplink connections. The matched IP address is actually the IP address of the PTT server. Further information such as service class may be used to refine the search. If a match is found, it determines whether local forwarding is possible. If local forwarding is possible, the method proceeds in the same fashion as the BS and RS initiated forwarding procedure for unicast local forwarding as described with the following differences.
  • a DSA-REQ 123 for the multicast connection is used.
  • the DSA-REQ 123 for the multicast transmission must include: the Multicast Group ID and the FID which are together used to identify the connection.
  • multiple packets DSA-REQs have to be sent to each downlink multicast member. Multiple local forwarding bindings may occur. This is because the multicast members may form subgroups that are dispersed over a few controlling RSs.
  • HR-MS 9, 11 or HR-RS 7 may trigger a handover process.
  • Both BS-initiated and RS-initiated methods consider the re-establishment of the connection to handle the handover process.
  • HR-MS 9 or HR-RS 7 will be triggered and context transfer will be done between serving station and target station.
  • the serving HR-RS send control messages to target BS (TBS) or target RS (TRS) (defined as T-ABS/T-ARS in 802.16m) that will serve the HR-MS requiring this handover.
  • target BS TBS
  • TRS target RS
  • T-ABS/T-ARS target RS
  • the binding of the flows of uplink and downlink station flow IDs should be detached in serving HR-RS and HR-BS if the HR-BS also keeps the related information.
  • the uplink flow from TRS to its corresponding BS should be established in addition to the uplink flow of the source HR-MS 9 to TRS, or the uplink flow of the source HR-MS 9 to TBS if there is no RS between TBS and HR-MS.
  • SRS should remove the uplink flow for this source HR-MS 9. If there is no common upstream HR-RS between SRS and TRS, SRS sends out DSA-REQ to its controlling HR-BS (SBS) to establish the downlink flow from SBS to this SRS for the incoming flow from the source HR-MS 9 that are handover to be under the control of TRS/TBS.
  • SBS controlling HR-BS
  • SRS should send out a DSA-REQ to the common upstream HR-RS to establish the downlink flow from this common upstream HR-RS to this SRS for the incoming flow from the source HR-MS 1, which are handed over to be under the control of TRS/TBS.
  • the binding will be transferred to the common upstream RS, which will replace SRS to perform the local forwarding, and the uplink flow of HR-MS 1 is established between HR-MS 1 and this common upstream HR-RS, after the uplink flow is also established between the access RS and the common upstream HR-RS if there are a few hops between them.
  • the binding at serving HR-RS should be removed.
  • the uplink flow from SRS to its corresponding SBS should be established if it hasn't been setup by the serving SRS for the case of no common upstream RS between TRS and SRS. If there is a common upstream RS between TRS and SRS, the uplink flow should be established between this common upstream RS and SRS. SRS should remove the downlink flow for this destination HR-MS 11. After handover to TBS/TRS, the downlink flow should be setup for this destination HR-MS 11 to receive the data from the source HR-MS 9. If there is no common upstream RS between SRS and TRS, the downlink flow is established between TBS and TRS.
  • the downlink flow is established between the common upstream RS and TRS.
  • the binding will be transferred to this common upstream RS, which will replace SRS to perform the local forwarding.
  • both BS-initiated and RS-initiated methods consider the re-establishment of the connection during the handover process.
  • HR-MS When handover starts, either HR-MS or HR-RS will be triggered.
  • the HR-RS controlling the HR-MS without handover informs the RS/BS serving the other HR-MS such that it will handle this handover.
  • the binding of the flows of uplink and downlink station flow identifier should be established in TRS if both the source HR-MS 9 and destination HR-MS 11 are under the control of same HR-RS, or in the common upstream HR-RS between the source HR-MS 9 and the destination HR-MS 11.
  • SBS/SRS should remove the uplink flow for this source HR-MS 9 and the uplink flow from TRS to its corresponding BS (TBS) should be established if required by BS in addition to the uplink flow from the source HR-MS 9 to TRS.
  • TRS should bind the uplink station flow identifier of HR-MS 9 and downlink station flow identifier of HR-MS 11 together and local forwarding will be done by TRS if there is no common upstream RS between the source HR-MS 1 and the destination HR- MS2. Otherwise the common upstream RS between the source HR-MS 9 and the destination HR-MS 11 should bind the uplink station flow identifier of HR-MS 9 and downlink station flow identifier of HR-MS 11 together and perform the local forwarding for HR-MS 9 and HR-MS 11.
  • FIG. 8 shows a communication flow arrangement according to an embodiment.
  • the source HR-MS 95 handover procedure is similar to the unicast cases described since mainly the uplink unicast component is affected.
  • the multicast member HR-MS 97 is handed over to a TRS that is also controlling a subgroup of multicast HR-MS 97 as shown in FIG. 8.
  • HR-MS 97 or HR-BS 5 can initiate the DSA messaging to connect to the downlink multicast service.
  • the downlink service will be the Enhanced Multicast Broadcasting Services (E-MBS).
  • E-MBS Enhanced Multicast Broadcasting Services
  • the DSA messaging for E-MBS is used instead. Note that in this case, the existing local forwarding binding is not affected.
  • the multicast member HR-MS 97 is handed over to a TRS with no existing sub-group.
  • the multicast member HR- MS 97 is in the 1st subgroup where there is only a single member.
  • the unbinding procedure is performed if local forwarding exists in the original 1st sub-group.
  • the handover to TRS is done, the same DSA messaging procedure is performed.
  • the BS needs to discover whether a local forwarding opportunity exists by searching for the common upstream RS that connects between HR-MS 95 and the handover HR-MS 97. The procedure of binding then follows as described.
  • an infrastructure station may include a handover module configured to a station handover where one of the at least two mobile stations moves out of local forwarding control of the infrastructure station and removes the data flow thereto. Further, the handover module may be configured to detect a station handover where the at least two mobile stations remain under local forwarding control of the infrastructure station and re-establish local forwarding after the station handover.
  • LF opportunity may be detected by HR-infrastructure station or other manner (e.g. ASN-GW).
  • ASN-GW Local forwarding
  • the following method and protocol specifies control messages for 802.16m but when the detection method and LF protocol is applied to 802.16e, AAI control messages given in the following description for 802.16m shall be replaced by the corresponding messages in 802.16e. In this case the proposed control messages should be renamed accordingly.
  • AAI-LFA-REQ is renamed as LFA-REQ.
  • CIDs in 802.16e are used as the station flow identifiers.
  • HR-MS obtains the identification in the related domain (e.g. IPv4 or IPv6 address).
  • HR infrastructure station e.g. as DHCP relay
  • HR infrastructure station is able to obtain this information to maintain a table of one unique STID and one or multiple identifications in the related domain (e.g. IPv4 address) for the HR-MSs.
  • the identification for HR-MS can be obtained (e.g. IPv4/IPv6 address or Ethernet MAC address).
  • HR infrastructure station is able to maintain a table of one unique STID and one or multiple identifications in the related domain for the HR-MSs.
  • the HR infrastructure station can negotiate with HR-BS during HR-RS network entry to enforce the compulsory presence of identifications for the concerned domain (e.g. IPv4).
  • ASN-GW may be able to detect the LF opportunity if the association of the identifications in a specific domain (such as IPv4 or IPv6) and SFIDs (or indirectly STIDs of both communicating HR-MSs) can be recognized by ASN-GW. In this case, even there is no data flow going to the destination HR-MS before the detection of LF opportunity, ASN-GW is able to determine whether there is an opportunity of LF for two communicating HR-MSs after the data traffic has been forwarded by ASN-GW once through the downlink to the destination HR-MS.
  • a specific domain such as IPv4 or IPv6
  • SFIDs or indirectly STIDs of both communicating HR-MSs
  • HR infrastructure station may implement some data path functions to facilitate the detection of LF opportunity, similar to ASN-GW detection. Even if there is no data flow going to the destination HR-MS before the detection of LF opportunity, a HR infrastructure station may be able to determine whether there is an opportunity of LF for two communicating HR-MSs after the data traffic has been forwarded by HR infrastructure station once through the downlink to the destination HR-MS.
  • HR infrastructure station (either HR-BS or HR-RS) shall detect the LF. In this case, the above methods without ASN-GW engaging may be used to determine LF opportunity.
  • the capability of LF is negotiated and may be enabled during HR-RS network entry.
  • HR-RS sends control message (e.g. AAI-SBC-REQ for 802.16m) to HR-BS, indicating that whether it can determine LF opportunity and/or perform LF.
  • HR-BS replies with control message (e.g. AAI-SBC-RSP) to indicate which shall detect LF opportunity and perform LF.
  • control message e.g. AAI-SBC-RSP
  • the AAI-SBC-REQ shall include TLVs within the set of Local Forwarding Supported that indicates the HR-BS or HR-RS capabilities, whether local forwarding detection is supported and local forwarding is supported.
  • HR-infrastructure station When HR-infrastructure station detects the LF opportunity, it may send control message to ASN to get the permission for the forwarding to be done by HR-infrastructure station without going through backhaul. If the ASN detects the opportunity of LF, it communicates with HR-infrastructure station via R6 interface. The details of control messages (e.g. PATH REG REQ/RSP/ACK and RR REQ/RSP/ACK) are out of scope.
  • HR-BS Upon HR-BS receives the downlink control messages from ASN, it recognizes that it is an HR-RS related after classification and can transfer the control message in AAI-L2- XFER format to HR-RS.
  • HR-RS sends the control message using AAI-L2- XFER message.
  • the control messages of AAI-SBC-REQ/RSP, AAI-LFA- REQ/RSP/ACK and AAI-LFD-REQ/RSP/ACK are sent through AAI-L2-XFER from HR-RS to HR-BS.
  • connection setup control message (AAI-DSA-REQ) sent by the source HR-MS has been received by HR-RS, if LF opportunity is detected and can be done by HR-RS, the control message AAI-LFA-REQ is sent by HR-RS to HR-BS, requesting to setup LF.
  • HR-BS receives this control message, it sends the control message (AAI- DSA-REQ) to the destination HR-MS for downlink connection establishment.
  • the handshaking is complete with the response (AAI-DSA-RSP) and the acknowledgement (AAI-DSA-ACK) between HR-BS and the destination HR-MS as normal connection as described.
  • HR-BS responds to the HR-RS by AAI-LFA-RSP with response code ObOO and valid downlink FID;
  • HR-BS sends AAI-LFA-RSP with response code 0b 10 and an empty downlink FID field;
  • the HR-RS will reply with AAI-LFA-ACK to HR-BS.
  • HR-RS responds to the source HR-MS with AAI-DSA-RSP, which confirms by AAI-DSA-ACK, following the DSA procedure in 16.2.12.6.
  • uplink FID is managed by HR-RS per 16.6.2.1.1.
  • HR-BS/HR-RS may use the field of Backup Option in control messages AAI- LFA-REQ/RSP to request or indicate the option, establishing the uplink for the source HR-MS to send data as backup to HR-BS/ASN.
  • HR-BS/ASN rather than HR-RS detects the LF opportunity that can be done through HR-RS, when control message of connection setup (AAI-DSA-REQ) sent by source HR-MS has received by HR-RS, uplink FID is managed by HR-RS and HR-RS communicates with the other network entities using AAI-L2-XFER messages carrying ASN control messages to setup the data path for this FID of the HR-MS.
  • AAI-L2-XFER messages carrying ASN control messages to setup the data path for this FID of the HR-MS.
  • HR-RS will communicate with ASN entities to complete data path setup, and the uplink setup is complete after HR-RS sends control message AAI-DSA-RSP and the source HR-MS confirms by control message AAI-DSA- ACK.
  • HR-BS will continue the downlink setup through control messages AAI-DSA-REQ/ RSP/ACK between HR-BS and the destination HR- MS.
  • HR-BS sends the control message AAI-LFA- REQ to the HR-RS, requesting the HR-RS to perform LF.
  • HR-BS confirms by control message AAI-LFA-ACK. If all these procedures are successful, the uplink setup is complete after HR-RS sends AAI-DSA-RSP and HR-MS confirms by AAI-DSA-ACK. In this case, if the field of Backup Option is set in LFA procedure (AAI-LFA-REQ/RSP/ACK), the data path for the uplink flow may be setup. Otherwise, data path may be setup without data transferring or not setup at all.
  • FIGs. 9-10 show message flow diagrams according to embodiments.
  • HR-BS 5 detects the LF opportunity for the source HR-MS 9 after HR-MS 7 initiates the connection setup to the destination HR-MS 11.
  • HR-RS 7 is instructed to perform LF for HR-MS 9 and HR-MS 11.
  • FIG. 9 the messaging 159 between HR-BS 5 and ASN 155 is illustrated but not shown in detail.
  • HR infrastructure station can initiate the similar handshaking process to set up the LF. If HR-BS 5 initiates the handshaking with HR-RS 7 for LF, it will send AAI-LFA-REQ 161 to HR-RS 7. After that HR-RS 7 should respond with AAI- LFA-RSP 163 and perform LF as described. If HR-RS 7 initiates the handshaking with HR-BS 5 for local forwarding, it will send an AAI-LFA-REQ to HR-BS 5. HR-BS 5 shall response with an AAI-LFA-RSP for the received AAI-LFA-REQ and performs local forwarding as described.
  • HR-BS 5 or HR-RS 7 may communicate with ASN 155 entities to remove data path for the corresponding uplink flow from the source HR- MS and the corresponding downlink flow to the destination HR-MS 11. Besides these messages, after receiving AAI-LFA-REQ 161, HR-RS 7 may send a DSA or DSC message to HR-BS 5 to reflect the changed QoS requirement on the relay link.
  • FIG. 10 thus shows a further embodiment as described in the previous paragraph.
  • HR infrastructure station may use AAI-LFD- REQ/RSP/ACK to end LF.
  • HR infrastructure station receives control message AAI-DSD-REQ from HR-MS (the source and/or the destination) to terminate the connection or it decides to stop LF due to other reasons, it may proceed with the handshaking procedure similar to the setup for LF.
  • HR-RS initiates the termination procedure after receiving AAI-DSD-REQ, it responds with AAI-DSD-RSP and the HR- MS will acknowledge with AAI-DSD-ACK.
  • HR-RS also sends AAI-LFD-REQ to its HR-BS, which responds with AAI-LFD-RSP. HR-RS will acknowledge with AAI-LFD- ACK.
  • HR-BS shall also send AAI-DSD-REQ to the other HR-MS to terminate the connection, following the normal procedure of connection termination.
  • HR infrastructure station When only LF is determined to stop, HR infrastructure station shall proceed with the handshaking using AAI-LFD-REQ/RSP/ACK without terminating the current connection. HR infrastructure station may setup the data path through ASN entities for the two communicating HS-MSs to maintain connectivity.
  • HR-infrastructure station shall forward the received data traffic from the source HR-MS to the destination HR-MS locally based on STIDs of the source HR-MS and the destination HR-MS, uplink FID of the source HR-MS and downlink FID of the destination HR-MS.
  • the field of Backup Option is set as Ob 1 during LFA procedure (AAI-LFA- REQ/RSP/ACK)
  • the data flow for the uplink shall be forwarded by HR infrastructure station accordingly.
  • the data traffic shall be forward by HR-RS without going through HR-BS;
  • the data traffic shall be forward by HR-BS without going through backhaul.
  • the LF opportunity is determined during data traffic forwarding after connection establishment and LF can be done through HR-RS
  • its serving HR-BS shall continue to deliver the data to maintain the connectivity of downlink flow to the destination HR-MS and forwarding HR-RS will forward the data locally to the destination HR-MS once the setup of LF is complete.
  • the forwarding from HR-RS to HR-BS for the uplink flow and/or from HR-BS to HR-RS for the downlink flow regarding to two communicating HR-MSs may continue till the transmissions of the data for uplink and/or downlink finish.
  • the data traffic forwarded locally by HR-RS shall follow MAC PDU formats in 16.2.2 and construction and transmission of MPDUs shall follow 16.2.3.
  • the data traffic forwarded locally by HR-BS shall follow MAC PDU formats in 6.2.2 and construction and transmission of MPDUs shall proceed.
  • case 1) when either the source or the destination is going out of the control of serving infrastructure station that performs LF for it; case 2) when both the source and the destination HR-MSs are going to be under the control of the same infrastructure station that shall perform LF for them.
  • serving infrastructure station has to relinquish the LF since source and destination are not under the same infrastructure station anymore. This results in the connection re-establishment after handover, which is same as the normal procedure without LF. After the connection re-establishment, data flow forwarding shall follow the normal procedure without LF.
  • HR-infrastructure station may update ASN entities on the removal of LF.
  • the details of the messages ((e.g. PATH REG REQ/RSP/ACK and RR REQ/RSP/ACK)) are out of scope.
  • the target infrastructure station or its associated ASN shall detect the LF opportunity for the HR-MS being handed over.
  • the target infrastructure station performs LF for the data traffic based on STIDs of source and destination, uplink FID of source and downlink FID of destination.
  • the control messages of AAI-LFA-REQ/RSP/ACK and AAI- LFD-REQ/RSP/ACK shall be used for the handshaking between HR-BS and HR-BS as described, if required.
  • the above description is applied to multicast service such as PTT (Push-To- Talk).
  • PTT Push-To- Talk
  • the LF can be done by HR infrastructure station (HR-BS/HR-RS).
  • the procedure for setup the multicast service in MAC layer includes the following:
  • HR infrastructure station detects and determines the LF opportunity
  • the messaging between HR-BS and HR-RS may occur.
  • HR-BS If HR-BS detects the LF opportunity that its HR-RS can perform LF, it sends AAI- LFA-REQ to HR-RS.
  • HR-RS detects the LF opportunity that it can perform LF, it sends AAI-LFA-REQ to HR-BS.
  • HR-BS performs LF, it locally forwards the data traffic from uplink flow to multicast group members through downlink multicast specific FID, without through backhaul. In this case all the multicast group members are associated with the same HR- BS.
  • HR-RS performs LF, it locally forwards the data traffic from uplink flow to multicast group members through downlink multicast specific FID, without through HR- BS. In this case all the multicast group members are associated with the same HR-RS. 3. If both HR-BS and HR-RS perform LF and HR-RS locally forwards the data traffic from downlink flow to some of multicast group members that are associated with it through downlink multicast specific FID, HR-RS also forwards the data traffic through its uplink to its associated HR-BS.
  • the HR-BS performs LF.
  • the HR-BS locally forwards the data traffic from uplink flow to all other multicast group members that are not associated with the HR-RS through downlink multicast specific FID, without through backhaul.
  • HR-BS performs LF, it locally forwards the data traffic from uplink flow to all other multicast group members through downlink multicast specific FID either directly or indirectly through other HR-RS with which some multicast group members are associated, without through backhaul.

Landscapes

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

Abstract

L'invention concerne une station d'infrastructure réalisant un réacheminement local direct dans un système de communication mobile cellulaire comprenant un réseau central. La station d'infrastructure comprend un émetteur-récepteur, un détecteur, une unité de liaison et une unité de réacheminement. Le détecteur est configuré pour détecter une opportunité de réacheminement locale entre au moins deux stations mobiles sous le contrôle de la station d'infrastructure en fonction d'émissions reçues. L'unité de liaison est configurée pour lier un flux de liaison montante et un flux de liaison descendante pour former une voie de flux de données entre lesdites au moins deux stations mobiles. Le flux de liaison montante et le flux de liaison descendante sont identifiés par des identificateurs de flux de station à identification unique. Ces identificateurs de flux de station sont des identificateurs de flux à service unique, une composition d'un identificateur de station à identification unique et d'un identificateur de flux à identification unique, ou des identificateurs de connexion. L'unité de réacheminement est configurée pour réacheminer les données reçues provenant desdites au moins deux stations mobiles au moyen d'un identificateur de flux de station fourni dans les émissions de données reçues pour déterminer le flux de voie de données.
PCT/SG2012/000068 2011-03-03 2012-03-02 Dispositifs de communication et procédés de communication WO2012118449A2 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
SG201101537-7 2011-03-03
SG2011015377 2011-03-03
SG201108175-9 2011-11-04
SG2011081759 2011-11-04

Publications (2)

Publication Number Publication Date
WO2012118449A2 true WO2012118449A2 (fr) 2012-09-07
WO2012118449A3 WO2012118449A3 (fr) 2012-11-01

Family

ID=46758413

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SG2012/000068 WO2012118449A2 (fr) 2011-03-03 2012-03-02 Dispositifs de communication et procédés de communication

Country Status (1)

Country Link
WO (1) WO2012118449A2 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014176408A1 (fr) * 2013-04-26 2014-10-30 Sprint Communications Company L.P. Système de communication sans fil à multiples configurations de communication de dispositif à dispositif (d2d)
WO2016106702A1 (fr) * 2014-12-31 2016-07-07 华为技术有限公司 Procédé et appareil de distribution de trafic de service

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030228854A1 (en) * 2002-06-10 2003-12-11 Nokia Corporation Method and system for increasing the output power of a wireless signal
US20070010197A1 (en) * 2005-07-07 2007-01-11 Fujitsu Limited Radio communication system, relay apparatus, and remote radio base station apparatus
US20110021193A1 (en) * 2009-07-27 2011-01-27 Pantech Co., Ltd. Mobile station, transmission relay, base station, and method for transferring data using connection identifier in multi-hop relay system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030228854A1 (en) * 2002-06-10 2003-12-11 Nokia Corporation Method and system for increasing the output power of a wireless signal
US20070010197A1 (en) * 2005-07-07 2007-01-11 Fujitsu Limited Radio communication system, relay apparatus, and remote radio base station apparatus
US20110021193A1 (en) * 2009-07-27 2011-01-27 Pantech Co., Ltd. Mobile station, transmission relay, base station, and method for transferring data using connection identifier in multi-hop relay system

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014176408A1 (fr) * 2013-04-26 2014-10-30 Sprint Communications Company L.P. Système de communication sans fil à multiples configurations de communication de dispositif à dispositif (d2d)
WO2016106702A1 (fr) * 2014-12-31 2016-07-07 华为技术有限公司 Procédé et appareil de distribution de trafic de service

Also Published As

Publication number Publication date
WO2012118449A3 (fr) 2012-11-01

Similar Documents

Publication Publication Date Title
CN108476394B (zh) 移动通信系统中终端通信的方法和装置
WO2008040170A1 (fr) Système de communication par retransmission sans fil à bonds multiples, et procédé et dispositif de transmission de données sens desendant associés au système
JP5642765B2 (ja) 移動性管理のための擬似配線
US20200260253A1 (en) Method and apparatus for managing packet data network connection on basis of local area in wireless communication system
JP5537651B2 (ja) Ｉｅｅｅ８０２．１１無線ｌａｎ環境における通信方法
US20150312953A1 (en) Reliable Multicast/Broadcast for P2P Communications
WO2015090057A1 (fr) Procédé et dispositif pour transmettre et recevoir des informations de routage, et système de traitement d'informations de routage
CN114208386B (zh) 用户设备到用户设备中继的连接建立方法及其用户设备
TW202215873A (zh) 層2使用者設備透過網路中繼進行信令傳輸的方法
WO2022001928A1 (fr) Procédé et appareil de communication
US8995319B2 (en) Terminal of supporting direct communication using infra communication and direct communication method of the same
WO2008034349A1 (fr) Procédé et un dispositif d'établissement d'une communication entre une sm et la sb dans un réseau relais à sauts multiples
JP2015510346A (ja) モバイル中継局トランシーバのための装置および方法、ならびにモバイル通信システムのための基地局
WO2014089756A1 (fr) Procédé et dispositif de communication destinés à un ue et à un système de communication
CN113938980A (zh) 无线通信系统中处置侧链路无线链路失败的方法和设备
WO2010081368A1 (fr) Procédé et dispositif permettant de transmettre, transporter et recevoir des données, et procédé et dispositif permettant de construire un réseau local
WO2013086949A1 (fr) Procédé et dispositif de communication
WO2015058339A1 (fr) Procédé de routage entre stations de base, passerelle de desserte, et station de base
JP2023533422A (ja) デュアルコネクティビティ下でのサイドリンクリレー通信のための方法
WO2014026390A1 (fr) Procédé, dispositif et système d'établissement de support radio
KR20130008482A (ko) 인프라 통신을 이용하여 직접 통신을 지원하는 단말 및 그의 직접 통신 방법
US9265071B2 (en) Signalling method for direct communication between terminals
WO2018061760A1 (fr) Terminal radio et dispositif de réseau
WO2012118449A2 (fr) Dispositifs de communication et procédés de communication
US9198201B2 (en) Method of direct communication between terminals respectively connected and unconnected to base station

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

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase in:

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12752756

Country of ref document: EP

Kind code of ref document: A2