WO2007071188A1

WO2007071188A1 - R4 network system and method for providing media resource

Info

Publication number: WO2007071188A1
Application number: PCT/CN2006/003501
Authority: WO
Inventors: Xiaoyan He
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2005-12-23
Filing date: 2006-12-20
Publication date: 2007-06-28
Also published as: CN1988687A; CN100450210C

Abstract

A method for providing media resource in the R4 network includes: the network entity which processes the service requests transmits the media resource control command to the multimedia resource entity; and the multimedia resource controller in the said multimedia resource entity analyzes the said media resource control command, and orders the multimedia resource processor to provide the media resource; and the said multimedia resource processor completes the multimedia resource processing based on the media resource control command, and completes bearing the media resource to the user terminal by the media gateway. There also provides a R4 network system which includes a MSC, a MGW, a service controlling point and a multimedia resource entity.

Description

4 network to the system and methods of providing media resources

Technical field

The present invention relates to the field of communications, and in particular, to an R4 network system and a method for providing media resources. Background technique

In the 3GPP R4 phase, the UMTS core network is divided into two domains: a circuit domain (CS domain) and a packet domain (PS domain). The core network CS domain (between the mobile switching center MSCs) is based on time division multiplexing (TDM) transmission, and the PS domain is based on IP transport carries non-real-time data services.

Starting from the 3GPP R5 phase, the UMTS core network is divided into three subsystems: CS, PS, and IP Multimedia Subsystem (IMS). IMS is an IP multimedia subsystem located above the PS domain in the WCDMA network defined by the 3GPP R5/R6 standard. The packet domain is used as the bearer channel for the upper layer control signaling and the media transmission, and the SIP protocol is introduced as the service control protocol. The SIP is simple, easy to expand, and the media combination is convenient, and the service control and the bearer control are separated to provide rich Multimedia business.

The processing of media resources under the R4 network architecture is divided into two parts: The processing of the circuit domain based on the 'media flow of the service and the supplementary service' is completed by the end office MGW; the media resources of the value-added service other than the basic service and the supplementary service It is provided by the special resource function module gsmSRF ( gsm Specialized Resource Function ).

Referring to Figure 1, in the network transition from R99 to R4, the MSC is split into two parts: MSC Server and MGW. The MSC Server completes the basic service of the circuit domain and the control function of the media stream involved in the supplementary service, and the MGW accepts the command of the MSC Server to complete the processing of the media stream and the bearer of the user plane. The change of the control bearer of the media stream involved in the basic service of the circuit domain and the supplementary service is realized.

In the R4 network, the MSC Server has the following characteristics:

(1) Inheriting all the circuit domain control plane functions of the R99 MSC, and not implementing the bearer switching function (implemented by the MGW in multiple bearer modes).

(2) Provide a pure signaling interface to the outside world. (3) Integrated R99 VLR function to process mobile user service data and CAMEL related data.

(4) The control of the bearer terminal and the media stream in the MGW involved in the basic service of the circuit domain and the supplementary service is realized by the 3G extended 248 protocol.

(5) Implement bearer-independent inter-office call control with other MSC servers through BICC signaling. (6) Support MGW and its own registration and fault recovery operations, and may require the MGW to take the initiative

^=艮 Its terminal characteristics.

In the R4 network, GMSC Sever has the following characteristics:

(1) It consists of call control and mobility control of the GMSC, and only performs the signaling processing function of the GMSC.

(2) Has the function of querying location information. If the mobile station MS is called, if the network cannot query the HLR to which the user belongs, it needs to query through the GMSC server, and then transfer the call to the currently registered MSC server.

(3) Controlling the connection of the media channel in the MGW through the H.248 protocol.

(4) Support the interoperability between BICC and ISUP;

In the R4 network, the MGW is a gateway switching device of the user bearer plane of the 3G R4 core network, located at the boundary of the 3G CS core network to the radio access network (UTRAN/BSS) and the traditional fixed network (PSTN/ISDN); The Iu interface, the bearer channel of the PST/PLMN interface, and the termination point of the packet network media stream (such as the RTP stream) have the following characteristics:

(1) The MGW is not responsible for any mobile user related business logic processing.

(2) MGW can support media conversion, bearer control and service switching functions, such as GSM/UMTS voice codec, echo canceller, IWF, access network and core network side terminal media stream exchange, conference bridge, Play the number of resources, etc.

(3) The MGW can accept resource control commands from the MSC server and the GMSC server through H.248 signaling.

(4) Support circuit domain services implemented on multiple transmission media (based on AAL2/ATM, TDM, or RTP/UDP IP) to provide the necessary bearer control. In the R4 network application layer mobile intelligent network system, the resource function module gsmSRF can provide rich dedicated media resources for various basic intelligent services outside the circuit domain and supplementary services, and centrally manage all dedicated media resources. The resource function module gsmSRF can be integrated with the service switching function module SSF in the MSC Server. As shown in FIG. 2A, it can also be implemented by a separate device and connected to the MSC Sever and the service control module SCF. It is an Intelligent Peripheral IP, as shown in Figure 2B.

If the gsmSRF is integrated in the (G) MSC Server, the gsmSRF is split into two parts: gsmSRF Server and MGW. The gsmSRF Server terminates the CAP protocol and converts it into signaling control MGW. The MGW is responsible for providing some simple media resources and completing single resource operations. Such as separate DTMF tone detection. Compared with the implementation of gsmSRF integration in (G) MSC Server, the independent IP implementation can provide more resource capacity and can provide centralized management of flexible playback.

Since the existing media resource equipment MGW and the intelligent peripheral only support the media resource capability of the traditional telecommunication network defined service, the media resource capability of the existing device cannot meet the requirements with the introduction of various new services (such as video mailbox). , is not conducive to the development of new business.

In addition, in the network evolution of R99 to R4, the media resource management involved in the basic service supplementary service realizes the separation of the bearer (MGW) control (MSC Server); the way in which the gsmSRF Server is integrated in the (G)MSC Server is also embodied. This idea, while independent IP completes resource provisioning and resource management at the same time, but does not achieve this function, and is inconsistent with the evolution direction of the next generation network.

In the IMS network architecture, all non-basic session connection type value-added application services are provided in the application server AS entity, and the CSCF series (P-CSCF, S-CSCF, I-CSCF) of the session control layer is the basic IMS SIP session. Provides a common platform for service trigger routing of ASs running different value-added service logics, as well as registration, security protection, QoS control, basic session routing, etc. that all value-added applications can share, ensuring that each AS provider only needs attention. The design of the value-added service logic itself can be applied to the server AS. The AS includes three types: SIP Application Server that provides new value-added services for IMS users based on the SIP protocol. It implements SIP and INAP/CAP interworking to access traditional SCPs to provide IMS users. Circuit switching network intelligent network original value-added services IM-SSF, and a third-party application server OS A Application Serve that provides value-added services by calling the Parlay/OSA interface of the IMS network operator SIP capability server.

In the IMS network architecture, users can enjoy rich multi-body services, in which the AS provides IMS users with all non-basic session connection type value-added application service logic, multimedia resource function controller (M FC ) and multimedia resource function processor. (MRFP) provides users with the media resources needed for their services. Their location in the network is shown in Figure 3. (For clarity, the interfaces between all network elements are not listed in Figure 3.).

The multimedia resource function controller (MFC) controls the media resources on the multimedia resource function processor (MRFP) through H.248, parses the SIP resource control commands from other S-CSCFs and ASs, and converts them into corresponding control commands for the MRFP. Generate corresponding billing information. As a common resource of the network, the MRFP controls the IP user plane bearer connection with other IMS terminals or IM-MGW, provides resource services under the control of the MRFC, and combines a body stream (multi-party conference) and multimedia information playback (playback). , streaming media), media content parsing processing (code conversion, speech recognition, etc.).

Although MRFC/MRFP can meet the media resource capability requirements of various value-added services, the existing technology of MRFC/MRFP is located in the IMS domain and provides services for IMS network users, which cannot provide certain resources to CS domain users in traditional circuit-switched networks. Business, CS domain users cannot enjoy the rich media resources in MRF. Summary of the invention

An embodiment of the present invention provides an R4 network system and a method for providing a media resource, so as to provide a user with a media resource service in an IMS network in an R4 network.

An R4 network system, comprising: a mobile switching center, connected to the service control point, for providing a signaling control function; a media gateway, connected to the mobile switching center, for providing a media stream bearer; a service control point, And the mobile switching center is connected to provide a mobile network enhanced logic application service; wherein, the method further includes: a multimedia resource entity, connected to the mobile switching center and the media gateway; and the multimedia resource entity includes multimedia a resource entity controller and a multimedia source entity processor, wherein the multimedia resource entity controller is configured to accept the sending by the mobile switching center The media resource control command, the multimedia resource entity processor and the media gateway are independent of each other, and are configured to complete media resource processing according to a control command of the multimedia resource entity controller and provide media resources by using the media gateway.

A method for providing media resources in an R4 network, comprising the following steps:

The network entity that processes the service request in the R4 network sends a media resource control command to the multimedia resource entity;

The multimedia resource controller in the multimedia resource entity parses the media resource control command, and instructs the multimedia resource processor to provide the media resource;

The multimedia resource processor completes the multimedia resource processing according to the media resource control command, and completes the media resource bearer to the user terminal by using the media gateway.

The beneficial effects of the present invention are as follows:

1. Realize the separation of bearer control when the value-added service media resources are realized through separate peripherals, which conforms to the evolution direction of the next-generation network, so that the division of labor of each business entity is clear and can be developed for different technologies.

2. Circuit-switched network The enhanced media resource capability of the CS-domain media resource device can meet the needs of various new services, facilitate the development of new services, and enable the sharing of certain resources within the network. DRAWINGS

FIG. 1 is a schematic diagram of an evolution of an existing R99 network to an R4 network;

2A is a schematic diagram of the integration of the gsmSRF in the MSC Server in the prior art; FIG. 2B is a schematic diagram of the gsmSRF implemented by the independent IP in the prior art;

3 is a schematic diagram of an MS network in the prior art;

4A and FIG. 4B are schematic structural diagrams of an R4 network according to the present invention;

FIG. 5 is a flowchart of performing playback by a multimedia resource entity according to an embodiment of the present invention;

FIG. 6 is a flowchart of establishing a multi-party by a multimedia resource entity according to an embodiment of the present invention; FIG. 7 is a flowchart of codec conversion by a multimedia resource entity according to an embodiment of the present invention.

Body implementation Referring to FIG. 4A, the R4 network architecture of the embodiment includes functional entities such as an existing service control point SCP, a gateway mobile switching center GMSC, a mobile switching center MSC, and a media gateway MGW, and includes providing service media resource management. The multimedia resource entity MRE includes a multimedia resource controller (module) MREC and a multimedia resource processor (module) MREP; wherein, the MREC is connected to the GMSC and the MSC, the MREP is connected to the MGW, and the further MREC is also connected to the SCP. The SCP provides a mobile network to enhance the logic to customize the application service, the MSC provides a signaling control function, and the MGW provides a media stream bearer.

Referring to FIG. 4B, the R4 network of this embodiment further includes an application server AS, which is connected to the GMSC and the MREC, respectively, on the basis of FIG. 4A.

The following is a detailed description of Figure 4B.

The MREC entities can be integrated with MREP in physical implementation (as shown in Figure 4B), or MREC and MERP can also be separate physical entities, or MRE can be integrated with (G)MSC Server/SCP/AS. together. The MREC parses the information received from the AS, SCP or MSC Server and controls the media stream resources in the MREP.

The MREP entity is independent of the MGW, and an MREP can be connected to multiple MGWs. MREP can complete the media resource capabilities that MGW can't provide in new business requirements. The physical implementation can be integrated with MREC or it can be a separate physical entity. MREP performs media processing under the control of MREC. Its functions include:

A. Provide the resources required for MREC control, such as: voice Announce resources, conference conference resources, and codec CODEC resources;

"B, mixed into the media stream, such as, multi-party meetings, etc.;

(:, as the source, send media streams, such as multimedia notification tones;

D. Processing media streams, such as audio codec conversion, media analysis, and the like.

There can be a one-to-many relationship between the MREC entity and the MREP entity, that is, one MREC can manage multiple MREP entities. '

An AS entity that provides service media resource management can be integrated with the SCP in physical implementation, or it can be a separate physical entity. The AS provides but is not limited to the following functions: A. Provide various value-added services for end users:

B. Providing an interface between the MSC Server and the MSC Server, and receiving a service trigger message reported by the MSC Server to perform service control.

C. Provide an interface between the MREC and the MREC to send a media resource control command to the MREC. After the MRE and the AS are introduced in the R4 network, the MSC Server supports SIP or other applicable protocols through protocol extension to support interworking with the AS and introduce various new services through software upgrades. These services can use the media resources capabilities of the MRE.

The interface between the MREC and the AS is used by the MREC to receive the media resource control command from the AS. The interface is an external interface, but not limited to the SIP protocol. If the internal interface is an internal interface, it can also be implemented through a custom internal interface.

The interface between the MREC and the MSC Server is used by the MREC to receive the media resource control command from the MSC Server. The interface is the same as the Nc interface and supports the TUP/ISUP/BICC protocol interworking. The physical bearer can be implemented using TDM/IP. If it is an internal interface, it can also be implemented through a custom internal interface.

The interface between the MREP and the MGW is used to implement the IP bearer of the media stream when the user interacts with the media stream. The interface is consistent with the Nb interface, that is, the RTP/AAL2/AMR protocol is supported. The physical bearer can use TDM/IP/. ATM implementation.

Interface between MREC and MREP Interface4 is used to indicate that the MREP completes the corresponding media resource processing. The interface is an external interface, but not limited to the H.248 protocol. If the internal interface is an internal interface, it can also be implemented through a custom internal interface.

The interface between the MSC Server and the AS is used by the MSC Server for value-added service triggering. The interface can be implemented by the SIP protocol.

Interface between MREC and SCP Interface6 is used by MREC to receive media resource control commands from SCP. This interface is implemented by CAP protocol when it is an external interface. It can also be implemented by a custom internal interface if it is an internal interface.

After introducing MRE/ and AS in the R4 network architecture:

The ways in which MREC entities manage MREP include: A. MREP actively registers with the MREC when the state changes (the resource capability changes, and the state changes), and the registration information includes resource capability and MREP address information.

An MREP can have multiple resource capabilities, or it can distribute different (something resources) on different MREPs;

B. When receiving the control command of the AS/SCP/MSC Server, the MREC sends a resource request to the MREP that meets the requirement according to the media resource capability and address information of the MREP stored therein.

The media resource control of a service can be done in one of several ways or any combination of them:

1. When the AS accepts the service trigger:

When the AS accepts the service trigger request of the MSC Server and finds that the service needs media resource support, it will initiate a resource request to the MREC that has been registered internally according to its internal service logic, or send the request to the (G) MSC. Server, the request is forwarded by (G) MSC Server, the MREC parses the request, converts it into a format that MREP can recognize (H.248 packet format), instructs MREP to perform corresponding media processing, and MREP provides media required by MREC The resource, and the bearer of the media resource to the end user is completed by the link path with the MGW, wherein the AS/(G) MSC Server discovers the MREC in the CS domain network through the traditional circuit switched network number segment routing manner.

2. When the SCP accepts the service trigger:

When the SCP accepts the service trigger request of the MSC Serve and finds that the service needs media resource support, it sends the service indication and the MRE address information to the (MSC) MSC Server according to its internal service control. (G) The MSC Server will The request is converted and forwarded to the specified MREC; or, the SCP directly initiates a resource request to the MREC, the MREC parses the request, converts it into a format that the MREP can recognize, instructs the MREP to perform corresponding media processing, and the MREP provides MREC requirements. Media resources, and through the link path with the MGW to complete the carrying of media resources to the end user. The SCP is implemented by the conventional circuit switching network number segment routing method for the discovery of the MREC in the CS domain network;

3 ( G ) MSC Server directly triggers through data configuration: (G) The MSC Server can configure the static table data to specify that for the value-added services, if the MRE needs to provide the media resources, the media resources request is not directly sent to the MREC specified in the data configuration table by the SCP or the AS, and the MREC receives the request. After the request, the signaling conversion indicates that the MREP performs the corresponding media processing > MREP provides the media resources required by the MREC, and completes the bearer of the media resource to the end user through the link path with the MGW. The (G) MSC Server discovers the MREC in the CS domain network through the traditional circuit switched network number segment routing.

Referring to FIG. 5, the SCP accepts service triggering, and the main process of playing the calling user is as follows: Steps 500 to 502: The terminal UE sends a service request, and the service request is connected to the called UE in the MSC bo.

Step 503: After the called MSC b receives the IAM incoming request, analyzes the called number carried in the judgment message, and if the called party is the CRBT service user, initiates a service trigger to the SCP.

Step 504: The SCP returns information such as the MRF address registered therein to the called MSC b through the service trigger response message.

Step 5Θ5-506: The called MSC b obtains the called user status.

Steps 507-508: When the called user is idle, the MSC b initiates a resource request to the MREC, and the MREC determines to support the resource type requested by the MSC b and returns a corresponding response thereto.

Step 509: The MREC controls the MREP to send a customized ring tone to the calling party through the link with the MGW.

Referring to Figure 6, the AS accepts service triggering. The main process of establishing a multiparty conference is as follows (the UE is not shown in the figure):

Step 600: The MSC receives the UE-1 setup multi-party call request message, and the request indicates that it wants to join the UE-2, UE-3 to the current conference.

Steps 601 - 602: The MSC returns a temporary response and forwards the request to the AS.

Step 603: The AS performs related business logic to allow establishment of the conference.

Steps 604 - 607: The AS sends a request to the MREC to indicate that a multiparty call is established, obtains the conference identity, and prepares for the UE-2 access.

Steps 608 - 612: The AS makes a request to UE-2 and establishes a connection with UE-2. Steps 613 - 616: The AS returns a response confirmation message.

Steps 617 - 620: The AS sends a resource request to the EC to prepare for the UE-3 access by using the conference identifier applied above.

Steps 621 - 625: The AS makes a request to UE-3 and establishes a connection with UE-3.

Steps 626 - 629: The AS returns a response confirmation message.

Steps 630 - 633: The AS sends a resource request to the MREC by using the conference identifier applied above to prepare for UE 1 access.

Steps 634 - 635: The UE-1 returns to this conference successfully established.

Step 636: Establish a meeting.

Steps 637 - 640: The AS returns a confirmation message.

Referring to Figure 7, the main process that the calling and called parties need to perform codec conversion during call setup is as follows:

Step 700: The MSC receives a calling party service request.

Step 701: The MSC returns a temporary response to the calling party.

Step 702: The MSC triggers the request to the AS according to the user subscription data.

Step 703: The AS business logic continues to process the service request.

Step 704: The AS sends a request to the peer called party through the MSC.

Step 705: The MSC forwards the request.

Step 706: The called party returns an unacceptable request, and indicates in the response message that the encoding method provided in the request is not supported, and carries the encoding scheme supported by itself.

Step 707: The MSC returns a confirmation message to the called party.

Step 708: The called party's response is forwarded to the AS.

Step 709: The AS service logic finds that the MREC can complete the codec conversion.

Step 710: The AS returns an acknowledgement message to the MSC.

Steps 711 - 716: The AS issues a request to the MREC to establish a codec conversion for the called party. Steps 717 - 724: The AS issues a request to the called party to request that a session be established between the called party and the MRE. Steps 725 - 728: The AS makes a request to the MREC to request a codec conversion for the calling party. Steps 729 - 737: The call is established, and the calling party is called normally.

By introducing the MREC MREP functional entity in the R4 network architecture, the bearer control phase separation of the media resources in the value-added service through the separate peripherals is realized. By improving the media resource capability, the media resource device can meet the higher service requirements of the user. , to facilitate the development of a variety of new businesses. The spirit and scope of the invention. Therefore, it is intended that the present invention cover the modifications and variations of the invention as claimed.

Claims

Rights request

1. An R4 network system, including:

a mobile switching center, connected to the service control point, for providing a signaling control function; a media gateway, connected to the mobile switching center, for providing a media stream bearer;

a service control point, connected to the mobile switching center, for providing a mobile network enhanced logic customized application service;

It is characterized in that it further comprises:

a multimedia resource entity, connected to the mobile switching center and the media gateway; and the multimedia resource entity includes a multimedia resource entity controller and a multimedia resource entity processor, where the multimedia resource entity controller is configured to accept the media resource sent by the mobile switching center Controlling the command, the multimedia resource entity processor and the media gateway are independent of each other, and are used according to the multimedia resource

2. The R4 network system according to claim 1, wherein the multimedia resource entity is further connected to the service control point, and the multimedia resource entity controller accepts and controls the media resource control command sent by the service control point. The multimedia resource entity processor.

The R4 network system according to claim 1, further comprising: an application server, connected to the multimedia resource entity and the mobile switching center, for providing a value-added application monthly service, or by using a multimedia resource entity The media resource control command is controlled by the multimedia resource entity controller in the multimedia resource entity to control the multimedia resource processor to complete media processing and provide media resources.

The R4 network system according to claim 1, 2 or 3, wherein the multimedia resource entity controller is integrated with the multimedia resource entity processor; or the multimedia resource entity controller and The multimedia resource entity processor is an independently set physical entity; or the multimedia resource entity processor is an independently set physical entity, and the multimedia resource entity controller is set in another network entity.

The R4 network system according to claim 4, wherein the multimedia resource is The body processor is connected to multiple media gateways.

The R4 network system according to claim 4, wherein the multimedia resource entity processor is a plurality of processors and is controlled by the multimedia resource entity controller.

A method for providing a media resource in an R4 network, comprising the following steps: a network entity that processes a service request in an R4 network sends a media resource control command to a multimedia resource entity;

The method according to claim 7, wherein, for the multimedia resource entity in the circuit domain, the network entity sends a media resource control command to the multimedia resource entity by using a circuit switched network number segment routing manner.

The method according to claim 7 or 8, wherein the network entity that processes the service request is a service control point, and the service control point directly sends a media resource control command to the multimedia resource entity, or the service The control point sends a media resource control command to the multimedia resource entity through the mobile switching center.

The method of claim 7 or 8, wherein the entity that processes the service request is an application server that provides a value-added application server, and the application server directly sends a media resource control command to the multimedia resource entity, or The application server sends a media resource control command to the multimedia resource entity through the mobile switching center.

The method according to claim 7 or 8, wherein the entity that processes the service request is a mobile switching center, and the mobile switching center receives the service request before directly reporting the configuration data to the multimedia resource entity. Send a media resource control command.