CN110324291B

CN110324291B - Communication method and related product

Info

Publication number: CN110324291B
Application number: CN201810286666.6A
Authority: CN
Inventors: 张彪; 舒续祖
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2018-03-30
Filing date: 2018-03-30
Publication date: 2022-04-22
Anticipated expiration: 2038-03-30
Also published as: WO2019184717A1; CN110324291A

Abstract

The embodiment of the invention provides a communication method and a related product, wherein the method comprises the following steps: after receiving a registration request of User Equipment (UE), the general IMS registers for the UE; after the UE is successfully registered, a call request sent by the UE is received, a session IMS slice is selected for the UE, and the call request is forwarded to the session IMS slice; or after the UE is registered, sending session IMS slice information to the UE, wherein the session IMS slice information is used for the UE to call the session IMS slice. The general IMS is responsible for the function of registering for the UE, and the UE does not need to be connected with a plurality of IMS slices in an abutting mode, so that the requirement on the UE is low; the UE does not need to search a plurality of IMS slices, and the call request is forwarded by the general IMS or sent according to the IMS slices provided by the general IMS; therefore, the network deployment complexity is lower.

Description

Communication method and related product

Technical Field

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

Background

Operators have plans to provide an industrial communication solution, and require a User Equipment (UE) to simultaneously access to multiple internet protocol multimedia subsystems (IMS), each IMS provides different real-time service types, for example, IMS1 provides a mission-critical push-to-talk (MCPTT) service, and IMS2 provides a general voice service.

The UE accesses to IMS1 and IMS2 at the same time, and may initiate IMS registration by the UE respectively accessing to IMS slice 1(slice1) and IMS slice2, and when the UE initiates voice over long term evolution (VoLTE) based public network voice service, selects IMS slice1, and when the UE initiates MCPTT service, selects IMS slice 2.

The above scheme has high requirements for the UE, and the network deployment is complex.

Disclosure of 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.

In one aspect, an embodiment of the present invention provides a communication method, including:

a common (common) IMS receives a registration request from a User Equipment (UE) and registers for the UE;

after the UE is successfully registered, a call request sent by the UE is received, a session (session) IMS slice is selected for the UE, and the call request is forwarded to the session IMS slice;

or after the UE is registered, sending session IMS slice information to the UE, wherein the session IMS slice information is used for the UE to call the session IMS slice.

The address of the general IMS may be obtained by a Packet Switching (PS) core network through configuration, and then sent to the UE using a Non Access Stratum (NAS) message, and then the UE sends a registration request to the general IMS according to the address of the general IMS.

The successful registration means that after the registration is completed completely, the registration is passed, that is, the authentication is passed in the authentication process, and the registration is not necessarily completed completely. The session IMS slice is a slice for providing a service for the UE, the information of the IMS slice may include information of 1 IMS slice or information of more IMS slices, and if the information of two or more IMS slices is included, the UE may select an IMS slice from the information of 1 IMS slice or more IMS slices as the session IMS slice.

In the embodiment, the general IMS is an IMS shared by a plurality of IMS slices, and is responsible for a function of registering for the UE, so that the UE does not need to interface to the plurality of IMS slices, and thus the requirement on the UE is low; in the process of initiating a call by the UE, the UE does not need to search a plurality of IMS slices, and the general IMS forwards a call request or sends the call request according to the IMS slices provided by the general IMS; therefore, the network deployment complexity is lower.

As a possible implementation, the following specific ideas of the procedures of selecting the session IMS slice and forwarding the call request are also provided: 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 one possible implementation, a process for obtaining a session IMS slice is also provided as follows: the obtaining the session IMS slice comprises:

and querying an IMS slice corresponding to the service type specified by the service type identifier in a Domain Name Server (DNS) or a network storage function (NRF) as a session IMS slice.

It should be noted that the correspondence between the service type and the IMS slice, if stored in the general IMS, may not be queried from the DNS or the NRF.

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

an address of the session IMS slice, and a type of service supported by the session IMS slice.

The purpose of the session IMS slice information is to let the UE know how to call to the session IMS slice, and thus may contain all necessary various information, which by way of example should not be understood as exhaustive of the session IMS slice information.

As a possible implementation, there is also provided a registration optional implementation as follows: the registering for the UE comprises:

obtaining a quintuple authentication vector from a Home Subscriber Server (HSS), authenticating the UE by using the quintuple authentication vector, determining that the UE is registered successfully after the UE passes the authentication, and determining that the UE is registered successfully after a response message indicating that the authentication passes is sent to the UE.

The quintuple authentication vector may include: expected response (XRES), random challenge (RAND), authentication token (AUTN), Integrity Key (IK), and encryption key (CK); the embodiment of the present invention is not limited to uniqueness, particularly, the authentication process using the quintuple authentication vector.

In another aspect, an embodiment of the present invention further provides a communication method, including:

user Equipment (UE) sends a registration request to a universal internet protocol multimedia subsystem (IMS);

after the UE passes the registration, receiving the information of the session IMS slice sent by the general IMS;

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

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

and receiving a response message indicating that the authentication is passed, and analyzing the response new message to obtain the information of the session IMS slice.

The response message for the knowledge authentication to pass may be a 200OK message in general.

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

The implementation of the invention in three aspects also provides a communication device used as a universal internet protocol multimedia subsystem IMS, comprising:

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

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

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

or, a sending unit, configured to send, to the UE, session IMS slice information after the UE registration is passed, where the session IMS slice information is used for the UE to call the session IMS slice.

As a possible implementation manner, 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 an IMS slice corresponding to the service type specified by the service type identifier;

and the sending unit is used for forwarding the call request to the session IMS slice according to the address of the session IMS slice.

As a possible implementation manner, the selecting unit, configured to obtain the session IMS slice, includes: the method is used for inquiring the IMS slice corresponding to the service type specified by the service type identification in a Domain Name Server (DNS) or a network storage function (NRF) as a session IMS slice.

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

As a possible implementation manner, the registration unit is configured to obtain a quintuple authentication vector from a home subscriber server HSS, authenticate the UE using the quintuple authentication vector, determine that the UE is registered successfully after the UE passes the authentication, and determine that the UE is registered successfully after a response message indicating that the authentication passes is sent to the UE through the sending unit.

In a fourth aspect, an embodiment of the present invention further provides a communications apparatus, used as a UE, including:

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

a receiving unit, configured to receive, after the UE passes registration, session IMS slice information sent by the generic 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, the receiving unit includes:

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

and the analysis unit is used for analyzing the response new message to obtain the information of the session IMS slice.

As a possible implementation, the session IMS information includes:

The embodiment of the present invention also provides a communication device, including: an input device, an output device, a processor, and a storage device; the storage device stores program codes, and the processor is used for calling the program codes to control the input device and the processor to cooperate to execute any method provided by the embodiment of the invention.

The sixth aspect of the present invention also provides a computer storage medium, in which a computer program is stored, where the computer program includes program instructions, and when the program instructions are executed by a processor, the computer program instructions execute any one of the methods provided by the embodiments of the present invention.

Seventh aspect embodiments of the present invention also provide a computer program product, where the computer program product includes program instructions, and the program code, when executed by a processor, causes the processor to cooperate with a receiving device or a transmitting apparatus to perform any one of the methods provided by the embodiments of the present invention.

The eighth aspect of the present invention further provides a communication system, including: a general internet protocol multimedia subsystem IMS, and two or more session IMS slices;

the general IMS is configured to perform any one of the method steps performed by the general IMS according to the embodiments of the present invention;

the session IMS slice is used for receiving the call request forwarded by the general IMS and executing session processing; or, the UE is configured to receive a call request sent by the UE, and perform session processing.

As a possible implementation, the communication system further includes: a packet switched PS core network; if the general IMS forwards the call request of the UE to the session IMS slice, the PS core network is in communication connection with the general IMS, and the general IMS is in communication connection with the media plane of the session IMS slice; and if the general IMS sends the information of the session IMS slice to the UE, the PS core network is respectively in communication connection with the general IMS and the media surface of the session IMS slice.

Drawings

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

FIG. 1 is a system architecture diagram according to an embodiment of the present invention;

FIG. 2 is a system architecture diagram according to an embodiment of the present invention;

FIG. 3 is a system architecture diagram according to an embodiment of the present invention;

FIG. 4 is a system architecture diagram according to an embodiment of the present invention;

FIG. 5 is a schematic flow chart of a method of an embodiment of the present invention;

FIG. 6 is a flowchart illustrating a registration method according to an embodiment of the present invention;

FIG. 7 is a flow chart of a calling method according to an embodiment of the present invention;

FIG. 8 is a flowchart illustrating a registration method according to an embodiment of the present invention;

FIG. 9 is a flow chart of a calling method according to an embodiment of the present invention;

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

FIG. 11 is a block diagram of a communication device according to an embodiment of the present invention;

FIG. 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 device according to an embodiment of the present invention.

Detailed Description

The embodiments of the present invention will be described below with reference to the drawings.

As shown in fig. 1, an example of a system of a 5G communication system includes in fig. 1: UE, Radio Access Network (RAN) or Access Network (AN), user interface function (UPF) device, Data Network (DN), Authentication Management Field (AMF), Service Management Function (SMF) device, Policy Control Function (PCF) device, Application Function (AF) device, authentication server function (AUSF) device, normalized data management (UDM) device; the communication is performed using N1 to N15 interfaces.

Fig. 2 is a simplified diagram of a network system structure diagram according to an embodiment of the present invention, and relates to network elements mainly related to the embodiment of the present invention, wherein a multimedia telephony (MMTEL) Access Stratum (AS) and an MCPTT AS belong to two slices, i.e., an IMS1 and an IMS 2. Wherein the IMS1 and the IMS2 further include a serving call session control function (S-CSCF) device, a proxy call session control function (P-CSCF) device, and an interrogating call session control function (I-CSCF) device, respectively. Among them, a 5G core network (5G core network, 5 GC)/evolved packet core network (EPC) is a common part of IMS1 and IMS 2. In the above fig. 2, the UE has access to IMS1 and IMS2 simultaneously, and may initiate IMS registration by the UE to IMS slice1 and IMS slice2, respectively, and when the UE initiates a VoLTE-based public network voice service, it selects IMS slice1, and when the UE initiates an MCPTT service, it selects IMS slice 2. The IMS slice is an IMS slice divided by service information (e.g., a service type and a service identifier), a subscriber number segment, or a terminal type, and the IMS slice Identifier (ID) is used to identify different IMS slices, that is, different IMS networks. The use of the I-CSCF in the system of figure 2 includes: allocating S-CSCF to UE initiating register request; in the process of session-related and session-unrelated, a Session Initiation Protocol (SIP) request from another network is routed to the S-CSCF; inquiring HSS, and obtaining the address of S-CSCF providing service for a certain UE from HSS; and forwarding the SIP request or response to the S-CSCF according to the S-CSCF address acquired from the HSS.

As shown in fig. 3 and 4, schematic diagrams of two other network system structure diagrams provided by the embodiment of the present invention are provided, in which a common IMS is added to the network system architecture; IMS slice1 and IMS slice2 contain session IMS1 and session IMS2 and their corresponding media planes; 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: UE sends a registration request to a general IMS;

502: after receiving a registration request from User Equipment (UE), the general IMS registers for the UE;

503A: after the UE is successfully registered, the UE sends a call request to the general IMS;

the call request should typically contain information such as a service type identifier for specifying the service type.

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

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

Or after 502, performing:

503B: after the UE is registered, sending session IMS slice information to the UE, wherein the session IMS slice information is used for calling the session IMS slice by the UE;

the information of the session IMS slice may be carried to the UE in a response message, such as a 200OK message, of successful registration.

The session IMS slice information may generally include information such as an address, a 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 general IMS is an IMS shared by multiple IMS slices, and is responsible for a function of registering for the UE, so the UE does not have to interface to multiple IMS slices, and thus the requirement on the UE is low; in the process of initiating a call by the UE, the UE does not need to search a plurality of IMS slices, and the general IMS forwards a call request or sends the call request according to the IMS slices provided by the general IMS; therefore, the network deployment complexity is lower.

The following embodiments will be exemplified with respect to the network system structures shown in fig. 3 and 4 above, respectively.

First, a network system structure shown in fig. 3.

The common IMS in fig. 3 masks the IMS slice for Packet Switching (PS) core network (5GC/EPC) and UEs, which only see the common IMS.

Among them, common IMS has main responsibilities: IMS slice1 or IMS slice2 is selected in handling IMS registration and session flow. Neither the UE nor the PS core network need to enhance the IMS slice. Including registration management functions of the P-CSCF and S-CSCF in the IMS architecture.

session IMS main responsibilities: handling session, routing, Policy and Charging Control (PCC) flow quality of service (QoS) control and traffic triggering. The session IMS may include session management, media control, Qos control functions and S-CSCF session management functions for the P-CSCF in the IMS architecture.

The main responsibilities of the media plane: codec, playback, internet protocol version 4 (IPV 4)/IPV6 conversion, and IMS media processing functions such as DTMF. The devices of the media plane may include an existing in-protocol IMS-Access Gateway (AGW).

In the system shown in fig. 3 above, the manner in which the UE acquires the common IMS address may be similar to the manner in which the UE acquires the P-CSCF address, for example: after the common IMS address is acquired by the 5GC/EPC through configuration and other modes, the common IMS address is sent to the UE in the NAS message.

And the common IMS selects the session IMS in the corresponding IMS slice according to the configuration strategy of the DNS or according to the internal configuration in the common IMS.

The session IMS and the media plane may be linked by h.248 or other protocols.

A Session Initiation Protocol (SIP) protocol may be used between the common IMS and the session IMS.

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

601: the UE sends a register message to the common IMS requesting IMS registration.

In this step, specifically, the UE first reads a Universal Subscriber Identity Module (USIM) card information to obtain an International Mobile Subscriber Identity (IMSI), and then derives an IMS private user identity (IMPI) and an IMS temporary multimedia public identity (T-IMPU) from the IMSI; sending a register message to the address of the common IMS to request IMS registration; the content of the register message and the register message of the IMS registration procedure initiated by the UE may be identical without enhancement. The main parameters of the register message are as follows:

From/To header domain: the internet protocol multimedia public Identity (IMPU) of the registered user is here filled out as T-IMPU.

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

Expires: the registration duration.

Authorization header domain: including the IMPI of the registered user.

Security-Client header field: and indicating the UE to use an Internet protocol security (IPSec) Authentication and Key Agreement (AKA) authentication mode, wherein alg is an integrity protection algorithm, SPI-c/SPI-s is a Security Parameter Index (SPI), and port-c/port-s is a security port number of the UE.

Require/Proxy-Require head domain: indicating that the UE requires to use IPSec AKA authentication mode.

602: and the common IMS and the HSS interactively acquire the quintuple authentication vector of the user.

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

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

The common IMS stores the parameter XRES for subsequent verification of the authentication response of the user. Other authentication elements are sent to the UE with the 401 response. The above 401 response message example: including RAND and AUTN.

604: after receiving the 401 response, the UE authenticates the AUTN according to the shared key stored in the local USIM, and if the authentication is passed, the 401 message is from the true home network of the user; and then, calculating Response (RES), CK and IK based on the shared secret key and the RAND, reconstructing a register message carrying AUTN, RAND and RES, and sending the message to the common IMS according to the path of the register message in the step 601.

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

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

The IMPU list of the implicit registration set bound with the T-IMPU is carried in the P-Associated-URI header field of the 200OK response, wherein the IMPU list comprises the Mobile terminal number (MSISDN) of the user, the Uniform Resource Identifier (URI) of the telephone (Tel) and the SIP URI of the user, and the registration of all numbers in the implicit registration set of the user is successful.

The above 401 and 200OK responses can refer to the third Generation Partnership Project (3 GPP) protocol, which is not described herein in detail.

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 invite (invite) message, and the detailed flow is as follows:

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

In the invite message, the following key information may be carried:

from: a calling subscriber number;

Request-URI: the number of the called party;

contact header field: the contact address of the calling subscriber;

feature-tag: a service type identifier;

session Description Protocol (SDP): the media capabilities of the calling UE, including supported media types and codec capabilities of the corresponding media.

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

The specific process of selecting IMS slices may be: and selecting the corresponding IMS slice according to the service type identification carried by the feature-tag in the invite message, the calling user number in the From header field and the characteristic data signed by the user in the HSS. The address of the IMS slice is configured/registered in a DNS/Network storage Function (NRF) or in a common IMS, and if the address is configured/registered in the DNS/NRF, the DNS/NRF needs to enhance and support the corresponding relationship between the configured IMS slice address and the supported service type.

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

704: the IMS slice sends 18x information to the common IMS and informs the calling user of called ringing;

705: common IMS forwards 18x messages to the UE;

706: the IMS slice sends a 200OK message to the common IMS and informs the calling user of the called response;

707: the common IMS sends a 200OK message to the UE to notify the calling party of the called response.

The network elements and the main functions related to the system structure shown in fig. 3 are described in table 1.

Table 1: network element and function description related to the embodiment

Second, a network system structure shown in fig. 4.

In fig. 4, the common IMS's main responsibilities: and processing an IMS registration flow and sending the IMS slice and the service type supported by the IMS slice to the UE in a response message of IMS registration. The common IMS comprises the registration management functions of a P-CSCF and an S-CSCF in an IMS architecture, and the IMS slice and the service types supported by the IMS slice are added to be sent to the UE in a registration response. The service types supported by the IMS slice may be carried in the form of a list.

session IMS main responsibilities: and processing conversation, routing, PCC flow QoS control and service triggering. Including session management, media control, Qos control functions and S-CSCF session management functions for P-CSCFs in the present IMS architecture.

The main responsibilities of the media plane: coding and decoding, playing, IPV4/V6 conversion, DTMF and other IMS media processing functions. Including the IMS-AGW in the present protocol.

In the system shown in fig. 4 above, IMS slice1 and IMS slice2 share the registration service of common IMS, and the IMS slice includes only session management and traffic processing. And the UE initiates a registration process to the common IMS, and in the registration process, the UE acquires an IMS slice ID and an IMS slice IP address corresponding relation list. And when the UE initiates a session process, using the corresponding IMS slice1 and IMS slice2 according to the service type.

The address of the IMS slice may be configured on the common IMS or configured/registered in the DNS/NRF, and if configured/registered in the DNS/NRF, the common IMS may acquire the address of a different IMS slice in the DNS/NRF.

The scheme for the UE to acquire the common IMS address may be similar to the scheme for the UE to acquire the P-CSCF address, for example: after the common IMS address is acquired by the 5GC/EPC through configuration and other modes, the common IMS address is sent to the UE in the NAS message.

Based on the network system structure shown in fig. 4, in the registration flow shown in fig. 8, a common IMS provides a common IMS registration service for 2 IMS slices, and the registration flow is different from the system structure shown in fig. 3 in that: in this embodiment, the common IMS sends a list of correspondence between the service type provided by the IMS slice and the IP address of the IMS slice to the UE in a 200ok message, and the UE records the IMS slice address and the service type supported by the IMS slice, where the detailed registration procedure is as follows:

801: the UE sends a register message to the common IMS requesting IMS registration.

In this step, UE may specifically read USIM card information to obtain IMSI, and derive IMPI and T-IMPU from IMSI; sending a register message to the address of the common IMS to request IMS registration; the content of the register message and the register message of the IMS registration procedure initiated by the UE may be identical without enhancement. The main parameters of the register message are as follows:

From/To header domain: the IMPU of the user is registered, here filled out as a T-IMPU.

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

Expires: the registration duration.

Authorization header domain: including the IMPI of the registered user.

Security-Client header field: and indicating the UE to use an IPSec AKA authentication mode, wherein alg is an integrity protection algorithm, SPI-c/SPI-s is SPI, and port-c/port-s is a security port number of the UE.

802: and the common IMS and the HSS interactively acquire the quintuple authentication vector of the user.

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

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

The common IMS stores the parameter XRES for subsequent verification of the authentication response of the user. Other authentication elements are sent to the UE with the 401 response. The 401 response message example "contains the 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 if the authentication is passed, the 401 message is from the true home network of the user; and then calculating response RES, CK and IK based on the shared secret key and RAND, reconstructing a register message carrying AUTN, RAND and RES, and sending the message to the common IMS according to the path of the register message in the step 801.

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

806: 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 a common IMS or configured/registered to a DNS/NRF, and if the address of the IMS slice and the service type supported by the IMS slice are configured/registered to the DNS/NRF, the common IMS needs to acquire the address of a different IMS slice from the DNS/NRF.

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

An IMPU list of an implicit registration set bound with T-IMPU is carried in a P-Associated-URI head field of the 200OK response, and comprises a mobile terminal number MSISDN (Tel URI) of the user and a SIP URI of the user, which indicates that all numbers in the implicit registration set of the user are successfully registered; wherein the P-Slice-URI header field carries the IMS Slice address and the list of the IMS Slice supporting service type. And after receiving the 200OK, the UE records the header field information of the P-Slice-URI.

The format of the P-Slice-URI is as follows:

P-Slice-URI [ number ]: // List

{

The IP address of the IMScertificate IP address// IMS slice;

feature-tag// service type identification supported by the IMScertificate

}

As shown in fig. 9, when a UE calls a service, it selects a corresponding IMS slice address according to an initiated service type to send an invite message, and the detailed flow is as follows:

901: when the calling UE initiates a session, an IMS slice address supporting the service type is selected according to the service type and is sent to the invite message.

The invite message may carry the following information:

from: the calling subscriber number.

Request-URI: the number of the called subscriber.

Contact header field: the contact address of the calling subscriber.

Feature-tag: and identifying the service type.

SDP: the media capabilities of the calling UE, including supported media types and codec capabilities of the corresponding media.

902: IMS slice sends 18x message to UE, notify the caller called ring;

after the session IMS and the media surface in the IMS slice receive the invite message, the service type is judged to be supported according to the feature-tag in the invite message, corresponding session processing and service triggering are carried out, and the calling party is sent to the 18x message to indicate that the called party rings.

903: the IMS slice sends 200ok information to the UE to the terminal, and informs the calling party of the called response.

The solution UE of the network system architecture shown in fig. 4 needs to acquire the address of the common IMS and the address of the session/service handling IMS slice supporting a specific service type.

The network elements and functions involved in the scheme of the network system architecture shown in fig. 4 are described in table 2.

Table 2: network element and function description to which the invention relates

The present invention also provides a communication apparatus, for use as a universal internet protocol multimedia subsystem IMS, as shown in fig. 10, including:

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

a registering unit 1002, configured to register for a user equipment UE after the receiving unit 1001 receives a registration request from the UE;

the receiving unit 1001 is further configured to receive a call request sent by the UE after the registering unit 1002 successfully registers for the UE; a selecting unit 1003, configured to select a session IMS slice for the UE after the receiving unit 1001 receives the call request sent by the UE; a sending unit, configured to forward the call request to the session IMS slice;

alternatively, the sending unit 1004 is configured to send, to the UE, session IMS slice information used for the UE to call the session IMS slice after the UE registration is passed.

As a possible implementation manner, 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; the session IMS slice is an IMS slice corresponding to the service type specified by the service type identifier;

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 manner, the selecting unit 1003, configured to obtain the session IMS slice, includes: the method is used for inquiring the IMS slice corresponding to the service type specified by the service type identification as the session IMS slice in a Domain Name Server (DNS) or a network storage function (NRF).

an address of the session IMS slice, and a service type supported by the session IMS slice.

As a possible implementation manner, the registering unit 1002 is configured to obtain a five-tuple authentication vector from a home subscriber server HSS, authenticate the UE using the five-tuple authentication vector, determine that the UE is registered successfully after the UE passes the authentication, and determine that the UE is registered successfully after a response message indicating that the UE passes the authentication is sent to the UE through the sending unit 1004.

An embodiment of the present invention further provides a communication apparatus, used as a UE, as shown in fig. 11, including:

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

a receiving unit 1102, configured to receive, after the UE registration is passed, session IMS slice information sent by the general 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 passes;

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

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

Fig. 12 shows a communication device 120 according to an embodiment of the present invention, where 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 portable read-only memory (CD-ROM), and the memory 1202 is used for related instructions and data. The transceiver 1203 is used for receiving and transmitting data.

The processor 1201 may be one or more Central Processing Units (CPUs), and in the case that the processor 1201 is one CPU, the CPU may be a single-core CPU or a multi-core CPU.

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

The memory 1202 stores a program code and a codebook.

In this embodiment, the processor 1201 may correspond to the aforementioned analyzing unit 11022 and the selecting unit 1003 in fig. 10 or fig. 11; the transmitting and receiving functions in fig. 10 and 11 may correspond to the input interface 1203 and the output interface 1204, respectively.

In the case where the communication device 120 is in the form of a chip or an 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 may be a chip or an integrated circuit mounted in the communication device.

Take the communication device as an example. Fig. 13 shows a simplified schematic of a communication device. The communication device comprises a signal transceiving part 1301, a data processing part 1302, a memory 1303 and possibly an input/output device 1304; the signal transceiving part may include an input interface 13021 part and/or an output interface 13011 part (which may also be collectively referred to as a transceiving unit). The signal transceiving part is mainly used for transceiving signals and converting the signals with baseband signals; the data processing section 1302 is mainly used for baseband processing, control of a communication apparatus, and the like. The input interface 13021 may also be referred to as a receiver, a receiving circuit, etc., and the output interface 13011 may also be referred to as a transmitter, a transmitting circuit, etc.

The data processing portion 1302 is generally a control center of the communication device, and may be generally referred to as a processing unit, and is used for controlling the communication device to execute steps executed by the communication device in the method flow, which may be specifically referred to as the description in the above related portion. The data processing portion 1302 may include one or more boards, each of which may include one or more processors and one or more memories, the processors being configured to read and execute programs in the memories to implement baseband processing functions and control of the communication apparatus. If a plurality of single boards exist, the single boards can be interconnected to increase the processing capacity. As a possible implementation, multiple boards may share one or more processors, multiple boards may 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 used to perform receiving a registration request, and data processing portion 1302 is used to perform selection of a session IMS.

An embodiment of the present invention further provides a communication system, as shown in fig. 3 or 4, including: a general internet protocol multimedia subsystem IMS, and two or more session IMS slices;

the session IMS slice is used for receiving the call request forwarded by the general IMS and executing session processing; or, the UE is configured to receive a call request sent by the UE, and perform session processing. Wherein the former corresponds to the network system shown in fig. 3 and the latter corresponds to the network system shown in fig. 4;

The embodiment of the present invention also provides a communication device, including: an input device, an output device, a processor, and a storage device; the storage device stores program codes, and the processor is used for calling the program codes to control the input device, the input device and the processor to cooperate to execute any method provided by the embodiment of the invention.

The sixth aspect of the present invention also provides a computer storage medium, where a computer program is stored, where the computer program includes program instructions, and the program instructions, when executed by a processor, perform any one of the methods provided by the embodiments of the present invention.

Embodiments of the present invention further provide a computer program product, where the computer program product includes program instructions, and the program code, when executed by a processor, causes the processor to cooperate with a receiving device or a transmitting apparatus to execute any one of the methods provided by the embodiments of the present invention.

Those of ordinary skill in the art will appreciate that the various illustrative elements and method steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the communication apparatus and the unit described above may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, method and apparatus may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the above-described division of units is only one type of division of logical functions, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

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

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The procedures or functions described above in accordance with the embodiments of the invention may be generated, in whole or in part, when the computer program instructions described above are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on or transmitted over a computer-readable storage medium. The computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that includes one or more of the available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a Digital Versatile Disk (DVD)), a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.

One of ordinary skill in the art will appreciate that all or part of the processes in the methods of the above embodiments may be implemented by hardware related to instructions of a computer program, which may be stored in a computer-readable storage medium, and when executed, may include the processes of the above method embodiments. And the aforementioned storage medium includes: various media that can store program codes, such as a read-only memory (ROM) or a Random Access Memory (RAM), a magnetic disk, or an optical disk.

Claims

1. A method of communication, comprising: a universal internet protocol multimedia subsystem IMS receives a registration request from user equipment UE and registers for 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, wherein the session IMS slice is an IMS slice corresponding to a service type specified by a service type identifier in the call request;

or after the UE is registered, sending session IMS slice information to the UE, wherein the session IMS slice information is used for the UE to call the session IMS slice, and the IMS slice information comprises the address of the session IMS slice and the service type supported by the session IMS slice.

2. The method of claim 1, wherein selecting a session IMS slice for the UE, and wherein 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;

3. The method of claim 2, wherein the obtaining the session IMS slice comprises:

and inquiring an IMS slice corresponding to the service type specified by the service type identification as a session IMS slice in a Domain Name Server (DNS) or a network storage function (NRF).

4. The method according to any of claims 1 to 3, wherein the registering for the UE comprises:

5. A method of communication, comprising:

after the UE is registered, receiving session IMS slice information sent by the general IMS, wherein the IMS slice information comprises an address of the session IMS slice and a service type supported by the session IMS slice;

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

6. The method of claim 5, wherein the receiving the information of the session IMS slice sent by the generic IMS comprises:

and receiving a response message indicating that the authentication is passed, and analyzing the response message to obtain the information of the session IMS slice.

7. A communications device for use as a universal internet protocol multimedia subsystem, IMS, comprising:

the receiving unit is further configured to receive a call request sent by the UE after the registration unit successfully registers for the UE; a selecting unit, configured to select a session IMS slice for the UE after the receiving unit receives the call request sent by the UE; a sending unit, configured to forward the call request to the session IMS slice, where the session IMS slice is an IMS slice corresponding to a service type specified by a service type identifier in the call request;

or, a sending unit, configured to send, to the UE after the UE registration is passed, session IMS slice information used for the UE to call the session IMS slice, where the session IMS slice information includes an address of the session IMS slice and a service type supported by the session IMS slice.

8. The communication device of claim 7,

the selection unit is used for obtaining a service type identifier from the call request, obtaining the session IMS slice, and obtaining an address of the session IMS slice;

9. The communication device of claim 8,

the selecting unit, configured to obtain the session IMS slice, includes: the method is used for inquiring the IMS slice corresponding to the service type specified by the service type identification in a Domain Name Server (DNS) or a network storage function (NRF) as a session IMS slice.

10. The communication device according to any of claims 7 to 9,

the registration unit is used for obtaining a quintuple authentication vector from a Home Subscriber Server (HSS), authenticating the UE by using the quintuple authentication vector, determining that the UE passes registration after the UE passes authentication, and determining that the UE succeeds registration after a response message indicating that the authentication passes is sent to the UE through the sending unit.

11. A communication apparatus, for use as a user equipment, UE, comprising:

a receiving unit, configured to receive, after the UE is registered, session IMS slice information sent by the generic IMS, where the session IMS slice information includes: the address of the session IMS slice and the service type supported by the session IMS slice;

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

12. The communication apparatus according to claim 11, wherein the receiving unit comprises:

a receiving subunit, configured to receive a response message indicating that the authentication passes;

and the analysis unit is used for analyzing the response message to obtain the information of the session IMS slice.

13. A communication system, comprising: a general internet protocol multimedia subsystem IMS, and two or more session IMS slices;

the general IMS is used for executing the method of any one of claims 1 to 4;

14. The communication system of claim 13, further comprising: a packet switched PS core network; if the general IMS forwards the call request of the UE to the session IMS slice, the PS core network is in communication connection with the general IMS, and the general IMS is in communication connection with the media plane of the session IMS slice; and if the general IMS sends the information of the session IMS slice to the UE, the PS core network is respectively in communication connection with the general IMS and the media surface of the session IMS slice.

15. A communication device, comprising: an input device, an output device, a processor, and a storage device; it is characterized in that the preparation method is characterized in that,

stored in the storage device is program code that is called by the processor to control the input device and the processor to cooperate to perform the method of any one of claims 1 to 6.

16. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program comprising program instructions which, when executed by a processor, perform the method of any of claims 1 to 6.