Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L12/00—Data switching networks
  • H04L12/02—Details
  • H04L12/16—Arrangements for providing special services to substations
  • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W48/00—Access restriction; Network selection; Access point selection
  • H04W48/02—Access restriction performed under specific conditions
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L12/00—Data switching networks
  • H04L12/02—Details
  • H04L12/16—Arrangements for providing special services to substations
  • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
  • H04L12/1813—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for computer conferences, e.g. chat rooms
  • H04L12/1818—Conference organisation arrangements, e.g. handling schedules, setting up parameters needed by nodes to attend a conference, booking network resources, notifying involved parties
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
  • H04W12/08—Access security
  • H04W12/086—Access security using security domains
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L12/00—Data switching networks
  • H04L12/02—Details
  • H04L12/16—Arrangements for providing special services to substations
  • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
  • H04L12/189—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast in combination with wireless systems
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L63/00—Network architectures or network communication protocols for network security
  • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
  • H04L63/102—Entity profiles
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
  • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
  • H04W4/10—Push-to-Talk [PTT] or Push-On-Call services

Definitions

• the present invention relates to point to point or point to multi-point communications systems. More specifically, the present invention relates to methods and apparatus for restricting inbound and/or outbound media communication for users within a group wireless communication network.
• a class of wireless services intended for quick, efficient, one-to-one or one-to- many (group) communication has existed in various forms for many years.
• these services have been half-duplex, where a user presses a "push-to-talk" (PTT) button on a phone/radio to initiate a group communication. If granted the floor, the talker then generally speaks for a few seconds. After the talker releases the PTT button, other users who are available may request the floor.
• PTT push-to-talk
• a service provider (carrier) or an enterprise may have reasons to limit the list of people that a user may communicate with. Users may also need to place restriction on who they receive media from such as blocking the dating group during office hours or parents wanting to restrict the targets that their children may contact.
• the disclosed embodiments provide novel and improved methods and apparatus for restricting media communication in a wireless communication network.
• the method provides for restricting media communication in a wireless communication network includes receiving an indication from an originator for setting up a media communication session with at least one target, applying at least one media communication restriction, and sending a request for setting up the media communication if the originator is allowed to have media communication with the target.
• the method includes receiving a request from a communication device for setting up a media communication session with at least one target, applying at least one media communication restriction on the target, and sending a media communication announcement to the target if the target is not restricted to receive media communication from the originator.
• the method includes receiving a media communication announcement for setting up a media communication session requested by an originator, applying at least one media communication restriction, and sending an acceptance for setting up the media communication if the originator is allowed to have media communication with the target.
• an apparatus for restricting media communication in a wireless communication network includes a memory unit, a receiver, a transmitter, and a processor communicatively coupled with the memory unit, the receiver, and the transmitter.
• the processor is capable of carrying out the above-mentioned methods.
• FIG. 1 illustrates a group communications system
• FIG. 2 illustrates how several communication devices interact with a group communication server;
• FIG. 3 illustrates one embodiment for an infrastructure for implementing various disclosed embodiments; and
• FIG. 4 illustrates a flow diagram for establishing a restricted media communication session.
• FIG. 1 illustrates a functional block diagram of a group communication system 100, for implementing one embodiment.
• Group communication system 100 is also known as a push-to-talk (PTT) system, a net broadcast service (NBS), a dispatch system, or a point-to-multi-point communication system, hi one embodiment, group communication system 100 includes a group communication server (GCS) 102, which may be deployed in either a centralized deployment or a regionalized deployment.
• GCS group communication server
• Group communication server 102 may be implemented as known in the art, including one or more processor, one or more memory units, and input/out hardware and software modules for various media communications, e.g., IP media communication.
• Group communication devices (CDs) 104 and 106 which may be deployed such as CDMA (e.g., cdma2000) handsets, for example, may request packet data sessions using a data service option. Each CD may use the session to register its Internet protocol (IP) address with the group communication server to perform group communication initiations.
• group communication server 102 is connected to the service provider's packet data service nodes (PDSNs) through service provider's network 116.
• CDs 104 and 106 upon requesting packet data sessions from the wireless infrastructure, may have IP connectivity to group communication server 102 through the PDSNs 114.
• Each PDSN may interface to a base station controller (BSC) through a packet control function (PCF) 108 and a network 112.
• BSC base station controller
• PCF packet control function
• the PCF may be co-located with the BSC within a base station (BS) 110.
• a packet data service node may fall in one of several states, e.g., active or connected state, dormant state, and null or inactive state.
• active or connected state a active traffic channel exists between the participating CD and the BS or BSC, and either side may send data.
• dormant state no active traffic channel exists between the participating CD and the BSC, but a point-to-point protocol (PPP) link is maintained between the participating CD and the PDSN.
• PPP point-to-point protocol
• Each one of CDs 104 and 106 may request packet data sessions. As part of establishing a packet data session, each CD may be assigned an IP address. Each CD may perform a registration process to notify group communication server 102 of the CD's IP address. Registration may be performed using an IP protocol, such as session initiation protocol (SIP) over user datagram protocol (UDP). The IP address of a CD may be used to contact the CD when the corresponding user is invited into or informed of a group communication.
• SIP session initiation protocol
• UDP user datagram protocol
• CDs 104 and 106 and group communication server 102 may exchange media and signaling messages.
• media may be exchanged between the participating CDs and the group communication server by using real-time protocol (RTP) over UDP.
• RTP real-time protocol
• the signaling messages may also be exchanged by using a signaling protocol over UDP.
• Group communication system 100 performs several different functions in order to operate group communication services.
• the functions that relate to the user side include user registration, group communication initiation, group communication termination, sending messages to group participants, late join to a group communication, talker arbitration, adding members to a group, removing members from a group, un-registering a member, and user authentication.
• the functions that relate to system preparation and operation include administration and provisioning, scalability, and reliability.
• FIG. 2 illustrates a group communication arrangement 200 for showing how CDs 202, 204, and 206 interact with a group communication server 208.
• Multiple group communication servers may be deployed as desired for large-scale groups.
• a user may input her desire to a CD 202, 204, 206 to initiate a communication session for exchanging communication media, e.g., data, voice, image, and/or video, with one or more CDs.
• the user may first invite the target users(s) before starting to communicate media, by pushing an "invite" or a PTT button on a CD.
• CD 202 when CD 202 has permission to transmit media to other members of the group, CD 202 is known as the originator and may transmit media over an established channel. When CD 202 is designated as the originator, the remaining participants, CD 204 and CD 206, may not be permitted to transmit media to the group. Accordingly, CD 204 and CD 206 are designated as targets. As described above, CDs 202, 204, and 206 are connected to group communication server 208, using at least one channel. In one embodiment, channels 210, 212, and 214 may include a session initiation protocol (SIP) channel, a media-signaling channel, and a media traffic channel.
• SIP session initiation protocol
• FIG. 3 is a simplified block diagram of one embodiment of an infrastructure including a base station/base station controller (BS/BSC) 304 and a communication device 306, which are capable of implementing various disclosed embodiments.
• BS/BSC base station/base station controller
• a communication device 306 which are capable of implementing various disclosed embodiments.
• voice, data, packet data, and/or alert messages may be exchanged between BS/BSC 304 and communication device 306, via an air interface 308.
• Various types of messages maybe transmitted, such as messages used to establish a communication session between the base station and the communication device, registration and paging messages, and messages used to control a data transmission (e.g., power control, data rate information, acknowledgment, and so on).
• voice and/or packet data e.g., from a data source 3
• messages e.g., from a controller 330
• TX transmit
• Each coding scheme may include any combination of cyclic redundancy check (CRC), convolutional, turbo, block, and other coding, or no coding at all.
• CRC cyclic redundancy check
• the voice, packet data, and messages may be coded using different schemes, and different types of messages may be coded differently.
• the coded data is then provided to a modulator (MOD) 314 and further processed (e.g., covered, spread with short PN sequences, and scrambled with a long PN sequence assigned to the communication device).
• the modulated data is then provided to a transmitter unit (TMTR) 316 and conditioned (e.g., converted to one or more analog signals, amplified, filtered, and quadrature modulated) to generate a reverse link signal.
• TMTR transmitter unit
• the reverse link signal is routed through a duplexer (D) 318 and transmitted via an antenna 320 to BS/BSC 304.
• the reverse link signal is received by an antenna 350, routed through a duplexer 352, and provided to a receiver unit (RCVR) 354.
• the antenna may be part of the wireless operator network, and the connection between the antenna and the BS/BSC may be routed through the Internet.
• BS/BSC 304 may receive media information and alert messages from communication device 306.
• Receiver unit 354 conditions (e.g., filters, amplifies, down converts, and digitizes) the received signal and provides samples.
• a demodulator (DEMOD) 356 receives and processes (e.g., despreads, decovers, and pilot demodulates) the samples to provide recovered symbols.
• Demodulator 356 may implement a rake receiver that processes multiple instances of the received signal and generates combined symbols.
• a receive (RX) data processor 358 then decodes the symbols to recover the data and messages transmitted on the reverse link.
• the recovered voice/packet data is provided to a data sink 360 and the recovered messages may be provided to a controller 370.
• Controller 370 may include instructions for receiving and sending information, receiving and sending responses to messages, identifying the targets, locating the targets, determining restrictions imposed on the originator and the targets, determining whether the originator and/or the targets are registered in the group communication system and/or whether at least one target accepts to receive media, and buffering media.
• the processing by demodulator 356 and RX data processor 358 are complementary to that performed at remote access device 306.
• Demodulator 356 and RX data processor 358 may further be operated to process multiple transmissions received via multiple channels, e.g., a reverse fundamental channel (R-FCH) and a reverse supplemental channel (R-SCH). Also, transmissions may be simultaneously from multiple communication devices, each of which may be transmitting on a reverse fundamental channel, a reverse supplemental channel, or both.
• R-FCH reverse fundamental channel
• R-SCH reverse supplemental channel
• voice and/or packet data e.g., from a data source 362
• messages e.g., from controller 370
• TX transmit
• MOD modulator
• TMTR transmitter unit
• the forward link signal is routed through duplexer 352 and transmitted via antenna 350 to remote access device 306.
• Forward link signals include paging signals.
• the forward link signal is received by antenna 320, routed through duplexer 318, and provided to a receiver unit 322.
• Receiver unit 322 conditions (e.g., down converts, filters, amplifies, quadrature modulates, and digitizes) the received signal and provides samples.
• the samples are processed (e.g., despreaded, decovered, and pilot demodulated) by a demodulator 324 to provide symbols, and the symbols are further processed (e.g., decoded and checked) by a receive data processor 326 to recover the data and messages transmitted on the forward link.
• the recovered data is provided to a data sink 328, and the recovered messages may be provided to controller 330.
• Controller 330 may include instructions for receiving and sending information, receiving and sending responses to messages, imposing restrictions on media communication traffic, determining the restriction imposed on the originator and/or the targets, buffering media, transmitting media to a group communication server, and granting permission to the originator to deliver media.
• a service provider carrier
• An enterprise or any other entity may have reasons to limit the list of people that a user may communicate with. Users may also need to place restriction on who they receive media from such as blocking the dating group during office hours or parents wanting to restrict the targets that their children may contact.
• media communication restrictions are configurable by both the carrier and the user, among other entities capable of defining media communication restriction.
• the carrier has the ultimate authority over some or all restrictions.
• Carrier-level restrictions provide the ability for the carrier to define for each user a subset of the carrier's user base within which commimication is allowed.
• User-level restrictions provide the ability for each user to define additional limitations on the communication between the user and the subset of users defined by the carrier- level restrictions.
• media communication restrictions may be specified as:
• ALLOW - communication is allowed but not required, i.e. ALLOW may be overridden by a DENY
• ALLOW_ALWAYS - communication is allowed and required, i.e. ALLOW_ALWAYS may not be overridden by a DENY
• communication may be allowed between all users in all domains, which may be viewed as an implicit "ALLOW all” entry as the first item in the carrier- level restriction list, enabling communication between all endpoints.
• Call restrictions may be applied as two independent ordered lists - one defined by the carrier and the other defined by each user.
• the ordering of the list may imply that the restriction entries at the end of the list override the entries at the beginning of the list.
• carrier-level restrictions may override the user-configured restrictions.
• Each media restriction entry may specify one of the following two types:
• the target's restrictions may be applied to the originator's user address only.
• the originator's restrictions may be applied on each entry in the target list specified in the media communication request.
• Each entry in the target list may be an ad-hoc group address, a chat-room address, or a user address. If a closed group address or closed chat-room address is specified, the restrictions may be applied to the group address only, and not to the members of the group.
• media restriction entries has the following syntax:
• token_to_match ⁇ user address, domain, or all (specified by the literal '*') ⁇
• type ⁇ DENY, ALLOW, or ALLOW_ALWAYS ⁇
• level ⁇ carrier or user ⁇
• Carrier-level restrictions may be configured at the time of user subscription and change infrequently during the duration of the subscription.
• User-level call restrictions may be configured by the user via an option on the user's CD. The anticipation is that user-level restrictions may change frequently.
• carrier-level restrictions define the limitations within which user-level restrictions may be further defined
• the carrier-level restrictions are delivered to the user's CD in order to provide the configuration of user-level restriction.
• Carrier-level and user-level media restrictions may be applied in two areas of the media communication setup process. Outbound media restrictions placed on the originator are applied at one of the initial steps of media communication setup. Inbound media communication restrictions placed on each target are applied when the group communication sever (GCS) is attempting to contact each target.
• GCS group communication sever
• outbound media communication restrictions are applied on outgoing calls only. Provided the carrier-level restrictions do not change frequently and the carrier-level restrictions have already been delivered to the user's CD, outbound restrictions are applied on the user's CD. Applying the outbound restrictions on the user's CD prior to each media communication origination eliminates the need to send a media communication setup request to the GCS for a media communication that cannot be established due to outbound restrictions. By eliminating these messages prior to using infrastructure resources to send a media communication setup request, a savings in the load on the infrastructure is gained, e. g, eliminating a single media communication setup request may result in a savings of a minimum of four GCS messages sent on the overhead channels and traffic channel.
• the inbound restrictions are applied on incoming calls only. Since the user-level restriction may change frequently, delivering and storing user-level restrictions on the server upon every update would add significant load to the system. Therefore, inbound user-level restrictions may be stored on the user's CD only. This results in the need to apply all (inbound and outbound) user level call restrictions on the user's CD only.
• Both the user's CD and the group communication server (GCS) may play a role in the enforcement of media communication restrictions.
• the restrictions imposed on an originator, both at carrier and user levels, are applied at the originator's CD prior to sending the communication setup request to the GCS.
• the carrier-level restrictions for each target are applied at the GCS, while the user (target)-level restrictions are applied when the communication announcement reaches the target's CD.
• FIG. 4 illustrates a process for establishing a restricted media communication session, according to one embodiment.
• the originator selects a member list and .presses the PTT button on his or her CD, as shown in step 402
• the originator's CD applies the outbound restrictions to all targets specified in the communication request, as shown in step 404.
• the targets may be specified by either users addresses and/or predefined group addresses.
• the domain portion of the group address is specified in the ⁇ token_to_match> field of the restriction entries.
• only the group address is checked against the restrictions, and each member in the group's membership list may not be checked against the restrictions.
• the originator's CD detects one or more restrictions that deny media communication establishment, the media communication setup is failed and the user is notified accordingly. If the user is allowed to communicate with all targets specified in the group's membership list, a "call request" is sent to the GCS or a regional dispatcher (RD), in step 406.
• the GCS or the regional dispatcher expands any closed groups included in the request to a list of users. Once the target list has been expanded to contain the user addresses, the GCS or the regional dispatcher verifies that the target list does not exceed the membership limit for the call type. After the regional dispatcher verifies the call is within the specified limit, the regional dispatcher locates all of the target users.
• the GCS or the regional dispatcher verifies that the call is within the specified participation limit for the call type. If the participation limit has not been exceeded, the GCS or the regional dispatcher applies the inbound carrier-level restrictions for each target to the originator's user address, as shown in step 408.
• the call proceeds without those targets being contacted.
• the GCS or the regional dispatcher may not modify the membership list of the call; therefore, every time the call is reestablished the target's call restrictions are applied, and if the communication is still denied, the target is not contacted anymore.
• the GCS or the regional dispatcher selects the vocoder and media control unit (MCU) using the reduced target list, and the GCS or the regional dispatcher sends out call announcements, as shown in step 410, to all targets in the reduced target list.
• the target's CDt receives the call announcement
• the target's CD applies the user-level inbound restrictions to the originator's user address, as shown in step 412, to determine if media communication is allowed. If communication is allowed, the target's CD acknowledges the call announcement, as shown in step 414, accepting the call. Otherwise, if communication is not allowed, the target's CD acknowledges the call announcement by rejecting the call.
• the GCS or the regional dispatcher Upon receipt of one or more acknowledgements accepting the call, the GCS or the regional dispatcher sends a "floor grant" message to the originator's CD, as shown in step 416, indicating the communication with one or more targets has been established, and permission to talk may be granted to the originator, as shown in step 418.
• the media communication restriction configuration system may not allow the user to add:
• carrier-level restrictions are applied first, starting from the last entry in the restriction list and proceeding until there is a match on an entry that specifies a DENY or until all entries in the restriction list have been evaluated. If a match on an entry that specifies an ALLOW_ALWAYS is found at the carrier level, all other restrictions against that address are ignored. If a match on an entry that specifies ALLOW is found at the carrier level, the user level restrictions are checked to determine if there is a match on an entry that specifies a DENY for that address. If a match occurs on either a carrier-level or a user-level DENY, the algorithm is aborted and the call is denied.
• Carrier-level restrictions may be configured using an interface into the carrier provisioning system.
• the carrier provisioning system is responsible for the distribution of the carrier-level restrictions to the GCS components and the CDs that are impacted by the change.
• User-level restrictions may be configured using an interface on the user's CD. The user is allowed to specify restrictions relating to user address or domains. The configuration application on the user's CD may verify the user-level restrictions do not attempt to override or contradict the carrier-level restrictions for that user.
• the carrier hi order for changes to the carrier-level restrictions for a particular user to be applied to a group communication involving the user in a timely fashion, the carrier notifies the GCS that changes have occurred. This may be done through two mechanisms. First, the carrier writes the new restrictions to a user and/or group database. If the user is not registered, the user's new restrictions are loaded upon the next registration. Second, the carrier notifies a home dispatcher (HD) that the user's restrictions have changed. The HD determines if the user is registered within the local carrier network. If the user is registered, the HD notifies the regional dispatcher (RD) that the uer's call restrictions need to be reloaded from the user and/or group database.
• HD home dispatcher
• Carrier-level restrictions may also be distributed to a user's CD via the application configuration access protocol (ACAP) provisioning interface.
• ACAP application configuration access protocol
• DSP digital signal processor
• ASIC application specific integrated circuit
• FPGA field programmable gate array
• a general-purpose processor may be a microprocessor, but, in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine.
• a processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
• the steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two.
• a software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
• An exemplary storage medium is coupled to the processor, such that the processor can read information from, and write information to, the storage medium.
• the storage medium may be integral to the processor.
• the processor and the storage medium may reside in an ASIC.
• the ASIC may reside in a user terminal.
• the processor and the storage medium may reside as discrete components in a user terminal.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Security & Cryptography (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• General Engineering & Computer Science (AREA)
• Multimedia (AREA)
• Mobile Radio Communication Systems (AREA)
• Data Exchanges In Wide-Area Networks (AREA)
• Telephone Function (AREA)
• Telephonic Communication Services (AREA)

Applications Claiming Priority (2)

Publications (1)

Family

ID=34422783

Family Applications (1)

Country Status (10)

Families Citing this family (10)

Family Cites Families (4)

• 2003
  • 2003-10-09 US US10/683,642 patent/US20050079858A1/en not_active Abandoned
• 2004
  • 2004-10-08 TW TW093130612A patent/TW200525997A/zh unknown
  • 2004-10-08 JP JP2006534314A patent/JP2007508748A/ja active Pending
  • 2004-10-08 AU AU2004306748A patent/AU2004306748A1/en not_active Abandoned
  • 2004-10-08 CN CNA2004800348264A patent/CN1886932A/zh active Pending
  • 2004-10-08 EP EP04794387A patent/EP1678872A1/de not_active Withdrawn
  • 2004-10-08 CA CA002542129A patent/CA2542129A1/en not_active Abandoned
  • 2004-10-08 WO PCT/US2004/033014 patent/WO2005036819A1/en not_active Application Discontinuation
  • 2004-10-08 KR KR1020067009025A patent/KR20060086959A/ko not_active Application Discontinuation
• 2006
  • 2006-04-28 EC EC2006006532A patent/ECSP066532A/es unknown

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events