WO2019184717A1 - Procédé de communication et produit associé - Google Patents

Procédé de communication et produit associé Download PDF

Info

Publication number
WO2019184717A1
WO2019184717A1 PCT/CN2019/078151 CN2019078151W WO2019184717A1 WO 2019184717 A1 WO2019184717 A1 WO 2019184717A1 CN 2019078151 W CN2019078151 W CN 2019078151W WO 2019184717 A1 WO2019184717 A1 WO 2019184717A1
Authority
WO
WIPO (PCT)
Prior art keywords
ims
session
slice
ims slice
session ims
Prior art date
Application number
PCT/CN2019/078151
Other languages
English (en)
Chinese (zh)
Inventor
张彪
舒续祖
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2019184717A1 publication Critical patent/WO2019184717A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1073—Registration or de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a communication method and related products.
  • IMS internet protocol multimedia subsystems
  • MCPTT mission-critical push-to-talk
  • 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.
  • VoLTE voice over long term evolution
  • 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;
  • 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.
  • PS packet switching
  • NAS non-access stratum
  • 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.
  • 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.
  • 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:
  • the session IMS slice is an IMS slice corresponding to the service type specified by the service type identifier;
  • the process of obtaining a session IMS slice is also provided as follows: the obtaining the session IMS slice includes:
  • an IMS slice corresponding to the service type specified by the service type identifier is queried as a session IMS slice.
  • DNS domain name server
  • NRF network repository function
  • 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 is 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.
  • the registering for the UE includes:
  • HSS home subscriber server
  • 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;
  • 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:
  • the response message passed by the knowledge authentication can usually be a 200 OK message.
  • the session IMS information includes:
  • the address of the session IMS slice and the type of service supported by the session IMS slice is the address of the session IMS slice and the type of service supported by the session IMS slice.
  • 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;
  • 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.
  • 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.
  • 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.
  • 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 is the address of the session IMS slice and the type of service supported by the session IMS slice.
  • 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.
  • the receiving unit includes:
  • the receiving subunit is configured to receive a response message indicating that the authentication is passed;
  • a parsing unit configured to parse the response message to obtain information of the session IMS slice.
  • the session IMS information includes:
  • the address of the session IMS slice and the type of service supported by the session IMS slice is the address of the session IMS slice and the type of service supported by the session IMS slice.
  • 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.
  • 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.
  • FIG. 1 is a schematic structural diagram of a system according to an embodiment of the present invention.
  • FIG. 2 is a schematic structural diagram of a system according to an embodiment of the present invention.
  • FIG. 3 is a schematic structural diagram of a system according to an embodiment of the present invention.
  • FIG. 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.
  • FIG. 7 is a schematic flowchart of a call method according to an embodiment of the present invention.
  • FIG. 8 is a schematic flowchart of a registration method according to an embodiment of the present invention.
  • FIG. 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.
  • 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 apparatus according to an embodiment of the present invention.
  • 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
  • UPF data network
  • AMF authentication management field
  • SMF service management function
  • PCF policy control function
  • AF application function
  • AUSF authentication server function
  • UDM unified data management
  • 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.
  • S-CSCF serving call session control function
  • P-CSCF proxy call session control function
  • I-CSCF Interrogating call session control function
  • the 5G core network (5GC)/evolved core network (EPC) is a common part of IMS1 and IMS2.
  • 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.
  • the IMS slice1 is selected, and the UE selects the MCPTT service.
  • 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 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.
  • FIG. 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:
  • the UE sends a registration request to the universal IMS.
  • the universal IMS After receiving the registration request of the user equipment UE, the universal IMS registers with the UE.
  • the UE 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.
  • the universal IMS selects a session IMS slice for the UE, and forwards the call request to the session IMS slice.
  • the universal IMS selects the session IMS slice of the call for the UE according to the information carried in the call request.
  • 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.
  • the UE sends a call request to the session IMS slice.
  • 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.
  • 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.
  • 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.
  • PS packet switching
  • 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 media side device may include an IMS-access gateway (AGW) in the current protocol.
  • AGW IMS-access gateway
  • 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.
  • SIP session initiation protocol
  • 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:
  • the UE sends a registration message to the common IMS to request IMS registration.
  • 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 IMS private user identity
  • T-IMPU IMS temporary multimedia public identity
  • 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.
  • IMPU Internet protocol multimedia public identity
  • Contact header field The contact address of the registered user.
  • 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.
  • IPSec internet security
  • AKA authentication key agreement
  • Require/Proxy-Require header field Indicates that the UE requires IPSec AKA authentication.
  • 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 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.
  • the UE 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.
  • RAND response toponse, RES
  • CK CK
  • IK IK
  • the IMS 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.
  • 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
  • MSISDN mobile station international ISDN number
  • Tel telephone
  • URI Uniform Resource Identifier
  • SIP URI SIP URI
  • 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.
  • the call message is implemented by using an invite message in the flow, and the detailed process is as follows:
  • the UE initiates a session, and sends an invite message to the common IMS.
  • Request-URI the called user number
  • Contact header field the contact address of the calling user
  • Feature-tag service type identifier
  • Session description protocol The media capability of the calling UE, including the supported media types and the codec capabilities of the corresponding media.
  • 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.
  • the IMS slice After receiving the invite message, the IMS slice performs session processing and service triggering.
  • the IMS slice sends an 18x message to the common IMS, informing the calling user that the called party is ringing;
  • the common IMS forwards the 18x message to the UE.
  • the IMS slice sends a 200 OK message to the common IMS to notify the calling user to be answered by the called party.
  • the common IMS sends a 200 OK message to the UE to notify the calling user to be answered by the called party.
  • 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.
  • session IMS 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.
  • 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.
  • 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.
  • 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:
  • the UE sends a registration message to the common IMS to request IMS registration.
  • 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.
  • 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.
  • Require/Proxy-Require header field Indicates that the UE requires IPSec AKA authentication.
  • 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.
  • the UE 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.
  • 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.
  • 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.
  • 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.
  • the UE After receiving the 200 OK, the UE records the P-Slice-URI header field information.
  • the UE 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:
  • 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:
  • 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.
  • the IMS slice sends an 18x message to the UE, informing the calling user that the called party is ringing;
  • 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.
  • 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 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.
  • 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.
  • 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.
  • 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.
  • the information about the session IMS slice includes:
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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. .
  • input interface 13021 is for performing a receive registration request
  • 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 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.
  • the former corresponds to the network system shown in FIG. 3, and the latter corresponds to the network system shown in FIG. 4;
  • 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.
  • 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
  • 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 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.
  • the disclosed systems, methods, and apparatus may be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the above units is only a logical function division.
  • 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.
  • 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.
  • 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.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • 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.
  • 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.)
  • 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.
  • 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.

Landscapes

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

Abstract

L'invention concerne un procédé de communication et un produit associé. Le procédé comprend les étapes suivantes : après avoir reçu une demande d'enregistrement d'un équipement utilisateur (UE), un IMS commun effectue un enregistrement pour l'UE; et si une demande d'appel envoyée par l'UE est reçue après l'enregistrement réussi pour l'UE, sélectionner une tranche IMS de session pour l'UE, puis transmettre la demande d'appel à la tranche IMS de session; ou après que l'UE a réussi l'enregistrement, envoyer des informations de la tranche IMS de session à l'UE, les informations de la tranche IMS de session permettant à l'UE d'appeler la tranche IMS de session. Un IMS commun est chargé de la fonction d'exécution de l'enregistrement pour un UE, il est inutile de connecter l'UE à de multiples tranches IMS; par conséquent, les exigences concernant l'UE sont moins élevées. L'UE ne doit pas rechercher de multiples tranches IMS. L'IMS commun transmet une demande d'appel ou envoie la demande d'appel en fonction des tranches IMS fournies par l'IMS commun. La complexité du déploiement du réseau est donc réduite
PCT/CN2019/078151 2018-03-30 2019-03-14 Procédé de communication et produit associé WO2019184717A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810286666.6 2018-03-30
CN201810286666.6A CN110324291B (zh) 2018-03-30 2018-03-30 一种通信方法、及相关产品

Publications (1)

Publication Number Publication Date
WO2019184717A1 true WO2019184717A1 (fr) 2019-10-03

Family

ID=68058564

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/078151 WO2019184717A1 (fr) 2018-03-30 2019-03-14 Procédé de communication et produit associé

Country Status (2)

Country Link
CN (1) CN110324291B (fr)
WO (1) WO2019184717A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114095365A (zh) * 2020-08-24 2022-02-25 中移物联网有限公司 基于5g消息的物联网业务的处理方法及装置

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110881207B (zh) * 2019-10-31 2022-06-14 荣耀终端有限公司 一种网络切片选择方法及相关产品
CN114884666A (zh) * 2021-01-22 2022-08-09 华为技术有限公司 认证方法及通信装置

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10373815B2 (en) * 2013-04-19 2019-08-06 Battelle Memorial Institute Methods of resolving artifacts in Hadamard-transformed data
CN104936262B (zh) * 2014-03-21 2020-02-28 中兴通讯股份有限公司 远端标识的发送、接收方法及装置、传输系统
US9509853B2 (en) * 2014-12-01 2016-11-29 T-Mobile Usa, Inc. SIP IMS call forking to multiple associated devices
CN106941734B (zh) * 2016-01-05 2020-06-12 中国移动通信集团公司 一种通信方法、装置及系统
JP2019515581A (ja) * 2016-05-12 2019-06-06 コンヴィーダ ワイヤレス， エルエルシー 仮想化されたモバイルコアネットワークへの接続

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specifica- tion Group Services and System Aspects; Study on Enhanced IMS to 5GC Integration(Release 16", 3GPP TR 23. 794 V0.6.0, 12 March 2019 (2019-03-12), XP051722761 *
"Technical Specification Group Services and System Aspects; Study on Enhanced IMS to 5GC Integration(Release 16)", 3GPP TR 23. 794 V0.2.0, 26 March 2018 (2018-03-26), XP051450495 *
HUAWEI: "Solution for Network Slicing and IMS Scenario 2", 4GPP SA WG2 MEETING #126, S2-182176, 2 March 2018 (2018-03-02), XP051408702 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114095365A (zh) * 2020-08-24 2022-02-25 中移物联网有限公司 基于5g消息的物联网业务的处理方法及装置
CN114095365B (zh) * 2020-08-24 2023-07-21 中移物联网有限公司 基于5g消息的物联网业务的处理方法及装置

Also Published As

Publication number Publication date
CN110324291B (zh) 2022-04-22
CN110324291A (zh) 2019-10-11

Similar Documents

Publication Publication Date Title
US9882943B2 (en) Method of access provision
US11063990B2 (en) Originating caller verification via insertion of an attestation parameter
US9232386B2 (en) System and method for terminating communication sessions with roaming mobile devices
US20220338152A1 (en) Support for ims routing with multiple ims pdu sessions over different 5gc slices
WO2019144935A1 (fr) Procédé de communication et dispositif de communication
US20160191523A1 (en) Service authority determination method and device
US20160359927A1 (en) Method and device for establishing channel
WO2006136106A1 (fr) Procede et systeme d'authentification de terminal d'usager
US20110173687A1 (en) Methods and Arrangements for an Internet Multimedia Subsystem (IMS)
WO2019128650A1 (fr) Procédé et dispositif de traitement de demande de service, et système de communication
US20110194554A1 (en) Systems and methods for implementing call pick up using gruu an ims network
WO2022083552A1 (fr) Procédé et appareil de traitement d'appels et support de stockage
US20120180117A1 (en) Method for Realizing End-to-End Call, End-to-End Call Terminal and System
WO2019184717A1 (fr) Procédé de communication et produit associé
US20220408251A1 (en) Method for supporting authentication of a user equipment
JP5470464B2 (ja) Ｉｐマルチメディア・サブシステム・ネットワークの緊急シグナリング
CN106941669B (zh) 无线通信方法和p-cscf设备
US9374469B2 (en) Voice over long term evolution-called party status
US9326141B2 (en) Internet protocol multimedia subsystem (IMS) authentication for non-IMS subscribers
US11490255B2 (en) RCS authentication
CN106790055B (zh) 一种ims系统的注册方法与装置
US20140328217A1 (en) Detecting quality of service and precondition capabilities of a core network
CN110446277B (zh) 一种双卡终端VoWiFi业务接入方法和终端
WO2012129913A1 (fr) Procédé et dispositif connexe permettant l'enregistrement d'un terminal sip et le traitement de service
CN113596836B (en) Single-card multi-point access and authentication method, device and system based on IMS environment

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19776965

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 19776965

Country of ref document: EP

Kind code of ref document: A1