WO2015192573A1 - Procédé et appareil d'enregistrement de services de jonction - Google Patents

Procédé et appareil d'enregistrement de services de jonction Download PDF

Info

Publication number
WO2015192573A1
WO2015192573A1 PCT/CN2014/089358 CN2014089358W WO2015192573A1 WO 2015192573 A1 WO2015192573 A1 WO 2015192573A1 CN 2014089358 W CN2014089358 W CN 2014089358W WO 2015192573 A1 WO2015192573 A1 WO 2015192573A1
Authority
WO
WIPO (PCT)
Prior art keywords
gcas
gciwf
cluster
service registration
registration request
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2014/089358
Other languages
English (en)
Chinese (zh)
Inventor
李志军
朱进国
谢宝国
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Publication of WO2015192573A1 publication Critical patent/WO2015192573A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • 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 present invention relates to the field of communications, and in particular to a cluster service registration method and apparatus.
  • the trunking communication system is a mobile communication system used for group dispatching command communication, and is widely used in public security, fire protection and other public security fields.
  • the biggest feature of trunking communication is that voice communication adopts push-to-talk (PTT), and the called party can answer without off-hook, and the connection speed is fast, and can support group call and other functions.
  • PTT push-to-talk
  • Its operation mode is mainly simplex and half-duplex, mainly adopting channel dynamic allocation mode, and users have different priority levels and special functions.
  • When communicating it can be used for one-stop communication, mainly in the field of professional mobile communication.
  • the cluster system transmits data through the shared channel to save resources and improve efficiency.
  • LTE Long Term Evolution
  • 3GPP Third Generation Partnership Project
  • FIG. 1 is a schematic diagram of a logic architecture for supporting cluster communication according to the related art LTE network. As shown in FIG. 1 , the functions of each part of the network element are as follows:
  • a user equipment (referred to as a UE) is also called a user equipment.
  • the user equipment accesses the base station through a wireless air interface and accesses the core network. Before the terminal accesses the core network, it needs to be authenticated by the core network. After the core network is registered, the terminal can have two states: idle state and connected state. In the idle state, the terminal and the base station are not connected. In the connected state, the terminal is connected to the base station and can send and receive data.
  • An evolved base station (Evolved NodeB, referred to as eNodeB) is a base station system in an LTE network, and mainly provides radio resources for terminal access, and the control plane and the mobile management unit communicate with each other through the S1-AP interface, and the user plane and The service gateway communicates through the S1-U interface.
  • the eNodeB informs the terminal of the current cell information by broadcasting.
  • the Mobility Management Element is a control plane entity in the LTE network and is responsible for user access authentication, mobility management, bearer management, etc., and temporarily stores the context in which the terminal is attached to the network.
  • the serving gateway (Serving Gateway, SGW for short) provides the anchor of the terminal in 2G ⁇ 3G and LTE mobility, and the SGW can also page the terminal through the MME if the terminal is in the idle state.
  • a public data network gateway (PDN Gateway, PGW for short), and the terminal accesses a public data network (PDN) through a PGW.
  • PGW allocates an IP address to the terminal and manages the quality of service (QoS) of the bearer.
  • QoS quality of service
  • PCRF Policy Changing Rule Function
  • the cluster service is implemented in an LTE network, and is based on a Multimedia Broadcast/Multicast Service (MBMS) subsystem.
  • the MBMS subsystem mainly includes a Broadcast Mode Service Center (BM-SC for short) and an MBMS Gateway (MBMS Gateway for short).
  • BM-SC Broadcast Mode Service Center
  • MBMS Gateway MBMS Gateway for short.
  • the BM-SC is responsible for establishing and maintaining the MBMS bearer
  • the MBMS GW is a data plane gateway function for implementing multicast/broadcast.
  • GCAS cluster application server
  • GCAS is used to manage cluster services, including cluster service group management, call setup, release, and management.
  • the GCAS and the UE are connected through the GC1 interface.
  • the main functions of the interface are the UE registration in the GCAS and the initiation of the group call.
  • GCAS and BM-SC are connected through the MB2 interface.
  • the MB2 interface includes a control plane part (MB2-C) for realizing the establishment and maintenance of the MBMS town, and a user plane part (MB2-U) for realizing the delivery of MBMS data.
  • M2-C control plane part
  • MB2-U user plane part
  • user plane data is delivered in two ways, unicast and multicast.
  • the so-called unicast that is, GCAS sends the downlink data to the terminal in a point-to-point manner, and uses the EPS bearer to send to the terminal.
  • the so-called multicast that is, the GCAS sends the downlink data to the MBMS subsystem (that is, to the BM-SC), and the MBMS GW delivers the data to the base station (ie, the eNodeB), and the UE obtains the MBMS data by reading the corresponding broadcast channel of the MBMS.
  • the implementation process of the trunking service by the broadcast mode generally includes the steps of: cluster registration, MBMS bearer establishment, MBMS data delivery, and UE receiving MBMS data.
  • FIG. 2 is a schematic flow chart of cluster registration and data delivery according to the related art. As shown in FIG. 2, the method has the following steps:
  • the UE is attached to the network, creates a PDN connection, and is assigned an IP address.
  • the UE belongs to a specific Public Land Mobile Network (PLMN), which is called the home network of the UE (Home PLMN, abbreviated as HPLMN).
  • PLMN Public Land Mobile Network
  • HPLMN home PLMN
  • VPLMN visited PLMN
  • the UE sends a cluster service registration request to the GCAS.
  • the UE provides a user identity (UE ID), an IP address (UE IP), a home network identifier (HPLMN ID), a visited network identifier (VPLMN ID), and current location information (usually a cell location Cell ID). , and other information.
  • UE ID user identity
  • UE IP IP address
  • HPLMN ID home network identifier
  • VPN ID visited network identifier
  • current location information usually a cell location Cell ID.
  • the GCAS checks whether the MBMS bearer has been established in the visited network/the area according to the visited network identifier (VPLMN ID) and the cell location (Cell ID) provided by the UE. If not, the GCAS initiates an MBMS bearer creation request to the BM-SC;
  • the GCAS sends a bearer creation request to the BM-SC, and the BM-SC requests the MBMS GW to create a response bearer;
  • the network allocates specific resources, including a core network and a radio resource, to the MBMS bearer.
  • the BM-SC carries a Temporary MBMS Group Identity (TMGI), an MBMS Flow ID, and the like in the bearer creation response message.
  • TMGI Temporary MBMS Group Identity
  • MBMS Flow ID an MBMS Flow ID
  • the GCAS returns a cluster service registration response to the UE.
  • GCAS returns the MBMS bearer information that has been created, including: TMGI.
  • the GCAS sends the downlink MBMS data to the BM-SC.
  • MBMS data is sent to the eNodeB after passing through the MBMS GW;
  • the UE monitors the MBMS broadcast and acquires the MBMS data.
  • GCAS must be able to find the appropriate BM-SC.
  • the MBMS service is based on the visited network, that is, the BM-SC exists in the visited network VPLMN. Since the UE can roam between multiple PLMNs, the GCAS must have the ability to select the corresponding BM-SC according to the VPLMN accessed by the current UE. In addition, for BM-SC, not all GCASs are allowed to access for security reasons, only some designated GCASs are allowed to access and use MBMS services.
  • FIG. 3 is a schematic diagram of a configuration, addressing, and verification process between BM-SC and GCAS according to the related art.
  • the figure shows the flow of GCAS configuration and discovery of BM-SC, as shown in FIG. 3, including the following step:
  • the BM-SC is configured with at least GCAS information (which may be a GCAS ID, a GCAS IP address, or a GCAS IP) that allows access to and use of the MBMS service.
  • GCAS information which may be a GCAS ID, a GCAS IP address, or a GCAS IP
  • the GCAS is configured with at least the identity of the PLMN that is allowed to access (PLMN ID) and the BM-SC information of the PLMN (which may be the BM-SC identifier BM-SC ID, the full domain name BM-SC FQDN, and the IP address).
  • BM-SC IP, etc. constitutes a mapping relationship of ⁇ PLMN ID, BM-SC ID/FQDN/IP>.
  • step S302 in step S202 in the process of Figure 2, the UE initiates a cluster service registration with the GCAS;
  • the GCAS obtains the VPLMN ID of the visited network that is accessed by the current UE, and determines whether the MBMS bearer has been created in the VPLMN. If the MBMS bearer has been created, go directly to step S308, otherwise obtain the BM-SC information under the VPLMN according to the VPLMN ID, and continue to S304;
  • the GCAS obtains the BM-SC under the visited network VPLMN according to the ⁇ PLMN, BM-SC> mapping relationship configured by itself. If the ID and FQDN of the BM-SC are obtained, the IP address of the BM-SC is obtained according to the corresponding method.
  • the GCAS sends an MBMS bearer request to the BM-SC.
  • the BM-SC performs authentication and authentication on the GCAS that sends the request.
  • the BM-SC authenticates the GCAS according to the GCAS information configured by itself. Authentication authentication may involve the interaction of BM-SC and GCAS, and the specific process is not the focus of the present invention.
  • the BM-SC sends an MBMS bearer request to the MBMS GW, and according to the request, the MBMS subsystem creates an MBMS bearer.
  • the MBMS bearer is created and returns a response.
  • step S308 in the process of FIG. 2 the GCAS returns a cluster service registration response.
  • the GCAS can discover the BM-SC and establish an MBMS bearer and notify the UE, thereby implementing a clustering service based on the broadcast technology.
  • GCAS and BM-SC are mutually configured, which brings more configuration workload and increases security risks in implementation:
  • BM-SC and GCAS mutually store the peers that can be allowed to access, and maintain a large number of MB2 connections between multiple BM-SCs (which can be in different PLMNs) and multiple GCASs;
  • GCAS belongs to a third party
  • BM-SC belongs to the operator
  • the BM-SC is directly exposed to the third-party AS, and the security is poor
  • the embodiment of the invention provides a method and a device for registering a cluster service, so as to solve at least the problem that the architecture configuration of the cluster service management in the related art is large and the security risk is large.
  • a cluster service registration method including: a cluster communication interoperation gateway GCIWF receiving a cluster service registration request of a terminal UE; the GCIWF acquiring a visited network identifier VPLMN ID of the UE, and A corresponding broadcast mode service center BM-SC is selected according to the VPLMN ID.
  • the GCIWF receives the cluster service registration request of the UE, and the GCIWF receives the cluster service registration request sent by the UE from the cluster application server GCAS.
  • the method further includes: the GCIWF performing authentication and authentication on the GCAS according to the subscription data of the UE.
  • the GCIWF After the GCIWF receives the cluster service registration request of the UE, the GCIWF selects a corresponding GCAS according to the service type in the cluster service registration request sent by the UE, and sends the cluster service registration request to the GCAS.
  • the GCIWF selects the corresponding GCAS according to the service type in the cluster service registration request sent by the UE, and the GCIWF selects the service type corresponding to the service type according to the service type in the cluster service registration request sent by the UE.
  • GCAS; or the GCIWF acquires the service type and the subscription data of the UE, and selects GCAS according to the correspondence between the service type and the GCAS in the subscription data.
  • the GCIWF obtains, by the GCIWF, the VPLMN ID of the UE, the GCIWF acquiring the VPLMN ID from the cluster service registration request of the UE; or the GCIWF querying the VPLMN ID from the policy charging rule function PCRF .
  • the method further includes: the GCIWF sending the information of the BM-SC to the cluster application server GCAS.
  • the information of the BM-SC includes: an IP address and a port of the MB2 user plane interface.
  • the transmitting, by the GCIWF, the information of the BM-SC to the GCAS includes: the GCIWF carrying the information of the BM-SC in a Create Multimedia Broadcast/Multicast Service MBMS Bearer Response sent to the GCAS.
  • the method further includes: the GCAS transmitting the MBMS data to the BM-SC according to the information of the BM-SC.
  • a cluster service registration method including: a cluster communication interoperation gateway GCIWF receiving a cluster service registration request of a terminal UE; the GCIWF selecting a cluster application server GCAS, and the cluster service A registration request is sent to GCAS.
  • the GCIWF selects the GCAS, and the GCIWF selects the corresponding GCAS according to the service type in the cluster service registration request.
  • the GCIWF selects the corresponding GCAS according to the service type in the cluster service registration request, and the GCIWF selects the GCAS corresponding to the service type according to the service type in the cluster service registration request; or
  • the GCIWF obtains the service type and the subscription data of the UE, and selects GCAS according to the correspondence between the service type and the GCAS in the subscription data.
  • a cluster service registration method including: the cluster communication interoperation gateway GCIWF, after receiving the cluster service registration request of the terminal UE, to the policy charging rule function
  • the PCRF subscribes to the PLMN/RAT change information of the UE; the GCIWF reports the change information to the cluster application server GCAS.
  • the method further includes: the GCIWF receiving the subscription of the GCAS to the PLMN/RAT change information of the UE.
  • the method further includes: the GCAS receiving PLMN/RAT change information of the UE; and the GCAS determining, according to the PLMN of the UE, whether to create an MBMS in the changed PLMN. Hosted.
  • a cluster service registration device which is located in the cluster communication interoperation gateway GCIWF, and includes: a first receiving module, configured to receive a cluster service registration request of the terminal UE; and a first selection module, The method is configured to acquire a visited network identifier VPLMN ID of the UE, and select a corresponding broadcast mode service center BM-SC according to the VPLMN ID.
  • the first receiving module includes: a first receiving unit, configured to receive a cluster service registration request sent by the UE from a cluster application server GCAS; and an authentication authentication unit configured to perform GCAS on the basis of the subscription data of the UE Right certification.
  • the first receiving module includes: a second receiving unit, configured to receive a cluster service registration request of the UE; and a selecting unit, configured to select a corresponding GCAS according to a service type in the cluster service registration request sent by the UE; And a sending unit, configured to send the cluster service registration request to the GCAS.
  • a cluster service registration device which is located at the cluster communication interoperation gateway GCIWF, and includes: a second receiving module, configured to receive a cluster service registration request of the terminal UE; and a second selection module, It is set to select the cluster application server GCAS and send the cluster service registration request to GCAS.
  • a cluster service registration device which is located in a cluster communication interoperation gateway GCIWF, and includes: a subscription module, configured to charge a policy after receiving a cluster service registration request of the terminal UE.
  • the rule function PCRF subscribes to the PLMN/RAT change information of the UE; the reporting module is configured to report the change information to the cluster application server GCAS.
  • the GCIWF is used to receive the cluster service registration request of the UE; the GCIWF obtains the VPLMN ID of the UE, and selects the corresponding BM-SC according to the VPLMN ID, and solves the cluster service in the related art.
  • the management architecture configuration has a large workload and a large security risk, which can effectively reduce the configuration complexity between BM-SC and GCAS and improve the security of cluster service calls.
  • FIG. 1 is a schematic diagram of a logical architecture of an LTE network implementation supporting cluster communication according to the related art
  • FIG. 2 is a schematic flow chart of cluster registration and data delivery according to the related art
  • FIG. 3 is a schematic diagram of a configuration, addressing, and verification process between a BM-SC and a GCAS according to the related art
  • FIG. 4 is a flowchart of a cluster service registration method according to an embodiment of the present invention.
  • FIG. 5 is a structural block diagram of a cluster service registration apparatus according to an embodiment of the present invention.
  • FIG. 6 is a flowchart of another cluster service registration method according to an embodiment of the present invention.
  • FIG. 7 is a structural block diagram of another cluster service registration apparatus according to an embodiment of the present invention.
  • FIG. 8 is a flowchart of still another cluster service registration method according to an embodiment of the present invention.
  • FIG. 9 is a structural block diagram of still another cluster service registration apparatus according to an embodiment of the present invention.
  • FIG. 10 is a schematic diagram of a cluster communication architecture according to Embodiment 1 of the present invention.
  • FIG. 11 is a schematic flowchart of a cluster communication architecture for implementing cluster service registration and data delivery according to the first embodiment of the present invention
  • FIG. 12 is a schematic diagram of a cluster communication architecture according to Embodiment 2 of the present invention.
  • FIG. 13 is a schematic flowchart of a cluster communication architecture for implementing cluster service registration and data delivery according to a second embodiment of the present invention
  • FIG. 14 is a schematic diagram of a cluster communication architecture according to Embodiment 3 of the present invention.
  • FIG. 15 is a schematic flowchart of a cluster communication architecture for implementing cluster service registration and data delivery according to a third embodiment of the present invention.
  • 16 is a schematic diagram of a cluster communication architecture according to the first, second, or third embodiment of the present invention to implement a process of switching a cluster service under a PLMN/RAT according to a terminal;
  • FIG. 17 is a schematic diagram of a cluster communication architecture enhancement in a roaming situation according to Embodiment 5 of the present invention.
  • FIG. 18 is a schematic flowchart of a cluster communication architecture and a cluster service registration and data delivery according to the embodiment of the present invention.
  • the embodiment proposes an architecture for implementing cluster service management, and improves the processes of cluster service registration, MBMS bearer establishment, and PLMN/RAT handover according to the architecture, which can effectively reduce BM-SC and GCAS. Between configuration complexity, improve the security of cluster business calls.
  • FIG. 4 is a flowchart of a cluster service registration method according to an embodiment of the present invention. As shown in FIG. 4, the method includes:
  • Step S402 the GCIWF receives the cluster service registration request of the UE.
  • Step S404 the GCIWF acquires a VPLMN ID of the UE, and selects a corresponding BM-SC according to the VPLMN ID.
  • the GCIWF is added to the current cluster service management architecture, and the GCIWF receives the cluster service registration request of the UE, and selects the corresponding BM-SC according to the VPLMN ID of the UE, so that there is no need between the BM-SC and the GCAS.
  • the mutual correspondence is stored, and the information of the BM-SC does not need to be exposed to the GCAS.
  • the configuration work is reduced due to the clear management structure of the cluster service.
  • the GCIWF receiving the cluster service registration request of the UE may include the following two situations:
  • the GCIWF may receive a cluster service registration request sent by the UE from the GCAS.
  • the GCIWF may perform the subscription data according to the UE from the Home Subscriber Server (HSS).
  • HSS Home Subscriber Server
  • the GCIWF may also receive the cluster service registration request sent by the UE directly from the UE. Preferably, after the GCIWF receives the cluster service registration request from the UE, the GCIWF may select a corresponding GCAS according to the service type in the cluster service registration request, and send the cluster service registration request to the GCAS.
  • the GCIWF may select the corresponding GCAS according to the service type in the cluster service registration request sent by the UE, and may include the following manner: mode 1: when the optional GCAS is small, the service type may be stored in the GCIWF. The corresponding relationship of the GCAS, the GCIWF selects the GCAS corresponding to the service type according to the service type in the cluster service registration request; and the second method, when the optional GCAS is large, the GCIWF can obtain the service type. And signing data with the UE, and selecting GCAS according to the correspondence between the service type and the GCAS in the subscription data.
  • the GCIWF may obtain the VPLMN ID of the UE from the cluster service registration request of the UE; or the GCIWF may also query the VPLMN ID from the PCRF.
  • the GCIWF may send the information of the BM-SC to the GCAS.
  • the information of the BM-SC may include an MB2 user plane IP address and a port.
  • the specific implementation manner in which the GCIWF sends the information of the BM-SC to the GCAS may be as follows: the GCIWF carries the information of the BM-SC in an MBMS bearer response sent to the GCAS.
  • the GCAS may send the MBMS data to the BM-SC according to the information of the BM-SC.
  • a cluster service registration device is provided, which is located in the GCIWF.
  • the device is configured to implement the foregoing embodiments and preferred embodiments, and has not been described again.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 5 is a structural block diagram of a cluster service registration apparatus according to an embodiment of the present invention. As shown in FIG. 5, the apparatus includes a first receiving module 52 and a first selecting module 54, and each module is described in detail below:
  • the first receiving module 52 is configured to receive a cluster service registration request of the UE, and the first selecting module 54 is connected to the first receiving module 52, configured to acquire a VPLMN ID of the UE, and select a corresponding BM according to the VPLMN ID. -SC.
  • the first receiving module 52 may include: a first receiving unit 522, configured to receive a cluster service registration request sent by the UE from the GCAS; and an authentication authentication unit 524 configured to perform GCAS according to the subscription data of the UE. Authentication certification.
  • the first receiving module 52 may further include: a second receiving unit 526 configured to receive a cluster service registration request of the UE; and a selecting unit 528 connected to the second receiving unit 526, configured to be configured according to the cluster sent by the UE
  • the service type in the service registration request selects the corresponding GCAS;
  • the sending unit 530 is connected to the second receiving unit 526 and the selecting unit 528, and is configured to send the cluster service registration request received by the second receiving unit 526 to the selecting unit 528.
  • the selected GCAS is
  • FIG. 6 is a flowchart of another cluster service registration method according to an embodiment of the present invention. As shown in FIG. 6, the method includes the following steps:
  • Step S602 the GCIWF receives the cluster service registration request of the UE.
  • Step S604 the GCIWF selects GCAS, and sends the cluster service registration request to the GCAS.
  • the GCIWF is added to the current cluster service management architecture, and the GCIWF receives the cluster service registration request of the UE, and forwards the cluster service registration request to the GCAS selected by the GCIWF, and solves the cluster in the related technology.
  • the architecture configuration of the service management has a large workload and a large security risk, which can effectively reduce the configuration complexity between the BM-SC and the GCAS, and improve the security of the cluster service call.
  • the GCIWF may select a corresponding GCAS according to the service type in the cluster service registration request.
  • the GCIWF may select the corresponding GCAS according to the service type in the cluster service registration request sent by the UE, and may include the following manner: mode 1: when the optional GCAS is small, the service type and the GCAS corresponding may be stored in the GCIWF.
  • the GCIWF may select the GCAS corresponding to the service type according to the service type in the cluster service registration request, and the GCIWF may obtain the service type and the foregoing when the optional GCAS is large.
  • the contract data of the UE is selected according to the correspondence between the service type and the GCAS in the subscription data.
  • FIG. 7 is a structural block diagram of another cluster service registration device according to an embodiment of the present invention.
  • the device includes a second receiving module 72 and a second selecting module 74, and each module is described in detail below:
  • the second receiving module 72 is configured to receive the cluster service registration request of the UE.
  • the second selecting module 74 is connected to the second receiving module 72, configured to select the GCAS, and send the cluster service registration request to the GCAS.
  • FIG. 8 is a flowchart of still another cluster service registration method according to an embodiment of the present invention. As shown in FIG. 8, the method includes the following steps:
  • Step S802 After receiving the cluster service registration request of the UE, the GCIWF subscribes to the PCRF for the PLMN/RAT change information of the UE.
  • Step S804 the GCIWF reports the change information to the GCAS.
  • the GCIWF is added to the current cluster service management architecture.
  • the GCIWF subscribes to the PLMN/RAT change information of the UE to the PCRF after receiving the cluster service registration request of the UE, and reports the information to the GCAS, and the related information is resolved.
  • the architecture configuration of the cluster service management in the technology has a large workload and a large security risk, which can effectively reduce the configuration complexity between the BM-SC and the GCAS, and improve the security of the cluster service call.
  • the GCIWF may be triggered to subscribe the PLMN/RAT change information of the UE to the PCRF if the GCIWF receives the subscription of the GCAS to the PLMN/RAT change information of the UE.
  • the GCAS After the GCIWF reports the change information to the GCAS, the GCAS receives the PLMN/RAT change information of the UE; the GCAS determines whether to create an MBMS bearer in the changed PLMN according to the PLMN of the UE.
  • FIG. 9 is a structural block diagram of another cluster service registration device according to an embodiment of the present invention.
  • the device includes a subscription module 92 and a reporting module 94, and each module is described in detail below:
  • the subscription module 92 is configured to subscribe to the PCRF for the PLMN/RAT change information of the UE after receiving the cluster service registration request of the UE; the reporting module 94 is connected to the subscription module 92 and configured to report the change to the GCAS.
  • an architectural enhancement is introduced, that is, a group communication interworking function (GCIWF) function controlled by an operator is introduced between the BM-SC and the GCAS.
  • GCIWF group communication interworking function
  • the GCIWF function is deployed in the UE's home network HPLMN, and GCAS only needs to be addressed to the GCIWF.
  • the ⁇ PLMN, BM-SC> information configured on the GCAS is changed to the configuration of ⁇ PLMN, GCIWF>, and the BM-SC only configures the GCIWF for each PLMN, which can effectively reduce the configuration workload.
  • the GCIWF sends the information of the BM-SC (such as the IP and Port of the MB2-U interface) to the GCAS, so that the GCAS can directly send the MBMS data to the BM-SC through the MB2-U interface.
  • the GCIWF selects the BM-SC instead of the GCAS according to the VPLMN ID provided by the UE.
  • GCAS In place of BM-SC for authentication of GCAS: authentication of GCAS is not required for BM-SC, GCAS is performed by GCIWF, and BM-SC and GCIWF are usually based on secure connections between operators.
  • GCIWF authenticates GCAS based on its own configuration data or based on user subscription data (also known as contract data) obtained from HSS.
  • GCIWF itself can configure GCAS information that allows access, such as GCAS address, authentication information, and so on.
  • the authentication for using the cluster service for each UE can be implemented: the GCIWF can determine whether the UE is allowed to use the cluster service according to the user subscription data obtained from the HSS. That is, the GCIWF obtains the UE subscription data from the HSS, and verifies the UE using the GCS service and the GCAS access permission.
  • the GCIWF can subscribe to the PCRF and obtain the PLMN and RAT currently accessed by the UE, and provide the GMN. That is, the GCIWF subscribes to the PLMN/RAT of the UE from the PCRF and provides it to the GCAS to create an MBMS bearer in the new PLMN to implement MBMS data transmission.
  • Embodiment 1 (Cluster Communication Architecture 1)
  • FIG. 10 is a schematic diagram of a cluster communication architecture according to a first embodiment of the present invention.
  • GC1 is implemented between UE and GCAS
  • MB2-U is implemented between GCAS and BM-SC
  • BM-SC address is provided by GCIWF. provide.
  • the cluster communication architecture of Figure 10 has the following improvements:
  • the control plane interface MB2-C is implemented between GCIWF and BM-SC, and the user plane interface MB2-U is implemented between GCAS and BM-SC. Then GCAS needs to obtain BM-SC information (ie IP, Port of user plane interface MB2-U);
  • GCIWF replaces GCAS to obtain BM-SC information (such as IP and Port of MB2-U interface), and returns BM-SC information to GCAS;
  • FIG. 11 is a schematic flowchart of a cluster communication architecture for implementing cluster service registration and data delivery according to the first embodiment of the present invention. As shown in FIG. 11, the method includes the following steps:
  • the UE sends a cluster service registration request to the GCAS.
  • the information includes: a user identifier (UE ID), an IP address (UE IP), a home network identifier (HPLMN ID), a visited network identifier (VPLMN ID), current location information (usually a cell location Cell ID), and the like. ;
  • the GCAS obtains the GCIWF under the PLMN according to the home network identifier (HPLMN ID) provided by the UE.
  • HPLMN ID home network identifier
  • the GCAS obtains the GCIWF information in the HPLMN of the UE according to the mapping relationship of the ⁇ PLMN, GCIWF> stored by itself, and may be a full domain name FQDN of the GCIWF, or an IP address.
  • S1103 The GCAS sends an MBMS bearer request to the GCIWF.
  • the GCAS ID (GCAS ID) is carried, and optionally the UE's identity (UE ID) and the visited network identifier (VPLMN ID) are carried.
  • GCIWF performs authentication and authentication on GCAS
  • the GCIWF authenticates the GCAS based on the GCAS information stored by itself.
  • step S1104 may occur after steps S1105-S1106.
  • the GCIWF obtains the GCAS information from the subscription data, and performs authentication authentication on the GCAS accordingly.
  • Authentication certification may involve the interaction process between GCIWF and GCAS. Wherein, when the number of GCAS is small, the GCAS information can be directly stored on the GCIWF, and the GCIWF authenticates the GCAS according to the service type in the cluster service registration request and the GCAS information corresponding to different service types stored by the GCIWF.
  • step S1106 if the UE ID is provided in step S1103, the GCIWF uses the UE ID to query the HSS for the subscription data of the UE;
  • the GCIWF authenticates whether the UE allows the use of the cluster service according to the user subscription data. If the authentication fails, the request sent by GCAS can be rejected.
  • the GCIWF obtains the BM-SC information of the PLMN according to the visited network identifier VPLMN ID provided by the GCAS in step S1103.
  • the GCIWF acquires the IP address of the BM-SC in the designated PLMN according to the ⁇ PLMN, BM-SC> mapping relationship stored by itself.
  • S1108 The GCIWF sends an MBMS bearer request to the BM-SC.
  • the BM-SC authenticates the GCIWF based on the roaming agreement between different PLMNs. Simply put, the BM-SC can authenticate the GCIWF based on the GCIWF information stored by itself.
  • the BM-SC communicates with other MBMS network elements to create a required MBMS bearer
  • the BM-SC sends an MBMS bearer response message, and carries the MBMS bearer information, such as: TMGI, Flow ID, and the like;
  • the GCIWF returns an MBMS bearer response message to the GCAS, and carries the MBMS bearer information, such as: TMGI, Flow ID, and the like;
  • the GCIWF carries the information of the BM-SC, such as the IP and Port of the MB2-U interface, so that the GCAS can directly send the MBMS data to the BM-SC through the MB2-U interface.
  • the GCAS returns a cluster service registration response to the UE, and carries MBMS parameter information, such as: TMGI;
  • the GCAS sends the MBMS data according to the obtained BM-SC information (such as the IP and Port of the MB2-U interface).
  • BM-SC information such as the IP and Port of the MB2-U interface.
  • the root MBMS technology the data is sent to the eNodeB via the MBMS GW, and the UE reads the MBMS data from the MBMS broadcast.
  • Embodiment 2 (Cluster Communication Architecture II)
  • FIG. 12 is a schematic diagram of a cluster communication architecture according to Embodiment 2 of the present invention.
  • GC1 is implemented between UE and GCIWF;
  • MB2-U is implemented between GCAS and BM-SC, and
  • BM-SC address is provided by GCIWF.
  • the cluster communication architecture of Figure 12 has the following improvements:
  • the control plane interface MB2-C is implemented between GCIWF and BM-SC, and the user plane interface MB2-U is implemented between GCAS and BM-SC. Then GCAS needs to obtain BM-SC information (ie IP, Port of user plane interface MB2-U);
  • GCIWF replaces GCAS to obtain BM-SC information (such as IP and Port of MB2-U interface), and returns BM-SC information to GCAS;
  • the GC1 interface is implemented between the UE and the GCIWF, and the UE registers with the GCAS, and uses a third-party AS registration mechanism;
  • FIG. 13 is a schematic flowchart of a cluster communication architecture for implementing cluster service registration and data delivery according to the second embodiment of the present invention, including the following steps:
  • the UE sends a cluster service registration request to the GCIWF.
  • the method includes: a user identifier (UE ID), an IP address (UE IP), a home network identifier (HPLMN ID), a visited network identifier (VPLMN ID), current location information (usually a cell location Cell ID), Selected) Service Type, and other information;
  • the GCIWF information (full domain name FQDI, IP address) is stored instead of the GCAS information, so the UE sends the cluster service registration request to the GCIWF.
  • the GCIWF queries the HSS for the subscription data of the UE;
  • the GCIWF acquires the GCAS to which the UE is to be registered, so as to perform third-party AS registration;
  • the GCIWF obtains the GCAS to which the UE is to be registered according to the local configuration data or the UE subscription data.
  • the UE may only register to one GCAS, and only the GCAS is included in the local configuration of the GCIWF or the subscription data of the UE.
  • the UE may allow registration to a plurality of different types of GCAS.
  • the mapping relationship of ⁇ Service Type, GCAS> is included in the local configuration of the GCIWF or the UE subscription data. Therefore, the GCIWF can acquire the GCAS to which the UE is to be registered according to the service type (Service Type) provided by the UE, so as to perform third-party AS registration.
  • the GCIWF After selecting the GCAS, the GCIWF sends the cluster service registration request of the UE to the GCAS.
  • S1306 The GCAS sends an MBMS bearer request to the GCIWF.
  • GCAS ID GCAS ID
  • UE ID UE ID
  • VPN ID visited network identifier
  • GCIWF performs authentication and authentication on GCAS
  • the GCIWF authenticates the GCAS based on the GCAS information stored by itself. Or, when the GCIWF obtains the GCAS information from the UE subscription data, and performs authentication authentication on the GCAS accordingly. Authentication certification may involve the interaction process between GCIWF and GCAS.
  • the GCIWF obtains the BM-SC information of the PLMN according to the obtained visited network identifier VPLMN ID.
  • the GCIWF acquires the full domain name/IP address of the BM-SC in the specified PLMN according to the ⁇ PLMN, BM-SC> mapping relationship stored by itself.
  • the GCIWF sends an MBMS bearer request to the BM-SC.
  • the BM-SC authenticates the GCIWF
  • the BM-SC communicates with other MBMS network elements to create a required MBMS bearer
  • the BM-SC sends an MBMS bearer response message, and carries the MBMS bearer information, such as: TMGI, Flow ID, and the like;
  • the GCIWF returns an MBMS bearer response message to the GCAS, and carries the MBMS bearer information, such as: TMGI, Flow ID, multicast IP/Port, and the like;
  • the GCIWF carries the information of the BM-SC, such as the IP and Port of the MB2-U interface, so that the GCAS can directly send the MBMS data to the BM-SC through the MB2-U interface.
  • the GCAS returns a cluster service registration response to the GCIWF, and carries MBMS parameter information, such as: TMGI, multicast IP/Port, and the like.
  • the GCIWF forwards the cluster service registration response to the UE;
  • the GCAS sends the MBMS data according to the obtained BM-SC information (such as the IP and Port of the MB2-U interface).
  • BM-SC information such as the IP and Port of the MB2-U interface.
  • the root MBMS technology the data is sent to the eNodeB via the MBMS GW, and the UE reads the MBMS data from the MBMS broadcast.
  • the GCIWF information is stored on the UE, instead of the GCAS information, so the UE sends the cluster service registration request to the GCIWF;
  • the GCIWF selects the GCAS to which the UE is to be registered according to the local configuration and/or user subscription data, and the service type, and performs the registration to the GCAS instead of the UE, that is, the cluster service registration request is sent to the GCAS;
  • Embodiment 3 (Cluster Communication Architecture 3)
  • FIG. 14 is a schematic diagram of a cluster communication architecture according to a third embodiment of the present invention.
  • GC1 is implemented between the UE and the GCIWF;
  • MB2-U is implemented between the GCIWF and the BM-SC, and the GCAS sends the MBMS data to GCIWF;
  • GCIWF maintains a list of ⁇ PLMN ID, BM-SC, MBMS Bearers>, and GCIWF sends MBMS data to BM-SCs in different PLMNs.
  • the cluster communication architecture shown in Figure 14 has the following improvements:
  • the control plane interface MB2-C is implemented between GCIWF and BM-SC, and the user plane interface MB2-U is implemented between GCIWF and BM-SC.
  • GCAS sends the MBMS data to the GCIWF, which is forwarded by the GCIWF to the BM-SC;
  • the GC1 interface is implemented between the UE and the GCIWF, and the UE registers with the GCAS, and uses a third-party AS registration mechanism;
  • FIG. 15 is a schematic diagram of a cluster communication architecture for implementing cluster service registration and data delivery according to the third embodiment of the present invention. Compared with the flow shown in FIG. 13, the method has the following differences:
  • step S1513 after the MBMS bearer is created, the GCIWF sends the MBMS bearer information to the GCAS, and does not carry the information of the BM-SC (such as the IP and Port of the MB2-U user plane interface). GCAS can only get information about GCIWF. Therefore, in step S1516, the GCAS transmits the MBMS to the GCIWF, forwards it to the BM-SC by the GCIWF, and then transmits it to the base station via the MBMS subsystem, and the UE reads from the MBMS broadcast.
  • the GCAS transmits the MBMS to the GCIWF, forwards it to the BM-SC by the GCIWF, and then transmits it to the base station via the MBMS subsystem, and the UE reads from the MBMS broadcast.
  • Embodiment 4 (Switching PLMN/RAT)
  • FIG. 16 is a schematic diagram of a cluster communication process implemented by a terminal in a process of switching between a PLMN/RAT, and can be applied to the cluster communication architecture of the first, second, or third embodiment, including the following steps:
  • the cluster service registration request may be directly sent by the UE to the GCAS, or sent by the UE to the GCIWF, and sent to the GCAS by the GCIWF through the third-party AS registration process.
  • the GCAS sends a subscription request to the GCIWF, and subscribes to the UE's network/access technology (PLMN/RAT) change event.
  • PLMN/RAT network/access technology
  • step S1605 is performed.
  • the GCIWF sends a subscription request to the PCRF to subscribe to the PLMN/RAT change event of the UE. After receiving the subscription request, the PCRF sends a corresponding request (such as PGW, MME) to the core network, and requests the UE to report to the PCRF when the UE switches the PLMN/RAT.
  • a corresponding request such as PGW, MME
  • the PCRF receives an event report, where the PLMN/RAT information after the UE switches the PLMN/RAT is included;
  • the PCRF sends an event report to the GCIWF, including the UE ID and the PLMN/RAT information.
  • the GCIWF sends an event report to the GCAS, including the UE ID and the PLMN/RAT information.
  • steps S1606-S1608 may occur. That is, GCIWF can send the event report to GCAS unconditionally, regardless of whether GCAS has a subscription.
  • the GCAS After receiving the event report, the GCAS determines, according to the provided PLMN/RAT information, whether to create an MBMS bearer in the PLMN/RAT.
  • the GCAS can use various rules and conditions to determine whether to create an MBMS bearer in the PLMN/RAT. For example, whether the MBMS bearer has been established in the PLMN/RAT, and the UE participating in the cluster service under the PLMN/RAT Is it enough, and so on. It is possible for GCAS to request to create an MBMS bearer within the PLMN when there are enough UEs in the PLMN to participate in the cluster service. If there are not enough UEs in the PLMN, the GCAS sends the cluster service data to the UE in a unicast manner based on the EPS bearer.
  • GCAS requests to create an MBMS bearer in the new PLMN.
  • the GCIWF obtains the BM-SC in the new PLMN, and sends a request to create an MBMS bearer.
  • the GCAS obtains the information of the new MBMS bearer.
  • the GCAS sends a notification to the UE, and carries the new MBMS bearer information, such as TMGI, Multicast IP/Port, and the like;
  • Embodiment 5 (Cluster Communication Architecture 4)
  • FIG. 17 is a schematic diagram of a cluster communication architecture enhancement in a roaming situation according to Embodiment 5 of the present invention, as shown in FIG. 17:
  • GCIWF is deployed on both the home network HPLMN and the visited network VPLMN.
  • the GCIWF of the home network is called H-GCIWF
  • the GCIWF of the visited network is V-GCIWF.
  • the MB2 interface is used to interconnect, and at least the MB2-C interface is included to implement signaling message transmission.
  • the MB2-U interface can be implemented between H-GCIWF and V-GCIWF according to different architectures as described above, or between BM-SC of H-GCIWF and VPLMN, or implemented in GCAS and VPLMN. Between BM-SC.
  • the visited network may not want to directly expose the BM-SC to other PLMNs.
  • the H-GCIWF can only discover the V-GCIWF, that is, the V-GCIWF is addressed by the H-GCIWF. Not a BM-SC of VPLMN.
  • the V-GCIWF may carry the BM-SC address back to the VPLMN for use by H-GCIWF or GCAS.
  • FIG. 18 is a cluster communication architecture according to the fifth embodiment of the present invention combined with the first embodiment to implement the cluster service.
  • S1801 The UE sends a cluster service registration request.
  • H-GCIWF obtains contract data from HSS and authenticates GCAS
  • the H-GCIWF obtains the V-GCIWF in the visited network according to the visited network VPLMN ID of the UE.
  • the VPLMN ID may be carried by the UE in the cluster service registration request, or may be obtained by the H-GCIWF from the PCRF query.
  • the H-GCIWF sends an MBMS bearer request to the V-GCIWF.
  • the created MBMS bearer information is included, including: TMGI, Flow ID, and the like.
  • the information of the BM-SC (such as the IP and Port of the MB2-U) may also be carried in the message, or the address of the BM-SC may be replaced by the address of the V-GCIWF.
  • the H-GCIWF may return all the information returned by the V-GCIWF to the GCAS, and may also replace the BM-SC or V-GCIWF address with the H-GCIWF address.
  • the GCAS returns a cluster service registration response to the UE, and carries the MBMS bearer information.
  • the GCAS uses the obtained BM-SC, or V-GCIWF address, or H-GCIWF address to deliver MBMS data.
  • a storage medium in which the above software is stored, including but not limited to an optical disk, a floppy disk, a hard disk, an erasable memory, and the like.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the cluster service registration method and apparatus provided by the embodiments of the present invention have the following beneficial effects: the problem that the architecture configuration workload of the cluster service management in the related art is large and the security risks are large, and the problem is achieved. It can effectively reduce the configuration complexity between BM-SC and GCAS and improve the security of cluster service calls.

Landscapes

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

Abstract

La présente invention se rapporte à un procédé et à un appareil d'enregistrement de services de jonction. Le procédé comprend les étapes suivantes : un GCIWF reçoit une demande d'enregistrement de service de jonction d'un UE; et le GCIWF acquiert un ID de VPLMN de l'UE et sélectionne un BM-SC conformément à l'ID de VPLMN correspondant. La présente invention remédie au problème de l'état actuel de la technique, à savoir une lourde charge de travail de configuration de l'architecture et des risques de sécurité élevés dans la gestion de services de jonction, réduit efficacement la complexité de configuration entre un BM-SC et un GCAS, et améliore la sécurité des appels aux services de jonction.
PCT/CN2014/089358 2014-06-16 2014-10-23 Procédé et appareil d'enregistrement de services de jonction Ceased WO2015192573A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410268506.0 2014-06-16
CN201410268506.0A CN105208555B (zh) 2014-06-16 2014-06-16 集群业务注册方法及装置

Publications (1)

Publication Number Publication Date
WO2015192573A1 true WO2015192573A1 (fr) 2015-12-23

Family

ID=54934798

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/089358 Ceased WO2015192573A1 (fr) 2014-06-16 2014-10-23 Procédé et appareil d'enregistrement de services de jonction

Country Status (2)

Country Link
CN (1) CN105208555B (fr)
WO (1) WO2015192573A1 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107172595B (zh) * 2016-03-08 2019-08-16 普天信息技术有限公司 宽带集群系统中终端漫游时的业务实现方法、系统及装置
CN106357648B (zh) * 2016-09-21 2019-10-29 海能达通信股份有限公司 一种集群终端的集群业务注册方法、系统及核心网系统
CN116155681B (zh) * 2022-12-23 2024-03-26 博上(山东)网络科技有限公司 一种物联网终端管控方法及系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101616011A (zh) * 2008-06-23 2009-12-30 阿尔卡特朗讯公司 用于将终端注册到ims中的应用服务器的方法、设备和系统
CN102014362A (zh) * 2009-12-28 2011-04-13 大唐移动通信设备有限公司 一种csg信息的发送方法、系统和设备
CN103702327A (zh) * 2012-09-27 2014-04-02 中兴通讯股份有限公司 用户设备选择拜访公共陆地移动网络的方法、系统和设备

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101251193B1 (ko) * 2006-06-09 2013-04-08 삼성전자주식회사 ＰｏＣ 시스템에서 그룹 세션을 개설하기 위한 방법 및 시스템
CN103188617B (zh) * 2011-12-27 2016-11-23 华为技术有限公司 实现集群业务的方法、实体及系统
CN103384380B (zh) * 2012-05-02 2018-12-21 中兴通讯股份有限公司 一种机器类通信事件的上报方法及相应装置
CN103716754A (zh) * 2012-09-29 2014-04-09 北京三星通信技术研究有限公司 一种支持承载资源控制的方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101616011A (zh) * 2008-06-23 2009-12-30 阿尔卡特朗讯公司 用于将终端注册到ims中的应用服务器的方法、设备和系统
CN102014362A (zh) * 2009-12-28 2011-04-13 大唐移动通信设备有限公司 一种csg信息的发送方法、系统和设备
CN103702327A (zh) * 2012-09-27 2014-04-02 中兴通讯股份有限公司 用户设备选择拜访公共陆地移动网络的方法、系统和设备

Also Published As

Publication number Publication date
CN105208555B (zh) 2020-01-14
CN105208555A (zh) 2015-12-30

Similar Documents

Publication Publication Date Title
EP2830337B1 (fr) Procédé de mise en oeuvre de service à ressources partagées numérique large bande et centre de gestion de planification de partage des ressources
CN115315965B (zh) 多播或广播会话建立和管理
WO2021232897A1 (fr) Établissement de liaison relais, procédé et appareil de transmission d'informations de configuration, et support de stockage lisible
CN114071376B (zh) 一种通信方法、装置以及系统
WO2022028437A1 (fr) Procédé, appareil et système de communication
CN113676887B (zh) 通过n3gpp接入的公共报警消息
CN110830983B (zh) 一种局域网通信的管理方法及装置
US10595168B2 (en) Enhancements to eMBMS for group communication
CN104284299A (zh) 集群多播决策方法、集群终端及集群服务器
WO2022233024A1 (fr) Procédé d'établissement d'une session se service de multidiffusion/diffusion, et système et appareil associés
WO2021109134A1 (fr) Procédé d'acquisition et de transmission d'informations mbms, dispositif terminal et dispositif d'élément de réseau
CN113811025A (zh) 一种释放中继连接的方法、设备及系统
WO2014166440A1 (fr) Système, dispositif, et procédé de relais en grappe et support de stockage
WO2023045472A1 (fr) Procédé, appareil et système de communication
CN120018317A (zh) 一种通信方法、装置以及系统
US10219309B2 (en) D2D service authorizing method and device and home near field communication server
KR20240004483A (ko) Mbs 세션의 핸드오버 방법, 및 그 시스템 및 장치
CN105208555B (zh) 集群业务注册方法及装置
CN115551082A (zh) 一种多播业务的通信方法、装置及系统
CN104254129A (zh) 临近业务发现的资源配置方法及装置
CN115334458A (zh) 一种通信方法及装置
CN105472530A (zh) 近距离通讯发现方法、装置及系统
CN103476144A (zh) 企业网系统及基于企业网系统的用户设备注册方法
WO2016050034A1 (fr) Procédé de traitement d'adressage de groupe, dispositif, passerelle d'intercommunication mtc, et passerelle d'api
CN115190433B (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: 14895178

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

Country of ref document: EP

Kind code of ref document: A1