WO2017063668A1 - Rétention de données pour itinérance à routage de rattachement s8 - Google Patents

Rétention de données pour itinérance à routage de rattachement s8 Download PDF

Info

Publication number
WO2017063668A1
WO2017063668A1 PCT/EP2015/073612 EP2015073612W WO2017063668A1 WO 2017063668 A1 WO2017063668 A1 WO 2017063668A1 EP 2015073612 W EP2015073612 W EP 2015073612W WO 2017063668 A1 WO2017063668 A1 WO 2017063668A1
Authority
WO
WIPO (PCT)
Prior art keywords
request
session
time
information
received
Prior art date
Application number
PCT/EP2015/073612
Other languages
English (en)
Inventor
Thomas Belling
Peter Leis
Original Assignee
Nokia Solutions And Networks Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Solutions And Networks Oy filed Critical Nokia Solutions And Networks Oy
Priority to PCT/EP2015/073612 priority Critical patent/WO2017063668A1/fr
Publication of WO2017063668A1 publication Critical patent/WO2017063668A1/fr

Links

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/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
    • 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/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]

Definitions

  • the present invention relates to apparatuses, methods, systems, computer programs, computer program products and computer-readable media regarding data retention for S8 home routed roaming.
  • the Internet Protocol Multimedia Subsystem is the standardized solution for Multimedia telephony over IP based networks, e.g. Voice over LTE (VoLTE) is utilizing IMS. It thus sees increased interest from the operator community.
  • VoIP Voice over LTE
  • PLMNs Public Land Mobile Networks
  • This invention is dealing with the so called S8/home routing based roaming model that has been selected by GSMA as one recommended roaming model for VoLTE.
  • 3GPP SA2 is now studying technical impacts of S8HR in document [1 ].
  • this invention describes that the visited network can support so called data retention in case S8HR is used.
  • Fig. 1 is a diagram illustrating the reference architecture for S8/home routing based roaming model.
  • solid lines indicate the user plane and dashed lines indicate the signaling plane.
  • VPLMN Regulatory requirements in the country of the VPLMN (Visited PLMN) can require that the VPLMN operator has to support so called data retention. For instance, data retention is required by regulations of the European Union. Data retention means that the VPLMN operator has to record data that is related to the traffic via his network nodes.
  • the S-GW will have to store data related to VoLTE calls, for instance the identities of the source of the communications (calling party) and the destination of the communication (called party), and the date, time and duration of the call.
  • data is part of the application layer protocol, and the S-GW has no understanding of any signalling above GTP-U, i.e. it has no understanding of Application Layer protocols, as can be seen from Fig. 2 showing the involved protocol stacks.
  • the application layer protocol can even be encrypted, e.g. via IPsec.
  • the data to be retained are encoded in SIP (Session Initiation Protocol) as application layer protocol.
  • SIP Session Initiation Protocol
  • the data contains:
  • Type of communication e.g. voice call, video call, messaging session.
  • a method for use in a call session control function comprising:
  • a request for initiating a communication session including at least information regarding a calling party, a called party, and information for deriving a communication type
  • extracting session information related to the communication session from the received request the extracted session information including at least one of information regarding the calling party, the called party, the communication type and a time when the request is received
  • a serving gateway comprising:
  • an apparatus for use in a call session control function comprising:
  • At least one memory for storing instructions to be executed by the processor, wherein the at least one memory and the instructions are configured to, with the at least one processor, cause the apparatus at least to perform:
  • a request for initiating a communication session including at least information regarding a calling party, a called party, and information for deriving a communication type
  • the extracted session information including at least one of information regarding the calling party, the called party, the communication type and a time when the request is received, and
  • an apparatus for use in a serving gateway comprising
  • At least one memory for storing instructions to be executed by the processor, wherein the at least one memory and the instructions are configured to, with the at least one processor, cause the apparatus at least to perform:
  • a computer program product comprising code means adapted to produce steps of any of the methods as described above when loaded into the memory of a computer.
  • a computer program product as defined above, wherein the computer program product comprises a computer- readable medium on which the software code portions are stored.
  • an apparatus comprising:
  • a request for initiating a communication session including at least information regarding a calling party, a called party, and information for deriving a communication type
  • an apparatus comprising:
  • Fig. 1 is a diagram illustrating the reference architecture for S8/home routing based roaming model.
  • Fig. 2 is a diagram illustrating the involved protocol stacks.
  • Fig. 3 is a diagram illustrating an overview of architecture for illustration of the involved nodes according to certain aspects of the present invention.
  • Fig. 4 is a signaling diagram illustrating an example call flow for data retention according to certain aspects of the present invention.
  • Fig. 5 is a flowchart illustrating an example of a method according to certain aspects of the present invention.
  • Fig. 6 is a flowchart illustrating another example of a method according to certain aspects of the present invention.
  • Fig. 7 is a block diagram illustrating an example of an apparatus according to certain aspects of the present invention.
  • the basic system architecture of a communication network may comprise a commonly known architecture of one or more communication systems comprising a wired or wireless access network subsystem and a core network.
  • Such an architecture may comprise one or more communication network control elements, access network elements, radio access network elements, access service network gateways or base transceiver stations, such as a base station (BS), an access point or an eNB, which control a respective coverage area or cell and with which one or more communication elements or terminal devices such as a UE or another device having a similar function, such as a modem chipset, a chip, a module etc., which can also be part of a UE or attached as a separate element to a UE, or the like, are capable to communicate via one or more channels for transmitting several types of data.
  • core network elements such as gateway network elements, policy and charging control network elements, mobility management entities, operation and maintenance elements, and the like may be comprised.
  • the communication network is also able to communicate with other networks, such as a public switched telephone network or the Internet.
  • the communication network may also be able to support the usage of cloud services.
  • BSs and/or eNBs or their functionalities may be implemented by using any node, host, server or access node etc. entity suitable for such a usage.
  • network elements and communication devices such as terminal devices or user devices like UEs, communication network control elements of a cell, like a BS or an eNB, access network elements like APs and the like, as well as corresponding functions as described herein may be implemented by software, e.g. by a computer program product for a computer, and/or by hardware.
  • nodes or network elements may comprise several means, modules, units, components, etc. (not shown) which are required for control, processing and/or communication/signaling functionality.
  • Such means, modules, units and components may comprise, for example, one or more processors or processor units including one or more processing portions for executing instructions and/or programs and/or for processing data, storage or memory units or means for storing instructions, programs and/or data, for serving as a work area of the processor or processing portion and the like (e.g. ROM, RAM, EEPROM, and the like), input or interface means for inputting data and instructions by software (e.g. floppy disc, CD-ROM, EEPROM, and the like), a user interface for providing monitor and manipulation possibilities to a user (e.g. a screen, a keyboard and the like), other interface or means for establishing links and/or connections under the control of the processor unit or portion (e.g.
  • radio interface means comprising e.g. an antenna unit or the like, means for forming a radio communication part etc.) and the like, wherein respective means forming an interface, such as a radio communication part, can be also located on a remote site (e.g. a radio head or a radio station etc.).
  • a remote site e.g. a radio head or a radio station etc.
  • processing portions should not be only considered to represent physical portions of one or more processors, but may also be considered as a logical division of the referred processing tasks performed by one or more processors.
  • Certain aspects of the present invention relate to the so called S8/home routing based roaming model as one recommended roaming model for VoLTE.
  • certain aspects of the present invention describe that the visited network can support so called data retention in case S8HR is used.
  • Fig. 3 is a diagram illustrating an overview of architecture for illustration of the involved nodes according to certain aspects of the present invention.
  • FIG. 3 One the right side of Fig. 3, there is shown the Home PLMN of party A (HPLMN A) 31 including the P-CSCF 31 1 and the PCRF 312 which are connected to each other via the Rx- interface.
  • the PCRF 312 is further connected to the P-GW 313 via the Gx-interface and the P-GW 313 is also connected to the P-CSCF 31 1 .
  • FIG. 3 On the left side of Fig. 3, there is shown the Visited PLMN of party A (VPLMN A) 32 including the S-GW 321 which is connected to the P-GW of the HPLMN A 31 via the S8- interface.
  • the S-GW 321 is further connected to the MME 322 via the S1 1 interface and is also connected to E-UTRAN 323 via the S1 -U interface.
  • the E-UTRAN 323 is also connected to the MME 322 and to a user equipment (UE) 324.
  • UE user equipment
  • the P-CSCF 31 1 in the home network HPLMN A 31 extracts data to be retained from SIP signaling related to the call establishment (e.g. Called and calling party identities, and time and type of communication).
  • the P-CSCF 31 1 provides these data to the PCRF312 via the Rx interface (as defined in document [2]), for instance within a new transparent container, as part of the service information related to the call being established.
  • the PCRF 312 forwards these data to the P-GW 313 via the Gx interface, or alternatively, to a BBERF (Bearer Binding and Event Reporting Function) via the Gxx interface (as defined in document [3]) (not illustrated in Fig. 3), for instance within the same transparent container, as part of the policy and charging information related to the call being established.
  • BBERF Bit Binding and Event Reporting Function
  • the P-GW 313 forwards the data, for instance within the same transparent container, in GTP (as defined in document [4]) via the S8 interface to the S-GW 321 in the VPLMN A 32 as part of the signaling to establish a bearer for the call being established.
  • the BBERF (not shown) forwards the data, for instance within the same transparent container, via PMIP (Proxy Mobile IP) to the S-GW 321.
  • the S-GW 321 stores this data, i.e. provides data retention capabilities.
  • the S-GW 321 can also add further data related to the radio bearer, for instance the location of mobile communication equipment, to the data to be retained.
  • the S-GW records when the bearer, for which it obtained retention data within GTP during its establishment, is terminated, and calculates the duration between the establishment and the termination of the bearer.
  • the P-CSCF derives the duration of the call and/or the time of the call termination from SIP signaling at call termination.
  • the P-CSCF forwards this information to the PCRF as part of the update of the session information at call termination, for instance again within a transparent container.
  • the PCRF forwards this information to the P-GW as part of the update of the policy and charging control information at IP CAN session termination.
  • the P-GW forwards this information to the S-GW via GTP signaling to update or terminate the bearer for the call.
  • the S-GW stores this information as part of the retained data.
  • Fig. 4 is a signaling diagram illustrating an example call flow for data retention according to certain aspects of the present invention.
  • the signaling elements and procedures according to certain aspects of the present invention are marked with italic font.
  • the P-CSCF 31 1 receives a SIP INVITE request.
  • the INVITE is received from the served UE.
  • the INVITE is received from the remote peer, which are both not illustrated in Fig. 4.
  • the called party identity is designated via the request URI, and the SDP (Session Description Protocol) offer contains information about the desired media that can be used to derive the type of the communication.
  • the P-CSCF has knowledge about the identity of the served UE acting as caller and inserts the P-Asserted-ldentity header, which then contains the calling party identity.
  • the calling party identity is designated in the P- Asserted Identity header field
  • the called party identity is designated in the P-Called- Party-ID header field.
  • step S42 the P-CSCF 31 1 extracts at least one of information about the media for the service information, information about the calling and called parties and the type of the communication (e.g. voice call) and records the time.
  • information about the media for the service information information about the calling and called parties and the type of the communication (e.g. voice call) and records the time.
  • the P-CSCF 31 1 forwards the SIP INVITE request to the called party in step S43 and receives a SIP message containing the SDP answer in step S44.
  • step S45 the P-CSCF 31 1 extracts further service information from the SDP answer received in step S44.
  • the P-CSCF 31 1 sends a Diameter AA-Request containing the extracted service information to the PCRF 312 in step S46.
  • the P-CSCF 311 also adds the calling and called party identities, the type of the communication and possibly the recorded time.
  • the P-CSCF 31 1 uses a transparent container to encapsulate this added information.
  • step S47 the P-CSCF forwards the SIP message containing the SDP answer.
  • the PCRF 312 Upon reception of message in step S46, the PCRF 312 derives PCC rules from the service information and sends them in a Diameter RA-Request to the P-GW 313 in step S48. According to certain aspects of the present invention, the PCRF 312 also adds the received calling and called party identities, the type of the communication and the possibly recorded time to the RAR. If this information is embedded in a transparent container, the PCRF 312 adds the transparent container to the RAR. The added information or transparent container is added to a PCC rule derived from the service information to achieve that the P-GW 313 will add this information to the bearer corresponding to the PCC rule in step S49.
  • the P-GW 313 inspects the PCC rule and decides that a dedicated bearer is required for the media. It sends a GTP "Create Bearer Request" message in step S49 to set up the bearer.
  • the P-GW 313 may also find that a suitable bearer towards the served UE already exists, but will then need to modify the bearer to provide information towards the served UE where to send media and will then send a GTP "Modify Bearer Request" message (not illustrated in Fig. 4).
  • the P-GW 313 also adds the received calling and called party identities, the type of the communication and the possibly recorded time to the GTP message. If this information is embedded in a transparent container, the P-GW 313 adds the transparent container to the GTP message.
  • the S-GW 321 receives the GTP message sent in step S49.
  • the S-GW 321 extracts the contained calling and called party identities, the type of the communication and the possibly recorded time. If no time is contained, the S-GW 321 records the time when it receives the GTP message.
  • the S-GW 321 stores this information and possibly adds additional information about the location (e.g. cell ID) and the type and/or identity of the mobile equipment that the S-GW 321 can obtain from other nodes in the radio access network.
  • the S-GW 321 can also forward this stored information to other network nodes for a centralized storage.
  • the P-CSCF 31 1 When the call is being terminated, the P-CSCF 31 1 will receive a SIP "BYE" message from the calling party in step S41 1 .
  • step S412 the P-CSCF 31 1 can record the time and calculate the duration of the call using the previously stored time when the INVITE message was received. Then, the P-CSCF 311 forwards the SIP BYE message to the called party in step S413.
  • the P-CSCF 31 1 further sends a Diameter ST-Request to the PCRF 312 in step S414.
  • the P-CSCF 31 1 can add the possibly recorded time or the calculated duration.
  • the P-CSCF 31 1 uses a transparent container to encapsulate this added information.
  • the PCRF 312 Upon reception of message sent in step S414, the PCRF 312 derives PCC rule(s) to be removed from the service information and sends a request to remove those PCC rule(s) in a Diameter RA-Request to the P-GW 313 in step S415.
  • the PCRF 312 also adds the possibly received time or duration to the RAR. If this information is embedded in a transparent container, the PCRF 312 adds the transparent container to the RAR. The added information or transparent container is added to the request to delete a PCC rule derived from the service information to achieve that the P-GW 313 will add this information to the bearer corresponding to the PCC rule in step S416.
  • the P-GW 313 inspects the PCC rule(s) to be removed and decides that the dedicated bearer for the media needs to be terminated. It sends a GTP "Delete Bearer Request" message in step S416 to terminate that bearer.
  • the P-GW 313 may also decide to retain that bearer towards the served UE for other media, but will then need to modify the bearer to provide information towards the served UE where to send media and will then send a GTP "Modify Bearer Request" message (not illustrated in Fig. 4).
  • the P-GW 313 also adds the possibly received time or duration to the GTP message. If this information is embedded in a transparent container, the P-GW 313 adds the transparent container to the GTP message.
  • the S-GW 321 receives the GTP message sent in step S416. According to certain aspects of the present invention, the S-GW 321 extracts the possibly received time or duration. If a time is contained, the S-GW 321 calculates the duration of the call by comparing the time with the time stored in step S410. If no time or duration is contained, the S-GW 321 records the time when it received the GTP message and calculates the duration of the call by comparing the time with the time stored in step S410. The S-GW 321 stores this information. The S-GW 321 can also forward this stored information to other network nodes for a centralized storage.
  • the VPLMN needs to retain the calling and called party identities for voice calls. This information is only available in IMS nodes in the HPLMN.
  • the P-CSCF in the HPLMN sends this information via PCC interfaces to the P-GW, which forwards it to the S-GW in the VPLMN that stores the data for retention purposes.
  • Fig. 5 is a flowchart illustrating an example of a method according to example versions of the present invention.
  • the method may be implemented in or may be part of a proxy call session control function or the like.
  • the method comprises receiving a request for initiating a communication session in a step S51 .
  • the request includes at least information regarding a calling party, a called party, and information for deriving a communication type.
  • the method comprises extracting session information related to the communication session from the received request in a step S52, the extracted session information including at least one of information regarding the calling party, the called party, the communication type and a time when the request is received.
  • the method comprises forwarding the session information to a policy and charging rules function in a step S53.
  • the session information is forwarded to the policy and charging rules function in an authentication request message.
  • the method further comprises extracting service information from the request and from a session initiation answer message received by the call session control function, and forwarding the service information to the policy and charging rules function in an authentication request message.
  • the session information and the service information is encapsulated in a transparent container, the transparent container being added to an authentication request message forwarded to the policy and charging rules function.
  • the method further comprises receiving a request for terminating the communication session, and recording a time when the request for terminating the communication session is received.
  • the method further comprises calculating a duration of the communication session based on the time when the request for initiating the communication session is received and the time when the request for terminating the communication session is received. According to some example versions of the present invention, the method further comprises forwarding the time when the request for terminating the communication session is received or the calculated duration to the policy and charging rules function.
  • the time or the duration is forwarded to the policy and charging rules function in a session termination request.
  • the time or the duration is encapsulated in a transparent container, the transparent container being added to the session termination request forwarded to the policy and charging rules function.
  • Fig. 6 is a flowchart illustrating another example of a method according to example versions of the present invention.
  • the method may be implemented in or may be part of a serving gateway or the like.
  • the method comprises receiving a bearer request message from a packet data network gateway in a step S61 , and extracting session information from the bearer request message in a step S62, the extracted session information including at least one of information regarding a calling party, a called party, and a communication type. Further, the method comprises storing or forwarding the extracted session information in a step S63.
  • the extracted session information may be stored in the serving gateway and/or may be forwarded for storage to an external entity.
  • the method further comprises recording a first time based on a time when the bearer request message is received or a time indicated in the session information extracted from the bearer request message indicating when a request for initiating a communication session has been received by a call session control function.
  • the method further comprises receiving a bearer delete message from the packet data network gateway.
  • the method further comprises extracting a second time included in the bearer delete message indicating when a request for terminating a communication session has been received by the call session control function, and calculating a duration of the communication session based on the first time and the second time extracted from the bearer delete message, and storing or forwarding the calculated duration.
  • the method further comprises recording a second time when the bearer delete message is received, and calculating a duration of the communication session based on the first time and the second time recorded when the bearer delete message is received, and storing or forwarding the calculated duration.
  • the method further comprises extracting a duration of a communication session from the bearer delete message, and storing or forwarding the extracted duration.
  • the bearer request message is a request for creating a new bearer or a request for modifying an existing bearer.
  • Fig. 7 is a block diagram illustrating an example of an apparatus according to some example versions of the present invention.
  • a block circuit diagram illustrating a configuration of an apparatus 70 is shown, which is configured to implement the above described aspects of the invention.
  • the apparatus 70 shown in Fig. 7 may comprise several further elements or functions besides those described herein below, which are omitted herein for the sake of simplicity as they are not essential for understanding the invention.
  • the apparatus may be also another device having a similar function, such as a chipset, a chip, a module etc., which can also be part of an apparatus or attached as a separate element to the apparatus, or the like.
  • the apparatus 70 may comprise a processing function or processor 71 , such as a CPU or the like, which executes instructions given by programs or the like.
  • the processor 71 may comprise one or more processing portions dedicated to specific processing as described below, or the processing may be run in a single processor. Portions for executing such specific processing may be also provided as discrete elements or within one or further processors or processing portions, such as in one physical processor like a CPU or in several physical entities, for example.
  • Reference sign 72 denotes transceiver or input/output (I/O) units (interfaces) connected to the processor 71 .
  • the I/O units 72 may be used for communicating with one or more other network elements, entities, terminals or the like.
  • the I/O units 72 may be a combined unit comprising communication equipment towards several network elements, or may comprise a distributed structure with a plurality of different interfaces for different network elements.
  • the apparatus 70 further comprises at least one memory 73 usable, for example, for storing data and programs to be executed by the processor 71 and/or as a working storage of the processor 71.
  • the processor 71 is configured to execute processing related to the above described aspects.
  • the apparatus 70 may be implemented in or may be part of a proxy call session control function or the like, and may be configured to perform a method as described in connection with Fig. 5.
  • the processor 71 is configured to perform receiving a request for initiating a communication session, the request including at least information regarding a calling party, a called party, and information for deriving a communication type, extracting session information related to the communication session from the received request, the extracted session information including at least one of information regarding the calling party, the called party, the communication type and a time when the request is received, and forwarding the session information to a policy and charging rules function.
  • the apparatus 70 may be implemented in or may be part of a serving gateway or the like, and may be configured to perform a method as described in connection with Fig. 6.
  • the processor 71 is configured to perform receiving a bearer request message from a packet data network gateway, extracting session information from the bearer request message, the extracted session information including at least one of information regarding a calling party, a called party, and a communication type, and storing or forwarding the extracted session information.
  • the apparatus for use in a proxy call session control function and the apparatus for use in a serving gateway, generally have the same structural components, wherein these components are configured to execute the respective functions of the network elements, i.e. the proxy call session control function and the serving gateway, respectively, as set out above.
  • the apparatus (or some other means) is configured to perform some function
  • this is to be construed to be equivalent to a description stating that a (i.e. at least one) processor or corresponding circuitry, potentially in cooperation with computer program code stored in the memory of the respective apparatus, is configured to cause the apparatus to perform at least the thus mentioned function.
  • a (i.e. at least one) processor or corresponding circuitry potentially in cooperation with computer program code stored in the memory of the respective apparatus, is configured to cause the apparatus to perform at least the thus mentioned function.
  • function is to be construed to be equivalently implementable by specifically configured circuitry or means for performing the respective function (i.e. the expression "unit configured to” is construed to be equivalent to an expression such as "means for").
  • any method step is suitable to be implemented as software or by hardware without changing the idea of the aspects/embodiments and its modification in terms of the functionality implemented;
  • CMOS Complementary MOS
  • BiMOS Bipolar MOS
  • BiCMOS Bipolar CMOS
  • ECL emitter Coupled Logic
  • TTL Transistor-Transistor Logic
  • ASIC Application Specific IC
  • FPGA Field- programmable Gate Arrays
  • CPLD Complex Programmable Logic Device
  • DSP Digital Signal Processor
  • - devices, units or means can be implemented as individual devices, units or means, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device, unit or means is preserved;
  • an apparatus may be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of an apparatus or module, instead of being hardware implemented, be implemented as software in a (software) module such as a computer program or a computer program product comprising executable software code portions for execution/being run on a processor;
  • a device may be regarded as an apparatus or as an assembly of more than one apparatus, whether functionally in cooperation with each other or functionally independently of each other but in a same device housing, for example.
  • respective functional blocks or elements according to above- described aspects can be implemented by any known means, either in hardware and/or software, respectively, if it is only adapted to perform the described functions of the respective parts.
  • the mentioned method steps can be realized in individual functional blocks or by individual devices, or one or more of the method steps can be realized in a single functional block or by a single device.
  • any method step is suitable to be implemented as software or by hardware without changing the idea of the present invention.
  • Devices and means can be implemented as individual devices, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device is preserved. Such and similar principles are to be considered as known to a skilled person.
  • Software in the sense of the present description comprises software code as such comprising code means or portions or a computer program or a computer program product for performing the respective functions, as well as software (or a computer program or a computer program product) embodied on a tangible medium such as a computer-readable (storage) medium having stored thereon a respective data structure or code means/portions or embodied in a signal or in a chip, potentially during processing thereof.

Landscapes

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

Abstract

La présente invention concerne des appareils, des procédés, des programmes informatiques, des produits de programme informatique et des supports lisibles par ordinateur concernant la rétention de données pour l'itinérance à routage de rattachement S8. La présente invention comprend les étapes suivantes : réception d'une demande pour initier une session de communication, la demande contenant au moins des informations concernant une partie appelante, une partie appelée, et des informations pour dériver un type de communication, extraction d'informations de session en rapport avec la session de communication à partir de la demande reçue, les informations de session extraites contenant des informations concernant au moins un élément parmi la partie appelante, la partie appelé, le type de communication et un moment où la demande est reçue, et transmission des informations de session à une fonction de politique et de règles de facturation.
PCT/EP2015/073612 2015-10-13 2015-10-13 Rétention de données pour itinérance à routage de rattachement s8 WO2017063668A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2015/073612 WO2017063668A1 (fr) 2015-10-13 2015-10-13 Rétention de données pour itinérance à routage de rattachement s8

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2015/073612 WO2017063668A1 (fr) 2015-10-13 2015-10-13 Rétention de données pour itinérance à routage de rattachement s8

Publications (1)

Publication Number Publication Date
WO2017063668A1 true WO2017063668A1 (fr) 2017-04-20

Family

ID=54293252

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2015/073612 WO2017063668A1 (fr) 2015-10-13 2015-10-13 Rétention de données pour itinérance à routage de rattachement s8

Country Status (1)

Country Link
WO (1) WO2017063668A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1770915A1 (fr) * 2005-09-29 2007-04-04 Matsushita Electric Industrial Co., Ltd. Contrôle de regles dans un système d'architecture évoluée
EP2056570A1 (fr) * 2007-10-29 2009-05-06 Nokia Siemens Networks Oy Session et média liés à une commande commune
US20110302289A1 (en) * 2010-06-07 2011-12-08 Verizon Patent And Licensing Inc. Selection of a policy and charging rules function device

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1770915A1 (fr) * 2005-09-29 2007-04-04 Matsushita Electric Industrial Co., Ltd. Contrôle de regles dans un système d'architecture évoluée
EP2056570A1 (fr) * 2007-10-29 2009-05-06 Nokia Siemens Networks Oy Session et média liés à une commande commune
US20110302289A1 (en) * 2010-06-07 2011-12-08 Verizon Patent And Licensing Inc. Selection of a policy and charging rules function device

Similar Documents

Publication Publication Date Title
US11343288B2 (en) Telecommunications network call control
CN108476448B (zh) 一种业务处理方法及ims核心网设备
US8848666B2 (en) Handover of emergency calls from a circuit switched to a packet switched access network
EP3316603B1 (fr) Dispositif de communication et procédé de communication pour traiter les appels d'urgence d'ims dans une situation d'itinérance
US11025676B2 (en) Communication system
CN1859412B (zh) 一种演进网络中漫游用户ip地址的注册和业务使用方法
US20150098394A1 (en) Ims centralized services (ics) interworking function (iwf) system and method
EP2603037A1 (fr) Procédé de communication mobile et n ud de régulation de niveau de priorité
WO2015050547A1 (fr) Scénarios de mobilité volte avec des supports vocaux ims et non-ims
CN109661800A (zh) 用于将侦听相关信息与呼叫内容相关的方法和设备
US20140370834A1 (en) Disable of supplementary service on emergency in ims network
WO2016138940A1 (fr) Détermination de prise en charge de session voix sur ps lorsque les deux modèles d'itinérance sont pris en charge, point de rattachement et décrochage local
US11570215B2 (en) Technique for enabling signaling message correlation
US8908643B2 (en) Handover of priority calls from a circuit switched access network with single radio voice call continuity
WO2013025554A1 (fr) Système pour simplifier les déploiements d'un dispositif de contrôle d'un accès mobile sans licence en utilisant des services de voix sur ip
WO2017063668A1 (fr) Rétention de données pour itinérance à routage de rattachement s8
US9544756B2 (en) Home communication network determination
Tanaka Volte roaming and interconnection standard technology
US10904740B2 (en) Method of inbound roamer detection for networks supporting service domain centralization in IMS
Perez VoLTE and ViLTE: Voice and Conversational Video Services Over the 4G Mobile Network
KR20160084516A (ko) VoLTE(Voice over Long Term Evolution) 시스템 및 그 제어방법과 및 이 시스템에 포함되는 PGW(PDN Gateway) 및 CSCF(Call Session Control Function)과 그 제어방법
KR102124500B1 (ko) 영상통화를 위한 메시지 변환 방법 및 장치
JP2016178484A (ja) ネットワーク装置、基地局、通信システム、ベアラ確立方法、通信方法及びプログラム
WO2010092147A1 (fr) Appel d'urgence efficace dans l'architecture ims

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: 15778952

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15778952

Country of ref document: EP

Kind code of ref document: A1