WO2019184717A1

WO2019184717A1 - Communication method and related product

Info

Publication number: WO2019184717A1
Application number: PCT/CN2019/078151
Authority: WO
Inventors: 张彪; 舒续祖
Original assignee: 华为技术有限公司
Priority date: 2018-03-30
Filing date: 2019-03-14
Publication date: 2019-10-03
Also published as: CN110324291B; CN110324291A

Abstract

Provided are a communication method and a related product. The method comprises: after receiving a registration request from a user equipment (UE), a common IMS carrying out registration for the UE; and if a call request sent by the UE is received after the registration for the UE is successful, selecting a session IMS slice for the UE, and forwarding the call request to the session IMS slice; or after the UE passes the registration, sending information of the session IMS slice to the UE, wherein the information of the session IMS slice is used for the UE to call the session IMS slice. A common IMS is responsible for the function of carrying out registration for a UE, and the UE does not need to be docked with multiple IMS slices; therefore, the requirements for the UE are lower. The UE does not need to search for multiple IMS slices, and the common IMS forwards a call request or sends the call request according to the IMS slices provided by the common IMS. Therefore, the network deployment complexity is lower.

Description

Communication method and related products

This application claims priority to Chinese Patent Application No. 201101286666.6, entitled "Communication Method, and Related Products", filed on March 30, 2018, the entire contents of which are hereby incorporated by reference. In this application.

Technical field

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

Background technique

The operator has plans to provide an industry communication solution, requiring user equipment (UE) to simultaneously access multiple internet protocol multimedia subsystems (IMS), each of which provides different real-time service types. For example, IMS1 provides mission-critical push-to-talk (MCPTT) services, and IMS2 provides common voice services.

The UE can simultaneously access the IMS1 and the IMS2, and the IMS registration can be initiated by the UE to the IMS slice 1 (slice 1) and the IMS slice 2, respectively, and the UE initiates the voice over long term evolution (VoLTE) public network voice service. Select IMS slice1, and select IMS slice2 when the UE initiates the MCPTT service.

The above solution has higher requirements for the UE and the network deployment is more complicated.

Summary of the invention

The technical problem to be solved by the embodiments of the present invention is to provide a communication method and related products, which reduce the requirements on the UE and the complexity of network deployment.

An embodiment of the present invention provides a communication method, including:

The common IMS receives a registration request from the user equipment UE, and registers with the UE;

Receiving a call request sent by the UE after the UE is successfully registered, selecting a session IMS slice for the UE, and forwarding the call request to the session IMS slice;

Or transmitting, after the UE is registered, the information of the session IMS slice to the UE, where the information of the session IMS slice is used by the UE to call the session IMS slice.

The address of the general IMS can be obtained by the packet switching (PS) core network through configuration, etc., and then sent to the UE by using a non-access stratum (NAS) message, and then the UE sends a registration to the universal IMS according to the address of the universal IMS. request.

The above registration success means that after the registration is completed, the above registration means that the authentication is passed during the authentication process and does not have to be registered. The session IMS slice is a slice that provides services for the UE. The information of the IMS slice may include information of one IMS slice or more information of the IMS slice. If information of two or more IMS slices is included, then The IMS slice can be selected by the UE as the session IMS slice, which is not limited in this embodiment.

In this embodiment, the universal IMS is an IMS shared by multiple IMS slices, and the universal IMS is responsible for registering functions for the UE, so the UE does not have to connect to multiple IMS slices, so the requirements for the UE are low; In the process, the UE does not have to search for multiple IMS slices, forward the call request by the universal IMS or send a call request according to the IMS slice provided by the universal IMS; therefore, the network deployment complexity is lower.

As a possible implementation, a process for selecting a session IMS slice and forwarding a call request is further provided as follows: the selecting a session IMS slice for the UE, and forwarding the call request to the session IMS slice includes:

Obtaining a service type identifier from the call request, obtaining the session IMS slice, and obtaining an address of the session IMS slice; the session IMS slice is an IMS slice corresponding to the service type specified by the service type identifier;

And forwarding the call request to the session IMS slice according to the address of the session IMS slice.

As a possible implementation, the process of obtaining a session IMS slice is also provided as follows: the obtaining the session IMS slice includes:

In a domain name server (DNS) or a network repository function (NRF), an IMS slice corresponding to the service type specified by the service type identifier is queried as a session IMS slice.

It should also be noted that if the correspondence between the service type and the IMS slice is stored in the general IMS, it is not necessary to query from the DNS or the NRF.

As a possible implementation, a specific example of the information of the session IMS slice is also provided as follows: the information of the session IMS slice includes:

The address of the session IMS slice and the type of service supported by the session IMS slice.

The purpose of the information of the session IMS slice is to let the UE know how to call to the session IMS slice, and thus can contain all the necessary various information, and the above information should not be construed as an exhaustive list of session IMS slice information.

As a possible implementation manner, an optional implementation of the registration is also provided as follows: the registering for the UE includes:

Obtaining a five-tuple authentication vector from a home subscriber server (HSS), authenticating the UE by using the five-tuple authentication vector, and determining that the UE is registered after the UE is authenticated Determining that the UE registration is successful after sending a response message indicating that the authentication is passed to the UE.

The above five-tuple authentication vector may include: expected response (XRES), random challenge (RAND), authentication attenuator token (AUTN), integrity key (IK), and The ciphering key (CK); the process of using the quintuple authentication vector for authentication is not limited by the embodiment of the present invention.

The second embodiment of the present invention further provides a communication method, including:

The user equipment UE sends a registration request to the universal internet protocol multimedia subsystem IMS;

Receiving, after the UE is registered, the information of the session IMS slice sent by the universal IMS;

Sending a call request to the session IMS according to the information of the session IMS slice.

As a possible implementation, the specific implementation manner of receiving the information of the session IMS slice is as follows: the receiving the information of the session IMS slice sent by the universal IMS includes:

Receiving a response message indicating that the authentication is passed, parsing the response new message to obtain information of the session IMS slice.

The response message passed by the knowledge authentication can usually be a 200 OK message.

As a possible implementation, a specific example of the information of the session IMS slice is also provided as follows: the session IMS information includes:

The invention also provides a communication device, which is used as a universal Internet Protocol Multimedia Subsystem IMS, and includes:

a receiving unit, configured to receive a registration request from the user equipment UE;

a registration unit, configured to register, after the receiving unit receives a registration request from the user equipment UE,

The receiving unit is further configured to: after the registration unit successfully registers the UE, receive a call request sent by the UE; and the selecting unit is configured to: after the receiving unit receives the call request sent by the UE, Selecting a session IMS slice for the UE, and sending, by the sending unit, the call request to the session IMS slice;

Or the sending unit, configured to send information of the session IMS slice to the UE after the UE registers, the information of the session IMS slice is used by the UE to call the session IMS slice.

As a possible implementation, the selecting unit is configured to obtain a service type identifier from the call request, obtain the session IMS slice, and obtain an address of the session IMS slice; the session IMS slice is the The IMS slice corresponding to the service type specified by the service type identifier;

The sending unit is configured to forward the call request to the session IMS slice according to an address of the session IMS slice.

As a possible implementation, the selecting unit, configured to obtain the session IMS slice, is configured to: in the domain name server DNS or network storage function NRF, query an IMS corresponding to the service type specified by the service type identifier Slice as a session IMS slice.

As a possible implementation manner, the information of the session IMS slice includes:

As a possible implementation, the registration unit is configured to obtain a 5-tuple authentication vector from the home subscriber server HSS, use the 5-tuple authentication vector to authenticate the UE, and authenticate the UE. After the UE is determined to pass the registration, the UE is determined to be successfully registered after sending a response message indicating that the authentication is passed to the UE by using the sending unit.

The fourth embodiment of the present invention further provides a communication device, which is used as a user equipment UE, and includes:

a sending unit, configured to send a registration request to the universal internet protocol multimedia subsystem IMS;

a receiving unit, configured to receive, after the UE is registered, the information of the session IMS slice sent by the universal IMS;

The sending unit is further configured to send a call request to the session IMS according to the information of the session IMS slice.

As a possible implementation manner, the receiving unit includes:

The receiving subunit is configured to receive a response message indicating that the authentication is passed;

And a parsing unit, configured to parse the response message to obtain information of the session IMS slice.

As a possible implementation manner, the session IMS information includes:

The fifth embodiment of the present invention further provides a communication device, including: an input device, an output device, a processor, and a storage device; a program code is stored in the storage device, and the processor is configured to invoke the program code to Controlling the input device and the input device and the processor cooperate to perform the method of any one of the embodiments of the present invention.

The embodiment of the present invention further provides a computer storage medium, where the computer storage medium stores a computer program, where the computer program includes program instructions, and when the program instructions are executed by the processor, the embodiment of the present invention is provided. Any of the methods described.

The embodiment of the present invention further provides a computer program product, where the computer program product includes program instructions, and when the program code is executed by the processor, the processor cooperates with the receiving device or the transmitting device to perform the embodiment of the present invention. Any of the methods provided.

The embodiment of the invention further provides a communication system, comprising: a universal internet protocol multimedia subsystem IMS, and two or more session IMS slices;

The general IMS is used to perform any method step performed by the universal IMS provided by the embodiment of the present invention;

The session IMS slice is configured to receive a call request forwarded by the universal IMS, perform session processing, or receive a call request sent by the UE, and perform session processing.

As a possible implementation manner, the communication system further includes: a packet switched PS core network; and if the universal IMS forwards a call request of the UE to the session IMS slice, the PS core network and the universal IMS a communication connection, the universal IMS is in communication with a media plane of the session IMS slice; if the universal IMS sends session IMS slice information to the UE, the PS core network and the universal IMS and the session The media faces of the IMS slices are respectively communicatively connected.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the background art, the drawings to be used in the embodiments of the present invention or the background art will be described below.

1 is a schematic structural diagram of a system according to an embodiment of the present invention;

2 is a schematic structural diagram of a system according to an embodiment of the present invention;

3 is a schematic structural diagram of a system according to an embodiment of the present invention;

4 is a schematic structural diagram of a system according to an embodiment of the present invention;

FIG. 5 is a schematic flowchart of a method according to an embodiment of the present invention; FIG.

6 is a schematic flowchart of a registration method according to an embodiment of the present invention;

7 is a schematic flowchart of a call method according to an embodiment of the present invention;

8 is a schematic flowchart of a registration method according to an embodiment of the present invention;

9 is a schematic flowchart of a call method according to an embodiment of the present invention;

FIG. 10 is a schematic structural diagram of a communication apparatus according to an embodiment of the present invention; FIG.

11 is a schematic structural diagram of a communication device according to an embodiment of the present invention;

12 is a schematic structural diagram of a communication device according to an embodiment of the present invention;

FIG. 13 is a schematic structural diagram of a communication apparatus according to an embodiment of the present invention.

detailed description

The embodiments of the present invention are described below in conjunction with the accompanying drawings in the embodiments of the present invention.

As shown in FIG. 1 , a system example of a 5G communication system includes: a UE, a radio access network (RAN), or an access network (AN), and a user interface function (user plane). Function, UPF) device, data network (DN), authentication management field (AMF), service management function (SMF) device, policy control function (PCF) device, An application function (AF) device, an authentication server function (AUSF) device, a unified data management (UDM) device, and an N1-N15 interface for communication.

FIG. 2 is a schematic diagram of a structure diagram of a network system according to an embodiment of the present invention, and relates to a network element mainly involved in an embodiment of the present invention, wherein a multimedia telephony (MMTEL) access stratum (AS), And MCPTT AS belong to two slices of IMS1 and IMS2. The IMS1 and the IMS2 respectively include a serving call session control function (S-CSCF) device, a proxy call session control function (P-CSCF) device, and an inquiry call session control function ( Interrogating call session control function, I-CSCF) device. Among them, the 5G core network (5GC)/evolved core network (EPC) is a common part of IMS1 and IMS2. In the above Figure 2, the UE accesses the IMS1 and the IMS2 at the same time, and the IMS registration can be initiated by the UE to the IMS slice1 and the IMS slice2, respectively. When the UE initiates the voice service based on the VoLTE public network, the IMS slice1 is selected, and the UE selects the MCPTT service. IMS slice2. An IMS slice refers to an IMS that divides different IMS slices according to service information (such as a service type, a service identifier), a user number segment, or a terminal type. The IMS identifier (ID) is used to identify different IMS slices, that is, different identifiers. IMS network. The use of the I-CSCF in the system shown in FIG. 2 includes: allocating an S-CSCF to a UE that initiates a registration request; in a session-related and session-independent process, a session initiation protocol from another network (session initiation protocol, The SIP request is routed to the S-CSCF; the HSS is queried, the address of the S-CSCF serving the UE is obtained from the HSS, and the SIP request or response is forwarded to the S-CSCF according to the S-CSCF address obtained from the HSS.

3 and FIG. 4 are schematic diagrams showing the structure diagrams of two other network systems according to an embodiment of the present invention, in which a common IMS is added in the network system architecture; IMS slice 1 and IMS slice 2 include session IMS1 and session IMS2. And the corresponding media plane; based on the above two possible network structure systems, the communication method provided by the embodiment of the present invention, as shown in FIG. 5, includes:

501: The UE sends a registration request to the universal IMS.

502: After receiving the registration request of the user equipment UE, the universal IMS registers with the UE.

503A: After the foregoing UE is successfully registered, the UE sends a call request to the universal IMS.

The above call request should typically contain information such as the service type identifier used to specify the type of service.

504A: The universal IMS selects a session IMS slice for the UE, and forwards the call request to the session IMS slice.

In this step, the universal IMS selects the session IMS slice of the call for the UE according to the information carried in the call request.

Or after 502, execute:

503B: After the UE is registered, the information about the session IMS slice is sent to the UE, where the information of the session IMS slice is used by the UE to call the session IMS slice.

The information of the session IMS slice may be carried to the UE in a response message that is successfully registered, for example, a 200 OK message.

The information of the session IMS slice may generally include information such as the address, service type, and the like of the session IMS slice.

504B: The UE sends a call request to the session IMS slice.

In this embodiment, the universal IMS is an IMS shared by multiple IMS slices, and the universal IMS is responsible for registering functions for the UE, so the UE does not have to connect to multiple IMS slices, so the requirements for the UE are low; the call is initiated at the UE. In the process, the UE does not have to search for multiple IMS slices, forward the call request by the universal IMS or send a call request according to the IMS slice provided by the universal IMS; therefore, the network deployment complexity is lower.

In the following embodiments, the network system structures shown in FIG. 3 and FIG. 4 above will be respectively illustrated.

First, the network system structure shown in Figure 3.

In Figure 3, the common IMS shields the IMS slice from the packet switching (PS) core network (5GC/EPC) and the UE, and the UE and PS core network only see the common IMS.

Among them, the main responsibilities of common IMS: processing IMS registration and session flow in selecting IMS slice 1 or IMS slice 2. Both the UE and the PS core network do not need to be enhanced for IMS slices. It includes the registration management functions of the P-CSCF and S-CSCF in the IMS architecture.

Session IMS's main responsibilities: handling session, routing, policy and charging control (PCC) process quality of service (QoS) control and service triggering. The session IMS may include session management, media control, QoS control functions, and S-CSCF session management functions of the P-CSCF in the IMS architecture.

The main responsibilities of the media: codec, playback, Internet Protocol version 4 (IPV4) / IPV6 conversion, DTMF and other IMS media processing functions. The media side device may include an IMS-access gateway (AGW) in the current protocol.

In the system shown in FIG. 3, the manner in which the UE obtains the common IMS address may be the same as the manner in which the UE obtains the P-CSCF address, for example, after the 5GC/EPC obtains the common IMS address through configuration, the NAS message is obtained. The intermediate sends the address of the common IMS to the UE.

The common IMS selects the session IMS in the corresponding IMS slice according to the DNS configuration policy or according to the internal configuration in the common IMS.

The session IMS and the media side can be linked by a protocol such as H.248.

A session initiation protocol (SIP) protocol can be used between common IMS and session IMS.

Based on the network system structure shown in FIG. 3, in the registration process shown in FIG. 6, the common IMS provides a common IMS registration service for the two IMS slices, and the UE does not need to perform enhancement processing. The detailed process is as follows:

601: The UE sends a registration message to the common IMS to request IMS registration.

In this step, the UE may first read the universal subsiberian identity module (USIM) card information to obtain an international mobile subscriber identity (IMSI), and then derive the IMS private user from the IMSI. IMS private user identity (IMPI) and IMS temporary multimedia public identity (T-IMPU); sending a register message to the address of the common IMS requesting IMS registration; the content of the register message and the IMS registration procedure initiated by the UE The register message can be identical and does not require enhancement. The main parameters of the register message are as follows:

From/To header field: The Internet protocol multimedia public identity (IMPU) of the registered user, filled in as T-IMPU.

Contact header field: The contact address of the registered user.

Expires: Registration duration.

Authorization header field: Includes the IMPI of the registered user.

Security-Client header field: Instructs the UE to use internet security (IPSec) authentication and authentication key agreement (AKA) authentication mode, where alg is the integrity protection algorithm, spi-c/spi-s For the security parameter index (SPI), port-c/port-s is the secure port number of the UE.

Require/Proxy-Require header field: Indicates that the UE requires IPSec AKA authentication.

602: The common IMS and the HSS interact to obtain the user's 5-tuple authentication vector.

The quintuple authentication vector may include: XRES, RAND, AUTN, IK, and CK.

603: The common IMS sends a 401 response to the UE.

The common IMS saves the parameter XRES for subsequent verification of the user's authentication response. Other authentication elements are sent to the UE with a 401 response. An example of the above 401 response message: containing RAND and AUTN.

604: After receiving the 401 response, the UE authenticates the AUTN according to the shared key stored in the local USIM. If the authentication succeeds, the 401 message is originated from the real home network of the user; and the response is calculated based on the shared key and the RAND (response, RES), CK, and IK, reconstruct the register message, carry the AUTN, RAND, and RES, and send it to the common IMS according to the path of the register message in step 601.

605: After receiving the register message, the IMS compares the expected authentication response XRES with the actually received authentication response RES. If the two match, the network authenticates the UE. The common IMS to IMS HSS obtains user subscription data.

606: The common IMS returns a 200 OK response to the UE.

The IMPU list of the implicit registration set bound to the T-IMPU in the P-Associated-URI header field of the 200 OK response, including the mobile station international ISDN number (MSISDN) and the telephone (Tel) unified The Uniform Resource Identifier (URI) and the SIP URI of the user indicate that all the numbers in the user's implicit registration set are successfully registered.

The above 401 and 200 OK responses may refer to the third generation mobile communication partner project (3GPP) protocol, and details are not described herein again.

Based on the network system structure shown in FIG. 3, in the call flow shown in FIG. 7, the call message is implemented by using an invite message in the flow, and the detailed process is as follows:

701: The UE initiates a session, and sends an invite message to the common IMS.

In the invite message, you can carry the following key information:

From: caller number;

Request-URI: the called user number;

Contact header field: the contact address of the calling user;

Feature-tag: service type identifier;

Session description protocol (SDP): The media capability of the calling UE, including the supported media types and the codec capabilities of the corresponding media.

702: The common IMS selects the IMS slice as the session IMS slice and forwards the invite message to the IMS slice.

The process of selecting an IMS slice may be: selecting a corresponding IMS slice according to the service type identifier carried in the feature-tag in the invite message, the calling user number in the From header field, and the feature data subscribed by the user in the HSS. The address configuration/registration of the IMS slice is in the DNS/Network Storage Function (NRF) or in the Common IMS. If configured/registered in the DNS/NRF, the DNS/NRF needs to be enhanced to support the configuration of the IMS slice address and support. The correspondence of the type of business.

703: After receiving the invite message, the IMS slice performs session processing and service triggering.

704: The IMS slice sends an 18x message to the common IMS, informing the calling user that the called party is ringing;

705: The common IMS forwards the 18x message to the UE.

706: The IMS slice sends a 200 OK message to the common IMS to notify the calling user to be answered by the called party.

707: The common IMS sends a 200 OK message to the UE to notify the calling user to be answered by the called party.

The network elements and main functions involved in the system structure shown in Figure 3 above are shown in Table 1.

Table 1: Network elements and function descriptions involved in this embodiment

Second, the network system structure shown in Figure 4.

In Figure 4, the main responsibility of the common IMS is to process the IMS registration procedure and send the IMS slice and the type of service supported by the IMS slice to the UE in the response message registered by the IMS. The common IMS includes a registration management function of the P-CSCF and the S-CSCF in the IMS architecture, and adds the IMS slice and the service type supported by the IMS slice to the UE in the registration response. The type of service supported by the IMS slice can be carried in the form of a list.

The main responsibilities of session IMS: handling session, routing, PCC process QoS control and service triggering. It includes session management, media control, QoS control functions and S-CSCF session management functions of the P-CSCF in the IMS architecture.

Main responsibilities of the media: codec, playback, IPV4/V6 conversion, DTMF and other IMS media processing functions. Includes IMS-AGW in the current agreement.

In the system shown in FIG. 4 above, IMS slice 1 and IMS slice 2 share the registration service of common IMS, and the IMS slice includes only session management and service processing. The UE initiates a registration process to the common IMS. In the registration process, the UE obtains a mapping list of the IMS slice ID and the IMS slice IP address. When the UE initiates the session process, the corresponding IMS slice 1 and IMS slice 2 are used according to the service type.

The address of the IMS slice can be configured on the common IMS or configured/registered to the DNS/NRF. If configured/registered into the DNS/NRF, the common IMS can obtain the address of the different IMS slice in the DNS/NRF.

The UE obtains the commomn IMS address, and the manner in which the UE obtains the common IMS address may be the same as the manner in which the UE obtains the P-CSCF address. For example, after the 5 IMS/EPC obtains the common IMS address through configuration, the NAS message will be The address of the common IMS is sent to the UE.

Based on the network system structure shown in FIG. 4, in the registration process shown in FIG. 8, common IMS provides a general IMS registration service for two IMS slices, and the registration process of the system structure shown in FIG. 3 is different: The common IMS sends a service type and an IMS slice IP address correspondence list provided by the IMS slice to the UE in the 200 ok message, and the UE records the IMS slice address and the service type supported by the IMS slice. The detailed registration process is as follows:

801: The UE sends a registration message to the common IMS to request IMS registration.

In this step, the UE may first read the USIM card information to obtain the IMSI, and then derive the IMPI and the T-IMPU from the IMSI; send a register message to the address of the common IMS to request the IMS registration; the content of the register message and the IMS initiated by the UE. The register message of the registration process can be identical and does not require enhancement. The main parameters of the register message are as follows:

From/To header field: The IMPU of the registered user, filled in as T-IMPU here.

Contact header field: The contact address of the registered user.

Expires: Registration duration.

Authorization header field: Includes the IMPI of the registered user.

Security-Client header field: Instructs the UE to use the IPSec AKA authentication mode, where alg is the integrity protection algorithm, spi-c/spi-s is the SPI, and port-c/port-s is the secure port number of the UE.

802: The common IMS and the HSS interact to obtain the user's 5-tuple authentication vector.

The quintuple authentication vector may include: XRES, RAND, AUTN, IK, and CK.

The 803common IMS sends a 401 response to the UE.

The common IMS saves the parameter XRES for subsequent verification of the user's authentication response. Other authentication elements are sent to the UE with a 401 response. The 401 response message example "contains RAND and AUTN parameters.

804: After receiving the 401 response, the UE authenticates the AUTN according to the shared key stored in the local USIM, and the authentication indicates that the 401 message is originated from the real home network of the user; and the response RES, CK is calculated based on the shared key and RAND. And IK, reconstruct the register message, carry the AUTN, RAND, and RES, and send the message to the common IMS according to the path of the register message in step 801.

805: The common IMS receives the register message and compares the expected authentication response XRES with the actually received authentication response RES. If the two match, the network authenticates the UE. The common IMS to IMS HSS obtains user subscription data.

806: The common IMS obtains the address of the IMS slice.

The address of the IMS slice and the service type supported by the IMS slice are configured on the common IMS or configured/registered to the DNS/NRF. If configured/registered into the DNS/NRF, the common IMS needs to obtain different IMS slices from the DNS/NRF. address.

807: The common IMS returns a 200 OK response to the UE.

The IMPU list carrying the implicit registration set bound to the T-IMPU in the P-Associated-URI header field of the 200 OK response, including the mobile terminal number MSISDN (Tel URI) of the user and the SIP URI of the user, indicating that the user implicitly registers All the numbers in the set are registered successfully; wherein the P-Slice-URI header field carries a list of IMS slice addresses and the IMS slice support service type. After receiving the 200 OK, the UE records the P-Slice-URI header field information.

The format of the P-Slice-URI is:

As shown in FIG. 9, when the UE calls the service, the UE selects the corresponding IMS slice address to send an invite message according to the type of the service to be initiated. The detailed process is as follows:

901: When the calling UE initiates the session, the IMS slice address that supports the service type is selected and sent to the invite message according to the service type.

The invite message can carry the following information:

From: Caller number.

Request-URI: The called subscriber number.

Contact header field: The contact address of the calling user.

Feature-tag: Service type identifier.

SDP: The media capabilities of the calling UE, including the supported media types and the encoding and decoding capabilities of the corresponding media.

902: The IMS slice sends an 18x message to the UE, informing the calling user that the called party is ringing;

After the session IMS and the media plane in the IMS slice receive the invite message, according to the feature-tag in the invite message, the session type and the service trigger are performed, and the caller is sent to the 18x message to indicate that the called party has already been called. Ringing.

903: The IMS slice sends a 200ok message to the UE to notify the calling user of the called party's response.

The UE of the network system architecture shown in Figure 4 needs to obtain the address of the common IMS and the address of the session/service processing IMS slice supporting the specific service type.

The network element and function descriptions of the scheme of the network system architecture shown in FIG. 4 are shown in Table 2.

Table 2: Network elements and function descriptions related to the present invention

The invention also provides a communication device, which is used as a universal Internet Protocol Multimedia Subsystem IMS, as shown in FIG. 10, and includes:

The receiving unit 1001 is configured to receive a registration request from the user equipment UE.

The registration unit 1002 is configured to register with the UE after the receiving unit 1001 receives the registration request from the user equipment UE.

The receiving unit 1001 is further configured to: after the registration unit 1002 successfully registers the UE, receive the call request sent by the UE; and the selecting unit 1003 is configured to: after the receiving unit 1001 receives the call request sent by the UE, The UE selects a session IMS slice, and the sending unit is configured to forward the foregoing call request to the session IMS slice.

Alternatively, the sending unit 1004 is configured to send, after the UE is registered, the information of the session IMS slice to the UE, where the information of the session IMS slice is used by the UE to call the session IMS slice.

As a possible implementation, the selecting unit 1003 is configured to obtain a service type identifier from the call request, obtain the session IMS slice, and obtain an address of the session IMS slice, where the session IMS slice is specified by the service type identifier. IMS slice corresponding to the type of service;

The sending unit 1004 is configured to forward the call request to the session IMS slice according to the address of the session IMS slice.

As a possible implementation, the foregoing selecting unit 1003, configured to obtain the foregoing session IMS slice, is configured to: in the domain name server DNS or network storage function NRF, query an IMS slice corresponding to the service type specified by the service type identifier as Session IMS slice.

As a possible implementation manner, the information about the session IMS slice includes:

The address of the above session IMS slice, and the type of service supported by the session IMS slice.

As a possible implementation manner, the foregoing registration unit 1002 is configured to obtain a 5-tuple authentication vector from the home subscriber server HSS, and use the foregoing 5-tuple authentication vector to authenticate the UE, and determine after the UE is authenticated. The UE is registered and passed, and after the sending unit 1004 sends a response message indicating that the authentication is passed to the UE, it is determined that the UE registration is successful.

The embodiment of the present invention further provides a communication device, which is used as a user equipment UE, as shown in FIG.

The sending unit 1101 is configured to send a registration request to the universal internet protocol multimedia subsystem IMS.

The receiving unit 1102 is configured to receive, after the UE is registered, the information of the session IMS slice sent by the universal IMS.

The sending unit 1101 is further configured to send a call request to the session IMS according to the information of the session IMS slice.

As a possible implementation manner, the receiving unit 1102 includes:

The receiving subunit 11021 is configured to receive a response message indicating that the authentication is passed;

The parsing unit 11022 is configured to parse the response message to obtain the information of the session IMS slice.

As a possible implementation manner, the foregoing session IMS information includes:

FIG. 12 is a communication device 120 according to an embodiment of the present invention. The communication device 120 includes a processor 1201, a memory 1202, an input interface 1203, and an output interface 1204.

The memory 1202 includes, but is not limited to, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read only memory (EPROM), or A compact disc read-only memory (CD-ROM) is used for related instructions and data. The transceiver 1203 is configured to receive and transmit data.

The processor 1201 may be one or more central processing units (CPUs). In the case where the processor 1201 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.

The processor 1201 in the communication device 120 is configured to read the program code stored in the memory 1202, and execute the method flow of the sending device or the receiving device in the foregoing method embodiment.

A program code is stored in the above memory 1202, and a codebook is also stored.

In this embodiment, the processor 1201 may correspond to the parsing unit 11022 and the selecting unit 1003 in FIG. 10 or FIG. 11 described above; the transmitting and receiving functions in FIGS. 10 and 11 may correspond to the input interface 1203 and the output interface 1204, respectively.

In the case where the communication device 120 appears as a chip or integrated circuit, the input interface 1203 and the output interface 1204 may be communication interfaces between chips of the communication device.

The communication device shown in FIG. 12 in the present application may be a communication device or a chip or an integrated circuit mounted in the communication device.

A communication device is taken as an example of a communication device. Figure 13 is a block diagram showing the structure of a simplified communication device. The communication device includes a signal transceiving portion 1301, a data processing portion 1302, a memory 1303, and possibly an input/output device 1304; the signal transceiving portion may include an input interface 13011 portion and/or an output interface 13021 portion (also collectively referred to as a transceiving unit). The signal transceiving portion is mainly used for signal transmission and reception and conversion with a baseband signal; the data processing portion 1302 is mainly used for baseband processing, control of a communication device, and the like. The input interface 13011 may also be referred to as a receiver, a receiver, a receiving circuit, etc., and the output interface 13021 may also be referred to as a transmitter, a transmitter, a transmitter, a transmitting circuit, or the like.

The data processing portion 1302 is generally a control center of the communication device, and may be generally referred to as a processing unit for controlling the steps performed by the communication device in the method flow for the communication device. For details, refer to the description of the relevant portions above. The data processing portion 1302 can include one or more boards, each of which can include one or more processors and one or more memories for reading and executing programs in the memory to implement baseband processing functions and Control of the communication device. If multiple boards exist, the boards can be interconnected to increase processing power. As a possible implementation, multiple boards may share one or more processors, or multiple boards share one or more memories, or multiple boards may share one or more processors at the same time. .

For example, in one embodiment, input interface 13021 is for performing a receive registration request, and data processing portion 1302 is for performing a selection of session IMS.

The embodiment of the present invention further provides a communication system, as shown in FIG. 3 or 4, comprising: a universal Internet Protocol Multimedia Subsystem IMS, and two or more session IMS slices;

The session IMS slice is configured to receive a call request forwarded by the universal IMS, perform session processing, or receive a call request sent by the UE, and perform session processing. The former corresponds to the network system shown in FIG. 3, and the latter corresponds to the network system shown in FIG. 4;

The fifth embodiment of the present invention further provides a communication device, including: an input device, an output device, a processor, and a storage device; a program code is stored in the storage device, and the processor is configured to invoke the program code to control the foregoing The input device and the above input device and the processor cooperate to perform the method of any of the embodiments of the present invention.

The embodiment of the present invention further provides a computer storage medium, where the computer storage medium stores a computer program, where the computer program includes program instructions, and when the program instructions are executed by the processor, execute any one of the embodiments provided by the embodiments of the present invention. The method of the item.

The embodiment of the present invention further provides a computer program product, where the computer program product includes a program instruction, and when the program code is executed by the processor, the processor cooperates with the receiving device or the transmitting device to perform the embodiment provided by the embodiment of the present invention. Any of the methods.

Those of ordinary skill in the art will appreciate that the elements and method steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.

A person skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the communication device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided herein, it should be understood that the disclosed systems, methods, and apparatus may be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the above units is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or may be Integrate into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

The units described above as separate components may or may not be physically separated. The components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it may be implemented in whole or in part in the form of a computer program product. The above computer program product includes one or more computer instructions. When the above computer program instructions are loaded and executed on a computer, the above described processes or functions in accordance with embodiments of the present invention are generated in whole or in part. The above computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions described above may be stored in a computer readable storage medium or transmitted by the computer readable storage medium described above. The above computer instructions may be routed from a website site, computer, server or data center to another via wire (eg coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg infrared, wireless, microwave, etc.) A website site, computer, server, or data center for transmission. The computer readable storage medium described above can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media. The above usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a digital versatile disc (DVD)), or a semiconductor medium (for example, a solid state disk (SSD)). Wait.

One of ordinary skill in the art can understand all or part of the process of implementing the above embodiments, which can be completed by a computer program to instruct related hardware, the program can be stored in a computer readable storage medium, when the program is executed The flow of the method embodiments as described above may be included. The foregoing storage medium includes: a read-only memory (ROM) or a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program code.

Claims

A communication method, comprising:

The universal internet protocol multimedia subsystem IMS receives a registration request from the user equipment UE, and registers with the UE;

Receiving a call request sent by the UE after the UE is successfully registered, selecting a session IMS slice for the UE, and forwarding the call request to the session IMS slice;

Or transmitting, after the UE is registered, the information of the session IMS slice to the UE, where the information of the session IMS slice is used by the UE to call the session IMS slice.
The method according to claim 1, wherein the selecting a session IMS slice for the UE, and forwarding the call request to the session IMS slice comprises:

Obtaining a service type identifier from the call request, obtaining the session IMS slice, and obtaining an address of the session IMS slice; the session IMS slice is an IMS slice corresponding to the service type specified by the service type identifier;

And forwarding the call request to the session IMS slice according to the address of the session IMS slice.
The method of claim 2 wherein said obtaining said session IMS slice comprises:

In the domain name server DNS or network storage function NRF, the IMS slice corresponding to the service type specified by the service type identifier is queried as a session IMS slice.
The method of claim 1, wherein the information of the session IMS slice comprises:

The address of the session IMS slice and the type of service supported by the session IMS slice.
The method according to any one of claims 1 to 4, wherein the registering for the UE comprises:

Obtaining a five-tuple authentication vector from the home subscriber server HSS, authenticating the UE by using the five-tuple authentication vector, and determining that the UE is registered to pass after the UE is authenticated, in the UE After the response message indicating that the authentication is passed, the UE is successfully registered.
A communication method, comprising:

The user equipment UE sends a registration request to the universal internet protocol multimedia subsystem IMS;

Receiving, after the UE is registered, the information of the session IMS slice sent by the universal IMS;

Sending a call request to the session IMS according to the information of the session IMS slice.
The method according to claim 6, wherein the receiving the information of the session IMS slice sent by the universal IMS comprises:

Receiving a response message indicating that the authentication is passed, parsing the response new message to obtain information of the session IMS slice.
The method according to claim 6 or 7, wherein the information of the session IMS slice comprises:

The address of the session IMS slice and the type of service supported by the session IMS slice.
A communication device characterized by being used as a universal Internet Protocol Multimedia Subsystem IMS, comprising:

a receiving unit, configured to receive a registration request from the user equipment UE;

a registration unit, configured to register, after the receiving unit receives a registration request from the user equipment UE,

The receiving unit is further configured to: after the registration unit successfully registers the UE, receive a call request sent by the UE; and the selecting unit is configured to: after the receiving unit receives the call request sent by the UE, Selecting a session IMS slice for the UE, and sending, by the sending unit, the call request to the session IMS slice;

Or the sending unit, configured to send information of the session IMS slice to the UE after the UE registers, the information of the session IMS slice is used by the UE to call the session IMS slice.
A communication device according to claim 9, wherein:

The selecting unit is configured to obtain a service type identifier from the call request, obtain the session IMS slice, and obtain an address of the session IMS slice; the session IMS slice is a service specified by the service type identifier Type corresponding IMS slice;

The sending unit is configured to forward the call request to the session IMS slice according to an address of the session IMS slice.
The communication device according to claim 10, characterized in that

The selecting unit, configured to obtain the session IMS slice, is configured to: in the domain name server DNS or network storage function NRF, query an IMS slice corresponding to the service type specified by the service type identifier as a session IMS slice.
The communication device according to claim 9, wherein the information of the session IMS slice comprises:

The address of the session IMS slice and the type of service supported by the session IMS slice.
A communication device according to any one of claims 9 to 12, characterized in that

The registration unit is configured to obtain a 5-tuple authentication vector from the home subscriber server HSS, perform authentication on the UE by using the 5-tuple authentication vector, and determine the UE registration after the UE authentication passes And determining, by the sending unit, that the UE is successfully registered after sending a response message indicating that the authentication is passed to the UE.
A communication device is used as the user equipment UE, and is characterized in that it comprises:

a sending unit, configured to send a registration request to the universal internet protocol multimedia subsystem IMS;

a receiving unit, configured to receive, after the UE is registered, the information of the session IMS slice sent by the universal IMS;

The sending unit is further configured to send a call request to the session IMS according to the information of the session IMS slice.
The communication device according to claim 14, wherein said receiving unit comprises:

The receiving subunit is configured to receive a response message indicating that the authentication is passed;

And a parsing unit, configured to parse the response message to obtain information of the session IMS slice.
The communication device according to claim 14 or 15, wherein the information of the session IMS slice comprises:

The address of the session IMS slice and the type of service supported by the session IMS slice.
A communication system, comprising: a universal internet protocol multimedia subsystem IMS, and two or more session IMS slices;

The universal IMS for performing the method of any one of claims 1-5;

The session IMS slice is configured to receive a call request forwarded by the universal IMS, perform session processing, or receive a call request sent by the UE, and perform session processing.
The communication system according to claim 17, wherein said communication system further comprises: a packet switched PS core network; and said PS core if said universal IMS forwards a call request of said UE to said session IMS slice The network is in communication with the universal IMS, the universal IMS is in communication with the media plane of the session IMS slice; if the universal IMS sends session IMS slice information to the UE, the PS core network and the The universal IMS and the media side of the session IMS slice are respectively communicatively coupled.
A communication device includes: an input device, an output device, a processor, and a storage device;

Program code is stored in the storage device, the processor is configured to invoke the program code to control the input device and the input device, and the processor cooperate to perform the method of any one of claims 1 to 8. method.
A computer storage medium, characterized in that the computer storage medium stores a computer program, the computer program comprising program instructions, when executed by a processor, performing any one of claims 1 to 8. Said method.