# US 11,122,538 B2 · Diameter/XML protocol conversion

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 11,122,538 B2
- Document ID: US11122538B2
- Status: Granted
- Kind: B2
- Application number: 14/778,983
- Filed: 2014-03-28
- Published: 2016-02-25
- Granted: 2021-09-14
- Earliest claimed: 2013-04-26
- Assignees: Apple Inc.
- Applicants: Apple Inc.
- Inventors: Meghashree Kedalagudde; Chen-Ho Chin; Muthaiah Venkatachalam
- Web page: https://patentgrep.com/patent/US11122538B2

## CPC

- H04L 65/80: Responding to QoS
- H04J 11/00: Orthogonal multiplex systems, {e.g. using WALSH codes}(H04J13/00 takes precedence)
- H04J 11/0023: {Interference mitigation or co-ordination (direct sequence spread spectrum [DSSS] systems H04B1/7097; frequency hopping H04B1/713; allocation criteria for ingress interference avoidance H04L5/0062; frequency allocation criteria for requirements on out-of-channel emissions H04L5/0066; arrangements for removing intersymbol interference or baseband equalisers H04L25/03006; peak power aspects in multicarrier modulation H04L27/2614; power management H04W52/00; traffic scheduling H04W72/54, H04W72/541)}
- H04J 11/005: {of intercell interference}
- H04L 1/1671: {the supervisory signal being transmitted together with control information}
- H04L 1/1812: Hybrid protocols; Hybrid automatic repeat request [HARQ]
- H04L 5/0007: {the frequencies being orthogonal, e.g. OFDM(A) or DMT}
- H04L 5/0032: {Distributed allocation, i.e. involving a plurality of allocating devices, each making partial allocation}
- H04L 5/0033: {each allocating device acting autonomously, i.e. without negotiation with other allocating devices}
- H04L 5/005: {of common pilots, i.e. pilots destined for multiple users or terminals}
- H04L 5/0073: {Allocation arrangements that take into account other cell interferences}
- H04L 12/1407: {Policy-and-charging control [PCC] architecture}
- H04L 43/16: Threshold monitoring
- H04L 65/1016: IP multimedia subsystem [IMS]
- H04L 65/1045: Proxies, e.g. for session initiation protocol [SIP]
- H04L 65/1069: Session establishment or de-establishment
- H04L 65/1073: Registration or de-registration
- H04L 65/1104: Session initiation protocol [SIP]
- H04L 65/403: Arrangements for multi-party communication, e.g. for conferences (data switching systems for conference H04L12/18; arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities H04M3/56; television conferencing systems H04N7/15)
- H04L 65/65: Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
- H04L 65/762: {at the source (reformatting of additional data in video distribution servers H04N21/2355)}
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04N 7/141: {between two video terminals, e.g. videophone (telephonic communication systems combined with television receiver for reception of entertainment or information matter H04M11/085)}
- H04N 7/147: {Communication arrangements, e.g. identifying the communication as a video-communication, intermediate storage of the signals (selecting H04Q)}
- H04N 7/15: Conference systems
- H04W 4/70: Services for machine-to-machine communication [M2M] or machine type communication [MTC]
- H04W 8/005: {Discovery of network devices, e.g. terminals}
- H04W 8/22: Processing or transfer of terminal data, e.g. status or physical capabilities
- H04W 24/06: Testing, {supervising or monitoring} using simulated traffic
- H04W 28/0236: {radio quality, e.g. interference, losses or delay}
- H04W 36/0009: {for a plurality of users or terminals, e.g. group communication or moving wireless networks (user group management H04W4/08; processing of subscriber group data H04W8/186)}
- H04W 36/0058: {Transmission of hand-off measurement information, e.g. measurement reports}
- H04W 36/0066: {of control information between different types of networks in order to establish a new radio link in the target network}
- H04W 36/035: {in self-organising networks}
- H04W 48/18: Selecting a network or a communication service
- H04W 52/0212: {managed by the network, e.g. network or access point is leader and terminal is follower}
- H04W 52/0216: {using a pre-established activity schedule, e.g. traffic indication frame}
- H04W 52/08: Closed loop power control
- H04W 52/32: TPC of broadcast or control channels
- H04W 60/00: Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
- H04W 68/00: User notification, e.g. alerting and paging, for incoming communication, change of service or the like
- H04W 68/02: Arrangements for increasing efficiency of notification or paging channel
- H04W 72/0446: Resources in time domain, e.g. slots or frames
- H04W 72/20: Control channels or signalling for resource management
- H04W 72/52: based on load
- H04W 72/542: using measured or perceived quality
- H04W 76/14: Direct-mode setup
- H04W 76/27: Transitions between radio resource control [RRC] states
- H04W 76/28: Discontinuous transmission [DTX]; Discontinuous reception [DRX]
- H04W 76/36: for reassigning the resources associated with the released connections
- H04W 88/02: Terminal devices
- H04L 1/1861: {Physical mapping arrangements (for ACK signaling see also H04L5/0053)}
- H04L 5/0044: {Allocation of payload; Allocation of data channels, e.g. PDSCH or PUSCH}
- H04L 5/0055: {Physical resource allocation for ACK/NACK (for physical mapping arrangements in ARQ protocols H04L1/1861)}
- H04N 21/4728: for selecting a Region Of Interest [ROI], e.g. for requesting a higher resolution version of a selected region
- H04N 21/4788: communicating with other users, e.g. chatting {(arrangements for providing for computer conferences, e.g. chat rooms, to substation in data switching networks H04L12/1813; distributed application using peer-to-peer [P2P] networks H04L67/104)}
- H04N 21/6437: Real-time Transport Protocol [RTP]
- H04W 16/14: Spectrum sharing arrangements {between different networks}
- H04W 36/0064: {of control information between different access points}
- H04W 36/1443: {between licensed networks}
- H04W 48/06: based on traffic conditions
- H04W 52/146: {Uplink power control}
- H04W 52/242: {taking into account path loss}
- H04W 52/325: {Power control of control or pilot channels}
- H04W 72/04: Wireless resource allocation
- H04W 72/044: based on the type of the allocated resource
- H04W 72/0453: Resources in frequency domain, e.g. a carrier in FDMA
- H04W 72/21: in the uplink direction of a wireless link, i.e. towards the network
- H04W 72/23: in the downlink direction of a wireless link, i.e. towards a terminal
- H04W 76/18: Management of setup rejection or failure
- H04W 76/38: triggered by timers
- H04W 88/06: adapted for operation in multiple networks {or having at least two operational modes}, e.g. multi-mode terminals
- Y02D 30/70: in wireless communication networks
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04J: MULTIPLEX COMMUNICATION (transmission in general H04B; peculiar to transmission of digital information H04L5/00; systems for the simultaneous or sequential transmission of more than one television signal H04N7/08; in exchanges H04Q11/00; stereophonic systems H04S)
- H04N: PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- Y02D: CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE

## Abstract

Embodiments of protocol converters (PCs), and related techniques, are disclosed herein. In some embodiments, a PC may include reception logic to receive Extensible Markup Language (XML) data transmitted by an Application Function (AF), conversion logic to convert the XML data into a Diameter Protocol (DP) message, and provision logic to provide the DP message for transmission to a Policy and Charging Rules Function (PCRF). Other embodiments may be disclosed and/or claimed.

## Claims

### Claim 1

A protocol converter (PC), comprising:
one or more communication interfaces to receive Extensible Markup Language (XML) data transmitted by an Application Function (AF) and to provide a Diameter Protocol (DP) message for transmission to a Policy and Charging Rules Function (PCRF), the PCRF disposed in a Diameter realm; and
conversion logic to convert the XML data into the DP message,
wherein the PC is to operate separately from the PCRF but within the Diameter realm in which the PCRF is disposed and an interface of the one or more communication interfaces is to provide the DP message for transmission to the PCRF through a diameter routing agent (DRA) that is communicatively coupled with the plurality of PCRFs including the PCRF,
wherein the PC is configured to convert XML elements and groups including groups for supported features, subscription, sponsored connectivity, media components, and granted service, wherein the granted service XML group is nested in the sponsored connectivity XML group according to an XML schema.

### Claim 2 (depends on 1)

The PC of claim 1, wherein the XML data includes an Attribute Value Pair, AVP, element, and the AVP element includes an AVP-Parameters element, the AVP-Parameters element being included in the AVP element by a reference attribute but not explicitly including XML elements respectively representative of AVP code, flag, and length.

### Claim 3 (depends on 2)

The PC of claim 2, wherein the AVP-Parameters element is a required element of the AVP element according to an XML schema.

### Claim 4 (depends on 1)

The PC of claim 1, wherein:
the PC is different from a second PC configured to operate within a second Diameter realm; and
the Diameter realm and the second Diameter realm are within a common Third Generation Partnership Project, 3GPP, Public Land Mobile Network, PLMN.

### Claim 5 (depends on 1)

The PC of claim 1, wherein a first interface of the one or more communication interfaces is to receive the XML data, and a second interface of the one or more communication interfaces is to provide the DP message for transmission to the PCRF.

### Claim 6 (depends on 1)

The PC of claim 1, wherein the XML data includes a plurality of Attribute Value Pair, AVP, elements, and each AVP element of the plurality of AVP elements includes an AVP-Parameters element.

### Claim 7

A non-transitory computer-readable storage medium storing program instructions executable by one or more processors to cause a computing device to:
receive Extensible Markup Language (XML), data transmitted by an Application Function, AF;
convert the XML data into a Diameter Protocol (DP) message; and
generate a Diameter Protocol (DP) message for transmission to a Policy and Charging Rules Function (PCRF), disposed in a Diameter realm, based at least in part on the XML data;
wherein the computing device is configured to operate separately from the PCRF but within the Diameter realm in which the PCRF is disposed, and an interface of one or more communication interfaces of the computing device is to provide the DP message for transmission to the PCRF through a Diameter routing agent, DRA, that is communicatively coupled with a plurality of PCRFs including the PCRF,
wherein the computing device is configured to convert XML elements and groups including groups for supported features, subscription, sponsored connectivity, media components, and granted service, wherein the granted service XML group is nested in the sponsored connectivity XML group according to an XML schema.

### Claim 8 (depends on 7)

The non-transitory computer readable memory medium of claim 7, wherein the XML data includes an Attribute Value Pair, AVP, element, and the AVP element includes an AVP-Parameters element, the AVP-Parameters element being included in the AVP element by a reference attribute but not explicitly including XML elements respectively representative of AVP code, flag, and length.

### Claim 9 (depends on 7)

The computer readable memory storage medium of claim 7, wherein the AVP-Parameters element is a required element of the AVP element according to an XML schema.

### Claim 10 (depends on 7)

The non-transitory computer readable memory medium of claim 7, wherein:
the computing device is different from a second computing device configured to operate within a second Diameter realm; and
the Diameter realm and the second Diameter realm are within a common Third Generation Partnership Project, 3GPP, Public Land Mobile Network, PLMN.

### Claim 11 (depends on 7)

The non-transitory computer readable memory medium of claim 7, wherein a first interface of the one or more communication interfaces is to receive the XML data, and a second interface of the one or more communication interfaces is to provide the DP message for transmission to the PCRF.

### Claim 12 (depends on 7)

The non-transitory computer readable memory medium of claim 7, wherein the XML data includes a plurality of Attribute Value Pair, AVP, elements, and each AVP element of the plurality of AVP elements includes an AVP-Parameters element.

### Claim 13

A method, comprising:
by a computing device:
receiving Extensible Markup Language (XML), data transmitted by an Application Function, AF;
converting the XML data into a Diameter Protocol (DP) message; and
generating a Diameter Protocol (DP) message for transmission to a Policy and Charging Rules Function (PCRF), disposed in a Diameter realm, based at least in part on the XML data;
wherein the computing device is configured to operate separately from the PCRF but within the Diameter realm in which the PCRF is disposed, and an interface of one or more communication interfaces of the computing device is to provide the DP message for transmission to the PCRF through a Diameter routing agent, DRA, that is communicatively coupled with a plurality of PCRFs including the PCRF,
wherein the computing device is configured to convert XML elements and groups including groups for supported features, subscription, sponsored connectivity, media components, and granted service, wherein the granted service XML group is nested in the sponsored connectivity XML group according to an XML schema.

### Claim 14 (depends on 13)

The method of claim 13, wherein the XML data includes an Attribute Value Pair, AVP, element, and the AVP element includes an AVP-Parameters element, the AVP-Parameters element being included in the AVP element by a reference attribute but not explicitly including XML elements respectively representative of AVP code, flag, and length.

### Claim 15 (depends on 14)

The method of claim 14, wherein the AVP-Parameters element is a required element of the AVP element according to an XML schema.

### Claim 16 (depends on 13)

The method of claim 13, wherein:
the computing device is different from a second computing device configured to operate within a second Diameter realm; and
the Diameter realm and the second Diameter realm are within a common Third Generation Partnership Project, 3GPP, Public Land Mobile Network, PLMN.

### Claim 17 (depends on 13)

The method of claim 13, wherein a first interface of the one or more communication interfaces is to receive the XML data, and a second interface of the one or more communication interfaces is to provide the DP message for transmission to the PCRF.

### Claim 18 (depends on 13)

The method of claim 13, wherein the XML data includes a plurality of Attribute Value Pair, AVP, elements, and each AVP element of the plurality of AVP elements includes an AVP-Parameters element.

### Claim 19 (depends on 13)

The method of claims 13, further comprising:
transmitting the DP message to the PCRF.

### Claim 20 (depends on 14)

The method of claim 14, wherein the AVP element is a Session ID element having a string data type.

### Claim 21 (depends on 14)

The method of claim 14, wherein the AVP element is an Origin Host element, an Origin Realm element, a Destination Realm element, a Destination Host element or a Route Record element, and wherein the AVP element has a string data type.

### Claim 22

A computing device, comprising:
wireless communication circuitry; and
at least one processor coupled to the wireless communication circuitry and configured to cause the computing device to:
receive Extensible Markup Language (XML), data transmitted by an Application Function, AF;
convert the XML data into a Diameter Protocol (DP) message; and
generate a Diameter Protocol (DP) message for transmission to a Policy and Charging Rules Function (PCRF), disposed in a Diameter realm, based at least in part on the XML data;
wherein the computing device is configured to operate separately from the PCRF but within the Diameter realm in which the PCRF is disposed, and an interface of one or more communication interfaces of the computing device is to provide the DP message for transmission to the PCRF through a Diameter routing agent, DRA, that is communicatively coupled with a plurality of PCRFs including the PCRF,
wherein the computing device is configured to convert XML elements and groups including groups for supported features, subscription, sponsored connectivity, media components, and granted service, wherein the granted service XML group is nested in the sponsored connectivity XML group according to an XML schema.

### Claim 23 (depends on 22)

The computing device of claim 22, wherein the XML data includes an Attribute Value Pair, AVP, element, and the AVP element includes an AVP-Parameters element, the AVP-Parameters element being included in the AVP element by a reference attribute but not explicitly including XML elements respectively representative of AVP code, flag, and length.

### Claim 24 (depends on 23)

The computing device of claim 23, wherein the AVP-Parameters element is a required element of the AVP element according to an XML schema.

### Claim 25 (depends on 22)

The computing device of claim 22, wherein:
the computing device is different from a second computing device configured to operate within a second Diameter realm; and
the Diameter realm and the second Diameter realm are within a common Third Generation Partnership Project, 3GPP, Public Land Mobile Network, PLMN.

### Claim 26 (depends on 22)

The computing device of claim 22, wherein a first interface of the one or more communication interfaces is to receive the XML data, and a second interface of the one or more communication interfaces is to provide the DP message for transmission to the PCRF.