WO2019154034A1

WO2019154034A1 - Communication method, related apparatus and system

Info

Publication number: WO2019154034A1
Application number: PCT/CN2019/072014
Authority: WO
Inventors: 张彪; 舒续祖
Original assignee: 华为技术有限公司
Priority date: 2018-02-12
Filing date: 2019-01-16
Publication date: 2019-08-15
Also published as: CN110166405A; CN110166405B

Abstract

Provided are a communication method, related device and system in an IMS slice network. In this embodiment, a core network device sends a slice identifier of different IMS slice networks and an address of the IMS slice network to a UE, so that the UE can initiate registration to the different IMS network slices, and in turn initiate a service in the different IMS slice networks.

Description

Communication method, related device and system

This application claims priority to Chinese Patent Application No. 201101146938.2, entitled "Communication Method, Related Devices and Systems", filed on February 12, 2018, the entire contents of which are hereby incorporated by reference. In the application.

Technical field

The present invention relates to the field of communications technologies, and in particular, to a communication method, related apparatus, and system.

Background technique

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.

However, in some scenarios, 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.

Summary of the invention

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.

In an aspect, 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:

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.

In the solution provided by the first aspect, 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.

In one possible solution, 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.

In a possible solution, 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.

In one possible solution, the core network device includes a session management function SMF device. At this time, 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. In addition, 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.

In a possible solution, 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.

In a possible solution, 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:

Sending, by the MME, a second request message to the home subscriber server, requesting a slice identifier of the IMS slice network and an address of the IMS slice network, and then receiving a second response message sent by the home subscriber server, the second response The message carries the slice identifier of the IMS slice network and the address of the IMS slice network. 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.

In a possible solution, 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.

In a second aspect, 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:

Receiving, by the UE, a correspondence between a slice identifier of the IMS slice network and an address of the IMS slice network, and then sending an IMS registration message to the IMS slice network according to the address, performing IMS registration, where the registration is performed. The message carries a slice identifier of the IMS slice network corresponding to the address. With the technical solution provided by the second aspect, 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.

In a possible solution, 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.

In a possible solution, the user equipment carries a slice identifier of the IMS slice network in a header field of the registration message.

In a possible solution, 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.

In a possible solution, 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.

In a possible solution, 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.

In one possible solution, the service request message generated by the UE may carry the slice ID of the IMS slice network.

In a possible solution, 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.

In a third aspect, 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.

With the solution provided by the third aspect, 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.

In a possible solution, 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.

In a fourth aspect, 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;

And 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.

In a possible solution, 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.

In one possible solution, 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.

In a possible solution, 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.

In a fifth aspect, 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;

And 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.

In a possible solution, 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.

In a possible solution, 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.

In a sixth aspect, 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. For the specific implementation process, refer to the first aspect.

In a seventh 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. For the specific implementation process, refer to the foregoing second aspect and Description of the third aspect.

In an eighth 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.

In an embodiment provided by any of the above aspects, the service request message may be an invite message, and the network connection request may be an attach request, a PDN connection setup request, or a session establishment request.

In an embodiment provided in any of the above aspects, the slice address of the IMS slice network may be the address of the P-CSCF in the IMS slice network.

DRAWINGS

1 is a schematic diagram of networking of a communication system according to Embodiment 1 of the present application;

2 is a flowchart of a communication method provided in Embodiment 2 of the present application;

3 is a flowchart of a communication method provided in Embodiment 3 of the present application;

4 is a flowchart of a communication method provided in Embodiment 4 of the present application;

5 is a flowchart of a communication method provided in Embodiment 5 of the present application;

6 is a hardware structural diagram of a core network device according to Embodiment 6 of the present application;

7 is a hardware structural diagram of a user equipment provided in Embodiment 7 of the present application;

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.

Detailed ways

The present application provides a communication method, related apparatus, and system. Referring to FIG. 1, FIG. 1 is a schematic diagram of networking of a communication system according to Embodiment 1.

As shown in FIG. 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.

Among them, 5GC can perform network segmentation, and 5GC can also not slice. For example, 5GC is cut into 5GC1 and 5GC2. In addition, 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. In addition, 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). 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. In addition, 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.

After the UE is powered on, 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. After the registration is completed, 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. Cluster service, which initiates voice call service or augmented reality (AR) service in IMS2.

Compared with the prior art, 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. In this embodiment, 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.

In this embodiment, different IMS slice networks can be distinguished by slice identification. 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. In addition, 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. When the core network device provides the slice identifier of the IMS slice network to the UE, the service information of the service provided by the IMS slice network is also provided to the UE. In addition, 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.

Based on the above communication system, the present embodiment provides a communication method. Referring to FIG. 2, 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. Thus, 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.

In addition, 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. For example, 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.

In addition, 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.

In this embodiment, 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.

In this embodiment, 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. For example, the SMF, AMF, or the combination in the 5GC can implement the functions of the core network device, and 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.

In this embodiment, 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. Optionally, 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.

In this embodiment, if the core network device returns information of multiple IMS slice networks (the slice identifier of the IMS slice network and the address of the corresponding 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.

Referring to FIG. 3, FIG. 3 is a flowchart of a communication method provided in Embodiment 3 of the present application.

In this embodiment, 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.

In this embodiment, 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). In this embodiment, 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.

Among them, 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.

In this embodiment, 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.

In addition, 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.

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.

In this embodiment, 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. For example, 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.

In this embodiment, 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.

In this embodiment, 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.

In this embodiment, 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. In addition, 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.

In addition, between steps 304-305, 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.

In this embodiment, 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.

IMS切片网络的切片标识Slice ID of the IMS slice network	IMS切片网络的地址IMS slice network address	业务信息Business information
IMS1IMS1	192.125.6.3192.125.6.3	VR/ARVR/AR
IMS2IMS2	192.125.6.5192.125.6.5	语音业务Voice service

In the communication method provided by the embodiment, 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.

Referring to FIG. 4, FIG. 4 is a flowchart of a communication method provided in Embodiment 4 of the present application.

In this embodiment, 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.

In this embodiment, the network connection request sent by the UE to the core network device by using the base station (not shown) 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.

In this embodiment, the core network device is an MME. In addition, 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.

In this embodiment, the MME may add a cell that acquires IMS slice information in the second request message sent to the HSS. In this embodiment, 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.

In addition, 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.

In this embodiment, 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. For example, 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.

In this embodiment, the IMS slice network acquired by the HSS includes IMS1 and IMS2. IMS1 provides public security cluster services, and 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.

In this embodiment, after acquiring the slice identifier of the IMS slice network and the address of the IMS slice network, the MME may send the message to the UE by using an attach accept message. In addition, 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.

In addition to the attach accept message mentioned above, the MME may also send such information to the UE through other messages.

Between steps 403-404, 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. Optionally, 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.

In this embodiment, after receiving the attach accept message, 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.

In this embodiment, 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. 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.

In this embodiment, 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.

In this embodiment, the correspondence between the ID of the IMS slice network and the address of the IMS slice network is stored on the PGW. After receiving the setup session request carrying the IMS bearer setup request, 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. For example, 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.

After the IMS information is obtained, the PGW may send an IMS bearer setup response to the MME, where the bearer setup response carries the IMS information. In this embodiment, 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.

In this embodiment, 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.

In the communication method provided in this embodiment, 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.

Referring to FIG. 5, 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. 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.

In this embodiment, 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.

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.

In this embodiment, after the registration process is completed, 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.

In this embodiment, 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. In this embodiment, the service information is specifically a voice service, and 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.

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.

In this embodiment, after determining that the service information in the service request is a voice service, 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.

In this embodiment, 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.

Referring to FIG. 6, 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.

In particular, 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.

The output device 605 can be used for core network device output information. In addition to the monitor, 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). In a networked environment, computer-executed instructions stored in a core network device can be stored in a remote storage device without being limited to local storage.

When the processor 601 in the core network device executes the executable code or application stored in the memory 602, 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. For the specific implementation process, refer to the foregoing embodiment, and details are not described herein again.

Referring to FIG. 7, 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. In addition, the user equipment may further include an application processor (AP), a battery, and the like.

In particular, 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.

The output device 705 can be used for the user device to output information. In addition to the display screen, 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. In a networked environment, computer-executed instructions stored in a user device can be stored in a remote storage device without being limited to local storage.

When the processor 701 in the user equipment executes the executable code or application stored in the memory 702, 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. . For specific implementation processes and beneficial effects, refer to the related embodiments above, and details are not described herein again.

Referring to FIG. 8, FIG. 8 is a schematic diagram of functional modules of a core network device according to Embodiment 8 of the present application.

As shown in the figure, 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. Compared with the core network device in the prior art, the core network device provided in this embodiment has the same beneficial effects as the foregoing method embodiments when performing the above communication process.

Optionally, 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.

Optionally, 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.

Optionally, 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.

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.

Referring to FIG. 9, FIG. 9 is a schematic diagram of functions of a user equipment according to Embodiment 9 of the present application.

As shown in the figure, 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. For details, refer to the foregoing method. Example. Compared with the user equipment in the prior art, the user equipment provided by this embodiment has the same beneficial effects as the foregoing method embodiments when performing the above communication process.

Optionally, in the user equipment provided in this embodiment, 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.

Optionally, 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.

For example, 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. For example, 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. For example, 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.

In addition, 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.

It should be noted that the technical solutions between the foregoing multiple embodiments provided by the present application may be combined with each other.

The foregoing is only a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the present application. It should be covered by the scope of protection of this application. Therefore, the scope of protection of the present application should be determined by the scope of the claims.

Claims

A communication method in an IMS slicing network of an IP multimedia subsystem, comprising:

Receiving, by the core network device, 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 core network device sends a slice identifier of the IMS slice network and an address of an IMS slice network to the UE.
The method according to claim 1, wherein the core network device comprises a session management function SMF device, and the core network device acquiring the slice identifier of the IMS slice network and the address of the IMS slice network includes:

The SMF device acquires a slice identifier of the IMS slice network and an address of the IMS slice network from a network storage function NRF; or

Sending, by the SMF device, a first request message to the user data management device, for requesting a slice identifier of the IMS slice network and an address of the IMS slice network;

The SMF device receives 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 method according to claim 1, wherein the core network device comprises an access management function AMF device and a session management function device SMF, and the core network device sends a slice identifier of the IMS slice network to the UE And the address of the IMS slicing 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;

The AMF device sends a session accept message to the UE, where the session accept message carries a slice identifier of the IMS slice network and an address of an IMS slice network.
The method of claim 1, wherein the core network device comprises a mobility management entity MME, and the core network device acquiring the slice identifier of the IMS slice network and the address of the IMS slice network comprises:

Sending, by the MME, a second request message to the home subscriber server, for requesting a slice identifier of the IMS slice network and an address of the IMS slice network;

The MME receives a second response message sent by the home subscriber server, where the second response message carries a slice identifier of the IMS slice network and an address of the IMS slice network.
The method of claim 1, wherein the core network device is a packet gateway PGW, and the core network device 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 an address of the IMS slice network;

The MME forwards the received slice identifier of the IMS slice network and the address of the IMS slice network to the UE.
A communication method in an IMS slicing network of an IP multimedia subsystem, which is applied to a user equipment, and includes:

Receiving, by the core network device, a correspondence between a slice identifier of the IMS slice network and an address of the IMS slice network;

Sending 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 method of claim 6, wherein the user equipment carries a slice identifier of the IMS slice network in a header field of the registration message.
The method according to claim 7, wherein the user equipment receives an address of the IMS slice network from the 5G core network device when establishing a PDU session with the 5G core network slice.
The method of claim 6 further comprising:

Receiving 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 method of claim 9 further comprising:

Generating a service request message, and determining an address of the IMS slice network corresponding to the service information in the service request message according to the correspondence relationship;

The service request message is sent to an IMS slice network corresponding to an address of the IMS slice network.
The method according to claim 10, wherein the determining the address of the IMS slice network corresponding to the service information in the service request message comprises:

Determining a slice identifier of the IMS slice network corresponding to the service information in the service request message;

Determining an address of the IMS slice network corresponding to the slice identifier of the IMS slice network according to the correspondence.
A core network device, comprising:

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;

And 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 according to claim 12, wherein said core network device comprises a session management function SMF device,

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;

The acquiring module in the SMF device 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 according to claim 13, wherein the core network device is a packet gateway PGW, and a sending module in the PGW sends a slice identifier of the IMS slice network and an IMS slice network to the UE. The address includes:

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.
A user equipment applied to an IP multimedia subsystem, comprising:

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;

And 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 according to claim 15, wherein the user equipment carries a slice identifier of the IMS slice network in a header field of the registration message.
The user equipment according to claim 15, wherein the receiving module is further configured to receive a registration completion message sent by the IMS chip network, where the registration completion message carries a slice identifier of the IMS slice network.
The user equipment of claim 15, further comprising:

a service request module, configured to generate a service request message;

a determining module, configured to determine, according to the correspondence, an address of an IMS slice network corresponding to the service information in the service request message;

The service requesting module is further configured to send the service request message to an IMS slice network corresponding to an address of the IMS slice network.