WO2018105024A1 - Système de communication - Google Patents

Système de communication Download PDF

Info

Publication number
WO2018105024A1
WO2018105024A1 PCT/JP2016/086115 JP2016086115W WO2018105024A1 WO 2018105024 A1 WO2018105024 A1 WO 2018105024A1 JP 2016086115 W JP2016086115 W JP 2016086115W WO 2018105024 A1 WO2018105024 A1 WO 2018105024A1
Authority
WO
WIPO (PCT)
Prior art keywords
tetra
node
communication system
interwork
network
Prior art date
Application number
PCT/JP2016/086115
Other languages
English (en)
Inventor
Suan Yee TAN
Tien Ming Benjamin Koh
Takako Hori
Toyoki Ue
Original Assignee
Panasonic Intellectual Property Management Co., Ltd.
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 Panasonic Intellectual Property Management Co., Ltd. filed Critical Panasonic Intellectual Property Management Co., Ltd.
Priority to PCT/JP2016/086115 priority Critical patent/WO2018105024A1/fr
Publication of WO2018105024A1 publication Critical patent/WO2018105024A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/02—Inter-networking arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/08—Trunked mobile radio systems

Definitions

  • the invention pertains to terminals equipped with multiple radio interfaces. More specifically, it relates to the operation of such terminals in a network assisted manner.
  • PTL 1 proposes a gateway to interconnect the Public Safety and Security (PSS) communication network and public cellular communication network.
  • PSS Public Safety and Security
  • the gateway converts between PSS and cellular data protocols.
  • PSS Public Safety and Security
  • Such a solution employs a voice transcoder to convert the voice signals from one format to another, required by the destination network. This results in additional network delay.
  • PTT Push-to-Talk
  • PTL 2 uses a dispatch gateway (DG) or real time exchange (RTX) that interfaces to the wireless communications system to provide advanced voice services.
  • DG dispatch gateway
  • RTX real time exchange
  • IP Internet Packet
  • eNodeBs or TETRA switching management interfaces SwMI
  • Another method is to include interworking functionality to TETRA server and private LTE service server. Through a new interface, TETRA service could be extended to use the LTE network. However this requires the existing TETRA network to be changed or upgraded and this might not be realistic.
  • this invention teaches a way to interwork between 3GPP user equipment and TETRA terminals to provide extension to voice communication coverage.
  • a method is also disclosed for network-assisted information for device selection.
  • Figure 1 is a system configuration figure of the main embodiment
  • Figure 2 shows the modules in the TETRA application that enables UE(s) in 3GPP network to be capable of receiving TETRA related traffic
  • Figure 3 shows the modules in the interwork node configured for private 3GPP network
  • Figure 4 shows the frame format to be used for encapsulating TETRA voice frame in 3GPP defined network
  • Figure 5 is a sequence flow for the main embodiment
  • Figure 6 is the UE attachment procedure to be used in the main embodiment which is used for private LTE network
  • Figure 7 illustrates the establishment of the EPS bearers from UE to the interwork node
  • Figure 8 shows how a filter module is used to route the TETRA traffic, bypassing the P-GW
  • Figure 9 is a sequence flow for QCI setting for the EPS bearers
  • Figure 10 is a sequence flow that illustrates how TETRA related data is being conveyed in the 3GPP defined network
  • Figure 11 is a system configuration of the interwork node when used in commercial 3GPP defined
  • FIG. 1 shows the interconnection of the invention that allows TETRA services extension.
  • 210 and 211 are TETRA SwMI which are connected to the TETRA network 230.
  • 200 and 201 are TETRA terminals that are attached to the TETRA network.
  • the interwork node 240 provides the functionalities of TETRA radio and the evolved packet core (EPC).
  • the interwork node 240 could be attached to the TETRA network acting as a terminal and all incoming and outgoing 3GPP traffic to and from TETRA network is transferred via this node.
  • the interwork node comprises of multiple TETRA radios to support concurrent frequency pairs (one for uplink and the other for downlink) such that each radio could be tuned to each carrier pairs.
  • each TETRA base station supports a maximum of 8 carrier pairs (uplink and downlink) thus the interwork node 240 needs only to support maximum of 8 radios with the assumption that each radio can support both uplink and downlink.
  • each radio will be serviced as if it is a terminal.
  • the 3GPP network is able to utilize the maximum capacity of the TETRA network through the interwork node 240. In short, more talk groups can be supported concurrently.
  • the interwork node 240 is connected to the 3GPP base station or eNodeB 220, 221 as it also serves as an EPC.
  • a Long Term Evaluation (LTE) user equipment (UE) 202 is attached to the 3GPP LTE network.
  • LTE UE 202 a TETRA application comprising of reduced TETRA stack resides on top of the LTE radio and protocol stack.
  • Figure 2 shows the architecture of the LTE UE 202 which is referred to as 300 in this diagram.
  • 300 is a LTE UE, it operates using a LTE radio and LTE protocol stack 330.
  • the TETRA application 310 comprising of a control 311, a reduced TETRA stack 313 and a frame buffering and jitter management module 312 that interfaces to the algebraic code-excited linear prediction (ACELP) codec 320.
  • ACELP algebraic code-excited linear prediction
  • ACELP is the codec used by TETRA for encoding and decoding voice frames and the frame buffering and jitter management module 312 in the UE regulates the voice frames to the decoder so that voice can be played out smoothly.
  • the control 311 receives commands from the user and maps them to corresponding instructions of the reduced TETRA stack 313. Requesting for permission to talk in a talk group by the pressing of a button on the UE is an example of a command from the user.
  • the reduced TETRA stack 313 is in fact a full TETRA stack but with its radio and part of the mac layer functionalities related to the radio removed.
  • the protocol stack 330 is made up of LTE radio layer 1 up to the RTP layer.
  • LTE radio layer 1 up to the RTP layer.
  • different encapsulation shall be used.
  • TETRA commands or signalling frames shall be encapsulated using the TCP/IP or UDP/IP datagram.
  • Voice frame on the other hand needs to be encapsulated in RTP/UDP/IP datagram.
  • FIG. 3 shows the main components or functionalities present in the interwork node 240 which is referred to as 400 in this diagram.
  • the interwork node 400 contains a TETRA radio module 450 that supports connection to a TETRA network.
  • the TETRA radio module 450 may support concurrent transmission/reception on multiple frequency carriers. This allows more LTE UEs to use the PTT services concurrently and TETRA SwMI capabilities shall be the limiting factor.
  • This radio module provides the interface and is the bridge to the TETRA network.
  • the mapping function 410 provides a means to map Individual TETRA subscriber identity (ITSI) to group TETRA subscriber identity (GTSI) to individual mobile subscriber identity (IMSI) and vice versa. Using this mapping, data could be directed to the correct individual or user group.
  • ITSI Individual TETRA subscriber identity
  • GTSI group TETRA subscriber identity
  • IMSI mobile subscriber identity
  • LTE UE presence monitor 420 is responsible for determining whether a UE is attached to the PTT service via LTE. If it is, PTT data destined for the UE will be forwarded to it.
  • the interwork node 400 on receiving TETRA voice frames from the TETRA network via the TETRA radio module 450 in the interwork node, will encapsulate them as IP/UDP/RTP format which is referred to as 500 in Figure 4 via the encapsulation module 460.
  • IP/UDP or IP/TCP format could be used.
  • the EPC comprises of the serving gateway (S-GW), packet data network gateway (P-GW), mobility and management entity (MME) and other sub-modules e.g. home subscriber server (HSS) and etc, may be connected to multiple eNodeB(s).
  • S-GW serving gateway
  • P-GW packet data network gateway
  • MME mobility and management entity
  • HSS home subscriber server
  • This EPC like other normal EPCs can be connected to external networks and identification of a network is via the access point name identifier.
  • the forwarding module 430 forwards the received LTE PTT frames back to the LTE network as there could be other LTE UEs using the PTT services in the LTE network.
  • the de-capsulation module 470 For frames from LTE network and destined for the TETRA network, the de-capsulation module 470, will retain the content of the LTE frame and repackage them using TETRA mac frame format.
  • the interwork node 400 besides supporting TETRA group/individual calls also supports TETRA device-to-device mode where one end is a TETRA device and the other end a LTE UE, enabling it to act like a walkie talkie.
  • LTE UE 202 and TETRA devices/terminals 200 and 201 can communicate with one another using the advanced voice service or also known as the TETRA voice service.
  • FIG. 5 summarizes the start-up behaviour of the proposed system.
  • the system comprises of SwMI 601, UE under TETRA coverage 600, interwork node 602 connected to the eNB/eNodeB 603 and UE under the LTE coverage 604.
  • the interwork node 602 as described earlier comprises of the TETRA radio and EPC.
  • the TETRA radio helps link up the TETRA network while the EPC provides LTE core network functionalities and is connected to the eNodeB(s).
  • the interwork node 602 is assigned an identity e.g. access point name (APN) 620 so that LTE UE(s) can establish EPS bearer(s) for the TETRA services e.g. PTT.
  • APN access point name
  • talk-groups need to be set up and ITSI, GTSI and IMSI of the allowed UEs are either pre-registered or dynamically registered into the system. Through this registration, the interwork node will be able to map the traffic to the corresponding UEs in the networks.
  • registration to the network with authentication is required 631.
  • registration and attachment procedure is needed 640.
  • FIG. 6 shows the attachment procedure.
  • UE first establishes a RRC connection 641. Then it sends the ATTACH REQUEST message together with a PDN CONNECTIVITY REQUEST 642 for the packet data network (PDN) connectivity on the established RRC Connection.
  • PDN packet data network
  • the NAS common procedure of NAS identity, authentication and security mode procedure 643 is used if the network is unable to identify the UE.
  • the MME updates the location of the UE and also requests the subscriber profile from the HSS 644.
  • the MME establishes an eGTP User Tunnel to establish the default bearer at the SGW which sends a Create Session Request toward the SGW.
  • the SGW creates the default bearer for this UE and requests the P-GW to create a bearer for this UE between the SGW and the P-GW to provide end-to end bearer connectivity.
  • the P-GW then creates the bearer and allocates an IP Address for the UE 645.
  • eNodeB Upon receiving the Initial Context Setup Request, eNodeB reconfigures the resources to the UE by sending an RRC Connection Reconfiguration Request to the UE and it responds back with an RRC Connection Reconfiguration Complete.
  • the eNodeB then responds with an Initial Context Setup Response 646.
  • the MME updates the eNodeB tunnel ID for the default bearer using Modify Bearer Request 647.Finally the attachment procedure is completed 648 and a default bearer is established for the TETRA network.
  • dedicated uplink and downlink channels are established 650 for the TETRA PTT traffic and the established dedicated bearers are linked to the earlier default bearer that is set up. This forms the virtual connection, EPS bearer, up to the interwork node 602.
  • Figure 7 shows the establishment of the EPS bearer from the UE to the interwork node.
  • the P-GW could be bypass through routing of this traffic at the S-GW or eNodeB.
  • the S-GW/eNodeB is able to identify a traffic is of TETRA type through determining EPS bearers that will lead up to the TETRA external network or other equivalent means.
  • the routed traffic is directed to the forwarding function module 430 in Figure 3.
  • FIG 8 shows the placement of a filter module 649 at the S-GW to direct TETRA traffic to/from the forwarding function module 430/ encapsulation module 460.
  • This filter module 649 can be based on the EPS bearer id as discussed earlier. This mechanism will improve the packet delay budget by a couple of milliseconds. It should be highlighted that the EPC in Figure 3 with the optimization explained earlier, will not be the standard EPC but one that can quickly route traffic from the S-GW or other entity bypassing the P-GW for TETRA traffic.
  • MBMS multimedia broadcast multicast service
  • Interwork node is made known of a UE's connection to TETRA service via LTE through the use of Session Initiated Protocol (SIP) or any other equivalent protocol 680.
  • SIP Session Initiated Protocol
  • TETRA traffic e.g. PTT could be directed to and from the networks for the concerned UEs.
  • Subsequent procedures 690, 692 and 691 are used to set up (join), terminate group calls and transmit data respectively.
  • TETRA commands and voice frames destined for LTE network are encapsulated in IP/UDP or IP/TCP format and IP/UDP/RTP format respectively as shown in Figure 6.
  • TETRA is generally deployed for public safety scenario (PSS) and when LTE is used to extend its coverage, there is a requirement to give TETRA services particularly PTT a higher priority as compared to the existing LTE services, since it is used in mission critical operations.
  • PSS public safety scenario
  • FIG 9 is an illustration of how the QoS class identifier (QCI) could be set for the PTT service over LTE.
  • QCI 1 could be used for PTT however allocation and retention priority (ARP) should be given a lower value than VoLTE 800 so that the latter is of lower priority and could be pre-empted in times of congestion.
  • ARP allocation and retention priority
  • QCI 65 which has been assigned for mission critical applications could also be used.
  • Figure 9 shows the QCI setting for the EPS bearer which is from the UE up to the P-GW.
  • the P-GW can be skipped and the data is directed to the S-GW.
  • S-GW For outgoing TETRA data from the LTE network, S-GW directs the frames to the forwarding module that checks whether forwarding back to the LTE network is necessary and also to the de-capsulation module 470 where it repackages the packet into TETRA mac frame format for transmission in the TETRA network.
  • the encapsulation module 460 will direct the traffic into EPC and within it, the filter module 649 in Figure 8 will direct it to the corresponding S-GW and then the targeted eNodeB based on the EPS bearer information which is made up of the data bearer, S1 bearer and S5 bearer.
  • EPS bearer information which is made up of the data bearer, S1 bearer and S5 bearer.
  • TETRA traffic re-routing could also be performed at the eNodeB. Modification proposal is not made to this procedure as it is still applicable and to minimize customization required to the existing LTE core network stack.
  • FIG 10 shows LTE UE 703 transmitting PTT voice and signalling frames.
  • the interwork node 704 when received the frames, will determine whether there are any PTT individual/group users in the LTE network. If there are e.g. LTE users 710, 711, 712, the frames will be rerouted back to the LTE network. As a general rule, TETRA signalling frames are rerouted however if voice frames from a particular group has no user in the LTE network, rerouting is unnecessary.
  • the approach described in this embodiment is used for private LTE network scenario however it is also applicable to mobile virtual network operator (MVNO) scenario where the wireless communications services provider does not own the wireless network infrastructure.
  • MVNO mobile virtual network operator
  • the MVNO could request the mobile network operator to customize their network such traffic traversing on certain EPS bearers be re-routed to some external ports instead of to the P-GW.
  • the interwork node minus the EPC capabilities can be connected to the ports and in this manner, TETRA PTT services could be extended using LTE infrastructure.
  • this concept could also be extended for MBMS.
  • the mobile network operator provides the MBMS service while the interwork node provides the broadcast multicast service centre (BM-SC).
  • BM-SC broadcast multicast service centre
  • FIG 11 shows the setup of the interwork node 910.
  • the interwork node 910 is connected to the commercial LTE network (LTE Core Network) 920 via the internet 930 where the LTE network 920 is connected through the P-GW 921.
  • the P-GW 921 is connected to the eNodeB 922.
  • the interwork node 910 at the other end is connected to the TETRA infrastructure (TETRA Network) 900 via the TETRA radio module 450.
  • TETRA Network TETRA Network
  • LTE UE 923 installed with a TETRA application will be able use TETRA PTT over LTE and communicate with TETRA devices 904, 903 which are connected to the TETRA base stations 902 and 901 respectively.
  • FIG 12 shows the main modules present in the interwork node 910 which is referred to as 1000 in this diagram.
  • the interwork node 1000 contains a TETRA radio module 1040 that supports connection to a TETRA network.
  • the TETRA radio module 1040 may support concurrent transmission/reception on multiple frequency carriers and is the interface to the TETRA network.
  • the mapping function 1010 provides a means to map Individual TETRA subscriber identity (ITSI) to group TETRA subscriber identity (GTSI) to individual mobile subscriber identity (IMSI) and vice versa. Using this mapping, data could be directed to the correct individual or user group.
  • ITSI Individual TETRA subscriber identity
  • GTSI group TETRA subscriber identity
  • IMSI mobile subscriber identity
  • LTE UE presence monitor 1020 is a session manager and based on the session established by the UE, it is able to determining whether the UE is attached to the PTT service via LTE. Protocols like session initiated protocol (SIP), HTTP session and etc are examples of protocols that could be used for session management, Besides being equipped with UE presence detection capability, the monitor 1020 maintains the virtual channel or session for TETRA traffic to flow from the interwork to the UE via the EPC and vice versa.
  • the interwork node 1000 upon receiving TETRA voice frames from the TETRA network via the TETRA radio module 1040 in the interwork node, will encapsulate them as IP/UDP/RTP format which is referred to as 500 in Figure 4 via the encapsulation module 1050.
  • IP/UDP or IP/TCP format could be used.
  • the forwarding function module 1030 enables other UEs in the LTE network to receive TETRA related frames send from a UE, through forwarding the frames at the interwork node back to the LTE network on knowing the presence of other UEs in the network using the TETRA services.
  • the de-capsulation module 1060 For frames from LTE network and destined for the TETRA network, the de-capsulation module 1060, will retain the content of the LTE frame and repackage them using TETRA mac frame format.
  • the attach procedure 1100 registers the UE to the network that provides the internet service.
  • the default bearer which is of non-guaranteed bit rate (UGBR) type usually is assigned for internet usage and this is decided by the network operator.
  • the UE then establishes a session 1101 with the interwork node using the internet service set up earlier.
  • LTE TETRA traffic will have to transverse through the P-GW as opposed to the main embodiment where P-GW could be bypassed.
  • the protocol used by this session could be based on session layer protocol, SIP or application layer protocol, http session or the likes.
  • One of the objectives is for the presence monitor to keep track of UEs currently using the TETRA services over LTE network. The remaining procedure is similar to the preferred embodiment.
  • the second embodiment can be easily integrated with any existing LTE network as it assumes no changes are required while the main embodiment enables a lower delay budget and is achieved via EPC optimization and setting QCI for EPS bearers carrying TETRA related data.
  • Figure 14 shows a scenario where a user carries on his person two mobile devices with different network capabilities.
  • the first mobile device is the TETRA terminal 160 and the other device is a 3GPP user equipment (UE) 170.
  • the user should have registered with an interwork node 150 accessible database that both devices belong to the same user.
  • the interwork node 150 is connected to the TETRA network 130 and EPC 100 via the internet 120.
  • the TETRA network 130 is connected to the TETRA base stations 140.
  • EPC 100 is connected to the eNodeB 110.
  • a switch application should be installed on the mobile devices.
  • the primary function of the switch application would be to send periodic notification messages to the interwork node 150 from the respective mobile devices.
  • the TETRA terminal 160 may use the TETRA SDS (Short Data Service) messages for efficiency purposes.
  • the 3GPP UE 170 may use generic data communications to communicate with the interwork node 150.
  • the interwork node 150 may choose to initiate establishment of another connection to a different device registered with the same user.
  • 3GPP UE 170 may start receiving TETRA messages or voice communications from the relevant groups that terminal 160 was registered to.
  • Some factors that may influence the selection of a terminal from the user list include location (i.e. near currently active device), pre-configured selection priority value of device, device status (for example, battery level, signal strength, device capabilities such as voice or text-only).
  • connection establishment may involve a text or voice message to the user so that the user can initiate establishment procedures or take action on the active terminal.
  • connection establishment take place pre-emptively based on predicted disconnection due to poor signal strength or low battery power of the device.

Abstract

La présente invention concerne le fonctionnement d'un nœud d'interface qui configure la façon dont un système 3GPP est configuré pour être interfacé avec un système TETRA afin de permettre une extension de couverture, le système 3GPP ciblé étant un réseau privé. Le deuxième mode de réalisation décrit une solution d'interfonctionnement alternative dans laquelle le système 3GPP ciblé est un réseau commercial où aucun changement du système 3GPP n'est effectué. Un troisième mode de réalisation décrit comment le nœud d'interfonctionnement basé sur le mode de réalisation principal peut aider l'utilisateur à sélectionner le terminal correct pour une utilisation.
PCT/JP2016/086115 2016-12-05 2016-12-05 Système de communication WO2018105024A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2016/086115 WO2018105024A1 (fr) 2016-12-05 2016-12-05 Système de communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2016/086115 WO2018105024A1 (fr) 2016-12-05 2016-12-05 Système de communication

Publications (1)

Publication Number Publication Date
WO2018105024A1 true WO2018105024A1 (fr) 2018-06-14

Family

ID=62491860

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2016/086115 WO2018105024A1 (fr) 2016-12-05 2016-12-05 Système de communication

Country Status (1)

Country Link
WO (1) WO2018105024A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060262771A1 (en) * 2005-05-17 2006-11-23 M/A Com, Inc. System providing land mobile radio content using a cellular data network

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060262771A1 (en) * 2005-05-17 2006-11-23 M/A Com, Inc. System providing land mobile radio content using a cellular data network

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
TC TETRA WG4 ET AL.: "Liaison Statement: Potential Implementation of TETRA services over LTE", 3GPP TSG-SA WG1#60 S1-124253, 30 October 2012 (2012-10-30), pages 1 - 14, XP055510497, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG1_Serv/TSGS1_60_Edinburgh/docs/S1-124253.zip> [retrieved on 20170207] *

Similar Documents

Publication Publication Date Title
US20220248318A1 (en) Control of Network Slice
US20220182896A1 (en) Identification of Time Sensitive Network Bridge
US9386480B2 (en) Systems and methods for providing LTE-based backhaul
JP2022518211A (ja) 時間依存ネットワーキングのための制御プレーンに基づく設定
JP2022524122A (ja) ワイヤレスネットワークによるワイヤレスデバイスのページング
US10966078B2 (en) Emergency network slice and method for processing an emergency communication in a packet switched communication network
CN102469415B (zh) 基于lte技术的集群系统中点对多点呼叫方法、终端及系统
EP4042830B1 (fr) Libération en masse de plusieurs sessions pdu
WO2014005536A1 (fr) Procédé, dispositif et système de communication pour des terminaux voisins
EP2380392A1 (fr) Procédé et entité pour transmettre des unités de données
WO2022081832A2 (fr) Réseau de communication
KR101651962B1 (ko) 셀룰러 원격통신 네트워크에서 사용자 장비에 의한 강화된 액세스 선택을 위한 방법, 원격통신 네트워크, 및 사용자 장비의 강화된 액세스 선택을 위한 시스템
US20230217509A1 (en) Method for adding non-3gpp leg to an ma pdu session with 3gpp pdn leg
US20230126582A1 (en) Method for selecting relay device, remote device and relay device
WO2018105024A1 (fr) Système de communication
WO2018105022A1 (fr) Nœud d&#39;interfaçage, dispositif radio multimode et système incluant le nœud d&#39;interfaçage et le dispositif radio multimode
KR101558230B1 (ko) 패킷 스위칭된 도메인으로부터 서킷 스위칭된 도메인으로 호 핸드오버 방법 및 장치
KR102199271B1 (ko) 호 처리 방법 및 장치
WO2018206101A1 (fr) Critères de sélection en vue de destinations de données (non ip)
WO2022183497A1 (fr) Procédé de communication et appareil de communication
US20240040427A1 (en) Systems and methods for configuring communication with an iab mec
KR102076766B1 (ko) 단말 활성화 유지 방법 및 장치
KR20150021262A (ko) 호 처리 방법 및 장치
KR102113308B1 (ko) 위치정보 갱신 방법 및 장치
KR101404559B1 (ko) 이종 통신망간 호처리 장치 및 방법

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

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

Country of ref document: EP

Kind code of ref document: A1