WO2019154034A1 - Procédé de communication, et appareil et système associés - Google Patents

Procédé de communication, et appareil et système associés Download PDF

Info

Publication number
WO2019154034A1
WO2019154034A1 PCT/CN2019/072014 CN2019072014W WO2019154034A1 WO 2019154034 A1 WO2019154034 A1 WO 2019154034A1 CN 2019072014 W CN2019072014 W CN 2019072014W WO 2019154034 A1 WO2019154034 A1 WO 2019154034A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
ims
slice
address
ims slice
Prior art date
Application number
PCT/CN2019/072014
Other languages
English (en)
Chinese (zh)
Inventor
张彪
舒续祖
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2019154034A1 publication Critical patent/WO2019154034A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1073—Registration or de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a communication method, related apparatus, and system.
  • the fifth-generation (5th generation, 5G) network is a next-generation network that network operators hope to deploy, which has high-rate and low-latency characteristics.
  • a network slice is one of the features provided by a 5G network, which can satisfy different service requirements by separating different network slices for the 5G network.
  • a process of selecting a 5G core (5GC) slice by a user equipment (UE) and a 5G network is defined in the prior art.
  • the UE selects a corresponding 5GC network slice according to different service requirements, and each 5GC slice is
  • the UE allocates different IP addresses, for example, the UE uses different IP addresses to initiate different services.
  • the IP multimedia sub-system IMS network also needs to be sliced.
  • the prior art does not provide a technical problem of how the UE selects different IMS slice networks for communication.
  • the embodiment of the present application provides a communication method, related apparatus and system, which can enable a UE to select an IMS slice network for communication.
  • the embodiment of the present application provides a communication method in an IMS snippet network of an IP multimedia subsystem, which is mainly implemented by a core network device, and specifically includes the following steps:
  • the core network device Upon receiving the network connection request of the user equipment UE, the core network device acquires the slice identifier of the IMS slice network and the address of the IMS slice network;
  • the core network device sends the slice identifier of the IMS slice network and the address of the IMS slice network to the UE.
  • the core network device sends the slice identifier of the different IMS slice network and the address of the IMS slice network to the UE, so that the UE can initiate registration to different IMS slice networks, and thus in different IMS slice networks. Initiate business.
  • the core network device may send the slice identifier of the IMS slice network and the address of the IMS slice network to the UE through the network connection response message.
  • the core network device may locally obtain the slice identifier of the IMS slice network corresponding to the UE and the address of the IMS slice network.
  • the core network device includes a session management function SMF device.
  • the core network device ie, the SMF device acquires the slice identifier of the IMS slice network and the address of the IMS slice network, including:
  • the SMF device acquires a slice identifier of the IMS slice network and an address of the IMS slice network from the network storage function NRF.
  • the SMF device may further send a first request message to the user data management device for requesting the slice identifier of the IMS slice network and the address of the IMS slice network, and then the SMF device receives the first response returned by the user data management device.
  • the message, the first response message carries a slice identifier of the IMS slice network and an address of the IMS slice network.
  • the solution can be applied to the scenario where the UE accesses the IMS slice network through the 5GC, and the SMF in the 5GC can send the information of the IMS slice network to the UE.
  • the core network device may further include an access management function AMF device, where the core network device (including the AMF device and the SMF device) sends the slice identifier of the IMS slice network to the UE and
  • the address of the IMS slice network includes:
  • the SMF device sends a notification message to the access management function device AMF, where the notification message carries the slice identifier of the IMS slice network and the address of the IMS slice network, and then the AMF device sends a session accept message to the UE,
  • the session accept message carries a slice identifier of the IMS slice network and an address of an IMS slice network.
  • the solution can be applied to the scenario where the UE accesses the IMS slice network through the 5GC.
  • the AMF and the SMF in the 5GC can send the information of the IMS slice network to the UE.
  • the core network device includes a mobility management entity MME, and the core network device (including the MME) acquiring the slice identifier of the IMS slice network and the address of the IMS slice network includes:
  • the solution may be applied to a scenario in which the UE accesses the IMS slice network through the EPC of the evolved packet core network, and the MME in the EPC may send information of the IMS slice network to the UE.
  • the core network device includes a packet gateway PGW, and the core network device (including the PGW) sends the slice identifier of the IMS slice network and the address of the IMS slice network to the UE, including:
  • the PGW sends a setup session response to the MME, where the setup session response carries the slice identifier of the IMS slice network and the address of the IMS slice network, and then the MME forwards the received slice identifier of the IMS slice network to the UE. And the address of the IMS slice network.
  • the solution can be applied to the scenario where the UE accesses the IMS slice network through the EPC, and the PGW in the EPC sends the information of the IMS slice network to the UE.
  • the present application provides a communication method in an IMS snippet network of an IP multimedia subsystem, which is applied to a user equipment UE, and includes the following steps:
  • the UE may acquire information of the IMS slice network from the core network device, and then may initiate IMS registration to the IMS slice network, and after the registration is completed, the IMS service may be initiated in the IMS slice network.
  • the UE may receive the correspondence between the slice identifier of the multiple IMS slice networks and the address of the IMS slice network, and the UE may locally save the received multiple sets of correspondences.
  • the slice identifier of the IMS slice network and the address of the IMS slice network are in one-to-one correspondence.
  • the user equipment carries a slice identifier of the IMS slice network in a header field of the registration message.
  • the user equipment obtains an address of the proxy call session control function device P-CSCF in the IMS slice network from the 5G core network slice when establishing a PDU session with the 5G core network slice.
  • the UE may further receive a registration completion message sent by the IMS slice network, where the registration completion message carries a slice identifier of the IMS slice network. After completing the IMS registration of the IMS slice network, the UE may initiate an IMS service on the IMS slice network.
  • the UE may further generate a service request message after completing the IMS registration, and determine an address of the IMS slice network corresponding to the service information in the service request message according to the correspondence relationship;
  • the IMS slice network corresponding to the address of the IMS slice network sends the service request message to perform IMS service.
  • the service request message generated by the UE may carry the slice ID of the IMS slice network.
  • the determining, by the UE, the address of the IMS slice network corresponding to the service information in the service request message includes:
  • the UE first determines a slice identifier of the IMS slice network corresponding to the service information in the service request message, and then determines an address of the IMS slice network corresponding to the slice identifier of the IMS slice network according to the correspondence.
  • the present application provides a communication method in an IMS snippet network of an IP multimedia subsystem, which is applied to a user equipment UE, and includes the following steps:
  • the UE obtains a correspondence between the slice identifier of the IMS slice network and the address of the IMS slice network, and then generates a service request message, and determines an address of the IMS slice network corresponding to the service information in the service request message according to the correspondence relationship; The UE then transmits the service request message to the IMS slice network corresponding to the address of the IMS slice network.
  • the UE may generate an IMS service request message, and then determine an address of the IMS slice network that the service request message needs to be sent according to the foregoing correspondence, and send the service request to the IMS slice network corresponding to the determined address.
  • the message thereby enabling the initiation of IMS services in the IMS tile network.
  • the service request message generated by the UE may carry the slice ID of the IMS slice network.
  • the determining, by the UE, the address of the IMS slice network corresponding to the service information in the service request message includes:
  • the UE first determines a slice identifier of the IMS slice network corresponding to the service information in the service request message, and then determines an address of the IMS slice network corresponding to the slice identifier of the IMS slice network according to the correspondence.
  • the UE may receive, from the core network device, a correspondence between a slice identifier of the IMS slice network and an address of the IMS slice network.
  • the application provides a core network device corresponding to the communication method of the first aspect, including:
  • An acquiring module configured to acquire a slice identifier of an IMS slice network and an address of the IMS slice network when receiving a network connection request of the user equipment UE;
  • a sending module configured to send, to the UE, a slice identifier of the IMS slice network and an address of an IMS slice network.
  • the core network device includes a session management function SMF device, and the acquiring module in the SMF device acquires a slice identifier of the IMS slice network and an address of the IMS slice network from the NRF; or
  • the sending module in the SMF device is further configured to send a first request message to the user data management device, to request a slice identifier of the IMS slice network and an address of the IMS slice network; and the acquiring module in the SMF device further uses And receiving the first response message returned by the user data management device, where the first response message carries a slice identifier of the IMS slice network and an address of the IMS slice network.
  • the core network device may include an AMF device that forwards the slice identifier of the received IMS slice network and the address of the IMS slice network to the UE.
  • the core network device is a packet gateway PGW, and the sending module in the PGW sends the slice identifier of the IMS slice network and the address of the IMS slice network to the UE, including:
  • the sending module sends a setup session response to the MME, where the setup session response carries the slice identifier of the IMS slice network and the address of the IMS slice network, so that the MME forwards the received IMS slice to the UE.
  • the slice identifier of the network and the address of the IMS slice network are the same or different.
  • the application provides a user equipment applied to an IP multimedia subsystem, which mainly includes:
  • a receiving module configured to receive a correspondence between a slice identifier of the IMS slice network and an address of the IMS slice network sent by the core network device;
  • a registration module configured to send an IMS registration message to the IMS slice network according to the address, where the registration message carries a slice identifier of the IMS slice network.
  • the user equipment carries a slice identifier of the IMS slice network in a header field of the registration message.
  • the receiving module of the user equipment is further configured to receive a registration completion message sent by the IMS slice network, where the registration completion message carries a slice identifier of the IMS slice network.
  • the user equipment further includes: a service requesting module, configured to generate a service request message, and a determining module, configured to determine, according to the correspondence, an IMS slice network corresponding to the service information in the service request message
  • the service request module is further configured to send the service request message to an IMS slice network corresponding to an address of the IMS slice network.
  • the embodiment of the present application provides a core network device, where the core network device can be implemented by using a general-purpose computer.
  • the core network device can include a memory, a processor, an input and output device, and the like.
  • the program code is stored in the memory, and the processor can acquire and execute the program code stored in the memory, so that the core network device can perform the communication method provided by the first aspect.
  • the specific implementation process refer to the first aspect.
  • the application further provides a user equipment, which may include a memory, a processor, an input device, an output device, and the like.
  • the program code is stored in the memory, and the processor can acquire and execute the program code stored in the memory, so that the user equipment can perform the communication method provided by the second aspect or the third aspect.
  • the specific implementation process refer to the foregoing second aspect and Description of the third aspect.
  • the embodiment of the present application provides a communication system, which includes the core network device of the fourth aspect and the user equipment provided by the fifth aspect.
  • the user equipment can connect to the core network equipment through the wireless access network.
  • the service request message may be an invite message
  • the network connection request may be an attach request, a PDN connection setup request, or a session establishment request.
  • the slice address of the IMS slice network may be the address of the P-CSCF in the IMS slice network.
  • FIG. 1 is a schematic diagram of networking of a communication system according to Embodiment 1 of the present application.
  • FIG. 2 is a flowchart of a communication method provided in Embodiment 2 of the present application.
  • Embodiment 3 is a flowchart of a communication method provided in Embodiment 3 of the present application.
  • Embodiment 4 is a flowchart of a communication method provided in Embodiment 4 of the present application.
  • Embodiment 5 is a flowchart of a communication method provided in Embodiment 5 of the present application.
  • FIG. 6 is a hardware structural diagram of a core network device according to Embodiment 6 of the present application.
  • FIG. 7 is a hardware structural diagram of a user equipment provided in Embodiment 7 of the present application.
  • FIG. 8 is a schematic diagram of functional modules of a core network device according to Embodiment 8 of the present application.
  • FIG. 9 is a schematic diagram of functional modules of a user equipment provided in Embodiment 9 of the present application.
  • FIG. 1 is a schematic diagram of networking of a communication system according to Embodiment 1.
  • the communication system provided in this embodiment includes a user equipment (UE) and a network side device.
  • the network side device includes a 5G core network (5GC core, 5GC) device, an evolved packet core network (EPC) device, and a user equipment for mobility management, user plane control, and the like of the user equipment accessing the 5G network.
  • An IMS network device that provides IMS services.
  • 5GC can perform network segmentation, and 5GC can also not slice.
  • 5GC is cut into 5GC1 and 5GC2.
  • the IMS network is also sliced, and the IMS network is cut into two IMS slice networks (which may also be referred to as IMS network slices or IMS slices), such as IMS1 and IMS2.
  • the UE connects to IMS1 through 5GC1 and to IMS2 through 5GC2. If the 5GC does not slice, the UE connects to IMS1 and IMS2 through 5GC.
  • the UE can also connect to the IMS slice networks IMS1 and IMS2 via EPC.
  • the principle that the IMS network and the 5GC are sliced may include a service type, a user type, a user level, a number segment, and the like, which are not limited in this embodiment of the present application.
  • Different IMS slice networks can provide different IMS services, for example, IMS1 provides public security cluster services, and IMS2 provides voice call services.
  • the device in the IMS1 may include a proxy-call session control function (P-CSCF1), a service-call session control function (S-CSCF1), and an application server 1 ( Application service, AS1).
  • P-CSCF1 proxy-call session control function
  • S-CSCF1 service-call session control function
  • AS1 Application service, AS1
  • Devices in IMS2 may include P-CSCF2, S-CSCF2, and AS2.
  • the home subscriber server (HSS) and the interrogating-call session control function (I-CSCF) belong to a device common to IMS1 and IMS2.
  • the devices in the 5GC include an access and mobility management function (AMF) for access and mobility management of the UE, and a session management function (SMF) for managing the session of the UE. ), a user plane function (UPF) that controls the user plane of the UE.
  • AMF access and mobility management function
  • SMF session management function
  • UPF user plane function
  • other devices are also included in the 5GC, for example, a device that performs a policy control function, which is not limited in this embodiment.
  • the equipment in the EPC includes a mobility management entity (MME) and a packetized gateway (PGW) that manage the mobility of the UE.
  • MME mobility management entity
  • PGW packetized gateway
  • the UE may send a network connection request to the core network device, and after receiving the network connection request, the core network device acquires a slice identifier of the IMS slice network (also referred to as an identifier of the IMS slice network or an identifier of the IMS slice). And the address of the corresponding IMS slice network (which may also be referred to as the address of the IMS slice).
  • the core network device then sends the slice identification of the IMS slice network and the address of the IMS slice network to the UE. Therefore, the UE can register with the IMS slice network according to the address of the IMS slice network.
  • the UE can initiate an IMS service on the IMS slice network, for example, the UE initiates a virtual reality (VR) service or public security on the IMS1.
  • V virtual reality
  • Cluster service which initiates voice call service or augmented reality (AR) service in IMS2.
  • this embodiment solves the technical problem that the UE cannot obtain the address of the IMS slice network in the case that the IMS network performs the slice.
  • the slice identifier and the IMS of different IMS slice networks are used by the core network device.
  • the address of the slice network is sent to the UE, so that the UE can initiate registration to different IMS slice networks, thereby initiating services in different IMS slice networks.
  • the slice identifier of the IMS slice network may correspond to the service information of the service provided by the IMS slice network.
  • the correspondence between the slice identifier of the IMS slice network and the service information of the service provided by the IMS slice network may be stored in the core network device, such as HSS, UDM, AMF, SMF, etc., and may also be stored in the UE.
  • the service information of the service provided by the IMS slice network may also be used as the attribute information of the slice identifier of the IMS slice network, and is stored in the parameter of the slice identifier of the IMS slice network.
  • the service information of the service provided by the IMS slice network is also provided to the UE.
  • the attribute information of the slice identifier of the IMS slice network may further include a home location of the IMS slice network, a user number segment corresponding to the IMS slice network, and the like.
  • FIG. 2 is a flowchart of implementing a communication method according to Embodiment 2 of the present application.
  • This embodiment describes the interaction process between the UE and the core network device, and mainly includes the following steps:
  • Step 201 The UE sends a network connection request to the core network device for requesting connection to the core network.
  • the UE may send a network connection request to the core network device after the power is turned on, for requesting to connect to the core network, and want to use the service provided by the network.
  • the core network device receives the network connection request sent by the user equipment, where the network connection request may carry the information of the UE.
  • the information of the UE may include an identifier of the UE, location information of the UE, and the like.
  • Step 202 The core network device acquires a slice identifier of the IMS slice network and an address of the IMS slice network.
  • the core network device may acquire the slice identifier of one or more IMS slice networks and the address of the IMS slice network. There may be a one-to-one correspondence between the slice identifier of the IMS slice network and the address of the IMS slice network.
  • the address of the IMS slice network may specifically be the address of the P-CSCF in the IMS slice network.
  • the slice identifier of the IMS slice network may be used to identify the IMS slice network, and there may be a correspondence between the information provided by the IMS slice network and the location of the IMS slice network.
  • the slice identification of the IMS slice network can be replaced with information such as the service provided by the IMS slice network, the location of the IMS slice network, and the like.
  • the core network device may further acquire a slice identifier of the corresponding IMS slice network and an address of the IMS slice network according to the information of the UE.
  • the core network device may also obtain the slice identifier of the corresponding IMS slice network and the address of the IMS slice network according to the number segment of the UE.
  • the core network device may also obtain the slice identifier of the corresponding IMS slice network and the address of the IMS slice network according to the location information of the UE.
  • the core network device can obtain the slice identifier of the IMS slice network and the address of the IMS slice network locally. For example, the information of these IMS slice networks is obtained from the local configuration.
  • Step 203 The core network device sends a slice identifier of the IMS slice network and an address of the IMS slice network to the UE.
  • the core network device may send the slice identifier of the previously acquired IMS slice network and the address of the IMS slice network to the UE by using a response message. For example, the core network device sends the information of the IMS slice network to the UE through the network connection, and the UE receives the slice identifier of the IMS slice network and the address of the IMS slice network sent by the core network device.
  • the core network device may be a generalized category, and the device that implements the actions of the above steps 201-203 may be referred to as a core network device.
  • the core network device is also not limited to a specific device, which may be a combination of multiple devices, that is, multiple devices jointly implement the method steps in the above steps 201-203.
  • the SMF, AMF, or the combination in the 5GC can implement the functions of the core network device
  • the MME and the PGW in the EPC can also implement the functions of the core network device.
  • Step 204 The UE sends an IMS registration message to the IMS slice network according to the address, where the registration message carries a slice identifier of the IMS slice network.
  • the UE after obtaining the address of the IMS slice network, the UE generates an IMS registration message carrying the slice identifier of the IMS slice network, and then sends an IMS registration message to the IMS slice network to perform an IMS registration procedure.
  • the slice identifier of the IMS slice network may be placed in the header field of the registration message and sent to the IMS slice network.
  • the UE may initiate IMS registration to multiple IMS slice networks, respectively. After the UE completes the IMS registration, the UE may initiate an IMS service on different IMS slice networks.
  • the UE may also select 1-2 IMS slice networks for IMS registration from information of multiple IMS slice networks returned by the core network device. For example, the UE may select an IMS slice network of the user location for IMS registration, and the UE may also select and The IMS slice network corresponding to the number segment performs IMS registration.
  • FIG. 3 is a flowchart of a communication method provided in Embodiment 3 of the present application.
  • the UE accesses the IMS network through the 5GC.
  • the communication method provided in this embodiment mainly includes:
  • Step 301 The UE sends a PDU session establishment request to the AMF through the base station, and is used to request to establish a PDU session with the 5GC.
  • the core network device includes an AMF and an SMF.
  • the AMF acquires user data of the UE from a User Data Management (UDM) device, and then receives a network connection request sent by the UE through a base station (not shown).
  • the network connection request is specifically a PDU session establishment request, where the request carries the information of the UE and the identifier of the PDU session.
  • the information of the UE is, for example, the capability of the UE, the type of the UE, or the location of the UE, and the like.
  • UDM can also be called unified data management (UDM) equipment.
  • Step 302 The AMF sends a session establishment request to the SMF to request to establish a PDU session.
  • Step 303 The SMF sends a first request message to the user data management device, where the identifier of the slice of the IMS slice network and the address of the IMS slice network are requested.
  • the SMF may add a cell that acquires IMS slice information in the first request message sent to the UDM.
  • the first request message sent by the SMF may specifically be a registration registration message in this embodiment.
  • the SMF obtains the slice identifier of the IMS slice network and the address of the IMS slice network from the user data management device, and obtains the slice identifier of the IMS slice network from the network repository function (NRF) in the 5GC.
  • the address of the IMS slice network is the address of the IMS slice network.
  • Step 304 The UDM returns a first response message to the SMF, where the message carries the slice identifier of the IMS slice network and the address of the IMS slice network.
  • the correspondence between the ID of the IMS slice network and the address of the IMS slice network is stored on the UDM, and after receiving the first request message, the UDM can store the IDs of all the IMS slice networks that it stores.
  • the correspondence between the addresses of the IMS-slice network is sent to the SMF, and the slice identifier of the corresponding IMS-slice network and the address of the IMS-slice network are also obtained according to the information of the UE.
  • the UDM may acquire the slice identifier of the corresponding IMS slice network and the address of the IMS slice network according to the number segment of the UE.
  • the UDM may also obtain the slice identifier of the IMS slice network and the address of the IMS slice network of the location where the UE is located according to the location information of the UE.
  • the slice identifier of the IMS slice network and the address of the IMS slice network may be sent to the SMF as part of the user data of the UE.
  • the first response message may be a subscription to obtain a subscription retrieval message.
  • the IMS slice network acquired by the UDM includes IMS1 and IMS2.
  • IMS1 provides public security cluster services, and IMS2 provides voice call services.
  • Step 305 The SMF sends a notification message to the AMF, where the slice identifier of the IMS slice network and the address of the IMS slice network are carried.
  • the notification message sent by the SMF may specifically be a Namf_Communication_N1N2MessageTransfer message.
  • the notification message may carry an identifier of the PDU session, a slice identifier of the IMS slice network, and an address of the IMS slice network.
  • the service information of the service provided by the IMS slice network (IMS1 and IMS2) is used as the attribute information of the slice identifier of the IMS slice network, and is also sent by the SMF to the AMF.
  • the service information of the service provided by the IMS slice network may also be sent to the AMF as a parameter parallel to the slice identifier of the IMS slice network and the address of the IMS slice network.
  • the SMF can also send this information to the AMF via other messages.
  • the SMF may also perform the step of selecting the UPF and establishing an N4 session with the UPF (not shown). These steps are not shown in Figure 3, but may exist in a particular implementation.
  • Step 306 The AMF sends a session accept message to the UE, where the slice identifier of the IMS slice network and the address of the IMS slice network are carried.
  • the AMF may send a PDU session establishment accept message to the UE, indicating that the PDU session establishment is completed.
  • the session accept message may carry the slice identifier of the IMS slice network and the address of the IMS slice network, and may also carry the IP address allocated by the core network for the UE.
  • the session accept message sent by the AMF may be forwarded to the UE by the radio base station. After receiving the session accept message, the UE may locally save the following correspondence.
  • the SMF in the 5GC acquires the slice identifier of the IMS slice network and the address of the IMS slice network from the user data management function device, and then sends the slice identifier and the identifier of the IMS slice network to the UE through the AMF.
  • the address of the IMS slicing network is such that the UE can initiate an IMS registration to the IMS slicing network based on the IMS information and initiate an IMS service in the IMS slicing network.
  • FIG. 4 is a flowchart of a communication method provided in Embodiment 4 of the present application.
  • the UE accesses the IMS network through the EPC.
  • the communication method provided in this embodiment mainly includes:
  • Step 401 The UE sends an attach request to the MME through the base station, and is used to connect to the EPC.
  • the network connection request sent by the UE to the core network device by using the base station may specifically be an attach Attach request for attaching to the EPC.
  • the attach request may carry the identifier of the UE, and may also carry the location information of the UE.
  • the core network device is an MME.
  • the core network device can also be a PGW.
  • Step 402 The MME sends a second request message to the HSS for requesting the slice identifier of the IMS slice network and the address of the IMS slice network.
  • the MME may add a cell that acquires IMS slice information in the second request message sent to the HSS.
  • the second request message sent by the MME may be an update location request message, which may send the current location information of the UE to the HSS in addition to the IMS slice information.
  • the MME may also locally store the slice identifier of the IMS slice network and the address of the IMS slice network, and the MME may directly obtain the IMS information from the local.
  • Step 403 The MME receives a second response message returned by the HSS, where the message carries the slice identifier of the IMS slice network and the address of the IMS slice network.
  • the correspondence between the ID of the IMS slice network and the address of the IMS slice network is stored on the HSS, and after receiving the second request message, the HSS may store the IDs of all the IMS slice networks that it stores.
  • the correspondence between the addresses of the IMS-slice network is sent to the MME, and the slice identifier of the corresponding IMS-slice network and the address of the IMS-slice network are also obtained according to the information of the UE.
  • the HSS may acquire the slice identifier of the corresponding IMS slice network and the address of the IMS slice network according to the number segment of the UE.
  • the HSS may also obtain the slice identifier of the corresponding IMS slice network and the address of the IMS slice network according to the location information of the UE.
  • the second response message returned by the HSS may specifically be an update location acknowledge message.
  • the IMS slice network acquired by the HSS includes IMS1 and IMS2.
  • IMS1 provides public security cluster services
  • IMS2 provides voice call services.
  • Step 404 The MME sends an attach accept message to the UE, where the slice identifier of the IMS slice network and the address of the IMS slice network are carried.
  • the MME may send the message to the UE by using an attach accept message.
  • the service information of the service provided by the IMS slice network (IMS1 and IMS2) is used as the attribute information of the slice identifier of the IMS slice network, and is also sent by the MME to the UE.
  • the MME may also send such information to the UE through other messages.
  • the MME may also establish a session with the PGW, and the PGW obtains policy information from the PCRF (not shown). These steps are not shown in Figure 4, but may exist in a particular implementation.
  • the attach accept message sent by the MME may be forwarded to the UE by the radio base station. After receiving the attach accept message, the UE may locally save the following correspondence.
  • the above steps 402-404 describe the process by which the MME sends the slice identifier of the IMS slice network and the address of the IMS slice network to the UE.
  • the identifier of the IMS slice network and the address of the IMS slice network may also be pre-configured on the PGW.
  • the MME may obtain the IMS information from the PGW and send the IMS information to the UE, which is described in detail below.
  • Step 405 The UE sends a PDN connection request to the MME, where the UE establishes a PDN connection with the core network.
  • the UE may further send a PDN connection request to the core network to establish a PDN connection with the core network, so that the UE can perform data services.
  • the network connection request sent by the UE to the core network device may include a packet data network (PDN) connection request in addition to the previously mentioned attach request.
  • PDN packet data network
  • the PDN connection request is used to establish a PDN connection with the core network, where the identifier of the UE may be carried, and the location information of the UE may also be carried.
  • Step 406 The MME sends an IMS bearer setup request to the PGW to establish an IMS signaling bearer for the UE.
  • the IMS bearer setup request may be sent to the PGW in a create session request, and the setup session request may be used to establish a session between the MME and the PGW.
  • Step 407 The PGW sends an IMS bearer setup response to the MME, where the slice identifier of the IMS slice network and the address of the IMS slice network are carried.
  • the correspondence between the ID of the IMS slice network and the address of the IMS slice network is stored on the PGW.
  • the PGW can store all the IMSs of the IMS.
  • the mapping between the ID of the IMS network and the address of the IMS snippet network is sent to the MME, and the slice identifier of the corresponding IMS slice network and the address of the IMS slice network are also obtained according to the information of the UE.
  • the PGW may acquire the slice identifier of the corresponding IMS slice network and the address of the IMS slice network according to the number segment of the UE.
  • the PGW may also acquire the slice identifier of the corresponding IMS slice network and the address of the IMS slice network according to the location information of the UE.
  • the PGW may send an IMS bearer setup response to the MME, where the bearer setup response carries the IMS information.
  • the IMS bearer setup response may be sent to the MME by establishing a create session response message.
  • Step 408 The MME sends a PDN connection response to the UE, where the slice identifier of the IMS slice network and the address of the IMS slice network are carried.
  • the MME may add a cell in the PDN connection response to carry the slice identifier of the IMS slice network and the address of the IMS slice network, and then send the PDN connection response to the UE, and the UE parses the PDN connection response.
  • the slice identification of the IMS slice network and the address of the IMS slice network are obtained.
  • the MME in the EPC may acquire the slice identifier of the IMS slice network and the address of the IMS slice network from the HSS or the PGW, and then send the slice identifier of the IMS slice network and the IMS to the UE.
  • the address of the network is sliced so that the UE can initiate an IMS registration to the IMS slice network based on the IMS information, thereby initiating an IMS service in the IMS slice network.
  • FIG. 5 is a flowchart of a communication method provided in Embodiment 5 of the present application.
  • the communication method provided in this embodiment is mainly described from the perspective of the user equipment UE.
  • the UE After receiving the slice identifier of the IMS slice network and the address of the IMS slice network from the core network device, for example, from the AMF, the MME, or the PGW, the UE may The IMS slicing network initiates an IMS registration process.
  • the UE may initiate the IMS registration to both the IMS1 and the IMS2, that is, the IMS registration is initiated twice.
  • the specific process includes the following steps:
  • Steps 501-502 The UE sends a registration message to the IMS slice networks IMS1 and IMS2, where the slice identifier of the IMS slice network is carried.
  • the UE After receiving the session accept message sent by the AMF, the UE generates an IMS registration message according to the address of the IMS slice network carried in the UE, and sends an IMS registration message to the IMS slice network, where the message carries the slice of the corresponding IMS slice network. Identifies IMS1 or IMS2.
  • Steps 503-504 The UE receives the registration completion message sent by the IMS slice networks IMS1 and IMS2.
  • both the IMS1 and the IMS2 return a registration completion message, such as a 200 OK message, to the UE.
  • the registration completion message may carry the slice identifier of the IMS1 or the IMS2 to notify the UE to complete the IMS registration on the corresponding IMS slice network.
  • Step 505 The UE generates a voice service request message, and obtains service information corresponding to the service request message.
  • the UE may generate a service request message locally (for example, the user initiates a service actively), and obtain the service information corresponding to the service request message.
  • the service information is specifically a voice service
  • the service request message is specifically an invite message.
  • the UE can identify the service information of the service initiated by the user.
  • the service information may be a service type (for example, a voice service, a public security service, a low latency service, a video service, and the like).
  • the service information can also be a specific service name or service identifier. For example, if the user initiates a dialing procedure and dials a voice call, the UE determines that the user initiates a voice call service. If the user launches the AR/VR application, the UE may determine that the user initiated the low latency service. If the user initiates a mission-critical push-to-talk (MCPTT) application, the UE may determine that the user initiated the public security cluster service.
  • MCPTT mission-critical push-to-talk
  • Step 506 The UE determines a slice identifier of the IMS slice network corresponding to the service information in the service request, and sends a voice service request to the IMS2.
  • the UE may determine the slice identifier of the IMS slice network corresponding to the service information in the current service request message according to the correspondence between the slice identifier of the IMS slice network and the service information of the service provided by the IMS slice network, and then go to the IMS.
  • the IMS slice network corresponding to the slice identifier of the slice network sends the public security cluster service request.
  • the service request message generated by the UE may further carry a slice identifier of the IMS slice network.
  • the UE may determine that the IMS slice network corresponding to the voice service is IMS2, and then send a voice service request to the IMS2 according to the address 192.125.6.5 of the IMS2, thereby implementing The processing of the service request under IMS2.
  • the UE may obtain the slice identifier of the IMS slice network and the address of the IMS slice network from the core network, and then perform IMS registration in the IMS slice network. After the registration is successful, the UE may initiate a service in the IMS slice network.
  • the technical problem of failing to initiate a service in an IMS slicing network in the prior art is overcome.
  • FIG. 6 is a hardware structural diagram of a core network device according to Embodiment 6 of the present application.
  • the core network device may be implemented by using general-purpose computer hardware, and includes a processor 601, a memory 602, a bus 603, an input device 604, an output device 605, and a network interface 606.
  • memory 602 can include computer storage media in the form of volatile and/or nonvolatile memory, such as read only memory and/or random access memory.
  • Memory 602 can store operating systems, applications, other program modules, executable code, program data, user account opening data, user subscription data, and the like.
  • Input device 604 can be used to input commands and information to a core network device, such as a keyboard or pointing device such as a mouse, trackball, touch pad, microphone, joystick, game pad, satellite television antenna, scanner, or the like. . These input devices can be connected to the processor 601 via the bus 603.
  • a core network device such as a keyboard or pointing device such as a mouse, trackball, touch pad, microphone, joystick, game pad, satellite television antenna, scanner, or the like.
  • the output device 605 can be used for core network device output information.
  • the output device 605 can also be configured for other peripheral outputs, such as speakers and/or printing devices, which can also be connected to the processor via the bus 603. 601.
  • the core network device can be connected to the network through the network interface 606, for example, to a local area network (LAN).
  • LAN local area network
  • computer-executed instructions stored in a core network device can be stored in a remote storage device without being limited to local storage.
  • the core network device may perform the method steps on the core network device side in the above embodiment, for example, performing steps 202-203, 302. -306, 402-404, etc.
  • the core network device may perform the method steps on the core network device side in the above embodiment, for example, performing steps 202-203, 302. -306, 402-404, etc.
  • FIG. 7 is a schematic structural diagram of a user equipment according to Embodiment 7 of the present application.
  • the user equipment mainly includes a processor 701, a memory 702, a bus 703, an input device 704, an output device 705, and a network interface 706.
  • the user equipment may further include an application processor (AP), a battery, and the like.
  • AP application processor
  • memory 702 can include computer storage media in the form of volatile and/or nonvolatile memory, such as read only memory and/or random access memory.
  • Memory 702 can store operating systems, applications, other program modules, executable code, and program data.
  • Input device 704 can be used to input commands and information to a user device, such as a keyboard or pointing device, such as a mouse, trackball, touch pad, microphone, joystick, game pad, round dish satellite television antenna, scanner, or Similar equipment. These input devices can be connected to the processor 701 via a bus 703.
  • a user device such as a keyboard or pointing device, such as a mouse, trackball, touch pad, microphone, joystick, game pad, round dish satellite television antenna, scanner, or Similar equipment.
  • the output device 705 can be used for the user device to output information.
  • the output device 705 can also be configured for other peripheral outputs, such as speakers, which can also be connected to the processor 701 via the bus 703.
  • the user equipment can be connected to the network through the network interface 706, for example, through a wireless interface to a WIFI network, 5G, long term evolution (LTE) network.
  • a wireless interface to a WIFI network, 5G, long term evolution (LTE) network.
  • LTE long term evolution
  • computer-executed instructions stored in a user device can be stored in a remote storage device without being limited to local storage.
  • the user equipment may perform the method steps on the user equipment side in the above embodiment, for example, perform steps 204, 301, 401, 405, and the like. .
  • steps 204, 301, 401, 405 perform steps 204, 301, 401, 405, and the like.
  • FIG. 8 is a schematic diagram of functional modules of a core network device according to Embodiment 8 of the present application.
  • the core network device provided by the embodiment of the present application mainly includes an obtaining module 801 and a sending module 802.
  • the obtaining module 801 is configured to acquire a slice identifier of the IMS slice network and an address of the IMS slice network when receiving the network connection request of the user equipment UE.
  • the network connection request may be a PDN connection request, a PDU session establishment request, or a network attach request.
  • the sending module 802 is configured to send, to the UE, a slice identifier of the IMS slice network and an address of an IMS slice network.
  • the core network device provided by the embodiment of the present application may be used in the foregoing method embodiment, and the method steps of the core network device side in the foregoing method embodiment are implemented by the cooperation between the obtaining module 801 and the sending module 802.
  • the core network device provided in this embodiment has the same beneficial effects as the foregoing method embodiments when performing the above communication process.
  • the core network device provided in this embodiment includes a session management function SMF device, and the acquiring module 801 in the SMF device may obtain the slice identifier of the IMS slice network and the address of the IMS slice network from the NRF.
  • the sending module 802 in the SMF device is further configured to send a first request message to the user data management device, to request a slice identifier of the IMS slice network and an address of the IMS slice network, and then the SMF device
  • the obtaining module 802 is further configured to receive a first response message returned by the user data management device, where the first response message carries a slice identifier of the IMS slice network and an address of the IMS slice network.
  • the core network device may further include an access management function AMF device, where the AMF device may forward the slice identifier of the IMS slice network sent by the SMF device and the address of the IMS slice network to the UE.
  • AMF device may forward the slice identifier of the IMS slice network sent by the SMF device and the address of the IMS slice network to the UE.
  • the core network device provided by the embodiment of the present application may also be a packet gateway PGW.
  • the sending module 802 in the PGW sends the slice identifier of the IMS slice network and the address of the IMS slice network to the UE, which may include: the sending module 802. Sending a setup session response to the MME, where the setup session response carries the slice identifier of the IMS slice network and the address of the IMS slice network, so that the MME forwards the received slice identifier of the IMS slice network to the UE And the address of the IMS slice network.
  • the embodiment of the present application may enable the PGW to send the slice identifier of the IMS slice network and the address of the IMS slice network to the UE.
  • FIG. 9 is a schematic diagram of functions of a user equipment according to Embodiment 9 of the present application.
  • the user equipment provided by the embodiment of the present application may be applied to the IMS, and the method mainly includes:
  • the receiving module 901 is configured to receive a correspondence between a slice identifier of the IMS slice network and an address of the IMS slice network sent by the core network device.
  • the registration module 902 is configured to send an IMS registration message to the IMS slice network according to the address, where the registration message carries a slice identifier of the IMS slice network corresponding to the address.
  • the registration module in the user equipment may carry the slice identifier of the IMS slice network in the header field of the registration message.
  • the user equipment provided by the embodiment of the present application may be used in the foregoing method embodiment, and the method steps of the user equipment side in the method embodiment are implemented by the cooperation between the receiving module 901 and the registration module 902.
  • the user equipment provided by this embodiment has the same beneficial effects as the foregoing method embodiments when performing the above communication process.
  • the receiving module 901 is further configured to receive a registration completion message sent by the IMS slice network, where the registration completion message carries a slice identifier of the IMS slice network.
  • the registration completion message is used to notify the user equipment that the IMS registration of the IMS slice network is completed.
  • the user equipment provided in this embodiment further includes: a service requesting module 903, configured to generate a service request message, and a determining module 904, configured to determine, according to the corresponding relationship, a service information corresponding to the service request message.
  • the address of the IMS slice network, the service request module 903 is further configured to send the service request message to an IMS slice network corresponding to an address of the IMS slice network.
  • the core network device and the user equipment in the above embodiments 8 and 9 are all presented in the form of functional modules, where the “module” may refer to a specific application integrated circuit, a processor that executes one or more software or firmware programs. And memory, integrated logic, and/or other devices that provide the above functionality.
  • a core network device and a user equipment in this embodiment may also be implemented by using the hardware forms shown in FIG. 6-7, respectively.
  • the functions implemented by the acquisition module 801 and the transmission module 802 in the core network device can be implemented by the processor 601 and the memory 602 in FIG. 6.
  • obtaining the slice identification of the IMS slice network and the address of the IMS slice network by the acquisition module 801 can be implemented by the processor 601 executing the code stored in the memory 602.
  • the functions implemented by the receiving module 901 and the registration module 902 in the user equipment can be implemented by the processor 701 and the memory 702 in FIG.
  • the act of the registration module 902 transmitting an IMS registration message to the IMS slice network based on the address may be implemented by the processor 701 executing code stored in the memory 702.
  • the processor for implementing the foregoing user equipment and core network equipment may be a central processing unit, a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a transistor logic device, Hardware components or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations and the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computer Security & Cryptography (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé de communication, ainsi qu'un dispositif et un système associés dans un réseau IMS à tranches. Selon un mode de réalisation, un dispositif de réseau central envoie à un UE un identifiant de tranche de différents réseaux IMS à tranches et une adresse des réseaux IMS à tranches, de sorte que l'UE peut lancer un enregistrement sur les différentes tranches de réseau IMS, puis lancer un service dans les différents réseaux IMS à tranches.
PCT/CN2019/072014 2018-02-12 2019-01-16 Procédé de communication, et appareil et système associés WO2019154034A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810146938.2 2018-02-12
CN201810146938.2A CN110166405B (zh) 2018-02-12 2018-02-12 通信方法、相关装置及系统

Publications (1)

Publication Number Publication Date
WO2019154034A1 true WO2019154034A1 (fr) 2019-08-15

Family

ID=67548202

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/072014 WO2019154034A1 (fr) 2018-02-12 2019-01-16 Procédé de communication, et appareil et système associés

Country Status (2)

Country Link
CN (1) CN110166405B (fr)
WO (1) WO2019154034A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113852949A (zh) * 2021-09-26 2021-12-28 中国电子科技集团公司第五十四研究所 接入网关及卫星终端通过接入网关接入5g移动网络方法
WO2023149731A1 (fr) * 2022-02-03 2023-08-10 Samsung Electronics Co., Ltd. Procédé et appareil de restauration de fonction de commande de session d'appel mandataire dans un système de communication sans fil

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113543232A (zh) * 2020-04-21 2021-10-22 中国移动通信有限公司研究院 一种数据传输方法、终端、用户面功能实体及服务器
CN111741512B (zh) * 2020-06-02 2022-08-12 中国联合网络通信集团有限公司 一种专网接入方法及装置
CN113517995B (zh) * 2021-03-05 2024-03-12 深圳艾灵网络有限公司 网络切片建立方法和设备
CN114039868B (zh) * 2021-11-09 2023-08-18 广东电网有限责任公司江门供电局 一种增值业务管理方法和装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017063708A1 (fr) * 2015-10-15 2017-04-20 Telefonaktiebolaget Lm Ericsson (Publ) Appareil et procédé pour rattacher un équipement d'utilisateur à un réseau de communications mobiles
US20170318450A1 (en) * 2016-04-29 2017-11-02 Motorola Mobility Llc Procedures to support network slicing in a wireless communication system

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6110410B2 (ja) * 2012-01-31 2017-04-05 ヴィド スケール インコーポレイテッド スケーラブルな高効率ビデオコーディング（ｈｅｖｃ）のための参照ピクチャセット（ｒｐｓ）シグナリング
CN107409339B (zh) * 2015-04-08 2020-12-18 瑞典爱立信有限公司 用于在接入间切换的网络分区保存的方法和网络节点
CN106211104B (zh) * 2015-04-30 2019-11-19 中国电信股份有限公司 一种传输短信的终端、系统及方法
CN105813195B (zh) * 2016-05-13 2019-05-17 电信科学技术研究院有限公司 一种按需为终端选择移动性管理机制的方法及装置
US10362511B2 (en) * 2016-05-17 2019-07-23 Lg Electronics Inc. Method and apparatus for determining PDU session identity in wireless communication system
US9967801B2 (en) * 2016-06-10 2018-05-08 Lg Electronics Inc. Method and apparatus for receiving authorization information on network slice

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017063708A1 (fr) * 2015-10-15 2017-04-20 Telefonaktiebolaget Lm Ericsson (Publ) Appareil et procédé pour rattacher un équipement d'utilisateur à un réseau de communications mobiles
US20170318450A1 (en) * 2016-04-29 2017-11-02 Motorola Mobility Llc Procedures to support network slicing in a wireless communication system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HTC: "Association of Slice Id to PDU Session Id After EPC to 5GC Mobility", SA WG2 MEETING #124 S2-178640, 1 December 2017 (2017-12-01), XP051379648 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113852949A (zh) * 2021-09-26 2021-12-28 中国电子科技集团公司第五十四研究所 接入网关及卫星终端通过接入网关接入5g移动网络方法
CN113852949B (zh) * 2021-09-26 2024-02-23 中国电子科技集团公司第五十四研究所 接入网关及卫星终端通过接入网关接入5g移动网络方法
WO2023149731A1 (fr) * 2022-02-03 2023-08-10 Samsung Electronics Co., Ltd. Procédé et appareil de restauration de fonction de commande de session d'appel mandataire dans un système de communication sans fil

Also Published As

Publication number Publication date
CN110166405A (zh) 2019-08-23
CN110166405B (zh) 2022-03-11

Similar Documents

Publication Publication Date Title
WO2019154034A1 (fr) Procédé de communication, et appareil et système associés
US11039381B2 (en) SMF selection based on supported DNN
CN109951876B (zh) 通信方法、相关装置及系统
US11218519B2 (en) Service based P-CSCF discovery
US11496526B2 (en) Service request processing method, apparatus, and communications system
US11178000B2 (en) Method and system for processing NF component exception, and device
CN113573326B (zh) 一种地址获取方法及装置
US10104532B2 (en) Processing method and device for device to device (D2D) discovery
US11979247B2 (en) Message forwarding method and apparatus
WO2022052875A1 (fr) Procédé de communication inter-région de terminal, dispositif d'élément de réseau, et support de stockage
WO2021008313A1 (fr) Procédé de mise en œuvre de continuité de service, appareil et système associés
JP2023518344A (ja) ユーザ装置またはｐｐｄｕセッションにサービスする分散ネットワーク機能の露出と発見
WO2019144786A1 (fr) Procédé d'abonnement à des informations sans fil, dispositifs associés, et système
US20230370823A1 (en) Network capability exposure method, device, and storage medium
WO2015085573A1 (fr) Procédé et dispositif de communication utilisant un spectre blanc
EP4319232A1 (fr) Procédé et appareil de communication
WO2015196809A1 (fr) Procédé et dispositif de traitement de message
WO2022007657A1 (fr) Procédé et appareil pour envoyer une demande de système de noms de domaine
CN111031528A (zh) 一种专用网络的连接建立方法和装置
JP6573288B2 (ja) 発見方法および装置
WO2023093271A1 (fr) Procédé et appareil de détermination de s-cscf
US20220329986A1 (en) Multicast service implementation method and apparatus, and communications device
WO2022088183A1 (fr) Procédé et appareil de communication
WO2024012070A1 (fr) Procédé et appareil d'appel d'urgence, dispositif associé
WO2022033491A1 (fr) Procédé d'authentification et appareil 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: 19750516

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

Country of ref document: EP

Kind code of ref document: A1