+

WO2019212546A1 - Auto-raccordement à signalisation améliorée - Google Patents

Auto-raccordement à signalisation améliorée Download PDF

Info

Publication number
WO2019212546A1
WO2019212546A1 PCT/US2018/030662 US2018030662W WO2019212546A1 WO 2019212546 A1 WO2019212546 A1 WO 2019212546A1 US 2018030662 W US2018030662 W US 2018030662W WO 2019212546 A1 WO2019212546 A1 WO 2019212546A1
Authority
WO
WIPO (PCT)
Prior art keywords
network node
request
session
network
data unit
Prior art date
Application number
PCT/US2018/030662
Other languages
English (en)
Inventor
Charles Payette
Bruce Cilli
Sameerkumar Sharma
Original Assignee
Nokia Technologies Oy
Nokia Usa Inc.
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 Nokia Technologies Oy, Nokia Usa Inc. filed Critical Nokia Technologies Oy
Priority to PCT/US2018/030662 priority Critical patent/WO2019212546A1/fr
Publication of WO2019212546A1 publication Critical patent/WO2019212546A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure

Definitions

  • Various communication systems may benefit from improved session establishment. For example, it may be helpful to improve session establishment in a self-backhaul network.
  • Third Generation Partnership Project (3GPP) technology such as Fifth Generation (5G) or New Radio (NR), may employ wireless self-backhauling.
  • a wireless base transceiver station (BTS) or base station can provide backhauling services for another BTS.
  • a BTS may be deployed in any location and use another BTS for its backhaul link.
  • a self- backhauling (sBH) BTS node may service a UE as a traditional base station, except that the backhaul of the sBH BTS node does not link to a core network, but rather to another BTS, which may be referred to as a donor BTS.
  • the sBH BTS node may simply be referred to as a sBH node.
  • the sBH BTS node may include two different parts having distinct functioning.
  • the first part of the sBH node may function as a BTS, referred to as sBH BTS, while the second part may function as a UE, referred to as sBH UE.
  • the sBH UEs may aggregate the backhaul traffic into tunnels that may be referred to as so-called fat pipes. From the perspective of a donor base station utilizing wireless sBH, the traffic transmitted from the one or more sBH BTS nodes in the fat pipes may appear to have been transmitted from a single UE. Multiple sBH BTS nodes may be chained together to support a multi-hop backhaul topology. The donor BTS may support the backhauling link to the sBH BTS node, while simultaneously supporting connections to other UEs.
  • the sBH node may be utilized in an environment with high frequency bands, such as an mm Wave range that supports greater bandwidth.
  • the mmWave band may not propagate through buildings or objects well, and may act as a line of sight wave that reaches very short distances, for example a couple of hundred meters.
  • a large number of closely spaced BTS units or 5G NR Node (gNB) may be deployed in order to provide sufficient coverage for mmWave usage.
  • Self-backhauling may help to alleviate the number of costly fixed wired backhaul connections needed for the gNBs.
  • an apparatus may include at least one memory including computer program code, and at least one processor.
  • the at least one memory and the computer program code may be configured, with the at least one processor, to cause the apparatus at least to receive from a network entity a request to establish a protocol data unit session.
  • the request may be received after a user equipment attaches to a cell in which the apparatus is located.
  • the at least one memory and the computer program code may also be configured, with the at least one processor, to cause the apparatus at least to transmit a session response to the network entity in response to the request to establish the protocol data unit session.
  • a method may include receiving at a network node from a network entity a request to establish a protocol data unit session.
  • the request may be received after a user equipment attaches to a cell in which the network node is located.
  • the method may also include transmitting a session response from the network node to the network entity in response to the request to establish the protocol data unit session.
  • An apparatus may include means for receiving from a network entity a request to establish a protocol data unit session. The request is received after a user equipment attaches to a cell in which the apparatus is located. The apparatus may also include means for transmitting a session response to the network entity in response to the request to establish the protocol data unit session.
  • a non-transitory computer-readable medium encoding instructions that, when executed in hardware, perform a process. The process may include receiving at a network node from a network entity a request to establish a protocol data unit session. The request may be received after a user equipment attaches to a cell in which the network node is located. The process may also include transmitting a session response from the network node to the network entity in response to the request to establish the protocol data unit session.
  • a computer program product may encode instructions for performing a process.
  • the process may include receiving at a network node from a network entity a request to establish a protocol data unit session.
  • the request may be received after a user equipment attaches to a cell in which the network node is located.
  • the process may also include transmitting a session response from the network node to the network entity in response to the request to establish the protocol data unit session.
  • An apparatus may include circuitry for receiving from a network entity a request to establish a protocol data unit session.
  • the request may be received after a user equipment attaches to a cell in which the apparatus is located.
  • the apparatus may also include circuitry for transmitting a session response to the network entity in response to the request to establish the protocol data unit session.
  • an apparatus may include at least one memory including computer program code, and at least one processor.
  • the at least one memory and the computer program code may be configured, with the at least one processor, to cause the apparatus at least to transmit to a network node a request to establish a protocol data unit session.
  • the request may be transmitted after a user equipment attaches to a cell in which the apparatus is located.
  • the at least one memory and the computer program code may also be configured, with the at least one processor, to cause the apparatus at least to receive a session response from the network node.
  • the session response may indicate whether the protocol data unit session has been accepted or rejected.
  • a method may include transmitting from a network entity to a network node a request to establish a protocol data unit session.
  • the request may be transmitted after a user equipment attaches to a cell in which the network node is located.
  • the method may also include receiving a session response at the network entity from the network node.
  • the session response may indicate whether the protocol data unit session has been accepted or rejected.
  • An apparatus may include means transmitting from to a network node a request to establish a protocol data unit session.
  • the request may be transmitted after a user equipment attaches to a cell in which the apparatus is located.
  • the apparatus may also include means for receiving a session response at the network entity from the network node.
  • the session response may indicate whether the protocol data unit session has been accepted or rejected.
  • a n on-transitory computer-readable medium encoding instructions that, when executed in hardware, perform a process.
  • the process may include transmitting from a network entity to a network node a request to establish a protocol data unit session.
  • the request may be transmitted after a user equipment attaches to a cell in which the network node is located.
  • the process may also include receiving a session response at the network entity from the network node.
  • the session response may indicate whether the protocol data unit session has been accepted or rejected.
  • a computer program product may encode instructions for performing a process.
  • the process may include transmitting from a network entity to a network node a request to establish a protocol data unit session.
  • the request may be transmitted after a user equipment attaches to a ceil in which the network node is located.
  • the process may also include receiving a session response at the network entity from the network node.
  • the session response may indicate whether the protocol data unit session has been accepted or rejected.
  • An apparatus in certain embodiments, may include circuitry for transmitting to a network node a request to establish a protocol data unit session.
  • the request may be transmitted after a user equipment attaches to a cell in which the apparatus is located.
  • the apparatus may also include circuitry for receiving a result of call admission control in the self-backhaul network from the network entity.
  • the call admission control may be based on the congestion level metric.
  • Figure 1 illustrates an example of a system according to certain embodiments.
  • Figure 2 illustrates an example of a system according to certain embodiments.
  • Figure 3 illustrates an example of a system according to certain embodiments.
  • Figure 4 illustrates an example of a signal flow diagram according to certain embodiments.
  • Figure 5 illustrates an example of a signal flow diagram according to certain embodiments.
  • Figure 6 illustrates an example of a signal flow diagram according to certain embodiments.
  • Figure 7 illustrates an example of a flow diagram according to certain embodiments.
  • Figures 8 illustrates an example of a flow diagram according to certain embodiments.
  • Figure 9 illustrates an example of a system according to certain embodiments.
  • sBH resources are pre-pro visioned or pre-configured at installation, and the backhaul resources remain static because the resources are meant for wired or microwaved connections.
  • Certain embodiments involve dynamic self-backhauling in which resources relating the backhaul change over time.
  • the dynamic nature of self-backhauling adds further complexity to the network. For example, a donor gNB may subtract or add independent UEs, thereby changing the amount of resources available for the sBH gNB to access the donor node.
  • the Signal-to-lnterference Ratio (SINR) may also change between the sBH node and the donor node.
  • SINR Signal-to-lnterference Ratio
  • a sBH node may be added to the network or handed over to a new donor node. All of the above changes to the network may lead to dynamic self- backhauling with changing resource availability among the different entities and nodes located within the network. The complexity of the sBH network may be further increased in a multi-hop scenario in which multiple network nodes may be chained together.
  • the traffic generated by the one or more UEs attaching to a network node may be tunneled such that multiple bearers supported by the sBH node appear as a single bearer to die donor node.
  • the aggregation of the multiple bearers may lead to the so-called fat pipes.
  • the donor node may be informed of the nature of the services supported by the sBH nodes connected or chained to the donor node.
  • die donor node may aware of the quality of service (QoS) of die flows or services supported by the given network nodes.
  • QoS quality of service
  • Knowing the nature of the flows or services may allow the donor node to schedule sBH node traffic, as opposed to traffic from an independent user equipment (UE) that attaches to the network.
  • the donor node in some embodiments, may be able to account for the pressure or volume traffic experienced by the backhaul tunnel when performing Call Admission Control (CAC).
  • CAC may be a decision or calculation made by the network node to authorize a UE’s service request and allow the UE to gain access to the network.
  • CAC Call Admission Control
  • certain embodiments provide for distributing information to each sBH node and/or donor node.
  • Distributing such information may allow for the donor node and/or the sBH node to account for, or take into consideration, downstream sBH nodes as part of their admission control and/or any other scheduling operation.
  • some embodiments help to alleviate some of the complexities caused by dynamic self-backhauling networks by properly distributing information to the sBH nodes and/or donor nodes.
  • the network nodes may then be able to make informed decisions, thereby preventing the use of unnecessary messaging and processing.
  • Figure 1 illustrates an example of a system according to certain embodiments.
  • Figure 1 illustrates a system that includes donor node 113, sBH node 1 110, sBH node 2 11 1, and sBH node 3 1 12.
  • the system therefore, includes three sBH nodes and one donor node.
  • each of the sBH nodes may include a gNB part and a UE part
  • the sBH nodes may perform functions of both a gNB and/or a UE.
  • the gNB used to access may be referred to as sBH gNB, while the UE that provides the connection for the backhaul may be referred to to a sBH UE.
  • both sBH node 2 111 and sBH node 3 112 may also act as donor nodes because they have backhaul connects to other sBH nodes.
  • the system shown in Figure 1 also include UE 1 121, UE 2 122, UE 3 123, UE 4 124, and/or UE 5 125.
  • the network node when performing the CAC for a UE or a bearer at a gNB sBH, the network node may account for local resources at the network node, as well as at the donor node at each upstream hop toward the core. Local resources may be those resources at the serving sBH node that can be used to service the UE. For example, when UE 2 122 requests service to sBH Node 2 111 , the available resources of sBH Node 3 112 and donor node 113 may be considered by the network node while performing CAC.
  • each sBH gNB along the chain may admit the UE, and each network resources at each of the network nodes along with chain may be accounted for when performing CAC.
  • a combination of a non-access stratum (NAS) or N2 signaling may be used with an Xn interface.
  • a NAS/N2 signaling may be used without using the Xn interface.
  • An Xn interface may be used to connect one or more network nodes, such as an sBH node and a donor node.
  • N2 may be an interface used to connect a network entity, such as Access and Mobility Function (AMF), and the radio access network (RAN).
  • AMF Access and Mobility Function
  • RAN radio access network
  • the RAN may include the one or more network nodes.
  • Figure 2 illustrates an example of a system according to certain embodiments.
  • Figure 2 illustrates an example in which information between one or more network nodes may be transmitted via an Xn interface.
  • the system illustrated in Figure 2 includes UE 210, sBH gNB 220, sBH gNB 230, donor gNB 240, and AMF 250.
  • sBH gNB 220 may be referred to as a network node
  • sBH gNB 230 may be referred to as another network node.
  • AMF 250 may be referred to as a network entity.
  • UE 210 may transmit to AMF 250 a service request.
  • the service request may be directly transmitted from UE 210 to AMF 250, while in other embodiments the service request may be transmitted from UE 210 to AMF 250 via sBH gNB 220.
  • AMF 250 may set up the one or more protocol data unit (PDU) sessions, for example, with help of a session management function (SMF).
  • sBH gNB 220 may receive from AMF 250 a request to establish a PDU session.
  • the request for example, may be an N2 request
  • the request may include a list of PDU sessions and/or quality of service (QoS) flows.
  • QoS quality of service
  • the request may also be received after a UE attaches to a cell in which the sBH gNB 220 is located
  • the UE may be in a CM- CONNECTED state.
  • the CM-CONNECTED state may be described in 3GPP TS 23.501. 3GPP TS 23.501 is hereby incorporated by reference.
  • After the UE attaches may mean at any point in time after the UE sends a service request to the network, including AMF 250.
  • the PDU session may be associated with a QoS requirement of the UE.
  • the PDU session may be referred to as a QoS flow.
  • the list of PDU sessions may be provided to the network by the UE in the service request.
  • the network node may transmit a backhaul request to another network node.
  • the backhaul request may include the received request to establish the PDU session.
  • the backhaul request may also include PDU session characteristics, such as QoS information or requirements.
  • the backhaul request may be transmitted on an Xn interface. If the another network node, which may be the next hop gNB in a multi-hop environment, has sufficient resources to support the PDU session, the another network node may transmit or forward the request to an additional network node or hop. The another network node or network node may then wait to receive an indication or a response that includes an acceptance or a rejection of the PDU session.
  • sBH gNB 220 may receive the indication or response from sBH gNB 230, while sBH gNB 230 may receive the indication or response from donor gNB 240.
  • the indication or response may be received via the Xn interface.
  • each of the network nodes may determine whether to accept or reject the requested PDU session.
  • An indication or response including the acceptance or rejection may cascade down to the target or originating netwoik node, which may be sBH gNB 220 in Figure 2.
  • sBH gNB 220 may transmit a positive session response to AMF 250. The session response may be transmitted via the N2 interface.
  • AMF 250 may complete establishment of the PDU session and grant the UE’s service request The UE may then join the network and attach to any one of the sBH nodes within the sBH network. Because the backhaul request has already been transmitted to all of the sBH nodes and donor nodes via the Xn interface, all of the sBH nodes may have already accounted for the resources used in supporting the UE. In the embodiment shown in Figure 2, Xn messaging may also be extended to support sBH node handover.
  • Figure 3 illustrates an example of a system according to certain embodiments.
  • Figure 3 illustrates an embodiment of a system that includes a UE 1 310 that attempts to attach to sBH node 1 320.
  • the system also includes sBH node 2 330, donor node 340, AMF 350, and a topology manager (TM) 360.
  • the TM may be a centralized server.
  • the TM server may maintain a network topology that includes a mapping of the one or more network nodes, such as sBH nodes and/or donor nodes, and how the one or more network nodes are connected.
  • an N2 session request may be transmitted to all of the network nodes, as well as the donor node, as opposed to only the target network node, as shown in Figure 2.
  • all of the network nodes may accept the request before the target network node may accept the UE’s service request
  • an N2 request may be transmitted from AMF 350 to sBH node 2 330 and donor node 350, and may receive a response with a positive indication affirming the PDU session, before AMF 350 may transmit the N2 request to sBH Node 1 320.
  • AMF 350 may receive a topology response from another network entity, for example TM 360, and determine whether to establish the PDU session based on the received topology response.
  • AMF 350 may transmit to a network node a request to establish the PDU session.
  • AMF 350 may also transmit the request to establish the PDU session to another network node, and subsequently receive an indication from the another network node or the network node that they has accepted or rejected the PDU session.
  • the request to establish the PDU session may be transmitted to the network node and the another network node simultaneously or one at a time.
  • AMF 350 and/or TM 360 may determine whether to establish the PDU session based on the session response and/or indication received from the network node or the another network node.
  • the request from the network entity may be transmitted to the network node after a UE attaches to a cell in which the network node is located.
  • the attachment of the UE may be an initial attachment of the sBH UE
  • the sBH node may not yet be fully operational.
  • the initial attachment may be the attachment of the UE inside the sBH node to the donor node, for example, as shown in Figure 1.
  • the CAC decision may consider whether the network node may serve as a donor node.
  • the sBH UE has already been active, the full context of the UE that the network node is capable of supporting may be conveyed.
  • the sBH context for example, may be transmitted amongst the network nodes using the Xn interface.
  • Certain embodiments may help to distribute information to each of the network nodes in an sBH network.
  • the distributed information may be in the form of an N2 or Xn request, and may allow the network nodes to consider downstream network nodes when performing admission control and/or other scheduling operations.
  • the embodiment shown in Figure 3, for example, may be an extension of the existing process for a UE attaching to a network node, such as a gNB.
  • each of the network nodes included along die path or in the network may receive the request and/or transmit the response, regardless of the decisions made by other network nodes.
  • the remaining network nodes may have their acceptance of the request rescinded.
  • die network entity such as the AMF or the TM, may alternatively transmit the request to the impacted netwoik nodes one at a time, waiting for a response before proceeding to the next netwoik node.
  • Figure 4 illustrates an example of a signal flow diagram according to certain embodiments.
  • Figure 4 illustrates the sharing of an identity, for example a global cell identity, in a sBH network including sBH gNB 2401 , sBH UE 2 402, sBH gNB 1 403, sBH UE 1 404, donor gNB 405, and a core network entity or AMF 406.
  • sBH gNB 2401 and sBH UE 2 402 maybe part of a single sBH node 2
  • sBH gNB 1 403 and sBH UE 2 404 may be part of a single sBH node 1.
  • the sBH gNB may determine the identity of die next hop, as well as how to address the next hop.
  • the next hop may be a neighboring network node or donor node.
  • the identity of the cell in which another network node is located may be obtained from die sBH UE part of die node when it initially attaches to the next hop. Based on the obtained identity, the sBH node may obtain the internet protocol (IP) address of the next hop.
  • IP internet protocol
  • the sBH gNB may maintain this relationship for as long as the sBH UE is connected. In other words, the global cell identity and/or the associated IP address is maintained so long as the sBH UE is connected to the sBH gNB.
  • the sBH gNB may maintain die Xn connection with the next hop for as long as the sBH UE is connected to the next hop.
  • the sBH UE may discover other neighbor network nodes for potential future use on the sBH gNB side in the event of a handover.
  • identity may also be referred to as an identifier.
  • sBH UE 2 402 may attach to sBH gNB 1 403, and send a request to sBH gNB 1 403 in an attempt to retrieve information related to the network node.
  • sBH UE 2402 may then obtain an identifier, such as a global cell identifier, from sBH gNB 1 403, as shown in step 411.
  • sBH gNB 2 401 may obtain a global identifier of sBH Node 1 from sBH UE 2402.
  • the network node may obtain an identity of a cell in which the another network node is located from a UE part of the network node.
  • sBH gNB 2401 may attempt to retrieve an internet protocol (IP) address from a core network entity 406, such as AMF.
  • IP internet protocol
  • sBH gNB 2 401 may obtain an IP address from core network entity 406.
  • the network node may obtain an IP address of the another node based on the obtained identity of the cell in which the another network node is located.
  • sBH node 1 may undergo a similar process as undergone by sBH node 2 in steps 410414, in order to obtain the cell identity of donor node 405.
  • sBH UE 1 404 may attached to donor gNB 405, and send a request to donor gNB 405 in order to retrieve information.
  • the global identifier of the donor node may be obtained by sBH UE 1 404.
  • sBH gNB 1 403 may then obtain a global identifier from the UE part of the sBH node, as shown in step 417.
  • sBH gNB 1 403 may send a request to core network entity 406 to obtain an IP address of the donor node.
  • the network node such as sBH node 1 , may obtain the IP address at least partially based on tire global cell identity obtained in step 417.
  • Figure 5 illustrates an example of a signal flow diagram according die certain embodiments.
  • Figure 5 illustrates an embodiment that utilizes an Xn interface, similar to the Xn interface shown in Figure 2.
  • the sBH network shown in Figure 5 includes UE 501, sBH gNB 2 502, sBH UE 2 503, sBH gNB 1 504, sBH UE 1 505, donor gNB 506, and a core network entity or AMF 507.
  • the network may undergo network setup.
  • the sBH network may discover one or more next hops.
  • the next hop of sBH node 1 for example, may be sBH node 2, while the next hop of sBH node 2 may be a donor node.
  • UE 501 may attach or request service to sBH node 2.
  • Core network entity or AMF 507 may then discover a service level agreement of the UE, and issue or transmit a request to sBH gNB 2 502.
  • the service level agreement may inform the core network entity or AMF 507 of the QoS requirements or information associated with the UE’s service request sBH gNB
  • sBH gNB 2 502 may be referred to a network node or a target network node.
  • sBH gNB 2 502 may receive a request to establish a PDU session.
  • the request may be an N2 session request, for example.
  • the request may be received after a UE attaches to a cell in which sBH gNB 2 502 is located, as shown in step 511.
  • sBH gNB 2 502 may perform a local CAC, and determine whether the network node has available resources for establishing die PDU session.
  • sBH gNB 2 502 may transmit a backhaul request to sBH gNB 1 504 via sBH UE 2 503, as shown in step 514.
  • the backhaul request may be transmitted via an Xn interface.
  • the backhaul request may include QoS information associated with the PDU session.
  • sBH gNB 1 504 which may be referred to as the another network entity, may also perform a local CAC to determine whether it has sufficient resources to accommodate the UE service request If so, sBH gNB 1 504 may transmit a backhaul request via the Xn interface to donor gNB 506, as shown in step 516.
  • the backhaul request may include QoS information associated with the PDU session.
  • Donor gNB 506 may then perform a local CAC, and determine whether the donor node has sufficient resources to accommodate the UE service request, as shown in step 517.
  • the nodes may transmit an indication comprising an acceptance of the PDU session over the Xn interface, as shown in steps 518 and 519.
  • the Xn indication may be cascaded from the donor node through the another network node to die network node.
  • the sBH gNB 2 502 may transmit a session response in response to the request to establish the PDU and/or based on the indication received from the another network node.
  • sBH gNB 2 502 may transmit a session response based on determining that the network node has die available resources for establishing the PDU session.
  • each of the network nodes in the sBH network may be updated with QoS infonnation and/or any other information related to the PDU session to account for the UE attaching anywhere within the path or sBH network.
  • Figure 6 illustrates an example of a signal flow diagram according to certain embodiments.
  • Figure 6 illustrates an embodiment that utilizes the Xn interface as shown in Figure 2.
  • the another network node may determine that it does not have sufficient resources to accommodate the UE’s service request, and reject die request
  • the another network node may reject the UE’s service request for any other reason.
  • the another network node then sends an indication of the rejection to the network node, rather than forwarding the request to the next hop. By not forwarding the request to the next hop, the network may prevent unnecessary messaging and reduce resources associated with network signaling.
  • the sBH network shown in Figure 6 includes UE 601, sBH gNB 2 602, sBH UE 2 603, sBH gNB 1 604, sBH UE 1 605, donor gNB 606, and a core network entity or AMF 607.
  • Steps 610-614 in Figure 6 may mimic steps 510- 514 shown in Figure 5.
  • network setup and next hop discovery may be performed by the different network nodes and entities in the network.
  • UE 601 may attach to sBH gNB 2 602.
  • the UE may request service to target node sBN gNB 2602.
  • Core network entity or AMF 607 may then discover a service level agreement of the UE, and issue or transmit a request to the target network node.
  • the service level agreement may include the QoS requirements or information associated with the UE’s service request or PDU session establishment
  • sBH gNB 2 602 may receive a request to establish a PDU session from core entity or AMF 607.
  • the request may be an N2 session request for example.
  • the request may be received after a UE attaches to a cell in which sBH gNB 2 602 is located, as shown in step 611.
  • sBH gNB 2 602 may perform a local CAC, and determine whether the network node has available resources for establishing the PDU session.
  • the network node may transmit a backhaul request to sBH gNB 1 604 via sBH UE 2 603, as shown in step 614.
  • the backhaul request may be transmitted via an Xn interface.
  • the backhaul request may include QoS information associated with the PDU session.
  • sBH gNB 1 604 may perform CAC and reject the UE’s request for service.
  • the sBH gNB 1 604 may transmit an indication to sBH gNB 2602 via sBH UE 2603. The indication may indicate that the UE’s service request has been rejected. In certain embodiments, therefore, instead of sending an Xn backhaul request to donor node 606, sBH gNB 1 604 may transmit an Xn rejection to sBH gNB 2 602 and halt the process.
  • sBH gNB 2 602 may transmit a session response to the core entity or AMF 607, where the session response indicates a rejection of the UE’s service request.
  • one or more N2 requests may be used along with a centralized function as shown in Figure 3.
  • the AMF and/or TM may transmit all of the N2 session requests simultaneously or at the same time.
  • the N2 session requests may include QoS information and/or requirements associated with the PDU session.
  • Some embodiment may also be able to inform the target gNB of the UE, or any other impacted network node, that one of the another network nodes rejected the N2 session request To do so, an acknowledged or a negative acknowledgement may be transmitted from the AMF and/or TM to the one or more network nodes in Figure 3.
  • the AMF and/or TM may transmit the N2 session request one at a time. For example, the AMF and/or TM may initially transmit the session request to the last hop or donor node. After the donor node accepts the session request, the AMF and/or TM may then proceed to transmit the session request to another network node, such as the second to last hop, and so on until the request reaches the target network node.
  • the AMF and/or TM may transmit the N2 session request one at a time. For example, the AMF and/or TM may initially transmit the session request to the last hop or donor node. After the donor node accepts the session request, the AMF and/or TM may then proceed to transmit the session request to another network node, such as the second to last hop, and so on until the request reaches the target network node.
  • each network node in the sBH network may update each network node when a UE detaches, is handed over, or a session are modified.
  • certain embodiments take advantage of N2 and/or Xn interface requests.
  • one or more network nodes may locally accept or reject a UE’s service request.
  • Session modification may include the additional of a new flow or radio bearer to support a QoS flow identity (QFT).
  • QFT QoS flow identity
  • Figure 7 illustrates an example of a flow diagram according to certain embodiments.
  • the network node may receive from a network entity a request to establish a PDU session.
  • the request may be received after a UE attaches to a cell in which the network node is located.
  • the request may be received on the N2 interface.
  • the PDU session may be associated with a QoS requirement of die UE.
  • the network entity for example, may be an AMF and/or a TM.
  • the network node may determine that it has available resources for establishing the PDU session.
  • the determining may be made or performed by the network node before the transmitting of the backhaul request to another network node.
  • the determining for example, may be based on the QoS requirement of the UE, which may have been received by the network node as part the request received in step 710.
  • the determining may involve CAC.
  • the network node may transmit a backhaul request to another network node.
  • the backhaul request may comprise the received request to establish the PDU session.
  • the backhaul request may be transmitted over the Xn interface.
  • the backhaul request may also include a QoS requirement of the UE.
  • the backhaul request may be transmitted to the another network node and to one or more additional network nodes.
  • the backhaul request may be transmitted from sBH gNB 2 to sBH gNB 1 and donor gNB.
  • the network node may obtain an identity of a cell in which the another network node is located from a user UE part of the network node.
  • the network may also obtain an IP address of the another node based on the obtained identity of the cell in which the another network node is located, as shown in step 750.
  • the backhaul request may be transmitted using the IP address of the another network node.
  • An embodiment of steps 740 and 750 are illustrated in Figure 4. In some embodiments, steps 740 and 750 may be performed before step 730.
  • the network node may receive an indication from the another network node.
  • the another network node may be a donor node or a seif-backhauling node.
  • the indication may include an acceptance and/or a rejection of the PDU session.
  • the indication received at the network node may be used for scheduling operations of the network node. Assuming the network node is serving individual UEs in addition to a self backhaul fat pipe, in certain embodiments the network node’s scheduler may allocate resources, for example PRBs, fairly between the fat pipe and the individual UEs.
  • the fat pipe may receive 4/5 of the available resources is both the uplink and downlink direction.
  • the network node’s scheduler may also accommodate the QoS flows.
  • a QoS flow may further specify other attributes that characterize the flow’s overall QoS requirements, such as Packet Error Rate (PER) and/or Packet Delay Budget (PDB).
  • PER Packet Error Rate
  • PDB Packet Delay Budget
  • the indication may be received from the network entity, such as the AMF.
  • the determining that the network node has available resources for establishing the PDU session may be based on the indication received from the another network node or network entity.
  • a session response may be transmitted from the network node to the network entity in response to the request to establish the PDU session.
  • the session response may be transmitted by the network node to the network entity based on the indication received from the another network node or the network entity.
  • the session response may be termed a positive session response.
  • the transmitted session response from the network node to the network entity is positive, the PDU session may be established.
  • Figure 8 illustrates an example of a flow diagram according to certain embodiments.
  • Figure 8 illustrates an embodiment of a method performed by a network entity, such as an AMF.
  • the network entity described in Figure 8 may communicate with tire network node illustrated in Figure 7.
  • the network entity may transmit to a network node a request to establish a PDU session.
  • the request may be transmitted after a UE attaches to a cell in which the network node is located.
  • the network entity may transmit the request to establish the PDU session to another network node.
  • the network node may be sBH gNB 2 while the another network node may be sBH gNB 1 or a donor node.
  • tire request to establish the PDU session may be transmitted to the network node and tire another network node simultaneously, as shown in Figure 3.
  • the network entity may receive a topology response from another network entity, such as the I'M.
  • the topology response may include a mapping of the network node and the another network node in a network.
  • the network entity may receive an indication that the another network node has accepted or rejected the PDU session.
  • the network entity may receive a session response from the network node. The session response may indicate whether the PDU session has been accepted and/or rejected by the network node.
  • the network entity may determine based on the session response from the network node and the received indication from the another network node to establish the protocol data unit session. In certain embodiments, the determining to establish the PDU session may be based on the received topology response from the TM. After receiving the session response from the network node and/or the indication from the another network node, the network entity may establish the PDU session. Once the PDU session is established, the UE may begin receiving service from one or more the network nodes in the sBH network.
  • Figure 9 illustrates a system according to certain embodiments. It should be understood that each table, signal, or block in Figures 1-8 may be implemented by various means or their combinations, such as hardware, software, firmware, one or more processors and/or circuitry.
  • a system may include several devices, such as, for example, network entity 920 or UE 910. The system may include more than one UE 910 and more than one network entity 920.
  • Network entity 920 may be a base station, an access point, an access node, an enhanced NodeB (eNB), a gNB, a server, a host, or any other network entity that may communicate with the UE.
  • eNB enhanced NodeB
  • Network entity 920 may also be a network node, such to an sBH node that may include an sBH gNB part and an sBH UE part. In some other embodiments, network entity 920 may be the AMF shown in Figures 2-6 or the TM shown in Figure 3.
  • Each of these devices may include at least one processor or control unit or module, respectively indicated to 911 and 921.
  • At least one memory may be provided in each device, and indicated as 912 and 922, respectively.
  • the memory may include computer program instructions or computer code contained therein.
  • One or more transceiver 913 and 923 maybe provided, and each device may also include an antenna, respectively illustrated as 914 and 924. Although only one antenna each is shown, many antennas and multiple antenna elements may be provided to each of the devices. Other configurations of these devices, for example, may be provided.
  • network entity 920 and UE 910 may be additionally configured for wired communication, in addition to wireless communication, and in such a case antennas 914 and 924 may illustrate any form of communication hardware, without being limited to merely an antenna.
  • Transceivers 913 and 923 may each, independently, be a transmitter, a receiver, or both a transmitter and a receiver, or a unit or device that may be configured both for transmission and reception.
  • the transmitter and/or receiver (as far as radio parts are concerned) may also be implemented to a remote radio head which is not located in the device itself, but in a mast, for example.
  • the operations and functionalities may be performed in different entities, such as nodes, hosts or servers, in a flexible manner. In other words, division of labor may vary case by case.
  • One possible use is to make a network entity deliver local content.
  • One or more functionalities may also be implemented as virtual applications) in software that can run on a server.
  • a user device or UE 910 may be a mobile station (MS), such as a mobile phone or smart phone or multimedia device, an loT cellular device, a computer, such as a tablet, provided with wireless communication capabilities, personal data or digital assistant (PDA) provided with wireless communication capabilities, portable media player, digital camera, pocket video camera, navigation unit provided with wireless communication capabilities or any combinations thereof.
  • MS mobile station
  • PDA personal data or digital assistant
  • the user equipment may be replaced with a machine communication device that does not require any human interaction, such as a sensor, meter, or robot.
  • an apparatus such as a user equipment or a network entity, may include means for carrying out embodiments described above in relation to Figures 1-8.
  • at least one memory including computer program code can be configured to, with the at least one processor, cause the apparatus at least to perform any of the processes described herein.
  • Processors 91 1 and 921 may be embodied by any computational or data processing device, such as a central processing unit (CPU), digital signal processor (DSP), application specific integrated circuit (ASIC), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), digitally enhanced circuits, or comparable device or a combination thereof.
  • the processors may be implemented as a single controller, or a plurality of controllers or processors.
  • the implementation may include modules or unit of at least one chip set (for example, procedures, functions, and so on).
  • Memories 912 and 922 may independently be any suitable storage device. such as a non-transitory computer-readable medium.
  • a hard disk drive (HDD), random access memory (RAM), flash memory, or other suitable memory may be used.
  • the memories may be combined on a single integrated circuit as the processor, or may be separate therefrom.
  • the computer program instructions may be stored in the memory and which may be processed by the processors can be any suitable form of computer program code, for example, a compiled or interpreted computer program written in any suitable programming language.
  • the memory or data storage entity is typically internal but may also be external or a combination thereof, such as in the case when additional memory capacity is obtained from a service provider.
  • the memory may be fixed or removable.
  • the memory and the computer program instructions may be configured, with the processor for the particular device, to cause a hardware apparatus such as netwoik entity 920 or UE 910, to perform any of the processes described above (see, for example, Figures 1-8). Therefore, in certain embodiments, a non-transitory computer-readable medium may be encoded with computer instructions or one or more computer program (such as added or updated software routine, applet or macro) that, when executed in hardware, may perform a process such as one of the processes described herein.
  • a non-transitory computer-readable medium may be encoded with computer instructions or one or more computer program (such as added or updated software routine, applet or macro) that, when executed in hardware, may perform a process such as one of the processes described herein.
  • Computer programs may be coded by a programming language, which may be a high-level programming language, such as objective-C, C, C++, C#, Java, etc., or a low-level programming language, such as a machine language, or assembler. Alternatively, certain embodiments may be performed entirely in hardware.
  • a programming language which may be a high-level programming language, such as objective-C, C, C++, C#, Java, etc.
  • a low-level programming language such as a machine language, or assembler.
  • certain embodiments may be performed entirely in hardware.
  • an apparatus may include circuitry configured to perform any of the processes or functions illustrated in Figures 1 -8.
  • Circuitry in one example, may be hardware-only circuit implementations, such as analog and/or digital circuitry.
  • Circuitry in another example, may be a combination of hardware circuits and software, such as a combination of analog and/or digital hardware circuits) with software or firmware, and/or any portions of hardware processors) with software (including digital signal processors)), software, and at least one memory that work together to cause an apparatus to perform various processes or functions.
  • circuitry may be hardware circuits) and or processor(s), such to a microprocessors) or a portion of a microprocessors), that include software, such as firmware for operation. Software in circuitry may not be present when it is not needed for the operation of the hardware.
  • Figure 9 illustrates a system including a network entity 920 and UE 910
  • certain embodiments may be applicable to other configurations, and configurations involving additional elements, as illustrated and discussed herein.
  • multiple user equipment devices and multiple base stations may be present, or other nodes providing similar functionality, such as nodes that combine the functionality of a user equipment and a base station, such as a relay node.
  • the UE 910 may likewise be provided with a variety of configurations for communication other than communicating with network entity 920.
  • the UE 910 may be configured for device-to-device, machine-to-machine, or vehicle-to-vehicle communication.
  • the above embodiments are directed to computer-related technology, and provide for significant improvements to the functioning of a network and/or to the functioning of the network entities within the network, or the user equipment communicating with the network.
  • certain embodiments help self-backhauling technology to be deployed in mmWave spectrum.
  • the above embodiments may help reduce the complexities involved with using a dynamic sBH network.
  • QoS information may be propagated to all of the network nodes in the sBH network using N2 or Xn messaging.
  • N2 signaling may be extended to all of the network nodes, and all impact nodes may be informed of the acceptance and/or rejection of the UE’s service request using, for example, an acknowledge or a negative acknowledgement
  • a centralized node may maintain a map of the network that may be used for N2 signaling, for example.
  • N2 signaling may be used for die target network node, while an Xn backhaul request may be used to message at least one other netwoik node sBH network. Using Xn messaging may allow the network to reduce the amount of resources used for signaling.

Landscapes

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

Abstract

Selon l'invention, divers systèmes de communication peuvent bénéficier d'un établissement de session amélioré. Par exemple, il peut être utile d'améliorer un établissement de session dans un réseau à auto-raccordement. Un procédé décrit dans certains modes de réalisation peut consister à recevoir, au niveau d'un nœud de réseau, une demande d'établissement d'une session d'unité de données de protocole, en provenance d'une entité réseau. La demande peut être reçue après qu'un équipement utilisateur s'est rattaché à une cellule dans laquelle se trouve le nœud de réseau. Le procédé peut également consister à transmettre une réponse de session, du nœud de réseau à l'entité réseau, en réponse à la demande d'établissement de la session d'unité de données de protocole.
PCT/US2018/030662 2018-05-02 2018-05-02 Auto-raccordement à signalisation améliorée WO2019212546A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/US2018/030662 WO2019212546A1 (fr) 2018-05-02 2018-05-02 Auto-raccordement à signalisation améliorée

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2018/030662 WO2019212546A1 (fr) 2018-05-02 2018-05-02 Auto-raccordement à signalisation améliorée

Publications (1)

Publication Number Publication Date
WO2019212546A1 true WO2019212546A1 (fr) 2019-11-07

Family

ID=62244557

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2018/030662 WO2019212546A1 (fr) 2018-05-02 2018-05-02 Auto-raccordement à signalisation améliorée

Country Status (1)

Country Link
WO (1) WO2019212546A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021247404A1 (fr) * 2020-06-03 2021-12-09 Qualcomm Incorporated Gestion d'une configuration de liaison terrestre dans un réseau sans fil à sauts multiples
WO2024160293A1 (fr) * 2024-02-06 2024-08-08 Lenovo (Beijing) Limited Établissement de session pdu
WO2024169800A1 (fr) * 2024-02-06 2024-08-22 Lenovo (Beijing) Limited Établissement de session pdu

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110194535A1 (en) * 2008-10-20 2011-08-11 Telefonaktiebolaget Lm Ericsson (Publ) QoS Management for Self-Backhauling in LTE
US20130310052A1 (en) * 2011-02-04 2013-11-21 Telefonaktiebolaget Lm Ericsson (Publ) Methods and devices for supporting backhaul selection
WO2017031636A1 (fr) * 2015-08-21 2017-03-02 华为技术有限公司 Procédé et appareil pour établir une connexion de raccordement sans fil

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110194535A1 (en) * 2008-10-20 2011-08-11 Telefonaktiebolaget Lm Ericsson (Publ) QoS Management for Self-Backhauling in LTE
US20130310052A1 (en) * 2011-02-04 2013-11-21 Telefonaktiebolaget Lm Ericsson (Publ) Methods and devices for supporting backhaul selection
WO2017031636A1 (fr) * 2015-08-21 2017-03-02 华为技术有限公司 Procédé et appareil pour établir une connexion de raccordement sans fil
EP3319370A1 (fr) * 2015-08-21 2018-05-09 Huawei Technologies Co., Ltd. Procédé et appareil pour établir une connexion de raccordement sans fil

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LG ELECTRONICS INC: "Discussion on Relay Functionality", 3GPP DRAFT; R2-100431 DISCUSSION ON RELAY FUNCTIONALITY, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Valencia, Spain; 20100118, 12 January 2010 (2010-01-12), XP050421081 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021247404A1 (fr) * 2020-06-03 2021-12-09 Qualcomm Incorporated Gestion d'une configuration de liaison terrestre dans un réseau sans fil à sauts multiples
US11672031B2 (en) 2020-06-03 2023-06-06 Qualcomm Incorporated Managing a backhaul configuration in a wireless multi-hop network
WO2024160293A1 (fr) * 2024-02-06 2024-08-08 Lenovo (Beijing) Limited Établissement de session pdu
WO2024169800A1 (fr) * 2024-02-06 2024-08-22 Lenovo (Beijing) Limited Établissement de session pdu

Similar Documents

Publication Publication Date Title
US11546811B2 (en) Method for establishing a fronthaul interface, method for performing access for a UE, method and apparatus for performing a handover for a UE, data forwarding method, user equipment and base station
US11109263B2 (en) Data transmission method and data transmission apparatus
US20230239757A1 (en) Method and apparatus for inter-donor mobility
KR102387163B1 (ko) 데이터 전달 방법, 장치, 및 시스템
WO2019214729A1 (fr) Procédé et dispositif de traitement de données
JP7579360B2 (ja) デュアルコネクティビティ下でのサイドリンクリレー通信のための方法
CN115150045B (zh) 无线通信方法与装置、终端和网络设备
US12245081B2 (en) Threshold-based reporting for efficient admission control support for wireless networks
WO2020098747A1 (fr) Procédé et appareil de configuration de trajet de transmission
CN110475210B (zh) 一种通信方法及装置
WO2022170798A1 (fr) Procédé de détermination de stratégie et appareil de communication
WO2018223824A1 (fr) Procédé et appareil de transmission de données de service
CN117616806A (zh) 用于处置节点迁移的第一节点、第二节点以及由此执行的方法
WO2019212546A1 (fr) Auto-raccordement à signalisation améliorée
WO2022082690A1 (fr) Procédé, appareil et système de commutation de groupe
CN110876171A (zh) 一种多跳数据传输方法及装置
US10051525B1 (en) Controlling relay-UE operation based on bearer content type
EP3542590B1 (fr) Ancrage de plan de commande à connectivité multiple
WO2022016452A1 (fr) Acheminement de données pour un équipement utilisateur avec transmission de données
WO2021204270A1 (fr) Procédé et appareil de communication
WO2019212544A1 (fr) Commande centralisée d'admission de cellule pour auto-raccordement
CN118679810A (zh) 集成接入和回传网络中的服务请求
WO2023197185A1 (fr) Dispositif de nœud iab, dispositif donneur iab et procédé de détermination d'adresse de transmission
WO2023197184A1 (fr) Dispositif donneur iab et procédé de configuration d'adresse de transmission
TW202345619A (zh) 用於中繼節點標識符獲取的方法及其使用者設備

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

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

Country of ref document: EP

Kind code of ref document: A1

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载