TWI726893B - Bearer binding in the presence of a ue-to-network relay - Google Patents

Abstract

A user equipment device (UE) may operate as a relay device (referred to as a relay UE) between other UEs (referred to as remote UEs) and a wireless telecommunications network. The wireless telecommunications network may allocate a bearer to the relay UE, and the remote UEs may initiate calls via an Internet Protocol (IP) multimedia subsystem (IMS) of a wireless telecommunications network. A Proxy Call Session Control Function (P-CSCF), a Packet Data Network (PDN) Gateway (PGW), and a Policy and Charging Rules Function (PCRF) may collaborate to bind the calls of the remote UEs to the bearer allocated to the relay UE in order to, for example, increase the number of UEs that may participate in calls via the relay UE.

Description

Carrier binding under the existence of a relay station from the user equipment to the network

The present invention relates to the carrier binding under the existence of the relay station of the user equipment to the network.

Background of the invention

Wireless networks can provide networking to mobile communication devices such as smart phones. Networking can be provided via a radio interface. Typically, the device can be connected to the network via an access point that is part of the network architecture. For example, the device can be connected to a cellular network through a cellular site, or connected to a wireless local area network (WLAN) through a WLAN access point (for example, a WiFi access point).

Some technologies allow devices to establish a direct communication path with each other (for example, without going through cellular stations or WiFi access points). For example, devices that are close to each other can explore each other and then establish a direct communication path with each other. Examples of direct communication technologies include, for example, in the technical report "3GPP TR 22.703, Technical Specifications for Group Services and Systems; Architecture Enhancement to Support ProSe) Research (Release 12)" (available from www.3gpp.org ) WiFi Direct standard or direct communication.

In some cases, the mobile communication device can be operated as another mobile Relay device between communication device and wireless network. For example, a first mobile communication device can establish a direct connection with a wireless network, and another connection with a second mobile communication device, for example, the second device is located outside the coverage area of the wireless network. The first mobile communication device can enter the relay mode, and the second mobile communication device can communicate with the wireless telecommunication network by relaying information between the second mobile communication device and the wireless network.

According to an embodiment of the present invention, a Proxy Call Session Control Function (P-CSCF) device is specifically proposed, which includes: a first network interface device for passing through a wireless telecommunication network A radio access network (RAN) to communicate with a user equipment device (UE); a second network interface device, the second network interface device is used to communicate with the wireless telecommunication network for a policy and billing Rules function (CRF) device communication; and the circuit for performing the following actions receives a Session Initiation Protocol (SIP) message, the SIP message includes a first indication that the SIP message originated from a remote UE, and the PCRF An Rx session is established or modified, and a request message is sent to the PCRF through the Rx session corresponding to a communication session of the remote UE, and the request message includes a description of at least one media stream.

100‧‧‧Environment

110‧‧‧User Equipment (UE)

115‧‧‧Evolved Node B (eNB)

120‧‧‧Service Gateway (SGW)

125‧‧‧Packet Data Network (PDN) Gateway (PGW)

130‧‧‧Mobile Management Entity (MME)

135‧‧‧Home User Server (HSS)

140‧‧‧Policy and Charging Rules Function (PCRF)

150‧‧‧Telephone Application Server (TAS)

155‧‧‧Proxy call session control function (P-CSCF)

300‧‧‧Method

310-370, 4.1, 4.2, 4.4, 4.6-4.8‧‧‧Block

4.3, 4.5‧‧‧ line

500‧‧‧Electronic device

502‧‧‧Application Circuit

503‧‧‧Storage Media

504‧‧‧Baseband circuit

504a-d‧‧‧Baseband processor

504e‧‧‧Central Processing Unit (CPU)

504f‧‧‧Audio Digital Signal Processor (DSP)

504g‧‧‧Memory/Storage Device

506‧‧‧Radio Frequency (RF) Circuit

506a‧‧‧Mixer circuit

506b‧‧‧Amplifier circuit

506c‧‧‧Filter circuit

506d‧‧‧Synthesizer circuit

508‧‧‧Front End Module (FEM) Circuit

560‧‧‧antenna

600‧‧‧device

610‧‧‧Processor circuit

620‧‧‧Memory and/or storage media

630‧‧‧Communication interface

640‧‧‧Communication circuit

650‧‧‧Input circuit

660‧‧‧Output circuit

The embodiments described herein will be more clearly understood through the detailed description part later in conjunction with the accompanying drawings. To assist the description herein, similar element symbols may indicate similar structural elements. The embodiment is illustrated by the drawings but not restrictive.

Figure 1 is a system in which the system and/or method described herein can be built Sketch of an example; Figure 2 is a sketch of an example of a device and interface that can be used to establish a call to a remote user equipment device (UE); Figure 3 is a sketch illustrating an example of a method of establishing a call to a remote UE; Figure 4 is a sequence The flowchart illustrates an example of a method for establishing a call for a remote UE; FIG. 5 illustrates an example of components of an electronic device for an embodiment; and FIG. 6 is a schematic diagram of an example of components of a device.

Detailed description of the preferred embodiment

The following detailed description refers to the accompanying drawings. The same component symbols in different drawings can identify the same or similar components. It should be understood that other embodiments can be used and structural or logical changes can be made without departing from the scope disclosed herein. Therefore, the following detailed description is by no means taken as restrictive, and the scope of the embodiments is defined by the scope of the attached patent application and its equivalent scope.

A user equipment device (UE) can operate as a relay device between one or more UEs (referred to herein as remote UEs) and a wireless telecommunication network (referred to herein as relaying UEs or UEs to a network relay station). However, currently available relay technologies may include certain limitations. For example, the UE can only act as a relay device for a limited number of UEs.

For example, the remote UE can be connected to the relay UE and participate in the call through the Internet Protocol (IP) Multimedia Subsystem (IMS) of the wireless telecommunication network. Every time a remote UE participates in such a call, the wireless telecommunication network can respond to the call Called to create a new bearer. However, because the relay UE can only support a limited number of bearers at any one time (for example, 8 or 11, depending on the third-generation partnership project (3GPP) specifications), the relay UE can The number of remote UEs participating in the call is limited. Therefore, the way in which the wireless telecommunication network establishes a call from a remote UE may limit the number of remote UEs that a relay UE can support.

The technology described herein enables a relay UE to support a large number of remote UEs by using a call initiated by a remote UE to bind to an existing bearer. For example, a relay UE may establish a packet data network (PDN) connection with a wireless telecommunication network, and the wireless telecommunication network may include a bearer assigned to the relay UE. The remote UE can be connected to the relay UE and can be registered with an IMS of the wireless telecommunication network as the remote UE.

The remote UE may initiate a call through the IMS, which may include providing the IMS with call quality (for example, quality of service (QoS)) for the call. The IMS can notify a core network of the wireless telecommunication network of the call and the call quality associated with the call. The core network can determine that any bearer (with the call quality) has been generated for the relay UE. If such a bearer does not currently exist, the core network can generate a new bearer to respond to the call. Conversely, if such a bearer has been created, the core network can bind the call to the existing bearer, and can modify the existing bearer to respond to the call (and call quality) added to the bearer. Therefore, by combining calls from remote UEs onto the same bearer, the techniques described herein can increase the number of remote UE calls that can be supported by a relay UE.

Figure 1 is a schematic diagram of an example of an environment 100 in which the systems and/or methods described herein can be built. Environment 100 may include user equipment (UE) 110, one or more radio access networks (RAN), wireless telecommunication networks, and one or more external networks. The wireless telecommunication network may include an evolved packet system (EPS), which includes a long-term evolution (LTE) network and/or an evolved packet core (EPC) network operating based on the 3GPP wireless communication standard. The LTE network may be or include a RAN including one or more stations, some or all of which may be in the form of an evolved node B (eNB) 115, through which the UE 110 can communicate with the EPC network.

The EPC network may include a service gateway (SGW) 120, a packet data network (PDN) gateway (PGW) 125, a mobile management entity (MME) 130, a home user server (HSS) 135, and/or policies And charging rules function (PCRF) 140. As shown in the figure, the EPC network enables the UE 110 to communicate with external networks, such as a public land mobile network (PLMN), a public switched telephone network (PSTN), and/or an IP network (for example, the Internet).

The wireless telecommunication network may also include an IMS core, which may include a telephone application server (TAS) 150 and a proxy call session control function (P-CSCF) 155. In several implementations, the IMS core may include additional devices, such as other call session control function (CSCF) devices, media servers, application servers, and so on. The IMS core can help deliver IP multimedia services, such as voice over IP (VoIP) services, video call services, etc., to the UE 110. In addition, the IMS core can operate based on the 3GPP wireless communication standard.

The UE 110 may include a portable computing and communication device, such as a personal digital assistant (PDA), a smart phone, a cellular phone, a laptop computer, a tablet computer, etc. having connectivity to a wireless telecommunication network. UE 110 may also include non-portable computing devices, such as desktop computers, consumer electronics or Enterprise electronics, smart TVs, or other devices that have the ability to connect to wireless telecommunication networks. The UE 110 may also include a computing and communication device (also called a wearable device) that can be worn by a user as a watch, health belt, necklace, glasses, ring, belt, earphone, or other types of wearable devices. The UE 110 can engage in one or more of the operations described herein, such as establishing a device-to-device (D2D) connection with another UE 110 and operating as a proxy UE or operating as a remote UE. In addition, the UE 110 can participate in calls supported by the wireless telecommunication network (e.g., IMS calls), which may include the use of appropriate protocols, such as Session Initiation Protocol (SIP).

The eNB 115 may include one or more network devices that receive, process, and/or send data streams destined for the UE 110 and/or received from the UE 110. The eNB 115 can receive the data stream from the SGW 120 and the PGW 125, and/or send the data stream to the external network or other devices. The eNB 115 can send a data stream to and/or receive a data stream from the UE 110 through an air interface.

The SGW 120 can aggregate data streams received from one or more eNBs 115, and can send the aggregated data streams to another network or device through the PGW 125. In addition, the SGW 120 may aggregate data streams received from one or more PGW 125, and may send aggregate data streams to one or more eNBs 115. The SGW 120 can operate as an anchor for the user plane during eNB handover and as an anchor for mobility between different telecommunication networks. The PGW 125 may include one or more network devices, which can aggregate data streams received from one or more SGW 120, and can send aggregate data streams to an external network or another device. The PGW 125 can also or alternatively receive a data stream from an external network and can send the data stream toward the UE 110 (via the SGW 120 and/or the eNB 115).

The MME 130 may include one or more computing and communication devices that serve as the control node of the eNB 115 and/or provide an air interface to the wireless telecommunication network to other devices. For example, the MME 130 can operate to register the UE 110 in the wireless telecommunication network to establish a bearer channel (for example, data stream flow) associated with the UE 110 session, and hand over the UE 110 to different eNBs and MMEs. , Or other networks, and/or engage in other operations. The MME 120 may perform supervisory operations on the data stream destined to and/or received from the UE 110.

The HSS 135 may include one or more devices that manage, update, and/or store profile information associated with the user (for example, the user associated with the UE 110) in the memory associated with the HSS 135. The profile information can identify the applications and/or services that are permitted to be used by the user and/or the user can access; the mobile phone number (MDN) associated with the user; the bandwidth or data rate threshold value associated with the application and/or service ; And/or other information. The user may be associated with the UE 110. In addition, or in addition, the authentication, authorization, and/or counting operations of the HSS 135 associated with the user and/or the communication session with the UE 110.

The PCRF 140 may include one or more devices, which may receive relevant strategies and/or subscription information from one or more sources, such as a user database and/or from one or more users. The PCRF 140 can provide these policies to the PGW 125 or another device so that the policies can be executed. As depicted in the figure, in some implementations, PCRF 140 can communicate with PGW 125 to ensure that charging policies are properly applied to local routing sessions within the telecommunications network. For example, after a local routing session ends, the PGW 125 may collect charging information about the session, and provide the charging information to the PCRF 140 for execution.

PCRF 140 can also perform additional operations described herein. For example, the PCRF 140 can communicate with the PGW 125 to establish a Gx session for the relay UE 110 (for example, a session involving the Gx interface of the 3GPP wireless communication standard). In another example, the PCRF 140 can communicate with the P-CSCF 155 to establish an Rx session for the remote UE 110 (for example, a session involving the Rx interface of the 3GPP wireless communication standard). In yet another example, the PCRF 140 can identify (or cause the PGW 125 to identify) that is associated with the relay UE 110 and is suitable (e.g., a bearer that has been associated with the QoS of the call) for processing from the remote UE An existing bearer of a call at 110 (for example, an EPS bearer). In addition, PCRF 140 can modify (or make PGW 125 modify) the capacity of existing bearers to handle new calls. In the case that no bearer is suitable for processing a new call, PCRF 140 can generate a new bearer for the call; however, PCRF 140 can be configured to prioritize and map the new call to the existing bearer (instead of generating a new bearer). ) In order to increase the number of remote UE 110 that can be served by the relay UE 110.

The TAS 150 may include one or more computing and communication devices that provide IP calling (eg, VoIP) services. TAS 150 can translate a phone number into an IP address and/or translate an IP address into a phone number to establish a call. TAS 150 can also provide call routing services and/or call bridging services. TAS 150 can also provide answering machine services, forwarding services, and free call routing services (for example, for so-called "1-800" numbers). The TAS 150 can operate based on a specific communication protocol such as SIP.

The P-CSCF 155 may include a computing and communication device that can collect, process, search, store, and/or provide information in the manner described herein. The P-CSCF 155 can operate as the first contact point of the IMS core. For example, The SIP message from the UE 110 to the IMS core can be intercepted by the P-CSCF 155 first. In some implementations, the communication between the UE 110 and the P-CSCF 155 may involve a specific interface, such as the Gm interface of the 3GPP wireless communication standard (not shown in the figure).

The number and arrangement of devices and/or networks illustrated in Figure 1 are for explanatory purposes only. In fact, there may be additional devices and/or networks compared to those illustrated in Figure 1; fewer devices and/or networks; different devices and/or networks; or different arrangements of devices and/or networks . Additionally, or in addition, one or more of the devices illustrated in FIG. 1 may perform one or more functions described as being performed by the other one or more of the devices illustrated in FIG. 1. The exemplified devices can be interconnected through a wired connection, a wireless connection, or a combination of wired and wireless connections.

FIG. 2 is a schematic diagram of an example of a device and interface that can be used to establish a call to a remote UE 110. As shown in the figure, examples of devices may include remote and relay UE 110, PGW 125, PCRF 140, and P-CSCF 155, examples of which are as described above with reference to FIG. 1. Examples of interfaces include Gx interface, Gm interface, and Rx interface.

The relay UE 110 may establish a PDN connection involving the PGW 125. In doing so, the relay UE 110 may be assigned an IPv6 address with a shortened prefix such as the /56 prefix. When establishing a PDN connection, the PGW 125 can establish a communication session with the PCRF 140 through the Gx interface, which can include the IPv6 prefix of the PGW 125 communication relay UE 110 to the PCRF 140. This communication session can be referred to as a Gx session. The establishment of the PDN connection may enable a bearer (for example, an EPS bearer) to be allocated to the relay UE 110.

The remote UE 110 can discover and establish a D2D connection with the relay UE 110 Knot. In some embodiments, the connection may be an LTE direct connection, a ProSe connection, or the like. In addition, the relay UE 110 can allocate an IPv6 address to the remote UE 110. In some embodiments, the relay UE 110 may use IPv6 prefix authorization to allocate an IP version 6 (IPv6) address with a longer prefix, such as a /64 prefix, to the remote UE 110. In addition, other remote UEs 110 connected to the relay UE 110 can be assigned IPv6 addresses (and prefixes) in a similar manner, so that the longer IPv6 prefixes of all remote UEs 110 can be logically aggregated into the shorter ones of the relay UE 110. The IPv6 prefix, which will be described in detail later, is meaningful for the PCRF 140 to map the call initiated by the remote UE 110 to the bearer assigned to the relay UE 110.

The remote UE 110 can register for the IMS service by communicating with the P-CSCF 155 through the Gm interface. When registering, the remote UE 110 can indicate to the P-CSCF 155 that the remote UE 110 is operating as a remote device (for example, communicating through the relay UE 110). Then, the P-CSCF 155 can establish a communication session with the PCRF 140 through the Rx interface. The communication session can be referred to as an Rx session. In some embodiments, the P-CSCF 155 may indicate to the PCRF 140 that the Rx session corresponds to the remote UE 110 (for example, the UE 110 operates as the remote UE 110). Establishing the Rx session may include the P-CSCF 115 transmitting the IPv6 prefix of the remote UE 110 to the PCRF 140, which enables the PCRF 140 to engage in session binding by mapping the Rx session of the remote UE 110 to the Gx session of the relay UE 110. For example, because the IPv6 prefix of the remote UE 110 can be based on the IPv6 prefix of the relay UE 110 (through IPv6 prefix authorization), the PCRF 140 can use the IPv6 prefix of the remote UE 110 to identify the IPv6 address of the relay UE 110. In addition, because the IPv6 prefix of the remote UE 110 can be sent to the PCRF 140 when the Rx session is established, and the IPv6 address of the relay UE 110 can be It is sent to the PCRF 140 when the Gx session is established, and the PCRF 140 can map the Rx session of the remote UE 110 to the Gx session of the relay UE 110.

After the IMS session is established, the remote UE 110 may send a request to the P-CSCF 155 to establish a call (for example, an IMS call) with another UE. The request may include an instruction from the remote UE 110 and/or information describing the call quality level (also referred to as call quality information herein). Examples of such information may include QoS information and allocation and reservation order (ARP) information. The PCRF 140 can update the Rx session according to the call quality information, and can include the P-CSCF 155 to indicate to the PCRF 140 that the call request is from the remote UE 110.

Then, PCRF 140 can instruct PGW 125 to perform bearer binding by binding the IP flow corresponding to the call with a bearer. The bearer may: 1) allocate to the relay UE 110; and 2) include one or Multiple other IP streams, which may include the quality level for the newly requested call. If there is such a bearer, the PGW 125 can modify the bearer to respond to the newly added IP stream, while still responding to the quality level of the call already associated with the bearer. If there is no such bearer, the PGW 125 can generate a new bearer for the IP flow corresponding to the call.

3 is a schematic diagram illustrating an example of a method 300 for establishing a call (or another type of communication session) for the remote UE 110. The method 300 can be implemented by one or more network devices, such as PGW 125, PCRF 140, and P-CSCF 155.

The method 300 may include establishing a Gx session for the relay UE 110 (block 310). For example, the relay UE 110 may establish a PDN connection with the wireless telecommunication network, which may include a Gx session established between the PGW 125 and the PCRF 140. Establishing a Gx session may include allocating a relay UE 110 can use to communicate with the radio A carrier (for example, an EPS carrier) of Internet communications. In some embodiments, the Gx session may include an IP Connectivity Access Network (IP-CAN) session, and the bearer may include an IP-CAN bearer. In some embodiments, establishing a Gx session may include the IPv6 of the relay UE 110 transmitted from the PGW 125 to the PCRF 140.

The method 300 may also include registering the remote UE 110 for IMS services (block 320). For example, the P-CSCF 155 may receive a request from the remote UE 110 to register with the IMS of the wireless telecommunication network. The request to register the remote UE 110 for the IMS service may include an indication (for example, one or more parameters) indicating that the request originated from the remote UE 110. In some implementations, the request may include the SIP REGISTER message, and may include the IPv6 prefix of the remote UE 110.

The method 300 may also include establishing an Rx session for the remote UE 110 (block 330). For example, the P-CSCF 155 can establish a communication session with the PCRF 140. The establishment of the Rx session may include the P-CSCF 155 communication session request message (for example, [Rx] verification-authorization request (AA-REQUEST) message) to the PCRF 140. In some embodiments, the request message may include an indication (for example, one or more parameters) that indicates the request originating from the remote UE 110 (as opposed to a UE operating in another operating mode or situation).

The method 300 may also include session binding between the Gx session of the relay UE 110 and the Rx session of the remote UE 110 (block 340). For example, when a Gx session is established for the relay UE 110, the PCRF 110 may receive the IPv6 address of the relay UE 110 (which includes the IPv6 prefix). Similarly, when an Rx session is established for the remote UE 110, the PCRF 140 can receive the IPv6 prefix of the remote UE 110. In addition, because the IPv6 prefix of the remote UE 110 has been allocated to the remote UE 110 based on the IPv6 prefix of the relay UE 110, the PCRF 140 can be based on the UE 110’s IPv6 prefix. The IPv6 prefix determines the Gx session corresponding to the Rx session. Once the Rx session and the corresponding Gx session have been identified, the PCRF 140 can engage in session binding by logically mapping the Rx session to the Gx session.

The method 300 may also include receiving a request to establish a call between the remote UE 110 and another UE 110 (block 350). For example, the P-CSCF 140 may receive a request from the remote UE 110 to establish a call with another UE 110 (for example, a VoIP call). In some implementations, the request to establish a call may include a SIP INVITE message. In addition, the request may indicate a request originating from a remote UE 110 (as opposed to, for example, a UE device operating as a relay device or operating in a standard operating mode).

The method 300 may also include updating the Rx session of the remote UE 110 (block 360). For example, in response to receiving a request from the remote UE 110 to establish a call with another UE 110, the P-CSCF 140 may update the Rx session established when the remote UE 110 registers for the IMS service. In some embodiments, updating the Rx session may include identifying information describing the quality level of the accompanying call (for example, in the request to establish the call). Examples of such information may include QoS parameters, ARP parameters, guaranteed bit rate (GBR) parameters, and/or another type of information describing the quality level that must accompany the call. In some embodiments, the QoS parameters may include QoS class identifier (QCI). The updated Rx session may also include communication quality information and/or identification information of the remote UE 110 to the PCRF 140. In some embodiments, the P-CSCF 155 can use the AA-REQUEST message to the PCRF 140 to send the information to the PCRF 140.

The method 300 may also include performing bearer binding for the call (block 370). For example, PCRF 140 can generate policy and charging control (PCC) rules and/or QoS rules (also known as PCC/QoS rules), and transmit the PCC/QoS rules to PGW 125. In some embodiments, the PCC/QoS rules may instruct the PGW 125 to associate a new IP flow initiated by the remote UE 110 with a bearer that has one or more of the same qualities as the new IP flow. Other IP flows (e.g., QCI, ARP, etc.). In addition, the PCC/QoS rules can instruct the PGW 125 to generate a new bearer for the new IP flow. In some embodiments, the PCRF 140 can use the CC-REQUEST message to send the PCC/QoS rule to the PGW 125, which can also include quality information for the call (for example, QCI, ARP, etc.) and/or the call corresponding remote An indication from the end UE 110. In some embodiments, the quality information and the indication that the call corresponds to the remote UE 110 may be part of the PCC/QoS rules.

Therefore, the PGW 125 can determine whether the existing bearer (e.g., the EPS bearer associated with the relay UE 110) includes the same quality (e.g., QCI) corresponding to the corresponding new IP flow of the call initiated by the remote UE 110 , ARP, etc.). If such a bearer does not currently exist, the PGW 125 can generate a new bearer (associated with the relay UE 110) and can allocate a new IP stream to the new bearer. However, if such a bearer does exist, the PGW 125 can aggregate the new IP flow to the existing bearer (or the IP flow to the existing bearer). In some embodiments, when a new IP stream is aggregated to an existing carrier, the PGW 125 can modify the carrier (for example, network resources associated with the carrier) to ensure that the carrier can respond to all IPs associated with the carrier The quality of flow.

FIG. 4 is a sequence flowchart illustrating an example of a method for establishing a call for the remote UE 110. As shown in the figure, the example in FIG. 4 may include remote UE 110, relay UE 110, MME 130, SGW/PGW 120/125, PCRF 140, And P-CSCF 155. The example of the device shown in FIG. 4 is as described above with reference to FIG. 1.

As depicted in the figure, the relay UE 110 may establish a PDN connection with the wireless telecommunication network, which may involve several network devices, such as MME 130, SGW/PGW 120/125, and/or PCRF 140 (block 4.1). When establishing a PDN connection, the relay UE 110 may be assigned an IPv6 address, which may include a shortened IPv6 prefix, such as the /56 prefix. In addition, the PDN connection may include an IP-CAN session between the PGW 125 and the PCRF 140 (also referred to as a Gx session herein), which may include the PGW 125 to relay the IPv6 address of the UE 110 to the PCRF 140.

The remote UE 110 can discover and connect to the relay UE 110 (block 4.2). The connection between the remote end and the relay UE 110 may include a ProSe connection, a point-to-point (P2P) connection, a D2D connection, an LTE direct connection, and so on. When the connection is established, the relay UE 110 can allocate an IPv6 address to the remote UE 110. The IPv6 address allocated to the remote UE 110 may include one of the IPv6 prefixes based on the IPv6 address allocated to the remote UE 110. For example, the relay UE 110 can use the IPv6 prefix grant to allocate an IPv6 prefix to the remote UE 110. The prefix is a version longer than the IPv6 prefix of the relay UE 110 (for example, the /64 prefix). As described above, doing so can enable the PCRF 140 to map the Rx session of the remote UE 110 to the Gx session of the relay UE 110.

At a certain point, the remote UE 110 may send a request to register with the IMS of the wireless telecommunication network. As shown in the figure, P-CSCF 155 can receive the request. In addition, the request may include a SIP REGISTER message, which includes a parameter indicating that the request is from a UE operating as a remote UE (also referred to herein as relay information or relay parameters) (line 4.3).

In response to the registration request, the P-CSCF 155 can communicate with the PCRF 140 to establish an Rx session for the remote UE 110 (block 4.4). In some embodiments, establishing an Rx session may include the P-CSCF 155 sending an AA-REQUEST request to the PCRF 140 through the Rx interface. As shown in the figure, establishing an Rx session may include P-CSCF 155 and PCRF 140 sharing relay parameters.

At a certain point after the remote UE 110 has registered for the IMS service and has established an Rx session, the remote UE 110 may communicate with another UE for a request to initiate a call. In some implementations, the request may include a SIP INVITE message. In addition, the request to initiate a call may include information indicating the quality level of the call. As described above, examples of such information may include QCI, ARP information, and so on.

Depending on the embodiment, the request to register for the IMS service and/or the request to initiate a call may include an indication that the request originated from a UE operating as a remote UE. For example, in some embodiments, only the request to register for the IMS service or the request to initiate a call may include an indication that the request originated from a UE operating as a remote UE. However, as shown in the figure, in some embodiments, the remote UE 110 may include the indication (for example, relay parameters) in both requests (ie, the request to register for the IMS service or the request to initiate a call).

In response to the request to initiate the call, P-CSCF 155 and PCRF 140 can update the Rx session using relay parameters (block 4.6). For example, the P-CSCF 155 can use the Rx interface to send the AA-REQUEST message to the PCRF 140. The AA-REQUEST may include quality information (for example, QCI, ARP information, etc.) and/or relay parameters included in the SIP INVITE message from the remote UE 110. Therefore, PCRF 140 can become aware of: 1) The source of the call request From the remote UE 110; and 2) The corresponding call includes a certain quality level.

As shown in the figure, PCRF 140 and PGW 125 can update the Gx session (block 4.7). For example, the PCRF 140 can generate instructions (also referred to as PCC/QoS rules in this document) about how the PGW 125 should manage the new IP flow corresponding to the call requested by the remote UE 110. In some embodiments, the PCRF 140 can send commands to the PGW 125 through the Gx interface using CC-REQUEST messages. The instructions may include mapping the new IP flow of the call to a bearer that can respond to one of the quality levels of the requested call. The instructions may also include preference for aggregating the new IP flow of the call to the IP flow of the existing carrier, which may have the same quality level as the new IP flow; and/or preference for modifying the existing carrier (for example, the network resources of the existing carrier) ) To meet the quality level of the new IP stream. For example, if the new IP flow includes GBR, the resources of the existing bearer can be increased in a commensurate manner with the GBR corresponding to the new IP flow. In some embodiments, if a bearer associated with an IP flow with the same quality level as the new IP flow does not yet exist, the instruction may include forming a new bearer for the new IP flow.

For the purpose of explaining the example of FIG. 4, suppose there is a bearer associated with an IP flow of the same quality level as the new IP flow. In this way, new IP flows can be allocated to existing bearers. In addition, the existing bearer can be modified to ensure that, in addition to maintaining the quality level of the IP stream that has been allocated to the bearer, the existing bearer can respond to the requested quality level for the new IP stream (block 4.8).

As used herein, the term "circuit" or "processing circuit" can refer to, be part of, or include application-specific integrated circuits (ASIC), electronic circuits, processors (shared, dedicated, or group), and/or execution Memory (shared, dedicated, or group), combination of one or more software or firmware programs Logic circuits, and/or other suitable hardware components that provide the functionality. In other embodiments, the circuit may be built in one or more software or firmware modules or functions associated with circuits built by these modules. In some embodiments, the circuit may include logic that is at least partially operable in hardware.

The embodiments described herein can be built into the system using any suitably configured hardware and/or software. FIG. 5 illustrates an example of components of the electronic device 500 for one embodiment. In some embodiments, the electronic device 500 may be a user equipment (UE), an eNB, or a number of other suitable electronic devices. In some embodiments, the electronic device 500 may include an application circuit 502, a baseband circuit 504, a radio frequency (RF) circuit 506, a front-end module (FEM) circuit 508, and one or more antennas 560, at least coupled together as shown in the figure .

The application circuit 502 may include one or more application processors. For example, the application circuit 502 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and special-purpose processors (eg, graphics processors, application processors, etc.). The processor may be coupled and/or may include a memory/storage device, such as a storage medium 503, and may be configured to execute instructions stored in the memory/storage device to enable various applications and/or operating systems to run on the system run. In some implementations, the storage medium 503 may include a non-transitory computer readable medium. In some embodiments, the application circuit 502 may be connected to or include one or more sensors, such as environmental sensors, cameras, and so on.

The baseband circuit 504 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The baseband circuit 504 may include one or more baseband processors and/or control logic to process the interface received from the RF circuit 506 Receive the fundamental frequency signal of the signal path, and generate the fundamental frequency signal for the transmit signal path of the RF circuit 506. The baseband processing circuit 504 can interface with the application circuit 502 for generating and processing baseband signals and for controlling the operation of the RF circuit 506. For example, in some embodiments, the baseband circuit 504 may include a second-generation (2G) baseband processor 504a, a third-generation (3G) baseband processor 504b, and a fourth-generation (4G) baseband processor. 504c, and/or a baseband processor 504d for other current generations, developing generations, or future generations (for example, fifth generation (5G), 5G, etc.). The baseband circuit 504 (for example, one or more baseband processors 504a-d) can process various radio control functions that enable it to communicate with one or more radio frequency networks through the RF circuit 506. Radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some implementations, the baseband circuit 504 may be associated with the storage medium 503 or other storage medium.

In some embodiments, the modulation/demodulation circuit of the baseband circuit 504 may include fast Fourier transform (FFT), precoding, and/or cluster mapping/demapping functions. In some embodiments, the encoding/decoding circuit of the baseband circuit 504 may include convolution, tail-biting convolution, vortex, Viterbi, and/or low-density parity check (LDPC) encoder/decoder functions . The embodiments of modulation/demodulation and encoder/decoder functions are not limited to these examples but may include other suitable functions in other embodiments. In some embodiments, the baseband circuit 504 may include protocol stacking elements. For example, the E-UTRAN protocol includes, for example, physical (PHY), medium access control (MAC), radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), and/or Radio Resource Control (RRC) components. Baseband circuit 504 A central processing unit (CPU) 504e can be configured to run protocol stacking components for PHY, MAC, RLC, PDCP, and/or RRC layer signaling. In some embodiments, the baseband circuit may include one or more audio digital signal processors (DSP) 504f. The audio DSP 504f may include compression/decompression and echo cancellation components, and other suitable processing components may be included in other embodiments.

The baseband circuit 504 may further include a memory/storage device 504g. The memory/storage device 504g can be used to load and store data and/or instructions for operations performed by the processor of the baseband circuit 504. For one embodiment, the memory/storage device may include any combination of electrical memory and/or non-electrical memory. The memory/storage device 504g may include any combination of various levels of memory/storage devices, including, but not limited to, read-only memory (ROM) (for example, firmware) with embedded software commands, random access memory Storage (for example, dynamic random access memory (DRAM)), cache, buffer, etc. The memory/storage device 504g can be shared among various processors or dedicated to a specific processor.

In some embodiments, the components of the baseband circuit can be conveniently combined into a single chip, a single chip group, or arranged on the same circuit board. In some embodiments, some or all of the components of the baseband circuit 504 and the application circuit 502 can be built together, for example, on a single chip system (SOC).

In some embodiments, the baseband circuit 504 can be used for communication compatible with one or more radio frequency technologies. For example, in some embodiments, the baseband circuit 504 can support and evolve the universal terrestrial radio access network (E-UTRAN) and/or other wireless metropolitan area networks (WMAN), wireless local area network (WLAN) ), wireless personal area network (WPAN) communication. The embodiment in which the baseband circuit 504 is configured to support radio communication of more than one wireless protocol can be referred to as a multi-mode baseband circuit.

The RF circuit 506 can enable the use of modulated electromagnetic radiation through non-solid media to communicate with the wireless network. In various embodiments, the RF circuit 506 may include switches, filters, amplifiers, etc. to assist in communicating with the wireless network. The RF circuit 506 may include a receiving signal path, which may include a circuit for down-converting the RF signal received from the FEM circuit 508 and providing a baseband signal to the baseband circuit 504. The RF circuit 506 may also include a transmission signal path, which may include a circuit for up-converting the baseband signal provided by the baseband circuit 504 and providing an RF output signal to the FEM circuit 508 for transmission.

In some embodiments, the RF circuit 506 may include a receiving signal path and a transmitting signal path. The receive signal path of the RF circuit 506 may include a mixer circuit 506a, an amplifier circuit 506b, and a filter circuit 506c. The transmit signal path of the RF circuit 506 may include a filter circuit 506c and a mixer circuit 506a. The RF circuit 506 may also include a synthesizer circuit 506d for synthesizing a frequency for use by the mixer circuit 506a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuit 506a of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 508 based on the synthesized frequency provided by the synthesizer circuit 506d. The amplifier circuit 506b can be configured to amplify the down-converted signal, and the filter circuit 506c can be a low-pass filter (LPF) or a band-pass filter (BPF) configured to remove the undesired signal from the down-converted signal. Generate output fundamental frequency signal.

The output baseband signal may be provided to the baseband circuit 504 for further processing. In some embodiments, the output fundamental frequency signal may be a zero frequency fundamental frequency signal. In some embodiments, the mixer circuit 506a of the receiving signal path can be a passive mixer, but the scope of the embodiments is not limited in this aspect.

In some embodiments, the mixer circuit 506a of the transmit signal path can be configured to up-convert the input baseband signal based on the synthesized frequency provided by the synthesizer circuit 506d to generate the RF output signal for the FEM circuit 508. The baseband signal can be provided by the baseband circuit 504 and can be filtered by the filter circuit 506c. The filter circuit 506c may include a low-pass filter (LPF), but the scope of the embodiment is not limited to this aspect.

In some embodiments, the mixer circuit 506a of the receive signal path and the mixer circuit 506a of the transmit signal path may include two or more mixers and may be configured for quadrature down-conversion and/or up-conversion, respectively. In some embodiments, the mixer circuit 506a of the receive signal path and the mixer circuit 506a of the transmit signal path may include two or more mixers and may be configured for image rejection (eg, Harley image rejection). ). In some embodiments, the mixer circuit 506a and the mixer circuit 506a of the receive signal path can be configured for direct down-conversion and/or direct up-conversion, respectively. In some embodiments, the mixer circuit 506a of the receive signal path and the mixer circuit 506a of the transmit signal path can be configured for superheterodyne operation.

In some embodiments, the output fundamental frequency signal and the input fundamental frequency signal may be analog fundamental frequency signals, but the scope of the embodiments is not limited in this aspect. In some alternative embodiments, the output fundamental frequency signal and the input fundamental frequency signal may be digital fundamental frequency signals. In these alternative embodiments, the RF circuit 506 may include an analog-to-digital converter (ADC) and a digital-to-analog converter (DAC) The circuit, and the baseband circuit 504 may include a digital baseband interface to communicate with the RF circuit 506.

In some dual-mode embodiments, separate radio frequency IC circuits can be provided for processing signals for each spectrum, but the scope of the embodiments is not limited to this aspect.

In some embodiments, the synthesizer circuit 506d may be a fractional-N synthesizer or a fractional N/N+6 synthesizer, but the scope of the embodiment is not limited to this aspect, because other types of frequency synthesizers may be suitable . For example, the synthesizer circuit 506d can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

The synthesizer circuit 506d can be configured to synthesize the output frequency based on the frequency input and the divider control input for use by the mixer circuit 506a of the RF circuit 506. In some embodiments, the synthesizer circuit 506d may be a fractional N/N+6 synthesizer.

In some embodiments, the frequency input can be provided by a voltage controlled oscillator (VCO). Depending on the desired output frequency, the divider control input can be processed by the baseband circuit 504 or the application circuit 502. In some embodiments, the divider control input (eg, N) can be determined from the look-up table based on the channel indicated by the application circuit 502.

The synthesizer circuit 506d of the RF circuit 506 may include a divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD can be configured to divide the input signal by N or N+6 (for example, based on execution) to provide fractional division Fabi. In some embodiments, the DLL may include a set of cascade, tunable, delay elements, phase detectors, charge pumps, and D-type flip-flops. In these embodiments, the delay elements can be configured to break a VCO cycle into Nd equal phase packets, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

In some embodiments, the synthesizer circuit 506d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (for example, double carrier frequency, quadruple carrier frequency) , And combined with the quadrature generator and divider circuit to generate multiple signals at the carrier frequency, which have different phases relative to each other. In some embodiments, the output frequency may be the LO frequency (fLO). In some embodiments, the RF circuit 506 may include an IQ/polarity converter.

The FEM circuit 508 may include a receiving signal path, which may include being configured to operate based on the RF signal received from one or more antennas 560, amplifying the received signal, and providing an amplified version of the received signal to the RF circuit 506 for use Circuit for further processing. The FEM circuit 508 may also include a transmission signal path, which may include a circuit configured to amplify the signal provided by the RF circuit 506 for transmission by one or more of the one or more antennas 560.

In some embodiments, the FEM circuit 508 may include a TX/RX switch to switch between transmit mode and receive mode operations. The FEM circuit may include a receiving signal path and a transmitting signal path. The received signal path of the FEM circuit may include a low noise amplifier (LNA) to amplify the received RF signal and provide the amplified received RF signal as an output (for example, to the RF circuit 506). The transmit signal path of the FEM circuit 508 may include a power amplifier (PA) to amplify the input RF signal (e.g., provided by the RF circuit 506), and one or more filters to generate the RF signal for subsequent transmission (e.g., by one or One or more of the multiple antennas 560).

In some embodiments, the electronic device 500 may include additional components, such as a memory/storage device, a display, a camera, a sensor, and/or an input/output (I/O) interface. In some embodiments, the electronic device of FIG. 5 may be configured to perform one or more methods, processes, and/or techniques, such as those described herein.

FIG. 6 is a schematic diagram of an example of the components of a device 600. Each of the devices illustrated in FIGS. 1, 2, and 4 may include one or more devices 600. In some embodiments, the device 600 may be an example of a PGW device, a PCRF device, and/or a P-CSCF device. The device 600 may include a processor circuit 610, a memory and/or storage medium 620, a communication interface 630, a communication circuit 640, an input circuit 650, and an output circuit 660. In another implementation, the device 600 may include additional, fewer, different, or differently arranged components. In addition, one or more of the components of the device 600 may be examples of circuits, network interfaces, etc. described herein.

The processor circuit 610 may include a processor, a microprocessor, or processing logic that can interpret and execute instructions. The memory and/or storage medium 620 may include any type of dynamic storage device that can store information and instructions for execution by the processor 610, and/or any type of non-electrical storage device that can store information for use by the processor 610.

The communication interface 630 may include any transceiver-like mechanism that allows The device 600 can communicate with other devices and/or systems. For example, the communication interface 630 may include an Ethernet interface, an optical interface, a coaxial interface, and so on. The communication interface 630 may include a wireless communication device, such as an infrared (IR) receiver, a cellular radio, a Bluetooth radio, and so on. In some embodiments, the device 600 may include more than one communication interface 630. For example, the device 600 may include an optical interface and an Ethernet interface.

The communication circuit 640 may include one or more communication paths (for example, internal buses) that allow communication between the components of the device 600. The input circuit 650 may include a mechanism that allows the operator to input information to the device 600, such as a keyboard, a numeric keypad, buttons, switches, and the like. The output component 660 may include a mechanism for outputting information to the operator, such as a display, one or more light emitting diodes (LED), a speaker, and the like.

The device 600 can perform certain operations described above. The device 600 can perform these operations in response to the processor circuit 610 executing software instructions stored in a computer-readable medium, such as a memory and/or a storage medium 620. Computer-readable media can be defined as non-transitory memory devices. A memory device can include a space within a single physical memory device or spread across multiple physical memory devices. The software instructions can be read from another computer readable medium or read into the memory and/or storage medium 620 from another device. The software instructions stored in the memory and/or storage medium 620 can cause the processor 610 to perform the processing procedures described herein. In addition, hard-wired circuits can be used to replace or combine software commands to implement the methods described herein. Therefore, the implementation described herein is not limited to any specific combination of hardware circuits and software.

Secondly, a number of examples related to the implementation of the aforementioned technologies will be given.

In the first example, a P-CSCF device may include: a first network interface device for communicating with the UE through a RAN of a wireless telecommunication network; a second network interface device for communicating with the wireless telecommunication network Communication with a PCRF device on the network; and a circuit for: receiving a SIP message including a first indication that the SIP message originated from a remote UE, using the PCRF to establish or modify an Rx session, and by corresponding to the A communication session of the remote UE includes the Rx session described by one of at least one media stream, and a request message is sent to the PCRF.

In Example 2, the subject matter of Example 1 may further include that the SIP message includes a SIP REGISTER message.

In Example 3, any of the subject matter of Example 1 or the examples herein may further include wherein the SIP message includes a SIP INVITE message.

In Example 4, any of the subject matter of Example 1 or the examples herein may further include wherein the request message includes an [Rx] AAR message.

In Example 5, any of the subject matter of Example 1 or the examples herein may further include a third indication in which the request message includes the quality requirements of the at least one media stream.

In Example 6, the subject matter of Example 1 or any of the examples herein may further include wherein the third indication includes at least one of the following: a QoS parameter, a QCI, an allocation and ARP, or a GBR.

In the seventh example, a PCRF device may include a plurality of transmission ports; and a circuit for: establishing a first control session corresponding to a first UE with a PDN PGW of a wireless telecommunication network; and with the wireless telecommunication network A P-CSCF of one IMS establishes a second control meeting corresponding to a second UE Words; mapping the first control session to the second control session based on the first UE operating as a relay device between the second UE and the wireless telecommunication network; through the P-CSCF, from the second control session The UE receives a request to establish a call between the second UE and a third UE; and causes the PGW to bind the call to a bearer associated with the first UE.

In Example 8, the subject matter of Example 7 may further include that the call is bound to the bearer based on a QoS required by the call and a QoS of another call that has been bound to the bearer.

In Example 9, the subject matter of Example 7 or any of the examples herein may further include wherein the circuit is used to enable the PGW to increase the network resources allocated to the bearer based on a QoS required by the call.

In Example 10, the subject matter of Example 7 or any of the examples herein may further include that the first communication session corresponds to a Gx interface between the PCRF and the PGW, and the second communication session corresponds to the PCRF and An Rx interface between the P-CSCF.

In Example 11, the subject matter of Example 7 or any of the examples herein may further include wherein the first control session is established as a packet data network established between the first UE and the wireless telecommunication network ( PDN) part of the connection, and the second control session is established as part of the second UE registered with the IMS.

In Example 12, the subject matter of Example 7 or any of the examples herein may further include that in order for the PGW to bind the call to the bearer, the circuit is used to make the PGW: determine one of the calls Quality of Service (QoS) A network protocol associated with another call with a similar QoS Whether the carrier has been allocated to the first UE; when the network carrier has been allocated to the first UE, bind the call to the network carrier; and when the network carrier has not been allocated to For the first UE, based on the QoS of the call, a new network bearer is allocated to the first UE, and the call is bound to the new network bearer.

In Example 13, the subject matter of Example 1 or 7 or any of the examples herein may further include wherein the carrier includes an EPS carrier.

In the fourteenth example, a computer-readable medium may contain program instructions for one or more processors to: receive a SIP message including a first indication that the SIP message originates from a remote UE, using The PCRF establishes or modifies an Rx session, and transmits a request message to the PCRF through the Rx session described by a communication session corresponding to the remote UE including at least one media stream.

In Example 15, the subject matter of Example 14 may further include that the SIP message includes a SIP REGISTER message.

In Example 16, the subject of Example 14 or any of the examples herein may further include wherein the SIP message includes a SIP INVITE message.

In Example 17, the subject of Example 14 or any of the examples herein may further include wherein the request message includes an [Rx] AAR message.

In Example 18, the subject matter of Example 14 or any of the examples herein may further include a third indication in which the request message includes the quality requirements of the at least one media stream.

In Example 19, any of the subject matter of Example 14 or the examples herein may further include wherein the third indication includes at least one of the following Either: one QoS parameter, one QCI, one allocation and ARP, or one GBR.

In the 20th example, a P-CSCF device may include: means for receiving a Session Initiation Protocol (SIP) message, including a first indication that the SIP message originated from a remote UE; A component for establishing or modifying an Rx session using the PCRF; and a component for sending a request message to the PCRF through the Rx session described by a communication session corresponding to the remote UE including at least one media stream .

In Example 21, the subject matter of Example 20 may further include that the SIP message includes a SIP REGISTER message.

In Example 22, the subject of Example 20 or any of the examples herein may further include wherein the SIP message includes a SIP INVITE message.

In Example 23, any of the subject matter of Example 20 or the examples herein may further include wherein the request message includes an [Rx] AAR message.

In the twenty-fourth example, the one or more network devices may include: one or more network interface devices for communicating with user equipment devices (UE) through a radio access network (RAN) of a wireless telecommunication network ) Communication; and a circuit for: receiving a request originating from a first UE through a second UE to establish a call between the first UE and a third UE; based on the request, determining and configuring the A quality level associated with the call; determine whether a network bearer associated with another call that has a similar quality level with the quality level associated with the establishment of the call has been assigned to the second UE; When the network bearer has been assigned to the second UE, bind the call to the network bearer, and modify the network assigned to the network bearer based on the quality level associated with the establishment of the call Resources; and when the network carrier has not been allocated to the In the case of the second UE, based on the quality level associated with the establishment of the call, a new network bearer is allocated to the second UE, and the call is bound to the new network bearer.

In Example 25, the subject matter of Example 24 or any of the examples herein may further include wherein the circuit is used to: before the request to establish the call, through a Gx interface of the wireless telecommunication network, to establish a A control session on the second UE originates from the first UE and receives a request through the second UE to register the first UE in an IMS of the wireless telecommunication network, through the wireless telecommunication network An Rx interface establishes a control session for the first UE, and maps the control session through the Gx interface to the control session through the Rx interface.

In Example 26, the subject matter of Example 24 or any of the examples herein may further include an indication where the request to register the first UE includes that the first UE is operating as a remote UE.

In Example 27, the subject matter of Example 24 or any of the examples herein may further include that in order to map the communication session of the Gx interface to the communication session of the Rx interface, the circuit is used to: An IPv6 address associated with the second UE is used to identify an IPv6 prefix associated with the first UE.

In Example 28, the subject matter of Example 24 or any of the examples herein may further include: the Gx interface includes a communication interface between an EPC, a PDN PGW and a PCRF, and the Rx interface includes a communication interface between the EPC A communication interface between the PCRF and a P-CSCF of the IMS.

In Example 29, the subject matter of Example 24 or any of the examples herein One may further include where the request to establish the call includes an indication that the first UE is operating as a remote UE.

In the foregoing specification, various embodiments have been described with reference to the drawings. However, various modifications and changes can be made to it without departing from the broader scope stated in the following claims, and additional embodiments can be implemented. Accordingly, the description and drawings must be regarded as illustrative rather than restrictive.

For example, although the series of signals have been described with reference to FIG. 4, the order of the signals may be modified in other embodiments. In addition, non-dependent signals can be performed in parallel.

The display is as described above, and the examples are oriented to implement many different forms of software, firmware, and hardware in the implementation illustrated in the figure. The actual software code or specific control hardware used to implement these aspects should not be interpreted as restrictive. Therefore, the operations and performance of these aspects do not refer to specific software code descriptions-it is necessary to understand that software and control hardware can be designed to implement these aspects based on the description in this article.

Also, some parts can be built as "logic" that performs one or more functions. Such logic may include hardware, such as application-specific integrated circuits (ASIC) or field programmable gate array (FPGA), or a combination of hardware and software.

Even if combinations of specific features are cited in the scope of patent application and/or disclosed in the specification, these combinations are not intended to be limiting. In fact, many of these features can be combined in ways that are not specifically cited in the scope of the patent application and/or are not specifically disclosed in the specification.

The elements, actions, or instructions used in this case should not be construed as critical or necessary unless they are specifically described clearly in this way. As here The use of the term "and" does not necessarily exclude the use of the phrase "and/or" in the interpretation of the example. In the same way, as used herein, the use of the term "or" does not necessarily preclude the phrase "and/or" from being intended to be used in the interpretation of the example. Also, as used herein, the article "a" is intended to include one or more items, and can be used interchangeably with the phrase "one or more." When the intention is only one item, use the terms "one", "single", "only", or similar language.

100‧‧‧Environment

110‧‧‧User Equipment (UE)

115‧‧‧Evolved Node B (eNB)

120‧‧‧Service Gateway (SGW)

125‧‧‧Packet Data Network (PDN) Gateway (PGW)

130‧‧‧Mobile Management Entity (MME)

135‧‧‧Home User Server (HSS)

140‧‧‧Policy and Charging Rules Function (PCRF)

150‧‧‧Telephone Application Server (TAS)

155‧‧‧Proxy call session control function (P-CSCF)

Claims (29)

A proxy call session control function (P-CSCF) device, comprising: a first network interface device, the first network interface device is used to access a radio access network (RAN) of a wireless telecommunication network Communicating with a user equipment device (UE); a second network interface device for communicating with a policy and charging rules function (PCRF) device of the wireless telecommunication network; and The circuit that performs the following actions receives a Session Initiation Protocol (SIP) message. The SIP message includes a first indication that the SIP message originated from a remote UE and a relay parameter identifying a relay UE; using the PCRF Establishing or modifying an Rx session; and corresponding to a communication session of the remote UE to send a request message to the PCRF via the Rx session, the request message including a description of at least one media stream. For example, the P-CSCF device of request item 1, wherein the SIP message includes a SIP REGISTER message. For example, the P-CSCF device of request item 1, wherein the SIP message includes a SIP INVITE message. For example, the P-CSCF device of request item 1, wherein the request message includes an Rx authentication and authorization request (AAR) message. For example, the P-CSCF device of claim 1, wherein the request message includes the A third indication of the quality requirements for one less media stream. For example, the P-CSCF device of claim 1, wherein the third indication includes at least one of the following: a quality of service (QoS) parameter; a QoS class identifier (QCI); an allocation and reservation order (ARP); Or a guaranteed bit rate (GBR). Such as the P-CSCF device of claim 1, wherein the relay parameter includes an IPv6 address identifying the relay UE. A policy and charging rules function (PCRF) device, which includes a plurality of transmission ports, and a circuit for performing the following actions: a packet corresponding to a first user equipment device (UE) and a wireless telecommunication network A data network (PDN) gateway (PGW) establishes a first control session; corresponds to a second UE and is a proxy for an Internet Protocol (IP) Multimedia Subsystem (IMS) of the wireless telecommunication network The call session control function (P-CSCF) establishes a second control session; based on a relay parameter received from the second UE for identifying the first UE as a relay device, and based on the operation as being in the second UE And the first UE of the relay device between the wireless telecommunications network and map the first control session to the second control session; via the P-CSCF, receive a request from the second UE to establish in the A call between a second UE and a third UE; and This allows the PGW to bind the call to a bearer associated with the first UE. Such as the PCRF of claim 8, wherein the call is bound to the bearer based on a quality of service (QoS) required by the call and a QoS of another call that has been bound to the bearer. Such as the PCRF of claim 8, wherein the circuit is used to perform the following actions: make the PGW increase the network resources allocated to the bearer based on a QoS required by the call. Such as the PCRF of claim 8, wherein: the first communication session corresponds to a Gx interface between the PCRF and the PGW; and the second communication session corresponds to an Rx interface between the PCRF and the P-CSCF. Such as the PCRF of claim 8, wherein: the first control session is established as part of a packet data network (PDN) connection established between the first UE and the wireless telecommunication network; and the second control session The system is established as part of the second UE registered with the IMS. Such as the PCRF of claim 8, in which, in order for the PGW to bind the call to the bearer, the circuit is used to perform the following actions to make the PGW: determine that a quality of service (QoS) is similar to that of the call Whether a network bearer associated with another call of QoS has been Is assigned to the first UE; when the network bearer has been assigned to the first UE, bind the call to the network bearer; and when the network bearer has not been assigned to the first UE In the case of the UE, a new network bearer is allocated to the first UE based on the QoS of the call; and the call is bound to the new network bearer. Such as the PCRF of claim 8, wherein the bearer includes an evolved packet system (EPS) bearer. Such as the PCRF of claim 8, wherein the relay parameter includes an IPv6 address identifying the relay device. A computer-readable medium containing program instructions that are used to enable one or more processors to perform the following actions: receive a Session Initiation Protocol (SIP) message, the SIP message including the SIP message originating from A first indication of a remote UE and a relay parameter identifying a relay UE; use the PCRF to establish or modify an Rx session; and correspond to a communication session of the remote UE to send a request through the Rx session A message is sent to the PCRF, and the request message includes a description of at least one media stream. For example, the computer in the request item 16 can read the media, wherein the SIP message includes a SIP REGISTER message. For example, the computer of the request item 16 can read the media, wherein the SIP message includes a SIP INVITE message. For example, the computer readable medium of the request item 16, wherein the request message includes an [Rx] authentication authorization request (AAR) message. For example, the computer readable medium of the request item 16, wherein the request message includes a third indication of the quality requirements of the at least one media stream. For example, the computer readable medium of request item 16, wherein the third instruction includes at least one of the following: a quality of service (QoS) parameter; a QoS class identifier (QCI); an allocation and reservation order (ARP) ; Or a guaranteed bit rate (GBR). For example, the computer of request item 16 can read the media, wherein the relay parameter includes an IPv6 address that identifies the relay UE. A network device including one or more components, the network device including one or more network interface devices, the one or more network interface devices are used to access the network via a radio of a wireless telecommunication network (RAN) to communicate with a user equipment device (UE); and a circuit for performing the following actions: receiving a request from a first UE via a second UE to establish a connection between the first UE and a second UE A call between three UEs; a quality level associated with the implementation of the call is determined based on the request; the call is determined and implemented based on a relay parameter received from the first UE for identifying the second UE The associated quality level has a similar quality level associated with another call Whether a network bearer has been assigned to the second UE; when the network bearer has been assigned to the second UE, bind the call to the network bearer, and based on the fact that it is related to the implementation of the call The quality level associated with the network to modify the network resources allocated to the network bearer; and when the network bearer has not been allocated to the second UE, based on the quality level associated with the implementation of the call A new network bearer is allocated to the second UE, and the call is bound to the new network bearer. For example, the request item 23 includes one or more components of the network device, wherein the circuit is used to perform the following actions before establishing the request of the call, through a Gx interface of the wireless telecommunication network, and establish for the A control session of a second UE receives a request from the first UE via the second UE to register the first UE with an Internet Protocol (IP) multimedia of the wireless telecommunication network The subsystem (IMS) establishes a control session for the first UE via an Rx interface of the wireless telecommunication network, and maps the control session to the control session via the Rx interface via the Gx interface. For example, the request item 23 includes a network device including one or more components, wherein the request for registering the first UE includes an indication that the first UE is operating as a remote UE. For example, the request item 23 includes one or more components of the network device, wherein, in order to map the communication session of the Gx interface to the communication session of the Rx interface, the circuit is used to perform the following actions: An IPv6 address associated with the second UE is used to identify an IPv6 prefix associated with the first UE. For example, the request item 23 includes one or more components of the network device, wherein: the Gx interface includes a packet data network (PDN) gateway (PGW) of an evolved packet core (EPC) and a strategy and calculation A communication interface between the PCRF; and the Rx interface includes a communication interface between the PCRF of the EPC and a proxy call session control function (P-CSCF) of the IMS. For example, the request item 23 is a network device including one or more components, wherein the request for establishing the call includes an indication that the first UE is operating as a remote UE. For example, the request item 23 includes a network device including one or more components, wherein the relay parameter includes an IPv6 address that identifies the relay UE.

Images