WO2016159841A1 - Continuité de service - Google Patents

Continuité de service Download PDF

Info

Publication number
WO2016159841A1
WO2016159841A1 PCT/SE2015/050388 SE2015050388W WO2016159841A1 WO 2016159841 A1 WO2016159841 A1 WO 2016159841A1 SE 2015050388 W SE2015050388 W SE 2015050388W WO 2016159841 A1 WO2016159841 A1 WO 2016159841A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
node
ran node
routing path
data packets
Prior art date
Application number
PCT/SE2015/050388
Other languages
English (en)
Inventor
Pontus Wallentin
Qianxi Lu
Fredrik Gunnarsson
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to PCT/SE2015/050388 priority Critical patent/WO2016159841A1/fr
Publication of WO2016159841A1 publication Critical patent/WO2016159841A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/03—Reselecting a link using a direct mode connection
    • H04W36/033—Reselecting a link using a direct mode connection in pre-organised networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices

Definitions

  • the techniques described herein relate to maintaining service continuity for a terminal device during a switch between an infrastructure routing path and a direct routing path.
  • Device-to-device communication is a well-known and widely used component of many existing wireless technologies, including ad hoc and cellular networks. Examples include Bluetooth and several variants of the IEEE 802.1 1 standards suite such as Wi- Fi Direct. These systems operate in the unlicensed spectrum.
  • D2D device-to-device
  • ProSe - Proximity Service - Direct Communication also known as ProSe - Proximity Service - Direct Communication
  • cellular networks to take advantage of the proximity of communicating terminal devices and at the same time to allow terminal devices to operate in a controlled interference environment.
  • device-to-device communication share the same spectrum as the cellular system, for example by reserving some of the cellular uplink resources for device-to-device purposes.
  • Allocating dedicated spectrum for device-to-device purposes is a less likely alternative as spectrum is a scarce resource and (dynamic) sharing between the device-to-device services and cellular services is more flexible and provides higher spectrum efficiency.
  • the transmission mode when sending data during D2D communication may be either: ⁇ Unicast - a specific terminal device (also known as a user equipment, UE) is the receiver
  • Multicast (may also be denoted groupcast) - a group of UEs are receivers Broadcast - all UEs are receivers
  • connectionless D2D communication data can be sent from one terminal device to another terminal device without prior arrangement, thereby reducing the overhead and increasing the communication capacity which is crucial in emergency situations.
  • the source terminal device transmits data to one (unicast) or more (multicast/groupcast/broadcast) other terminal devices, without first ensuring that the recipients are available and ready to receive the data.
  • Connectionless communication may be used for one-to-one or one-to-many communication, but it is particularly effective for multicast and broadcast transmissions and thus well-suited for broadcast and group communication.
  • connectionless communication may be realized, e.g., via PHY (physical) unicast/multicast/groupcast/broadcast transmissions; with PHY broadcast transmissions, the transmissions may still be turned into unicast/groupcast/multicast at higher layers.
  • PHY physical
  • MAC physical
  • layer multicast or even unicast addresses may be used.
  • IP Internet Protocol addresses may be used at the IP layer.
  • any D2D communication is controlled by the network nodes (such as the eNB). Since the radio resources in a cell (especially the uplink resources) are shared between traditional cellular communication and D2D communication, the eNB should divide and assign the radio resources for D2D communication.
  • a Sidelink UE Information message has been introduced as part of the radio resource control (RRC) protocol (3GPP TS 36.331 v12.5.0).
  • RRC radio resource control
  • This message is used whenever the UE needs to inform the eNB about need for E-UTRAN transmission and/or reception radio resources for ProSe communication or ProSe Discovery.
  • the message contains a list of ProSe destinations, and an index associated to each of these.
  • a ProSe destination is a ProSe Layer 2 Group identity.
  • the index may be used as a 4-bit short reference to a given destination, e.g. as used in a MAC Buffer Status Report when transmitting data to the destination.
  • a given unicast traffic session between two UEs may use either a direct communication path or an infrastructure communication path.
  • the direct communication path also known as "sidelink”
  • the data is transmitted directly between the UEs using D2D communication channels.
  • the infrastructure communication path the data is instead transmitted via one or more network nodes that use non-D2D legacy physical (uplink and downlink) channels, and the packets are transmitted over an EPS (evolved packet system) bearer, which is effectively a tunnel between the UE and the packet data network (PDN) gateway (GW) network node.
  • PDN packet data network gateway
  • a service continuity switch in the context of ProSe communication, is the procedure for moving a user traffic session from the direct communication path to the infrastructure communication path, or vice versa. Service continuity switching for ProSe will likely be included in 3GPP Release 13.
  • a first UE (UE1) 11 is in coverage of a first eNB (eNB1) 13 and is communicating via an infrastructure path with a second UE (UE2) 12 that is in coverage of a second eNB (eNB2) 14).
  • UE2 is referred to as the "peer UE” of UE1 , and vice versa.
  • a user traffic session is maintained even when a UE goes between being in coverage of the network and out of coverage of the network.
  • a first UE (UE1) 21 is communicating with an eNB (eNB1) 22 that generally has a coverage area indicated by dotted line 28 can communicate 'normally' with eNB 22 while in coverage (indicated by the solid arrow). Communications to/from UE1 therefore pass via eNB1 22, a packet data network (PDN) gateway (PGW) 23 (PGW1 ) and a PDN 24.
  • PDN packet data network gateway
  • a second UE (UE2) 25 can act as a relay between UE1 and the PDN 24.
  • UE2 25 is served by a different eNB to UE1 (eNB2 26) and a different PGW (PGW2 27).
  • PGW2 27 PGW
  • UE2 25 is referred to as the "relay UE” of UE1 21
  • UE1 21 the "remote UE” of UE2 25.
  • the relay path is shown by the dashed lines.
  • the objective of service continuity is to keep the session between the two UEs (in the first scenario) or the session between the first UE (UE1) and the network (in the second scenario) considering the UE mobility (either both UE1 and UE2 in the first scenario or only UE1 in the second scenario).
  • it is an objective to provide lossless switching in the above scenarios i.e. to perform switching while ensuring that all data packets reach the intended destination).
  • the packets in the source path would need to be forwarded to target path in order to achieve lossless switching.
  • GTP General Packet Radio Service
  • the method comprises establishing a first forwarding bearer to the first terminal device; and forwarding, to the first terminal device via the first forwarding bearer, data packets of the data session from the first terminal device that have not been received by the second terminal device following initiation of the switch.
  • the method comprises establishing a forwarding bearer with the first RAN node; receiving, from the first RAN node via the forwarding bearer, data packets of the data session previously sent from the first terminal device to the second terminal device that have not been received by the second terminal device following initiation of the switch; and forwarding the received data packets directly to the second terminal device.
  • the first RAN node is in the first routing path and the method comprises establishing a first forwarding bearer to a gateway node in the first routing path; and forwarding, to the gateway node via the first forwarding bearer, data packets of the data session that have not been received by the first terminal device following initiation of the switch.
  • the first gateway node is in the first routing path and the method comprises establishing a first forwarding bearer with a RAN node in the first routing path; receiving, from the RAN node via the first forwarding bearer, data packets of the data session that have not been received by the first terminal device following initiation of the switch; and forwarding the received data packets to a node in the second routing path.
  • terminal devices radio access network nodes, gateway nodes, and computer program products corresponding to the methods recited above.
  • Figure 1 illustrates communications in a two UE scenario
  • Figure 2 illustrates communications in a one UE scenario
  • Figure 3 is a non-limiting example block diagram of a Long Term Evolution (LTE) cellular communications network
  • FIG. 4 is a block diagram of a radio access network (RAN) node according to an embodiment
  • Figure 5 is a block diagram of a terminal device according to an embodiment
  • Figure 6 is a block diagram of a gateway node according to an embodiment
  • Figure 7 is a signalling diagram illustrating the signalling during a switch from routing data via an infrastructure path to routing data via a direct path in the two UE scenario
  • Figure 8 is a flow chart illustrating a method of operating a RAN node according to an embodiment
  • Figure 9 is a flow chart illustrating a method of operating a terminal device according to an embodiment
  • Figure 10 is a signalling diagram illustrating the signalling during a switch from routing data via an infrastructure path to routing data via a direct (relay) path in the one UE scenario;
  • Figure 11 is a signalling diagram illustrating the signalling during a switch from routing data via a direct (relay) path to routing data via an infrastructure path in the two UE scenario;
  • Figure 12 is a flow chart illustrating a method of operating a RAN node according to an embodiment
  • Figure 13 is a flow chart illustrating a method of operating a gateway node according to an embodiment.
  • Hardware implementation may include or encompass, without limitation, digital signal processor (DSP) hardware, a reduced instruction set processor, hardware (e.g., digital or analog) circuitry including but not limited to application specific integrated circuit(s) (ASIC) and/or field programmable gate array(s) (FPGA(s)), and (where appropriate) state machines capable of performing such functions.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • a computer is generally understood to comprise one or more processors, one or more processing modules or one or more controllers, and the terms computer, processor, processing module and controller may be employed interchangeably.
  • processor When provided by a computer, processor, or controller, the functions may be provided by a single dedicated computer or processor or controller, by a single shared computer or processor or controller, or by a plurality of individual computers or processors or controllers, some of which may be shared or distributed.
  • processor or “controller” also refers to other hardware capable of performing such functions and/or executing software, such as the example hardware recited above.
  • UE user equipment
  • UE user equipment
  • a UE herein may comprise a UE (in its general sense) capable of operating or at least performing measurements in one or more frequencies, carrier frequencies, component carriers or frequency bands. It may be a "UE” operating in single- or multi-radio access technology (RAT) or multi-standard mode.
  • RAT radio access technology
  • mobile device and terminal device may be used interchangeably in the following description, and it will be appreciated that such a device does not necessarily have to be 'mobile' in the sense that it is carried by a user. Instead, the term “mobile device” encompasses any device that is capable of communicating with communication networks that operate according to one or more mobile communication standards, such as the Global System for Mobile communications, GSM, Universal Mobile Telecommunications System (UMTS), Long- Term Evolution, LTE, etc.
  • GSM Global System for Mobile communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long- Term Evolution
  • a cell is associated with a base station, where a base station comprises in a general sense any network node transmitting radio signals in the downlink (DL) and/or receiving radio signals in the uplink (UL).
  • Some example base stations, or terms used for describing base stations, are eNodeB, eNB, NodeB, macro/micro/pico/femto radio base station, home eNodeB (also known as femto base station), relay, repeater, sensor, transmitting-only radio nodes or receiving-only radio nodes.
  • a base station may operate or at least perform measurements in one or more frequencies, carrier frequencies or frequency bands and may be capable of carrier aggregation. It may also be a single-radio access technology (RAT), multi-RAT, or multi-standard node, e.g., using the same or different base band modules for different RATs.
  • RAT radio access technology
  • network node can refer to a base station, such as an eNodeB, a network node in the RAN responsible for resource management, such as a radio network controller (RNC), or, in some cases, a core network node, such as a mobility management entity (MME), a ProSe function (ProSe- F) node or a ProSe Application Server.
  • a base station such as an eNodeB
  • RNC radio network controller
  • MME mobility management entity
  • ProSe- F ProSe function
  • ProSe Application Server a ProSe Application Server
  • FIG. 3 shows an example diagram of an evolved UMTS Terrestrial Radio Access Network (E-UTRAN) architecture as part of a Long Term Evolution (LTE)-based communications system 32.
  • Nodes in the core network 34 include one or more Mobility Management Entities (MMEs) 35, a key control node for the LTE access network, one or more Serving Gateways (SGWs) 36 which route and forward user data packets while acting as a mobility anchor, a ProSe Function node 37, a ProSe Application Server 38 and a home subscriber server (HSS) 39.
  • MMEs Mobility Management Entities
  • SGWs Serving Gateways
  • HSS home subscriber server
  • the ProSe Function node 37 is used for network related actions required for ProSe, such as provisioning the UEs with necessary parameters to use ProSe, and network support for ProSe direct discovery and EPC-level discovery.
  • the Application server 38 provides network functionality required by the application in the UEs based on ProSe communication and/or discovery, for example a Mission-Critical Push-To-Talk (MCPTT) application server.
  • MCPTT Mission-Critical Push-To-Talk
  • the application server 38 is connected with the ProSe-Function node 37, which in turn is connected with the HSS 39 that is a database that contains user-related and subscriber-related information.
  • the HSS 39 is connected to the MME 35.
  • the MME(s) 35 and SGW(s) 36 communicate with base stations 40 referred to in LTE as eNBs, over an interface, for example an S1 interface.
  • the eNBs 40 can include the same or different categories of eNBs, e.g. macro eNBs, and/or micro/pico/femto eNBs.
  • the eNBs 40 communicate with each other over an interface, for example an X2 interface.
  • the S1 interface and X2 interface are defined in the LTE standard.
  • a UE 42 is shown, and a UE 42 can receive downlink data from and send uplink data to one of the base stations 40 with that base station 40 being referred to as the serving base station of the UE 42.
  • UE 42 is configured or adapted to be able to communicate with another UE in D2D mode (i.e. communicate directly with the other UE without routing the communications via one or more eNBs 40).
  • UE 42 may also be configured or adapted to be able to communicate with another UE in local routing mode (i.e. communicate with the other UE via one or more eNBs 40).
  • the eNBs are configured or adapted to enable local routing between UEs 40.
  • Figure 4 shows a radio access network, RAN, node that can be adapted or configured to operate according to the example embodiments described.
  • the network node can be a base station 40 (for example a NodeB or an eNodeB as shown in Figures 1 and 2) or other node in the radio access network (RAN) of the network 32.
  • RAN radio access network
  • the RAN node 40 comprises a processor or processing module 60 that controls the operation of the RAN node.
  • the processing module 60 can be connected to a transceiver module 62 (which comprises a receiver and a transmitter) with associated antenna(s) 64 which are used to transmit signals to, and receive signals from, UEs 42 in the network 32.
  • the RAN node also comprises a memory or memory module 66 that is connected to the processing module 60 and that contains instructions or computer code executable by the processor 60 and other information or data required for the operation of the network node.
  • the RAN node also includes components and/or circuitry 68 for allowing the RAN node to exchange information with other network nodes.
  • the circuitry 68 can allow the RAN node to communicate with other RAN nodes via an X2 interface and/or communicate with network nodes in the core network via an S1 or other type of interface.
  • RAN nodes for use in other types of network e.g. UMTS Terrestrial Radio Access Network (UTRAN) or Wideband Code Division Multiple Access (WCDMA) RAN
  • UTRAN UMTS Terrestrial Radio Access Network
  • WCDMA Wideband Code Division Multiple Access
  • FIG. 5 shows a terminal device 42 or user equipment (UE) that can be adapted for use in one or more of the non-limiting example embodiments described.
  • the terminal device 42 comprises a processing module 70 that controls the operation of the terminal device 42.
  • the processing unit 70 is connected to receiver circuitry, transmitter circuitry or transceiver circuitry 72 (which comprises a receiver and a transmitter) with associated antenna(s) 74 which are used to receive signals from or both transmit signals to and receive signals from a radio access network, such as RAN node 40 in the LTE network 32.
  • Circuitry 72 is also configured to enable the terminal device 42 to communicate with other terminal devices 42 using D2D communications.
  • the terminal device 42 also comprises a memory module 76 that is connected to the processing module 70 and that stores computer program code and other information and data required for the operation of the terminal device 42.
  • FIG. 6 shows a gateway node 23; 27 that can be used in the example embodiments described.
  • the gateway node 23; 27 can be a node that controls the operations of one or more RAN nodes 40.
  • the gateway node 23; 27 can be a PGW 23; 27 or a SGW 36.
  • the gateway node 23; 27 comprises a processing module 82 that controls the operation of the gateway node 23; 27.
  • the processing module 82 is connected to inter-node interface circuitry 84 for allowing the gateway node 23; 27 to exchange information with RAN nodes 40 with which it is associated.
  • the gateway node 23; 27 also comprises a memory module 86 that is connected to the processing unit 82 and that stores computer program code and other information and data required for the operation of the gateway node 23; 27. It will be appreciated that only the components of the terminal device 42, RAN node 40 and gateway node 23; 27 required to explain the embodiments presented herein are illustrated in Figures 4, 5 and 6.
  • two UEs that are communicating with each other via an infrastructure path can switch to using a ProSe Direct Communication path when the UEs are within proximity of each other.
  • an infrastructure path e.g. via one or more eNBs and also possibly a core network
  • the infrastructure path fails (e.g. where UE2 12 moves out of coverage of eNB2) - which can be the trigger to switch to the direct routing path 18, there may be some packets sent by UE1 11 that have not yet arrived at UE2 12.
  • Figure 7 illustrates the signalling used to achieve lossless signalling according to an embodiment.
  • Figure 7 shows the signalling between UE1 1 1 , the serving eNB 13 of UE1 (eNB1), UE2 12 (the UE2 that loses coverage with the network), and eNB2 14 (the serving eNB of UE2 before UE2 loses coverage).
  • the two UEs have a communication session that uses conventional cellular mode communication for the packet transmission (which is also known as the infrastructure routing path).
  • a decision is made to switch to use D2D communication for the packets in this communication session.
  • the trigger for the decision can be one or more measurement reports from one or both UEs, and the entity taking the decision can be a network node on either the UE1 side or UE2 side (e.g.
  • the switching decision in the general case, is performed per direction. In this example, the switching decision is made for the packets being sent from UE1 to UE2. The packets being sent in the opposite direction can therefore be subject to a separate switching decision (although this does not have to be the case).
  • forwarding bearers are established between eNB2, eNB1 and UE1 to enable the packets to be returned to UE1 so that they can be retransmitted by UE1 to UE2 when the direct communication path is established.
  • eNB2 therefore sends a signal 703 to eNB1 to establish a forwarding bearer to eNB1 (although in some embodiments eNB1 can send signal 703 to eNB2 instead), and eNB1 sends a signal 704 to UE1 to establish a forwarding bearer to UE1.
  • Signal 703 can be sent via the X2 interface between the eNBs (although optionally it can be sent through SGW 36 via the S1 interface), and can make use of existing X2 HO preparation signalling.
  • the forwarding bearer to UE1 can reuse the existing data radio bearer (DRB) for UE1 , which means it possibly co-exists with other Internet Protocol, IP, flows in the same bearers, so that UE1 can only differentiate the packet at IP layer or higher, e.g., based on the source/destination IP address.
  • the forwarding bearer can be a dedicated DRB for UE1 which means it can have dedicated QoS (quality of service) control with respect to the direct path, so that UE1 can differentiate the packets at a lower layer, based on the LCID (logical channel ID).
  • eNB1 So that UE1 is aware that data packets received via the forwarding bearer are to be sent to UE2, eNB1 provides an indication to UE1 that data packets received via the bearer are to be sent to UE2. In some embodiments, eNB1 can indicate to UE1 that the forwarding bearer is linked to a bearer used for the retransmission of packets to UE2, and vice versa, and this link can be signalled when the forwarding bearer and/or the other bearer is established.
  • eNB2 forwards any data packets from UE1 that have not been received by UE2 (which can include packets stored or buffered in UE2 that were not sent to UE2 before the switch was triggered, and/or packets that were sent to UE2 but not acknowledged by UE2) to eNB1 (signal 705). eNB1 then forwards the data packets to UE1 (signal 706) via the forwarding bearer to UE1.
  • UE1 forwards the data packets received from eNB1 directly to UE2 (indicated by signal 707).
  • UE1 can start to transmit new data packets to UE2 using the direct communication path (signal 708).
  • This signalling may indicate to UE1 to stop the transmission along the cellular path, and be ready to send the forwarded packets (received from eNB1) to UE2 via the direct path.
  • This signalling may indicate to UE2 (assuming that eNB2 can still send signals to UE2) that it should stop the reception of data packets along the cellular path, and be ready to receive data packets (included any forwarded data packets) from UE1 via a direct path.
  • eNB1 may indicate the end of the forwarded packets (i.e. the last of the forwarded packets) to UE1 so that UE1 knows when to start the transmission of new data packets to UE2 via the direct communication path 708.
  • an 'End marker' or other signal indicating a last data packet can be sent from eNB1 to UE1 at the point that uplink transmission of data packets from UE1 to UE2 is prevented.
  • UE1 can be notified of the end marker in the form of Uu data/signalling, e.g., RRC or MAC CE signalling, empty packet data convergence protocol (PDCP)/radio link control (RLC)/MAC packets, etc.
  • Uu data/signalling e.g., RRC or MAC CE signalling, empty packet data convergence protocol (PDCP)/radio link control (RLC)/MAC packets, etc.
  • forwarding bearers are established after the switching decision (step 702) is taken, it will be appreciated that in some embodiments the forwarding bearers may already be established when the switching decision is taken. For example, the forwarding bearers may be established when the data session with UE1 is set up. In addition or alternatively, forwarding bearers can be established when a switch may be imminent, for example based on a measurement report from a UE.
  • the flow chart in Figure 8 illustrates a method of operating a RAN node according to an embodiment.
  • the RAN node corresponds to eNB1 13 in Figure 7.
  • the RAN node 13 is operated to maintain service continuity for a data session from a first terminal device 1 1 to a second terminal device 12 during a switch from routing the data session via the RAN node 13 to routing the data session directly from the first terminal device 1 1 to the second terminal device 12.
  • step 801 a forwarding bearer is established to the first terminal device.
  • the flow chart in Figure 9 illustrates a method of operating a terminal device according to an embodiment.
  • the terminal device corresponds to UE1 in Figure 7.
  • the terminal device is operated to maintain service continuity for a data session from the terminal device 1 1 to a second terminal device 12 during a switch from routing the data session via a first RAN node 13 to routing the data session directly from the terminal device 1 1 to the second terminal device 12.
  • a forwarding bearer is established with the first RAN node 13. Then, the terminal device 11 receives, from the first RAN node 13 via the forwarding bearer, data packets of the data session previously sent from the terminal device 1 1 to the second terminal device 12 that have not been received by the second terminal device 12 following initiation of the switch (step 903).
  • the received data packets are then forwarded directly to the second terminal device 12 (step 905).
  • a first UE (UE1) 21 passes via eNB1 22, PGW1 23 and PDN 24.
  • This is referred to as the infrastructure path.
  • UE1 21 loses coverage from eNB1 22, a second UE (UE2) 25 can act as a relay between UE1 and the PDN 24, and in Figure 2 UE2 25 is served by eNB2 26 and PGW2 27.
  • UE2 25 is referred to as the "relay UE" of UE1 21
  • UE1 21 the "remote UE" of UE2 25.
  • the packets in the infrastructure path need to be forwarded to the direct path.
  • Figure 10 illustrates the signalling used to achieve lossless signalling according to an embodiment.
  • Figure 10 shows the signalling between UE1 21 (the remote UE that loses coverage from the network), the serving eNB of UE1 (eNB1 22), the serving PGW of UE1 (PGW1 23), the PDN 24, UE2 25 (the relay UE), eNB2 26 (the serving eNB of UE2) and the serving PGW of UE2 (PGW2 27).
  • UE1 has a PDN connection towards the network in which data packets for UE1 are transmitted over evolved packet system (EPS) bearers using an infrastructure communication path (i.e.
  • EPS evolved packet system
  • a decision is made to switch UE1 to using UE2 as a relay UE for data packets in UE1's communication session.
  • the trigger for the decision can be one or more measurement reports from one or both UEs, and the entity taking the decision can be a network node on either the UE1 side or UE2 side (e.g. an eNB, an MME, a PGW, or even a ProSe-F node).
  • forwarding bearers are established between eNB1 , PGW1 and PGW2 to enable the packets to be rerouted to PGW2 and then to UE1 via the relay UE (UE2) once the direct communication path is established.
  • PGW1 therefore sends a signal 1003 to PGW2 to establish a forwarding bearer to PGW2 (although in some embodiments PGW2 can send signal 1003 to PGW1 instead), and PGW1 sends a signal 1004 to eNB1 to establish a forwarding bearer from eNB1 to PGW1 (although in some embodiments eNB1 can send signal 1004 to PGW1 instead).
  • signal 1003 can reuse the registration request/response signalling in a mobile IP procedure to establish the forwarding bearer (e.g. IP tunnel) between the two PGWs.
  • the forwarding bearer e.g. IP tunnel
  • eNB1 forwards any data packets from PDN 24 that have not been received by UE1 (which can include packets stored or buffered in eNB1 that were not sent to UE1 before the switch was triggered, and/or packets that were sent to UE1 but not acknowledged by UE1) back up to PGW1 via the forwarding bearer (signal 1005).
  • PGW1 then forwards the data packets to PGW2 (signal 1006) via the forwarding bearer between the PGWs, and PGW2 reroutes the packets back to the GTP tunnel of the relay UE.
  • PGW2 sends the data packets to the serving eNB of UE2 (eNB2 26), signal 1007.
  • eNB2 transmits the data packets to UE2 (signal 1008)
  • UE2 transmits the data packets to UE1 (signal 1009) when the direct communication path is established between UE1 and UE2.
  • new data packets from PDN 24 are sent to UE1 via PGW2, eNB2 and UE2 (indicated by the group of signals labelled 1010).
  • PGW2 eNB2
  • UE2 UE2
  • eNB1 stops the downlink transmission of data packets to UE1 , and data packets received from PGW1 are sent back to PGW1 on the forwarding bearer, so that PGW1 can forward them to the relay UE side.
  • PGW1 may indicate the end of the downlink data packets (i.e. the last of the data packets for UE1 sent to eNB1) to eNB1.
  • eNB1 forwards the last of the data packets to PGW1
  • eNB1 includes an 'end marker' or other signal indicating a last data packet to indicate this to PGW1.
  • PGW1 can send the end marker to PGW2 after the last data packet is forwarded from PGW1 to PGW2 so PGW2 knows when to start the transmission of new data packets to UE1 via UE2.
  • the 'end marker' might go through multiple PGWs to reach UE1 , so PGWs require the capability to forward the end marker information as a special IP packet.
  • eNB1 establishes the forwarding bearer with PGW1 , forwards any data packets to PGW1 , and then PGW1 sends them to eNB2.
  • forwarding bearers are established after the switching decision (step 1002) is taken, it will be appreciated that in some embodiments the forwarding bearers may already be established when the switching decision is taken. For example, the forwarding bearers may be established when the data session with UE1 is set up. In addition or alternatively, forwarding bearers can be established when a switch may be imminent, for example based on a measurement report from a UE.
  • a first UE (UE1) 21 passes via a relay UE (UE2 25), eNB2 26 (the serving eNB of UE2), PGW2 27 (the serving PGW of UE2) and PDN 24.
  • UE2 25 the relay UE
  • eNB2 26 the serving eNB of UE2
  • PGW2 27 the serving PGW of UE2
  • PDN 24 the serving PDN 24.
  • the direct path may have been established due to UE1 losing coverage from the network (although other reasons are possible). If UE1 21 subsequently regains coverage from the network (e.g. it is within the coverage of eNB1 22), it can switch back to using an infrastructure path via eNB1.
  • the packets in the direct path need to be forwarded to the infrastructure path.
  • Figure 1 1 illustrates the signalling used to achieve lossless signalling according to an embodiment.
  • Figure 1 1 shows the signalling between UE1 21 (the remote UE that is receiving data packets via a relay UE), the serving eNB of UE1 (eNB1 22), the serving PGW of UE1 (PGW1 23), the PDN 24, UE2 25 (the relay UE), eNB2 26 (the serving eNB of UE2) and the serving PGW of UE2 (PGW2 27).
  • UE1 is receiving data packets from PDN 24 via UE2 25 (i.e. from PDN 24 to PGW2, from PGW2 to eNB2, from eNB2 to UE2 and from UE2 to UE1).
  • a decision is made to switch UE1 to using the infrastructure path (i.e. to stop using UE2 as a relay UE for data packets in UE1 's communication session).
  • the trigger for the decision can be one or more measurement reports from one or both UEs, and the entity taking the decision can be a network node on either the UE1 side or UE2 side (e.g. an eNB, an MME, a PGW, or even a ProSe-F node).
  • forwarding bearers are established between eNB2, PGW2 and PGW1 to enable the packets to be rerouted to PGW1 and then to UE1 once the infrastructure communication path is established.
  • PGW2 therefore sends a signal 1 103 to PGW1 to establish a forwarding bearer to PGW1 (although in some embodiments PGW1 can send signal 1 103 to PGW2 instead), and PGW2 sends a signal 1104 to eNB2 to establish a forwarding bearer from eNB2 to PGW2 (although in some embodiments eNB2 can send signal 1104 to PGW2 instead).
  • the forwarding bearer from eNB2 to PGW2 requires bearer differentiation (between the relay UE (UE2) and the remote UE (UE1), or between multiple remote UEs) capability at eNB2, so that different GTP tunnels would be used by different UEs (relay UE and remote UEs), and to map to a single DRB between eNB2 and UE1.
  • signal 1 103 can reuse the registration request/response signalling in a mobile IP procedure to establish the forwarding bearer (e.g. IP tunnel) between the two PGWs.
  • eNB2 forwards any data packets from PDN 24 that have not been received by UE1 (which can include packets stored or buffered in eNB2 that were not sent to UE2 for relaying to UE1 before the switch was triggered, and/or packets that were sent to UE1 but not acknowledged by UE1) back up to PGW2 via the forwarding bearer (signal 1 105).
  • PGW2 then forwards the data packets to PGW1 (signal 1 106) via the forwarding bearer between the PGWs, and PGW1 reroutes the packets back to UE1 via the infrastructure path.
  • PGW1 sends the data packets to the serving eNB of UE1 (eNB1 22), signal 1 107.
  • eNB1 then transmits the data packets to UE1 (signal 1108) when the infrastructure communication path is established between UE1 and eNB1.
  • new data packets from PDN 24 are sent to UE1 via PGW1 and eNB1 (indicated by the group of signals labelled 1109).
  • This signalling may be from PGW2 to eNB2, or from an MME 35 to eNB2.
  • eNB2 stops the downlink transmission of data packets to UE1 via UE2, and data packets received from PGW2 are sent back to PGW2 via the forwarding bearer, so that PGW2 can forward them to the remote UE side.
  • PGW2 may indicate the end of the downlink data packets (i.e. the last of the data packets for UE1 sent to eNB2) to eNB2.
  • eNB2 When eNB2 forwards the last of the data packets to PGW2, eNB2 includes an 'end marker' or other signal indicating a last data packet to indicate this to PGW2.
  • PGW2 can send the end marker to PGW1 after the last data packet is forwarded from PGW2 to PGW1 so PGW1 knows when to start the transmission of new data packets to UE1 via eNB1.
  • the 'end marker' might go through multiple PGWs to reach UE1 , so PGWs require the capability to forward the end marker information as a special IP packet.
  • eNB2 establishes the forwarding bearer with PGW1 , forwards any data packets to PGW1 , and then PGW1 sends them to eNB1.
  • forwarding bearers are established after the switching decision (step 1 102) is taken, it will be appreciated that in some embodiments the forwarding bearers may already be established when the switching decision is taken. For example, the forwarding bearers may be established when the data session with UE1 is set up. In addition or alternatively, forwarding bearers can be established when a switch may be imminent, for example based on a measurement report from a UE.
  • the flow chart in Figure 12 illustrates a method of operating a RAN node according to an embodiment.
  • the RAN node corresponds to eNB1 22 in Figure 10 and eNB2 26 in Figure 1 1.
  • the RAN node is operated to maintain service continuity for a data session to a first terminal device 21 during a switch from a first routing path to a second routing path (the RAN node is in the first routing path).
  • the first and second routing paths comprises a routing path in which the data session is routed via a RAN node 22 that is serving the first terminal device 21 , and a routing path in which the data session is routed to the first terminal device 21 via a relay terminal device 25.
  • a forwarding bearer is established to a gateway node 23, 27 in the first routing path.
  • step 1203 data packets of the data session that have not been received by the first terminal device 21 following initiation of the switch are forwarded to the gateway node 23, 27 via the first forwarding bearer.
  • the flow chart in Figure 13 illustrates a method of operating a gateway node according to an embodiment.
  • the gateway node corresponds to PGW1 23 in Figure 10 and PGW2 27 in Figure 11.
  • the gateway node is operated to maintain service continuity for a data session to a first terminal device 21 during a switch from the first routing path to the second routing path (with the gateway node being in the first routing path).
  • a forwarding bearer is established with a RAN node 22, 26 in the first routing path.
  • the gateway node then receives, from the RAN node via the first forwarding bearer, data packets of the data session that have not been received by the first terminal device 21 following initiation of the switch (step 1303).
  • the received data packets are then forwarded to a node in the second routing path, such as a RAN node or another gateway node (step 1305).
  • a node in the second routing path such as a RAN node or another gateway node (step 1305).
  • the techniques described above allow for service continuity during switching between infrastructure and direct routing paths to reduce packet loss and session interruptions due to packet re-transmission.
  • the data packets of the data session from the first terminal device that have not been received by the second terminal device following initiation of the switch are received from the second RAN node via the second forwarding bearer and sent to the first terminal device via the first forwarding bearer.
  • the first forwarding bearer is an existing data radio bearer, DRB, to the first terminal device that is used for the data session.
  • the first forwarding bearer is a data radio bearer, DRB, to the first terminal device that is dedicated to the forwarding of data packets that have not been received by the second terminal device following initiation of the switch.
  • a first radio access network, RAN, node for use in maintaining service continuity for a data session from a first terminal device to a second terminal device during a switch from routing the data session via the first RAN node to routing the data session directly from the first terminal device to the second terminal device, the first RAN node being adapted to:
  • a first RAN node as defined in statement 9 wherein the first RAN node is a serving node for the first terminal device, and the second terminal device is served by a second RAN node. 12.
  • a first RAN node as defined in statement 11 further adapted to:
  • a first RAN node as defined in any of statements 9-12, wherein the first forwarding bearer is an existing data radio bearer, DRB, to the first terminal device that is used for the data session.
  • DRB data radio bearer
  • the first forwarding bearer is an existing data radio bearer, DRB, that is used for the data session.
  • the first forwarding bearer is a data radio bearer, DRB, to the first terminal device that is dedicated to the forwarding of data packets that have not been received by the second terminal device following initiation of the switch.
  • DRB data radio bearer
  • a first terminal device for use in maintaining service continuity for a data session from the first terminal device to a second terminal device during a switch from routing the data session via a first radio access network, RAN, node to routing the data session directly from the first terminal device to the second terminal device, the first terminal device being adapted to: establish a forwarding bearer with the first RAN node;
  • DRB data radio bearer
  • a computer program product having computer readable code embodied therein, the computer readable code being configured such that, on execution by a suitable computer or processor, the computer or processor performs the method as defined in any of statements 1-8 or 17-22.
  • a first radio access network, RAN, node for use in maintaining service continuity for a data session from a first terminal device to a second terminal device during a switch from routing the data session via the first RAN node to routing the data session directly from the first terminal device to the second terminal device the first RAN node comprising a processor and a memory, said memory containing instructions executable by said processor whereby said first RAN node is operative to:
  • DRB data radio bearer
  • DRB data radio bearer
  • a first terminal device for use in maintaining service continuity for a data session from the first terminal device to a second terminal device during a switch from routing the data session via a first radio access network, RAN, node to routing the data session directly from the first terminal device to the second terminal device, the first terminal device comprising a processor and a memory, said memory containing instructions executable by said processor whereby said first terminal device is operative to:
  • DRB existing data radio bearer
  • a first terminal device as defined in statement 41 wherein new data packets are data packets in a transmission buffer of the first terminal device that have not yet been sent to the second terminal device.
  • a method as defined in statement 44 wherein the first routing path is the routing path in which the data session is routed via a RAN node that is serving the first terminal device and the second routing path is the routing path in which the data session is routed to the first terminal device via a relay terminal device; and wherein the first RAN node is the RAN node serving the first terminal device.
  • the gateway node receiving a first signal from the gateway node, the first signal indicating a last data packet that is to be sent to the first terminal device;
  • a first radio access network, RAN, node for use in maintaining service continuity for a data session to a first terminal device during a switch from a first routing path to a second routing path, the first and second routing paths comprising a routing path in which the data session is routed via a RAN node that is serving the first terminal device, and a routing path in which the data session is routed to the first terminal device via a relay terminal device, wherein the first RAN node is in the first routing path, the first RAN node being adapted to:
  • a first RAN node as defined in statement 48 wherein the first routing path is the routing path in which the data session is routed via a RAN node that is serving the first terminal device and the second routing path is the routing path in which the data session is routed to the first terminal device via a relay terminal device; and wherein the first RAN node is the RAN node serving the first terminal device.
  • the gateway node receives a first signal from the gateway node, the first signal indicating a last data packet that is to be sent to the first terminal device;
  • a method as defined in statement 52 wherein the first routing path is the routing path in which the data session is routed via a RAN node that is serving the first terminal device and the second routing path is the routing path in which the data session is routed to the first terminal device via a relay terminal device; and wherein the first forwarding bearer is established with the RAN node that is serving the first terminal.
  • the step of forwarding the received data packets comprises forwarding the received data packets to a second gateway node that is serving the relay terminal device.
  • a method as defined in statement 52 wherein the first routing path is the routing path in which the data session is routed to the first terminal device via a relay terminal device and the second routing path is the routing path in which the data session is routed via a RAN node that is serving the first terminal device; and wherein the first forwarding bearer is established with a RAN node that is serving the relay terminal device.
  • a method as defined in statement 56, wherein the step of forwarding the received data packets comprises forwarding the received data packets to a second gateway node that is serving the first terminal device.
  • the first gateway node is serving the first terminal device and the relay terminal device and wherein the step of forwarding the received data packets comprises forwarding the received data packets to the RAN node that is serving the first terminal device.
  • a first gateway node for use in maintaining service continuity for a data session to a first terminal device during a switch from a first routing path to a second routing path, the first and second routing paths comprising a routing path in which the data session is routed via a radio access network, RAN, node that is serving the first terminal device, and a routing path in which the data session is routed to the first terminal device via a relay terminal device, wherein the first gateway node is in the first routing path, the first gateway node being adapted to: establish a first forwarding bearer with a RAN node in the first routing path;
  • a first gateway node as defined in statement 61 wherein the first routing path is the routing path in which the data session is routed via a RAN node that is serving the first terminal device and the second routing path is the routing path in which the data session is routed to the first terminal device via a relay terminal device; and wherein the first forwarding bearer is established with the RAN node that is serving the first terminal.
  • a first gateway node as defined in statement 61 wherein the first routing path is the routing path in which the data session is routed to the first terminal device via a relay terminal device and the second routing path is the routing path in which the data session is routed via a RAN node that is serving the first terminal device; and wherein the first forwarding bearer is established with a RAN node that is serving the relay terminal device.
  • the first gateway node is adapted to forward the received data packets to a second gateway node that is serving the first terminal device.
  • a computer program product comprising a computer readable medium having computer readable code embodied therein, the computer readable code being configured such that, on execution by a suitable computer or processor, the computer or processor is caused to perform the method of any of statements 44-47 and 52-60. 71 .
  • a first radio access network, RAN, node for use in maintaining service continuity for a data session to a first terminal device during a switch from a first routing path to a second routing path, the first and second routing paths comprising a routing path in which the data session is routed via a RAN node that is serving the first terminal device, and a routing path in which the data session is routed to the first terminal device via a relay terminal device, wherein the first RAN node is in the first routing path, the first RAN node comprising a processor and a memory, said memory containing instructions executable by said processor whereby said first RAN node is operative to:
  • a first RAN node as defined in statement 71 wherein the first routing path is the routing path in which the data session is routed to the first terminal device via a relay terminal device and the second routing path is the routing path in which the data session is routed via a RAN node that is serving the first terminal device; and wherein the first RAN node is a RAN node serving the relay terminal device.
  • the RAN node being further operative to:
  • the gateway node receives a first signal from the gateway node, the first signal indicating a last data packet that is to be sent to the first terminal device;
  • a first gateway node for use in maintaining service continuity for a data session to a first terminal device during a switch from a first routing path to a second routing path, the first and second routing paths comprising a routing path in which the data session is routed via a radio access network, RAN, node that is serving the first terminal device, and a routing path in which the data session is routed to the first terminal device via a relay terminal device, wherein the first gateway node is in the first routing path, the first gateway node comprising a processor and a memory, said memory containing instructions executable by said processor whereby said first gateway node is operative to:
  • a first gateway node as defined in statement 75 wherein the first routing path is the routing path in which the data session is routed via a RAN node that is serving the first terminal device and the second routing path is the routing path in which the data session is routed to the first terminal device via a relay terminal device; and wherein the first forwarding bearer is established with the RAN node that is serving the first terminal.
  • a first gateway node as defined in statement 75 wherein the first routing path is the routing path in which the data session is routed to the first terminal device via a relay terminal device and the second routing path is the routing path in which the data session is routed via a RAN node that is serving the first terminal device; and wherein the first forwarding bearer is established with a RAN node that is serving the relay terminal device.
  • 80. A first gateway node as defined in statement 79, wherein the first gateway node is operative to forward the received data packets to a second gateway node that is serving the first terminal device.
  • a first module configured to establish a first forwarding bearer to the first terminal device
  • a second module configured to forward, to the first terminal device via the first forwarding bearer, data packets of the data session from the first terminal device that have not been received by the second terminal device following initiation of the switch.
  • a first module configured to establish a forwarding bearer with the first RAN node; a second module configured to receive, from the first RAN node via the forwarding bearer, data packets of the data session previously sent from the first terminal device to the second terminal device that have not been received by the second terminal device following initiation of the switch;
  • a third module configured to forward the received data packets directly to the second terminal device.
  • a first radio access network, RAN, node for use in maintaining service continuity for a data session to a first terminal device during a switch from a first routing path to a second routing path, the first and second routing paths comprising a routing path in which the data session is routed via a RAN node that is serving the first terminal device, and a routing path in which the data session is routed to the first terminal device via a relay terminal device, wherein the first RAN node is in the first routing path, the first RAN node comprising: a first module configured to establish a first forwarding bearer to a gateway node in the first routing path; and
  • a second module configured to forward, to the gateway node via the first forwarding bearer, data packets of the data session that have not been received by the first terminal device following initiation of the switch.
  • a first gateway node for use in maintaining service continuity for a data session to a first terminal device during a switch from a first routing path to a second routing path, the first and second routing paths comprising a routing path in which the data session is routed via a radio access network, RAN, node that is serving the first terminal device, and a routing path in which the data session is routed to the first terminal device via a relay terminal device, wherein the first gateway node is in the first routing path, the first gateway node comprising:
  • a first module configured to establish a first forwarding bearer with a RAN node in the first routing path
  • a second module configured to receive, from the RAN node via the first forwarding bearer, data packets of the data session that have not been received by the first terminal device following initiation of the switch;
  • a third module configured to forward the received data packets to a node in the second routing path.

Landscapes

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

Abstract

Selon un aspect, l'invention concerne un procédé de fonctionnement d'un premier réseau d'accès radio, RAN, un nœud (13) pour conserver la continuité de service pour une session de données à partir d'un premier dispositif terminal (11) vers un second dispositif terminal (12) lors d'une commutation entre un routage de la session de données par l'intermédiaire du premier nœud RAN (13) et un routage de la session de données directement à partir du premier dispositif terminal (11) vers le second dispositif terminal (12). Le procédé consiste à établir une première porteuse de transmission vers le premier dispositif terminal (11) ; et transmettre, au premier dispositif terminal (11) par l'intermédiaire de la première porteuse de transmission, des paquets de données de la session de données provenant du premier dispositif terminal (11) qui n'ont pas été reçus par le second dispositif terminal (12) qui suivent le lancement de la commutation.
PCT/SE2015/050388 2015-03-31 2015-03-31 Continuité de service WO2016159841A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/SE2015/050388 WO2016159841A1 (fr) 2015-03-31 2015-03-31 Continuité de service

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/SE2015/050388 WO2016159841A1 (fr) 2015-03-31 2015-03-31 Continuité de service

Publications (1)

Publication Number Publication Date
WO2016159841A1 true WO2016159841A1 (fr) 2016-10-06

Family

ID=52991927

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2015/050388 WO2016159841A1 (fr) 2015-03-31 2015-03-31 Continuité de service

Country Status (1)

Country Link
WO (1) WO2016159841A1 (fr)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018166326A1 (fr) * 2017-03-16 2018-09-20 中兴通讯股份有限公司 Procédé et système de gestion d'informations d'utilisateur
WO2018171881A1 (fr) * 2017-03-22 2018-09-27 Nokia Technologies Oy Support de transfert de données
CN109391603A (zh) * 2017-08-11 2019-02-26 华为技术有限公司 数据完整性保护方法和装置
CN109688608A (zh) * 2019-01-02 2019-04-26 广州汇智通信技术有限公司 一种语音数据分流方法和系统
WO2019214384A1 (fr) * 2018-05-11 2019-11-14 华为技术有限公司 Procédé et dispositif de communication
WO2022113875A1 (fr) * 2020-11-24 2022-06-02 三菱電機株式会社 Système et terminal de communication
WO2023020481A1 (fr) * 2021-08-20 2023-02-23 华为技术有限公司 Procédé de transmission de données et appareil

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100279672A1 (en) * 2009-04-29 2010-11-04 Nokia Corporation Apparatus and Method for Flexible Switching Between Device-to-Device Communication Mode and Cellular Communication Mode
US20100322194A1 (en) * 2009-06-19 2010-12-23 Research In Motion Limited Mechanisms for Data Handling During a Relay Handover with S1 Termination at Evolved Universal Terrestrial Radio Access Network Access Node
EP2306765A1 (fr) * 2009-10-02 2011-04-06 Research in Motion Limited Système et procédé pour le transfert entre relais
US20130265974A1 (en) * 2010-12-14 2013-10-10 Vinh Van Phan Mode switching
US20140160950A1 (en) * 2012-12-07 2014-06-12 Alcatel-Lucent Usa Inc. Methods and apparatuses for facilitating d2d bearer switching

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100279672A1 (en) * 2009-04-29 2010-11-04 Nokia Corporation Apparatus and Method for Flexible Switching Between Device-to-Device Communication Mode and Cellular Communication Mode
US20100322194A1 (en) * 2009-06-19 2010-12-23 Research In Motion Limited Mechanisms for Data Handling During a Relay Handover with S1 Termination at Evolved Universal Terrestrial Radio Access Network Access Node
EP2306765A1 (fr) * 2009-10-02 2011-04-06 Research in Motion Limited Système et procédé pour le transfert entre relais
US20130265974A1 (en) * 2010-12-14 2013-10-10 Vinh Van Phan Mode switching
US20140160950A1 (en) * 2012-12-07 2014-06-12 Alcatel-Lucent Usa Inc. Methods and apparatuses for facilitating d2d bearer switching

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11647551B2 (en) 2017-03-16 2023-05-09 Zte Corporation Method and system for user information management
WO2018166326A1 (fr) * 2017-03-16 2018-09-20 中兴通讯股份有限公司 Procédé et système de gestion d'informations d'utilisateur
US11089640B2 (en) 2017-03-16 2021-08-10 Zte Corporation Method and system for user information management
WO2018171881A1 (fr) * 2017-03-22 2018-09-27 Nokia Technologies Oy Support de transfert de données
US11147122B2 (en) 2017-03-22 2021-10-12 Nokia Technologies Oy Data forwarding support
CN109391603A (zh) * 2017-08-11 2019-02-26 华为技术有限公司 数据完整性保护方法和装置
US11025645B2 (en) 2017-08-11 2021-06-01 Huawei Technologies Co., Ltd. Data integrity protection method and apparatus
CN109391603B (zh) * 2017-08-11 2021-07-09 华为技术有限公司 数据完整性保护方法和装置
US11818139B2 (en) 2017-08-11 2023-11-14 Huawei Technologies Co., Ltd. Data integrity protection method and apparatus
WO2019214384A1 (fr) * 2018-05-11 2019-11-14 华为技术有限公司 Procédé et dispositif de communication
CN109688608A (zh) * 2019-01-02 2019-04-26 广州汇智通信技术有限公司 一种语音数据分流方法和系统
CN109688608B (zh) * 2019-01-02 2022-04-15 广州汇智通信技术有限公司 一种语音数据分流方法和系统
WO2022113875A1 (fr) * 2020-11-24 2022-06-02 三菱電機株式会社 Système et terminal de communication
WO2023020481A1 (fr) * 2021-08-20 2023-02-23 华为技术有限公司 Procédé de transmission de données et appareil

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
US11356924B2 (en) Radio communication system, base station, mobile station, communication control method, and computer readable medium
US10419985B2 (en) Method of supporting access network handover operation of user equipment in wireless communication system and apparatus for the same
CN110831095B (zh) 通信方法和通信装置
JP2023155461A (ja) デバイスツーデバイス（ｄ２ｄ）通信のモバイル中継器の実現
JP2021153323A (ja) 無線通信システムにおける次のメッセージのために使われるベアラのタイプを指示する方法及び装置
CN111602462A (zh) 用户设备、节点以及在其中执行的方法
US20190274076A1 (en) Method for supporting ue mobility in wireless communication system and device therefor
JP6259125B2 (ja) 無線通信システムにおけるＤ２Ｄ（ｄｅｖｉｃｅ−ｔｏ−ｄｅｖｉｃｅ）資源に関する情報を転送する方法及び装置
WO2016159841A1 (fr) Continuité de service
EP3410814B1 (fr) Procédé de déclenchement de mise à jour de zone de suivi et équipement d'utilisateur
US20200267800A1 (en) Method for performing s1 connection release by mobility management object, mobility management object, method for performing s1 connection release by base station, and base station
WO2018061760A1 (fr) Terminal radio et dispositif de réseau
CN109804708B (zh) 控制通信的方法、无线通信设备、接入点和无线通信系统
WO2023005351A1 (fr) Dispositif terminal, noeud de réseau et procédés à l'intérieur de celui-ci pour gérer un commutateur de trajet et un transfert
US20220046527A1 (en) Method and apparatus for relay utilizing sidelink in wireless communication system
WO2022082690A1 (fr) Procédé, appareil et système de commutation de groupe
WO2022075906A1 (fr) Nœud de réseau, nœud de réseau demandeur et procédés de communication sur un chemin comprenant un équipement utilisateur distant, un équipement utilisateur relais et un nœud de réseau radio
CN116724589A (zh) 群组迁移方法、装置和系统
WO2022255133A1 (fr) Système de communication et station de base
WO2021251210A1 (fr) Système de communication, terminal de communication et dispositif de gestion
WO2024031267A1 (fr) Techniques de communication sans fil en liaison latérale
WO2022181526A1 (fr) Système de communication et station de base
KR20220017375A (ko) 무선 통신 시스템에서 사이드링크를 이용한 중계 방법 및 장치
WO2022216215A1 (fr) Procédés et nœuds de réseau radio pour la gestion de communication

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

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

Country of ref document: EP

Kind code of ref document: A1