WO2019128650A1 - 业务请求处理方法、装置及通信*** - Google Patents
业务请求处理方法、装置及通信*** Download PDFInfo
- Publication number
- WO2019128650A1 WO2019128650A1 PCT/CN2018/119262 CN2018119262W WO2019128650A1 WO 2019128650 A1 WO2019128650 A1 WO 2019128650A1 CN 2018119262 W CN2018119262 W CN 2018119262W WO 2019128650 A1 WO2019128650 A1 WO 2019128650A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- cscf
- called
- service
- address
- information
- Prior art date
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/10—Architectures or entities
- H04L65/1045—Proxies, e.g. for session initiation protocol [SIP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/10—Architectures or entities
- H04L65/1016—IP multimedia subsystem [IMS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
-
- 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/1069—Session establishment or de-establishment
-
- 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
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1101—Session protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W40/00—Communication routing or communication path finding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
- H04W48/14—Access restriction or access information delivery, e.g. discovery data delivery using user query or user detection
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/11—Allocation or use of connection identifiers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/18—Selecting a network or a communication service
-
- 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
- H04W60/005—Multiple registrations, e.g. multihoming
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/04—Registration at HLR or HSS [Home Subscriber Server]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
- H04W8/20—Transfer of user or subscriber data
Definitions
- the present invention relates to the field of communications technologies, and in particular, to a service request processing method, a related device, and a communication system.
- the fifth-generation (5th generation, 5G) network is a next-generation network that network operators hope to deploy, which has high-rate and low-latency characteristics.
- a network slice is one of the features provided by a 5G network, which can satisfy different service requirements by separating different network slices for the 5G network.
- the user equipment (UE) can select the corresponding 5G core network slice (referred to as 5GC network slice or 5GC slice) and initiate different services according to different service requirements.
- the service-call session control function (S-CSCF) in the IMS network of the IP multimedia sub-system is mainly used to receive the called service request for the UE.
- the called service request is routed to a proxy-call session control function (P-CSCF) in the IMS system currently registered by the UE, and the P-CSCF may send the called service request to the UE for processing.
- P-CSCF proxy-call session control function
- the UE accesses the IMS through different 5GC network slices, it performs multiple registrations in the IMS network through different P-CSCFs, and each registration corresponds to one 5GC network slice. After the registration is successful, the user can initiate different IMS services on different 5GC network slices.
- the prior art does not solve the technical problem of how the S-CSCF in the IMS sends the called service request for the UE to the corresponding P-CSCF after the UE accesses the IMS through different 5GC network slices.
- the embodiment of the present application provides a method, related apparatus, and system for transmitting a called service request of a UE to a corresponding P-CSCF for processing in a case of a 5GC network slice.
- the embodiment of the present application provides a method for processing a called service request, which is applied to a first S-CSCF in an IMS system, and includes the following steps:
- I-CSCF interrogating-call session control function
- the P-CSCF in the IMS since the 5GC network slice corresponds to different services, the P-CSCF in the IMS also corresponds to different service information, and after receiving the called service request sent by the I-CSCF, the first S-CSCF The address of the corresponding P-CSCF may be obtained according to the information of the called service carried therein, so that the first S-CSCF sends the called service request to the P-CSCF corresponding to the address, and the called party is called by the P-CSCF. Business requests are processed.
- This embodiment solves the technical problem of how the S-CSCF in the IMS sends the called service request for the UE to the corresponding P-CSCF for processing after the UE accesses the IMS through different 5GC network slices.
- the called service request further carries the identifier of the called user equipment UE, and the first S-CSCF determines the proxy corresponding to the information of the called service and the identifier of the called UE.
- the call session controls the address of the functional device P-CSCF and sends the called service request to the P-CSCF.
- the first S-CSCF determines the address of the P-CSCF corresponding to the information of the called service and the identifier of the called UE, and the first S-CSCF may send a query request to the home subscriber server HSS.
- a message configured to query an address of the P-CSCF corresponding to the identifier of the called UE and the information of the called service, where the query request message carries the identifier of the called UE and the information of the called service;
- the HSS receives a query response message, where the query response message carries an address of the P-CSCF corresponding to the identifier of the called UE and the information of the called service.
- the first S-CSCF determines the address of the proxy call session control function device P-CSCF corresponding to the information of the called service and the identifier of the called UE by sending a query request message to the HSS, thereby
- the corresponding information may be obtained from the HSS.
- the address of the P-CSCF which in turn can send the called service request to the P-CSCF to continue the IMS called service.
- the determining, by the first S-CSCF, the address of the P-CSCF corresponding to the service information in the called service request and the identifier of the called UE may further include: querying the local correspondence and the The service information in the called service request and the address of the P-CSCF corresponding to the identifier of the called UE.
- the S-CSCF may determine whether there is data of the called UE locally, and if so, query the corresponding relationship locally to obtain the address of the P-CSCF, if not Then, the HSS is queried for the address of the P-CSCF.
- the first S-CSCF may further receive a registration message of the called UE sent by the I-CSCF, where The registration message carries the identifier of the called UE, the service information of the service provided by the 5G core network network slice, and the address of the P-CSCF, and then the first S-CFCF locally saves the identifier of the called UE, 5G.
- the correspondence between the service information of the service provided by the core network network slice and the address of the P-CSCF may query the corresponding relationship, and send the called service request of the UE to the corresponding P-CSCF for service processing.
- the first S-CSCF further sends the identifier of the called UE, the service information of the service provided by the 5G core network network slice, and the address of the P-CSCF to the HSS.
- the solution can enable the HSS to save the correspondence and implement backup of the correspondence. Therefore, in the event that the first S-CSCF fails, the correspondence may be sent to the reselected S-CSCF to implement fault recovery, thereby ensuring the IMS service to continue.
- the foregoing first S-CSCF is an S-CSCF that provides services for the UE, and may be an S-CSCF initially registered by the UE, and may also be an IMS network after the initial registration of the S-CSCF fails. Selected S-CSCF.
- the I-CSCF before the first S-CSCF receives the called service request sent by the I-CSCF, the I-CSCF receives the called service request sent by the external network (other than the IMS network), and determines the The initial S-CSCF registered by the called UE in the called service request is faulty, and then the called S-CSCF is sent to the first S-CSCF to trigger the first S-CSCF to process the called service request.
- the first S-CSCF is currently serving the UE, and it does not fail.
- the application provides a service call session control function device, which includes a receiving module, a determining module, and a sending module.
- the receiving module is configured to receive the called service request sent by the inquiring call session control function device I-CSCF, where the called service request carries the identifier of the called user equipment UE and the information of the called service; An address of the proxy call session control function device P-CSCF corresponding to the information of the called service and the identifier of the called UE; and a sending module, configured to send the called party to the P-CSCF Business request.
- the determining module in the S-CSCF includes:
- a sending sub-module configured to send a query request message to the home subscriber server HSS, to query an address of the P-CSCF corresponding to the identifier of the called UE and the information of the called service, where the query request message carries the The identity of the called UE and the information of the called service;
- the receiving submodule is configured to receive the query response message returned by the HSS, where the query response message carries an address of the P-CSCF corresponding to the identifier of the called UE and the information of the called service.
- the determining module in the S-CSCF determines the address of the P-CSCF corresponding to the service information in the called service request and the identifier of the called UE, including: querying the local correspondence and the The service information in the service request and the address of the P-CSCF corresponding to the identifier of the called UE.
- the receiving module in the S-CSCF receives the registration message of the called UE sent by the I-CSCF before receiving the called service request sent by the I-CSCF, where the registration message is received.
- the identifier of the called UE, the service information of the service provided by the 5G core network network slice, and the address of the P-CSCF are carried in the identifier.
- the S-CSCF further includes a saving module, configured to save the identifier of the called UE, the service information of the service provided by the 5G core network network slice, and the correspondence between the addresses of the P-CSCF.
- the sending module in the S-CSCF is further configured to send the identifier of the called UE and the address of the P-CSCF to the HSS.
- the present application provides a communication system, which mainly includes: a first service call session control function entity S-CSCF, an inquiry call session control function device I-CSCF, and a proxy call session control function device P-CSCF.
- the first S-CSCF is configured to receive the called service request sent by the I-CSCF, where the called service request carries the identifier of the called user equipment UE and the information of the called service, and determines the called service. And the information of the P-CSCF corresponding to the identifier of the called UE, and sending the called service request to the P-CSCF.
- the communication system further includes a home subscriber server HSS, and the first S-CSCF determines a P-CSCF corresponding to the service information in the called service request and the identifier of the called UE.
- the address includes: sending a query request message to the HSS, for querying an address of the P-CSCF corresponding to the identifier of the called UE and the information of the called service, where the query request message carries the called UE.
- the query response message carries an address of the P-CSCF corresponding to the identifier of the called UE and the information of the called service.
- the first S-CSCF in the communication system further receives the registration message of the called UE sent by the I-CSCF before receiving the called service request sent by the I-CSCF, where
- the registration message carries the identifier of the called UE and the address of the P-CSCF, and the correspondence between the identifier of the called UE and the address of the P-CSCF is saved.
- the I-CSCF in the communication system is further configured to receive the called service request, and determine an initial S-CSCF fault registered by the called UE in the called service request; An S-CSCF sends the called service request.
- the first S-CSCF in the communication system may further send the identifier of the called UE, the service information of the service provided by the 5GC network slice, and the address of the P-CSCF to the HSS.
- the present application further provides a method for processing a called service request, which may be implemented by a home subscriber server HSS, including:
- the home subscriber server HSS receives the query request message sent by the first S-CSCF, where the query request message carries the identifier of the called UE in the called service request and the information of the called service in the called service request, and then the HSS determines An address of the P-CSCF corresponding to the identifier of the called UE and the information of the called service, and sending a query response message to the first S-CSCF, where the query response message carries the address of the P-CSCF.
- the HSS may send the locally saved one to the first S-CSCF when the first S-CSCF sends a query request message to the first S-CSCF, so that the first S-CSCF may be The service request is sent to the corresponding P-CSCF for processing to implement the IMS service.
- the HSS before receiving the query request message sent by the first S-CSCF, the HSS further includes: receiving an identifier of the called UE sent by the S-CSCF, service information of the service provided by the 5GC network slice, and the The address of the P-CSCF registered by the called UE, and the correspondence between the identifier of the called UE, the service information of the service provided by the 5GC network slice, and the address of the P-CSCF registered by the called UE is saved, which is convenient for subsequent Query the correspondence.
- the application provides a method for registering a user equipment, which is applied to a user equipment UE, which mainly includes: the UE first acquires service information of a service provided by a 5G core network slice and a proxy call session control function device P in an IMS network. The address of the CSCF is then sent to the P-CSCF according to the address, and the registration message carries the service information of the service provided by the 5G core network slice or the identifier of the 5G core network slice.
- the registration message sent by the UE is sent to the S-CSCF by the P-CSCF in the IMS network, and is sent by the S-CSCF to the HSS, so that both the S-CSCF and the HSS can store the service information of the service provided by the 5GC network slice.
- Corresponding relationship between the P-CSCFs in the IMS network corresponding to the foregoing first aspect, is convenient for the S-CSCF to subsequently query the P-CSCF corresponding to the service information to solve the routing error of the incoming service request in the 5GC network slicing scenario.
- the UE acquiring the service information of the service provided by the 5G core network slice includes: acquiring, by the UE, the 5G core from a 5G core network (for example, AMF) when attaching to the 5G core network slice The business information of the business provided by the network slice.
- a 5G core network for example, AMF
- the user equipment UE carries the service information in a header field of a registration message.
- the UE acquiring the address of the proxy call session control function device P-CSCF in the IMS network includes: when the UE establishes a PDU session with the 5G core network slice, the slice is sliced from the 5G core network (for example, AMF) Obtaining an address of the proxy call session control function device P-CSCF in the IMS network.
- the 5G core network for example, AMF
- An optional solution is that the user equipment can obtain the service information of the service request initiated by the user, and then send the service request to the P-CSCF corresponding to the service information. Therefore, the user equipment can process the service request initiated by the user and send it to the P-CSCF corresponding to the service information for processing.
- an embodiment of the present application provides an S-CSCF, which can be implemented by using a general-purpose computer.
- the S-CSCF may include a memory, a processor, an input and output device, and the like.
- the program code is stored in the memory, and the processor can acquire and execute the program code stored in the memory, so that the S-CSCF can perform the communication method provided by the first aspect.
- the specific implementation process refer to the first aspect.
- an embodiment of the present application provides an HSS, which can be implemented by using a general-purpose computer.
- the HSS may include a memory, a processor, an input and output device, and the like.
- the program code is stored in the memory, and the processor can acquire and execute the program code stored in the memory, so that the HSS can perform the communication method provided by the fourth aspect.
- the specific implementation process refer to the fourth aspect.
- the service request may be an invite message
- the identifier of the UE may be an IP address of the UE, or an IP multimedia private identity (IMPI) or an IP multimedia public identity (IP) of the user. Multimedia public identity, IMPU).
- the query request message may specifically allocate a request message to the server, and the query response message may allocate a response message to the server.
- FIG. 1 is a schematic diagram of networking of a communication system according to Embodiment 1 of the present application.
- FIG. 2 is a flowchart of a service request processing method according to Embodiment 2 of the present application.
- FIG. 3 is a flowchart of a service request processing method according to Embodiment 3 of the present application.
- FIG. 4 is a flowchart of a service request processing method according to Embodiment 4 of the present application.
- FIG. 5 is a flowchart of a service request processing method according to Embodiment 5 of the present application.
- FIG. 6 is a hardware structural diagram of an S-CSCF according to Embodiment 6 of the present application.
- FIG. 7 is a hardware structural diagram of a user equipment provided in Embodiment 7 of the present application.
- FIG. 8 is a schematic diagram of functional modules of an S-CSCF according to Embodiment 8 of the present application.
- FIG. 9 is a schematic diagram of functional modules of a user equipment provided in Embodiment 9 of the present application.
- FIG. 1 is a schematic diagram of networking of a communication system according to Embodiment 1.
- the communication system provided in this embodiment includes a user equipment (UE) and a network side device.
- the network side device may include a 5G core network (5GC) that performs mobility management, user plane control, and the like for the user equipment accessing the 5G network, and an IMS network that provides IMS services to the user equipment.
- 5GC 5G core network
- 5GC can perform network slicing.
- the 5GC is cut into 5GC1 and 5GC2.
- the principle of the 5GC to slice may include a service type, a user type, a user level, a number segment, and the like, which is not limited in this embodiment of the present application.
- Different 5GC network slices (also referred to as 5G network slices or 5GC slices) can provide different services, for example, 5GC1 provides voice call service, and 5GC2 provides public security cluster service.
- the devices in the 5GC include an access and mobility management function (AMF) for access and mobility management of the UE, and a session management function (SMF) for managing the session of the UE. ), a user plane function (UPF) that controls the user plane of the UE.
- AMF access and mobility management function
- SMF session management function
- UPF user plane function
- other devices are also included in the 5GC, for example, a device that performs a policy control function, which is not limited in this embodiment.
- the devices in the IMS may include a proxy-call session control function (P-CSCF1) and a proxy call session control function device 2 (P-CSCF2), and a service call session control function device (service-call session).
- P-CSCF proxy-call session control function
- P-CSCF2 proxy call session control function device 2
- S-CSCF service call session control function device
- S-CSCF service call session control function
- I-CSCF interrogating-call session control function
- AS application service
- HSS home subscriber server
- P-CSCF1 is connected to 5GC1
- P-CSCF2 is connected to 5GC2.
- the HSS is mainly used to store user account opening data, and its function can also be implemented by a unified device management (UDM) device.
- UDM unified device management
- the UE can access 5GC1 and 5GC2 to obtain two IP addresses (IP1 and IP2), IP1 corresponds to 5GC1, and IP2 corresponds to 5GC2.
- IP1 and IP2 corresponds to 5GC2.
- the UE also establishes a packet data unit (PDU) session at 5GC1 and 5GC2, respectively.
- PDU packet data unit
- the UE acquires the address of the P-CSCF1 and the address of the P-CSCF2 in the IMS from 5GC1, 5GC2, respectively.
- the UE initiates an IMS registration with the P-CSCF1 using IP1, and initiates an IMS registration with the P-CSCF2 using IP2.
- the UE may initiate an IMS service on the two 5GC network slices respectively, for example, the UE initiates a virtual reality (VR) service or a public security cluster service at 5GC1, and initiates a voice call service or augmented reality at 5GC2.
- VR virtual reality
- AR AR
- the registration message (register) sent to the P-CSCF1 carries the service information 1 of the service provided by the 5GC1 (or the information of the called service, such as the service type or service).
- the identifier is transmitted to the S-CSCF through the P-CSCF1, so that the S-CSCF can save the correspondence between the service information 1 and the P-CSCF1.
- the UE also carries the service information 2 of the service provided by the 5GC2, and the S-CSCF also stores the correspondence between the service information 2 and the P-CSCF2.
- the S-CSCF in the subsequent IMS network may determine the corresponding information according to the service information in the called service request (which may also be referred to as the called service request message).
- the P-CSCF sends the called service request to the corresponding P-CSCF, and the P-CSCF sends the called service request to the UE for processing.
- the P-CSCF in the corresponding IMS since the 5G network slice corresponds to different services, the P-CSCF in the corresponding IMS also corresponds to different service information, and after receiving the called service request sent by the I-CSCF, the S-CSCF receives the called service request.
- the address of the P-CSCF corresponding to the information may be obtained according to the information of the called service carried therein, so that the S-CSCF sends the called service request to the P-CSCF corresponding to the address.
- the present embodiment solves the technical problem of how the S-CSCF in the IMS sends the called service request for the UE to the corresponding P-CSCF for processing after the UE accesses the IMS through different 5G network slices, thereby avoiding the service request.
- the situation in which the IMS service fails due to being routed to the wrong P-CSCF improves the stability and efficiency of the communication system.
- FIG. 2 is a flowchart of implementing a method for processing a called service request according to Embodiment 2 of the present application.
- the I-CSCF in the IMS network receives the called service request for the incoming user equipment, and the I-CSCF goes to the S-CSCF (corresponding to the first S-CSCF in the content of the invention) Sending the called service request, the S-CSCF can perform the following steps:
- Step 201 The S-CSCF receives the called service request sent by the I-CSCF, where the called service request carries the identifier of the called UE and the information of the called service.
- the S-CSCF can receive the called service request sent by the I-CSCF through the Mw interface, where the request carries the identifier of the called UE and the information of the called service.
- the identifier of the UE may be an address of the UE, such as an IP address of the UE, a session initiation protocol address, an International Mobile Equipment Identity (IMEI), a physical address, etc., and may also be an identifier of the called user, for example, IP multimedia private identity (IMPI) or IP multimedia public identity (IMPU), mobile station international integrated services Digital Network number (MSISDN). Therefore, the identity of the UE may be in different expressions in all embodiments provided in this application, but may be used to identify this UE. These possible alternatives are all included in the embodiments of the present application.
- the identifier of the UE in step 201 may be a session initialization protocol address of the UE.
- the identifier carried in the registration message sent by the UE may be an IP address of the IMPU or the UE in the 5G network.
- the identifiers of the UEs in all the embodiments of the present application may be plural, that is, may be multiple specific identifiers, for example, the SIP address and the MSISDN number of the UE that can carry the UE in the called service request.
- the information of the called service may be a service type or a service identifier.
- Step 202 The S-CSCF determines an address of the P-CSCF corresponding to the service information in the called service request and the identifier of the called UE.
- the S-CSCF can locally store the service information of the service provided by the 5GC network slice, the correspondence between the identifier of the called UE and the address of the P-CSCF registered by the called UE, and further receive the called service. After the request, the corresponding relationship is queried locally, and the address of the P-CSCF corresponding to the service information carried in the called service request and the identifier of the called UE is obtained.
- the service information carried in the called service request may also be simply referred to as the information of the called service. Since different 5GC network slices correspond to different P-CSCFs, the P-CSCF registered by the called UE may be referred to as a P-CSCF corresponding to the 5GC network slice.
- the S-CSCF may also query other devices in the IMS network, such as the HSS, for the address of the P-CSCF corresponding to the service information in the called service request and the identifier of the called UE.
- the S-CSCF may determine whether there is data of the called UE locally, and if so, query the corresponding relationship locally to obtain the address of the P-CSCF, if not, Query the HSS for the address of the P-CSCF.
- Step 203 The S-CSCF sends the called service request to the P-CSCF.
- the S-CSCF since the S-CSCF obtains the address of the P-CSCF corresponding to the service information in the called service request and the identifier of the UE, the called service request may be sent to the corresponding P-CSCF, so that P- The CSCF processes the service request to implement processing of the called service request in the 5GC slice scenario.
- the S-CSCF may receive a register message of the UE sent by the I-CSCF when the called user equipment UE initiates the IMS registration in the 5GC network slice, and the header field of the registration message carries the The identifier of the UE, the service information of the service provided by the 5GC network slice, and the address of the P-CSCF, so that the S-CSCF saves the identity of the called UE, the service information of the service provided by the 5GC network slice, and the address of the P-CSCF.
- the correspondence between the two is convenient for subsequently querying the address of the P-CSCF corresponding to the service information according to the correspondence.
- FIG. 3 is a flowchart of implementing a user equipment registration method according to Embodiment 3 of the present application.
- the IMS registration method provided by the embodiment of the present application is mainly used for a user equipment, and the method includes:
- Step 301 The UE acquires service information of a service provided by the 5GC network slice and an address of the proxy call session control function device P-CSCF in the IMS network.
- the user equipment can obtain the service information of the service provided by the 5GC network slice from the 5G core network (for example, AMF) when attaching to the 5GC network slice. Also.
- the UE may also establish a PDU session with the 5GC network slice after attaching to the 5GC network slice, and acquire the address of the P-CSCF corresponding to the 5GC network slice from the 5GC during the establishment of the PDU session.
- the UE can locally store the correspondence between the service information of the services provided by the multiple 5GC network slices and the address of the P-CSCF corresponding to the 5GC network slice.
- Step 302 The UE sends a registration message to the P-CSCF according to the address, where the registration message carries the service information of the service provided by the 5GC network slice or the identifier of the 5GC network slice.
- the UE may generate a registration message (also referred to as a registration request), and then send a registration message to the P-CSCF in the IMS network through the 5GC1, where the service information of the service provided by the 5GC network slice is carried.
- the registration message may also carry the IP address of the UE in the 5GC network slice.
- the service information of the service provided by the 5GC network slice in the registration message may also be the identifier of the 5GC network slice, and then the P in the IMS network.
- the CSCF or the S-CSCF may associate it with the service information of the service provided by the 5GC network slice.
- the registration message sent by the UE may also carry the identifier of the UE, such as the IP address of the terminal and/or the IMPU.
- the P-CSCF may send the registration message to the S-CSCF in the IMS network, so that the S-CSCF can save the message.
- the service information, the identifier of the UE, and the correspondence between the P-CSCF and the P-CSCF are facilitated to be subsequently queried to the address of the P-CSCF corresponding to the service information, thereby routing the incoming service request to the P corresponding to the service information.
- -CSCF proceeds to processing and continues IMS service processing.
- the second IMS registration can also be completed through 5GC2.
- the UE may initiate a service at 5GC1 or 5GC2, and the related service request is sent to the P-CSCF through the 5GC, and then forwarded by the P-CSCF to the S-CSCF in the IMS network.
- the UE initiates a low-latency service such as AR/VR in 5GC1.
- the UE initiates a public security cluster service such as a mission-critical push-to-talk (MCPTT) at 5GC2.
- MCPTT mission-critical push-to-talk
- an embodiment of the present application further provides an implementation process of a service processing method.
- the service processing method provided in Embodiment 4 of the present application specifically includes the following steps:
- Step 401 The UE acquires an address of the proxy call session control function device P-CSCF in the IMS network and service information of the service provided by the 5GC network slice.
- the service information may be a service type or a service identifier
- the service type may include a low-latency service (such as an augmented reality AR, a VR service), a voice call service, a short message, a public security cluster service, etc.
- the service identifier may be The identifier of the application APP.
- the service provided by the 5GC network slice is usually the service that the UE can initiate or receive. Therefore, the service information of the service provided by the 5GC network slice may also be referred to as the service information of the UE.
- the services provided by the 5GC network slice can be the same as those provided by the IMS network. For example, the voice service requires 5GC network slice and IMS network to provide support at the same time.
- the UE may send the slice ID of all 5GC network slices supported by the network to the UE when the UE is attached to the 5GC, and then the UE selects different 5GC network slices according to its capability or service information.
- the 5GC network slice that the UE needs to select may also be specified by the 5GC.
- Different 5GC network slices provide different IP addresses for the UE. In this embodiment, there are two slices in the 5GC network, namely 5GC1 and 5GC2. The address provided by the 5GC1 for the UE is IP1, and the address provided by the 5GC2 for the UE is IP2.
- different 5GC network slices can provide different services, and the UE can select two 5GC network slice attachments at the same time, and locally establish a correspondence between the service information of the service provided by the 5GC slice network and the 5GC network slice. relationship.
- the UE may acquire the address of the P-CSCF1 in the IMS network from the 5GC during the establishment of the PDU session with the 5GC network slice. Specifically, the UE may acquire the address of the P-CSCF1 in the IMS network from the AMF or SMF in the 5GC.
- the UE can also obtain the address of the P-CSCF1 from the local device in a locally configured manner.
- the address of the P-CSCF in the IMS network and the service information of the service provided by the 5GC network slice are all configured in the subscriber identity module of the UE.
- the SIM the UE can obtain the address and service information of the P-CSCF locally.
- the process of acquiring the P-CSCF address by the UE may also be referred to as P-CSCF discovery.
- Step 402 The UE sends a registration message to the P-CSCF1 according to the address of the P-CSCF1, where the registration message carries the service information of the service provided by the IMS network.
- the UE initiates IMS registration (initiating registration with the P-CSCF1) in the 5GC network slice 5GC1, and the process is the same as the process in which the UE initiates registration in the 5GC network slice 5GC2.
- the UE may initiate IMS registration on two 5GC network slices using an IP multimedia private identity (IMPI) and an IP multimedia public identity (IMPU) pair.
- IMPI IP multimedia private identity
- IMPU IP multimedia public identity
- the UE may also initiate IMS registration on two 5GC network slices using different IMPI and IMPU pairs, respectively.
- the UE may locally construct a session initial protocol (SIP)-based register message carrying the service information of the service provided by the 5GC network slice 5GC1.
- SIP session initial protocol
- the identity of the UE can also be carried.
- the identity of the UE may be the IP address (ie, IP1) of the UE in 5GC1 in addition to the possibilities mentioned previously.
- the registration message is sent to the P-CSCF1 through 5GC1 to continue the IMS registration process.
- Step 403 The P-CSCF1 sends the received registration message to the S-CSCF1.
- the P-CSCF1 can send the received registration message to the S-CSCF1 through the Mw interface.
- the registration message sent by the P-CSCF1 carries the address of the P-CSCF1, the IP address of the UE, and the service information of the service provided by the 5GC network slice. .
- the IP address of the UE (the IP address of the UE in 5GC1) carried in the registration message received by the P-CSCF and the IP address of the UE carried in the registration message sent by the P-CSCF may be different, that is, P
- the CSCF may convert the IP address of the UE carried in the received registration message, so that the registration message sent by the P-CSCF to the S-CSCF1 carries the translated address (for example, may be a SIP address).
- IP address of the UE in 5GC1 There is a correspondence between the IP address of the UE in 5GC1 and the above-mentioned converted address.
- the IP address of the UE carried in the registration message received by the P-CSCF and the address of the UE carried in the registration message sent by the P-CSCF to the S-CSCF1 are collectively referred to as the identifier of the UE.
- Step 404 The S-CSCF1 sends the service information of the service provided by the 5GC network slice carried in the registration message, the address of the P-CSCF1, and the identifier of the UE to the HSS.
- the S-CSCF1 may send a message to the HSS (specifically, may be a server assignment request (SAR) message), where the message carries the service information of the service provided by the 5GC network slice, the identifier of the UE, and the P - The address of CSCF1 (for example, IP address).
- SAR server assignment request
- the S-CSCF1 may also locally store the service information of the service provided by the 5GC network slice 5GC1, the correspondence between the identifier of the UE and the address of the P-CSCF1.
- Step 405 The HSS saves the correspondence between the service information of the service provided by the 5GC network slice 5GC1, the identifier of the UE, and the address of the P-CSCF1.
- the HSS can save the received correspondence, so that the subsequent HSS can query the address of the P-CSCF1 according to the corresponding relationship.
- the HSS can also store the correspondence between the address and the name of the UE and the S-CSCF1, so as to facilitate the subsequent query of the address of the S-CSCF registered by the UE.
- the HSS can store the service information of the services provided by different 5GC network slices, the correspondence between the address of the P-CSCF and the identifier of the UE.
- the correspondence between S-CSCF1 and HSS can be as follows:
- the two sets of correspondences may be associated by the IMPU of the UE.
- the HSS may also update the registration status of the UE to be registered, and send a server assignment answer (SAA) message to the S-CSCF1, where the user equipment is carried in the HSS. Subscribe to the information. Then, the S-CSCF1 may send a registration accept message to the UE to notify the UE that the current IMS network registration is successful.
- SAA server assignment answer
- the UE may initiate a VR service at 5GC1 after the registration is successful.
- the UE can also receive the incoming service request as the called party, for example, receiving a voice call request initiated by another user.
- the S-CSCF1 may also be referred to as an S-CSCF initially registered by the UE, and if it fails, the service of the S-CSCF1 may be replaced by the S-CSCF2.
- the service request processing method in this scenario is described in detail below.
- the service request processing method provided in this embodiment may further include:
- Step 501 The I-CSCF receives the service request.
- the I-CSCF in the IMS network receives the voice call service request.
- the voice service request may be an invite invite message carrying an identifier of the called UE, such as a SIP address or a mobile phone number of the UE.
- Step 502 The I-CSCF sends a location information request to the HSS for querying an address of the S-CSCF in the IMS network.
- the I-CSCF After receiving the service request, the I-CSCF sends a location information request (LIR) to the HSS for determining the S-CSCF registered by the UE.
- LIR location information request
- Step 503 The HSS returns a location information answer (LIA), where the address or name of the S-CSCF1 is carried.
- LIA location information answer
- the HSS locally stores the identifier (such as an address or a name) of the S-CSCF (ie, the S-CSCF1) when the UE is registered. After the local query, the HSS returns the identifier of the S-CSCF1 to the I-CSCF through the LIA.
- the identifier such as an address or a name
- the I-CSCF determines that the S-CSCF1 is faulty, and then continues to send a location information request to the HSS for querying addresses of other S-CSCFs in the IMS network.
- Step 504 The I-CSCF sends a location information request to the HSS for querying an address of the S-CSCF in the IMS network.
- Step 505 The HSS returns a location information response, where the address or name of the alternate S-CSCF2 is carried.
- the HSS determines the S-CSCF2 that the UE is in standby, and then sends a response message carrying the address or name of the standby S-CSCF2 to the I-CSCF through the location information response.
- Step 506 The I-CSCF sends the received service request to the device corresponding to the address of the S-CSCF2 carried in the location information response.
- the I-CSCF forwards the received service request to the S-CSCF2 in the IMS network, and the S-CSCF2 performs service processing.
- Step 507 The S-CSCF2 sends a query request message to the HSS, where the identifier of the UE is carried.
- a query request message is sent to the HSS for obtaining backup data of the UE.
- the identifier of the UE such as an IMPU, may be carried in the query request message.
- the query request message may specifically allocate a request SAR message to the server in this embodiment.
- Step 508 The HSS returns a query response message, where the correspondence between the IP address of the previously saved UE, the address of the P-CSCF, and the service information of the service provided by the 5GC network slice is carried.
- the correspondence between the IP address of the UE, the address of the P-CSCF, and the service information of the service provided by the different 5GC network slices is associated by the IMPU, and thus the HSS is received.
- the query request message of the IMPU is carried, the previously saved correspondence relationship can be obtained, and sent to the S-CSCF2 through the query response message.
- the query response message may specifically be a server assignment answer (SAA) message in this embodiment.
- SAA server assignment answer
- Step 509 The S-CSCF2 sends a service request to the P-CSCF1.
- the S-CSCF2 queries the foregoing correspondence table according to the identity of the UE (IMPU) and the service information (voice service), and obtains the IP address of the UE as 232.02.5.31, P. - The address of CSCF1 is 192.125.6.5, and then the service request is sent to the P-CSCF1 corresponding to 192.125.6.5, and the processing of the incoming (called) service request for the UE is implemented.
- FIG. 6 is a hardware structural diagram of a service call session control function device S-CSCF according to Embodiment 6 of the present application.
- the S-CSCF can be implemented by using general-purpose computer hardware, which includes a processor 601, a memory 602, a bus 603, an input device 604, an output device 605, and a network interface 606.
- memory 502 can include computer storage media in the form of volatile and/or nonvolatile memory, such as read only memory and/or random access memory.
- Memory 602 can store operating systems, applications, other program modules, executable code, program data, user account opening data, user subscription data, and the like.
- Input device 604 can be used to input commands and information to an S-CSCF, such as a keyboard or pointing device such as a mouse, trackball, touch pad, microphone, joystick, game pad, satellite television antenna, scanner, or the like. . These input devices can be connected to the processor 601 via the bus 603.
- the output device 605 can be used for S-CSCF output information. In addition to the monitor, the output device 605 can also be used for other peripheral outputs, such as speakers and/or printing devices, which can also be connected to the processor via the bus 603. 601.
- the S-CSCF can be connected to the network through a network interface 606, such as a local area network (LAN).
- a network interface 606 such as a local area network (LAN).
- computer-executed instructions stored in the S-CSCF can be stored in a remote storage device without being limited to local storage.
- the S-CSCF may perform the method steps on the S-CSCF side in the above embodiment, for example, performing steps 201-203, 507. , 509, etc.
- the S-CSCF may perform the method steps on the S-CSCF side in the above embodiment, for example, performing steps 201-203, 507. , 509, etc.
- FIG. 7 is a schematic structural diagram of a user equipment according to Embodiment 7 of the present application.
- the user equipment mainly includes a processor 7701, a memory 702, a bus 703, an input device 704, an output device 705, and a network interface 706.
- the user equipment may further include an application processor (AP), a battery, and the like.
- AP application processor
- memory 702 can include computer storage media in the form of volatile and/or nonvolatile memory, such as read only memory and/or random access memory.
- Memory 702 can store operating systems, applications, other program modules, executable code, and program data.
- Input device 704 can be used to input commands and information to a user device, such as a keyboard or pointing device such as a mouse, trackball, touch pad, microphone, joystick, game pad, round dish satellite television antenna, scanner, or Similar equipment. These input devices can be connected to the processor 701 via a bus 703.
- the output device 705 can be used for the user device to output information.
- the output device 705 can also be configured for other peripheral outputs, such as speakers, which can also be connected to the processor 701 via the bus 703.
- the user equipment can be connected to the network through the network interface 706, for example, through a wireless interface to a WIFI network, 5G, long term evolution (LTE) network.
- a wireless interface to a WIFI network, 5G, long term evolution (LTE) network.
- LTE long term evolution
- computer-executed instructions stored in a user device can be stored in a remote storage device without being limited to local storage.
- the user equipment may perform the method steps on the user equipment side in the above embodiment, for example, perform steps 301-302, 401-402, and the like. .
- the processor 701 in the user equipment executes the executable code or application stored in the memory 702
- the user equipment may perform the method steps on the user equipment side in the above embodiment, for example, perform steps 301-302, 401-402, and the like. .
- steps 301-302, 401-402, and the like for specific implementation processes and beneficial effects, refer to the related embodiments above, and details are not described herein again.
- FIG. 8 is a schematic diagram of functions of a service call session control function device S-CSCF according to Embodiment 8 of the present application.
- the service call session control function device S-CSCF provided by the embodiment of the present application mainly includes a receiving module 801, a determining module 802, and a sending module 803.
- the receiving module 801 is configured to receive the called service request sent by the called call session control function device I-CSCF, where the called service request carries the identifier of the called user equipment UE and the information of the called service;
- the determining module 802 is configured to determine an address of the P-CSCF corresponding to the information of the called service and the identifier of the called UE. The determining module 802 determines that the address of the P-CSCF corresponding to the information of the called service and the identifier of the called UE can be obtained by querying the information corresponding to the called service and the identifier of the called UE in the local correspondence. The CSCF address is implemented.
- the sending module 803 is configured to send the called service request to the P-CSCF.
- the S-CSCF provided by the embodiment of the present application may be used in the foregoing method embodiment, and the S-CSCF side of the foregoing method embodiment is implemented by the cooperation between the receiving module 801, the determining module 802, and the sending module 803. Method steps.
- the S-CSCF provided in this embodiment has the same beneficial effects as the foregoing method embodiments when performing the above communication process.
- the determining module 802 in the S-CSCF may specifically include: a sending submodule and a receiving submodule.
- the sending sub-module may be configured to send a query request message to the home subscriber server (HSS) for querying an address of the P-CSCF corresponding to the identifier of the called UE and the information of the called service, where the query request message is carried.
- HSS home subscriber server
- the receiving submodule may be configured to receive the query response message returned by the HSS, where the query response message carries the identifier and the called party of the called UE
- the information of the service corresponds to the address of the P-CSCF.
- the S-CSCF determines the address of the proxy call session control function device P-CSCF corresponding to the information of the called service and the identifier of the called UE by sending a query request message to the HSS, thereby
- the S-CSCF has no called UE related data locally (for example, the S-CSCF is a reselected S-CSCF after the initial S-CSCF failure)
- the address of the corresponding P-CSCF can be obtained from the HSS, and then The called service request is sent to the P-CSCF to continue the IMS called service.
- the receiving module 801 in the S-CSCF further receives the registration message of the called UE sent by the I-CSCF, before receiving the called service request sent by the I-CSCF, where the registration message carries the The identifier of the called UE, the service information of the service provided by the 5GC network slice, and the address of the P-CSCF.
- the S-CSCF device may further include a saving module 804, configured to save the identifier of the called UE, the service information of the service provided by the 5GC network slice, and the correspondence between the addresses of the P-CSCF, and then receive the corresponding relationship. When the called service requests, the corresponding relationship is queried, and the address of the corresponding P-CSCF is obtained, so that the received called service request is sent to the P-CSCF.
- the sending module 803 in the S-CFCF is further configured to send, by using a message, the identifier of the called UE, the service information of the service provided by the 5GC network slice, and the address of the P-CSCF to the HSS, so that the HSS can save the
- the corresponding relationship is used to implement backup of the corresponding relationship. Therefore, in the event that the S-CSCF fails, the correspondence can be sent to the reselected S-CSCF to implement fault recovery, thereby ensuring the IMS service.
- FIG. 9 is a schematic diagram of functions of a user equipment according to Embodiment 9 of the present application.
- the user equipment provided in this embodiment of the present application includes:
- the information obtaining module 901 is configured to obtain service information of a service provided by the 5GC network slice and an address of the proxy call session control function device P-CSCF in the IMS network;
- the registration module 902 is configured to send a registration message to the P-CSCF according to the address, where the registration message carries service information of a service provided by the 5GC network slice.
- the registration module 802 can carry the service information in a header field of the registration message.
- the user equipment provided by the embodiment of the present application may be used in the foregoing method embodiment, and the method step of the user equipment side in the method embodiment is completed by the cooperation between the information acquiring module 901 and the registration module 902.
- the information acquiring module 901 and the registration module 902 in this embodiment may further implement other functions of the user equipment in the foregoing method embodiments, and details are not described herein.
- the user equipment provided by this embodiment has the same beneficial effects as the foregoing method embodiments when performing the above communication process.
- the step of the information acquiring module 901 acquiring the service information of the service provided by the 5GC network slice may include: the information acquiring module 901 attaching to the 5G core network slice in the user equipment (5GC network) When sliced, the service information of the service provided by the 5GC network slice is obtained from a 5G core network slice (for example, AMF).
- a 5G core network slice for example, AMF
- the information acquiring module 901 acquiring the address of the proxy call session control function device P-CSCF in the IMS network includes: the information acquiring module 901, when the user equipment establishes a PDU session with the 5G core network slice, from the 5G A core network slice (e.g., AMF) obtains the address of the proxy call session control function device P-CSCF in the IMS network.
- the 5G A core network slice e.g., AMF
- the S-CSCF and the user equipment in the foregoing Embodiments 8 and 9 are all presented in the form of functional modules, where the “module” may refer to a specific application integrated circuit, a processor executing one or more software or firmware programs. And memory, integrated logic, and/or other devices that provide the above functionality.
- the S-CSCF and the user equipment in this embodiment can also be implemented by using the hardware forms shown in FIG. 5 and FIG. 6, respectively.
- the functions implemented by the receiving module 801, the determining module 802, and the transmitting module 803 in the S-CSCF can be implemented by the processor 601 and the memory 602 in FIG.
- the receiving module 801 receiving the called service request sent by the query call session control function device I-CSCF can be implemented by the processor 601 executing the code stored in the memory 602.
- the functions implemented by the information acquisition module 901 and the registration module 902 in the user equipment can be implemented by the processor 701 and the memory 702 in FIG.
- the step of the information acquisition module 901 acquiring the service information of the service provided by the 5GC network slice and the address of the proxy call session control function device P-CSCF in the IMS network may be implemented by the processor 701 executing the code stored in the memory 702. .
- the processor for implementing the foregoing user equipment and the home subscriber server may be a central processing unit, a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a transistor logic device, Hardware components or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
- the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations and the like.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Computer Security & Cryptography (AREA)
- Databases & Information Systems (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
Abstract
在实施例提供了一种IMS网络中的业务请求处理、相关设备和通信***。在本实施例中,由于5GC网络切片对应不同的业务,因而IMS中的P-CSCF也是与不同的业务信息对应的,第一S-CSCF在接收到I-CSCF发送的被叫业务请求后,可以根据其中携带的叫业务的信息来获取对应的P-CSCF的地址,从而第一S-CSCF向与该地址对应的P-CSCF发送该被叫业务请求,由该P-CSCF对该被叫业务请求进行处理。本实施例解决了UE通过不同的5GC网络切片接入到IMS后,IMS中的S-CSCF如何将针对UE的被叫业务请求发送到对应的P-CSCF进行处理的技术问题。
Description
本申请要求于2017年12月29日提交中国国家知识产权局、申请号为201711489721.3、发明名称为“业务请求处理方法、装置及通信***”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
本发明涉及通信技术领域,具体而言涉及一种业务请求处理方法、相关装置及通信***。
第五代(5th generation,5G)网络是网络运营商希望部署的下一代网络,其具有高速率,低延时的特性。网络切片(slice)是5G网络提供的特性之一,其可以通过对5G网络分出不同的网络切片来满足不同的业务需求。用户设备(User Equipment,UE)可以根据不同的业务需求选择对应的5G核心网切片(简称5GC网络切片或5GC切片)并发起不同的业务。
IP多媒体子***(IP multimedia sub-system)IMS网络中的业务呼叫会话控制功能设备(service-call session control function,S-CSCF)主要用于在接收到针对UE的被叫业务请求后,将该被叫业务请求路由到UE当前注册的IMS***中的代理呼叫会话控制功能设备(proxy-call session control function,P-CSCF),进而P-CSCF可以将该被叫业务请求发送给UE进行处理。
但是,UE通过不同的5GC网络切片接入IMS时,其通过不同的P-CSCF分别在IMS网络中进行了多次注册,每次注册对应一个5GC网络切片。在注册成功后,用户可以在不同的5GC网络切片发起不同的IMS业务。但是,现有技术没有解决UE通过不同的5GC网络切片接入到IMS后,IMS中的S-CSCF如何将针对UE的被叫业务请求发送到对应的P-CSCF进行处理的技术问题。
发明内容
本申请实施例提供了一种可以在5GC网络切片的情况下,将UE的被叫业务请求发送到对应的P-CSCF进行处理的方法,相关装置和***。
在一方面,本申请实施例提供一种被叫业务请求的处理方法,应用于IMS***中的第一S-CSCF,其包括如下的步骤:
接收查询呼叫会话控制功能设备(interrogating-call session control function,I-CSCF)发送的被叫业务请求,所述被叫业务请求中携带被叫业务的信息;
确定与所述被叫业务的信息对应的P-CSCF的地址,然后向所述P-CSCF发送所述被叫业务请求。
在本实施例中,由于5GC网络切片对应不同的业务,因而IMS中的P-CSCF也是与不同的业务信息对应的,第一S-CSCF在接收到I-CSCF发送的被叫业务请求后,可以根据其中携带的叫业务的信息来获取对应的P-CSCF的地址,从而第一S-CSCF向与该地址对应的P-CSCF发送该被叫业务请求,由该P-CSCF对该被叫业务请求进行处理。本实施例解决了UE通过不同的5GC网络切片接入到IMS后,IMS中的S-CSCF如何将针对UE的被叫业务请求发送到对应的P-CSCF进行处理的技术问题。
在一个可能的方案中,被叫业务请求中还携带了被叫用户设备UE的标识,此时第一S-CSCF确定与所述被叫业务的信息和所述被叫UE的标识对应的代理呼叫会话控制功能设备P-CSCF的地址,并向所述P-CSCF发送所述被叫业务请求。上述方案可以应用于一个5GC网络切片中包括多个P-CSCF的场景。此时,不同的UE在5GC中不同的P-CSCF中注册。
在一个可能的方案中,第一S-CSCF确定与被叫业务的信息和所述被叫UE的标识对应的P-CSCF的地址包括:第一S-CSCF可以向归属用户服务器HSS发送查询请求消息,用于查询与所述被叫UE的标识和被叫业务的信息对应的P-CSCF的地址,所述查询请求消息中携带所述被叫UE的标识和被叫业务的信息;然后从该HSS接收查询响应消息,所述查询响应消息中携带与所述被叫UE的标识和被叫业务的信息对应的P-CSCF的地址。在方案中,第一S-CSCF通过向HSS发送查询请求消息来确定与所述被叫业务的信息和所述被叫UE的标识对应的代理呼叫会话控制功能设备P-CSCF的地址,从而在第一S-CSCF本地无被叫UE相关数据的情况下(例如在UE初始注册的S-CSCF故障后,该第一S-CSCF为重新选定的S-CSCF),可以向HSS获取对应的P-CSCF的地址,进而可以将被叫业务请求发送到该P-CSCF,继续IMS被叫业务。
在一个可选的方案中,第一S-CSCF确定与被叫业务请求中的业务信息和所述被叫UE的标识对应的P-CSCF的地址还可以包括:查询本地对应关系中与所述被叫业务请求中的业务信息和所述被叫UE的标识对应的P-CSCF的地址。
在一个可选的方案中,S-CSCF可以在接收到被叫业务请求后,判断本地有没有被叫UE的数据,如果有,则在本地查询该对应关系获得P-CSCF的地址,如果没有,则向HSS查询P-CSCF的地址。
在一个可选的方案中,在第一S-CSCF接收I-CSCF发送的被叫业务请求之前,第一S-CSCF还可以接收I-CSCF发送的所述被叫UE的注册消息,所述注册消息中携带所述被叫UE的标识、5G核心网网络切片提供的业务的业务信息和所述P-CSCF的地址,然后第一S-CFCF在本地保存所述被叫UE的标识、5G核心网网络切片提供的业务的业务信息和所述P-CSCF的地址之间的对应关系。进而,第一S-CSCF在接收到被叫业务请求后,可以查询该对应关系,将UE的被叫业务请求发送到对应的P-CSCF进行业务处理。
在一个可选的方案中,第一S-CSCF还向所述HSS发送所述被叫UE的标识、5G核心网网络切片提供的业务的业务信息和所述P-CSCF的地址。本方案可以使得HSS保存该对应关系,实现对该对应关系的备份。从而在第一S-CSCF发生故障的情况下,可以将该对应关系发送给重新选择的S-CSCF,实现故障恢复,从而保证IMS业务的继续。
在一个可选的方案中,上述第一S-CSCF是为UE提供服务的S-CSCF,其可以为UE初始注册的S-CSCF,还可以为初始注册的S-CSCF故障后,IMS网络重新选择的S-CSCF。
在一个可选的方案中,在第一S-CSCF接收I-CSCF发送的被叫业务请求之前,I-CSCF会接收到外部网络(IMS网络以外的)发送的被叫业务请求,确定所述被叫业务请求中的被叫UE注册的初始S-CSCF故障,然后向第一S-CSCF发送所述被叫业务请求,触发第一S-CSCF对该被叫业务请求进行处理。在本方案中,为区分UE注册的初始S-CSCF,第一S-CSCF是当前为UE服务的,其没有发生故障。
第二方面,本申请提供一种业务呼叫会话控制功能设备,其包括接收模块、确定模块和发送模块。其中,接收模块主要用于接收查询呼叫会话控制功能设备I-CSCF发送的被叫业务请求,所述被叫业务请求中携带被叫用户设备UE的标识和被叫业务的信息;确定模块,主 要用于确定与所述被叫业务的信息和所述被叫UE的标识对应的代理呼叫会话控制功能设备P-CSCF的地址;发送模块,主要用于向所述P-CSCF发送所述被叫业务请求。
在一个可选的方案中,S-CSCF中的确定模块包括:
发送子模块,用于向归属用户服务器HSS发送查询请求消息,用于查询与所述被叫UE的标识和被叫业务的信息对应的P-CSCF的地址,所述查询请求消息中携带所述被叫UE的标识和被叫业务的信息;
接收子模块,用于接收所述HSS返回的查询响应消息,所述查询响应消息中携带与所述被叫UE的标识和被叫业务的信息对应的P-CSCF的地址。
在一个可选的方案中,S-CSCF中确定模块确定与被叫业务请求中的业务信息和所述被叫UE的标识对应的P-CSCF的地址包括:查询本地对应关系中与所述被叫业务请求中的业务信息和所述被叫UE的标识对应的P-CSCF的地址。
在一个可选的方案中,S-CSCF中的接收模块还在接收I-CSCF发送的被叫业务请求之前,接收所述I-CSCF发送的所述被叫UE的注册消息,所述注册消息中携带所述被叫UE的标识、5G核心网网络切片提供的业务的业务信息和P-CSCF的地址。进而S-CSCF还包括保存模块,用于保存所述被叫UE的标识、5G核心网网络切片提供的业务的业务信息和所述P-CSCF的地址之间的对应关系。
在一个可选的方案中,S-CSCF中的发送模块还用于向所述HSS发送所述被叫UE的标识和所述P-CSCF的地址。
第三方面,本申请提供一种通信***,其主要包括:第一业务呼叫会话控制功能实体S-CSCF、查询呼叫会话控制功能设备I-CSCF和代理呼叫会话控制功能设备P-CSCF。
上述第一S-CSCF用于接收所述I-CSCF发送的被叫业务请求,所述被叫业务请求中携带被叫用户设备UE的标识和被叫业务的信息,确定与所述被叫业务的信息和所述被叫UE的标识对应的P-CSCF的地址,向所述P-CSCF发送所述被叫业务请求。
在一个可选的方案中,所述通信***还包括归属用户服务器HSS,所述第一S-CSCF确定与被叫业务请求中的业务信息和所述被叫UE的标识对应的P-CSCF的地址包括:向所述HSS发送查询请求消息,用于查询与所述被叫UE的标识和被叫业务的信息对应的P-CSCF的地址,所述查询请求消息中携带所述被叫UE的标识和被叫业务的信息,接收所述HSS发送的查询响应消息,所述查询响应消息中携带与所述被叫UE的标识和被叫业务的信息对应的P-CSCF的地址。
在一个可选的方案中,通信***中的第一S-CSCF还在接收I-CSCF发送的被叫业务请求之前,接收所述I-CSCF发送的所述被叫UE的注册消息,所述注册消息中携带所述被叫UE的标识和所述P-CSCF的地址,保存所述被叫UE的标识和所述P-CSCF的地址之间的对应关系。
在一个可选的方案中,通信***中的I-CSCF还用于接收所述被叫业务请求,确定所述被叫业务请求中的被叫UE注册的初始S-CSCF故障;向所述第一S-CSCF发送所述被叫业务请求。
在一个可选的方案中,通信***中的第一S-CSCF还可以向所述HSS发送所述被叫UE的标识、5GC网络切片提供的业务的业务信息和所述P-CSCF的地址。
第四方面,本申请还提供一种被叫业务请求的处理方法,其可以由归属用户服务器HSS来实现,包括:
归属用户服务器HSS接收第一S-CSCF发送的查询请求消息,所述查询请求消息中携带被叫业务请求中的被叫UE的标识和被叫业务请求中的被叫业务的信息,然后HSS确定与所述被叫UE的标识和被叫业务的信息对应的P-CSCF的地址,并向第一S-CSCF发送查询响应消息,所述查询响应消息中携带所述P-CSCF的地址。
在本申请提供的实施例中,HSS可以在第一S-CSCF向其发送查询请求消息时,将本地保存的发送给第一S-CSCF,从而第一S-CSCF可以根据该对应关系将被叫业务请求发送到对应的P-CSCF进行处理,实现IMS业务。
在一个可选的方案中,HSS在接收第一S-CSCF发送的查询请求消息之前,还包括:接收S-CSCF发送的被叫UE的标识、5GC网络切片提供的业务的业务信息和所述被叫UE注册的P-CSCF的地址,保存所述被叫UE的标识、5GC网络切片提供的业务的业务信息和所述被叫UE注册的P-CSCF的地址之间的对应关系,便于后续查询该对应关系。
第五方面,本申请提供一种用户设备的注册方法,其应用于用户设备UE,主要包括:UE先获取5G核心网切片提供的业务的业务信息和IMS网络中的代理呼叫会话控制功能设备P-CSCF的地址,然后根据所述地址向所述P-CSCF发送注册消息,所述注册消息中携带所述5G核心网切片提供的业务的业务信息或所述5G核心网切片的标识。由于UE发送的注册消息会被IMS网络中的P-CSCF发到S-CSCF,并由S-CSCF发送到HSS,从而S-CSCF和HSS可以均存储该5GC网络切片提供的业务的业务信息与该IMS网络中的P-CSCF之间的对应关系,与上述的第一方面对应,便于S-CSCF后续查询与业务信息对应的P-CSCF,以解决5GC网络切片场景下的入局业务请求路由错误的技术问题。
在一个可能的方案中,所述UE获取所述5G核心网切片提供的业务的业务信息包括:UE在附着到所述5G核心网切片时,从5G核心网(例如AMF)获取所述5G核心网切片提供的业务的业务信息。
在一个可能的方案中,所述用户设备UE在注册消息的头域中携带所述业务信息。
在一个可能的方案中,UE获取IMS网络中的代理呼叫会话控制功能设备P-CSCF的地址包括:UE在与所述5G核心网切片建立PDU会话时,从所述5G核心网切片(例如AMF)获取所述IMS网络中的代理呼叫会话控制功能设备P-CSCF的地址。
一个可选的方案,用户设备可以获取用户发起的业务请求的业务信息,然后向与业务信息对应的P-CSCF发送该业务请求。从而,用户设备可以处理用户主动发起的业务请求,并将其发送到与业务信息对应的P-CSCF进行处理。
第六方面,本申请实施例提供一种S-CSCF,该S-CSCF可以采用通用的计算机来实现。S-CSCF可以包括存储器、处理器、输入输出设备等。其中,存储器中存储了程序代码,处理器可以获取并执行存储器中存储的程序代码,从而使得S-CSCF可以执行上述第一方面提供的通信方法,具体执行过程参见上述第一方面。
第七方面,本申请实施例提供一种HSS,该HSS可以采用通用的计算机来实现。HSS可以包括存储器、处理器、输入输出设备等。其中,存储器中存储了程序代码,处理器可以获取并执行存储器中存储的程序代码,从而使得HSS可以执行上述第四方面提供的通信方法,具体执行过程参见上述第四方面。
在以上任一方面提供的方案中,业务请求可以为邀请消息,UE的标识可以为UE的IP地址,还可以用户的IP多媒体私有标识(IP multimedia private identity,IMPI)或IP多媒体公有标识(IP multimedia public identity,IMPU)。上述查询请求消息具体可以为服务器分配 请求消息,查询响应消息可以为服务器分配响应消息。
图1是本申请实施例一提供的通信***的组网示意图;
图2是本申请实施例二提供的业务请求处理方法的流程图;
图3是本申请实施例三提供的业务请求处理方法的流程图;
图4是本申请实施例四提供的业务请求处理方法的流程图;
图5是本申请实施例五提供的业务请求处理方法的流程图;
图6是本申请实施例六提供的S-CSCF的硬件结构图;
图7是本申请实施例七提供的用户设备的硬件结构图;
图8是本申请实施例八提供的S-CSCF的功能模块示意图;
图9是本申请实施例九提供的用户设备的功能模块示意图。
本申请提供一种业务请求处理方法、相关装置及***,参见图1,图1是本实施例一提供的通信***的组网示意图。
如图1所示,本实施例提供的通信***包括用户设备(user equipment,UE)和网络侧设备。网络侧设备可以包括对接入5G网络的用户设备进行移动性管理、用户面控制等的5G核心网(5G core network,5GC)以及对用户设备提供IMS业务的IMS网络。
其中,5GC可以进行网络切片。例如5GC被切为5GC1和5GC2。5GC进行切片的原则可以包括业务类型、用户类型、用户级别、号码段等,本申请实施例对此不作限定。不同的5GC网络切片(也可以简称为5G网络切片或5GC切片)可以提供不同的业务,例如5GC1提供语音呼叫业务,5GC2提供公共安全集群业务。
5GC中的设备包括对UE进行接入和移动性管理的接入和移动性管理功能设备(access and mobility management function,AMF)、对UE的会话进行管理的会话管理功能设备(session management function,SMF)、对UE的用户面进行控制的用户面功能设备(user plane function,UPF)。此外,5GC中还包括其他设备,例如,进行策略控制功能的设备,本实施例对此不作限定。
IMS中的设备可以包括代理呼叫会话控制功能设备1(proxy-call session control function,P-CSCF1)和代理呼叫会话控制功能设备2(P-CSCF2)、业务呼叫会话控制功能设备(service-call session control function,S-CSCF)、查询呼叫会话控制功能设备(interrogating-call session control function,I-CSCF)、应用服务器(application service,AS)以及归属用户服务器(home subscriber server,HSS)。其中,P-CSCF1接入5GC1,P-CSCF2接入5GC2。HSS主要用于存储用户的开户数据,其功能也可以由统一设备管理(unified device management,UDM)设备来实现。
在UE开机后,UE可以接入5GC1和5GC2,获得两个IP地址(IP1和IP2),IP1对应5GC1,IP2对应5GC2。UE还在5GC1和5GC2分别建立分组数据单元(packet data unit,PDU)会话。在建立PDU会话的过程中,UE分别从5GC1、5GC2获取到IMS中的P-CSCF1的地址和P-CSCF2的地址。此后,UE使用IP1向P-CSCF1发起IMS注册,使用IP2向P-CSCF2发起IMS注册。在注册完成后,UE可以分别在这两个5GC网络切片发起IMS业务,例如 UE在5GC1发起虚拟现实(virtual reality,VR)业务或公共安全集群业务,在5GC2发起语音呼叫业务或增强现实(augmented reality,AR)业务等。
在本实施例中,UE在5GC1发起IMS注册时,向P-CSCF1发送的注册消息(register)中携带了5GC1提供的业务的业务信息1(或简称被叫业务的信息,例如业务类型或业务标识),然后通过P-CSCF1将业务信息1发送给S-CSCF,从而S-CSCF可以保存该业务信息1与P-CSCF1的对应关系。同样的,UE在5GC2发起IMS注册时,同样携带5GC2提供的业务的业务信息2,S-CSCF同样保存业务信息2与P-CSCF2的对应关系。进而,在后续IMS网络中的S-CSCF接收到被叫(或称入局)业务请求时,S-CSCF可以根据被叫业务请求(也可以称为被叫业务请求消息)中的业务信息确定对应的P-CSCF,进而将被叫业务请求发送到对应的P-CSCF,由P-CSCF将被叫业务请求发送到UE进行处理。
在本实施例中,由于5G网络切片对应不同的业务,因而对应的IMS中的P-CSCF也是与不同的业务信息对应的,S-CSCF在接收到I-CSCF发送的被叫业务请求后,可以根据其中携带的被叫业务的信息来获取与该信息对应的P-CSCF的地址,从而S-CSCF向与该地址对应的P-CSCF发送该被叫业务请求。本实施例解决了UE通过不同的5G网络切片接入到IMS后,IMS中的S-CSCF如何将针对UE的被叫业务请求发送到对应的P-CSCF进行处理的技术问题,避免了业务请求被路由到错误的P-CSCF而导致IMS业务失败的情况,提高了通信***的稳定性和效率。
基于上述通信***,本实施例提供一种被叫业务请求的处理方法。参考图2,图2是本申请实施例二提供的被叫业务请求处理方法的实现流程图。
在本实施例提供的通信方法中,IMS网络中的I-CSCF接收到针对用户设备的入局的被叫业务请求,I-CSCF向S-CSCF(对应与发明内容中的第一S-CSCF)发送该被叫业务请求,S-CSCF可以执行以下步骤:
步骤201、S-CSCF接收I-CSCF发送的被叫业务请求,所述被叫业务请求中携带被叫UE的标识和被叫业务的信息。
其中,S-CSCF可以通过Mw接口接收I-CSCF发送的被叫业务请求,该请求中携带被叫UE的标识和被叫业务的信息。
其中,UE的标识可以是UE的地址,例如UE的IP地址、会话初始化协议地址、国际移动设备识别码(International Mobile Equipment Identity,IMEI)、物理地址等,还可以为被叫用户的标识,例如IP多媒体私有标识(IP multimedia private identity,IMPI)或IP多媒体公共标识(IP multimedia public identity,IMPU),移动台综合业务数字网号码(mobile station international Integrated Services Digital Network number,MSISDN)。因此,UE的标识在本申请提供的所有实施例中,其可能为不同的表现形式,但都可以用于标识这个UE。这些可能的替换都包括在本申请的实施例中。例如,步骤201中的UE的标识可以为UE的会话初始化协议地址。UE发送的注册消息中携带的标识可以为IMPU或UE在5G网络中的IP地址。
此外,本申请所有实施例中的UE的标识可以为复数,即可以是多个具体的标识,例如被叫业务请求中可以携带UE的SIP地址和MSISDN号码。
此外,被叫业务的信息可以为业务类型或业务标识。
步骤202、S-CSCF确定与被叫业务请求中的业务信息和所述被叫UE的标识对应的P-CSCF的地址。
其中,S-CSCF可以在本地保存5GC网络切片提供的业务的业务信息、被叫UE的标识与被叫UE注册的P-CSCF的地址三者之间的对应关系,进而在接收到被叫业务请求后,在本地查询该对应关系,获得与被叫业务请求中携带的业务信息和所述被叫UE的标识对应的P-CSCF的地址。被叫业务请求中携带的业务信息也可以简称为被叫业务的信息。由于不同的5GC网络切片对应不同的P-CSCF,因而被叫UE注册的P-CSCF可以称为5GC网络切片对应的P-CSCF。
此外,S-CSCF还可以向IMS网络中的其他设备,例如HSS,查询与被叫业务请求中的业务信息和所述被叫UE的标识对应的P-CSCF的地址。
在本实施例中,S-CSCF可以在接收到被叫业务请求后,判断本地有没有被叫UE的数据,如果有,则在本地查询该对应关系获得P-CSCF的地址,如果没有,则向HSS查询P-CSCF的地址。
步骤203、S-CSCF向P-CSCF发送所述被叫业务请求。
在本实施例中,由于S-CSCF获取了与被叫业务请求中的业务信息和UE的标识对应的P-CSCF的地址,因而可以向对应的P-CSCF发送被叫业务请求,从而P-CSCF对该业务请求进行处理,实现了在5GC切片场景下的被叫业务请求的处理。
在本实施例中,S-CSCF可以在被叫用户设备UE在5GC网络切片中发起IMS注册时,接收I-CSCF发送的UE的注册(register)消息,该注册消息的头域中携带该被叫UE的标识、5GC网络切片提供的业务的业务信息和P-CSCF的地址,从而S-CSCF保存被叫UE的标识、5GC网络切片提供的业务的业务信息和所述P-CSCF的地址之间的对应关系,便于后续根据该对应关系查询与业务信息对应的P-CSCF的地址。
参考图3,图3是本申请实施例三提供的用户设备注册方法的实现流程图。
本申请实施例提供的IMS注册方法主要用于用户设备,该方法包括:
步骤301、UE获取5GC网络切片提供的业务的业务信息和IMS网络中的代理呼叫会话控制功能设备P-CSCF的地址。
其中,用户设备可以在附着到5GC网络切片时,从5G核心网(例如AMF)获得5GC网络切片提供的业务的业务信息。此外。UE还可以在附着到5GC网络切片后,和5GC网络切片建立PDU会话,并在建立PDU会话的过程中从5GC获取到5GC网络切片对应的P-CSCF的地址。
由于用户设备可以附着到多个5GC网络切片,因而UE本地可以保存多个5GC网络切片提供的业务的业务信息与该5GC网络切片对应的P-CSCF的地址之间的对应关系。
步骤302、UE根据所述地址向所述P-CSCF发送注册消息,注册消息中携带所述5GC网络切片提供的业务的业务信息或所述5GC网络切片的标识。
其中,UE可以生成注册消息(也可以称为注册请求),然后通过5GC1向IMS网络中的P-CSCF发送注册消息,其中携带5GC网络切片提供的业务的业务信息。此外,该注册消息中还可以携带UE在5GC网络切片中的IP地址。在本实施例中,由于5GC网络切片与5GC网络切片提供的业务是对应的,因而注册消息中的5GC网络切片提供的业务的业务信息也可以为5GC网络切片的标识,进而IMS网络中的P-CSCF或S-CSCF在接收到携带5GC网络切片的标识的注册消息后,可以将其关联到5GC网络切片提供的业务的业务信息。
此外,UE发送的注册消息中还可以携带UE的标识,例如终端的IP地址和/或IMPU。
在本实施例中,UE向P-CSCF发送携带5GC网络切片提供的业务的业务信息的注册消息后,P-CSCF可以向IMS网络中的S-CSCF发送该注册消息,从而S-CSCF可以保存该业务信息、UE的标识、与该P-CSCF三者之间的对应关系,便于后续查询到与业务信息对应的P-CSCF的地址,从而将入局的业务请求路由到与业务信息对应的P-CSCF进处理,继续IMS业务处理。
进一步的,UE通过5GC1完成IMS注册后,还可以通过5GC2完成第二次IMS注册。随后,UE可以在5GC1或5GC2发起业务,相关的业务请求通过5GC发送到P-CSCF,然后由P-CSCF向IMS网络中的S-CSCF进行转发。例如,UE在5GC1中发起AR/VR等低时延业务。UE在5GC2发起关键任务一键通(mission-critical push-to-talk,MCPTT)等公共安全集群业务。
为更详细的理解本申请,出本申请实施例还提供一种业务处理方法的实现流程。参考图4,本申请实施例四提供的业务处理方法具体包括如下步骤:
步骤401、UE获取IMS网络中的代理呼叫会话控制功能设备P-CSCF的地址和5GC网络切片提供的业务的业务信息。
在本实施例中,业务信息可以为业务类型或业务标识,业务类型可以包括低时延业务(例如增强现实AR,VR业务),语音通话业务,短消息,公共安全集群业务等,业务标识可以为应用APP的标识。需要说明的是,5GC网络切片提供的业务通常也是UE能够发起或接收到的业务,因此5GC网络切片提供的业务的业务信息也可以称为UE的业务信息。此外,5GC网络切片提供的业务可以和IMS网络提供的业务相同,例如语音业务需要5GC网络切片和IMS网络同时提供支持。
UE可以在附着到5GC的时候,5GC下发网络支持的所有5GC网络切片的切片ID给UE,然后UE根据其能力或业务信息选择不同的5GC网络切片。或者,也可由5GC来指定UE需要选择的5GC网络切片。不同的5GC网络切片为UE提供了不同的IP地址。在本实施例中,5GC网络存在两个切片,即5GC1和5GC2。5GC1为UE提供的地址为IP1,5GC2为UE提供的地址为IP2。
在本实施例中,不同的5GC网络切片可以提供了不同的业务,UE可以同时选择两个5GC网络切片附着,并在本地建立5GC切片网络提供的业务的业务信息与5GC网络切片之间的对应关系。
在本实施例中,UE可以在和5GC网络切片建立PDU会话的过程中从5GC获取到IMS网络中的P-CSCF1的地址。具体的,UE可以从5GC中的AMF或SMF获取到IMS网络中的P-CSCF1的地址。
此外,UE还可以通过本地配置的方式从本地获取P-CSCF1的地址,例如IMS网络中的P-CSCF的地址和5GC网络切片提供的业务的业务信息都配置在UE的用户识别模块(subscriber identity module,SIM)中,UE可以从本地获取上述P-CSCF的地址和业务信息。上述UE获取P-CSCF地址的过程也可以称为P-CSCF发现。
步骤402、UE根据P-CSCF1的地址向P-CSCF1发送注册消息,所述注册消息中携带所述IMS网络提供的业务的业务信息。
本实施例以UE在5GC网络切片5GC1中发起IMS注册(向P-CSCF1发起注册)为例,该过程与UE在5GC网络切片5GC2中发起注册的过程相同。在本实施例中,UE可以使用 一个IP多媒体私有标识(IP multimedia private identity,IMPI)和一个IP多媒体公有标识(IP multimedia public identity,IMPU)对在两个5GC网络切片发起IMS注册。UE也可以使用不同的IMPI和IMPU对分别在两个5GC网络切片发起IMS注册。
在本实施例中,UE可以在本地构造基于会话初始化协议(session initial protocol,SIP)的注册(register)消息,其中携带5GC网络切片5GC1提供的业务的业务信息。此外,还可以携带UE的标识。UE的标识除了之前提到的可能外,还可以为UE在5GC1中的IP地址(即IP1)。该注册消息通过5GC1发送到P-CSCF1,继续IMS注册流程。
步骤403、P-CSCF1向S-CSCF1发送接收到的注册消息。
其中,P-CSCF1可以通过Mw接口向S-CSCF1发送该接收到的注册消息,P-CSCF1发送的注册消息中携带P-CSCF1的地址、UE的IP地址和5GC网络切片提供的业务的业务信息。需要说明的是,P-CSCF接收到的注册消息中携带的UE的IP地址(UE在5GC1中的IP地址)和P-CSCF发送的注册消息中携带的UE的IP地址有可能不同,即P-CSCF可以对接收到的注册消息中携带的UE的IP地址进行转换,从而P-CSCF向S-CSCF1发送的注册消息中携带转换后的地址(例如可以为SIP地址)。UE在5GC1中的IP地址和上述转换后的地址之间存在对应关系。为叙述方便,本实施例对P-CSCF接收到的注册消息中携带的UE的IP地址和P-CSCF向S-CSCF1发送的注册消息中携带的UE的地址统称为UE的标识。
步骤404、S-CSCF1向HSS发送注册消息中携带的5GC网络切片提供的业务的业务信息、P-CSCF1的地址和UE的标识。
其中,S-CSCF1可以向HSS发送消息(具体可以为服务器分配请求(server assignment request,SAR)消息),该消息中携带所述5GC网络切片提供的业务的业务信息、UE的标识和所述P-CSCF1的地址(例如IP地址)。
此外,S-CSCF1本地也可以保存所述5GC网络切片5GC1提供的业务的业务信息、UE的标识和P-CSCF1的地址之间的对应关系。
步骤405、HSS保存所述5GC网络切片5GC1提供的业务的业务信息、UE的标识和P-CSCF1的地址的对应关系。
其中,HSS可以保存接收到的对应关系,便于后续HSS根据该对应关系查询P-CSCF1的地址。此外,HSS还可以保存UE与S-CSCF1的地址或名称(name)之间的对应关系,便于后续查询UE注册的S-CSCF的地址。
在本实施例中,由于通过两个5GC网络切片发起了两次IMS注册。HSS可以保存不同5GC网络切片提供的业务的业务信息、P-CSCF的地址和UE的标识之间的对应关系。例如,S-CSCF1和HSS保存的对应关系可以如下:
UE的IP地址 | P-CSCF的地址 | 业务信息 |
232.02.5.30 | 192.125.6.3 | VR/AR |
232.02.5.31 | 192.125.6.5 | 语音业务 |
其中,上述两组对应关系可以通过UE的IMPU关联起来。
在本实施例中,HSS还可以将UE的注册状态更新为已注册(registered),并向S-CSCF1发送服务器分配响应(server assignment answer,SAA)消息,其中携带所述用户设备在HSS中的订阅信息。然后,S-CSCF1可以向UE发送注册接受消息,通知UE当前IMS网络注册成功。
本实施例提供的通信方法中,UE可以在注册成功后,在5GC1发起VR业务。此外,UE 还可以作为被叫接收入局的业务请求,例如接收其他用户发起的语音呼叫请求。
在本实施例中,上述S-CSCF1也可以称为UE初始注册的S-CSCF,若其发生故障,则S-CSCF1的业务可以由S-CSCF2进行接替。下面详细描述该场景下的业务请求处理方法。
参见图5,本实施例提供的业务请求处理方法还可以包括:
步骤501、I-CSCF接收业务请求。
在本实施例中,IMS网络中的I-CSCF接收到语音呼叫业务请求。语音业务请求可为邀请invite消息,其中携带被叫UE的标识,例如UE的SIP地址或手机号码。
步骤502、I-CSCF向HSS发送位置信息请求,用于查询IMS网络中的S-CSCF的地址。
其中,I-CSCF在接收到业务请求后,向HSS发送位置信息请求(location information request,LIR),用于确定UE注册的S-CSCF。LIR中也可以携带UE的标识,例如UE的IMPI或IMPU。
步骤503、HSS返回位置信息响应(location information answer,LIA),其中携带S-CSCF1的地址或名称。
其中,HSS本地保存了UE注册时的S-CSCF(即S-CSCF1)的标识(例如地址或名称),HSS在本地查询后,通过LIA向I-CSCF返回S-CSCF1的标识。
在本实施例中,I-CSCF确定该S-CSCF1故障,则继续向HSS发送位置信息请求,用于查询IMS网络中的其他S-CSCF的地址。
步骤504、I-CSCF向HSS发送位置信息请求,用于查询IMS网络中的S-CSCF的地址。
步骤505、HSS返回位置信息响应,其中携带备用的S-CSCF2的地址或名称。
在本实施例中,HSS确定UE备用的S-CSCF2,然后通过位置信息响应向I-CSCF发送携带备用的S-CSCF2的地址或名称的响应消息。
步骤506、I-CSCF将接收的业务请求发给与所述位置信息响应中携带的S-CSCF2的地址对应的设备。
在本实施例中,I-CSCF将接收到的业务请求转发给IMS网络中的S-CSCF2,由S-CSCF2进行业务处理。
步骤507、S-CSCF2向HSS发送查询请求消息,其中携带UE的标识。
在本实施例中,由于备份的S-CSCF2确定本地没有存储UE相关的信息,因而向HSS发送查询请求消息,用于获得UE的备份数据。查询请求消息中可以携带UE的标识,例如IMPU。
其中,查询请求消息在本实施例中具体可以为服务器分配请求SAR消息。
步骤508、HSS返回查询响应消息,其中携带之前保存的UE的IP地址、P-CSCF的地址和5GC网络切片提供的业务的业务信息之间的对应关系。
在本实施例中,在上述步骤405中,UE的IP地址、P-CSCF的地址和不同的5GC网络切片提供的业务的业务信息之间的对应关系通过IMPU进行了关联,因而HSS在接收到携带IMPU的查询请求消息后,可以获得之前保存的对应关系,并通过查询响应消息发给S-CSCF2。
其中,查询响应消息在本实施例中具体可以为服务器分配响应(server assignment answer,SAA)消息。
步骤509、S-CSCF2向P-CSCF1发送业务请求。
在本实施例中,由于该业务请求为语音业务请求,因此S-CSCF2根据UE的标识(IMPU)和业务信息(语音业务)查询上述对应关系表,获得UE的IP地址为232.02.5.31,P-CSCF1的地址为192.125.6.5,然后向192.125.6.5对应的P-CSCF1发送业务请求,实现了针对UE的 入局(被叫)业务请求的处理。
参见图6,图6是本申请实施例六提供的业务呼叫会话控制功能设备S-CSCF的硬件结构图。
其中,S-CSCF可以采用通用的计算机硬件来实现,其包括处理器601、存储器602、总线603、输入设备604、输出设备605以及网络接口606。
具体的,存储器502可以包括以易失性和/或非易失性存储器形式的计算机存储媒体,如只读存储器和/或随机存取存储器。存储器602可以存储操作***、应用程序、其他程序模块、可执行代码、程序数据、用户开户数据、用户订阅数据等。
输入设备604可以用于向S-CSCF输入命令和信息,输入设备604如键盘或指向设备,如鼠标、轨迹球、触摸板、麦克风、操纵杆、游戏垫、***天线、扫描仪或类似设备。这些输入设备可以通过总线603连接至处理器601。
输出设备605可以用于S-CSCF输出信息,除了监视器之外,输出设备605还可以为其他***输出设各,如扬声器和/或打印设备,这些输出设备也可以通过总线603连接到处理器601。
S-CSCF可以通过网络接口606连接到网络中,例如连接到局域网(Local Area Network,LAN)。在联网环境下,S-CSCF中存储的计算机执行指令可以存储在远程存储设备中,而不限于在本地存储。
当S-CSCF中的处理器601执行存储器602中存储的可执行代码或应用程序时,S-CSCF可以执行以上实施例中的S-CSCF一侧的方法步骤,例如执行步骤201-203、507、509等。具体执行过程参见上述实施例,在此不再赘述。
参见图7,图7是本申请实施例七提供的用户设备的结构示意图。
其中,用户设备主要包括处理器7701、存储器702、总线703、输入设备704、输出设备705以及网络接口706。此外,用户设备还可以包括应用处理器(application processor,AP),电池等部件。
具体的,存储器702可以包括以易失性和/或非易失性存储器形式的计算机存储媒体,如只读存储器和/或随机存取存储器。存储器702可以存储操作***、应用程序、其他程序模块、可执行代码和程序数据。
输入设备704可以用于向用户设备输入命令和信息,输入设备704如键盘或指向设备,如鼠标、轨迹球、触摸板、麦克风、操纵杆、游戏垫、圆盆式***天线、扫描仪或类似设备。这些输入设备可以通过总线703连接至处理器701。
输出设备705可以用于用户设备输出信息,除了监视器之外,输出设备705还可以为其他***输出设各,如扬声器,这些输出设备也可以通过总线703连接到处理器701。
用户设备可以通过网络接口706连接到网络中,例如通过无线接口连接到WIFI网络、5G、长期演进(long term evolution,LTE)网络。在联网环境下,用户设备中存储的计算机执行指令可以存储在远程存储设备中,而不限于在本地存储。
当用户设备中的处理器701执行存储器702中存储的可执行代码或应用程序时,用户设备可以执行以上实施例中的用户设备一侧的方法步骤,例如执行步骤301-302、401-402等。具体执行过程和有益效果参见上述相关实施例,在此不再赘述。
参见图8,图8是本申请实施例八提供的业务呼叫会话控制功能设备S-CSCF的功能示意图。
如图所示,本申请实施例提供的业务呼叫会话控制功能设备S-CSCF主要包括接收模块801、确定模块802和发送模块803。
接收模块801,用于接收查询呼叫会话控制功能设备I-CSCF发送的被叫业务请求,所述被叫业务请求中携带被叫用户设备UE的标识和被叫业务的信息;
确定模块802,用于确定与所述被叫业务的信息和所述被叫UE的标识对应的P-CSCF的地址。其中,确定模块802确定与被叫业务的信息和被叫UE的标识对应的P-CSCF的地址可以通过查询本地对应关系中与被叫业务的信息和所述被叫UE的标识对应的P-CSCF的地址来实现。
发送模块803,用于向所述P-CSCF发送所述被叫业务请求。
本申请实施例提供的S-CSCF可以使用在前述方法实施例中,其通过上述的接收模块801、确定模块802以及发送模块803之间的配合来完成上述方法实施例中S-CSCF一侧的方法步骤。与现有技术中的S-CSCF相比,本实施例提供的S-CSCF在执行上述通信流程时,具有与前述方法实施例相同的有益效果。
可选的,S-CSCF中的确定模块802具体可以包括:发送子模块以及接收子模块。其中,发送子模块可以用于向归属用户服务器HSS发送查询请求消息,用于查询与所述被叫UE的标识和被叫业务的信息对应的P-CSCF的地址,所述查询请求消息中携带所述被叫UE的标识和被叫业务的信息;其中的接收子模块可以用于接收所述HSS返回的查询响应消息,所述查询响应消息中携带与所述被叫UE的标识和被叫业务的信息对应的P-CSCF的地址。在本实施例中,S-CSCF通过向HSS发送查询请求消息来确定与所述被叫业务的信息和所述被叫UE的标识对应的代理呼叫会话控制功能设备P-CSCF的地址,从而在S-CSCF本地无被叫UE相关数据的情况下(例如该S-CSCF为初始S-CSCF故障后,重新选定的S-CSCF),可以向HSS获取对应的P-CSCF的地址,进而可以将被叫业务请求发送到该P-CSCF,继续IMS被叫业务。
可选的,S-CSCF中的接收模块801还在接收I-CSCF发送的被叫业务请求之前,接收所述I-CSCF发送的所述被叫UE的注册消息,所述注册消息中携带所述被叫UE的标识、5GC网络切片提供的业务的业务信息和所述P-CSCF的地址。S-CSCF设备还可以包括保存模块804,用于保存所述被叫UE的标识、5GC网络切片提供的业务的业务信息和所述P-CSCF的地址之间的对应关系,进而后续在接收到被叫业务请求时,查询该对应关系,获得对应的P-CSCF的地址,从而向该P-CSCF发送接收到的被叫业务请求。
此外,S-CFCF中的发送模块803还用于通过消息向所述HSS发送所述被叫UE的标识、5GC网络切片提供的业务的业务信息和所述P-CSCF的地址,便于HSS保存该对应关系,实现对该对应关系的备份。从而在S-CSCF发生故障的情况下,可以将该对应关系发送给重新选择的S-CSCF,实现故障恢复,从而保证IMS业务。
参见图9,图9是本申请实施例九提供的用户设备的功能示意图。
如图所示,本申请实施例提供的用户设备包括:
信息获取模块901,用于获取5GC网络切片提供的业务的业务信息和IMS网络中的代理 呼叫会话控制功能设备P-CSCF的地址;
注册模块902,用于根据所述地址向所述P-CSCF发送注册消息,所述注册消息中携带所述5GC网络切片提供的业务的业务信息。其中,注册模块802可以在注册消息的头域中携带所述业务信息。
本申请实施例提供的用户设备可以使用在前述方法实施例中,其通过上述的信息获取模块901和注册模块902之间的配合来完成方法实施例中用户设备一侧的方法步骤。本实施例中的信息获取模块901、注册模块902还可以实现上述方法实施例中用户设备的其他功能,在此不再赘述。
与现有技术中的用户设备相比,本实施例提供的用户设备在执行上述通信流程时,具有与前述方法实施例相同的有益效果。
可选的,在本实施例提供的用户设备中,信息获取模块901获取5GC网络切片提供的业务的业务信息的步骤具体可以包括:信息获取模块901在用户设备附着到5G核心网切片(5GC网络切片)时,从5G核心网切片(例如AMF)获取所述5GC网络切片提供的业务的业务信息。
此外,信息获取模块901获取IMS网络中的代理呼叫会话控制功能设备P-CSCF的地址包括:信息获取模块901在所述用户设备在与所述5G核心网切片建立PDU会话时,从所述5G核心网切片(例如AMF)获得所述IMS网络中的代理呼叫会话控制功能设备P-CSCF的地址。
其中,上述实施例八、九中S-CSCF和用户设备均是以功能模块的形式来呈现的,这里的“模块”可以指特定应用集成电路,执行一个或多个软件或固件程序的处理器和存储器,集成逻辑电路,和/或其他可以提供上述功能的器件。本领域的技术人员可以想到本实施例中的S-CSCF和用户设备也可以分别采用图5、6所示的硬件形式来实现。
例如,S-CSCF中的接收模块801,确定模块802和发送模块803所实现的功能都可以通过图6中的处理器601和存储器602来实现。例如,接收模块801接收查询呼叫会话控制功能设备I-CSCF发送的被叫业务请求可以通过由处理器601来执行存储器602中存储的代码来实现。
用户设备中的信息获取模块901和注册模块902所实现的功能都可以通过图7中的处理器701和存储器702来实现。例如,信息获取模块901获取5GC网络切片提供的业务的业务信息和IMS网络中的代理呼叫会话控制功能设备P-CSCF的地址的步骤可以通过由处理器701来执行存储器702中存储的代码来实现。
此外,用于实现上述用户设备和归属用户服务器的处理器可以是中央处理器,通用处理器、数字信号处理器、专用集成电路,现场可编程门阵列或者其他可编程逻辑器件、晶体管逻辑器件,硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框,模块和电路。所述处理器也可以是实现计算功能的组合,例如包含一个或多个微处理器组合等。
以上所述,仅为本发明的具体实施方式,但本发明的保护范围并不局限于此,任何熟悉本技术领域的技术人员在本发明揭露的技术范围内,可轻易想到变化或替换,都应涵盖在本发明的保护范围之内。因此,本发明的保护范围应所述以权利要求的保护范围为准。
Claims (15)
- 一种业务请求的处理方法,其特征在于,包括:第一业务呼叫会话控制功能实体S-CSCF接收查询呼叫会话控制功能设备I-CSCF发送的被叫业务请求,所述被叫业务请求中携带被叫用户设备UE的标识和被叫业务的信息;所述第一S-CSCF确定与所述被叫业务的信息和所述被叫UE的标识对应的代理呼叫会话控制功能设备P-CSCF的地址;向所述P-CSCF发送所述被叫业务请求。
- 如权利要求1所述的方法,其特征在于,所述确定与被叫业务的信息和所述被叫UE的标识对应的P-CSCF的地址包括:向归属用户服务器HSS发送查询请求消息,用于查询与所述被叫UE的标识和被叫业务的信息对应的P-CSCF的地址,所述查询请求消息中携带所述被叫UE的标识和被叫业务的信息;接收所述HSS发送的查询响应消息,所述查询响应消息中携带与所述被叫UE的标识和被叫业务的信息对应的P-CSCF的地址。
- 如权利要求1所述的方法,其特征在于,所述确定与被叫业务请求中的业务信息和所述被叫UE的标识对应的P-CSCF的地址包括:查询本地对应关系中与所述被叫业务请求中的业务信息和所述被叫UE的标识对应的P-CSCF的地址。
- 如权利要求1所述的方法,其特征在于,在所述接收I-CSCF发送的被叫业务请求之前,所述方法还包括:接收所述I-CSCF发送的所述被叫UE的注册消息,所述注册消息中携带所述被叫UE的标识、5G核心网网络切片提供的业务的业务信息和所述P-CSCF的地址;保存所述被叫UE的标识、5G核心网网络切片提供的业务的业务信息和所述P-CSCF的地址之间的对应关系。
- 如权利要求4所述的方法,其特征在于,还包括:向所述HSS发送所述被叫UE的标识、5G核心网网络切片提供的业务的业务信息和所述P-CSCF的地址。
- 如权利要求1所述的方法,其特征在于,在所述接收I-CSCF发送的被叫业务请求之前,所述方法还包括:所述I-CSCF接收所述被叫业务请求,确定所述被叫业务请求中的被叫UE注册的初始S-CSCF故障;向所述第一S-CSCF发送所述被叫业务请求。
- 一种业务呼叫会话控制功能设备,其特征在于,包括:接收模块,用于接收查询呼叫会话控制功能设备I-CSCF发送的被叫业务请求,所述被叫业务请求中携带被叫用户设备UE的标识和被叫业务的信息;确定模块,用于确定与所述被叫业务的信息和所述被叫UE的标识对应的代理呼叫会话控制功能设备P-CSCF的地址;发送模块,用于向所述P-CSCF发送所述被叫业务请求。
- 如权利要求7所述的设备,其特征在于,所述确定模块包括:发送子模块,用于向归属用户服务器HSS发送查询请求消息,用于查询与所述被叫UE的标识和被叫业务的信息对应的P-CSCF的地址,所述查询请求消息中携带所述被叫UE的标识和被叫业务的信息;接收子模块,用于接收所述HSS返回的查询响应消息,所述查询响应消息中携带与所述被叫UE的标识和被叫业务的信息对应的P-CSCF的地址。
- 如权利要求7所述的设备,其特征在于,所述确定模块确定与被叫业务请求中的业务信息和所述被叫UE的标识对应的P-CSCF的地址包括:查询本地对应关系中与所述被叫业务请求中的业务信息和所述被叫UE的标识对应的P-CSCF的地址。
- 如权利要求7所述的设备,其特征在于,所述接收模块还在接收I-CSCF发送的被叫业务请求之前,接收所述I-CSCF发送的所述被叫UE的注册消息,所述注册消息中携带所述被叫UE的标识、5G核心网网络切片提供的业务的业务信息和述P-CSCF的地址;所述设备还包括保存模块,用于保存所述被叫UE的标识、5G核心网网络切片提供的业务的业务信息和所述P-CSCF的地址之间的对应关系。
- 如权利要求10所述的设备,其特征在于,所述发送模块还用于向所述HSS发送所述被叫UE的标识和所述P-CSCF的地址。
- 一种通信***,其特征在于,包括:第一业务呼叫会话控制功能实体S-CSCF、查询呼叫会话控制功能设备I-CSCF和代理呼叫会话控制功能设备P-CSCF;所述第一S-CSCF用于接收所述I-CSCF发送的被叫业务请求,所述被叫业务请求中携带被叫用户设备UE的标识和被叫业务的信息,确定与所述被叫业务的信息和所述被叫UE的标识对应的P-CSCF的地址,向所述P-CSCF发送所述被叫业务请求。
- 如权利要求12所述的***,其特征在于,所述***还包括归属用户服务器HSS,所述第一S-CSCF确定与被叫业务请求中的业务信息和所述被叫UE的标识对应的P-CSCF的地址包括:向所述HSS发送查询请求消息,用于查询与所述被叫UE的标识和被叫业务的信息对应的P-CSCF的地址,所述查询请求消息中携带所述被叫UE的标识和被叫业务的信息,接收所述HSS发送的查询响应消息,所述查询响应消息中携带与所述被叫UE的标识和被叫业务的信息对应的P-CSCF的地址。
- 如权利要求12所述的***,其特征在于,所述第一S-CSCF还在接收I-CSCF发送的被叫业务请求之前,接收所述I-CSCF发送的所述被叫UE的注册消息,所述注册消息中携带所述被叫UE的标识和所述P-CSCF的地址,保存所述被叫UE的标识和所述P-CSCF的地址之间的对应关系。
- 如权利要求12所述的***,其特征在于,所述I-CSCF还用于接收所述被叫业务请求,确定所述被叫业务请求中的被叫UE注册的初始S-CSCF故障;向所述第一S-CSCF发送所述被叫业务请求。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP18895395.4A EP3720187B1 (en) | 2017-12-29 | 2018-12-05 | Service request handling method and device and communication system |
US16/913,531 US11496526B2 (en) | 2017-12-29 | 2020-06-26 | Service request processing method, apparatus, and communications system |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201711489721.3A CN109995721B (zh) | 2017-12-29 | 2017-12-29 | 业务请求处理方法、装置及通信*** |
CN201711489721.3 | 2017-12-29 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/913,531 Continuation US11496526B2 (en) | 2017-12-29 | 2020-06-26 | Service request processing method, apparatus, and communications system |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2019128650A1 true WO2019128650A1 (zh) | 2019-07-04 |
Family
ID=67066513
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2018/119262 WO2019128650A1 (zh) | 2017-12-29 | 2018-12-05 | 业务请求处理方法、装置及通信*** |
Country Status (4)
Country | Link |
---|---|
US (1) | US11496526B2 (zh) |
EP (1) | EP3720187B1 (zh) |
CN (1) | CN109995721B (zh) |
WO (1) | WO2019128650A1 (zh) |
Families Citing this family (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2021000229A1 (en) * | 2019-07-01 | 2021-01-07 | Telefonaktiebolaget Lm Ericsson (Publ) | Network nodes and methods performed therein for handling discovery of entrance points to an ip multimedia subsystem |
CN110248410B (zh) * | 2019-07-18 | 2022-08-26 | 中国联合网络通信集团有限公司 | 一种5g网络下群组通信的无线资源分配方法和*** |
US11122092B2 (en) * | 2019-08-05 | 2021-09-14 | Verizon Patent And Licensing Inc. | System and method for prioritizing SIP registrations |
US20230046490A1 (en) * | 2020-02-04 | 2023-02-16 | Telefonaktiebolaget Lm Ericsson (Publ) | Nodes and methods for handling provision of an ims service in a communications network |
CN113259856A (zh) * | 2020-02-10 | 2021-08-13 | 普天信息技术有限公司 | 一种5g专网通信***及通信方法 |
CN114095923A (zh) * | 2020-07-09 | 2022-02-25 | ***通信有限公司研究院 | 切片访问认证方法、upf、应用服务器、pcf及终端 |
CN114339724B (zh) * | 2020-09-29 | 2023-07-25 | 成都鼎桥通信技术有限公司 | 应用于集群通信***的集群通信方法、***及存储介质 |
US11997748B1 (en) * | 2021-08-24 | 2024-05-28 | T-Mobile Usa, Inc. | Methods and systems for MT call recovery |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060153353A1 (en) * | 2005-01-07 | 2006-07-13 | O'neil Douglas | Intelligent secondary call treatment for advanced calling scenarios |
CN101426261A (zh) * | 2008-12-17 | 2009-05-06 | 华为技术有限公司 | 多媒体子***业务处理的方法、p-cscf、i-cscf和多媒体子*** |
CN101494890A (zh) * | 2006-12-08 | 2009-07-29 | 华为技术有限公司 | 一种路由会话的方法、网络及设备 |
CN102752879A (zh) * | 2012-03-23 | 2012-10-24 | 中兴通讯股份有限公司 | 会话接入方法及装置 |
Family Cites Families (36)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070189215A1 (en) * | 2004-01-07 | 2007-08-16 | Huawei Technologies Co., Ltd. | Method for reducing interface load of home subscriber server |
FI20045298A0 (fi) * | 2004-08-16 | 2004-08-16 | Nokia Corp | Mediapalvelun reititys |
CN1642083A (zh) * | 2004-09-23 | 2005-07-20 | 华为技术有限公司 | 网络侧选择鉴权方式的方法 |
WO2006116939A1 (fr) * | 2005-04-29 | 2006-11-09 | Huawei Technologies Co., Ltd. | Méthode pour réaliser un service de messagerie basé sur un sous-système multimédia en réseau ip |
KR100880992B1 (ko) * | 2005-05-10 | 2009-02-03 | 삼성전자주식회사 | 아이엠에스망과 에이치.323망간 연동 시스템 및 방법 |
KR100758970B1 (ko) * | 2005-11-28 | 2007-09-14 | 한국전자통신연구원 | 아이엠에스 기반 통신 시스템에서의 서비스 등록, 제어와서비스 브로커링 방법 및 그 시스템 |
CN100474854C (zh) * | 2006-01-10 | 2009-04-01 | 华为技术有限公司 | 一种选择被叫接续网络的方法及网络*** |
DE602006004300D1 (de) * | 2006-03-01 | 2009-01-29 | Nokia Siemens Networks Gmbh | Methode zur eigenständigen Bereitstellung von Benutzerdaten in einem IP Multimedia Subsystem (IMS) |
DE602006014032D1 (de) * | 2006-10-16 | 2010-06-10 | Ericsson Telefon Ab L M | Mobilität für ims-benutzer |
US8929360B2 (en) * | 2006-12-07 | 2015-01-06 | Cisco Technology, Inc. | Systems, methods, media, and means for hiding network topology |
RU2474067C2 (ru) * | 2007-02-22 | 2013-01-27 | Телефонактиеболагет Лм Эрикссон (Пабл) | Групповой доступ к услугам мультимедийной подсистемы на базе ip-протокола |
US7936683B2 (en) * | 2007-06-20 | 2011-05-03 | At&T Intellectual Property I, L.P. | System and method of monitoring network performance |
US8401169B2 (en) * | 2007-12-19 | 2013-03-19 | At&T Intellectual Property I, L.P. | System and method of delivering ringback audio content |
CN101911635B (zh) * | 2007-12-27 | 2014-05-28 | 阿尔卡特朗讯 | 用于在电信网络中向未注册或不可用的用户提供呼叫完成服务的方法 |
CN101471797B (zh) * | 2008-03-31 | 2012-05-30 | 华为技术有限公司 | 决策方法及***和策略决策单元 |
US9184940B2 (en) * | 2008-12-12 | 2015-11-10 | At&T Intellectual Property I, L.P. | Method and apparatus for completing a circuit switched service call in an internet protocol network |
US8812700B2 (en) * | 2008-12-12 | 2014-08-19 | At&T Intellectual Property I, L.P. | Method and apparatus for providing network based services to non-registering endpoints |
US8369313B2 (en) * | 2008-12-17 | 2013-02-05 | At&T Intellectual Property I, L.P. | IMS and method of multiple S-CSCF operation in support of single PUID |
CN101931900B (zh) * | 2009-06-26 | 2014-03-19 | 中兴通讯股份有限公司 | 一种ip多媒体子***网络的业务实现方法及*** |
CN101931901A (zh) * | 2009-06-26 | 2010-12-29 | 中兴通讯股份有限公司 | 一种ip多媒体子***网络的业务实现方法及*** |
WO2011038554A1 (en) * | 2009-09-30 | 2011-04-07 | Alcatel Lucent | Online charging in ims networks for sessions handed over between different operator networks |
CN102104862B (zh) * | 2009-12-22 | 2014-03-12 | 华为技术有限公司 | 一种电路域cs锚定ip多媒体子***的方法、装置和*** |
US20110161519A1 (en) * | 2009-12-24 | 2011-06-30 | Siegel Steven A | Method and apparatus for providing a transit service for an aggregate endpoint |
US9019954B2 (en) * | 2010-06-18 | 2015-04-28 | Telefonaktiebolaget L M Ericsson (Publ) | Methods and apparatuses for handling public identities in an internet protocol multimedia subsystem network |
WO2012072407A1 (en) * | 2010-11-30 | 2012-06-07 | Koninklijke Kpn N.V. | Dynamic assignment of a serving network node |
CN104137554A (zh) * | 2012-02-24 | 2014-11-05 | Vid拓展公司 | 使用分组损耗检测的视频编码 |
US10536330B2 (en) * | 2013-04-03 | 2020-01-14 | Nokia Solutions And Networks Gmbh & Co. Kg | Highly dynamic authorisation of concurrent usage of separated controllers |
CN103441862B (zh) * | 2013-08-07 | 2017-08-04 | 华为技术有限公司 | 一种实现终端被叫业务恢复的方法、相关装置及*** |
US9648053B2 (en) * | 2014-05-12 | 2017-05-09 | Verizon Patent And Licensing Inc. | On-demand registration for internet protocol multimedia subsystem (IMS) services |
US9467183B2 (en) * | 2014-09-29 | 2016-10-11 | AT&T Intellectaul Property I, L.P. | Method and apparatus for receiving wireless communications |
FR3030968A1 (fr) * | 2014-12-23 | 2016-06-24 | Orange | Procede et dispositif de maintien d'associations d'adresses de transport aupres d'une entite de traduction d'adresses |
US9667665B1 (en) * | 2015-02-25 | 2017-05-30 | Spring Communications Company L.P. | Session initiation protocol (SIP) communications over trusted hardware |
US9392471B1 (en) * | 2015-07-24 | 2016-07-12 | Viavi Solutions Uk Limited | Self-optimizing network (SON) system for mobile networks |
US20170127427A1 (en) * | 2015-11-02 | 2017-05-04 | Viavi Solutions Uk Limited | Enhancing network topology information for a self-organizing network |
US10149193B2 (en) * | 2016-06-15 | 2018-12-04 | At&T Intellectual Property I, L.P. | Method and apparatus for dynamically managing network resources |
US9781259B1 (en) * | 2016-07-27 | 2017-10-03 | At&T Intellectual Property I, L.P. | Method and apparatus for asset location tracking in a communication network |
-
2017
- 2017-12-29 CN CN201711489721.3A patent/CN109995721B/zh active Active
-
2018
- 2018-12-05 WO PCT/CN2018/119262 patent/WO2019128650A1/zh unknown
- 2018-12-05 EP EP18895395.4A patent/EP3720187B1/en active Active
-
2020
- 2020-06-26 US US16/913,531 patent/US11496526B2/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060153353A1 (en) * | 2005-01-07 | 2006-07-13 | O'neil Douglas | Intelligent secondary call treatment for advanced calling scenarios |
CN101494890A (zh) * | 2006-12-08 | 2009-07-29 | 华为技术有限公司 | 一种路由会话的方法、网络及设备 |
CN101426261A (zh) * | 2008-12-17 | 2009-05-06 | 华为技术有限公司 | 多媒体子***业务处理的方法、p-cscf、i-cscf和多媒体子*** |
CN102752879A (zh) * | 2012-03-23 | 2012-10-24 | 中兴通讯股份有限公司 | 会话接入方法及装置 |
Also Published As
Publication number | Publication date |
---|---|
CN109995721B (zh) | 2021-10-22 |
US20200329075A1 (en) | 2020-10-15 |
EP3720187B1 (en) | 2023-08-16 |
US11496526B2 (en) | 2022-11-08 |
EP3720187A4 (en) | 2021-04-21 |
EP3720187A1 (en) | 2020-10-07 |
CN109995721A (zh) | 2019-07-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2019128650A1 (zh) | 业务请求处理方法、装置及通信*** | |
CN109951876B (zh) | 通信方法、相关装置及*** | |
US20220338152A1 (en) | Support for ims routing with multiple ims pdu sessions over different 5gc slices | |
US8533348B2 (en) | Failover communication services | |
WO2019154034A1 (zh) | 通信方法、相关装置及*** | |
US20110145388A1 (en) | Method, system, and device for realizing registration mechanism of ip multimedia subsystem | |
JP6396372B2 (ja) | 緊急呼(emergency call)の処理方法およびこれを用いた通信装置 | |
WO2016101791A1 (zh) | 故障处理的方法、装置和*** | |
WO2019144786A1 (zh) | 无线信息订阅方法、相关装置及*** | |
US11310845B2 (en) | Wireless management and connectivity across multiple networks | |
WO2019184717A1 (zh) | 一种通信方法、及相关产品 | |
WO2010069197A1 (zh) | 多媒体子***业务处理的方法、装置和多媒体子*** | |
WO2017028773A1 (zh) | 一种ims终端自组网的方法及装置 | |
WO2021213243A1 (zh) | 关联业务注册方法及相关设备、以及计算机可读存储介质 | |
WO2013037251A1 (zh) | Ils网络的ue在ims网络中的认证方法和*** | |
WO2023093271A1 (zh) | 一种确定s-cscf的方法及装置 | |
KR20200001122A (ko) | Ims 망에서 가입자를 관리하는 가입자 정보 관리 서버 및 방법 | |
US11818677B2 (en) | Restoration of long-duration services | |
EP3864814B1 (en) | Apparatus, method and computer program for call session control function restoration | |
US20170272939A1 (en) | Method, apparatus and computer program product for provisioning multiple user identities in an ip multimedia subsystem | |
CN117812619A (zh) | 一种数据处理方法以及装置 | |
WO2020001390A1 (zh) | 一种通信方法、设备及*** | |
KR20230141740A (ko) | 레벨 1 번호들의 라우팅을 용이하게 하기 위한 시스템 및 방법 | |
CN117675767A (zh) | 信息查询方法、装置、介质及设备 | |
WO2011134157A1 (zh) | 个人网络元素注册方法、设备和*** |
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: 18895395 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2018895395 Country of ref document: EP Effective date: 20200703 |