Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.
It should be noted that, all actions for acquiring signals, information or data in the present disclosure are performed under the condition of conforming to the corresponding data protection rule policy of the country of the location and obtaining the authorization given by the owner of the corresponding device.
In the description of the present disclosure, terms such as "first," "second," and the like are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. In addition, unless otherwise stated, in the description with reference to the drawings, the same reference numerals in different drawings denote the same elements.
In the description of the present disclosure, unless otherwise indicated, "a plurality" means two or more than two, and other adjectives are similar thereto; "at least one item", "an item" or "a plurality of items" or the like, refer to any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one term(s) may represent any number; as another example, one (or more) of a, b, and c may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or plural; "and/or" is an association relationship describing an association object, meaning that there may be three relationships, e.g., a and/or B, which may represent: there are three cases, a alone, a and B together, and B alone, wherein a, B may be singular or plural.
Although operations or steps are described in a particular order in the figures in the disclosed embodiments, it should not be understood as requiring that such operations or steps be performed in the particular order shown or in sequential order, or that all illustrated operations or steps be performed, to achieve desirable results. In embodiments of the present disclosure, these operations or steps may be performed serially; these operations or steps may also be performed in parallel; some of these operations or steps may also be performed.
The following first describes the environment in which embodiments of the present disclosure are implemented.
The technical scheme of the embodiment of the disclosure can be applied to various communication systems. The communication system may include one or more of a 4G (the 4th Generation) communication system, a 5G (the 5th Generation) communication system, and other future wireless communication systems (e.g., 6G). The communication system may also include one or more of a public land mobile network (Public Land Mobile Network, PLMN) network, a Device-to-Device (D2D) communication system, a machine-to-machine (Machine to Machine, M2M) communication system, an internet of things (Internet of Things, ioT) communication system, a Vehicle-to-evaluation (V2X) communication system, or other communication systems.
Fig. 1 is a schematic diagram of a communication system, which may include a user device 11 and a network device 12, as shown in fig. 1, according to an example embodiment. The communication system may be used to support 4G network access technologies, such as long term evolution (Long Term Evolution, LTE) access technologies, or 5G network access technologies, such as New radio access technologies (New Radio Access Technology, new RAT), or other future wireless communication technologies. It should be noted that, in the communication system, the number of network devices 12 and user devices 11 may be one or more, and the number of network devices 12 and user devices 11 in the communication system shown in fig. 1 is merely an adaptive example, which is not limited in this disclosure.
The network device 12 in fig. 1 may be used to support access by the user equipment 11, for example, the network device 12 may be an evolved base station (evolutional Node B, eNB or eNodeB) in LTE; the network device 12 may also be a next generation base station (the next Generation Node B, gNB or gNodeB) in a 5G network; the network device 12 may also be a radio access network (NG Radio Access Network, NG-RAN) device in a 5G network; the network device 12 may also be a base station in a future evolved public land mobile network (Public Land Mobile Network, PLMN), a broadband network service gateway (Broadband Network Gateway, BNG), a converged switch, or a non-3 GPP (3 rd Generation Partnership Project, third generation partnership project) access device, etc.
Alternatively, the network device 12 in embodiments of the present disclosure may include various forms of base stations, such as: macro base stations, micro base stations (also referred to as small stations), relay stations, access points, 5G base stations or future base stations, satellites, transmission points (Transmitting and Receiving Point, TRP), transmission points (Transmitting Point, TP), mobile switching centers, and devices-to-devices (D2D), machines-to-machines (M2M), internet of things (Internet of Things, ioT), internet of vehicles (V2X), or other devices in communication that assume the functions of a base station, etc., as in the embodiments of the present disclosure, are not specifically limited. For convenience of description, in all embodiments of the present disclosure, the means for providing the wireless communication function for the user equipment 11 is collectively referred to as the network equipment 12 or the base station.
Illustratively, the network device 12 may be an application server (Application Server, AP) and a data channel signaling entity (Data Channel Signalling Function, DCSF). The data channel signaling entity DCSF may also be referred to as a data channel signaling function or a data channel signaling network element.
The user equipment 11 in fig. 1 may be an electronic device providing voice or data connectivity, for example, the user equipment 11 may also be referred to as a Subscriber Unit (Subscriber Unit), a Mobile Station (Mobile Station), a Station (Station), a Terminal (Terminal), etc. By way of example, the user device 11 may include a smart phone, a smart wearable device, a smart speaker, a smart tablet, a wireless modem (modem), a wireless local loop (Wireless Local Loop, WLL) station, a PDA (Personal Digital Assistant ), a CPE (Customer Premise Equipment, customer user device), and the like.
With the development of wireless communication technology, the user equipment 11 in the embodiments of the present disclosure may be an access communication system, a device that can communicate with a network device of the communication system, a device that can communicate with other objects through the communication system, or a device that can directly communicate between two or more devices; for example, terminals and automobiles in intelligent transportation, household devices in intelligent homes, meter reading instruments for electric power in smart grids, voltage monitoring instruments, environment monitoring instruments, video monitoring instruments in intelligent security networks, cash registers, etc. In the disclosed embodiment, the user device 11 may communicate with the network device 12. Communication may also take place between a plurality of user equipments 11. The user equipment 11 may be stationary or mobile, and this disclosure is not limited in this regard.
An IP (Internet Protocol ) multimedia Core Network (CN) subsystem includes all Core Network elements for providing multimedia services, where the Core Network elements may include a collection of signaling and media related Network elements. IP multimedia services are session control capabilities that may be defined based on IETF (The Internet Engineering Task Force, internet engineering task force) that may be accessed to a network over an IP connection along with multimedia transport capabilities.
In order to achieve independence of access and to smoothly maintain interoperability with wired terminals on the internet, IP multimedia subsystems attempt to make them meet the IETF's "internet standard". Thus, in the case of selecting an IETF protocol, the specified interface may meet IETF "internet standards". Such as SIP (Session initial Protocol, session initiation protocol) and RTP (Real-Time Transport Protocol ).
The IP multimedia core network (IM CN) subsystem enables operators to provide multimedia services for users, and in particular, the IP multimedia core network subsystem can combine wireless and wired users and obtain voice (voice), video (video), messaging (messaging), data (data), web-based technologies, and the like.
The Data Channel (DC) may be established in the context of an IMS (IP Multimedia Subsystem, internet protocol multimedia subsystem) MMTel (multimedia Telephony) session. As shown in fig. 2 and 3, the IMS architecture may support separation of signaling functions and media functions supporting data channel services, and the data channel signaling entity DCSF may be a network element to which data channel signaling management is specified. In addition, the network function of processing the data channel medium in the embodiments of the present disclosure may be provided in the following two ways.
The first way is shown in fig. 2, which is mainly to perform the media functions related to the data channels by enhancing the existing IMS multimedia resource functions (Multimedia Resource Function, MRF) 101. As shown in fig. 2, the IMS multimedia resource function 101 may interact with the IMS application server 102 via an enhanced Mr'/Cr interface.
The second way is shown in fig. 3, which mainly introduces a new network function, which may be called a data channel media function (Data Channel Media Function, DCMF) 103, which data channel media function DCMF 103 may interact with the IMS application server 102 based on the service interface DC 2.
In some embodiments, 3GPP (3 rd generation partnership project, third generation partnership project) PS (Packet Switch) data shutdown may be an optional feature. When the user activates and the network supports the 3GPP PS data shutdown function, the data path media function DCMF allows to control IMS services and more widely SIP-based services, where the user can access the IMS framework in the data in the shutdown state for initiating and terminating sessions.
The list of 3GPP PS data closed exempt services can be configured by the HPLMN (Home Public Land Mobile Network, local public land mobile network) in the user equipment and the network equipment. In some embodiments, the SIP-based service list may include media telephony service-Voice (MMTel Voice), short message service (SMS over IMS) sent over IMS, media telephony service-Video (MMTel Video), USSI, and specific IMS services not defined by 3GPP, etc. Here, a specific IMS service not defined by the 3GPP may be identified by an IMS communication service identifier.
In some embodiments, when PS data is turned off, applications that rely on IMS data channels will not be available, which in turn may result in portions of the IMS multimedia telephony service being impacted.
Fig. 4 is a flow chart illustrating a method of data traffic processing according to an embodiment. As shown in fig. 4, the method may be used in a data channel signaling entity, comprising the following steps.
In step S110, a data channel call request sent by an application server AS is received.
In an embodiment of the present disclosure, the data channel signaling entity DCSF may receive a data channel call request sent by the application server AS, where the data channel call request may include first capability information. Here, the first capability information is used to indicate that the user equipment UE is capable of running traffic on an internet protocol multimedia subsystem, IMS, data channel (Services over IMS Data Channel).
In the embodiment of the disclosure, the data channel call request may be referred to as nimsas_sessioneventcontrol_notify, and may further include at least one of a third generation partnership project 3GPP packet switched PS data off state (3 GPP PS Data Off status), a session establishment request event (sessionestablischentrequestion), a caller identification (callid), a callee identification (CalledID), a session case (SessionCase), a session identification (SessionID), and the like, in addition to the first capability information.
The disclosed embodiments provide that the data channel signaling entity DCSF may receive a data channel call request sent by the application server AS, wherein the data channel call request comprises first capability information for indicating that the user equipment is capable of running services on the IMS data channel, such that an application dependent on the IMS data channel may still be available in case the data of the user equipment is in a closed state.
Fig. 5 is a flow chart illustrating a method of data traffic processing according to another embodiment. As shown in fig. 5, the method may be used in a data channel signaling entity, comprising the following steps.
In step S210, a data channel call request sent by the application server AS is received.
The specific embodiment of step S210 is described in detail above, and will not be described herein.
In step S220, the traffic on the IMS data channel is adjusted according to the 3GPP PS data off state and/or the operator policy.
As an alternative, after receiving the data channel call request, the data channel signaling entity DCSF may determine, based on the relevant parameters, a policy on how to determine how to bootstrap the data channel setup invitation, i.e. to adjust the traffic on the IMS data channel based on the relevant parameters.
The relevant parameters may include, among other things, the 3GPP data off state (active) and/or operator policy in the data channel call request. The operator may configure the data channel signaling entity DCSF as an application/service allowing the user equipment UE/user to use in the 3GPP data off state (active).
In particular, the data channel signaling entity DCSF may determine whether to provide a Data Channel (DC) and determine a data channel control policy (DC control policy). Here the data path control policy may be which of the services that can be run on the IMS data path in case the 3GPP data off state is activated. It can be seen that the data channel signaling entity DCSF may take into account the 3GPP data off state (activation) of the IMS data channel application of the user equipment UE.
As an example, the data path control policy does not allow video and audio transmission and only runs text transmission, and then the traffic that can run on the IMS data path is text with the 3GPP data off state activated. For example, the service that can be run on the IMS data channel is a short message service.
In addition, as is known from the above description, the data channel call request may include at least one of an establishment request event (Session Establishment Request Event), caller identification (caller ID), called identification (called ID), session case (SessionCase) session identification (SessionID), media information list (medialnfolist), and 3GPP data off state (activation), etc. Since the sessionesponstable request event in nimsas_sessioneventcontrol_notify indicates that the local bootstrap media is provided to the user to which the service is provided, the data channel signaling entity DCSF can acquire the media information of the originating MDC1 (mobile data channel) and acquire the remote bootstrap media information of the terminating MDC1 (mobile data channel) according to its determined policy. Wherein the remote bootstrapping media information is primarily directed to a remote user equipment. It can be seen that the data channel signalling entity DCSF can create Data Channel (DC) media information of the originating (origin) and terminating (terminating).
Based on this, the data channel signaling entity DCSF may invoke nimsas_mediacontrol_mediainstruction operations according to its determined data channel control policy, so AS to instruct the IMS AS how to establish the bootstrap data channels of the initiator and the terminator with the DCMF, AS shown in fig. 6 in detail. Among them, nimsas_mediacontrol_mediainstruction may include a session ID (SessionID) media indication group/setting group (MediaInstruction set), and the like.
In other embodiments, the data channel signaling entity DCSF may receive a Nimsas transmitted nimsas_mediacontrol_mediainstruction response. On this basis, the data channel signaling entity DCSF may store the media resource information and respond to the nimsas_sessioneventcontrol_notify request received by the data channel signaling entity DCSF, i.e. send nimsas_sessioneventcontrol_notify response to the IMSAS.
As is known from fig. 6, a bootstrap data channel has been established between the initiator DCMF or MRF and the first user equipment/second user equipment, and the first user equipment and the second user equipment may send an application request message to the DCMF or MRF through the data channel capability of the bootstrap data channel. Here, the DCMF or MRF may forward the message to the receiving media point (received media point) of the data channel signalling entity DCSF.
In addition, the data channel signaling entity DCSF may provide the first user equipment and the second user equipment with the appropriate data channel application based on the data channel capabilities and 3GPP data off state (activation) of the first user equipment and the second user equipment through DCMF or MRF. In other words, the data channel signaling entity DCSF may respectively issue the adjusted services on the IMS data channel to the first user equipment and the second user equipment.
As is known from the above description, the data channel signalling entity DCSF may be operator configured, which may allow the user equipment/user to use applications/services in the 3GPP data off state (active).
In other embodiments, the terminating party DCMF or MRF may establish a bootstrap data channel between the first user equipment/second user equipment, and the data channel application may be requested and downloaded from the terminating party data channel signaling entity DCSF to the first user equipment and the second user equipment. When multiple data channel DC applications are available, the user equipment UE may request a list of data channel applications after bootstrapping the data channel setup.
In summary, in the case where the packet switched data shutdown is activated in the embodiments of the present disclosure, the application dependent on the IMS data channel is still available.
It should be noted that the use of multiple embodiments or features that are "or" spaced apart may not affect other aspects even if some of them are not possible. In addition, in the case of no contradiction, the embodiments of the present disclosure may be combined with the embodiments or implementations related to the method for processing the data traffic of the data channel signaling entity and various alternatives thereof, which are not described herein again.
In the embodiment of the disclosure, the data channel signaling entity DCSF may receive a data channel call request sent by the application server AS, and on this basis, the data channel signaling entity DCSF may adjust a service running on the IMS data channel according to a 3GPP PS data closing state and/or an operator policy, so that not only an application dependent on the IMS data channel may still be available in a case that data of the user equipment is in a closing state, but also flexibility of data service processing may be improved.
Fig. 7 is a flow chart illustrating a method of data traffic processing according to an embodiment. AS shown in fig. 7, the method may be used in an application server AS, including the following steps.
In step S310, a session initiation protocol SIP invite request sent by the UE is received.
In some embodiments, the application server AS may receive a session initiation protocol SIP invite request sent by the user equipment UE. Wherein the SIP invite request is for the AS to send a data channel call request to the DCSF, the data channel call request may include the first capability information. Here, the first capability information is used to indicate that the user equipment UE is capable of running traffic on the IMS data channel.
In other embodiments, the application server AS may receive the SIP invite request from the user equipment UE through the P-CSCF (Proxy Call Session Control Function, proxy call session control entity) and the I-CSCF (inter-calling session control entity), or the application server AS may receive the SIP invite request from the user equipment UE through the P-CSCF and the S-CSCF (Serving Call Session Control Function, serving call session control entity). Wherein the SIP invite request may be used for the application server AS to send a data channel call request to the data channel signaling entity DCSF.
In the embodiment of the present disclosure, the application server AS may be an IMS AS. In addition, the proxy call session control function may also be referred to as a proxy call session control entity or a proxy call session control network element; the inquiring call session control entity may also be referred to as an inquiring call session control function or an inquiring call session control network element; the serving call session control entity may also be referred to as a serving call session control function or a serving call session control network element.
AS an alternative, after receiving the SIP invite request, the IMS AS may verify the user subscription data to determine whether to forward the data channel call request to the data channel signalling entity DCSF. When the IMS AS determines to send a data channel call request to the data channel signaling entity DCSF according to the user situation, the IMS AS may discover and select one data channel signaling entity DCSF based on local configuration or through NRF (Network Repository Function, network storage function), and then use the data channel signaling entity DCSF AS the data channel signaling entity DCSF corresponding to the user equipment UE. In other words, the application server AS may be used to determine the data channel Routing (DC Routing) and to discover the data channel signaling entity DCSF.
In step S320, a data channel call request is transmitted to the DCSF.
As is known from the above description, the data channel call request comprises first capability information, wherein the first capability information may be used to indicate that the user equipment UE is capable of running services on the IMS data channel.
Optionally, the data channel call request may further include at least one of the following information: 3GPP PS data off state; a session establishment request event; a calling identifier; a called identifier; a session condition; and session identification, etc.
As an alternative, after receiving the SIP invite request, the IMSAS may send a data channel call request to the data channel signalling entity DCSF based on the SIP request. In particular, the IMS AS may Notify the data channel signaling entity DCSF of the call event, i.e. send a data channel call request (nimsas_sessioneventcontrol_notify) to the data channel signaling entity DCSF.
In some implementations, the SIP invite request may carry an initial session description protocol SDP (Session Des cription Protocol), where the SDP may include a bootstrap data path setup offer.
In other embodiments, the IMS AS may also receive nimsas_mediacontrol_mediainstruction information from the data channel signaling entity DCSF AS shown in fig. 6 and select DCMF according to the information and the local configuration, or discover and select DCMF or enhanced MRF supporting the data channel media function through NRF.
On this basis, the IMSAS may invoke the DCMF service to instruct the DCMF to allocate an Mb resource to terminate a media description (media descriptor) specified by the data channel signaling entity DCSF for the initiator. In addition, the DCMF may be an IMS AS independent DCMF. At this time, the media information acquired and stored by the data channel signaling entity DCSF according to its policy may be referred to as a data channel media resource, which may be stored in DC 1. Alternatively, when using an enhanced MRF, the IMS AS may use Mr'/Cr to save data path media resources to the MRF. Thus, the IMS AS may request the DCMF or the enhanced MRF to save the initiator media resources, and the DCMF may allocate resources for the initiator MDC1 (mobile data channel 1).
In other embodiments, the IMS AS may invoke the DCMF service to instruct the DCMF to allocate an Mb resource to terminate the media descriptor specified by the data channel signaling entity DCSF for the terminating party. DCMF is independent of IMS AS. At this time, the media information acquired and stored by the data channel signaling entity DCSF according to its policy may be referred to as a data channel media resource, which may be stored in DC 2. Alternatively, when enhanced MRF is used, the IMS AS may use Mr'/Cr to conserve data channel media resources. Thus, the IMS AS may request the DCMF or the enhanced MRF to save the terminating media resources, and the DCMF may allocate resources for the terminating MDC1 (mobile data channel 1).
It should be noted that, in the embodiments of the present disclosure, the allocation of DCMF media resources may be accomplished by invoking one or more industry services.
In other embodiments, the IMS AS may also respond to the MediaInstruction request it receives, i.e. the IMS AS may send a nimsas_mediacontrol_mediainstruction response to the data channel signaling entity DCSF. The nimsas_mediacontrol_mediainstruction response here may include the success of the IMS AS receive operation and media resource information.
In other embodiments, the IMS AS may send an invite request to the remote network side and the second user equipment (ue#2) through the originating S-CSCF, where the invite request may include a proposal to update SDP, and may include media information of DCMF or MRF. In this case, the invite request may further comprise an SDP offer providing a bootstrap data path to the second user equipment.
It should be noted that the content included in the invite request in step 12 and step 13 in fig. 6 may be the same, and specifically, the invite request in step 12 may include an audio/video offer (audio/video offer), and SDP (modified SDP offer for bootstrap DC) provided by changing to the bootstrap data channel; the invite request in step 13 may include an audio/video offer (audio/video offer), SDP (modified SDP offer for bootstrap DC) provided for changing to the bootstrap data channel.
In other embodiments, as shown in fig. 6, the second user device and the terminating network may return an 18X response to the originating network, the 18X response having an SDP response to the bootstrap data path. If the terminating network determines to establish another bootstrap data channel for the first user equipment (ue#1) and the second user equipment (ue#2), a corresponding data channel media description may also be included in the SDP response.
In addition, the second user equipment (ue#2) and the terminating network may return a 200OK response. On this basis, the IMS AS can inform the data channel signaling entity DCSF session establishment success through nimsas_sessioneventcontrolnotify. The nimsas_sessioneventcontrolnotify herein may include a session establishment success event (sessionestablischentsuccessevent), a session ID (SessionID), a media information list (medialnolist), and the like. In addition, the data channel signaling entity DCSF may respond to nimsas_sessioneventcontrol Notify, i.e. the data channel signaling entity DCSF sends nimsas_sessioneventcontrol_notify response to the application server.
It should be further noted that the use of multiple embodiments or features that are "or" spaced apart may not affect other aspects even if some of these features are not available. In addition, the embodiments of the present disclosure may be combined with other embodiments or implementations related to the methods for data traffic processing of the data channel signaling entity and the application server and various alternatives thereof, where not contradicted, and will not be described herein.
The embodiments of the present disclosure provide that the application server AS may receive a SIP invite request sent by the user equipment UE, where the SIP invite request is used for sending a data channel call request to the data channel signaling entity DCSF, on the basis of which the application server AS may send a data channel call request to the data channel signaling entity DCSF, where the data channel call request includes first capability information, where the first capability information is used to indicate that the user equipment is capable of running a service on an IMS data channel of the internet protocol multimedia subsystem, so that it may be ensured that an application dependent on the IMS data channel is still available in case that data of the user equipment is in a closed state.
Fig. 8 is a flow chart illustrating a method of data traffic processing according to another embodiment. As shown in fig. 8, the method can be used in an application server, including the following steps.
In step S410, a registration information stream sent by the UE is received, where the registration information stream includes first capability information.
In some embodiments, the application server AS may receive a registration information flow (Register) sent by the user equipment UE, which may include the first capability information. The first capability information may be used to indicate that the user equipment UE is capable of running a service on an IMS data channel of the internet protocol multimedia subsystem.
As an alternative, the first capability information may be indicated by a media feature tag (media feature tag) associated with the data closure exemption service (Data Off Exempted Services). Wherein, the data closing exemption service can be 3GPP PS data closing exemption service; the media feature tag may be a g.3gpp.ps-data-off media feature tag or a g.3 gpp.ici-ref media feature tag. Here, the g.3 gpp.ici-ref media feature tag may represent the traffic running on the IMS data channel in the IMS registration request.
In an embodiment of the present disclosure, the media feature tag may comprise a service (Services over IMS Data Channel) running on an internet protocol multimedia subsystem, IMS, data channel. The services running on the IMS data channel may include, among others, media telephony services-Voice (MMTel Voice), short message services sent over IMS (SMS over IMS), media telephony services-Video (MMTel Video), USSI, and specific IMS services not defined by 3GPP. In addition, the media feature tag can also be used to indicate that other 3GPP PS data is closing exemption services.
Optionally, the registration information flow may further include at least one of the following information: 3GPP PS data off state (3 GPP PS data off status); -a public user identity (Public User Identity); a private user identity (Private User Identity); a home network domain name (home network domain name) and an internet protocol, IP, address (UE IP address) of the user equipment, UE.
In some embodiments, the application server AS may receive the registration information flow sent by the user equipment UE through the P-CSCF and the I-CSCF. Optionally, the application server AS may also receive the registration information flow sent by the user equipment UE through the P-CSCF and the S-CSCF.
To more clearly illustrate the flow of receiving the registration information flow, the embodiment of the present disclosure presents an exemplary diagram as shown in fig. 9, and it is known from fig. 9 that the UE may send the first registration information flow to the proxy call session control entity P-CSCF, and then send the second registration information flow to the querying call session control entity I-CSCF/serving call session control entity S-CSCF through the proxy call session control entity P-CSCF.
Specifically, the proxy call session control entity P-CSCF may send the second registration information flow to the querying call session control entity I-CSCF after receiving the first registration information flow, or may also send the second registration information flow to the serving call session control entity S-CSCF. On the basis of this, the querying call session control entity I-CSCF/serving call session control entity S-CSCF may send the third registration information flow to the application server AS.
In other words, the application server AS may receive a registration information flow from the I-CSCF/S-CSCF, which may be sent by the user equipment UE to the I-CSCF/S-CSCF via the P-CSCF.
It should be noted that the registration information flow may include not only the first capability information, the 3GPP PS data closed state, the public user identity, the private user identity, the home network domain name, the IP address of the user equipment UE, and the like, but also the address/name of the proxy call session control entity P-CSCF, the network identity of the proxy call session control entity P-CSCF, and the like.
In other embodiments, after receiving the registration information flow sent by the UE, the application server AS may record the first capability information in the registration information flow, and after receiving the SIP invite request sent by the UE, send the recorded first capability information to the data channel signaling entity DCSF through the data channel call request.
In other embodiments, the application server AS may send a 200OK message flow to the user equipment UE after receiving the registration message flow. Wherein the 200OK message flow is used to indicate success with respect to service registration running on the IMS data channel. The 200OK information flow may carry configuration parameters of the user equipment UE, which may be used to support IMS services. In addition, the configuration parameters of the user equipment UE may be referred to as IMS service parameters of the user equipment UE. Here, the IMS service may include typical services such as a voice call, a video call, a message, and a data service.
AS an alternative, the 200OK message flow may be sent to the user equipment UE by the application server AS after receiving the registration message flow sent by the user equipment UE, where the registration message flow may include first capability information, where the first capability information is used to indicate that the user equipment UE is capable of running a service on an IMS data channel of the internet protocol multimedia subsystem. In addition, in case the 3GPP PS data off state of the user equipment UE is activated, the application server AS may allow only SIP traffic transmission in the SIP-based 3GPP PS data off exempt traffic.
In other embodiments, the application server AS may send the 200OK information flow to the user equipment UE via the P-CSCF and the I-CSCF, or the application server AS may send the 200OK information flow to the user equipment UE via the P-CSCF and the S-CSCF.
In step S420, the first capability information is transmitted to the DCSF through the data channel call request.
AS an alternative, after sending the 200OK information stream to the UE, if the SIP invite request sent by the UE is received, the application server AS may send a data channel call request to the DCSF, where the data channel call request may include the first capability information recorded by the application server AS. In addition, the foregoing embodiments of the other embodiments of step S420 have been described in detail, and will not be described herein.
It should be noted that the use of multiple embodiments or features that are "or" spaced apart may not affect other aspects even if some of them are not possible. In addition, the embodiments of the present disclosure may be combined with other embodiments or implementations related to the methods for data traffic processing of the data channel signaling entity and the application server and various alternatives thereof, where not contradicted, and will not be described herein.
The embodiments of the present disclosure provide that the application server AS may receive a SIP invite request sent by the user equipment UE, where the SIP invite request is used for sending a data channel call request to the data channel signaling entity DCSF, on the basis of which the application server AS may send a data channel call request to the data channel signaling entity DCSF, where the data channel call request includes first capability information, where the first capability information is used to indicate that the user equipment is capable of running a service on an IMS data channel of the internet protocol multimedia subsystem, so that it may be ensured that an application dependent on the IMS data channel is still available in case that data of the user equipment is in a closed state. In addition, the application server AS can acquire the first capability information through the registration information flow sent by the user equipment UE, so that the effectiveness of data service processing can be improved.
Fig. 10 is a flow chart illustrating a method of data traffic processing according to yet another embodiment. As shown in fig. 10, the method can be used in an application server, including the following steps.
In step S510, a session initiation protocol SIP invite request sent by the UE is received, the SIP invite request including first capability information.
In an embodiment of the present disclosure, the session initiation protocol SIP invite request received by the application server AS from the user equipment UE may include first capability information, i.e. the first capability information may be carried in the session initiation protocol SIP invite request sent by the user equipment UE. The first capability information may be used to indicate that the user equipment UE is capable of running services on the IMS data channel. In addition, the session initiation protocol SIP invite request may also include a 3GPP data off state.
Optionally, after receiving the SIP request including the first capability information sent by the user equipment UE, the application server AS may send the first capability information to the data channel signaling entity DCSF through the data channel call request, i.e. step S520 is entered.
In step S520, the first capability information is transmitted to the DCSF through the data channel call request.
The above embodiment of step S520 has been described in detail, and will not be described here again.
It should be noted that the use of multiple embodiments or features that are "or" spaced apart may not affect other aspects even if some of them are not possible. In addition, the embodiments of the present disclosure may be combined with other embodiments or implementations related to the methods for data traffic processing of the data channel signaling entity and the application server and various alternatives thereof, where not contradicted, and will not be described herein.
The embodiments of the present disclosure provide that the application server AS may receive a SIP invite request sent by the user equipment, where the SIP invite request is used for sending a data channel call request to the data channel signaling entity DCSF by the application server AS, on the basis of which the application server AS sends a data channel call request to the data channel signaling entity DCSF, where the data channel call request includes first capability information, where the first capability information is used to indicate that the user equipment is capable of running a service on an IMS data channel of the internet protocol multimedia subsystem, so that it may be ensured that an application dependent on the IMS data channel is still available in case that data of the user equipment is in a closed state. In addition, the application server AS can acquire the first capability information through the registration information flow sent by the user equipment, so that the effectiveness of data service processing can be improved.
Fig. 11 is a flow chart illustrating a method of data traffic processing according to an embodiment. As shown in fig. 11, the method may be used in a user equipment, including the following steps.
In step S610, a SIP invite request is sent to the AS.
In some embodiments, the user equipment UE may send a SIP invite request to the application server AS for the application server AS to send a data channel call request to the data channel signaling entity DCSF. The data channel call request may include first capability information, where the first capability information is used to indicate that the user equipment UE is capable of running a service on the IMS data channel.
In some implementations, the data channel call request may further include at least one of the following information: 3GPP PS data off state; a session establishment request event; a calling identifier; a called identifier; a session condition; and (5) session identification.
In other embodiments, the user equipment UE may send the SIP invite request to the application server AS through the P-CSCF and the I-CSCF, or the user equipment UE may send the SIP invite request to the application server AS through the P-CSCF and the S-CSCF.
AS a specific embodiment, after receiving the 200OK information stream sent by the application server AS, the user equipment UE may establish a Bootstrap (bootstrapping) data channel, and the establishment procedure of the Bootstrap (bootstrapping) data channel may be AS shown in fig. 6. AS is known from fig. 6, when a bootstrapping (bootstrapping) data channel is established, the user equipment UE may first send a session initiation protocol SIP INVITE (INVITE) request to the application server AS.
Here, the SIP invite request may be used for the application server AS to send a data channel call request to the data channel signaling entity DCSF, wherein the data channel call request may comprise the first capability information.
Specifically, AS shown in fig. 6, the UE may send a session initiation protocol SIP invite request to the application server AS through the P-CSCF and the I-CSCF of the originating network (originating network), or the UE may also send a session initiation protocol SIP invite request to the application server AS through the P-CSCF and the S-CSCF of the originating network.
Here, the SIP invite request may be an invite request carrying an initial SDP, which may include a proposal (offer) to establish an invite for a Bootstrap (boottrap) data channel. In other words, the SIP invite request may include an initial session description protocol SDP, which may include a bootstrap data path setup offer. Alternatively, the SDP may include a proposal (offer) for a Bootstrap (bootstrapping) data channel for both the initiator (originating side) and the terminator (terminating side).
In some embodiments, the SIP invite request may be a SIP re-invite performed after the initial IMS audio session establishment. Here, the SIP invite request may include an audio/video offer (audio/video offer) and SDP (offer for bootstrap DC) provided for the bootstrap data channel.
In other embodiments, the SIP invite request may comprise the first capability information, i.e. the user equipment UE may send the first capability information to the application server AS via the SIP invite request. Optionally, the SIP invite request may also include a 3GPP PS data off state.
It should be noted that the use of multiple embodiments or features that are "or" spaced apart may not affect other aspects even if some of them are not possible. In addition, the embodiments of the present disclosure may be combined with other embodiments or implementations related to the methods for data traffic processing of the data channel signaling entity and the application server and various alternatives thereof, where not contradicted, and will not be described herein.
The disclosed embodiments provide that the user equipment UE may send a SIP invite request to the application server AS for the application server AS to send a data channel call request to the data channel signaling entity DCSF, where the data channel call request comprises first capability information, where the first capability information is used to indicate that the user equipment is capable of running traffic on an IMS data channel of the internet protocol multimedia subsystem, such that it may be ensured that an application dependent on the IMS data channel is still available in case the data of the user equipment is in a closed state.
Fig. 12 is a flow chart illustrating a method of data traffic processing according to another embodiment. As shown in fig. 12, the method may be used in a user equipment, including the following steps.
In step S710, a registration information flow is sent to the AS, the registration information flow including first capability information.
In some embodiments, the user equipment UE may send a registration information stream (Register), which may include the first capability information, to the application server AS. The first capability information may be used to indicate that the user equipment UE is capable of running a service on an IMS data channel of the internet protocol multimedia subsystem.
As an alternative, the first capability information may be indicated by a media feature tag (media feature tag) associated with the data closure exemption service (Data Off Exempted Services). Wherein, the data closing exemption service can be 3GPP PS data closing exemption service; the media feature tag may be a g.3gpp.ps-data-off media feature tag or a g.3 gpp.ici-ref media feature tag. Here, the g.3 gpp.ici-ref media feature tag may represent the traffic running on the IMS data channel in the IMS registration request.
Specifically, the UE may set the g.3gpp.ps-data-off media feature tag to a preset value, where the preset value is used to indicate that the 3GPP PS data of the UE is in an off state, so as to indicate that the 3GPP PS data of the UE is in an off state. Here, the network may be an application server AS. In other words, the user equipment UE may inform the network device what its current 3gpp ps data off state is by being a g.3gpp.ps-data-off media feature tag.
As an alternative, the user equipment UE may add a first tag in the g.3gpp.ps-data-off media feature tag in case it determines that the 3gpp ps data off state is "active". The first tag may be a media feature tag related to 3GPP PS data closed exemption service.
In a specific embodiment, the user equipment UE may perform IMS registration, i.e. send a registration information flow to the application server AS, after obtaining the IP connection. Specifically, the UE may send the registration information flow to the application server AS through the P-CSCF and the I-CSCF, or the UE may send the registration information flow to the application server AS through the P-CSCF and the S-CSCF.
In some embodiments, based on an initial filtering rule (initial filter criteria) for the correct application server AS, the serving call session control entity S-CSCF, after receiving the registration information flow sent by the user equipment UE, may send the registration information to the application server AS through third party registration (third party registration) and execute the corresponding traffic control procedure.
As known from the above description, the transmission process of the registration information flow may be shown in fig. 9, and it may be known from fig. 9 that the UE may transmit the first registration information flow to the proxy call session control entity P-CSCF, and then transmit the second registration information flow to the querying call session control entity I-CSCF/serving call session control entity S-CSCF through the proxy call session control entity P-CSCF. In other words, the proxy call session control entity P-CSCF may, after receiving the first registration information flow, send the second registration information flow to the querying call session control entity I-CSCF or may also send the second registration information flow to the serving call session control entity S-CSCF. On the basis of this, the querying call session control entity I-CSCF/serving call session control entity S-CSCF may send the third registration information flow to the application server AS.
In some implementations, the registration information flow may further include at least one of the following information: 3GPP PS data off state; public user identification; a private user identity; a home network domain name; and an internet protocol, IP, address of the user equipment, UE.
In other embodiments, the user equipment UE may receive a 200OK message flow sent by the application server AS, where the 200OK message flow may be used to indicate success of registration with respect to a service running on the IMS data channel.
Alternatively, the user equipment UE may receive a 200OK information flow sent by the application server AS via the P-CSCF and the I-CSCF/S-CSCF. AS shown in fig. 9, the querying call session control entity I-CSCF/serving call session control entity S-CSCF may receive the first 200OK information flow sent by the application server AS. On the basis, the querying call session control entity I-CSCF/serving call session control entity S-CSCF may send the second 200OK information stream to the proxy call session control entity P-CSCF, which may send the third 200OK information stream to the user equipment UE after receiving the second 200OK information stream. In other words, the user equipment UE may receive a 200OK information flow sent by the proxy call session control entity P-CSCF.
It should be noted that the use of multiple embodiments or features that are "or" spaced apart may not affect other aspects even if some of them are not possible. In addition, in the case of no contradiction, the embodiments of the present disclosure may be combined with other embodiments or implementations related to the methods for data traffic processing of the data channel signaling entity, the application server and the user equipment, and various alternatives thereof, which will not be described herein.
The disclosed embodiments provide that the user equipment may send a SIP invite request to the application server AS for the application server AS to send a data channel call request to the data channel signaling entity DCSF, where the data channel call request comprises first capability information, where the first capability information is used to indicate that the user equipment is capable of running traffic on an IMS data channel of the internet protocol multimedia subsystem, such that it may be ensured that an application dependent on the IMS data channel is still available in case the data of the user equipment is in a closed state. In addition, the user equipment can send the first capability information to the application server AS through the registration information flow, so that the effectiveness of data service processing can be improved.
Fig. 13 is a flow chart illustrating a method of data traffic processing according to yet another embodiment. As shown in fig. 13, the method may be used in a user equipment, including the following steps.
In step S810, in case that the 3GPP PS data off state is activated, a registration information flow is transmitted.
AS an alternative, the user equipment UE may send a registration information flow to the application server AS in case it is determined that the 3GPP PS data off state is activated. Specifically, the UE sends a registration information flow to the application server AS through the P-CSCF and the I-CSCF/S-CSCF in case it is determined that the data close button is triggered. In other words, the registration information flow may be sent to the application server AS each time the user equipment UE determines that its 3GPP PS data off state is activated.
In addition, the UE may send a registration information stream when it is determined that the 3GPP PS data off state of the UE is activated and a new 3GPP PS data off exempt service list sent by the network is received. Alternatively, the user equipment UE may transmit the registration information stream in case it is determined that the 3GPP PS data off state of the user equipment UE is activated and it is determined that the 3GPP PS data off state is changed.
It should be noted that the use of multiple embodiments or features that are "or" spaced apart may not affect other aspects even if some of them are not possible. In addition, in the case of no contradiction, the embodiments of the present disclosure may be combined with other embodiments or implementations related to the methods for data traffic processing of the data channel signaling entity, the application server and the user equipment, and various alternatives thereof, which will not be described herein.
The embodiment of the disclosure provides that the user equipment can send the registration information flow under the condition that the 3GPP PS data closing state is activated, so that the data service processing can be more accurately performed.
Fig. 14 is a flow chart illustrating a method of data traffic processing according to yet another embodiment. As shown in fig. 14, the method may be used in a user equipment, including the following steps.
In step S910, in the case where the 3GPP PS data off state is changed, a registration information flow is transmitted.
AS an alternative, the user equipment UE may send a registration information flow to the application server AS in case it is determined that the 3GPP PS data off state has changed. AS an example, the user equipment UE sends a registration information flow to the application server AS via the P-CSCF and the I-CSCF/S-CSCF in case it is determined that the 3GPP PS data off-state is switched from the active state to the inactive state.
AS another example, the user equipment UE sends a registration information flow to the application server AS via the P-CSCF and the I-CSCF/S-CSCF in case it is determined that the 3GPP PS data off-state is switched from the inactive state to the active state.
Alternatively, the user equipment UE may send the registration information stream upon determining that the 3GPP PS data off state of the user equipment UE is activated and that the 3GPP PS data off state is changed.
In summary, when the packet switched data closure is activated, the service on the IMS data channel may be configured as a part of the 3GPP PS data closure exemption service, and may still be used in the data closure state, so that the transmission of the data service may be more flexibly and effectively implemented.
It should be noted that the use of multiple embodiments or features that are "or" spaced apart may not affect other aspects even if some of them are not possible. In addition, in the case of no contradiction, the embodiments of the present disclosure may be combined with other embodiments or implementations related to the methods for data traffic processing of the data channel signaling entity, the application server and the user equipment, and various alternatives thereof, which will not be described herein.
The embodiment of the disclosure provides that the user equipment can send the registration information flow under the condition that the 3GPP PS data closing state is changed, so that the data service processing can be more accurately performed.
Fig. 15 is a block diagram illustrating a data channel signaling entity 1000, according to an embodiment. Referring to fig. 15, the data channel signaling entity 1000 may include a receiving module 1010.
The receiving module 1010 is configured to receive a data channel call request sent by an application server AS, the data channel call request comprising first capability information for indicating that the user equipment UE is capable of running a service on an internet protocol multimedia subsystem IMS data channel.
In some embodiments, the data channel call request further comprises at least one of:
the third generation partnership project 3GPP packet-switched PS data off state;
a session establishment request event;
a calling identifier;
a called identifier;
a session condition; and
and (5) session identification.
In some embodiments, the data channel signaling entity 1000 further comprises:
and the processing module is configured to adjust the service of the IMS data channel according to the 3GPP PS data closing state and/or an operator policy.
The embodiments of the present disclosure provide that a data channel signaling entity may receive a data channel call request sent by an AS, where the data channel call request includes first capability information, where the first capability information is used to indicate that a user equipment is capable of running a service on an IMS data channel, so that an application dependent on the IMS data channel may still be available when data of the user equipment is in a closed state.
Fig. 16 is a block diagram illustrating an application server 1100, according to one embodiment. Referring to fig. 16, the application server 1100 may include a receiving module 1110 and a transmitting module 1120.
The receiving module 1110 is configured to receive a session initiation protocol SIP invite request sent by a UE, where the SIP invite request is used for the AS to send a data channel call request to a DCSF;
a sending module 1120 configured to send a data channel call request to the DCSF, the data channel call request including first capability information for indicating that the UE is capable of running a service on an IMS data channel.
In some embodiments, the receiving module 1110 is further configured to receive the SIP invite request sent by the UE through a proxy call session control entity P-CSCF and a query call session control entity I-CSCF, or to receive the SIP invite request sent by the UE through a P-CSCF and a serving call session control entity S-CSCF.
In some embodiments, the receiving module 1110 is further configured to receive a registration information stream sent by the UE, the registration information stream including first capability information; the transmitting module 1120 is further configured to transmit the first capability information to the DCSF through the data channel call request.
In some embodiments, the registration information flow further includes at least one of the following information:
3GPP PS data off state;
public user identification;
a private user identity;
a home network domain name;
the UE's internet protocol IP address.
In some embodiments, the receiving module 1110 is further configured to receive, by the AS, the registration information flow sent by the UE through the P-CSCF and the I-CSCF, or receive, by the P-CSCF and the S-CSCF, the registration information flow sent by the UE.
In some embodiments, the SIP invite request includes the first capability information.
In some embodiments, the data channel call request further comprises at least one of:
3GPP PS data off state;
a session establishment request event;
a calling identifier;
a called identifier;
a session condition; and
and (5) session identification.
In some embodiments, the SIP invite request includes an initial session description protocol, SDP, that includes a bootstrap data path setup offer.
In the embodiment of the disclosure, the application server may receive a SIP invite request sent by the user equipment, where the SIP invite request is used for sending a data channel call request to the DCSF by the AS, and on this basis, send the data channel call request to the DCSF, where the data channel call request includes first capability information, where the first capability information is used to indicate that the user equipment is capable of running a service on an IMS data channel of the internet protocol multimedia subsystem, so that it may be ensured that an application dependent on the IMS data channel is still available when data of the user equipment is in a closed state.
Fig. 17 is a block diagram illustrating a user device 1200, according to an embodiment. Referring to fig. 17, the user device 1200 may include a transmission module 1210.
The sending module 1210 is configured to send a SIP invite request to an AS, where the SIP invite request is used for the AS to send a data channel call request to a DCSF, where the data channel call request includes first capability information, where the first capability information is used to indicate that the UE is capable of running a service on an IMS data channel.
In some embodiments, the data channel call request further comprises at least one of:
3GPP PS data off state;
A session establishment request event;
a calling identifier;
a called identifier;
a session condition; and
and (5) session identification.
In some embodiments, the sending module 1210 is further configured to send the SIP invite request to the AS through the P-CSCF and the I-CSCF, or to send the SIP invite request to the AS through the P-CSCF and the S-CSCF.
In some implementations, the sending module 1210 is further configured to send a registration information flow to the AS, the registration information flow including the first capability information.
In some embodiments, the registration information flow further includes at least one of the following information:
3GPP PS data off state;
public user identification;
a private user identity;
a home network domain name;
the UE's internet protocol IP address.
In some embodiments, the sending module 1210 is further configured to send the registration information flow to the AS through the P-CSCF and the I-CSCF, or send the registration information flow to the AS through the P-CSCF and the S-CSCF.
In some embodiments, the UE sends the registration information flow to the AS when a 3GPP PS data off state is activated and/or when the 3GPP PS data off state changes.
In some embodiments, the SIP invite request includes the first capability information.
In some embodiments, the SIP invite request includes an initial session description protocol, SDP, that includes a bootstrap data path setup offer.
Embodiments of the present disclosure provide that a user equipment may send a SIP invite request to an AS, the SIP invite request being used by the AS to send a data channel call request to a DCSF, where the data channel call request includes first capability information, where the first capability information is used to indicate that the user equipment is capable of running a service on an IMS data channel of an internet protocol multimedia subsystem, so that it may be ensured that an application dependent on the IMS data channel is still available in case the data of the user equipment is in a closed state.
The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein.
The present disclosure also provides a computer readable storage medium having stored thereon computer program instructions which, when executed by a processor, implement the steps of the method of data traffic processing provided by the present disclosure.
The present disclosure also provides a communication system, which may include a data channel signaling entity, an application server, and a user equipment, where the data channel signaling entity may perform the steps of the method related to data traffic processing of the data channel signaling entity in the above embodiments; the application server may perform the steps of the method of the above embodiments relating to data traffic handling of the application server; the user equipment may perform the steps of the method of the above embodiments involving data traffic handling of the user equipment.
Fig. 18 is a block diagram illustrating a communication apparatus 1300, which communication apparatus 1300 may be a user device, according to an embodiment. For example, the communications apparatus 1300 can be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, an exercise device, a personal digital assistant, a smart car, and the like.
Referring to fig. 18, a communications apparatus 1300 can include one or more of the following: a processing component 1302, a memory 1304, a power component 1306, a multimedia component 1308, an audio component 1310, an input/output interface 1312, a sensor component 1314, and a communication component 1316.
The processing component 1302 generally controls overall operation of the communications device 1300, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 1302 can include one or more processors 1320 to execute instructions to perform all or part of the steps of the methods for data traffic processing described above. Further, the processing component 1302 can include one or more modules that facilitate interactions between the processing component 1302 and other components. For example, the processing component 1302 may include a multimedia module to facilitate interaction between the multimedia component 1308 and the processing component 1302.
The memory 1304 is configured to store various types of data to support operations at the communications apparatus 1300. Examples of such data include instructions for any application or method operating on the communications device 1300, contact data, phonebook data, messages, pictures, video, and the like. The memory 1304 may be implemented by any type or combination of volatile or nonvolatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.
The power supply component 1306 provides power to the various components of the communications device 1300. Power supply components 1306 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for communication device 1300.
The multimedia component 1308 includes a screen between the communications device 1300 and the user that provides an output interface. In one embodiment, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may sense not only the boundary of a touch or slide action, but also the duration and pressure associated with the touch or slide operation. In one embodiment, the multimedia component 1308 includes a front-facing camera and/or a rear-facing camera. When the communications device 1300 is in an operational mode, such as a shooting mode or a video mode, the front camera and/or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have focal length and optical zoom capabilities.
The audio component 1310 is configured to output and/or input audio signals. For example, the audio component 1310 includes a Microphone (MIC) configured to receive external audio signals when the communication device 1300 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may be further stored in the memory 1304 or transmitted via the communication component 1316. In one embodiment, the audio component 1310 also includes a speaker for outputting audio signals.
The input/output interface 1312 provides an interface between the processing component 1302 and peripheral interface modules, which may be a keyboard, click wheel, buttons, etc. These buttons may include, but are not limited to: homepage button, volume button, start button, and lock button.
The sensor assembly 1314 includes one or more sensors for providing status assessment of various aspects of the communications device 1300. For example, the sensor assembly 1314 may detect an open/closed state of the communication device 1300, a relative positioning of the components, such as a display and keypad of the communication device 1300, the sensor assembly 1314 may also detect a change in position of the communication device 1300 or a component of the communication device 1300, the presence or absence of a user's contact with the communication device 1300, an orientation or acceleration/deceleration of the communication device 1300, and a change in temperature of the communication device 1300. The sensor assembly 1314 may include a proximity sensor configured to detect the presence of nearby objects in the absence of any physical contact. The sensor assembly 1314 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In an embodiment, the sensor assembly 1314 may also include an acceleration sensor, a gyroscopic sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
The communication component 1316 is configured to facilitate communication between the communications apparatus 1300 and other devices, either wired or wireless. The communications device 1300 may access a wireless network based on a communications standard, such as WiFi,2G, or 3G, or a combination thereof. In one exemplary embodiment, the communication component 1316 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 1316 further includes a Near Field Communication (NFC) module to facilitate short range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, ultra Wideband (UWB) technology, bluetooth (BT) technology, and other technologies.
In an exemplary embodiment, the communications apparatus 1300 can be implemented by one or more Application Specific Integrated Circuits (ASICs), digital Signal Processors (DSPs), digital Signal Processing Devices (DSPDs), programmable Logic Devices (PLDs), field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic elements for performing the methods of data traffic processing described above.
In an exemplary embodiment, a non-transitory computer readable storage medium is also provided, such as a memory 1304 including instructions executable by the processor 1320 of the communications device 1300 to perform the method of data traffic processing described above. For example, the non-transitory computer readable storage medium may be ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.
The apparatus may be a stand-alone electronic device or may be part of a stand-alone electronic device, for example, in one embodiment, the apparatus may be an integrated circuit (Integrated Circuit, IC) or a chip, where the integrated circuit may be an IC or may be a collection of ICs; the chip may include, but is not limited to, the following: GPU (Graphics Processing Unit, graphics processor), CPU (Central Processing Unit ), FPGA (Field Programmable Gate Array, programmable logic array), DSP (Digital Signal Processor ), ASIC (Application Specific Integrated Circuit, application specific integrated circuit), SOC (System on Chip, SOC, system on Chip or System on Chip), etc. The integrated circuit or chip may be configured to execute executable instructions (or code) to implement the method of data traffic processing described above. The executable instructions may be stored on the integrated circuit or chip or may be retrieved from another device or apparatus, such as the integrated circuit or chip including a processor, memory, and interface for communicating with other devices. The executable instructions may be stored in the memory, which when executed by a processor implement the method of data traffic processing described above; alternatively, the integrated circuit or chip may receive executable instructions through the interface and transmit the executable instructions to the processor for execution to implement the method for data traffic processing described above.
In another exemplary embodiment, a computer program product is also provided, comprising a computer program executable by a programmable apparatus, the computer program having code portions for performing the above-described method of data traffic processing when executed by the programmable apparatus.
Fig. 19 is a block diagram of a communication apparatus 1400, which communication apparatus 1400 may be a network device, is shown in accordance with an exemplary embodiment. For example, the communication device 1400 may be provided as a server. Referring to fig. 19, the communication device 1400 includes a processing component 1422 that further includes one or more processors, and memory resources represented by memory 1432, for storing instructions, such as applications, executable by the processing component 1422. The application programs stored in memory 1432 may include one or more modules, each corresponding to a set of instructions. Further, the processing component 1422 is configured to execute instructions to perform a method of data traffic processing.
The communication device 1400 may also include a power component 1426 configured to perform power management of the communication device 1400, a wired or wireless network interface 1450 configured to connect the communication device 1400 to a network, and an input/output interface 1458. The communications device 1400 may operate based on an operating system, such as Windows Server, stored in the memory 1432 TM ,Mac OS X TM ,Unix TM ,Linux TM ,FreeBSD TM Or the like.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure. This disclosure is intended to cover any adaptations, uses, or adaptations of the disclosure following the general principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.