Method for coordinating paging occasions on a common paging channel

Integrated method for calling events on shared un-call channels

The present invention generally relates to the field of wireless communications. More particularly, the present invention relates to a mechanism for providing call services in a cellular network.

In traditional third-generation (3G) cellular networks, point-to-point (PtP) and point-to-multipoint (PtM) call institutions must provide efficient use of wireless call resources while still maintaining low user equipment (UE) power consumption. The call system is used to establish a connection and initiate transmission. For point-to-point services, the call signal transmitted to the user equipment is associated with the unique identifier assigned to the user equipment. The user equipment is expected to be in the passive call state for a long period of time to wait for the call indication. Therefore, the power consumption when the user equipment is in the call state must be minimized. To achieve this, call events are scheduled in the user equipment and the network. This allows the user equipment to minimize the transmission and reception processing between call events, which will result in a reduction in power consumption and a corresponding increase in battery life.

For point-to-point services, the physical call channel and call event are determined from the unique identifier of each user device. The motivation for using the user equipment identifier is to provide a substantially equal distribution of all call resources for call transmission.

System information block type 5 (SIB5) defines the shared channel used in "idle" mode, and system information block type 6 defines the shared channel used in "connected" mode. In the cell, one or more call transmission channels (PCH) can be established. Each secondary shared control physical channel (SCCPCH) marked with system information to the user equipment can carry a call transmission channel. Therefore, for each defined call transmission channel, there is a unique associated call indicator channel (PICH) that is also marked. When more than one single call transmission channel and related call indicator channels are defined in system information block type 5 or system information block type 6, the user equipment is listed in the system information block type based on the International Mobile Subscriber Identity (IMSI) 5 or system information block type 6 choose the secondary shared control entity channel as follows:

Selected secondary shared control entity channel index = IMSI mod K; equation (1)

Where K is equal to the number of listed secondary shared control entity channels that carry a call transmission channel (that is, the secondary shared control entity channels only carry forward access channels (FACH) that should not be counted. These secondary shared control entities Channels are marked from 0 to K-1 in the order in which they appear in system information block type 5 or system information block type 6.

Channels are marked from 0 to K-1 in the order in which they appear in system information block type 5 or system information block type 6.

Therefore, the user equipment selects the physical call channel from the call channel list according to the number of selected call channels as follows:

Number of selected calling channels = user equipment identifier mod K; equation (2)

Where K is the number of physical call channels existing in the cell. Equation (2) can randomly allocate user equipment between calling channels.

The user equipment can use Discontinuous Reception (DRX) in idle mode or connected mode to reduce power consumption. When discontinuous reception is used, the user equipment only needs to monitor a call indicator (PI) for a call event every discontinuous reception period. The user equipment can be attached to different core network domains with different core network (CN) domain specific discontinuous reception cycle lengths. The user equipment may store the specific discontinuous reception period length of each core network domain for each core network domain to which the user equipment is attached, and use the shortest discontinuous reception period length. The length of the discontinuous reception period used in the UTRAN connection mode is the shortest of the following:

(1) The length of the discontinuous reception period of the global wireless access network; or

(2) Any stored core network domain specific discontinuous reception period length that does not have a transmission signal establishment for the core network domain to which the user equipment is only attached.

The user equipment uses the international mobile user identity, carries the secondary common control entity channel of the call transmission channel (K), the cell system frame number (SFN), Np, frame offset, call block periodicity (PBP), and The length of the discontinuous reception period determines the call event.

For Frequency Division Duplex (FDD), Np is the number of call indicators in the frame, and the frame offset is equal to zero. In the frequency division duplex, the user equipment can monitor the call indicator in the call indicator channel by the cell system frame number given by the call event.

For Time Division Duplex (TDD), Np is the number of call indicators in the call block, and the offset value of the call indicator channel box is given in the system information.

In time-sharing duplex, the user equipment can monitor the call indicators in the call block given by the call event. The call event gives the cell system frame number of the first frame of the call block.

The call event value system is determined as follows:

Call event={(IMSI div K)mod(DRX cycle length div PBP)}*PBP+n*DRX cycle length+frame offset; equation (3)

Among them, as long as the number of cell system frames is lower than its maximum value, n=0,1,2.... The actual call indicator in the call event that the user equipment should read is also determined based on the international mobile user identity.

The call index used is calculated using the following formula:

PI=DRX index mod Np; equation (4)

Where DRX indicator = IMSI div 8192.

In the time-sharing duplex mode, the call message reception event is calculated using the following formula:

Call message reception event=Call event+NPICH+NGAP+{(DRX indicator mod Np)mod NPCH}*2; equation (5)

The NPICH value is the number of frames used for the call indicator channel, and is equal to the received length of the call indicator channel given in the system information. The NGAP value is the number of frames between the last frame of the carrier call indicator channel of this call event and the first frame of the carrier call indicator channel of this call event. The NPCH value is the number of calling groups. The NPCH and NGAP values are given in the system information.

Therefore, the user equipment can determine the call event identified by the unique radio frame number on the selected call indicator channel according to the following:

Number of call event frames = (user equipment identifier div K) mod (DRX cycle length) + n* (DRX cycle length); equation (6)

Among them, DRX is discontinuous reception.

Equation (6) can identify the number of frames in each discontinuous reception period and then apply it to each successive period.

In a time-sharing duplex system, call block periodicity and frame offset are also considered. The motivation for using the user equipment identifier is to provide an approximately equal distribution of all call resources for call transmission.

The first figure depicts that the user equipment may have to receive individual call events and physical call channels to receive user group and user equipment specific calls. In the first figure, "UP" 105 represents a user equipment specific call event; "GP" 110 represents a user group call event; and "X" 115 represents a user equipment in discontinuous reception. A more effective way to perform group calls is expected.

The present invention defines a user equipment call mechanism that can synchronize user-specific and user group call events to support broadcast and multicast services. The call mechanism system can integrate user-specific and user group call events on the shared call channel. The present invention can apply the point-to-multipoint group call service to similar call channels and event determination logic, so that the above equations (2) and (6) can be replaced by a shared user group identifier. This enables a call channel and call event group to be associated with a specific point-to-multipoint user group. The advantage of the point-to-multipoint user group call is that the physical resources of each cell call are only required once per user group instead of once per user in the group.

The present invention can define a user equipment call mechanism in a wireless system, which can synchronize user-specific and user group call events by forcing call transmission channels and call events to be the same, so that users can save battery and call The channel is used more efficiently. When the call transmission channel during a specific call is a call event, the calling organization only has to wake up once to look for the call message during the period. Because the call organization does not need to continuously and individually monitor the call transmission channel for point-to-point and point-to-multipoint call events.

Thereafter, the user equipment is a wireless transmission/reception unit (WTRU), which includes, but is not limited to, mobile stations, fixed or mobile subscriber units, pagers, or any other types of devices that can operate in a wireless environment.

According to the present invention, the specific channel and the call events on the channel are always known by the user equipment and the network. As shown in the second figure, the system reveals the mechanism that integrates user-specific and user group call events on the shared call channel. In this figure, the term UP is a user equipment specific call event; GP is a user group call event and X is a user equipment in discontinuous reception mode.

Referring to the third figure, a program 300 according to the present invention is shown. The shared identity management function or the integration between the user group and user specific identity management functions can provide the identity that associates the shared call channel and the call event. According to the procedure 300, the new temporary user specific identification system is assigned to the implementation of the point-to-multipoint service for all user devices in the user group (step 305). The temporary user specific identifier can associate the call channel of the same entity and the call event related to the group call.

In step 310, the user equipment selects a physical call channel from the call channel list. The call channel is based on the following selection:

Number of selected calling channels = user equipment identifier mod K; equation (7)

Where K is the number of physical call channels existing in the cell.

The user equipment can then determine the call event identified by the unique wireless frame number on the selected call indicator channel (step 315), where:

Number of call event frames = (user equipment temporary identification body div K) mod (DRX cycle length) + n* (DRX cycle length); equation (8)

Call channels and call events can continue to be determined from the low-level bits of the assigned identifier. In this example, high-level bits can be used to distinguish user device specific and user group call events.

According to the present invention, the user equipment has a shared call event for user-specific and point-to-multipoint user group calls. There is no need to increase the number of call events for point-to-multipoint services. Therefore, there is no need to increase the power consumption for implementing point-to-multipoint services.

When a call event occurs, the user equipment checks the user equipment specific call identifier and the point-to-multipoint user group identifier. Depending on the received identity, the call type is known by the user equipment. Alternatively, it is possible to provide a common identifier and determine the user equipment specific or point-to-multipoint group call in the cause of the related outgoing call. Therefore, when the user equipment reads its call event, it can read the called identity and the cause of the call, and any of them can indicate the service type (point-to-point or point-to-multipoint).

Depending on the maximum number of users per call event, it may be necessary to assign user-specific call events to user groups across more than one physical call channel and call events. For large point-to-multipoint user groups, several point-to-multipoint identification systems can be provided so that individual call events are not saturated. Each point-to-multipoint identification system is associated with a subset of calls in the point-to-multipoint user group.

The subset call identification system is generated for the related call events required by each entity call channel and point-to-multipoint user group. When a point-to-multipoint user group call is required, each subset call identification system is applied to its related call channels and call events.

As mentioned above, the user equipment identification system is used to determine call channels and call events. The present invention provides a point-to-multipoint service call for multiple users. Usually, these users have different calling channels and different events. One of the objectives of the present invention is to create an equal distribution of call events for the entire call transmission channel, so that physical resources can be effectively configured. Otherwise, if the calls are not distributed equally, there will be a period when the call transmission channel is not fully utilized. The occurrence of excess calls during a specific call event will cause call overflow and loss of the opportunity to call the user's equipment in response to the call event.

The user identification system is used to create equal distribution. For point-to-multipoint services provided to multiple users with user equipment that must wake up and recognize calls, the present invention can minimize the total number of calls. For example, if fifty users are served point-to-multipoint, it is not expected to call all fifty users individually. The present invention can execute a set of call events generated by the network to receive the service by using a single set of call events used to wake up the user equipment of the fifty users.

In the preferred embodiment of the present invention, the point-to-multipoint service system is synchronized so that the temporary identification system is used to synchronize the call events of the point-to-point and point-to-multipoint services. Temporary identification systems are generated for point-to-point and point-to-multipoint services, or shared identifiers can be established for both (for example, when a call is caused by certain non-"high-order bits", the method is used to determine point-to-point and point-to-point services). To many points). Only the low-level bits of the call identifier or the user equipment identifier are used to determine the call event. High-level bits can be used to determine whether point-to-point and point-to-multipoint services are used. When the user equipment receives a call, a match on the specific call identifier of the user equipment occurs. Therefore, it is not only necessary to find out the call event on the call channel assigned to the user equipment, when the call event is viewed, the value of the sent signal at the call identifier is used to indicate whether the service is point-to-point and point-to-multiple. The call identifier of the point is also checked. Alternatively, it also has a call cause that is received together with the call identifier. The call cause can send a signal to the user, whereby the shared identifier can be identified and the related call cause can be reviewed to determine whether the service is point-to-point or point-to-multipoint.

For a very large number of users (such as 1000 users) in a point-to-point group, when a specific call event is forced to calibrate a point-to-multipoint call event, too many point-to-point call events or users can withdraw from the same call event, resulting in the call Saturation of events. Furthermore, the user assignment of all available call events is missing. Therefore, it is not expected that all call events of a large number of users will be gathered on a single call event.

Referring to the fourth figure, the user equipment can select a physical call channel from the call channel list according to the procedure 400 (step 405). Call events are set by keeping track of call channels and call event assignment logic. More than one point-to-multipoint call event system was created for very large groups. The user group related to this point-to-multipoint group is associated with the individual of the point-to-multipoint call event. For example, if there are currently 1000 users but only a maximum of 100 users are allowed to be associated with any call event, then a system of 10 call events with 100 users related to each other is created, so that the 100 users The associated user equipment will wake up normally during a call event and look for the point-to-point and point-to-multipoint identification numbers to determine which services are activated (step 410). Because it is used for point-to-multipoint services, the number of user devices per call event must be limited, and call channels and call events are not allocated equally. Among the 1000 users who are listening, 100 groups will focus on specific call events, so when the point-to-multipoint service is established, 10 call lines are generated, a group for 100 users (step 415 ).

Referring to the fifth figure, the radio network controller 500 can determine how the call event is set by keeping track of the call channel and call event assignment logic. The wireless network controller 500 includes a shared identity management function device 505, a call channel tracking device 510, a call event assigning logic device 515, and a call channel generating device 520. The shared identifier management function device 505 can provide identifiers associated with the shared call channel and call events. The calling channel tracking device 510 can set a calling event by keeping track of the calling channel. The call event assignment logic device 515 keeps track of the call event assignment logic. The call channel generating device 520 can associate the user group of the point-to-multipoint group with the individual of the point-to-multipoint call event.

Although the present invention has been specifically shown and described with reference to the preferred embodiments, those skilled in the art should understand that various changes in various forms and details can be made without departing from the scope of the present invention described above.

<p>105. . . User device specific call event</p><p>110. . . User group call event</p><p>115. . . User equipment in discontinuous reception</p><p>500. . . Wireless network controller</p><p>505. . . Shared identifier management function device</p><p>510. . . Call channel tracking device</p><p>515. . . Call event assignment logic device</p><p>520. . . Call channel generating device</p>

Figure 1 is a block diagram depicting traditional independent user specific and user group call events on individual entity call channels;

Figure 2 is a block diagram depicting the integration of user-specific and user group call events on a shared call channel according to the present invention;

Figure 3 is a flow chart of a method for synchronizing call services by calling multiple users with a temporary identifier according to an embodiment of the present invention;

Fig. 4 is a flowchart of the method steps of a call subset including a plurality of users according to another embodiment of the present invention; and

Figure 5 shows the radio network controller (RNC) used to integrate user specific and user group call events.