CN1073328C - Method for communicating in a wireless communication system - Google Patents

Abstract

A communication system in which information is transmitted by grouping time slots into superframes, which in turn are divided into paging frames. In each paging frame, the remote station receives some paging messages.

Description

Method for selecting control channel in wireless communication network and base station and mobile station

This application contains subject matter related to co-pending U.S. Patent Application Serial No. 07/955,591, filed October 2, 1992, entitled "Method and Apparatus for Communication Control in a Wireless Telephone System"; Co-pending U.S. Patent Application No. 07/956,640, filed October 5, 1992, entitled "Digital Control Channel," and Application No. 07/047,452, filed April 19, 1993, entitled Co-pending US patent application for "Layer 2 Protocol for Random Access Channel and Access Response Channel." These three co-pending applications are incorporated herein by reference.

The present invention relates to wireless communication systems, and more particularly to methods and apparatus for communicating information in wireless communication systems including, for example, cellular wireless systems. cellular phone equipment

Cellular mobile phones are one of the fastest growing items in the worldwide telecommunications market. For example, between 1984 and 1992 the number of mobile phone subscribers in the United States increased from approximately 25,000 to over 10 million. By the end of 1995, it is estimated that the number of users will rise to nearly 22 million and by the year 2000 to 90 million.

Cellular telephone services operate much like fixed wireline telephone services in homes and offices, except instead of telephone lines, radio frequencies are used to connect telephone calls to and from mobile subscribers. Each mobile subscriber is assigned a private (10 digit) directory number and is billed based on the amount of "air time" he or she spends talking on the cell phone each month. Many of the service features available to landline users, such as call waiting, call forwarding, three-way calling, etc., are often also available to mobile users.

In the United States, the Federal Communications Commission (FCC) authorizes cellular licenses under a licensing scheme that divides the nation into geographic service markets as per the 1980 findings. Only two cellular licenses are authorized for each market. The two cellular systems are commonly referred to as the "A" system and the "B" system, respectively, in each market. Each of the two systems is assigned different frequency bands (referred to as segment A and segment B respectively) in the 800 MHz frequency band. To date, the FCC has allocated a total of 50MHz of frequency (25MHz per system) for cellular services.

Mobile subscribers have the freedom to receive service from either the A-system or the B-system operator (or both). The local system for booking services is called the home system. When moving ("roaming") out of the home system, the mobile subscriber can be served by the remote system if there is an agreement between the operators of the home system and the "visited" system. cellular system

In a typical cellular radio system, a geographic area, such as a metropolitan area, is divided into a number of smaller contiguous radio coverage areas called "cells". These cells are served by a series of fixed radio stations called "base stations". The base stations are connected to and controlled by a Mobile Services Switching Center (MSC). The MSC is in turn connected to the land (wired) Public Switched Telephone Network (PSTN). Telephone users (mobile subscribers) in cellular radio systems are equipped with portable (hand-held), transportable (hand-carried), or mobile (vehicle-mounted) telephone The base station performs voice and/or data communication with the MSC. The MSC switches calls between the wireline lines and the mobile subscribers, controls signaling to the mobile stations, collects billing statistics and provides for operation, maintenance and testing of the system.

Figure 1 shows the architecture of a conventional Honeycomb wireless system built in accordance with the Advanced Mobile Phone Service (AMPS) standard. In FIG. 1, an arbitrary geographic area can be divided into a plurality of contiguous wireless coverage areas, or cells C ₁ -C ₁₀ . Although the system of Figure 1 is shown to include only 10 cells for purposes of illustration, in practice the number of cells may be much greater. Associated with and located within each cell _C1 - _C10 is a base station denoted as a corresponding one of the plurality of base stations _B1 - _B10 . Each base station _B1 - _B10 comprises a plurality of channel units, each unit comprising a transmitter, receiver and controller as known in the art.

In Fig. 1, base stations B ₁ -B ₁₀ are located at the centers of cells C ₁ -C ₁₀ respectively, and are equipped with non-directional radios, which transmit equally in all directions. In this case, all channel elements in each base station B ₁ -B ₁₀ are connected to one antenna. However, in other cellular radio system compositions, the base stations _B1 - _B10 may be located near the perimeter, or conversely remote from the center of the cells _C1 - _C10 and may transmit radio signals directionally to the cells C1 _-C10 . C ₁₀ . For example, the base station can be equipped with three directional antennas, as shown in FIG. 2 , each antenna covers a sector cell of 120 degrees. In this case, some channel elements will be connected to antennas covering one sector cell, other channel elements will be connected to antennas covering another sector cell, and the remaining channel elements will are connected to the remaining antennas covering the remaining sector cells. Thus, in Figure 2, the base station serves three sector cells. However, it is not always necessary that there be three sector cells, but only one sector cell for covering eg roads or highways.

Returning to Fig. 1, each base station _B1 - _B10 is connected to a mobile switching center (MSC) 20 by a voice or data link, and said center is connected to a central office (not shown) in the public switched telephone network (PSTN). out) or similar facilities such as the Integrated Services Digital Network (ISDN). Between the mobile and switching center MSC20 and the base stations _B1 - _B10 , or between the mobile switching center MSC20 and the PSTN or ISDN, the corresponding connection and transmission modes are well known to those skilled in the art and may include twisted pairs Wire pair, coaxial cable, fiber optic cable or microwave radio channel operating in analog or digital mode. Alternatively, voice and data links can be provided by an operator, or leased from a telephone company (telco).

With continued reference to FIG. 1, a plurality of mobile stations M ₁ -M ₁₀ may be found in cells C ₁ -C ₁₀ . Again, although only 10 mobile stations are shown in Figure 1, in practice the actual number of mobile stations can be much greater and will greatly exceed the number of base stations. Also, while _{mobile stations M1-M10 may not be found in some of the cells C1-C10 , the presence or absence} of The mobile stations _M1 - _M10 depend on the individual needs of each mobile subscriber, which may move from one location in one cell to another, or from one cell to an adjacent or neighboring cell .

Each mobile station _M1 - _M10 includes a transmitter, a receiver, a controller and a user interface, such as a telephone handset, as is known in the art. Each mobile station _M1 - _M10 is assigned a Mobile Identification Number (MIN), which in the United States is a numerical representation of a mobile subscriber directory number. The MIN defines the mobile subscriber's subscription on the radio path and is sent from the mobile station to the MSC 20 at call origination and from the MSC 20 to the mobile station at call termination. Each mobile station M ₁ -M ₁₀ is also identified by an Electronic Serial Number (ESN), which is a factory set, "non-alterable" number used to prevent unauthorized use of the mobile station. For example, at call origination, the mobile station will send the ESN to MSC 20. MSC 20 compares the received ESN to the ESNs of a "black list" of mobile stations that have been reported stolen. If a match is found, access to the stolen mobile station will be denied.

Each cell _C1 - _C10 is assigned to a subset of the radio frequency (RF) channels assigned to the overall cellular system by a relevant government agency, such as the Federal Communications Commission (FCC) in the United States. Each subset of RF channels is divided into several voice or voice channels, which are used for voice conversations, and at least one paging/connection or control channel, which is used for each Management data messages are communicated between base stations _B1 - _B10 and mobile stations _M1 - _M10 . Each RF channel comprises a duplex channel (two-way radio transmission path) between a base station and a mobile station. The RF channel consists of a pair of independent frequencies, one frequency used by the base station for transmission (received by the mobile station) and one frequency used by the mobile station for transmission (received by the base station). In the base stations B ₁ -B ₁₀ , each channel unit usually works on a pre-selected radio channel assigned to the corresponding cell, that is, the transmitter (TX) and receiver (RX) of the channel unit are respectively tuned to cannot be changed of a pair of transmit and receive frequencies. However, the transceiver (TX/RX) of each mobile station _M1 - _M10 can be tuned to any radio channel specified by the system.

Depending on capacity needs, one cell may have 15 voice channels, while another cell may have more than 100 voice channels, and corresponding channel units. In general, however, there is only one control channel (CC) in each non-directional cell or sector cell served by one base station, i.e. the base station serving the non-directional cell (Fig. 1) will With one control channel element, a base station (FIG. 2) serving three sector cells will have three control channel elements. RF (control and voice) channels already assigned to any known cell can be reassigned to distant cells according to frequency reuse schemes known in the art. In order to avoid wireless interference, all wireless channels in the same cell will operate on different frequencies, and in turn, the wireless channels in any one cell will operate on a different set of frequencies than those used by any adjacent cells superior.

When in the idle state (powered on but not in use), each mobile station M ₁ -M ₁₀ tunes to and then continuously monitors the strongest control channel (generally, the control channel of the cell the mobile station is in at the moment) and A telephone call can be received or initiated via a corresponding one of the base stations _B1 - _B10 connected to the mobile switching center MSC20. While moving between cells, while idle, the mobile station will eventually "lose" the radio connection on the control channel of the "old" cell and switch to the control channel of the "new" cell. Both the initial tuning and the change of control channels are performed automatically during cellular system operation by scanning all control channels for the "best" control channel (there are 21 "dedicated" control channels in each AMPS system in the United States, i.e. Their TX/RX frequencies are predetermined and cannot be changed, which means that the mobile station has to scan a maximum number of 21 channels). When a control channel with good reception quality is found, the mobile station remains tuned to this channel until the quality deteriorates again. In this manner, all mobile stations are always "in touch" with the system.

While in the idle (standby) state, each mobile station _M1 - _M10 continuously determines whether a paging message addressed to it via the control channel has been received. For example, when a normal (landline) subscriber calls a mobile subscriber, the call is transferred from the PSTN to the MSC 20 where the dialed number is analyzed. If the dialed number is valid, MSC 20 requests some or all of base stations _B1 - _B10 to page the called mobile station through their respective cells _C1 - _C10 . Each base station B ₁ -B ₁₀ receiving a request from MSC 20 will then send a paging message contained in the MIN of the called mobile station over the control channel of the corresponding cell. Each idle mobile station _M1 - _M10 compares the MIN in the paging message received over the control channel being monitored with the MIN stored at the mobile station. The called mobile station matching the MIN automatically sends a paging response to the base station through the control channel, and the base station sends a paging response to the MSC20.

When a paging response is received, the MSC 20 selects an available voice channel in the cell to receive the paging response, switches on the transceiver of the selected voice channel, and requests the base station in the cell to command movement via the control channel The station tunes to the selected voice channel (the MSC maintains at any time a list of all channels in its service area and their status, ie idle, busy, blocked, etc.). The connection is established once the mobile station tunes to the selected voice channel.

On the other hand, when a mobile subscriber initiates a call by, for example, dialing a regular subscriber's telephone number and pressing the "send" key on the mobile station's telephone handset, the MIN and ESN of the mobile station and the dialed number pass through the control channel is sent to the base station and communicated to the MSC 20 which authorizes the mobile station, assigns a voice channel, and establishes a connected connection for the conversation as previously described.

If the mobile station moves between cells while in conversation, the MSC will perform a handoff of the call from the old base station to the new base station. The MSC selects an available voice channel in the new cell, and then orders the old base station to send a handover message to the mobile station on the current voice channel in the old cell, which notifies the mobile station to tune to the new cell. on the selected voice channel in the cell. Handoff messages are sent in a "space and burst" mode, causing short but hard-to-find interruptions during conversations. When the handover message is received, the mobile station tunes to the new voice channel and a connected connection is established by the MSC via the new cell. The old voice channel in the old cell is marked as free in the MSC and can be used for further conversations.

In addition to call origination and page response, AMPS mobile stations can access the cellular system for registration. Two types of registrations are possible in AMPS: (i) Periodic registrations, which are time-based, or more specifically based on the REGIP ("current time") and REGINCR values ("registration period") sent by the base station and stored in The NXTREG value ("wake-up time") in the mobile station, and (ii) based on the system area registration of the location, or more specifically the system identification (SID) transmitted in the serving cellular system. Periodic registration can be used to determine whether a mobile station is active (in radio range and switched on) or not in the cellular system. System area registration may be used exclusively to determine when a mobile station has crossed the boundary from one cellular system to another.

When a REGID message is received on the forward control channel (base station to mobile station), the mobile station compares the REGID value with the NXTRECT value, and compares the last received SID with the NXTRECT value if registration is permitted in the serving cellular system. The SID value of the cellular system where the mobile station was last registered. If the REGID value is greater than or equal to the NXTREG value, indicating that the periodic registration is correct, or the last received SID value is different from the last stored SID value, indicating that the mobile station has moved from one cellular system to another because the last successful registration, the mobile station will automatically send a registration access message over the reverse control channel (mobile station to the base station) and after receiving the registration confirmation message on the forward control channel with the last received REGID value and REGINCR The sum of the values updates the NXTREG value (the mobile station also updates the NXTREG value after each call origination or page response). Format of wireless transmission

Since its inception, the wireless transmission format in cellular systems has been analog Frequency Modulation (FM). In each cell, voice (analog) and data (digital) signals form the input signal to the transmitter (at the base or mobile station), resulting in a constant frequency corresponding to one of the frequencies assigned to that cell sine carrier. With FM, the carrier frequency is modulated (varied) in proportion to the instantaneous amplitude of the input signal. The modulated carrier occupies a relatively narrow spectral range of the nominal center frequency (the unmodulated carrier frequency). The resulting frequency offset of the modulated carrier frequency around the unmodulated (center) frequency is usually limited to a certain bandwidth (using a bandpass filter), e.g. 30KHz in the US, to avoid overlapping of adjacent RF channels and causing Adjacent channel interference. Therefore, each analog voice channel occupies 30KHz of spectrum, while a voice session requires 60KHz.

Thus, in a conventional AMPS system, an analog voice signal modulates a carrier for transmission over a wireless channel. The AMPS system utilizes analog frequency modulation (FM), which is a single channel per carrier (SCPC) system, ie, one voice circuit (telephone conversation) per RF channel. The wireless channel access scheme in the HMPS system is a frequency division multiple access (FDMA) scheme. In FDMA, multiple users have access to the same group of RF channels, and each user is assigned an available RF channel according to requirements, and different users Assign different RF channels. Moving from Analog to Digital

Recent developments have ushered in a new digital era of cellular communications. The main driving force behind the move to digital is the desire to increase spectral efficiency to meet the growing demands on system capacity. Since each cellular system is allocated a finite amount of radio spectrum, capacity can be increased by reducing the amount of bandwidth required for each voice channel or conversely by sharing each RF channel between several voice sessions. This is possible with digital technology.

By encoding (digitizing and compressing) the voice from several voice circuits before modulation and transmission, instead of being occupied by only one analog voice channel (one voice session), a single RF voice channel can be occupied by several digital voice channels shared. In this way, the channel capacity and overall system capacity can be increased significantly without increasing the bandwidth of the voice channel. As a corollary, cellular radio systems are able to serve a relatively large number of mobile stations at relatively low cost, eg requiring a relatively small number of channel elements (transceivers) in the base station. In addition, the digital format readily forms a cellular network in the form of a digital network.

In the United States, the transition from analog to digital has been led by the Electronics Industries Association (EIA) and the Telecommunications Industry Association, and EIA/TIA has taken on the task of systematically proposing common air interface standards to meet the industry requirements for next-generation digital cellular systems. To date, EIA/TIA has published two separate air interface standards based on different wireless channel multiple access schemes. The first EIA/TIA Interim Standard (IS) is based on the Time Division Multiple Access (TDMA) scheme and is called the "Dual Mode Mobile Station-Base Station Compatible Standard" (IS-54B). The second standard is based on the Code Division Multiple Access scheme (COMA) benchmark and is called "Mobile Station-Base Station Compatible Standard for Dual-Mode Wideband Spread Spectrum Cellular Systems" (PN-3118 published as IS-95). These standards are hereby incorporated by reference (copies of various revisions of IS-54B and PN-3118 are available from the Electronic Industries Association, 2001 Pennsylvania Avenue, N.W., Washington D.C. 20006.)

The term "dual mode" in both standards refers to the ability of a system to operate in either analog or digital mode. The analog mode of operation uses analog FM and utilizes the old EIA/TIA-553 standard based on the AMPS standard. Digital modes of operation use TDMA (IS-54B) or CDMA (PN-3118). The dual-mode capability facilitates popularization and application of digital systems by gradually reducing analog capabilities, that is, removing analog FM services from RF channels to provide digital services. This is considered a desirable step to ease the transition from analog to digital and to provide what is known as "backward" compatibility with existing analog systems. While analogue and digital modes of operation can exist separately, the aim is for them to co-exist, at least in the short term, in order to allow roaming within existing systems that cannot promote new digital technologies. During the transition phase, existing analog-only mobile stations will continue to provide service, while the use of digital-capable mobile stations and base stations becomes more widespread.

A mobile station following the specified specification (IS-54B or PN-3118) can be served from an analog-only base station, a digital-only base station, or an analog-digital (dual mode) base station. The type of system serving a mobile station will depend on the availability of digital services (TOMA or CDMA) in the mobile station's geographic area and the mobile subscriber's choice. A dual-mode mobile station can access an analog voice channel (AVC) or optionally a digital traffic channel (DTC) during call setup or handoff. However, analog-only or digital-only mobile stations can only be designated as AVC or DTC, respectively. TDMA system

TDMA is a multiple-access scheme that enables multiple simultaneous telephone conversations on one physical channel, based on time-division multiplexing (TDM) techniques already used in landline telephone networks. In the wired telephone network, the analog voice signal sent by the local telephone user to the central office of the local telephone company (telecom company) through a separate line (subscriber loop) is continuously sampled and the amplitude of the samples is quantized, and then in a method called Processes for Pulse Code Modulation (PCM) are encoded as binary numbers represented by pulses of constant amplitude. A predetermined number of PCM channels (digital voice channels) are transmitted in a series of frames, each frame containing a burst of information (encoded samples) from each PCM channel. On an actual channel, for example, bursts from different PCM channels occupy different time slots (time intervals) in each frame sent by copper wire equipment. Most long-distance telephone calls are routed using the TDM switching system. This technique can also be applied to the transmission of RF channels in cellular radio systems.

An RF channel operating in TDM mode is divided into a series of repeating time slots (periodic trains of time intervals), each time slot containing a burst of information from a different data source, such as encoded speech from a voice circuit source encoder. Timeslots are grouped into frames of predetermined duration. The number of time slots per frame varies with the number of digital channels one is trying to accommodate on the RF channel given the coding rate of the digital channel, the modulation level of the RF channel, and the bandwidth of the RF channel. Each time slot in a frame usually represents a different digital channel. Thus, the length of each TDM frame on the RF channel is the minimum amount of time between two repeating time slots used by the same digital channel (assigned to the same user). In other words, each TDM frame contains no more than one time slot per user.

According to IS-54B, each TDM RF channel can carry three to six digital voice channels (three to six phone sessions). The vocoder for each digital traffic channel (DTC) can operate at either full rate or half rate (full rate vocoders are expected to be used in the near future until half rate coders have been developed to produce acceptable voice quality). Full rate DTC requires twice as many slots in a given time period as half rate DTC. In IS-54B, each TDM RF channel can carry up to three full-rate DTCs or six half-rate DTCs.

The frame structure of the TDC RF channel of IS-54B is shown in Figure 3. The TDM channel occupies a 30KHz channel of the existing analog system. In each "frame" of a TDM RF channel, there are 6 equally sized time slots (1-6) with a frame length of 40ms (25 frames per second). Each full rate DTC utilizes two equally spaced time slots of the frame as shown in FIG. 3, namely slots 1 and 4, or slots 2 and 5, or slots 3 and 6. When working at full rate, the TDM RF channel is allocated to three users (A-C), that is, user A allocates time slots 1 and 4 of the frame shown in Figure 3; user B allocates time slots 2 and 5 of the frame shown in Figure 3 ; and User C is assigned slots 3 and 6 of the frame shown in Figure 3 (so, for full rate, each TDM frame actually consists of three slots instead of six, and is 20ms long instead of 40ms long). Each half-rate DTC utilizes one time slot of the frame shown in FIG. In half rate, a TDM RF channel can be assigned to six users (A-F), each user A-F assigned one of the six time slots of the frame shown in Figure 3 (for half rate, each TDM frame actually consists of six time slot, conforming to the definition of "frame" in IS-54B).

Thus, unlike an analog FDMA cellular system, in which base stations and mobile stations continuously transmit and receive over one RF channel, a TDMA cellular system operates in a buffered and burst discontinuous transmission mode. Each mobile station transmits (and receives) on assigned time slots of the RF channel. For example, at full rate, user A's mobile station will transmit on slot 1, hold on slot 2, receive on slot 3, transmit on slot 4, hold on slot 5, and receive on slot 6, then repeat This cycle (transmit and receive time slots are staggered from each other to avoid the use of duplexer circuits, which would otherwise be required to allow the mobile station's transmitter and receiver to operate simultaneously). Thus, a mobile station transmits (or receives) part of the time (1/3 time for full rate, 1/6 time for half rate), and can be turned off the rest of the time to save power. CDMA system

CDMA is a multiple access scheme based on the spread spectrum communication technology that has long been used in military communications to combat radio frequency interference and prevent interception by the opponent. Unlike FDMA and TDMA systems, where each transmission (signal) at any given time is confined to its own separate frequency and its own distinct channel isolated from adjacent channels, CDMA systems simultaneously Send multiple signals. The two main spread spectrum techniques are frequency hopping spread spectrum and direct sequence or noise modulated spread spectrum.

In frequency hopping spread spectrum, a fairly wide frequency band (eg several megahertz) is divided into a large number of much narrower channels. The transmitter "hops" from channel to channel, that is, sends a very short burst from channel to channel. The hopping sequence is a pseudo-random sequence generated according to a key (secret key) that is available to both the transmitter and receiver. Appears to occupy the entire bandwidth, and thus "spread" the spectrum, as seen over a longer period of time throughout the transmission, rather than in individual bursts, although at any instant, for any one burst, it only occupies the channel a very small percentage. Many users can follow a frequency hopping orthogonal pseudo-random sequence and share the same channel for each user's transmission.

The PN-3118 standard utilizes direct sequence or direct coded spread spectrum, which is a digital form of noise modulation. In noise modulation, the original signal is added to (mixed with) a stronger noise-like signal with known properties. The synthesized signal is tuned to a carrier and transmitted to the receiver. In the receiver, a noise-like replica of the input to the transmitter is extracted from the received signal to restore the original signal. In direct sequence, a high-rate pseudorandom binary sequence is used for a noise-like signal. This pseudo-noise (PN) sequence is added to a digital information signal (eg, digital speech) and the resulting bit stream is transmitted. In the receiver, this PN sequence is extracted to generate the information signal. Since the transmitted signal has a high bit rate (eg, 100 Mbps), "spread spectrum" (ie, wide band) is required (eg, 100 MHz), as with frequency hopping spread spectrum. However, unlike frequency hopping spread spectrum, direct sequence spread spectrum transmits over the entire channel bandwidth at all times. Here too, many users can share the same channel with each user being assigned a code for generating an orthogonal random sequence, which sequence is mixed with the information signal. The signal is separated in each receiver by using a correlator or matched filter which accepts only the signal energy from the designated binary sequence for spreading.

FIG. 4 shows the overall structure of the forward CDMA channel (base station to mobile station) specified in PN-3118. The forward CDMA channel occupies 1.23MHz of spectrum centered on a 30KHz channel of the existing analog system. According to PN-3118, forward CDMA channels include up to 64 code channels (W0-W63) assigned to different users, for example, one pilot channel (W0), one synchronization channel (W32), seven paging channels (W1 -W7), and fifty-five traffic channels (W8-W31 and W33-W63). Each of these code channels is spread by an orthogonal PN sequence at a fixed slot rate of 1.23 Mcps (a "PN chip" is one bit of the PN sequence). Multiple forward CDMA channels can be transmitted by the base station in a frequency division multiplexed manner.

The pilot channel conveys an unmodulated direct-sequence spread spectrum signal which is transmitted consecutively on each active forward CDMA channel of the base station. Mobile stations operating within the base station's coverage area use this signal for synchronization (sounding, timing, and phase reference for correlation demodulation) and for signal strength comparisons between base stations to determine when to handoff . Each base station uses the time offset of the pilot PN sequence to identify each forward CDMA channel. Therefore, different base stations are identified by different pilot PN sequence offsets.

The synchronization channel is used by mobile stations to obtain system configuration and timing information (eg, system identification, system time, pilot PN sequence offset, paging channel data rate, etc.). Each traffic channel (user) is identified by a distinct long code sequence (1.23Mcps) which is added to the information bits before the PN sequence is spread. Each paging channel is divided into multiple 80ms time slots. The mobile station can operate in either "slotted" or "unslotted" mode in order to receive paging and control messages on the paging channel. In the slotted mode, the mobile station monitors the paging channel only during certain designated time slots. In the unslotted mode, the mobile station monitors all slots of the paging channel. hybrid system

Some systems utilize mixed access methods. For example, in the IS-54B digital cellular standard, a combination of FDMA and TDMA is utilized. More specifically, IS-54B utilizes a 30KHz FDMA channel subdivided into 3 or 6 time slots (3 or 6 voice calls per 30KHz bandwidth) for TDMA transmissions. Similarly, a CDMA system can also be a hybrid of FDMA and CDMA technologies, in which the total system bandwidth is divided into a set of wideband channels, each channel containing a large number of CDMA signals. Personal Communications Service (PCS)

Cellular technology has its origins in car telephone service facilities. Recently, however, there has been a move towards the use of lightweight portable phones in homes, offices and public meeting places, and virtually any other place where users can obtain services. The next step in this evolution was the concept of "Personal Communication Services" (PCS), or what is sometimes called "walking speed" services. The concept is that not only telephone calls, but also faxes, computer data, paging messages and even video signals can be sent and received by users on the move, for example, in buildings, factories, warehouses, shopping centers, conference centers, airports or Move in open areas.

The PCS system operates at low power and utilizes a smaller cellular structure than conventional wide-area (vehicular) cellular systems, providing the high-quality, high-capacity wireless coverage required by commercial and other applications. By reducing the transmit power of the base station, the size of the cell (or the radius of the cell) (for this reason, the frequency reuse distance is also reduced), more channels per geographical area. Additional benefits of smaller cells include longer talk time (battery life time) for the user since the mobile station will use significantly lower transmit power than in larger cells.

The industry has grown accustomed to using the terms "macrocell," "microcell," and "picocell" to distinguish the relative sizes of cells required for a particular application (indoor or outdoor). The term "macrocell" generally refers to a cell comparable in size to a conventional cellular telephone system (eg, 1 kilometer or greater radius). Macrocells serve fast-moving users and cover low to moderate utilization areas. Instead, the terms "microcell" and "picocell" refer to progressively smaller cells, such as are used in PCS systems, for example. Microcells serve slow-moving users and can cover public indoor or outdoor areas, such as convention centers or busy streets. Picocells can cover office corridors or the floors of high-rise buildings. Microcells and picocells can also cover high-density pedestrian areas or busy avenues (streets or highways) in conventional cellular systems.

It is now clear that future cellular systems are likely to implement a hierarchical cell structure of macrocells, microcells and picocells. From a system (MSC) point of view, base stations in microcells and picocells can be seen as extensions of adjacent or overlapping macrocell base stations. In this case, the microcell and picocell base stations may be connected to the macrocell base station via digital transmission lines, for example. On the other hand, microcells and picocells can be treated like macrocells and connected directly to the MSC.

From a radio coverage point of view, macrocells, microcells and picocells can be differentiated from each other or, alternatively, superimposed one on top of the other in order to handle different traffic patterns or radio environments. For example, handoffs between microcells can sometimes be difficult to perform near street corners, especially if the user is moving so fast that the signal strength varies by more than 20 dB per second. In this state, it is possible to use a kind of "umbrella" macrocell for fast-moving users and a microcell for slow-moving users. By managing different types of users differently, handover between microcells can avoid the severe street corner effect suffered by fast-moving users.

It can be easily understood that seeking to improve the capacity of next-generation cellular systems can be achieved by more advanced macro-cellular technologies, such as digital TDMA or CDMA, or by introducing microcells and picocells into specific region, or use a combination of the two methods. Thus, for example, analog microcells may enable coverage of "dead spots" (areas where radio signals are prevented from penetrating due to terrain, region, or other constraints) or hot spots (areas with heavy traffic). In this example, coverage or capacity can be improved for the existing subscriber base of analog mobile stations. However, the effectiveness of the microcell concept in increasing capacity is maximized through the use of digital technology requiring mobile stations with new digital capabilities. control channel

The continuing need to serve existing analog-only mobile stations has led to the specification in IS-54B and PN-3118 of the Analog Control Channel (ACC), which is derived from the original AMPS or equivalent EIA/TIA-553 standard inherited. According to EIA/TIA-553, the analog forward control channel (FOCC) on the downlink from the base station to the mobile station carries a continuous stream of message (word) data in the format shown in FIG. Several different types (functional classes) of messages can be sent on a simulated FOCC. These messages include System Parameter Overhead Messages (SPOM), Global Operation Overhead Messages (GAOM), Registration Identification Messages (REGID), mobile station control messages such as paging messages, and control fill messages. SPOM, GOAM and REGID are overhead messages that will be used by all mobile stations in the base station's coverage area. Overhead messages are sent in groups called overhead message sequences (OMTs). The first message of each OMT is always SPOM, which is sent every 0.8±0.3 seconds.

The FOCC-like format shown in Figure 4 requires an idle mobile station to listen to the FOCC to read all messages sent in each OMT (not the one being paged), although the information contained in these messages It may be constant from one OMT to the next. This requirement unnecessarily limits the life of the mobile station battery. However, one goal of next-generation digital cellular systems is to extend the user's "talk time," ie, the life of the mobile station battery. To this end, co-pending U.S. Patent Application Serial No. 07/956,640 (hereby incorporated by reference) discloses a digital FOCC that can transmit the type of messages specified for an analog FOCC, but in a In the format, an idle mobile station is allowed to read overhead messages when locked into the FOCC, and then only when the information changes, and to enter "sleep mode" at all other times. While in sleep mode, the mobile station turns off most internal circuits to conserve battery power.

Co-pending US Patent Application Serial No. 07/956,640 cited above shows how a Digital Control Channel (DCC) can be defined alongside the Digital Traffic Channel (DTC) specified in IS-54B. Referring to FIG. 3, half-rate DCC will occupy 1 of the 6 slots in each 410 ms frame, and full-rate DCC will occupy two of them. For additional DCC capacity, additional half-rate or full-rate DCCs can be defined at each DTC position until no more time slots are available on the carrier (DCCs can be defined on additional carriers if desired). Therefore, only DTC, only DCC, or a mixture of DTC and DCC can be transmitted on each IS-54B RF channel. In IS-54B frame structure, each RF channel can have up to 3 full rate DTC/DCC, or 6 half rate DTC/DCC or any combination between them, for example, one full rate and four half rate DTC/DCC.

However, in general, the DCC transmission rate does not need to be consistent with the half rate and full rate specified in IS-54B, and the length of the DCC time slot may not be uniform and may not be consistent with the length of the DTC time slot. Figure 6 shows the more general case of frontal DCC organized as a series of time slots. These DCC slots may be defined per IS-54B RF channel and may include, for example, all nth slots in a TDM code stream. In this case, the length of each DCC slot may or may not be equal to the IS-54B DTC slot length of 6.66 ms (6 DTC slots in each 40 ms frame). In another approach (and without limitation to other alternatives), these DCC slots may be limited to the paging channel specified by PN-3118, but may or may not be 80 ms long, which is based on the PIN- 3118 The length of each paging channel slot.

DCC slots as shown in Figure 6 may be organized into a higher level structure called a "superframe". Each superframe consists of logical channels that carry different kinds of information. In a superframe, one or more DCC slots may be allocated to each logical channel. The exemplary superframe shown in FIG. 6 includes at least three logical channels, namely Broadcast Control Channel (BCCH), Paging Channel (PCH) and Access Response Channel (ARCH). In this example, BCCH is assigned 6 DCC time slots to transmit overhead messages. PCH is assigned a DCC time slot to transmit paging messages. The ARCH is also assigned a DCC time slot to carry channel assignments and other messages. The exemplary superframe of Figure 6 may contain other logical channels, including additional paging channels. If more than one PCH is specified, different groups of mobile stations identified by different sequences (eg, the last digit of the MIN) may be assigned different PCHs.

For the purpose of efficient sleep mode operation and fast cell selection, the BCCH can be divided into multiple subframes. Co-pending U.S. Patent Application No. 07/956,640 discloses a BCCH structure that allows a mobile station to Only the minimum amount of information is read out. After power up, an idle mobile station only has to regularly monitor its assigned PCH (Paging Time Slot) in a superframe and can return to sleep mode during other time slots.

In one aspect, the present invention provides a method of transmitting information to a remote station, the method comprising the steps of grouping the information into a plurality of time slots; grouping the time slots into a plurality of superframes; grouping the superframes into the steps of a plurality of paging frames; allocating one of the plurality of time slots in each paging frame to the remote station, the allocated time slot being used for paging the remote station; and The step of sending an indication of the change in the paging frame to the remote station in the allocated time slot.

In another aspect, the present invention provides a method of registering a remote station with a communication system, the method comprising the steps of sending a registration number from the system to the remote station; the steps of comparing the list of registration numbers in the list; the steps of sending a registration message from the remote station to the system if the registration number is found in the table; the steps of sending a list of registration numbers from the system to the remote station; and using the slave system The received list of registration numbers replaces the list of registration numbers stored at the remote station.

In another aspect, the present invention provides a method for validating the registration of remote stations, each remote station assigned an identification number using a communication system, comprising the steps of receiving a plurality of registration messages sent by the remote stations; and sending an acknowledgment message including the identification numbers of the at least two remote stations to the at least two remote stations.

In another aspect, the present invention provides a method for transmitting information to a remote station, the method comprising the steps of grouping the information into a plurality of repeated time slots; grouping the plurality of time slots into a plurality of superframes steps; a step of allocating time slots in a superframe to a plurality of logical channels; and a step of varying a repetition rate of transmitted messages in at least one logical channel.

In another aspect, the present invention provides a method of identifying serviceable remote stations in one of a plurality of communication systems, the method comprising the steps of assigning each system an operator code; at the remote station the steps of storing a list of services associated with each operator code; the step of sending a request operator code from a remote station; and the step of sending an operator code from a system to the remote station.

In another aspect, the present invention provides a method of transmitting information to a remote station, the method comprising the steps of grouping the information into a plurality of time slots; grouping the time slots into a plurality of superframes; and at each Superframe phase information is sent in each slot of a superframe so that the remote station can identify the start of each superframe.

In another aspect, the present invention provides a method of managing the transmission of messages from a communication system to a remote station, the method comprising the steps of dividing each message into Layer 2 (L2) frames; The step of sending each frame to the remote station; the step of sending the identification indication of the remote station from the system to the remote station through the second channel; if the identification indication is consistent with the identification indication stored in the remote station, then from The remote station sends an indication to the system over the third channel whether each frame has been received correctly.

In a further aspect, the present invention provides a method of registering a remote station with a system, the method comprising sending from the system to the remote station a message containing a list of communication channels in adjacent cells, whether they are in each corresponding cell an indication that a cell has required registration and a signal strength hysteresis indication message for each cell; and if registration is required in the corresponding cell, selecting a channel using the signal strength hysteresis.

Those skilled in the art will have a better understanding of the present invention, and its multiple objects and advantages will become apparent by referring to the following drawings.

Figure 1 shows the structure of a conventional cellular radio system;

Figure 2 shows three sector cells that may be used in the system shown in Figure 1;

Fig. 3 shows the structure of the forward time division multiple access (TDMA) channel according to IS-54B of a kind of known cellular industry standard;

Fig. 4 shows the structure of the forward code division multiple access (CDMA) channel according to another kind of known cellular industry standard PN-3118;

Figure 5 shows the format of the forward analog control channel (ACC) specified by IS-54B and PN3118;

Figure 6 is a generalized representation of a digital control channel (DCC) having a plurality of time slots grouped into a superframe;

Fig. 7 shows the logical channel of DCC;

Fig. 8 represents an exemplary TDMA frame structure;

Figure 9 shows an exemplary slot format in DCC;

Figure 10 shows the BRI field in Figure 9c;

Figure 11 shows the data division before channel coding;

Figure 12 shows that the CPE is mapped into a slot format;

Figure 13 shows the R/N field in Figure 9c;

Figure 14 shows the CFSP field in Figure 9c;

Figure 15 shows a hyperframe structure;

Figure 16 shows the paging frame structure;

Figure 17 shows the SMS frame structure;

Figure 18 shows an example of SMS subchannel multiplexing;

Figure 19 shows a table of DCCs broadcast on BCCH;

Figure 20 shows the relationship between uplink slots and downlink SCF flags;

Figure 21 shows an L3 confirmation dialogue between MS and BS;

22A-L represent RACH layer 2 frames;

Figures 23A-C represent F-BCCH layer 2 frames;

Figures 24A-C represent E-BCCH layer 2 frames;

Figures 25A-C represent F-BCCH layer 2 frames;

Figures 26A-N represent SPACH layer 2 frames;

27A-B show the process of random connection between MS and BS;

Figure 28A-B shows that MS and BS work in SPACH AR2 mode;

Figure 29 shows a mobile station state diagram;

Figures 30-37 represent aspects of the authentication process according to the present invention; and

Figure 38 illustrates an exemplary cellular mobile radiotelephone system.

Although the following description focuses on IS-54B compliant systems, the principles of the present invention are equally applicable to various wireless communication systems, such as cellular and satellite radio systems, regardless of their particular mode of operation (analog, digital, dual mode etc.), access technology (FDMA, TDMA, CDMA, hybrid FDMA/TDMA/CDMA, etc.), or architecture (macrocell, microcell, picocell, etc.). As is known from the previous discussion of FDMA, TDMA and CDMA systems, logical channels carrying voice and/or data can be implemented in different ways at the physical level. The actual channel can be, for example, a relatively narrow RF frequency band (FDMA), time slots on a radio frequency (TDMA), a unique code sequence (CDMA), or a combination of these. Therefore, for the purposes of the present invention, the term "channel" means any actual channel that can carry voice and/or data, and is not limited to any specific mode of operation, access technology or system architecture.

The following statements together with those in Appendix A provide a detailed framework for working in AVC, ACC, DTC and DCC. The following description is mainly for the DCC air interface and is divided into different sections for layer 1, layer 2 and layer 3 operations. Appendix A proposes air interface requirements for ACC, DTC and AVC through amendments to the IS-54B standard. In the following, the term "IS-54B" will mean either the existing IS-54B standard, or the IS-54B standard as modified by Appendix A, depending on its context.

Glossary of terms

ACC: Analog Control Channel

AG: Reduced protection time

ARCH: Access Response Channel

ARQ: automatic retransmission request

AVC: Analog Voice Channel

BC: start to continue

BCN: Broadcast Channel Change Notification Flag

BER: bit error rate

BMI: base station, interworking function of MSC

BMR: Base Station Measurement Requirements

BP: bit position

BRI: Busy, Reserved, Idle (Busy Reserved Idle)

BS: base station

BSCO: base station query (challenge) order

BSMC: Base Station Manufacturing Code

BT: Burst type

BU: Burst Utilization

CDL: Coded DCC positioning

CDVCC: Coded DVCC

CLI: Persistence Length Indicator

CPE: Coded Partial Echo

CR: Continuous repetition

CRC: Cyclic Redundancy Check

CSFP: Coded Superframe Phase

DCC: Digital Control Channel

DL: DCC positioning

DTC: Digital Traffic Channel

DVCC: Digital Verification Color Code

E-BCCH: Extended Broadcast Control Channel

ECS: Extended Advertisement Channel Period Begins

F-BCCH: Fast Broadcast Control Channel

FRNO: frame number

G: guard time

HP: Hyperframe

IDT: mobile station identification type

IMST: International Mobile Station Identification

L3DATA: layer 3 data

L3LI: Layer 3 Message Length Indicator

MAC: Media Access Control

MACA: Mobile Assignment Channel Allocation

MAHO: Mobile Assigned Handoff

MLRQ: Radio Link Quality Monitoring

MS: Mobile Station

MSC: Mobile Telephony Service Center

MSID: Mobile Station Identification

PCH: paging channel

PCON: paging continue

PE: partial echo

PF: paging frame

PFM: Paging frame modifier (modifier)

PREAM: preamble

R: Ramp time

R/N: received/not received

RACH: random access control channel

RDCC: reverse digital control channel

RSS: Received Signal Strength

RSVD: reserved

S-BCCH: Short Message Service Broadcast Control Channel

SAP: Business Access Point

SCF: Shared Control Feedback

SF: super frame

SMS: short message service

SMSCH short message service point-to-point channel

SMSN: Broadcast Short Message Service Change Notification

SOC: System Operation Code

SPACH: SMS, PCH, and ARCH

SSD: Share separate data

SYNC: synchronous

SYNC+: additional synchronization to shortened RACH bursts

TDMA: Time Division Multiple Access

TID: transaction identifier

WER: Word Error Rate DCC Logical Channel Definition

DCC includes logical channels shown in FIG. 7 . DCC logical channels include BCCH (F-BCCH, E-BCCH, S-BCCH), SPACH, PCH, ARCH, SMSCH and RACH.

Broadcast Control Channel (BCCH)

BCCH is an acronym used to collectively refer to F-BCCH, E-BCCH, and S-BCCH logical channels. Generally speaking, these three logical channels are used to convey general, system-related information. The characteristics of these three channels are: unidirectional (downlink), shared, point-to-multipoint, and unacknowledged.

Fast Broadcast Control Channel (F-BCCH) is a logical channel used to broadcast time-critical system information.

  Extended BCCH (E-BCCH)

This logical channel is used to broadcast system information with less stringent time requirements than information sent on the F-BCCH.

  SMS broadcast BCCH (S-BCCH)

This logical channel is used to broadcast short messages used in the SMS broadcast service.

SMS point-to-point, paging and access response channel (SPACH)

This logical channel is used to send information about SMS point-to-point (SMSCH) paging to specific mobile stations and, as described below, provides an Access Response Channel (ARCH). SPACH can be considered as a logical channel further divided into 3 types: SMSCH, ARCH and PCH, as also described below. The characteristics of SPACH are: unidirectional (downlink), shared and unacknowledged. SMSCH is point-to-multipoint. ARCH and SMSCH are point-to-point.

  Paging Channel (PCH)

Such logical channels of the SPACH subset are dedicated to the transfer of paging and orders.

  Access Response Channel (ARCH)

This logical channel is a subset of SPACH, and the mobile station automatically moves to SPACH when access is successfully completed on RACH. ARCH can be used to convey AVC or DTC assignments or other responses to mobile access attempts. Layer 2 ARQ is possible using acknowledgment messages on RACH.

SMS point-to-point channel (SMSCH)

This logical channel is used to deliver short messages to specific mobile stations receiving SMS services. Random Access Channel (RACH)

This logical channel is a random access channel used to request access to the system. The characteristics of this channel are: unidirectional (uplink), shared, point-to-point and confirmed. Contention decision and/or collision avoidance feedback is provided on the corresponding forward sub-channel. layered approach

In order to better understand the structure and operation of the present invention, DCC can be divided into three layers: the first layer (physical layer), the second layer and the third layer. The physical layer (L1) defines the parameters of the actual communication channel, such as RF spacing, modulation characteristics, etc. The second layer (L2) defines the techniques required for accurate information transmission within the constraints of the actual channel, such as error correction and error detection. The third layer (L3) defines the procedures for receiving and processing information sent over the actual channel. Physical Layer RF Carrier Spacing and Identification

The RF carrier spacing and identification used in IS-54B can also be used in the present invention. modulation characteristics

The modulation characteristics of the radio frequency carrier may be similar to those of IS-54B. TDMA frame structure

An exemplary frame structure is shown in FIG. 8 (FIG. 8 is similar to FIG. 3). Each DCC TDMA RF channel has a frame length of 40 milliseconds (ms). Each frame consists of six time slots (1-6) of equal length, exactly 162 symbols (324 bits) in length. The bit positions (BP) of the forward and reverse slots/bursts are numbered sequentially from 1 to 324. TDMA slot structure

Possible slot structures for DCC uplink and downlink are shown in Figure 9. Figure 9A shows the normal slot format for the MS-BS on the DCC. Figure 9B shows the shortened slot format for the MS-BS on the DCC. Figure 9C shows the slot format of the BS-MS on the DCC.

In the forward direction, the BP=1 of the first transmitted bit of the SYNC word and BP=324 of the last transmitted bit of the RSVD field. In the reverse direction, the first transmitted bit BP=1 of Guard protection. The last transmitted bit BP of the DATA field is equal to 324 in the normal slot format. The last transmitted bit BP of the AG field is equal to 324 in the shortened slot format.

AG

Field AG indicates shortened guard time for access burst format. This field is 22 symbols (44 bits) long.

BRI

Field BRI is used to indicate whether the channel is busy, reserved or idle. This field is 6 bits long and is divided into two 3-bit fields. The bits of the BRI are transmitted as shown in FIG. 10 .

DATA

The user data bits are mapped to the field DATA for transmission. In the forward direction, this field is 260 bits long. In the reverse direction, the length of the DATA field: 244 bits for the full-length slot format and 200 bits for the shortened slot format.

Encoding

Fig. 11 shows division of data before channel coding. All logical channels BCCH, SPACH and RACH (normal and shortened) use 1/2 rate convolutional coding. The same coding polynomials as in IS-54B for full rate voice can be used. The first bit received from layer 3 is the leftmost bit in Figure 11 and should be the first bit passed to the channel coding. The last five bits sent to the channel encoder are set to 0 (tail bits). The CRC polynomial may be the same as in IS-54B. Generally, DVCC is added as information bits when calculating CRC as in IS-54B. However, for F-BCCH, the DVCC value is set to 0 before calculating the CRC.

The length of the information field in Figure 11 depends on the length of the burst (see Figures 9A-C):

SPACH and BCCH: =130-16-5=109

RACH (normal length): =122-16-5=101

RACH (reduced length): =100-16-5=79

staggered

For all channel types and burst lengths, all bits are sent within one burst, ie only intra-burst interleaving is performed. The output bits from the interleaver are sequential, ie the first bit is the first bit sent in the first DATA field. After the completion of the first DATA field, the output of the interleaver is sent in the first position of the second DATA field.

Downlink (SPACH)

260 coded data bits are interleaved in a matrix of 13 rows by 20 columns. The data bits are placed into a rectangular interleaved array as shown in the matrix below, and the individual bits have been numbered 0-259, corresponding to the order of their encoder output. These data bits are input to the column direction of the array. These bits are then sent in the row direction using the following algorithm: cycle row = 0 to 12

loop column = 0 to 19

send(array(row, col))

loop end loop end

0 13 26...234 247

1 14 27...235 248

                                     

... ... ... ... ... ...

                                               

12 25 38...246 259

Therefore, the bits are sent in the following order:

0,13,...,247 (line 1)

1,14,...,248 (line 2)

12,25,...,259 (line 13).

uplink

normal length burst

244 coded data bits are interleaved in a matrix of 12 rows by 20 columns with an additional partial column of 4 bits. The data bits are placed into a rectangular interleaved array shown in the matrix below, where the bits are numbered 0-243, corresponding to their order at the output of the encoder. Data bits are input to the array in the column direction. These bits are then transferred in the row direction using the following algorithm: cycle row = 0 to 3

loop column = 0 to 20

send(array(row, col))

loop end loop end loop line = 4 to 11

loop column = 0 to 19

send(array(row, col))

loop end loop end

                                       

                                         

2 14 26...230 242

                                         

                                                         

Therefore, the bits are sent in the following order:

1,12,...,240 (line 1)

1,13,...,241 (line 2)

11,23,...,239 (line 12)

shortened length burst

The 200 coded data bits are interleaved in a 12 row by 16 column matrix with an additional partial column of 8 bits. The data bits are placed into a rectangular interleaved array shown in the matrix below, where the bits are numbered 0-199, corresponding to their order at the encoder output. Data bits are input to the array in the column direction. These bits are then transferred in the row direction using the following algorithm: cycle row = 0 to 7

loop column = 0 to 16

send(array(row, col))

loop end loop end loop line = 8 to 11

loop column = 0 to 15

send(array(row, col))

loop end loop end

                                       

                                         

                                           

                                                         

                                                           

Therefore, the bits are transmitted in the following order:

0,12,...,192 (line 1)

1,13,…,193 (line 2)

11,23,...,191 (line 12)

G

Field G in Figures 9A-B provides a guard time, which is 3 symbols (6 bits) in duration. During this time, ms remains in the carrier off state.

CPE

The partial echo (PE) in FIG. 9C is used to identify which mobile station was acquired after the random access start burst, or to identify which mobile station a time slot was marked reserved for. The channel coding of PE to CPE is similar to how CDVCC is handled in IS-54B (ie a (12,8) code). The d7 bit in IS-54B is dropped (set to 0) during encoding and is not transmitted as part of the CDL. The LSB of PE is do. After encoding, the conversion to the slot format is shown in FIG. 12 according to the IS-54B CDVCC procedure. The parity bits b ₃ , b ₂ , b ₁ and b ₀ are all reversed, that is, an exclusive operation is performed with (1,1,1,1) before forming the obtained CDL information.

PREAM

The PREAM (preamble) field in Figures 9A-B allows the BS to perform automatic gain control (AGC) and obtain symbol synchronization before the subsequent data and burst synchronization portions of the received burst arrive. This field consists of the bit pattern 1001 repeated four times.

R

The R field in Figure 9A-B indicates the Power ramp-up interval, and the duration is 3 symbols (6 bits).

R/N

The R/N field in FIG. 9 is used to convey the received/not received status of each burst sent to the base station on the RACH. The transmission of R/N bits is as shown in FIG. 13 .

RSVD

These two bits are set to 11 (FIG. 9C).

CSFP (coded superframe phase)

The CSFP field in FIG. 9C is used to convey information about the superframe phase (SFP) so that the mobile station can find the start of the superframe. The content in this field can also be used to distinguish DCC and DTC, wherein CSFP of DCC and CDVCC of DTC have no common code word. This is achieved by using the same basic encoding method and changing the parity bits of all CSFP codewords before transmission. The CFSP field is 12 bits long.

The SFP channel is coded as CSFP, similar to how DVCC is handled in IS-54B (ie a (12,8) code). The least significant bit (LSB) of the SFP, the bit incremented per TDMA block, is do (a TDMA block is 20ms long). Bits d7, d6 and d5 are reserved and all set to 0 (000). After encoding, according to the process of IS-54B DVCC, check bits b ₃ , b ₂ , b ₁ , and b ₀ are all reversed, that is, use (1,1,1,1) exclusive operation, and form the obtained CSFP The information was previously denoted b ₃ , b ₂ , b ₁ , b ₀ . These bits are transmitted as shown in Figure 14 (exactly as CDVCC).

SYNC

The SYNC word in Figures 3A-C is similar in content and function to the SYNC word in IS-54B.

SYNC+

SYNC+ in Figures 9A-B provides additional synchronization information to improve BS receiver performance. The SYNC+ word is determined by the following phase changes in radians: π/4, -π/4, 3π/4, -3π/4, -π/4, -π/4, -3π/4, 3π/4, 3π/4, π/4, π/4K and π/4. superframe:

Definition of superframe

A superframe is defined as the interval between non-contiguous F-BCCH slots. The length of a superframe (SF) is fixed. Its length is 32 TDMA blocks (half rate is 16 blocks), that is, 32×20=640ms. Therefore the superframe phase counter is assigned 5 bits. The first F-BCCH SFP value in a superframe is assigned a value of 0, the next slot of the DCC of the same logic is assigned a value of 1, and so on. For half-rate DCC, the values 0, 2, 4, ... are used in consecutive bursts assigned to that DCC.

Master and slave DCC

A DCC may be a master or a slave DCC. Each frequency delivering DCCs must have one master DCC assigned to slot 1, and possibly additional slave DCCs. Only the primary DCC transmits the BCCH. MSs assigned to a secondary DCC use the BCCH on the corresponding primary DCC.

DCC at different frequencies

If several DCCs assign different frequencies so that there are several primary DCCs, different slot numbers may be assigned to the combined BCCHs (F-BCCH, E-BCCH and S-BCCH) on each primary DCC. Layer 2/3 information may also be different for each primary DCC. Therefore a mobile station must always obtain all its BCCH information on the same frequency as its PCH channel (see PCH allocation algorithm below). The first step in the PCH assignment algorithm is to select a frequency. If the MS is assigned to a different frequency than the one it is currently locked to, it must re-read the DCC structure message in the new frequency before it continues with the PCH slot assignment calculation.

hyperframe definition

The hyperframe structure is shown in Figure 15. A hyperframe (HP) consists of two superframes. Each SPACH in the first superframe is always repeated in the second superframe. This means "repetition of specification recognition". The slots in the first SF of the HF are called "primary" and the slots in the second SF are called "secondary". The F-BCCH conveys the same information in every superframe until the change flag triggers (changes value) in the PCH. At this time, new data can be placed on the F-BCCH. E-BCCH and S-BCCH information may be different from SF to SF.

SPACH Persistence Rules

If the PCON bit in the assigned PCH is set, the mobile station will read as many additional SPACH slots as indicated by the parameter PCH-DISPLACEMENT, which is sent on the BCCH. The additional time slots that are read are separated by 40 ms from the assigned PCH for full-rate and half-rate DCC. For full rate DCC operation, this means that the mobile station reads every other SPACH slot, up to the limit indicated by the information element PCH-DISPLACEMENT. BCCH slots and reserved slots are not counted as part of the paging of the read continuous procedure.

ARCH or SMSCH message transmission to one mobile station can be interrupted to allow message transmission to another mobile station. Each interruption of ARCH and SMSCH messages by another SPACH message may be limited to no more than n slots, or L3 timeout of SMSCH or ARCH. The number of outages per mobile station may also be limited.

paging frame definition

A Paging Frame (PF) is defined as an integer hyperframe (see Figure 16). There are four PF classes: PF ₁ ... PF ₄ . PF ₁ is considered the "lowest" PF rating, while PF ₄ is the "highest". Three terms are used to define the operation of a PF level: default PF level, assigned PF level, and current PF level.

A mobile station is assigned a PF class at the time of subscription. This is called the default PF rating. If the default PF level is higher than the highest supported level specified by the parameter MAX-SUPORTED-PFC broadcast on BCCH, the mobile station uses the PF level specified by MAC-SUPORTED-PFC.

The MS may also be assigned to another PF class at the time of registration. When the MS registers, it temporarily changes the PF level to PF ₁ until it receives a registration response. If the response contains a PF level, the MS will use that PF level; otherwise, it will use the previous PF level, and the PF level obtained from the registration response or broadcast information is called the specified PF level.

The PF grade actually used is called the current PF grade. If the Paging Frame Modifier transmitted on SPACH is not set, the current PF class is equal to the specified PF class, or it is equal to the specified PF class+1 if PFM is set. The highest PF class is PF ₄ which is used in all cases.

A hyperframe count and a basic SF indicator are provided in the BCCH. These two counts together (2 x HF count + basic SF indicator) constitute the superframe count. The least common multiple at the paging frame level is 12. So HF counts: 0,1,…,11,0,1,….

In Figure 16, the auxiliary PCH is always placed in the next superframe. For PF(i), i=2,3,4, only PCH assignments aligned with HF ₀ are shown for illustration.

Check the status of E-BCCH information

Before reading the E-BCCH, the mobile station shall store the value of the E-BCCH change notification flag transmitted in the F-BCCH. After the mobile station has obtained the relevant information (this may depend on the specific task the mobile station is engaged in), the mobile station then reads the E-BCCH change notification flag. The update/initiation process of the E-BCCH message set is considered successful only if this flag is the same before and after E-BCCH readout.

SMS broadcast

SMS broadcast (S-BCCH) is a broadcast channel in a superframe.

SMS frame

The S-BCCH channel is compiled into fixed-length SMS frames, and each SMS frame includes 24 superframes, as shown in Figure 7 . The SF number is derived from the hyperframe count and the basic superframe indicator sent on the BCCH (SF number = 2 x HF count + basic SF indicator). The first S-BCCH slot (superframe 0) within each SMS frame contains a header which describes the structure of the SMS channel. The number of superframes within each SMS frame is fixed. Therefore, the number of slots assigned to the SMS frame is 0, 24, 48, 72, ..., depending on how many slots per superframe are assigned to the S-BCCH. SMS frames are aligned with the start of the counter equal to zero. Additionally, regardless of which paging frame group is supported, the system must increment the hyperframe count (0 to 11 modulo 12) to provide SMS frame synchronization information to the mobile station.

SMS sub-channel

The SMS subchannel specification allows for different repetition periods for different messages. Each subchannel has its own repetition period defined in units of possible SMS frames. The number of sub-channels is: 0,1,...,N. To limit the subchannel repetition time, the maximum N can be set equal to 4. The sub-channels are SMS(i) multiplexed on the S-BCCH channel in units of SMS frames, where i=1,...,N. Figure 18 shows an example of SMS subchannel multiplexing, where N=4.

According to the L2 information found in each first time slot of each SMS frame, groups of messages in SMS(i) can be separated by M(i) SMS frames before the end of a period. The SMS frame number "i" is always followed by the frame number ((i+1) modulo N+1) for transmission, although message groups vary periodically in the subchannel.

Each SMS Subchannel (SMSN) provides a Transaction Token (TF). The tags of all SMS sub-channels are then multiplexed onto a single tag transmitted on the SPACH channel, which points to the next logical SMS frame (see Figure 18). If there is a transaction for a subchannel in this tag, the MS must read the S-BCCH header field at the beginning of the next logical SMS frame for further information, as discussed in more detail below.

  Header information

The header information describes the subchannel on which the SMS is broadcast and is provided in the first time slot of each SMS frame. The MS can also find the L3 structure of the SMS frame associated with this header. The SMS header element (beginning of each SMS frame) is shown in the table below. information unit range(logic) bits Subchannel number Subchannel number Subchannel cycle phase length Subchannel cycle phase number. Number of SMS messages (N). SMS message ID (Note 1) L2 frame start (Note 1) 1-41-41-641-641-64 (set to 1+ field value) 0-255 (unique ID in cycle) 0-255 (L2 frame identifier) 2266688

NOTE: The N instances of these two units are transmitted consecutively.

Even though SMS data may be separated by several SMS frames, the change flag may interrupt the subchannel period (period clearing). At this point the MS assumes that the next subchannel is the beginning of a new period. There are two ways to change the data provided on the broadcast SMS: changing the L3 messages within the SMS (messages can be added and/or removed from anywhere in the cycle), and changing the structure of the subchannels.

SMS message IDs and their associated L2 frame starts include a list of all messages present in this SMS frame. The message ID must be unique for each SMS frame, and all 256 values must be used to help mobile stations retrieve changed messages and avoid reading unchanged messages before reuse. The start parameter of the L2 frame is used to indicate the beginning of the L2 frame at which this message starts (the message does not have to be at the beginning of the L2 frame). See the description of the S-BCCH L2 format for message passing.

In the example shown in the table below, 4 messages make up SMS frame 1. In this example, 1 slot is dedicated to the S-BCCH of each superframe, therefore, there are 24 slots per SMS frame. Previous SMS frame 1 header New SMS frame 1 header Subchannel number 3 Subchannel number 1 Subchannel period length 2 Subchannel period phase 1 Number of SMS messages (N) 4.1 SMS message ID 1.1 L2 frame start 1.2 SMS message ID 2.2 L2 frame start 2.3 SMS message ID 3.3 L2 frame start 2.4 SMS message ID 4.4 L2 frame start 3 Subchannel Number 3 Subchannel Number 1 Subchannel Period Length 2 Subchannel Period Phase 1 Number of SMS Messages (N) 5.1 SMS Message ID 1.1 L2 Frame Beginning 1.2 SMS Message ID 2.2 L2 Frame Beginning 2.4 SMS message ID 4.4 L2 frame start 2.5 SMS message ID 5.5 L2 frame start 3.6 SMS message ID 6.6 L2 frame start 3

In the above table, a mobile station is considered to be monitoring SPACH when the SMSN indicates a change in S-BCCH. The mobile station knows from the superframe counter that SMS subchannel 3 is currently broadcasting, and at this time determines that the SMSN refers to a change in SMS subchannel 1. When SMS subchannel 1 starts, the MS reads the SMS header. It determines that message 3 has been removed, the location of message 4 has changed (but the ID is the same, so the mobile station does not need to reread this message) and new messages 5 and 6 have been added and must be read. A mobile station may skip an appropriate number of L2 frames to read new messages. PCH is assigned to MS

Each MS is allocated a specific PCH sub-channel within the paging frame of a specific DCC. Available PCH subchannels and DCCs can be identified by DCC parameters broadcast on BCCH. The subchannel used is determined by the MS's IS-54B MIN identifier, which is hereinafter referred to as MSID.

DCC selection

DCCs are identified in a table broadcast on BCCH. This table must be the same for all DCC frequencies. The table contains:

1. Frequency or channel (f ₁ , i=1...k). For the current DCC, the position (i) in the table is broadcast and not the frequency.

2. The time slot number used for DCC (n _i , i=1...k), k is the DCC frequency number in the table.

A frequency can have any number of DCC slots indicated in the first table below. The used slots (s _j ) are numbered as shown in the second table below. slot number(n _i ) Timeslot used (s _j ,j=0,…n _j -1) rate 1246 11,41,4,2,51,4,2,5,3,6 Half Rate Full Rate 2 Full Rate 3 Full Rate

The slots (s _j ) used are numbered as follows: j S _j 012345 142536

The DCCs are numbered in the order they appear in Table (f _i ) and in Figure 16 as follows:

P=Summation(n _m ,m=0…i-1)+j,n ₀ =0,j=0…n _i -1,i=1…k

DCCp=f _i ,s _j ，

Note that full rate DCC gives two numbers. The total number of slots assigned to the DCC is N=sum(n _i ,i=0...k).

Figure 19 shows an example of a table broadcast on the BCCH (after including the current frequency). This is a case with two frequencies, f ₁ has 4 slots and f ₂ has 1 slot. The total number of DCCs is N=5. The DCC numbers are as follows: DCC number frequency time slot rate 12345 f ₁ f ₁ f ₁ f ₁ f ₂ 14251 full full half

MS is assigned to DCC according to the following algorithm:

DCC group = MSID modulo N, N as defined above.

The DCC group is the DCC number (P) according to the above table. If it (implicitly) indicates a full-rate channel ( _ni > 1), the entire full-rate channel is specified. The following PCH designations are based on parameters broadcast on the designated DCC frequency.

PCH sub-channel selection

The MS assigns the PCH slots in the superframe according to the following algorithm:

Case 1: main half rate, (j=0,n _i =1)

PCH-SUBCH=[(MSID div N)modulo NP+NB] ^*2

NP=16-NB case 2: main full rate, (j=0,1,ni＞1)

PCH-SUBCH=(MSID div N+j mod 2) mod NP

+NB

NP=32-NB case 3: slave full rate, (=2,3,4,5)

PCH-SUBCH=(MSID div N+j mod 2) mod NP

+NB+2 ^*

NP=32-4-NB

where: * = time slots in the frame corresponding to the BCCH and the previous and subsequent frames that cannot be used for the PCH dependent on the DCC.

NB=NFB+NEB+NSB+NSS

  NFB=Number of F-BCCH

The number of NEB=E-BCCH

The number of NSB=S-BCCH

NSS=Number of time slots skipped

N, j, _ni = as defined above.

PCH-SUBCH is the TDMA block number of the PCH subchannel within the superframe. The TDMA block number (SF phase count) is broadcast in the CSFP field.

PCH hyperframe selection

The MS assigns to the PCH hyperframe in the paging frame according to the following algorithm:

(MSID div N div NP) mod PFC=HFC mod PFC return

In the formula:

PFC = Paging Frame Class (1...4) for this actual MS.

HFC = Hyperframe Count (broadcast on BCCH). RACH sub-channel

overview

Multiplexing of RACH is done in order to have some processing time at base station and mobile station. In addition, the required time between the transmission of a burst and the SCF response corresponding to that burst is the same for both full-rate and half-rate DCC. Therefore, the number of sub-channels of the full-rate DCC can be set to six, for example.

SCF flags - relationship between uplink and downlink bursts

Fig. 20 shows the relationship between uplink slots and downlink SGF flags. Thus, following the arrow from left to right on sub-channel P1, the BRI readout of the SCF flag indicates the availability of the subsequent P1 uplink time slot, as shown in the figure. If an uplink burst is sent in that time slot, the next P1 downlink SCF indicates whether that burst was received or not, as indicated by the arrow. Also in case the burst is the first burst of random access, successive downlink PE values indicate to each mobile station which mobile station was acquired. If the mobile station's burst is received correctly, the BS will set PE, which tells the MS to send the next burst of its message in the next occurrence of P1 on the uplink (assuming the message is older than a burst string length). Note that this subchannel multiplexing is performed only with the SCF information in the downlink payload on the RACH. The payload data in the downlink is not transmitted using this subchannel multiplex.

In the case of reservation-based access (as distinguished from random access), the partial echo value is used together with the previous occurrence of the reservation flag for the downlink of that subchannel in order to identify the reserved access for a particular mobile station. Fig. 21 shows subchannels in the case of using full rate DCC. In the case of half-rate DCC, only subchannels P1, P3 and P5 are used.

Figure 21 shows an example of an L3 confirmed dialog between a mobile station and a base station (only time slots 1 and 4 corresponding to full rate DCC are shown). The mobile station first transmits a two-burst message via random access, checking the PE after the first burst. The actual transmission time of the MS is marked as X. Within a predetermined time (typically longer than shown in the figure), the base station responds with a message that is two bursts long (labeled Y in the figure). Finally, the mobile station transmits a single burst with reserved access (this reservation-based access is optional by the BS). Figure 21 also shows the associated SCF values. Layer 2/3 information conversion to E-BCCH

Groups of Layer 3 E-BCCH messages sent on the E-BCCH form a message string. The start of the message group is indicated by the start of the E-BCCH period found in the L2 header. Layer 2 Operating Protocol

Layer 2 protocols for downlink operation support the transmission of layer 3 messages on SPACH (SMSCH, PCH and AACH), F-BCCH, E-BCCH and S-BCCH. The Layer 2 protocol includes support for the ARQ mode of operation of SMSCH and ARCH. Layer 2 protocols for uplink operation support the transmission of layer 3 messages on the RACH. Since Shared Channel Feedback (SCF) determines channel operation for random access, no additional ARQ capability is explicitly built into the RACH layer 2 protocol.

The Layer 2 protocol defined here consists of Media Access Control (MAC) functions, although higher level Logical Link Control (LLC) may be included. Layer 2 protocol frames identified here are always transmitted logically, starting with the leftmost bit of the frame and ending with the rightmost bit of the frame.

RACH protocol

The RACH layer 2 protocol is used in the uplink, where all TDMA bursts are used to convey RACH information. Two RACH layer 2 protocol frames are constructed so as to be in the 117 or 95 bit envelope range. Another 5 bits are reserved as tail bits, resulting in a total of 122 or 100 bits of information conveyed in each RACH burst. The layer 2 protocol defined for RACH works using a shared channel feedback mechanism, as such, only ARQ operation type is supported. The range of possible RACH layer 2 frames is shown in Figures 22A-L. A summary of the fields used for RACH operation, including layer 2 protocol frames, is provided in the table below. Multiple L3 messages can be sent in one transaction.

Normal length protocol frame

When the system broadcast information indicates that normal length bursts are sent during the mobile station access procedure, the range of layer 2 protocol frames shown in Figures 22A-F can be used for the entire access. Fig. 22A shows a BEGIN frame (MSID type TMSI). Figure 22B shows a BEGIN frame (MSID type IS-54B MIN). Fig. 22C shows a BEGIN frame (MSID type TMSI). Fig. 22D shows a CONTINUE frame. Fig. 22E shows an END (end) frame. Figure 22F shows a SPACH ARQ status frame.

Application of normal length frames

BEGIN frame

The BEGIN frame must be used for the start burst of a random access transaction. The length of the L3 data field varies based on the length of the MSID and the number of layer 3 messages indicated by NL3M. The entire access transaction can be performed within this burst.

CONTINUE frame

CONTINUE frames are used when random access requires more than two frames to complete the access transaction. As many CONTINUE frames are sent as needed to complete multiple burst access transactions. The value in the CI field is inverted between 1 and 0 (starting with 0) with each new (ie, non-repeating) frame transmitted by the mobile station as indicated by the CF information. If the SCF requires retransmission of a previously sent frame, the frame shall be repeated without the CI field being inverted.

END frame

The END frame is sent as the final burst of a random access that requires more than one frame to complete the access transaction.

SPACH ARQ status frame

The SPACH ARQ Status frame is used to report the partial or complete status of ARQ based transmissions received by the mobile station on the SPACH. For each BEGIN or CONTINUE frame of ARQ mode received on SPACH, the FRNO MAP bit conversion field is set to "1" when received or set to "0" when not received.

  Shorten length protocol frame

When the system broadcast information indicates that shortened length bursts are sent during the mobile station access procedure, then the range of layer 2 protocol frames shown in Figures 22G-L can be used. Fig. 22G shows a BEGIN frame (TMSI of type MSID). Figure 22H shows a BEGIN frame (MSID type IS-54B MIN). Figure 22I shows a BEGIN frame (MSID type IM51). Figure 22J shows a CONTINUE frame. Figure 22K shows the END frame. Figure 22L shows a SPACH ARQ status frame. The length of the L3 data field varies based on the length of the MSID and the number of layer 3 messages indicated by NL3M.

Application of shortened length frame

The application of shortened length frames is no different from the application of normal length frames.

RACH field total

The following table summarizes the protocol fields of RACH layer 2: Field Name Length (bits) value BT=burst type 3 000=Start 001=Continue 010=End 011=SPACH ARQ Status 100…111=Reserve RSVD=Reserved 1 set to 0 CI = change indicator 1 Starting at 0, trigger on each newly transmitted frame. Keep the same for each repeated frame. IDT=identification type 2 00=20 bits TMSI01=34 bits MIN/IS-54B10=50 bits IMSI11=Reserved MSID = mobile station identification 20/34/50 20-bit TMSI34-bit IS-54B MIN50-bit IMSI NL3M=Number of Layer 3 Messages 2 00=1 Layer 3 message 01=2 Layer 3 messages 10=3 Layer 3 messages 11=4 Layer 3 messages L3LI = Layer 3 Length Indicator 8 Variable length Layer 3 messages supported by a maximum of 225 octets. L3DATA=Third layer data variable Field portions not used to carry a layer 3 message are filled with zeros including a portion (some or all) of the layer 3 message having the full length as indicated by the L3LI. PE=partial echo 7 The 7 least significant bits of the IS-54B MIN of the mobile station. TID=Treat ID 2 Indicates ARQ mode processing related to status reporting. FRNO MAP= frame number map 32 Partial or full bitmap indicating reception status of ARCH or SMSCH ARQ mode processing (1=frame received, 0=frame not received.) FILLER=burst filler variable All filler bits are set to 0 CRC = Cyclic Redundancy Code 16 Same generator polynomial as IS-54B (including DVCC). F-BCCH protocol

F-BCCH Layer 3 procedures are used when a TDMA burst is used to carry F-BCCH information. The first F-BCCH slot of a superframe must have a superframe segment (Phase) whose value is set to zero. All F-BCCH slots in a superframe are assumed to calculate the DVCC value with a CRC value of zero for the second layer. It should be noted that a full cycle of F-BCCH information (such as a set of Layer 3 messages) always starts at the first F-BCCH slot of a superframe and within the same superframe as many F-BCCH slots must be used Finish.

A single F-BCCH Layer 2 protocol frame is constructed so as to fit within a 125-bit packet. An additional 5 bits are reserved for tail bits, resulting in a total of 130 bits of information carried in each F-BCCH burst. The Layer 2 procedures defined for F-BCCH operation only support unacknowledged operation. The range of possible F-BCCH layer 2 frames is shown in Figures 23A-C. All fields included in the Layer 2 procedure frame for F-BCCH operation are provided in the table below.

The use of F-BCCH frame

The start (BEGIN) frame

Figure 24A shows a F-BCCH start frame (command minimum). Figure 24B shows another F-BCCH start frame (two L3 messages with a second L3 continuation message). The start frame is used to start sending one or more L3 messages on the F-BCCH. If the first L3 message is shorter than one frame, BE is added to the end of the L3 DATA field to indicate whether to start appending the L3 message in the start frame. If BE is equal to "END", the remaining BEGIN frames are filled with FILLER. If BE is equal to "BEGIN", then a new L3 message starts at the BEGIN frame. If the L3 DATA field ends on a frame boundary, there will be no BE bit. The "END" is implied. If the L3 DATA field ends with less than the remaining 9 bits in the frame, BE is set to "END" and the remaining frame is filled with filler.

Continuous frame (CONTINUE Frame)

Figure 24C shows a F-BCCH CONTINUE frame (command minimum). The CONTINUE frame is used for the continuation of an L3 message that was too long to fit in the previous frame. The CLI indicates how many bits belong to the frame of the continuation message. Since the CLI is given in bits, previous L3 messages must be filled with fillers. If BE is equal to "END", the remaining CONTINUE frames are filled with fillers. If BE equals "BEGIN", a new L3 message starts in CONTINUE. If the L3 DATA ends on a frame boundary, the BE bit will be set. The "END" is implied. If the L3 DATA field ends with less than the remaining 9 bits in the frame, BE is set to "END" and the remaining frame is filled with filler. CLI enables a mobile station to receive any message at the beginning of a consecutive frame even if the previous frame was not received.

Overview of F-BCCH fields

The following table summarizes the fields of the F-BCCH layer 2 procedure: Field Name Length (bits) value EC=E-BCCH change 1 Trigger to indicate the E-BCCH change. BC=start/continuous 1 0=start; 1=continuous CLI=Continuation Length Indicator 7 The number of remaining bits in the previous L3 message. L3LI = Layer 3 Length Indicator 8 Variable length Layer 3 messages supported by up to 255 octets. L3 DATA=Third layer data variable Include a part (some or all) of the Layer 3 message with the full length as indicated by L3LI. The portion of the field not used to carry Layer 3 information is filled with zeros. BE=begin/end 1 0=start; 1=end FILLER=burst filler variable All padding characters are set to zero. CRC=Cyclic Redundancy Code 16 Same generator polynomial as IS-548. A value of zero for DVCC is applied in the calculation for each F-BCCH L2 frame.

E-BCCH protocol

The E-BCCH Layer 2 procedure is used when a DATA burst carries E-BCCH information. It should be noted that a full period of E-BCCH (eg, a set of Layer 3 messages) does not have to be aligned with the start of the first E-BCCH slot of a superframe, and can span multiple superframes. A single E-BCCH Layer 2 protocol frame is structured so as to fit in a 125-bit packet. An additional 5 bits are reserved as tail bits to generate a total of 130 bits of information carried in each E-BCCH burst. The Layer 2 procedures defined for E-BCCH operation only support uncertified operation. The possible range of E-BCCH layer 2 frames is shown in Figures 24A-C. Figure 24A shows the E-BCCH BEGIN frame (command minimum). Diagram 2413 represents another E-BCCH BEGIN frame (two L3 messages with consecutive second L3 messages). Figure 24C shows an E-BCCH CONTINUE frame (command minimum). An overview of the fields comprising the Layer 2 procedures for E-BCCH operation is provided in the table below.

The use of E-BCCH frame

The use of E-BCCH frames is the same as the use of F-BCCH frames except as follows:

1. Compared with EC used in F-BCCH frame, ECS is an open field of E-BCCH frame.

2. An E-BCCH BEGIN (ECS=1) shall be used as the first frame of the E-BCCH period.

Overview of the E-BCCH field

The following table outlines the fields of the E-BCCH layer 2 procedures: Field Name Length (bits) value ECS=E-BCCH cycle start 1 0 = An E-BCCH cycle has not started 1 = An E-BCCH cycle has started BC=start/continuous 1 0=start; 1=continuous CLI=Continuation Length Indicator 7 Number of remaining bits in previous L3 message L3LI = Layer 3 Length Indicator 8 Variable-length Layer 3 messages supported by up to 255 octets L3 DATA=Third layer data variable Include a part (some or all) of the Layer 3 message with the full length as indicated by L3LI. Fields that are not used to carry Layer 3 information are filled with zeros. BE=begin/end 1 0=start; 1=end FILLER=burst filler variable All padding characters are set to zero CRC=Cyclic Redundancy Code 16 Same generator polynomial as IS-54B. Standard DVCC is applied in the calculation of CRC for each E-BCCH L2 frame.

S-BCCH protocol

The S-BCCH Layer 2 procedure is used when a TDMA burst is used to carry S-BCCH information. A single S-BCCH layer 2 protocol frame is structured so as to fit in a 125-bit packet. An additional 5 bits are reserved as tail bits to generate a total of 130 bits of information carried in each S-BCCH burst. The Layer 2 procedures defined for S-BCCH operation only support unproven operation. The possible range of S-BCCH layer 2 frames is shown in Figures 25A-C. Fig. 25A shows the BEGIN frame (command min). 25B (the other) represents the S-BCCH BEGIN frame (two L3 messages with consecutive second L3 messages). Figure 25C shows the S-BCCH CONTINUE frame (command minimum). An overview of the Layer 2 procedure frames including S-BCCH operation is provided in the table below.

The use of S-BCCH frame

The use of the S-BCCH frame is the same as the use of the F-BCCH frame except as follows:

1. The SCS is an open field of the S-BCCH frame compared with the EC used in the F-BCCH frame.

2. A S-BCCH BEGIN shall be used as the first frame of the S-BCCH period. Field Name Length (bits) value SCS=S-BCCH cycle start 1 0 = A S-BCCH cycle has not started 1 = A S-BCCH cycle has started BC=start/continuous 1 0=start; 1=continuous CLI=Continuation Length Indicator 7 Number of bits reserved in the previous L3 message. L3LI = Layer 3 Length Indicator 8 Variable length Layer 3 messages supported by up to 255 octets. L3 DATA=Third layer data variable Include a part (some or all) of the Layer 3 message with the full length as indicated by L3LI. Fields that are not used to carry Layer 3 information are filled with zeros. BE=begin/end 1 0=start; E=end FILLER=burst filler variable All padding characters are zeroed. CRC=Cyclic Redundancy Code 16 Same generator polynomial as IS-54B. Standard DVCC is applied in CRC calculation for each E-BCCH L2 frame.

SPACH procedure

The SPACH Layer 2 protocol is used when a TDMA burst is used to carry point-to-point SMS, paging, or ARCH messages. A single SPACH Layer 2 frame is structured to fit in a 125-bit packet. An additional 5 bits are reserved as tail bits to generate a total of 130 bits of information carried in each slot designated for SPACH purposes. Figures 26A-N illustrate the possible range of SPACH Layer 2 protocol frames under various conditions. An overview of possible SPACH frame formats is provided in the first table below. An overview of the fields containing the Layer 2 procedure frame for SPACH operation is provided in the second table below.

The use of SPACH frames

The same frame format is used for all SPACH channels, eg all frames always have a common header A. The content of header A determines whether header B is present in any given SPACH frame. Header A discriminates between hard (dedicated) paging frames, PCH frames, ARCH frames and SMSCH frames. A Hard Triple Page frame including three 34-bit MSIDs can be sent on the PCH (BU=Hard Triple Page). A hard quadruple page frame comprising four 20 or 24 bit MSIDs can be transmitted on the PCH (BU=hard quadruple page).

One or more L3 messages can be sent in one frame, or concatenated over several frames. MSID is only carried in frames with BU=PCH ARCH or SMSCH with BT=Single MSID, Double MSID, Triple MSID, Quadruple MSID or BEGIN in ARQ mode. The IDT identifies the formats of all MSIDs carried in a given SPACH frame (eg MSID formats are not mixed is allowed). Carrying pages on the PCH is not allowed for a continuation later than one SPACH frame (although the procedure allows it). All other PCH messages may continue later than one SPACH frame.

For operation without ARQ mode, the L2 SPACH procedure supports sending one L3 message to multiple MSIDs appended with a fixed point-to-point relationship between the MSID and the L3 message. The Message Map field (MM) is used to control this aspect of Layer 2 frame operation. A valid SPACH frame requires all L2 headers related to a given L2 frame to be fully included in the frame (eg, L2 headers from a given SPACH frame cannot be bundled into other SPACH frames). The offset indicator field (OI) is used to allow completion of a previously started Layer 3 message and start of a new Layer 3 message occurring within a SPACH frame.

Overview of the SPACH frame format

The following table outlines the possible SPACH formats: SMS PCH ARCH can be serialized Single MSID Two MSIDs Triple MSID Quadruple MSID Hard Triple Paging (MIN) Hard Quadruple Paging (MIN1) Continuous ARQ Mode BEGINARQ Mode CONTINUE Y Y Y YN Y Y YN Y Y YN Y Y YN Y N NN Y N NY Y Y YY N Y YY N Y Y

Fig. 26A shows the SPACH header A. Fig. 26B shows SPACH header B. Figure 26C shows a zero frame. Figure 26D shows a hard triple page frame (34-bit MIN). Figure 26E shows a Hard Quadruple Paging frame (24-bit MIN). Figure 26F shows a single MSID frame (PCH). Figure 26G shows a dual MSID frame (ARCH). Figure 26H shows a dual MSID frame with continuation (ARCH). FIG. 26I shows the continuation frame (ARCH). Figure 26J illustrates compensating for a single MSID frame (ARCH). Figure 26K shows a triple MSTD frame (ARCH, one L3 message for three MSIDs). Fig. 26L shows the continuous frame (ARCH). Figure 26M shows the start of ARQ mode (SMSCH). FIG. 26N shows the continuous (SMSCH) of ARQ mode.

SPACH header A

The SPACH header A includes burst usage information and a flag to manage the mobile station for sleep mode. The BU field provides a high level indication of burst usage. These flags indicate changes in sleep mode configuration as well as BCCH information. This header is always present in all possible SPACH frame types.

SPACH header B

The SPACH header B includes additional header information for identifying the reserved content of the Layer 2 frame. This header is present when header A indicates a PCH, ARCH or SMSCH type burst.

zero frame

When there is nothing to transmit for any given SPACH frame, a zero frame is transmitted by the BMI, if required.

Hard Triple Paging Frame

A hard triple page consists of three 34-bit MIN single-frame page messages.

Hard Quadruple Paging Frame

A hard quadruple page consists of a single frame page message for four 20 or 24 bit MISs as determined by the IDT.

A single MSID frame

A single MSID frame is used to start the transmission of an ARCH or SMS CHL3 message in no ARQ mode. In addition, this frame can also be used to send defined non-ARQ L3 PCH messages (paging or other). Paging messages sent using a single MSID frame cannot continue to other frames.

If an ARCH or SMSCH L3 message is too long to fit within a single MSID frame, then the remaining L3 information is carried using additional CONTINUE frames or MSID frames, if necessary. If the entire ARCH or SMSCH L3 message fits in a single MSID frame, it is padded with filler if necessary.

If a no-page PCH L3 message is too long to fit in a single MSID frame, then the remaining L3 information is carried using additional CONTINUE frames or MSID frames, if necessary. If the entire PCH L3 message fits in a single MSID frame, it is padded with filler if necessary.

Double MSID frame

The double MSID frame is used to start the transmission of two ARCH messages or two PCH L3 messages in no ARQ mode. The number of MSIDs is indicated in the BT field in the same IDT format used for both instances of the MSID. Paging messaging using a double MSID frame cannot be extended to other frames.

Triple MSID frame

The triple MSID frame is used to initiate the transmission of three ARCH L3 messages or three PCH L3 messages in no ARQ mode. The number of MSIDs is indicated in the BT field in the same IDT format used for all instances of MSIDs. Paging message transmissions using triple MSID frames cannot be extended to other frames.

Quadruple MSID frame

A quadruple MSID frame is used to initiate the transmission of four ARCH L3 messages or four PCH L3 messages in no ARQ mode. The number of MSIDs is indicated in the DT field in the same IDT format used for all instances of MSIDs. Paging message transmissions using quadruple MSID frames cannot be extended to other frames.

CONTINUE frame

CONTINUE frames are used for continuation of L3 messages that were too long for the previous frame. Note that the L2 header specific to any given SPACH frame must always be fully carried in that frame (eg the L2 header associated with a given SPACH frame will not be done with the following SPACH frame).

  ARQ mode BEGIN

The ARQ mode BEGIN frame is used for the start of a L3 ARCH or SMSCH message transmission in ARQ mode. The ARQ mode only includes an MSID in its L2 header and part of the L3 message itself. If the L3 message is too long for a single ARQ mode BEGIN frame, the reserved L3 information is carried in an additional ARQ mode CONTINUE frame if necessary. If the L3 message fits in a single ARQ mode BEGIN frame, it is padded with filler if necessary.

The PE field concatenated with the TID field identifies the processing started by the ARQ Mode BEGIN frame, and is used to associate any subsequent ARQ Mode CONTINUE frame with this same processing. An ARQ mode BEGIN frame has associated with it an implicit FRNO value of zero.

ARQ mode CONTINUE frame

The ARQ mode CONTINUE frame is used to extend an L3 ARCH or SMSCH message that was too long for the previous ARQ mode frame (BEGIN or CONTINUE). The FRNO field identifies CONTINUE frames within the entire L3 message. The FRNO field value is incremented for the transmission of each CONTINUE frame supported by a given process (ie, multiple CONTINUE frames may be sent to complete the process started by the ARQ mode BEGIN frame). The continuation frame of this ARQ mode is also used to repeat any previously transmitted ARQ CONTINUE frame that was not correctly received by the mobile station

Overview of SPACH Fields

The following table summarizes the SPACH Layer 2 procedure fields: Field Name Length (bits) value BU = use of burst 3 000=hard triple page (34 bit MSID) 001=hard quadruple page (20 or 24 bit MSID)010=PCH burst 011=ARCH burst 100=SMSCH burst 101=reserved 110=reserved 111=zero PCON=PCCHContinue 1 0 = No PCH continues 1 = PCH continues, active Notification of BCN=PCCH change 1 Switches when there is a change in the F-BCCH information. SMSN=SMS notification 1 Switches when there is a change in the S-BCCH information. PFM = paging frame modifier 1 0=Use the specified PF 1=Use a higher one than the specified PF BT=burst type 3 000=single MSID frame 001=double MSID frame 010=triple MSID frame 011=quadruple MSID frame 100=continuous frame 101=ARQ mode start 110=ARQ mode continuous 111=reserved IDT=identification type 2 00=20-bit TMSI01=24-bit MINI/IS-54B10=34-bit MINI/IS-54B11=50-bit IMSI MSID = mobile station identification 20/24/34/50 20-bit TMSI24-bit MINT34-bit MIN50-bit IMSI MM=Message Map 1 0=one L3L1 and L3 DATA sample per MSID sample, 1=one L3L1 and L3 DATA sample for multiple MSIDs OI = offset indicator 1 0 = Does not contain the offset of the message. 1=Include message offset. CLI=Continuation Length Indicator 7 Number of bits reserved in the previous L3 message L3LI = Layer 3 Length Indicator 8 Variable length Layer 3 messages supported by up to 255 octets. L3 DATA=Third layer data variable Include a part (some or all) of the Layer 3 message with the full length as indicated by L3LI. Fields not used to carry Layer 3 information are filled with zeros PE=partial echo 7 The 7 least significant bits of the mobile station IS-54B MIN. TID=Treat ID 2 A transaction indicating ARQ mode is being sent on ARCH or SMSCH. FRNO=frame number 5 Uniquely indicates the transmission of a particular frame processed in ARQ mode. FILLER=burst fill variable All filler bits are set to zero CRC=Cyclic Redundancy Code Filler 16 Same generator polynomial as IS-54B (including DVCC) random access

start MS side

start random access

The mobile station will be in the "start random access" state until the first message unit sent by random access has been sent.

Start reserved access:

The mobile station will be in the "start reserved access" state until the first message unit sent by the reserved access basis has been sent.

Multiple units

A mobile station will be in "multiple cell" state if there are more than one cell associated with the same outstanding transmitted access event.

After the last burst

If the last unit of an access event has been sent, the mobile station will be in the "after most burst" state.

success

After a message has been successfully sent, the mobile station will be in the "success" state.

Components of the procedure

  Forward sharing control feedback flag

General

Forward Shared Control Feedback (SCF) flags are used to control reserved channels such as RACH.

Busy/Reserved/Free

The busy/reserved/idle flag is used to indicate whether the corresponding uplink RACH slot is busy, reserved or idle. There are six bits used for these flags, and the different states are encoded, as shown in the following table: BRI ₅ BRI ₄ BRI ₃ BRI ₂ BRI ₁ BRI ₀ busy keep free 1 1 1 1 0 00 0 1 1 1 10 0 0 0 0 0

received/not received

A received/not received flag (R/N) is used to indicate whether the base station has received the last transmitted burst. Five repetitions are used to encode these flags, as shown in the following table: R/N ₄ R/N ₃ R/N ₂ R/N ₁ R/N ₀ received not received 1 1 1 1 10 0 0 0 0

partial echo

Part of the voiced information is used to identify that the MS was correctly received after the initial random access burst and/or that the MS intends to have access to reserved slots. Seven LSBs of IS-54B are assigned to PE. The channel coding has been described in the physical layer specification above.

Decoding of the SCF flag

BRI and R/N

The following table shows how the mobile station decodes the received flag according to the state of the second layer. It should be noted that only flags related to the state of the second layer are shown. In the "start random access" state, the BRI flag is only an association flag. During multi-burst message transmission, the BRI is associated with the R/N flag. In the summary of the table below, bi is equal to the bit value.

partial echo

If it differs from the corrected coded partial echo (CPE) by less than 3 bits, the mobile station interprets the received coded partial echo value as an error-corrected decode. This is called PE matching.

The process of random access

  Mobile Site Test

A mobile station is allowed a maximum of Y+1 transmission attempts, where Y=(0...7), before it considers an attempt to convert an error message. After no idle state or one transmission attempt, the random delay period for the mobile station is evenly distributed between 0 and 200ms with a granularity of 6.667ms (slot length). The mobile station is not allowed to generate more than Z consecutive repetitions of each burst, where Z=(0...3).

start random access

When the mobile station is in the starting "random access" state, it will see the first occurrence of a downlink DCC slot regardless of the subchannel of the current DCC (see physical layer). If the mobile station finds a free time slot, it will send the first unit of the message in the corresponding sub-channel uplink RACH. If the slot is found to be busy or reserved, the mobile station will generate a random delay. After the random delay expires, the mobile station will repeat the previous process. Each transmission attempt for an idle retrieval is repeated at most X+1 times, where X=(0.9). Except initially, the MS has to monitor its PCH during the random access procedure.

  Start reserved access

For slots marked with BRI as reserved and a PE match, when the mobile station is in the "begin reserved access" state, it will continuously see in the slots of the current DCC in all downlinks, regardless of the subchannel . The BS can assign reserved time slots to a given MS regardless of the subchannels previously used by the MS. If the mobile station finds this time slot, the mobile station will send the first unit of the message in the corresponding uplink RACH subchannel. If the mobile station does not find this time slot within a predetermined time-out period (T), the mobile station will enter the "start random access" state.

Check for PE match

After the random access first burst has been sent. The mobile station reads the partial echo field in the next time slot of the corresponding DCC subchannel. If a PE match is found, the mobile station will assume that the SCF designation in the downlink has been assigned to it, and then enter the subsequent last burst state or multi-cell state. If the mobile station does not find a PE match, it will generate a random delay and enter the start random access state.

Multiple units

If the mobile station has multiple cells to transmit, it will decode the SCF flag for the corresponding subchannel. If it finds the R/N flag set, it will consider the last sent burst received; otherwise it will consider it not received. It will also consider the burst not received if it finds that the channel is placed on reserve or idle. If more than S+1, where S=(0,1), consecutive "not busy" reads are generated by the mobile station, it will discard the transmitted message and begin another transmission after a random delay try. If the burst is deemed received, the mobile station will transmit the next burst of the message in the next time slot of the lower subchannel. If the burst is found not received, the mobile station will retransmit the last transmitted burst.

After the last burst

If the mobile station reads the SCF flag of the currently used subchannel, after it has sent the last burst and determined from the R/N flag that this burst has been received, the MS side of the SCF procedure will consider the message to have been received. sent correctly. It will also consider the burst not received if it finds that the burst has not been received and the channel has been placed on reserve or idle. If more than S+1, where S=(0,1), consecutive combined "not received" and "not busy" reads are generated by the mobile station, it will abort the transmission of the message and Afterwards another transfer attempt is started. If the burst is found not received, the mobile station will resend the last transmitted burst.

The process of MS and BS random access

The random access process described above is illustrated in Figures 27A-B. FIG. 27A shows the random access procedure of the MS, and FIG. 27B shows the random access procedure of the BS. The following is an itemized illustration of the truth table used in the process in Figure 27A:

1. At the beginning of an access-based contention, the truth table is checked. If SCF = "Reserved" or "Busy", the mobile station will increment the busy/idle counter and compare it to X. If SCF = "idle", the mobile station shall set the cell counter to 1 and send the first burst of the access.

2. After sending a given burst of an access with at least one multi-pending burst, the truth table is checked. If SCF = "idle" or "reserved", the mobile station will increment the "stop" counter and the PB counter, then compare the "stop" counter with S. If SCF = "busy" and "not received" then the mobile station will increment the PB counter and then compare it with Z. If SCF = "Busy" and "Received", the mobile station will increment the "Unit" counter and set the PB counter to zero.

3. After sending the last burst of an access, the truth table is checked. If SCF = "Received", then the mobile station will increment the "Stop" counter and the PB counter, then compare the "Stop" counter with S. If SCF = "Reserved" and "Not Received", the mobile station will increment the "Stop" counter and the PB counter, then compare the "Stop" counter with S. If SCF = "busy" and "not received", the mobile station will retransmit the last burst of the visit.

4. At the beginning of an access-based reservation, the truth table is checked. If SCF = "busy" or "idle", then the mobile station checks the reservation timer. If SCF="Reserved" and PE do not match, the mobile station checks the reserved timer. If SCF="Reserved" and PE do not match, the mobile station will set the cell counter to 1 and send the first burst of the access.

Monitoring of radio link quality (MRLQ)

 Measuring process and processing

The mobile station will measure word errors during the readout of one slot in each paging frame. During each paging frame, the MS can read one or more SPACH slots corresponding to the PCH continuation and first/second superframe structure. However only one read will update the MRLQ word error parameter, ie only one update per paging frame. During RACH operation, the MS must also read one forward slot per paging frame for this purpose.

The MS shall initially set the MRLQ counter to ten (10) based on one cell's camping (Campimg). Each update of the MRLQ will increment the MRLQ counter by one (1) if the CRC check is successful. An unsuccessful read will decrement the MRLQ counter by one (1). If the value of the MRLQ counter exceeds ten (10), the MRLQ counter will be shortened to a value of ten (10), ie its value will never exceed ten (10).

Criteria for wireless link errors

When the MRLQ counter reaches zero (0), then a radio link error is declared, in which case the MS will check the full reselection data parameter. The MS will then perform RSS measurements on frequencies in NL until the full reselection data parameter equals one.

Allocation of Mobile Auxiliary Channels

General

When the mobile station is in the idle state, the mobile station will inform the system of the quality of the forward DCC (this function is referred to herein as function i). The report generated by the mobile station will include the results of Word Error Rate (WER), Bit Error Rate (BER) and Received Signal Size (RSS) measurements. During the idle state, the mobile station also measures RSS on other frequencies and reports to the system (this other function is referred to herein as function ii).

operation mode

According to the information received on BCCH, the system can choose the following modes:

1. Invalid MACA (MACA-STATUS=00)

2. Function ⅰ (MACA-STATUS=×1)

3. Function Ⅱ(MACA-STATUS=1×)

4. Use the MACA TYPE parameter (MACA TYPE = 01, 10 and 11 respectively) to enable function i and function ii according to the type of access attempt (paging response, origination and registration).

  Broadcast information

The BCCH includes the following information:

1. MACA-STATUS: No MACA, function i, function ii, or functions i and ii.

2. MACA-LIST: This system sends a list of 8 frequencies on the BCCH on which the mobile station will measure its signal strength.

3. MACA-TYPE: What type of access will include function i or function ii, if any, as part of the MACA report.

Contents of MACA report information

The MACA report will contain the following information:

1. What type of MACA report is being generated (functions i and ii).

2. Whether a MACA report is based on a full measurement interval.

3. This measurement is generated by a specific MACA report.

process

 Measurement process for DCC (function ⅰ)

Units of measurement

The mobile station will report measurements of channel quality and signal strength. Channel quality is defined as word error rate (WER) and bit error rate (BER). Signal strength is measured in dBm.

The measurement time interval

The mobile station performs a running average over its last 32 paging frames related to the PCH for signal quality and signal strength. This first SPACH read will update all three variables. Averaging of signal strength is done in dBm units. Averaging can be done similar to IS-54B MAHO.

Measurement process on another channel (function ii)

Units of measurement

The mobile station will report signal strength in dBm.

The measurement time interval

The mobile station will measure each frequency at least 4 times. The minimum time between measurements on the same frequency will be 20ms. The maximum time between measurements at the same frequency will be 500ms. Average signal strength is done in dBm. MS can take continuous measurements or just before a visit.

      MACA Report

The mobile station informs the system by moving the full MACA interval flag, whether a full measurement interval has been completed at that time, the MACA report is sent.

SPACH ARQ

BMI side

Start ARQ mode

The BMI starts an ARQ mode procedure by sending an ARQ mode BEGIN frame, which includes the mobile station identification (MSID), partial echo (PE), which is placed on the 7 least significant bits of the mobile station IS-54B MIN , the process identification (TID), which uniquely identifies an instance of an ARQ mode process is beginning to be sent to the mobile station, the L3 length indicator (L3LI), which is used by a mobile station to calculate the number of consecutive frames expected to follow the ARQ mode BEGIN frame Quantity, and a part of L3 data (L3 DATA).

  Acknowledgment of starting ARQ mode

After sending an ARQ mode BEGIN frame, the BMI can wait for an acknowledgment from the mobile station, since this frame contains the key information for all successful processing of an ARQ mode. If the BMI decides not to wait for an acknowledgment from a mobile station, it proceeds to send an ARQ mode CONTINUE frame. Conversely, the BMI will proceed as follows: The BMI polls the mobile station with the BRI flag set to "reserved" and the PE set to the value corresponding to the target mobile station in the same downlink time slot. The BMI then waits for an uplink ARQ status message on the same access channel that polled the mobile station. If an ARQ Status message is not received on a reserved access slot, or an erroneous command is received with a frame not yet acknowledged, the BMI will retransmit the Start ARQ Mode message up to a predetermined number of times. If the BMI has not received a correct ARQ status message after a certain number of attempts, it shall terminate the processing of the ARQ mode. If the BMI receives a correct ARQ status message after a certain number of attempts, it shall proceed to transmit a CONTINUE frame in ARQ mode.

Continuous in ARQ mode

The BMI sends an ARQ mode CONTINUE frame to complete the initial ARQ mode processing. These frames include a partial echo (PE) of the 7 least significant bits of the IS-54B MIN set to the mobile station, a transaction identifier (TID) that uniquely identifies an ARQ mode transaction instance being sent to the mobile station, and identifies each consecutive The continuous frame number (FRNO) of the frame, and a part of the L3 data. An ARQ mode BEGIN frame has an implicit FRNO value of 0 associated with it, whereas an ARQ mode CONTINUE frame has an explicit FRNO value starting with 1. The FRNO value is incremented for each new ARQ mode consecutive frame transmitted with a BMI supported by the particular ARQ mode process.

After transmitting any intermediate ARQ mode CONTINUE frames, the BMI starts polling the mobile station. If the BMI decides to issue an intermediate poll, it proceeds: the BMI sets the BMI flag to "reserved" and sets PE to the value corresponding to the target mobile station in the same downlink time slot. The BMI then waits for an uplink ARQ status message on the same access channel that polled the mobile station. If no ARQ Status message is received on the reserved access slot, the BMI will send the Start ARQ Mode message up to a predetermined number of times. If the BMI has not received a correct ARQ status message after a certain number of attempts, it will terminate the processing of the ARQ mode. If the BMI receives an ARQ status message, it shall send ARQ mode CONTINUE frames starting with those marked as received in error. When the BMI sends the last ARQ mode CONTINUE frame, it will proceed as described in the next section.

Termination of ARQ mode

After sending the last ARQ mode CONTINUE frame, the BMI polls the mobile station as follows: The BMI sets the BRI flag to "reserved" and sets PE to the value corresponding to the target mobile station in the same downlink slot. The BMI then waits for an uplink ARQ status message on the same access channel that polled the mobile station. If no ARQ Status message is received on the reserved access slot, the BMI will retransmit the Start ARQ Mode message a predetermined number of times. If the BMI has not received a correct ARQ status message after a certain number of attempts, it will terminate the processing of the ARQ status mode. If the BMI receives an ARQ Status message and the FRNO MAP indicates "all correct", the ARQ mode process is considered to have completed successfully. If the BMI receives an ARQ status message, but the FRNO MAP does not indicate "all correct", it will send an ARQ mode CONTIUE frame marked incorrectly received. The BMI shall retransmit any given ARQ Mode CONTINUE frame up to a predetermined maximum number of times before terminating the ARQ Mode process.

MS side

Start ARQ mode

After a mobile station has entered the start ARQ mode and has successfully completed the transmission of the first burst of an ARCH or SMSCH message (as indicated by the SCF flag), the mobile station begins the period from 40 ms after the successful completion of this burst transmission. ARCH or SMSCH is read in a predetermined number of SPACH frames. When it receives an ARQ-mode BEGIN frame with an MSID matching its own, the mobile station will proceed: TID is stored for ARQ-mode transmission identification purposes. A number of outstanding ARQ mode CONTINUE frames will be calculated from the received L3LI. The FRNO MAP shall be set to "received" for FRNO zero (corresponding to ARQ mode BEGIN) and to "not received" for all outstanding ARQ mode CONTINUE frames. The FRNO MAP supports BMI transmissions up to 32 ARQ mode frame lengths (1BEGIN and 31CONTINUE). The part of the L3 message carried in L3 DATA will be stored. The mobile station will then proceed to what is described in the next section.

Continuous in ARQ mode

The mobile station will read the SPACH frame and respond as follows: If the poll is issued (i.e. PE match is generated together with an SCF reservation order), the mobile station will send an ARQ status with FRNO MAP indicating the current FRNO reception status to BMI. If the FRNO MAP indicates that there is an "all correct" status, the mobile station considers that the processing of the corresponding ARQ mode is successfully completed. If the ARQ mode CONTINUE frame is correctly received for an unacknowledged ARQ mode process (ie PE and TID matching), the mobile station shall store the L3 DATA contained therein and set the corresponding FRNOMAP part to RECEIVED. If no ARQ mode CONTINUE frames or polls are received within a predetermined period, the mobile station will send an ARQ status message using contention based random access. Such unsolicited ARQ states may be sent in bulk before the corresponding ARQ mode transmission is terminated. 28A-B illustrate the operation of MS (FIG. 28A) and BS (FIG. 28B) in SPACH ARQ mode. Layer 3 and Higher Layer 3 Operations

Figure 29 shows a state diagram for a mobile station which will be discussed in more detail below. Description of mobile station state Zero state (D1)

If a mobile station is powered off, it will be in a "zero" state. When the power is turned on, the mobile station will enter the "control channel scan and lock" state. Control channel scan and lock status (D2)

When a mobile station is in the process of selecting a candidate service provider (ACC or DCC), it will be in the "control channel scan and lock" state. While in this state, a mobile station can determine an analog control channel (ACC) as the best service provider at any time, in which case it will enter the "initialization" task (see 2.6.1 of IS-54B) . Additionally, the mobile station will attempt to find a Digital Control Channel (DCC) service provider. It can search for a candidate DCC as described below in the DCC Scanning and Locking Process section. If a mobile station finds a candidate DCC, it will perform the cell selection procedure described below. If the candidate DCC meets the criteria described in the cell selection procedure, the mobile station will enter the "DCC Camping" state described below. Otherwise, the mobile station will search for another candidate DCC. DCC reservation status (D3)

As long as a mobile station is logically connected to the "best" cell as specified by the cell selection rules described below, it will be in the "DCC Camping" state. At cell reselection or when the visited system is used for a mobile station to originate a call, a mobile station terminate a call, a registration, an SSD update or a point-to-point SMS (mobile station terminated), the mobile station will leave the state. When reading the broadcast information of its current DCC or neighboring DCCs, the mobile station will not appear in the "DCC camped" state. While in this state, the mobile station performs different tasks depending on the received different information.

If a BCCH message is received, the mobile station will update the stored BCCH information according to the received message. If a Registration Parameters message is received, and the optional information element "REGID parameter" is not part of this message, then the mobile station shall not add REGID to this DCC. If the optional information elements "REGID parameter" and "REG period" are part of this message, the mobile station shall maintain an updated REGID code by continuously monitoring it or incrementing it internally every REGID-PER superframe. The mobile station will then invoke the registration procedure described below.

If a BCCH Neighbor Cell message is received, the mobile station will begin monitoring neighboring DCCs for cell reselection purposes by invoking a cell reselection procedure, if necessary.

The mobile station will respond with the states shown below:

PER-COUNTER TIMEOUT: The registration procedure will be called.

REREG-TMR timeout: The registration procedure will be called.

REGID INCREASE EVENT: The register procedure will be called.

Power down event: The registration procedure will be called.

The originally received FDCC indication includes a PCH message: Termination procedure shall be invoked.

User Start: The start procedure will be called.

Current DCC is blocked: If the current DCC becomes blocked, the mobile station will invoke the cell reselection procedure in order to select a new service provider from its neighbor list. Registration process (D6)

When a mobile station has sent registration messages to the base station, but has not received a response, it will be in the "registration process". The mobile station will respond with a status indicated as follows:

REG-TMR timeout: If the mobile station retransmits its registration up to 5 times, it will terminate this procedure and enter the DCC camped state. Instead, it sets the REREG-TMR timer to a random time evenly spaced in the interval of 10 to 100 seconds, terminates the procedure, and then enters the DCC Reserved state.

ARCH message received: If a registration accept message is received, the mobile station will terminate this procedure and then invoke the registration success procedure described below. If a registration rejection message is received, the mobile station will terminate the procedure and then invoke the registration failure procedure.

PCH message received: stop REG-TMR, terminate this procedure, then call the termination procedure as described below. Start Process (D4)

After a mobile station has successfully sent a start message but has not received a response from the BMI, it will be in the "start process". The mobile station will respond with a status indicated as follows:

ORIG-TMR timeout: Terminate this procedure, and then enter the DCC reservation state.

ARCH message received: If a digital traffic channel indication message is received, the mobile station will stop the ORTG TMR, update the parameters as received in the message, invoke the registration update procedure, and then enter the task of confirming the initial traffic channel ( See 2.6.4.2 of IS-54B). If an Analog Traffic Channel Indication message is received, the mobile station shall stop the ORIG TMR, update the parameters as received in the message, invoke the Registration Update procedure, and proceed to the Verify Initial Voice Channel task (see 2.6. 4.2). Wait for command (D5)

After a mobile station has successfully sent a page response in response to a page, but has not received a response from the BMI, it will be in the "waiting for command" state. The mobile station will respond with a status indicated as follows:

WAFO-TMR timeout: Terminate this procedure, and then enter the DCC reservation state.

ARCH message received: If a digital traffic channel indication message is received, the mobile station will stop WAFO-TMR, update the parameters as received in the message, invoke the registration update procedure, and then enter the task of confirming the initial traffic channel (see 2.6.5.2 of IS-54B). If an analog traffic channel indication is received, the mobile station shall stop WAFO-TMR, update the parameters as received in the message, invoke the registration update procedure, and then proceed to the task of confirming the initial voice channel (see IS-54B 2.6. 5.2). SMS peer-to-peer process (D8)

After a mobile station has successfully sent a SPACH in response to an SMS notification, but has not yet received a response from the BMI, it will enter the "SMS point-in-time process" state. The mobile station will respond with a status indicated as follows:

SMS-TMR timeout: Terminate this procedure, and then enter the DCC reservation state.

ARCH message received: If an R-DATA message is received and accepted by the mobile station, it will stop the SMS-TMR, update the information as received in the message, send an R-DATA ACCEPT message, and terminate the message. program, and then enters the DCC reservation state. If a R-DATA message is received and rejected by the mobile station, it will stop SMS-TMR, send a R-DATA REJECT message, terminate the procedure, and then enter the DCC reservation state.

PCH message received: Stop SMS-TMR, terminate this procedure, then call the termination procedure described below. SSD update process (D7)

After a mobile station has successfully sent a response to an SSD update command but has not yet received a response from the BMI, it will be in the "SSD update in progress" state. The mobile station will respond with a status indicated as follows:

Expiration of SSDU-TMR: Terminate this procedure, and then enter the DCC reservation state.

ARCH message received: If the BMI query order confirmation was received, the mobile station will stop the SSDU-TMR, update the parameters as received in the message, send an SSD UPDATE order confirmation message, terminate the procedure, and enter DCC reservation state.

PCH message received: Stop SSDU-TMR, terminate this procedure, then invoke the termination procedure described below. Program DCC scan and lock

Find the DCC

Two techniques can be used to simplify the mobile station's acquisition of a DCC: DCC probability assignment and DCC positioning. Probability Assignment for DCC

To aid the mobile station in its search for a DCC, the available frequencies can be grouped into blocks, with each block assigned a different probability, which reflects the relative likelihood of finding a DCC in each block. In this way, the time required for mobile station traffic acquisition can be significantly reduced. The following two tables illustrate how the channels in the A-segment and B-segment respectively are assigned different relative probabilities for supporting DCC acquisition. This technique is typically used by a mobile station before a mobile station has received any DCC location information (described below). Once a mobile station has received DCC location information, it will use this information instead of the channel block probability scheme described here.

A-block channel number relative probability 1-2627-5253-7879-104105-130131-156157-182183-208209-234235-260261-286287-312313-333667-691692-716991-1023 12345678910111216131415

B-block channel number relative probability 334-354355-380381-406407-432433-458459-484485-510511-536537-562563-588589-614615-640641-666717-741742-766767-799 16123456789101112131415 DCC positioning

The DCC locate is a 7-bit parameter that provides information to help a mobile station locate a DCC. The DL identifies the mobile station RF channel that carries the DCC. DL values 1, 2, 3, . . . 127 are encoded to form the CDL sent on DTC in bit positions 314 to 324 of a TDMA slot (see physical layer description). DL values 1, 2, 3...127 are mapped to channels 1-8, 9-16, 17-24,...1009-1016, respectively. So, for example, if a DCC occupies channel number 10, a value of 2 for DL will be sent on the DTC of the same cell. A DL value of zero does not provide any location information, but instead indicates that no DL information is being provided by the system. priority channel assignment

All channel numbers are valid candidates for DCC allocation. Given that the DL does not uniquely identify any particular channel number, it is desirable to establish a priority scheme within each channel block. A mobile station receiving a DL value associated with a particular channel block will not be able to automatically search all channels, but will instead search for DCCs in that block according to this priority scheme. So, for example, for a DL value of 1, the mobile station will check channel numbers 8 to 1, starting at 8, 7, etc., in an attempt to find the DCC. Discriminate CDVCC and CSFP field information between DCC and DTC

Although the IS-54B DTC and DCC downlink slot formats have a common structure, there are certain differences that allow the DTC to determine the DCC. First, due to the difference in DVCC and SFP channel coding, there are always 4 bits other than 12 that differ in each pair of CDVCC and CSFP, regardless of the CDVCC or CSFP codeword transmitted by a base station (thus due to wireless channel impairments The generated bit error may change to a different content than the transmitted codeword received by the mobile station). Second, the CDVCC content is fixed slot-by-slot on a DCT, whereas the content of the CSFP changes slot-by-slot on a DCC in a predictable manner. Data Field Information

Utilization of channel coding and interleaving on DTC is different from that on DCC, regardless of DTC traffic (voice or FACCH). This difference can be used to distinguish between DCC and DTC. SACCH and RESERVED (standby) field information

The IS-54B SACCH and RESERVED fields have different functions on DCC. Therefore, these fields may also be used to distinguish between DCC and DTC. mesh selection

To perform a cell selection procedure to allow a mobile station to determine whether a given alternative DCC is acceptable for the purpose, the mobile station should always perform a path loss determination procedure (described below) and may optionally perform a traffic aspect determination procedure (described below). The mobile station then returns to the calling procedure. Path loss determination

The mobile station uses the "path loss criterion" C_PL > 0 to determine whether the alternative DCC is suitable for camping purposes:

C_PL=RSS-RSS_ACC_MIN-MAX(MS_ACC_PW-P)＞0

here:

RSS is the average received signal strength. Signal strength measurements may be performed in a manner similar to the task of signal strength measurement techniques in IS-54B.

RSS_ACC_MIN is a parameter broadcast on BCCH. It is the minimum received signal level required to access the cell.

MS_ACC_PW is a parameter broadcast on BCCH. It is the maximum output power a mobile station can use when initially accessing the network.

P is the maximum output power of the mobile station, determined by its power class according to IS-54B.

If the alternative DCC does not meet the path loss criteria, it shall be rejected by the mobile station. The mobile station should then return to the calling procedure. Determination of business aspects Mandatory

If the broadcast option DCC is identified as blocked according to the "Cell Barred" parameter in the Access Parameters message, it shall be rejected by the mobile station. If this procedure is invoked, resulting in a cell selection, and the ISP flag broadcast in the cell selection parameters is set, the mobile station will not select a cell unless there are no other cells satisfying the path loss criterion C_PL. If the selector DCC is marked private according to the network type (see below), and the PSID compliance criteria are not met, the mobile station shall not attempt to camp or camp on the private system. optional

If the selected cell does not provide the desired service to the mobile, the mobile station is authorized to reselect the following criteria (i.e. the mobile station may not choose the best RF neighbor) among the cells satisfying the first set of criteria (Re)select a mesh. mesh reselection

A cell reselection procedure is performed to allow a mobile station to determine whether a given neighboring DCC constitutes a better service provider than its current DCC. The mobile station should always execute the cell reselection algorithm and the reselection criteria procedure described below, and then return to the calling procedure. scanning process

There are two information units sent on the BCCH related to the scanning process: SCANFREQ and HL_RFEQ. SCANFREQ is sent within the Cell Selection message on the F-BCCH and informs the mobile station about the minimum number of required signal strength (SS) measurements per superframe about errors. The total number of SCNFREQSS measurements per SF that the mobile station should complete regardless of the size of the neighbor list (NL). However, this error rule may be modified by the HL_FREQ message. HL_FREQ is sent within NL. There is one HL_FREQ associated with each input (frequency) of NL. If HL_FEEQ is set to HIGH, this particular frequency shall be measured according to the basic rules specified by the SCANFREQ rule. If HL_FREQ is set LOW, this particular frequency can be measured at half the frequency required by the error SCANFREQ rule. For example, if an NL contains 16 inputs, some with HL_FREQ set to HIGH and the rest to LOW, and SCANFREQ is set to 12 measurements per SF, then the number of measurements marked HIGH on the input should be 12 measurements per SF 12/16 minimum ratio measurements, and the number of measurements marked LOW on the input should be measured with a 12/16/2 minimum ratio per SF. Basic Process and Requirements

The mobile station shall determine the number of measurements per input per superframe from the information of NL (frequency and HL_FREQ) and the measurement parameter SCANFREQ. This requirement is specified as the Basic Measurement Requirement (BMR). Therefore, different measurement frequencies may be required for different input BMRs. However, assuming all inputs are processed with HL_FREQ set to HIGH, the mobile station can select all frequencies. The mobile station should spread the timing of the measurements, possibly even over the entire frequency. Errors and potentially modified paging frame classes assigned to the MS should not affect MS procedures. Optional enhancements to the base process

To benefit the effectiveness of the dormant approach, the MS allows changes to the BMR process described in Basic Processes and Requirements and still follow this specification. Only the frequency required by the measurement can be changed. There are three techniques that can be used by the MS to minimize battery consumption. All three techniques can be applied simultaneously if the pre-required conditions are met. The three technologies and their associated conditions are as follows:

1. If the number of cell reselections performed by the MS during the extended period of time (>5 hours) is low (<5), and because the last cell reselection expiration time is greater than 2 hours, then the mobile unit allows access to all incoming The measurement frequency is reduced, but the DCC of the service is twice as compared to the BMR. This reduction is canceled if the MS performs a cell reselection.

2. If the rate of change of signal strength (SS) on the serving DCC is less than 5 dB in the last 5 minutes, and the rate of change of all incoming signal strength (SS) in NL is less than 5 dB in the last 5 minutes, then the mobile unit is allowed Reduce the test volume frequency, but the DCC and BMR of the service are 2 times.

3. If the rate of change of the difference between the SS and NL specific inputs of the serving DCC is less than 5 dB in the last 5 minutes, the mobile unit can reduce the measurement frequency by a factor of 2 on the NL specific inputs satisfying the above conditions.

If the rate of change in the serving DCC signal strength (SS) is 5 dB within the last 20 paging frames or if the change in signal strength on any input to the NL is within the last 100 superframes If the rate is greater than 5dB, the reduction of the measurement frequency according to the above points 2 and 3 is cancelled. Processing of measurement data

The full reselection data is set to zero according to the reserved cell parameters. The full reselection parameter is set to 1 after each entry in the neighbor list has been measured 4 times. reselect criteria

The mobile station uses the "Cell Reselection Criteria" C_RES to determine the best candidate DCC to camp on. The mobile station shall select a new serving DCC if the following criteria are met: (C_PL _new > o) AND (T > DELAY) AND [(CELLTYPE = PREFERRED AND RSS > SS SUFF) OR (CELLTYPE = REGULAR AND C_RES > O) OR(CELLTYPE=NON_PREFERED AND RSS _old <SS_SUFF _old ]

here:

C_RES=C_PL _new -C_PL _old +RESEL_OFFSET _new -RESEL OFFSET _old

C_PL is the "path loss criterion".

C_PL _new is the C_PL for the option DCC.

C_PL _old is the C_PL for the current DCC.

T is a timer, when C_PL _new becomes greater than o, the timer starts. When CP_L _new becomes less than or equal to O, T is reset.

DELAY is a broadcast parameter on BCCH (see below).

RESEL_OFFSET is a broadcast parameter on BCCH (see below).

RESEL_OFFSET _new is the reselected offset relative to the selector DCC.

RESEL_OFFSET _old is the offset relative to the current DCC.

CELLTYPE is a broadcast parameter on BCCH (see below). It takes the value REGULAR, PREFERPED or NON_PREFERRED.

SS_SUFF is a broadcast parameter on BCCH (see below).

SS_SUFF _new is SS_SUFF for selector DCC.

SS_SUFF _old is the SS_SUFF for the current DCC.

RSS _new is the RSS for selector DCC.

RSS _old is the RSS for the current DCC.

Whenever more than one selector DCC of CELLTYPE satisfies this criterion, they shall be selected in priority order of PREFERRED, REGULAR, NON_PREFERRED. Whenever more than one candidate DCC of the same CELLTYPE satisfies this criterion, the DCC with the largest C_RES value shall be selected. However, a selector DCC with a lower C_RES can still be selected if its C_RES satisfies the following formula:

C_RES＞=MAX[MAX(C_RES ₁ ,C_RES ₂ ,…C_RES _N )-SERV_SS,O]

here:

SERV_SS is the offset value broadcast on BCCH.

To enable the MS to avoid "ping-pong" cell selection and reselection, the MS does not need to return to the cell it previously camped on within 10 seconds after reselection. termination

When such a procedure is invoked, the mobile station shall determine which of the subsequent PCH messages has been received, and respond as indicated:

paging

The mobile station shall send a paging response message, start WAFO_TMR to terminate the procedure, and then enter the waiting command state.

SSD update command

The mobile station shall send an inquiry command, initiate SSDU_TMR to terminate the procedure, and then enter the state where SSD update is in progress. SMS notification

The mobile station shall send a SPACH confirmation, initiate SMS_TMR, terminate the procedure, and then enter the SMS point-to-point ongoing state. unique query command

According to this unique challenge response procedure, the mobile station should send to a unique challenge order confirmation, terminate this procedure, and then enter the DCC camping state. message waiting

The mobile station shall send a SPACH acknowledgment, terminate the procedure, and then enter the DCC Camp state. parameter update

The mobile station shall send a SPACH acknowledgment, terminate the procedure, and then enter the DCC Camp state. direction retry

The mobile station shall send a SPACH acknowledgment, mark the current DCC as blocked for the period indicated in the direction retry message, terminate the procedure, and then enter the DCC camped state. leave

The mobile station shall send a SPACH acknowledgment, mark the current DCC as blocked for the period indicated in the leave message, terminate the procedure, and then enter the control channel scan and lock state. capability request

The mobile station shall send a Capability Report, terminate the procedure, and then enter the DCC Camp state. starting

When this procedure is invoked, the mobile station should wait for the F-BCCH Access Parameters message and check the Overload Control (OLC) information element included therein. The mobile station should proceed as follows: if the mobile station is blocked for access according to the OLC, or if the mobile station has not received the full set of F-BCCH messages on its current DCC, it should terminate the procedure, and then Enter the DCC reservation state. Otherwise, the mobile station should formally propose origination. If the BMI requires serial number information (S bit set to 1 on the Access Parameters message), the mobile station shall formally present the serial number message. If the BMI requires authorization information (AUTH bit set to 1 on the Access Parameters message), the mobile station should also formally present an authorization message under the authorization of the mobile origination procedure. The mobile station should then send an origination along with any other conforming messages to the requirements stated above. Start ORIG_TMR and enter the origination in progress state. SMS point-to-point

Layer 3 SMS point-to-point operations use three bidirectional messages: R_DATA, R_FATA ACCEPT and R_DATA REJECT. The R_DATA message shall be the message used to record the SMS application layer. In the context of the subsequent Layer 3 Short Message Service procedure, two classes are identified: MS-terminated SMS and MS-originated SMS. MS terminates SMS process

In the context of this third layer process, the MS terminates the delivery of SMS including the short message (i.e. the SMS DELIVER application message) and the SMS feature status report (i.e. the SMSFEAT CTRL STATUS application message) to the MS. Delivery of SMS over DCC

If the MS is in the "DCC Camped on" state, the BMI should page the MS and wait to receive a Page Response message from the MS. Once the BMI receives the paging message, the BMI sends the R-DATA message containing the SMS DELIVER application message to the mobile station by using the SPACH frame mode indicating SMS point-to-point and the L2 acknowledgment mode. The BMI then starts Timer X. Upon receipt of the R-DATA message, the mobile station shall provide a layer-3 acknowledgment to the BMI as follows: If the R-DATA message is acceptable to the MS, then the MS sends a respond with an R-DATA ACCEPT message with the same R-transaction identifier. If the R-DATA message is unacceptable to the MS, the MS shall generate the information element by sending the R-DATA REJECT message with the same R-Transaction Identifier and mandatory R-DATA as appearing in the R-DATA message. to respond. If the BMI timer X expires before receiving a Layer 3 acknowledgment, the BMI may resend R-DATA. The BMI should not resend R-DATA more than once. Delivery of SMS on DTC

If the MS has been assigned a DTC (e.g. included in the call), the BMI sends a message containing the SMS DELIVER APPLICATION to the mobile station by using the FACCH or SACCH with the transport traffic indicating L2 Acknowledgment Mode. The BMI then starts timer Y. Upon receipt of the R-DATA message, the mobile station shall provide a Layer 3 acknowledgment to the BMI as follows: If the R-DATA message is acceptable to the MS, it shall send a Identifier R-DATAACCEPT message to respond. If the R-DATA message is unacceptable to the MS, it shall do so by sending an R-DATA REJECT message with the same R-Transaction-Identifier and mandatory R-Generation Information Element as appearing in the R-DATA message. response. If the BMI timer Y expires before receiving the Layer 3 acknowledgment, the BMI may resend the R-DATA. The BMI shall not resend R-DATA more than once. MS originating SMS process

Within the context of this Layer 3 procedure, the MS-originated SMS includes: MS-originated short message (i.e., SMS SUBMIT application message), MS user acknowledgment (i.e., SMS USER ACK application message) and SMS feature control by the MS (ie SMS FEAT CTRL REQU application message). SMS originating from MS on DCC

When an MS in the "DCC Camp-On" state is requested by the MS SMS application layer to send a short message, the MS shall first check the SMS Access Flag broadcast on the BCCH, which indicates the maximum SMS message length, and the MS is authorized Sent on RACH. The MS shall refrain from sending the R-DATA message if the MSR-DATA message length is greater than the maximum SMS message length (in octets) authorized by the BMI.

If the MSR-DATA message length is less than the maximum SMS message length (in octets) authorized by the BMI, the MS can send an R-DATA message providing that registration rule to allow the MS to access the system.

The MS initiates the transmission of RDATA messages by sending an RDCC request to layer 2 with the original request. The MS starts timer X if the R-DATA message is sent. Upon receipt of the R-DATA message, the BMI shall provide a layer 3 acknowledgment to the MS as follows: If the R-DATA message is acceptable to the BMI, it shall send a The R-DATA ACCEPT message for the R-transaction identifier responds with an acknowledgment. If the R-DATA message is unacceptable to the MS, it shall de-acknowledge it by sending the R-DATA with the same R-Transaction Identifier as it appeared in the R-DATA message and with the mandatory R-Generate Information Element. REJECT message to respond. If the MS's timer Z expires before receiving the Layer 3 acknowledgment, the MS may resend the R-DATA. The MS shall not retransmit R-DATA more than once. MS start on DTC

If the MS has referred to a DTC (eg, involved in the call), the MS sends the R-DATA message to the BMI by using the FACCH or SACCH with Transport Service Indication L2 Acknowledgment mode. The MS then starts timer Z. Once the R-DATA message is received, the BMI will provide a Layer 3 acknowledgment to the MS as follows: If the R-DATA message can be received by the BMI, it will be identified by the sender in the R-DATA message with the same R-transaction as now R-DATA ACCEPT message to respond for confirmation. If R-DATA is not received by the MS it shall respond in the R-DATA message by sending an R-DATA REJECT message with the same R-Transaction Identification now and with the mandatory R-Cause information element for confirmation. If MS timer Z expires a previously received layer 3 acknowledgment, the MS may resend R-DATA. The MS shall not send R-DATA more than once. register (record)

When invoking this procedure, the mobile station should wait for the F-BCCH Access Parameters message and check the Overload Control (OLC) information element within it. The mobile station then proceeds as follows: If the mobile station is blocked for accessing according to the OLC, it should terminate the procedure and then enter the DCC camping state. If the mobile station is in its home SID area and RECH is blocked, it should terminate the procedure and then enter the DCC camped state. If the mobile station is not in its home SID area and REGR is blocked, it should terminate the procedure and then enter the DCC camped state. Otherwise, the mobile station should check the state table, as can be seen below, a registration (record) is required. These conditions are prioritized so that if more than one transaction is fulfilled, only one entry is sent.

If the power saving condition exists (i.e. the mobile station has just saved power) and the PDREG flag sent in the Registration Parameters message is enabled, the mobile station should send a Registration message with a power saving indication and then enter the inactive state (zero state). If the power-on condition exists (that is, the mobile station has just been powered on), and the PUREG flag sent in the registration parameter message is activated, the mobile station shall send a registration message with a power-on indication, start REGTMR, and then enter the registration progress state .

The SYREG flag sent in the Registration Parameters message is activated if the broadcasted SID value does not match the SID value stored in the semi-permanent memory. The mobile station shall send a REGISTER message with geographical indication, start REG_TMR, and then enter the REGISTRATION IN PROGRESS state.

If the broadcast RNUM value is not part of the RNUM table stored in semi-permanent memory and the LAREG flag sent in the Registration Parameters message is enabled, the mobile station shall send a Registration message with a geographic indication, start REG_TMR, and then enter the Registration in progress state.

If the current DCC is pre-identified as a neighboring registration (eg REG field in the neighboring table), the mobile station shall send a registration message with geographic indication, start REG_TMR, and then enter the registration in progress state.

If the FOREG flag sent in the Registration Parameters message is enabled, the mobile station shall send a Registration message with a mandatory indication, start REG_TMR, and then enter the Registration Progressing state.

If the periodic registration timer PER_COUNTER expires, the mobile station should send a registration message with a periodic indication, start REG_TMR, and enter the registration progress state.

If the REREG_TMR expires, the mobile station shall send a REGISTER message with the same indication as its previous registration attempt and enter the REGISTER IN PROGRESS state.

Otherwise, the mobile station shall invoke the periodic registration determination procedure. If registration is not required, the mobile station should terminate this procedure and return to the calling procedure. Registration update (record modification)

If the mobile station has received a "Periodic Registration (Record)" information element instead of a "REGID parameter" information element, it shall count its PER_COUNTER to REGPER*94 superframes. If the mobile station has received a "REG period" and a "REGID parameter" information element, it shall set (NXTREG=REGID+REGPER*94/REGID_PER) and store NXTREG in semi-permanent memory. The mobile station should update its semi-permanent memory with the currently broadcast SID value. After completing these updates, the mobile station should terminate this procedure and return to the calling procedure. Periodic registration (record) determination

If the mobile station receives a "REG Period" and a "REGID Parameter" information element, it shall check NXTREG to determine whether the REGID has a cycle through zero using the following algorithm: If NXTREG is greater than or equal to REGID+(REGPER*94/REHID_PER )+5, then NXTREG should be greater than 0 or NXTREG-2 ²⁰ instead, otherwise NXTREG will not be changed. If REGID is greater than or equal to NXTREG, the mobile station shall send a registration message with periodic indication, start REGTER, and then enter the registration progress state. Otherwise, the mobile station shall terminate this procedure and return to the calling procedure. Register (record) successfully

The mobile station should stop REG_TMR, invoke the registration update procedure, and proceed as follows: If a table of RNUM values is provided in the registration received message, the mobile station should set its RNUM table in semi-permanent memory according to the received table. The mobile station should only be required to store the first 50RNUM received in any given Registration Accept message.

The mobile station shall terminate this procedure and return to the DCC camped state. Registration (logging) failed

If the mobile station resends its registration up to a maximum of 5 times, it shall terminate the procedure and enter the DCC camp-on state. Otherwise, it shall store the rejection result, set the REREG_TMR timer for random times evenly distributed in the interval of 10 to 100 seconds, terminate the process and enter the DCC preempted state. Authorization (Authentication) Shared Secret Data (SSD)

SSD is a 128-bit format stored in the mobile station (semi-permanent memory) and is already available for the base station. As depicted in Figure 30, SSDs are assigned to two different subgroups. Each subgroup is used to support a different process. Specifically, SSD-A is used to support the authorization process, while SSD-B is used to support voice security and message security. SSDs can be produced according to the process specified in IS-54B of Annex A. Random Request Memory (RAND) RAND is a 32-bit value maintained at the mobile station. It is a value received on BCCH and is used in conjunction with SSD-A and other parameters to properly authorize mobile station origination, termination and registration (recording). Call history parameter (COUNT _sp )

The call history parameter is a modulo-64 count maintained at the mobile station. Update COUNT _sp mobile station registration authorization according to the received parameter update order message. When the information element AUTH on BCCH is set to 1, and the mobile station attempts to register, the following authorization procedures shall be performed: the mobile station Start the authorization algorithm (CAVE) shown in Figure 31; execute the CAVE process; put AUTHR equal to 18 bits of CAVE algorithm output; and send AUTHR with RANDC (the 8 most important bits of RAND) and COUNT _sp to this A base station that compares the received value for RANDC and the optional COUNT to an internally stored value associated with the received MIN1/ESE; computes AUTHR as described above (except using the internally stored SSD-A value); and The internally calculated AUTHR value is compared with the AUTHR value received from the mobile station.

If any of the comparisons made by the base station fail, the base station may consider the registration attempt unsuccessful and initiate a unique challenge response procedure or start the process of updating the SSD. unique query response process

The unique query response procedure is initiated by the BMI and can be performed via any combination of control and/or traffic channels. The base station generates a 24-bit random format called RANDU, sends the RANEU to the mobile station via a unique inquiry sequence message; initiates CAVE as shown in Figure 32; executes the CAVE algorithm; and sets AUTHU equal to the 18 bits output by the CAVE algorithm . The mobile station calculates the AUTHU as described above using the received RANDU and its internally stored values for keeping the input parameters, and sends the AUTHU via a unique challenge confirmation message to the base station. Based on the unique challenge sequence confirmation received from the mobile station, the base station compares the received value for AUTHU with its internally "generated/stored value. If the comparison fails, the base station may reject another access attempt by the mobile station, for An ongoing call goes off-hook or initiates the process of updating the SSD. Mobile-originated authorization

When the information element AUTH on the BCCH is set to 01, and the mobile station attempts to initiate a call, the following authorization procedures shall be performed:

CAVE as shown in Figure 33 is initiated at the mobile station; CAVE algorithm is executed; AUTHR is set equal to 18 bits output by CAVE algorithm; and AUTHR is sent to BMI together with RANDC (8 most significant bits of RAND and COUNT _sp . The The base station compares the value received for RANDC and the optional COUNT with the internally stored value associated with the received MIN1/ESN; calculates AUTHR as described above (except that it uses the internally stored SSD-A value); and compares the internally calculated The value of the AUTHR is compared with the AUTHR value received from the mobile station. If the comparison is successful at the base station, start the appropriate channel assignment procedure. Once a digital traffic channel is assigned, the base station will It is possible to send a parameter update order message to the mobile station. The mobile station confirms the parameter update order by sending the parameter update order confirmation. If any comparison of the base station fails, the base station can deny service, start a unique inquiry response process or start an update SSD process. The mobile station Terminated authorization

When the information element AUTH in the BCCH is set to 1 and "paging match" occurs, the following relevant authorization procedures should be performed: the mobile station starts the CAVE shown in Figure 34; executes the CAVE algorithm; sets AUTHR equal to the output of the CAVE algorithm 18 bits; and send AUTHR through message with RANDE (8 most significant bits of RAND) and COUNT _sp to the base station, the base station combines the optional COUNT for the value received by RANDC with the received MIN1/ESN Relative internally stored values are compared; AUTHR is calculated as described above (except using the internally stored SSD-A value); and the internally calculated AUTHR value is compared to the AUTHR value received from the mobile station. If the comparison is successful at the base station, the appropriate channel assignment process is started. Once a digital traffic channel is assigned, the base station may send a parameter update sequence message to the mobile station at the discretion of the system operator. The mobile station confirms receipt of the parameter update sequence according to the transmitted parameter update sequence. If any comparison by the base station fails, the base station can deny service, initiate a unique challenge response procedure or start the process of updating the SSD. SSD Update (Modified)

The updated SSD includes an application to start the CAVE with mobile station specific information, random data and the mobile station's A-key (key). The A-key is 64 bits long; is assigned and must be entered into each mobile station; is stored in the mobile station's permanently secure and identifying memory; and is known only to the mobile station and its associated HLR/AC. The latter feature of the A-key is intended to enhance the encrypted data of the mobile station, eliminating the need to transmit the A-key itself from system to system as the user roams. Therefore, SSD updates are only performed at the mobile station and its associated HLR/AC, not at the serving system. The serving system obtains a copy of the SSD computed via intersystem communication (see EIA/TIA IS-41) via the HLR/AC with the mobile station's HLR/AC.

The SSD updated by the mobile station is shown in Figure 35, the BMI sends an update command with the RANDSS field setting the same 56-bit random number as used in the HLR/AC calculation, sent on the SSD update command message to the mobile station. According to the SSD update command received, the mobile station initiates the CAVE shown in Figure 36; executes the CAVE algorithm; sets SSD-A_NEW equal to 64 most important bits output by the CAVE algorithm and sets SSD-B_NEW equal to 64 output by the CAVE algorithm Minimum significant bits; select a 32-bit random number RANDBS and send it to the BMI in the BMI's Query Command message; restart the CAVE shown in Figure 37; execute the CAVE algorithm; and set AUTHBS equal to the 18 bits output by the CAVE algorithm.

Upon receipt of the BMI query command, the BMI starts the CAVE shown in Figure 37, where RANDBS is set to the value received in the BMI query command; the CAVE algorithm is executed; AUTHBS is set equal to the 18 bits output by the CAVE algorithm; The AUTHBS included in the command confirmation message confirms the receipt of the BMI query command. Upon receipt of the BMI query command confirmation, the mobile station compares the received AUTHBS with its internally generated; acknowledges the receipt of the SSD update command. If the comparison at the mobile station is successful, the mobile station sets SSD-A and SSD-B as SSD-A_NEW and SSD-B_NEW respectively, and sends an SSD Update Command Confirmation message to SSD-UPDATE with SSD-UPDATE set to "1" The BMI and all other parameters of the messaging unit are set to appropriate values. If the result of the comparison at the mobile station fails. The mobile station discards SSD-A_NEW and SSD-B_NEW, and sends an SSD Update Command Confirmation message to the BMI with the SSD-UPDATE information element set to 0 and all other parameters set to appropriate values. If the SSD Update Confirmation indication received from the mobile station was successful, the BMI sets SSD-A and SSD-B to the values received from the HLR/AC (see EIA/TIA//IS-41). Layer 3 Message Group

The next section describes Layer 3 messages. The higher layer messages of SMS are described in the next section. In all the information shown in the table below, the information element in the top row of the table shall be the first element transmitted to the second layer. In this information element, the most significant bit (the leftmost bit of the table) is the first bit passed to the second layer. In the messages described below, the information elements are described in alphabetical order. F-BCCH message

F-BCCH records and carries broadcast information, which enables the mobile station to record and find the structure of DCC and other information of its own system. The set of Layer 3 messages specified for transmission on the F-BCCH is described as follows: Mandatory F-BCCH Message DCC Structure

This message should always be sent first. The format of the DCC structure message is as follows: information unit type Length (bits) Message Type Number of F-BCCH Number of E-BCCH Number of S-BCCH Number of Empty Slots Number of E-BCCH Change Notification Superframe Count Primary Superframe Indication DCC Slot Number of Frequency MAX_SUPPORTED_PFEPCH_DISPLACEMENT Additional DCC Frequency MMMMMMMMMMO 8234314122323-114 Total = 33-147

M = Mandatory

O = optional

Parameter type codes for optional information elements Parameter Type code Additional DCC frequency 0001

access parameters

The format of the access parameter message is as follows: information unit type Length (bits) Message Type AUTHSRANDMS_SCC_PWR Access Burst Size DVCCLOC Max Retries Max Busy Standby Max Repeat Max Stop Count SMS Message Length SOS and BSMCID Control Local MS Capabilities Roaming MS Capabilities Mesh Blocking MMMMMMMMMMMMMMMMM 8113241816312131111 Total = 85 Mesh Selection Parameters

The format of the cell selection parameter message is as follows: information unit type Length (bits) Message Type SS_SUFFRSS_ACC_MINSCANFREQDVCC Mesh Selection Control RESEL_OFFSET MMMMMMM 8554816 Total = 37 registration parameters

The registration parameter message format is as follows: information element type Length (bits) Message Type REGHREGRPUREGPDREGSYREGLAREGDEREGFOREGREG Period REGID Parameter MMMMMMMMOO 8111111111328 Total = 18-59

Parameter type codes for optional information elements Parameter Type code REF cycle REGID parameter 00010010 BMI identification The format of the BMI identification message is as follows: information unit type Length (bits) Message Type System ID Country Code IS-54+Procedure Version MMMM 814104 Total = 36 Optional F-BCCH Message Mobile Assisted Channel Assignment (MSCA)

This information can also be sent on the E-BCCH. This message is used to command the MS to perform radio measurements on certain channels. It contains information about channels that the MS has to measure and report for mobile assisted channel allocation. information element reference type Length (bits) Message type MACS_STATUSMACA_TYPEMACA table MMMO 82218-93 Total = 12-105

For optional message element parameter type code Parameter Type code MACA table 0001 E-BCCH message

The E-BCCH carries broadcast information which has a smaller critical time than the F-BCCH for mobile stations. For optional information a message type and length indication is included. Groups of messages within the E-BCCH may cover some superframes before a repetition occurs. However, it is not possible for a particular message to start and end within a different superframe. Filter information shall be used to terminate the last E-BCCH burst if required. Mandatory E-BCCH message adjacent cell

The format of the neighboring cell message is as follows: information element type Length (bits) Message Type SERV_SS Adjacent Mesh List (TDMA) (See Note) Adjacent Mesh List (Analog) (See Note) MMOO 849+48 ^* n9+13 ^* m Total = 12 - ^*

Note: Up to 24 cases can be transmitted (total number of TDMA and analog adjacent cells). Parameter Type code Adjacent Mesh Table (TDMA) Adjacent Mesh Table (Analog) 00010010 Optional E-BCCH message Mobile Assisted Channel Assignment (MACH)

See F-BCCH message section. emergency information broadcast

The emergency broadcast message format is as follows: information unit type Length (bits) message type file message data unit MM 8N ^* 8 Mmax=254 leave

This message is used to temporarily block all mobile stations using DCC. The blocking time is indicated in minutes from 0 to 255 minutes. A value of 0 indicates that the mesh is blocked. This message can also be sent on the SPACH. The format of the leave message is as follows: information element type Length (bits) message type min MM 88 Total = 16 SOS/BSMC Identification

This message is used to support SOC and/or BSMC specified commands. The format of this information is as follows: information element type Length (bits) Message TypeSOCBSMC MMM 888 Total = 24 S-BCCH message

There are two types of S-BCCH messages used for SMS broadcasts, SMS header messages and non-header messages. S-BCCH SMS frame header

This header information shall describe the structure of the SMS subchannel and is only provided in the first time slot of each SMS frame. The format of the SMS frame header is as follows: information unit type Length (bits) Message type Number of subchannels Number of subchannels Phase length of subchannel period Phase number of subchannel periods Number of SMS messages (N) SMS message ID (Note) L2 frame start (Note) MMMMMMMM 82266688 Total = 46

NOTE: N instances of these two units are sent adjacently.

S-BCCH SMS broadcast message content

This information content is used to deliver the actual SMS message to the MS. The format of SMS broadcast message content is as follows: information unit type Length (bits) Message Type SMS Message ID File Message Data Unit MMM 88N ^* 8 Nmax=253 Design of SPACH Information Analog Voice Channel

This message is used to assign the MS to an analog voice channel with corresponding parameters. The format of this message is as follows: information unit type Length (bits) Message type MEMSCCVMACCHHANPAGE MODE MMMMMM 8124118 Total = 34 Base Station Query Command Confirmation

This message responds to the base station interrogation command and contains the authorization algorithm output. The format of this information is as follows: information unit type Length (bits) Procedure Authentication and Message Type AUTHBS MM 818 Total = 26 capability request

This information is sent by the BMI to inquire about the capabilities of a particular mobile station. The format of this information is as follows: information unit type Length (bits) information type m 8 Digital Traffic Channel Design

This information is used to assign the MS to a digital traffic channel with corresponding parameters. The format of this information is as follows: information unit type Length (bits) INFO TYPE MEMDVCCPMMACCHANPAGE MODEATSDELTA TIMESB MMMMMMMMOM 818141184151 Total = 61 information waiting

This information is used to inform the mobile station that it has a message waiting. The format of this information is as follows: information unit type Length (bits) message type number of messages MM 86 Total = 14 paging

This message is used to notify the MS that an attempt to establish a mobile-terminated call is in progress. The format of this message is as follows: information unit type Length (bits) Message type PAGE MODE MO 812 Total = 8-20 parameter update

This message is used to inform the mobile station to update its internal call history parameters used in the authorization process. The format of this message is as follows: information unit type Length (bits) Number of message type requests MM 88 Total = 16 Point-to-point short message service R-data

This message is used to record the SMS application layer message for the MS to terminate the SMS. The content of the message is as follows: message unit type Length (bits) Message Type R-Transaction Identifier R-Data Unit Message Center Address MMMO(Note) 112-2412-12

Note: Including results, the message center of the original SMS has the address within the SMS including its terminating SMS.

Parameter type codes for optional information elements Parameter Type code message center address 0001 R-Data Acceptance

This message is used to acknowledge and accept R-data messages. The content of the message is as follows: information unit type Length (bits) Message Type R - Transaction Identifier MM 88 Total = 16 R-Data Rejection

This message is used to acknowledge and reject R-Data messages. The content of the message is as follows: information unit type Length (bits) Message Type R-Transaction Recognizer R-Reason MMM 888 Total = 24 RACH confirmed

The format of the RACH confirmation message is as follows: information unit type Length (bits) Message Type Confirmation Message MM 88 Total = 16 registration accepted

The format of the registration acceptance message is as follows: information unit type Length (bits) Message type RNUM MO 810-640 Total=8-648 Parameter type code for optional message element Parameter Type code RNUM 0001 registration refusal

The format of the registration rejection message is as follows: information unit type Length (bits) message type reason MM 84 Total = 12 SSD update command

This message causes the mobile station to execute the authorization algorithm. The SSD update command message is as follows: information unit type Length (bits) Message TypeRANSSD MM 856 Total = 64 SOC/BSMC Identification

This message is used in support of SOC and/or BSMC specified signaling. It is sent by the BMI in response to a mobile station's SOC and BSMC ID request message. The format of the SOC/BSMC identification message is as follows: information unit type Length (bits) Message TypeSOCBSMC MMM 888 Total = 24 SOC/BSMS messaging

This message is used to carry the signaling information specified by the SOC/BSMC. The format of the SOC/BSMC messaging message is as follows: information unit type Length (bits) Message Type User Control (Note 1) MM 88 ^* n Total=8+(8 ^* n)

NOTE 1: May be sent (254) as many circumstances as L2 procedures allow. unique query command

This message causes the mobile station to execute the authorization algorithm. The only query command message is as follows: information unit type Length (bits) Message type RANDU MM 824 Total = 32 leave

This message is used to block the mobile station from communicating with the DCC used. The blocking time is expressed in minutes, from 0 to 255 minutes. A value of 0 indicates that the mesh is not blocked. The format of the leave message is as follows: information unit type Length (bits) message type min MM 88 Total = 16 point to retry

This message is used to force the mobile station to reject the DCC and select a channel from its neighbor list. The format of the pointer to retry message is as follows: information unit type Length (bits) message type min MM 88 Total = 16 time and date

The format of the time and date message is as follows: information unit type Length (bits) Message type Julian date Seconds of day MMM 81617 Total = 41 RACH message

For RACH the following message is specified. The 8-bit message type is used to distinguish between messages. authorized

The format of the authorization message is as follows: information unit type Length (bits) Message TypeCOUNTRANDCAUTNR MMMM 86818 Total = 40 base station inquiry command

The format of the base station inquiry command message is as follows: information unit type Length (bits) Message Type RANDBS MM 832 Total = 40

The following messages may be attached to the Page Response message: Sequence Number Message - if the S bit is set. Capability report

The content format of the capability report message is as follows: information unit type Length (bits) Message Type MPCISCM Software Lifetime Firmware Lifetime Model ESN MMMMMMM 83566432 64 MACA report

The format of the MACA report message is as follows: information unit type Length (bits) Message TypeWERBERRSS MMMO 83310 twenty four origination (establishment) information unit type Length (bits) Message Type MPCIVP Call Mode Dial Digit PAGE_MODE MMMMMO 83136412 Total = 79-91 The following messages can be appended to an originating message:

Sequence Number Message - If the S bit is set.

Authorization message - if the AUTH bit is set. paging response

The paging response message format is as follows: information unit type Length (bits) Message type MPCIVP call mode PAGE_MODE MMMMO 8121312 Total = 14-26

The following messages can be appended to the Page Response message:

Sequence Number Message - If the S bit is set.

Authorization message - if the AUTH bit is set. Point-to-point short message service

R-data

This message is used to record SMS application messages for MS and MS user acknowledgment of initiated SMS. The content of the message is as follows: information unit type Length (bits) Message Type R-Transaction Recognizer R-Data Unit Message Center Address MMMO (Note 1) 112-2412-12

Note 1: Including results, the destination address is different with a different center in the distribution of MS subscripts. R-DATA accepted

This message is used to acknowledge and accept R-DATA messages. The content of the message is as follows: information unit type Length (bits) Message Type R - Transaction Recognizer MM 88 Total = 16 R-DATA rejected

This message is used to acknowledge and reject R-DATA messages. The content of the message is as follows: information unit type Length (bits) Message Type R-Transaction Recognizer Reason MMM 888 Total = 24 register (record)

The format of the registration (record) message is as follows: information unit type Length (bits) Message Type Registration Type SCMMPCI MMMM 8343 Total = 18

The following messages can be appended to the Page Response message:

Sequence number message - if the S bit is set;

Authorization message - if the AUTH bit is set,

Capability Report Message - Access Parameter message on F-BCCH if Registration Type equals Power On or Geographic and if Home/Roaming MS Capability flag is enabled. serial number

The format of the serial number message is as follows: information unit type Length (bits) Message TypeESN MM 832 Total = 40 SOC/BSMC identification request

This message is used in support of SOC and BSMC specified signaling. If flag authorization is requested by the BCCH SOC/BSMC, the mobile station may send a SOC/BSMC Request message to request SOC and BSMC identification. information unit type Length (bits) message type m 8 SOC/BSMC messaging

This message is used to carry the information specified by the SOC/BSMC. The format of the SOC/BSMC messaging message is as follows: information unit type Length (bits) Message Type User Control (Note 1) MM 88 ^* n Total=8+(8 ^* n)

Note 1: As in many cases, an example L2 procedure may be allowed to be sent (254). SPACH confirmed

The format of the SPACH confirmation message is as follows: information unit type Length (bits) Message Type Confirmation Message MM 88 Total = 16 SSD update command confirmed

The format of the SSD update command confirmation message is as follows: information unit type Length (bits) Message Type SSD Update Status MM 82 Total = 10 time and date

The format of the time and date message is as follows: information unit type Length (bits) Message Type Julian Date Seconds of Day MMM 81617 Total = 41 The only query command confirms

The format of the unique query command confirmation message is as follows: information unit type Length (bits) Message Type AUTHU MM 818 Total = 26

The following information can be appended to the unique query order confirmation message:

Sequence Number Message - If the S bit is set. Information unit description

The following encoding rules apply to all information element declarations:

A cell of type "marker" will have the value:

0=disable(disconnect, false)

1=Enable(On, True)

In the BCCH change flag of SPACH, some BCCH fields do not trigger a transition, those fields are called "NC" (non-critical).

A "transition" type of unit is a modulo-1 counter that indicates a change in the current state.

Unless otherwise noted, all stated lengths are in BIT, unless otherwise noted.

Channel numbers will be coded as IS-54B unless otherwise noted. access character group size

This field informs the mobile station of the burst size used on the RACH according to the following table: value Function 01 Normal length charset used on RACH Shorted length charset used on RACH Additional DCC frequency

This optional field contains information about additional DCC frequencies in this cell and the relationship to the current DCC. field length(value) Parameter type Additional DCC frequency number (Note 1) Position of current DCC frequency in the table DCC channel information (Note 2) DCC frequency The frequency, DCC slot number 4(0001)33112

Additional DCC frequency number: The additional DCC frequency number is provided by the cell.

In the table, the position of this DCC: at this point the current DCC frequency is inserted into the DCC channel information table for DCC selection.

DCC Channel Information - This field contains two subfields. When determining the DCC selection, the DCC frequency must be considered for the additional DCC provided by this cell. "DCC slot number for this frequency" is described in this section.

Notice:

1. All additional DCCs provided in this optional information element list must be the same DCC logic set in the same sequence of all other DCC optional information element lists.

2. In the number in the additional DCC frequency field, the number of instances sends the same value. ART

This field defines the assigned time slot value Function 000000010010100110101011110011011110 Full rate digital traffic channel on time slot 1,4, full rate digital traffic channel on time slot 2,5, full rate digital traffic channel on time slot 1,4, full rate digital traffic channel on time slot 1, half rate digital traffic channel On time slot 2, the half-rate digital traffic channel is on time slot 3, the half-rate digital traffic channel is on time slot 4, the half-rate digital traffic channel is on time slot 5, and the half-rate digital traffic channel is on time slot 6, half rate digital traffic channel AUTH

The authentication flag indicates whether the mobile station sends an authentication message with a recorded, originating, or call response message sent on the RACH. AUTHBS

This information element contains the output of the authentication program. AUTHR

This is the output response of the authentication algorithm for origination, logging and termination. AUTHU

This is the output response of the authentication algorithm for the unique query command. BSMS

This is the base station manufacturer's code. call method

The most preferred calling method for the next Voice/Traffic channel designation according to the table below: value Function 000001010011100101110111 Acceptable Analog Voice Channels Unacceptable Analog Voice Channels Acceptable Full Rate Digital Traffic Channels Unacceptable Full Rate Digital Traffic Channels Acceptable Half Rate Digital Traffic Channels Unacceptable Half Rate Digital Traffic Channels Reserved Reserved Cause

This field indicates the case for the mobile station to reject the record. coding reason 00000001 Unknown MSID Invalid C-Number All other encodings are preserved Mesh blocking

This flag is used to indicate the currently blocked mesh. Mesh selection control

This flag is used so that a mobile station performing cell selection (primary selection) cannot select the current cell. Mesh type

Preferred type of mesh according to the table below: value Function 00011011 Mesh type of REGULAR Mesh type of PREFERRED Mesh type of non-PREFERRED reserved CHAN

This is the C channel number as specified in IS-54B. confirmation message

The Acknowledged Message field is a repetition of the MessageType field of an acknowledged message. According to the table below, the following messages are valid acknowledgment messages: value convention function RACH message Waiting for RACH parameter update RACH Restore RACH Retry RACH directly Remove RACH SMS notify SPACHSPACH count

Se IS-54B is used for this parameter. country code

This field indicates the country code of the serving system. field Length (bits) Country Code (CC) 10

This CC is the same as the CC of the mobile country code stipulated in CCITT recommendation E.212. The CC value is specified in Appendix A of E.212. Subsequent values are extracted from E.212 and are for illustration only. If other CC values are required, refer to Appendix A of E.212 for the complete table of CC values. code (decimal) nation 302310311312313314315316334 Canada USA USA USA USA USA USA USA Mexico

The 3 decimal numbers of the CC are represented as the corresponding decimal numbers (0<=didjdk<=999) encoded in 10 binary bits using the usual decimal to binary conversion (0 to 999). traditional control

In use, binary data is specified according to the current SOC/BSMC protocol. time delay

Time in seconds. Delta (DELTA) time

This parameter represents the difference in DTC and DCC timing of the mobile station in terms of slots and symbols. field Length (bits) number of digits of the parameter type slots 4(0001)38 DEREG

This flag indicates whether logging is enabled or disabled. Dial digits

The dialed digits of the MS are used for origination. DVCC

Digital check color codes are used in a manner consistent with IS-54B. E-BCCH Change Notice

The transition bit indicates a change of E-BCCH data start with the current superframe. If switching has occurred, all mobile stations read the E-BCCH of the current superframe and all subsequent superframes until the entire period of the E-BCCH is read. ESN

Identify the electronic serial number of the MS. Firmware lifetime

The firmware lifetime is determined by the mobile station manufacturer. FOREG

This flag indicates whether forced logging is enabled or disabled. HL_FREQ

If HL_FREQ is set to high, the MS shall proceed to perform frequency measurements according to the rules in the SCANFREQ information element. If set to low, the frequency will be measured with half the frequency required by the rules in the SCANFREQ information element. value Function 01 low high hyperframe counter

The counter is used to identify the hyperframe that is currently being broadcast. A hyperframe consists of two superframes. This counter starts from 0. Julian date

Sequence data counters start from January 1, 1900. Reset to 1 on January 1, 2000. L2 frame start

This variable represents the number of time slots from the start of the SMS subchannel period to the start of the SMS message. The message may not be at the beginning of the SMS slot indication, but may be included in the end/begin burst for the start of the message transmission. LAREG

When the current cell's record number is not part of the mobile station's record number table, the location area of the record flag indicates whether the mobile station is a regional record. MAC

This field indicates the power level used on the assigned digital traffic channel. Coding is according to IS-54B Table 2.1.2-1. MACA list

This optional field indicates the mobile channel used for the mobile auxiliary channel configuration that has to be measured. field Length (bits) Parameter type MACA channel (K) number channel number 4(0010)3K ^* 11 MAX_SUPPORTED_PFC

According to the following table, the maximum call frame level that the DCC can support: value Function 00011011 PF1 is the maximum supported call frame level PF2 is the maximum supported call frame level PF3 is the maximum supported call frame level PF4 is the maximum supported call frame level Maximum Busy Reserve

A maximum number of times, the mobile station performs the following steps: generates a random delay period, waits until the termination of the period, and reads the B/R/I flags that have been set to non-idle. value Function 01 1 random delay period 10 random delay period maximum repetition

The maximum number of consecutive repeats of an individual RACH burst before it is considered to test for a failure. max retries

The maximum number of RACH transmissions that may be allowed before attempting to transmit a message (any burst of single or multi-burst RACH) as a failure. Maximum Stop Counter

Maximum number of times, the mobile station performs the following steps: transmits a burst in RACH, checks the SCF that has been set not busy (R/N=N or B/I/R=R or I), generates a random delay period, waits No more bursts are transmitted on the RACH until the period expires. MEM

This flag indicates whether the mobile station will use message encryption on the assigned traffic channel. Information Center Address

The purpose of the message center address is to identify the message center address for the message being delivered. The maximum length of this information element is limited to 12 octets. bit octet 8 7 6 5 4 3 2 1 Length of message center address content (in octets) Information center address 0 0 01 parameter code 1 0 reserved type of number Numbering Plan Identification 2 second number 1st digit 3 ··· ··· ··· [(2×N)-4]th number or padding number (odd number) Number [(2×N)-5] N

type of number (octet 2) (see note 1)

bits

765

001 international number (see note 2)

010 domestic number (see note 2,4,5)

011 Network-dedicated number (see note 3)

110 abbreviated number

111 Extended reservation

All other values will be preserved

Notice:

1. For the definition of "international and domestic numbers", see CCITT recommendation I.330.

2. Do not include prefixes or escape numbers.

3. The number type "network-private number" is used to represent a service number of a managed or private service network.

4. For calls between the United States and other countries in world zone 1 (see CCITT Recommendation E.163 Assignment of Country Codes). Here, the numbering plan identification is "ISDN/Telephone Numbering Plan", and the "Number Type" is coded to "National Number".

5. For numbers containing service access codes (eg, "700", "800", "900"), the "Number Type" is encoded as "National Number".

Numbering Plan Identification (Octet 2)

Numbering Plan (for Number Type = 001 and 010)

bits

4321

0000 unknown

0001 ISDN/telephone numbering plan (CCITT recommends E.164 and E.163)

1001 private numbering plan

1111 reserved extension

All other values are preserved

number (octet 3, etc.)

This field is coded TBCD as follows: binary value number 0000000100100011010001010110011110001001101010111100 Filling number 1234567890*# All other values are reserved message type

This 8-bit information element identifies the function of the message being sent. Message types are encoded as follows: F-BCCH message encoding (binary-six) DCC structure access parameter BMI identification 0010 0001-210010 0010-220010 0011-23 Cell Selection Parameters Mobile Auxiliary Channel Configuration F-BCCH Information Override Record Parameters 0010 0100-240010 0101-250010 1001-290110 1000-68

F-BCCH message encoding (binary-six) Neighboring Cells Urgently Use Information Broadcasting to Remove 0001 0000-100001 0001-110110 0000-60

SPACH message encoding (binary-six) Call digital service channel flag Analog voice channel flag record receiving record cancel SSD update command base station query command confirm unique query command point-point short message service R-DATA point-point short message service R-DATA receiving point-point short message service R- DATA cancel message wait for SOC/BSMC message to send RACH confirmation parameter update SOC/BSMC identification 0000 0000-000111 0000-700111 0001-711100 0011-C31100 0010-C2001-090000 1000-080000 011-070000-060001 0010-120001-1300-280001 0100-15111010101010101010101010101010101010110 0010110 0010110 0010110 0010110 0010110 0010110 001010-A2000 Restore and try again to remove 0001 1000-180110 0001-610110 0000-60

RACH message encoding (binary-six) Call Response Origination (Preparation) Record SOC/BSMC/Identification Request SSD Update Command Confirm Base Station Inquiry Instruction Unique Inquiry Instruction Confirmation Point-to-Point Short Message Service R-DATA Point-to-Point Short Message Service R-DATA Receiving Point-to-Point Short Message Service R-DATA cancel SOC/BSMC message send parameter update confirmation SPACH confirmation MACA report 0010-020000 0100-041100 0001-C10001 0111-170000 0101-050000 0011-030000 0001-010000-060001 0010-120001 0011-130001 1001-1900-340000-200010-26 0110-26

S-BCCH message encoding (binary-six) broadcast information message 0010 0111-27 point

This field indicates the time in minutes. model

This field indicates the model of the mobile station. MPCI

The mobility protocol capacity indicator is used to inform the BS of its processing capacity according to the following table: value Function 000001010011100101110111 Indicates an EIA-553 or IS-54-A mobile station Indicates an EIA/TIA IS-54-B dual-mode mobile station Indicates an IS-7X DCC mobile station Indicates an IS-54+ mobile station (DCC and IS-54C) Reserved Reserved Reserved

Notice:

An IS-54 mobile station is a mobile station conforming to the protocol proposed in this specification. MS_ACC_PWR

The mobile station access power level determines the maximum output power that the MS can use to initially access the network. MS_ACC_PWR coding Value (decibel dBm) 000000010010001101000101 363228242016 01100111100010011010 12840-4 All other values are reserved Adjacent Mesh Table (Analog)

This optional information element indicates the mobile station's analog channel to be used for cell reselection measurements. field Length (bits) Parameter type simulates the number (=m) CHANPCI of neighboring cells 4(0010)511 ^* m2 ^* m Total=9+13 ^* m

PCI represents the protocol capacity for simulating adjacent meshes. It is prescribed as follows: PCI coding value 00011011 EIA553IS-54B Reserved Reserved Adjacent Mesh Table (TDMA)

This optional information element indicates that the TEMA channel is used for cell reselection. field Length (bits) Parameter Type TDMA Neighboring Number (=n) CHANDVCCRESEL_OFFSETSS_SUFFDELAYHL_FREQCELLTYPE Network Type MS_ACC_PWRRSS_ACC_MIN 4(0001)511 ^* n8 ^* n6 ^* n5 ^* n4 ^* n1 ^* n2 ^* n2 ^* n4 ^* n5 ^* n Total = 9+48 ^* n

Notice:

Unrestricted fields in this section are restricted under the corresponding IE. Delay coding value 00000001*11101111 0 seconds 20 seconds 280 seconds reserved Simulate the number of neighboring cells

The numbers of adjacent cells are of analog type. The number of DCC slots, the frequency

According to the table below, the slot number is dedicated to the DCC on that frequency. value Function 00011011 Half rate DCC on time slot 1 Full rate DCC on time slot 1,4 Double full rate DCC on time slot 1,4 and 2,5 (note 1) on time slot 1,4; 2, 5; and triple full rate DCC on 3,6 (note 1)

Note 1:

Timeslots 1 and 1,4 must be primary DCCs, while slots 2,5 and 3,6 must be secondary DCCs and on the same frequency as the primary (DCC). E-BCCH number

Contiguous number per superframe dedicated to E-BCCH slots (value in this field plus 1). F-BCCH number

Contiguous number per superframe dedicated to F-BCCH slots (value in this field plus 1). message number

This field indicates the number the message is waiting for. S_BCCH number

Number of contiguous S-BCCH slots per superframe. number of skipped slots

A number per superframe dedicated to skipped slots. See PCH subchannel selection. SMS message number

In the SMS frame, a variable indicates the number of the broadcast SMS message (the value in this field is incremented by 1). subchannel number

A variable indicating the SMS subchannel number used by this DCC (the value in this field is incremented by 1). TDMA adjacent cell number

Number of adjacent cells of TDMA type. OLC

The Overload Class (OLC) determines whether a mobile can generate an origination on the RACH. The mobile station must check the value of the bit table corresponding to its internally stored access overload level assignment. If the identification OLC bit is enabled, the movement can be continued with an initial access. Otherwise, the mobile cannot initiate access.

The recommended overload control bit assignments are: value Function 00000000000000000000000000000010000000000000010000000000000010000000000000010000000000000010000000000000010000000000000010000000000000010000000000000010000000000000010000000000 Normal users of evenly distributed assignments Normal users of evenly distributed assignments Normal users of evenly distributed assignments Normal users of evenly distributed assignments Normal users of evenly distributed assignments Normal users of evenly distributed assignments Normal users of uniform distribution Normal users for distributed assignments Normal users for evenly distributed assignments Normal users for evenly distributed assignments Test moves 00001000000000000001000000000000001000000000000001000000000000001000000000000000 Reserve Move Reserve Reserve Reserve Reserve

For more information, refer to EIA Radio Communications Systems Bulletin No. 16 (March 1985), "Assignment of Access Overload Levels in Cellular Radio Services". call method

This information element specifies the type of mobile channel assigned to it according to the following table: Value Function DCH transfer

The maximum number of times an expected paging message can be diverted to other downlink channels. PDREG

This flag indicates whether the region record is on or off. (according to IS-54B). cycle record

This optional field indicates the period record used, and also contains the specified period in minutes. field Length (bits) The record period of the parameter type in minutes 4(0001)9 Phase length of the subchannel period

A variable to represent the phase number of the subchannel period equal to the number of one periodic SMS frame (value in this field plus 1)

A variable to represent the SMS frame in the cycle that is currently being broadcast. PM

This flag determines whether the mobile station will use the privacy mode on the originally assigned digital traffic channel. primary superframe indicator

The bit flip-flop indicates whether the current superframe being broadcast is the primary superframe or the secondary superframe in the hyperframe. value Function 01 major minor PURFG

This flag indicates whether level-up recording is on or off (according to IS-54B). RAND

A random number stored by the mobile for use in the selection authentication process. RANDBS

Random number generated by MS used in SSD update program. RANDC

A number used to validate the last RAND received by the MS. RANDSSD

Random number generated by MS used in SSD update program. RANDU

A nonce generated by the BS in the unique query updater used. R_Cause (reason)

This Information Element (IE) is 1 octet long and is an indicator in the R-DATA Reject message.

The following table provides the R_Cause IE layout and cause value description: bit octet 8 7 6 5 4 3 2 1 0, standby reason 1

Reason direction Coding decimal binary Unassigned (unspecified) number call prohibited Short message conversion canceled Storage capacity exceeds specified Cannot work Unidentified user equipment abandoned message, unspecified indicating information unit error B→MSB→MSB→MSMS→BB→MSB→MSB→MSB→MSB→MSB→MSB→MSB→MSB→MSB→MSB→MS Both have 1102122272829303841424769819596 0000001000101000101010010110001101100111000011101001111001000100101001010101001011111000101101000110111111100000 Message type does not exist or is not implemented Message or type of message that does not exist or is not implemented is not compatible with the short message conversion state Information element does not exist or is not implemented Invalid information element content is incompatible with the short message conversion state Message protocol error, unspecified cooperate with each other, unspecified (both) B→MSB→MS both have (both) both have both have both have B→MS 979899100101111127 110000111000101100011110010011001011101111111111 All other values are reserved R-data unit

The R-data unit IE contains higher layer protocol data units. This IE is an indicator in the R-DATA message. The IE has a variable length of up to 241 octets, the first octet is sent by the length indicator. bit octet 8 7 6 5 4 3 2 1 length indicator (octet) higher layer protocol identifier higher layer protocol data unit higher layer protocol data unit 123n

The higher layer protocol identification field is encoded as follows:

[(Paste P.131 1.)]REGH

This flag indicates whether the home mobile station will record. REG_HYST

If the selected DCC from the neighbor list has been checked and considered to be the best choice for cell reselection and the selected DCC requires logging, then the MS moves to the new cell only after a signal strength difference of REG_HYST dB is obtained . value Function 000001010011100101110111 0dB (decibel) 2dB (decibel) 4dB6dB8dB10dB12dB∞dB REGID parameter

This optional field contains information on the current REGID value and the time between stepping REGID. The latter value is expressed in superframes. field Length (bits) Parameter type REGIDREGID_PER 4(0010)204 record type

Movements used to represent record types are made according to the following table: value Function 000001010011100101110111 Reservation of Forced Cycles for Power Down Power Up Regions Reservation Reservation REG cycle

This optional field indicates the use period record, also contains the period specified in 94 superframe units (60.16 seconds) field Length (bits) Parameter type REGPER: recording period in units of 94 superframes 4(0001)9 REGR

This flag indicates whether the inter-area mobile station will log or not. request number

See IS-54B. reselect offset

The reselection offset value is used in the optimal increase/decrease of the newly selected cell taking into account cell reselection. reselect offset Coding Value (dB) 000000000001111110111111 02124126 RNUM

This 10-bit field contains the record number used in identifying the specific Mobile Virtually Moved Location Area (VMLA). field Length (bits) Number RNUM of parameter type RNUM (note 1) 4(0001)610

Note 1: It can be sent when it reaches 63. RSS_ACC_MIN This information element is used for cell (re)selection processing. This is the minimum received signal strength required to access the cell. RSS_ACC_MIN Coding Value (dBm) 00000000011111011111 -113-111-53-51 R - transaction identifier

The R-transaction identifier is used to associate an R-DATA ACC EPT or an R-DATA REJECT message with an acknowledged R-DATA message. S

The sequence number flag indicates whether the mobile station sends the ESN message with the record, origination, call response, unique inquiry order acknowledgment, or base station inquiry order message on RACH. SB

This flag determines whether the mobile station will use the original shortened burst on the assigned digital traffic channel. SCAN FREQ

The minimum number of absences required for signal strength measurements per superframe for DCCs selected in the neighbor list. SCC

This field identifies the SAT color code to be used on the assigned analogue voice channel. bit pattern SAT frequency 00011011 5970Hz6000Hz6030Hz reserved SCN

The station class mark indicates the power class, transmission capacity and frequency bandwidth of the MS. days in seconds

Serial time-of-day counter in seconds, where 12:00:00 A.M.=0SERV_SS

This information element is used in the cell reselection process. The signal strength is used to define a threshold beyond which a neighboring cell will enable the relevant service of the cell selection process. coding Value (dB) 00000001"11101111 SMS message ID

A variable is used to identify the unique SMS message. SMS message length

Maximum allowable length (octets) of L3 short messages sent on RACH according to the table below. value Function 000001010011100101110111 31 octets for MS-initial RACH SMS that are not allowed Maximum 63 octets for MS-initial RACH SMS Maximum 127 octets for MS-initial RACH SMS Reservation Reservation is limited only by the L2 format SOC & BSMC ID Control

This flag indicates whether MS can request BS SOC & BSMC ID. software lifetime

This flag indicates the software lifetime for mobile. SSD update status

Indicates the completion of an SSF update command, or the cause of a failure, according to the following table: value Function 00011011 SSD update succeeded by child AUTHBS uncoordinated SSD update invalidated due to suspend SSD update failure reserved SS_SUFF

The minimum signal strength considered sufficient for the newly selected DCC to be considered for cell reselection. SS_SUFF coding value 0000000001"1111011111 -113dBm-111dBm"-53dBm-51dBm subchannel number

A variable to identify the subchannel that is currently broadcasting. SYREG

When a move enters a new system-recognized area, the system base record flag indicates whether the move has regional records. text message data unit

The Text Message Data Unit is a variable length IE containing the message to be broadcast. This IE allows only one case per message. The following table provides the text message data unit description. bit octet 8 7 6 5 4 3 2 1 Length indicator (octet) short message character 1 (IA5) "short message character 253 (IA5) 121+LL minimum=0L maximum=253 VMAC

This field indicates the power level for the assigned analogue voice channel. Coding is according to IS-54B Table 2.1.2-1. VP MEM

The voice privacy, message encryption mode bits are used to request a most preferred calling method. SMS High Layer Operation

The higher layer protocol data unit field in the R-data unit is used to carry out SMS application layer messages. message settings

SMS application messages are restricted in this area. These messages are transmitted on the air interface via layer 3 R-DATA messages, or rather in R-data unit information elements.

For each SMS application message, two tables are provided: the first table provides the information elements containing each message, and the second table provides the message layout for the indicated IE.

The maximum length of an SMS application layer message shall not exceed 239 octets to accommodate the R-Data Unit IE.

SMS application layer messages are as follows. SMS delivery

This SMS application layer message is used to support MS delivery of terminated SMS from network to MS.

The following table provides the message content and the message layout used to indicate IE. information unit direction type length Message Type Indicator (MTI) Reply Optional (RO) Urgent Indicator (UI) Privacy Indicator (PI) Message Reference User Data Unit User Originating Address User Originating Subaddress Message Center Timestamp B→MSB→MSB→MSB→MSB→MSB→MSB→MSB→MSB→MS MMMMMMO(note 1)O(note 2)O(note 3) 3 bits 1 bit 2 bits 2 bits 6 or 13 bits 2- ^* octet 2- ^* octet 2- ^* octet 8 octet NOTE 1: The originating user may be included or a message center identifying the originating user may be included. NOTE 2: Include the subaddress to which the originating user indicated it. NOTE 3: The message center may include a time stamp at which time the message is received by the message center.

bit octet 8 7 6 5 4 3 2 1 0, standby UI P.I. MTI 1 0/1 extension Message Base (MSB) RO 2 (Note 1) 1 extension Message Base (LSB) 2a (note 1) user data unit 3 user data unit etc. NOTE 1: If the message reference value exceeds 63, bit 8 of octet 2 is set to 0, and octet 2a is present. If the message reference value is less than 64, octet 2a is absent and bit 8 of octet 2 is set to one. SMS SUBMIT

This SMS application layer message is intended for MSs that support originating SMS.

The following table provides the message content and message layout. information unit refer to direction type length Message Type Indicator (MTI) Urgency Indicator (UI) Privacy Indicator (PI) Message Reference Sending and Receiving (DR) User Destination Address User Data Unit User Destination Subaddress Valid Period Delay Sending Time MS→BB→MSB→MSMS→BMS→BMS→BMS→BMS→BMS→BMS→B MMMMMMMO(note 2)O(note 2)O(note 3) 3 bits 2 bits 2 bits 6 or 13 bits 1 bits 2- ^* octet 1- ^* octet 2- ^* octet 2 or 8 octet 2 or 8 octet Note 1: Included in events specifying that the recipient has a sub-address. Note 2: Included to indicate the validity of the MS providing the short message to the information center. Note 3: When sending by the MS providing the short message, include the time indicating the information center. bit octet 8 7 6 5 4 3 2 1 0 spare DR UI 0 spare MTI 1 0/1 extension Message Base (MSB) spare 2 (Note 1) 1 extension Message Base (LSB) 2a (note 1) user data unit 3 user data unit etc. NOTE 1: If the message reference value exceeds 63, bit 8 of the octet is set to 0, and octet 2a is present. If the message reference value is less than 64, then octet 2a is absent and bit 8 of octet 2 is set to one. SMS USER ACK

This SMS Application message is sent by the MS user in response to the SMS DELIVER message, with an answerable Select IE indicating that user confirmation is required.

The following table provides the message content and the message layout used to indicate IE. information unit refer to direction type length Message Type Indicator (MTI) Response Code (RC) Message Reference User Data Unit User Destination Address User Destination Subaddress MS→BMS→BMS→BMS→BMS→BMS→B MMMMO(note 1)O(note 2 3 bits 4 bits 6 or 13 bits 1- ^* 2- ^* octets 2- ^* octets Note 1: Include whether the user's originating address is included in the SMS DELIVER message of "User Confirmation". Note 2: If the user originating subaddress is included in the "User Confirmation" of the SMS DELIVER In the message, it can be included. bit octet 8 7 6 5 4 3 2 1 response code 0 spare MTI 1 0/1 extension Message Base (MSB) 0 spare 2 (Note 1) 1 extension Message Base (LSB) 2a (Note 1) user data unit 3 user data unit etc. NOTE 1: If the message reference value exceeds 63, bit 8 of octet 2 is set to 0, and octet 2a is present. If the message reference value is less than 64, octet 2a is absent and bit 8 of octet 2 is set to one. SMS FEAT_CTRL_REOU

This SMS application layer message is used to allow the MS user to control the controlled SMS application features. The Feature Parameter IE and Feature Status IE are related to the Feature ID IE. information unit refer to direction type length Number features set by the Message Type Indicator (MTI) feature MS→BMS→BMS→B MMM (note 1) 3 bits 3 bits 2-* octets Note 1: The number of the feature setting indicates the number of the feature setting IE case. bit octet 8 7 6 5 4 3 2 1 number of feature settings 0 0 spare MTI 1 feature set 1, octet 1 2 feature set 1, octet 2 3 SMS FEAT_CTRL_STATUS

This SMS application layer message is used to allow the MS to receive information about the status of its SMS application features. information unit direction type length Number Feature Set for Message Type Indicator (MTI) Feature Set B→MSB→MSB→MS MMM (note 1) 3 bits 3 bits 2-* octets Note 1: The number of the feature setting indicates the number of the feature setting IE case.

bit octet 8 7 6 5 4 3 2 1 number of feature settings 0 0 spare MTI 1 feature set 1, octet 1 2 feature set 1, octet 2 3 Information unit description

The following table provides a complete list of IEs specified on the SMS application layer. information unit information unit identifier MS/E Bbit 4321 B/E MS bit 4321 Message Type Indicator Delay Send Time Send Receive Feature Set Message Center Time Stamp Message Reference Feature Set Number Confidentiality Indicator Response Selection Response Code Urgent Indicator User Data Unit User Destination Address User Destination Subaddress User Origination Address User Origination Valid period of subaddress n/a0010n/an/an/an/an/an/an/an/an/an/an/a0011n/an/a0110 n/an/an/an/a0001n/an/an/an/an/an/an/an/an/a01000101n/a All other IEI values are reserved message type indicator

The Message Type Indicator is a 3-bit field located in bits 1, 2 and 3 of the first octet of each SMS Application Message MTI. MTI is encoded as follows: bit 321 message type B→MS MS→B 000001010011 SMS DELIVER reserved reserved SMS FEAT_CTRL_STATUS SMS SUBMIT reserved SMS USER_ACKSMS FEAT_CTRL_REQU All other values are reserved delayed sending time

Delay Send Time is an optional IE included in SMS SUBMIT to allow the message center to send the message at a later time.

The Delayed Send Time field is expressed in whole or half octets. In the first case, the Delayed Send Time consists of two octets giving the relative send time, calculated from the receipt of the SMS SUBMIT from the Message Center. In the second case, the delayed sending time consists of 8 octets given to provide the absolute time at which the short message was sent. bit octet 8 7 6 5 4 3 2 1 0 0 0 Reserved format=0 Delayed Send Time 0 0 1 0 Information Unit Identifier 1 Delay Send Time - Relative 2 List of delayed transport information elements, 8-octet format: bit octet 8 7 6 5 4 3 2 1 0 0 0 Reserved format=1 Delayed Delivery Time 0 0 1 0 Information Unit Identifier 1 Delay Delivery Time - Absolute 2 Delay Delivery Time - Absolute 3 Delay Delivery Time - Absolute 4 Delay Delivery Time - Absolute 5 Delay Delivery Time - Absolute 6 Delay Delivery Time - Absolute 7 Delay Delivery Time - Absolute 8 Transmit Receive Transmit Receive is used in SMS SVBMIT messages to request the message center to provide a Transmit Receive to the MS when transmitting to the intended recipient of the MS-originating SMS. Bit value 0 does not need to transmit and receive 1 needs to transmit and receive Feature Set The Feature Set IE is used to control or provide status about a specific feature. When the SMSFEAT-CTRL-REQU or SMS FEAT-CTRL-STATUS message is sent, at least one conditional feature group must be followed, and the feature parameter and feature status are related to the feature value ID.

Feature Group Information Unit Directory bit octet 8 7 6 5 4 3 2 1 0 0 0 0 Spare Feature ID 1 feature state feature state 0 0 0 Spare 2

The Feature ID field is used to identify the Feature associated with the Feature Status and Feature Parameters for a given case in the SMS FEAT XTRL REQ and SMSFEAT STATUS messages. The Feature ID field is coded as follows: Bit 4 3 2 10 0 0 0 0 SMS All other values are reserved.

The feature parameter field is used in SMS FEAT CTRL STATUS and SMSFEAT XTRL REQU to identify the feature parameter associated with a given feature ID. If the feature ID indicates SMS, the feature parameter is defined as follows: bit 6 5 40 0 0 receive all messages 0 0 1 store all messages 0 1 0 receive selected messages all other values are reserved.

Feature Status is a 2-bit field used to indicate status (in SMS FEAT CTRLSTATUS message) or requested feature status (in SMD FEAT CTRL): Bit 8 70 0 Feature parameter "Off" 0 1 Feature parameter "On" All others value is preserved. Dashboard Timestamp

The message center time stamp is optionally included in the SMS DELIVER message to indicate the time when the message was received by the message center.

The Information Center Timestamp IE is given in half-octet form and represents the time as follows: bit octet 8 7 6 5 4 3 2 1 0 0 0 0 Reserved Information Center Timestamp 0 0 0 1 Information Unit Identifier 1 year number 1 year number 2 2 month number 1 month number 2 3 day number 1 day number 2 4 hour number 1 hour number 2 5 score number 1 score number 2 6 second number 1 second number 2 7 time zone number 1 time zone number 2 8 Note: The number 1 is the most valid number, for example, if the year number 1=9, and the year number 2=3, the year is 93. information benchmark

The message reference (MR) IE uses an integer to represent the reference number of the short message

If the MR value is less than 64, only the 6-bit field is used for MR. If the MR value is greater than 63 but less than 8192, a 13-bit field is used for MR.

In an SMS-terminated MS, MR is used to link the user confirmation message with the previously sent SMS DELIER message "confirmed by the user". exactly the same. number of feature groups

The feature group number product indicates the number of instances of the feature group IE in the SMS FEAT-CTRL-REQU or SMS-CTRL-STATUS message. Bit 8 7 60 0 0 Reserved 0 1 0 1 Feature Group 0 1 0 2 Feature Group 1 1 0 6 Feature Group 1 1 1 7 Feature Group Confidentiality Indicator

The privacy indicator is used in SMS DEVIVER and SMS SUBMIT messages to allow the sending user to set the privacy level of the sent message.

Depending on the level of security (protected, for example, by using a different password entered by the mobile user who reads the incoming SMS DELIVER message), the mobile station receiving the SMS DELIVER may process the information differently. Bit 6 50 0 Unrestricted (Privacy Level 0) 0 1 Restricted (Privacy Level 1) 1 0 Encryption (Privacy Level 2) 1 0 Privacy (Privacy Level 3) Answer Selection

The response selection IE must follow a field in the SMS DELIVER message, indicating whether to ask the user to confirm. This bit is set in bit 0 of the second octet of the SMS-DELIVER message. 0 Need user confirmation 1 Need user confirmation response code

The response code is used to carry the MS user response to the previously received short message.

The response code is 4 bits long and must follow the IE used in the SMS USER ACK message. This response code value is specific to the message center. emergency indicator

The urgency indicator IE is used to allow the sender of the short message to provide the urgency of the short message, for example, the MS can use the UI to provide different user notifications. The UI must follow the 2-digit IE included in the SMS DELIVER and SMS SUBMIT messages. The UI is coded as follows: bit 7 60 0 most 0 1 normal 1 0 urgent 1 0 very urgent user data unit

The user data unit IE is used to carry user text information. bit octet 8 7 6 5 4 3 2 1 length indicator (in octets) 1 0 0 0 coded identifier spare 2 User data 3 " " User data no User data represents user information and is coded as specified by the Coded Identifier as follows: bits 5 4 3 2 10 0 0 0 1 IA5 as specified in Table 11 of CCITT rec.T.50. Record T.500 0 0 1 0 User specific All other values are reserved User destination address

The purpose of the user destination address information element is to identify the user destination address of the short message (ie SMSSUBMIT message) sent by the MS.

The maximum length of this information unit is network dependent. User purpose information element (TBCD code) bit octet 8 7 6 5 4 3 2 1 The length of the destination address content 1 address_code=0 type of number Numbering Plan Identification 2 second number first number 3 · · · · · · ··· (2n-4)th digit or filler number (odd) (2n-5)th number no User destination address information unit (IA5 encoding) bit octet 8 7 6 5 4 3 2 1 The length of the destination address content 1 address_code=1 type of number Numbering Plan Identification 2 first number/character 3 ··· ··· nth number/character no Type of number (octet 2), (see note 1) digit 7 6 50 0 0 unknown 0 0 1 international number (see note 2) 0 1 0 national number (see note 2, 4, 5, 6) 0 1 1 Network dedicated number (see Note 3) 1 0 0 Subscriber number (see Note 2, 6) 1 1 0 Abbreviated number 1 1 1 Reserved Extended All other values are reserved. Notice:

1. For the definition of "international, national and subscriber numbers", see CCITT Introduction 1.330.

2. will not include prefixes or escape digits

3. The number type of "network-dedicated number" is used to indicate a management and service number dedicated to the service network.

4. Views on short messages between the United States and other countries in region 1 worldwide (see CCITT's E.163 Recommendation for Assignment of Country Codes), where the numbering plan identification is "ISDN/Telephone Numbering Plan", "Number Type " to "National Number".

5. For numbers containing service access codes (eg "700", "800", "900"), the type of number is coded as "National Number".

6. Service codes in "N11" format (eg: "911", "411") are unique and can be sent using the "subscriber number" or "national number" code point. Coding Scheme Identification (Octet 2) Coding Scheme (for types of numbers = 000, 001, 010, and 100) Bits 4 3 2 10 0 0 0 Unknown 0 0 0 1 ISDN/Telephone Numbering Plan (CCITT Recommendations E.164 and E .163) 0 0 1 1 Data Numbering Plan (CCITT Recommendation X.121) 0 1 0 0 Teletype Numbering Plan (CCITT Recommendation F.69) 1 0 0 1 Private Numbering Plan 1 1 1 1 Reserved Extensions All other values are reserved . Number digits (octet 3, etc.) This field is coded TBCD or IA5, as indicated by the address code field (octet 2, bit 8). If using TBCD, the encoding is as follows: binary value number 0000000100100011010001010110011110001001101010111100 Filling item 1234567890*# All other values are reserved The purpose of the user destination subaddress user destination subaddress information element is to identify the subaddress of the destination user subaddress of the short message. See CCIIT Recommendations 1.330 and 1.334 for definitions of subaddresses. User Destination Subaddress Information Element bit octet 8 7 6 5 4 3 2 1 0 0 0 0 Reserved Destination user subaddress 0 0 1 1 information unit identification 1 The length of the content of the user's destination sub-address 2 ORSVD type of subaddress odd/even indicator 0 0 0 Reserved 3 subaddress information 4 and so on Type of subaddress (octet 3) Bit 7 6 50 0 0 NSAP (CCITT Recommendation X.213 or ISO 8348 AD2) 0 1 0 User-specified All other values are reserved. Odd/even indicator (octet 3) Bit 40 Even number of address signal 1 Odd number of address signal Note: Odd/even indicator is used when the type of subaddress is "user-specified" and coded For TBCD subaddress information (octet 4, etc.) the NSAP address will be encoded using the preferred binary encoding specified in CCITT Recommendation X.213 or ISO8348AD2.

When AFI=50 (coded as 01 010000 according to BCD), the IA5 character is coded by setting the eighth bit to 0 according to Table 11 of CCITT Recommendation T.50 or the specification of ISO646. When AFI=51 (01010001 according to BCD encoding), ASCII characters are encoded by setting the eighth bit to 0 according to the ANST X3.4 specification.

For user-specific subaddresses, the fields are coded according to user specifications, subject to a maximum length of 20 octets. When interoperating with the CCITT Recommendation X.25 network, TBCD encoding is applied. User originating address The user of the user originating address unit is to identify the originating address of the short message. The maximum length of this information unit is network dependent. User originating address information unit (TBDC code) bit octet 8 7 6 5 4 3 2 1 0 0 0 0 Reserved User Origination Address 0 1 0 0 Information Unit Identifier 1 The length of the content of the user's originating address 2 address_code=1 number type Numbering Plan Identification 3 first address character 4 · · nth address character no Digit 7 6 50 0 0 unknown 0 0 1 international number (see note 2) 0 1 0 domestic number (see note 2, 4, 5, 6) 0 1 1 network-private number (see note 3) 1 0 0 subscriber number (See note 2, 6) 1 1 0 abbreviated number 1 1 1 reserved expansion All other values are reserved. Notice:

1. For the definition of "international, national and subscriber numbers", see CCITT Recommendation 1.330.

2. Will not include prefixes or escape digits.

3. The number type of "network-dedicated number" is used to indicate a management and service number dedicated to the service network.

4. SMS transactions between the United States and other countries in zone 1 worldwide (see CCITT Recommendations for Assignment of Country Codes), where the numbering plan identification is "ISDN/Telephone Numbering Plan" and "Type of Number" is coded to "National Number ".

5. For numbers containing service access codes (such as "700", "800", "900"), the "type of number" is coded according to "domestic number".

6. Service codes in "N11" format (such as "911", "411") are unique and can be sent with "subscriber number" or "national number" code points. Coding Scheme Identification (octet 3) Coding Scheme (for types of numbers = 000, 001, 010 and 100) Bits 4 3 2 10 0 0 0 Unknown 0 0 0 1 ISDN/Telephone Numbering Plan (CCITT Recommendations E.164 and E. 163) 0 0 1 1 Data Numbering Plan (CCITT Recommendation x.121.) 0 1 0 0 Teletype Numbering Plan (CCITT Recommendation F.69) 1 0 0 1 Private Numbering Plan 1 1 1 1 Reserved Extensions All other values are reserved . Numbers (octet 3, etc.) This field encodes TBCD as follows: binary value number 0000000100100011010001010110011110001001101010111100 Filling item 1234567890*# All other values are reserved The user originating subaddress The purpose of the user originating subaddress information element is to identify the subaddress of the originating user subaddress of the short message. For the definition of the subaddress, see CCITT recommendations 1.330 and 1.334. Subscriber originating subaddress information element bit octet 8 7 6 5 4 3 2 1 0 0 0 0 Reserved User Origination Subaddress 0 0 1 1 Information Unit Identifier 1 The length of the content of the user's originating address 2 ORSVD subaddress type odd/even indicator 0 0 0 Reserved 3 subaddress information 4 and so on Type of subaddress (octet 3) Bits 7 6 50 0 0 (CCITT Recommendation X.213 or ISO 8348 AD2) 0 1 0 User-specified All other values are reserved. Odd/even indicator (octet 3) Bit 40 Number of address signal 1 Number of address signal Note: The odd/even indicator is used when the type of subaddress is "user-specified" and coded as TBCD Subaddress information (octet 4, etc.) NASP addresses will be encoded using the preferred binary encoding described in CCITT Recommendation X.213 or ISO8348AD2. When AFI=5 (encoded as 01010000 in BCD), IA5 characters are encoded by setting the eighth bit to zero as described in Table 11 of CCITT Recommendation T.50 or ISO646. When AF1=51 (encoded as 01010001 in BCD), ASCII characters are encoded by setting the eighth bit to zero as described in ANSTX3.4.

For user-specified subaddresses, the fields are coded according to user specifications, subject to a maximum length of 20 octets. When interoperating with CCITT Recommendation X.25 networks, TBCD encoding is applied. Valid period

The effective period IE is used in the short message originating from the MS. If the message is not delivered to the designated recipient user, it is used to indicate the time of the information center after the message is deleted.

The Valid Period field gives either an integer or a half-octet representation. In the first case, the validity period consists of two octets giving the length of the validity period calculated when the SMS-SUBMIT was received by the message center. In the second case, the live period consists of 8 octets giving the absolute time of the end of the live period. The Valid Period Format IE indicates a format for encoding the valid period. Valid period information element content, two octet format bit octet 8 7 6 5 4 3 2 1 0 0 0 Reserved format=0 Valid period 0 1 1 0 information element indicator 1 Valid period - relative 2 Valid period information element content, 8-octet format bit octet 8 7 6 5 4 3 2 1 0 0 0 Reserved format=1 Valid period 0 1 1 0 information element indicator 1 Valid Period - Absolute 2 Valid Period - Absolute 3 Valid Period - Absolute 4 Valid Period - Absolute 5 Valid Period - Absolute 6 Valid Period - Absolute 7 Valid Period - Absolute 8 The relationship between valid period and field coding VP decimal value Effective period value 0 to 143144 to 167 (VP+1)×5 minutes (that is, 5 minutes gap until 12 hours) at 12 o’clock+(VP-143)×30 minutes 168 to 196197 to 255 (VP-166)×1 day (VP-192)×1 week

The absolute validity period is coded according to the information center time stamp IE. Identification [[Mobile Station Identification (MSID) This mobile station can be identified using 4 different numbering methods: 1. 34-bit IS-54B MIN2. 24-bit IS-54B MINI3. IMSI4. TMSI34-Bit IS-54B MIN

[[See IS-54B. 24-Bit IS-54B MIN1

See IS-54B. IMSI

[[Definition

The International Mobile Subscriber Identity (IMSI) is a number with a maximum length of 15 decimal digits, constructed as follows, (D=one decimal digit) [[incorporated in Figure Pg.159]] MCC Mobile Communications Country Code MNC Mobile Network Code MSIN Mobile Station Identification Number NMSI National Mobile Station Identification IMSI International Mobile Station Identification

The MCC is specified in Appendix A of E.212, and the MCC uniquely identifies the country of the MS. All MCCs are 3 digits long. The United States and Canada are included in Region 3 of the Appendix. Canada reserves code 302; US reserves codes 310-316.

The MNC is uniquely used to identify the MS's local Public Land Mobile Network (PLMN). PLMN is called a mobile network served by an HLR. MCC and MNC are the global addresses of the MS's HLR.

The IMSI is not used as a dial number; and typically there is only one IMSI per NAM. Backward compatibility with MIN

There is a need for backward compatibility with the IS-54B type of MIN, and systems operating with IS-54B MIN are supported if the following conditions are fulfilled:

MCC indicates users from subzone 3 (US and Canada), and

The first two (decimal) digits of the network code are 00, then the remaining digits can be assumed to be the normal 10-digit MIN, with the appropriate translations added for network addressing. IMSI code

The IMSI is encoded in a 50-bit fixed-length field.

MSIN represents the 10 decimal digits used to drive the 34-bit IS-54B MIN.

The 15 decimal digits are divided into 5 groups of 3 digits each. Each of the resulting groups of 5 decimal digits is then represented as: using the general decimal-to-binary transformation (0 to 999), the corresponding decimal number encoded in 10 binary bits (0<=d _i d _j d _k <= 999, i=j+1, j=k+1, k=1, 4, 7, 10, 13). TMSI Temporary Mobile Station Identity (TMST) may be a 20-bit MSID, which is dynamically assigned to a mobile station by the network. Through the network, TMSI can be used for paging or sending a message to a mobile station on the SPACH. Mobile ESN

     According to the IS-54B system identification

Base stations may broadcast values indicating their identity, ie with respect to: country, SID, network type, and, if they are not public, private system ID.

They may optionally broadcast their system operator code and vendor code BS. These optional values are optional via ad-hoc queries or possible broadcasts of these values. These optional values will only be needed when special private signals are requested, which the BS can transmit, or for accessing the local private network.

The identification structure will support national private system identification as well as local private system identification. Monitoring of numbering systems will be handled differently for local and national identification configurations.

Country codes can be supported to allow international regulatory use and international roaming. information unit definition type bit SID System Identification - as specified by the FCC in IS-54 m 15 Network Type Public/Private/Semi-Private/Home set by system operator m 2 country code Country Code - Same as E.212 m 10 PS ID setting Private system identification - by operator/TBD o 4+16 ^* n SOCBSMC System operator code Base station manufacturer code OO 1212 SID This 15-bit SID structure can be used as specified in IS-54B. Network Type

Two bits can be used to identify the type of network, examples of which are: public, private, semi-private and home.

Private systems can only be accessed by specified mobile stations.

A semi-private system may transmit a private identification number (PSID), but be openly available to the public. This allows private users to act as a private cell while also allowing public use.

The home system may be a "femto base station" such as a cordless telephone. Network Type the code Public semi-dedicated dedicated household 00011011 country code

Country codes described in E.212 can be broadcast on DCC. Dedicated System ID

Private system IDs can be used to allow MSs to camp on private systems that they do not already have access to. When an MS detects that a private system ID is not in its private system ID table, the MS will not attempt to camp or register on that private system.

If a cell is marked as public, the cell may broadcast a PSID of "O" or not broadcast a PSID at all. PSID match

A PSID will be assigned by the system operator to a specific private system. It is the operator's responsibility to assign a same-PSID to the same private network in a different SID zone.

Part of the PSID range is reserved for national use. These assignments are only used in the case of a specific private network handled by different operators.

If the PSID is nationwide, the mobile station may not have to check for a matching SOC combination and can use the correct PDID and country code. This should be the case where multiple operators are used to give a nationwide coverage of a dedicated system.

The PSID, country code and SOC combination can be used by the mobile station to verify full access to the BMI.

By extending or enhancing existing recording/authentication procedures, BMI can optionally verify that a particular mobile station has access to a particular network. PSID allocation encoding (hexadecimal) Not using national distribution (requires external management of codes) by operator 00000001-07FF0800-FFFF A mobile station may have the capability to store multiple PSID and SOC combinations. Multiple Dedicated System Base Stations

A base station serving more than one private system may broadcast the PSID of each private system being served. The number of PSID being broadcast is identified by the number of the PSID field. field length (value) Parameter Type 4(0001) PSID number (note) 4 PSID 16 ^* n(n=1 to 16) Note: The number of PSIDs in this group is 1 plus the value of this field System Operating Code (SOC) and Base Station Manufacturer Code (BSMC)

The SOC and BSMC may be verified by the MS in order for the MS to acquire services provided by a private system operator or a private vendor's base station.

SOC can also be used by mobile stations to uniquely identify a local private system. An Example of SMS Messaging (BMI/EMS) Scope This example is provided for illustration purposes only. It provides a simple example of MS terminating SMS without user acknowledgment. A 63-octet character message transfer

Assume that the text message sent to the MS is as follows: "Votre rendez-Vous de cet apres-midi est Cancelle!!. Solut, Eric" This message is 63 characters long. The SMS application layer SMSDELIVER message sent by the message center will be as follows: Example of SMS DELIVER message format information unit type length illustrate Message Type Indicator (MTI) Reply Option (RO) Urgency Indicator (UI) Message Reference User Data Unit User Originating Address User Originating Subaddress Information Center Timestamp MMMMMOOO 3 bits 1 bit 2 bits 1 octet 65 octets 7 octets 0 octets 0 octets Indicates part of the first octet Indicates the part of the first octet Total = 74 octets SMS DELIVER is compressed in a layer 3 message in the message center and sent to BMI. The BMI receives Layer 3 messages from Messages and formats Layer 3 R-DATA messages to be transmitted to the MS. The R-DATA message is: Example of R-DATA message format: information unit type length (octets) illustrate Message Type R-Transaction Identifier R-Data Unit Information Center Originating Address MMMO 11760 Indicates the first octet indicates the second octet SMS DELIVER compression is assumed not to exist in this IE Total = 78 octets

Thus, a 77-octet layer 3 message will be transmitted to the MS over the air interface. The original sender text information is 63 octets, plus 7 octets to identify the originator (70 octets total). Therefore, 8 octets appear as additional: 1 octet for the R-DATA message type. 1 octet for R-Transaction Identifier. 2 octets appended to the R-Data unit (1 for the length indicator and 1 for the higher layer protocol identifier. 2 octets in the header of the SMS transport message. 2 octets The group of bytes is at the head of the User Data Element IE (Length Indicator and Encoding Identifier).

It is assumed that the MS has received and accepted the R-DATA message. The MS returns a Layer 3 R-DATAACCEPT message to the BMI. This message is two octets long (1 for the layer 3 message type and 1 for the R-transaction identifier).

This layer 3 confirmation will be used by the BMI to provide SMS terminal confirmation to the message center.

The above description has generally referred to, for example, communications between mobile stations and base stations, without describing the stations themselves. Therefore, the following description provides an example of such a mobile station and base station according to FIG. 38 .

Figure 38 shows a block diagram of a typical cellular mobile radiotelephone capable of using an embodiment of the present invention with the apparatus described above. The system represents a typical base station 110 and mobile station 120, and the signaling of messages between the base station and mobile stations described above can be performed using these or other devices. The base station comprises a control and processing unit 130 connected to the MSC 140 which in turn is connected to the public switched telephone network (not shown).

The base station 110 of a cell includes a plurality of voice channels handled by a voice channel transceiver 150 which is controlled by the control and processing unit 130 . Each base station also includes a control channel transceiver 160 which can handle more than one control channel, the control channel transceiver 160 being controlled by the control and processing unit 130 . Control channel transceiver 160 broadcasts control information over the control channel of the base station or the cell of a mobile station locked to the control channel. The voice channel is the transceiver broadcast traffic or voice channel, which may include digital control channel location information as previously described.

When mobile station 120 first enters idle mode, it periodically scans the control channels of base stations like base station 110 to determine which cell to lock or camp on. The mobile station 120 receives the absolute and relative information broadcast on the control channel of its voice and control channel transceiver 170 . The processing unit 180 then evaluates the received control channel information including the characteristics of the candidate cells and determines which network the mobile station should lock to. The received control channel information includes not only absolute information about the cell to which it is connected, but also relative information about other networks in the vicinity of the cell to which the control channel is associated. These neighboring cells are periodically scanned, monitoring the main control channel for more suitable candidates.

The foregoing detailed description is indicative of only certain specific embodiments of the invention. However, various modifications and changes can be made by those skilled in the art without departing from the spirit and scope of the inventions discussed and illustrated herein. Therefore, it should be clearly understood that the forms of the invention described herein are typical examples only and should not be limited thereto, and the scope of the invention should be determined in accordance with the appended claims.

Claims (10)

1. method of in the radio communication network, selecting the control channel, its step comprises:

Be created in the arrangement table by its candidate's mesh that may select that the far-end station receives;

Estimate above-mentioned arrangement table, provide the candidate's mesh that requires service until identify;

Select the control channel relevant with above-mentioned identification candidate mesh, unless the quality index of above-mentioned control channel is less than the first predetermined threshold.

2. according to claim 1 method is characterized in that, described the first predetermined threshold that the candidate's mesh that requires service is provided is than low deviation value of the second predetermined threshold of candidate's mesh that above-mentioned required service is not provided.

3. according to claim 1 method is characterized in that, described quality index comprises that signal intensity lags behind.

4. one kind is moved the station, comprising:

The device by the arrangement table of its candidate's mesh that may select that is created in that the far-end station receives;

Estimate above-mentioned arrangement table, until identify the device that the candidate's mesh that requires service is provided;

Select the control channel relevant with above-mentioned identification candidate mesh, unless the quality index of above-mentioned control channel is less than the device of the first predetermined threshold.

5. base station comprises:

Transmitter is used for the table that transmits control channel; With

Processor comprises the characteristic mark relevant with above-mentioned control channel in described table, represent whether above-mentioned control channel is synchronous with the control channel of serving.

6. according to claim 5 base station is characterized in that, the superframe that described characteristic mark represents described at least one control channel whether with the superframe-synchronized of described control channel of serving.

7. according to claim 5 base station is characterized in that, described characteristic mark represent the described superframe of respectively controlling channel whether with the superframe-synchronized of described control channel of serving.

8. one kind is moved the station, comprising:

Receiver receives the table that comprises at least one control channel by air interface; With

Processor according to the characteristic mark that finds, determines whether above-mentioned at least one control channel is synchronous with the control channel of serving mobile station in above-mentioned table.

9. according to claim 8 mobile station is characterized in that described characteristic mark represents whether the time crack of described at least one control channel is synchronous with the time crack of described control channel of serving.

10. according to claim 8 mobile station is characterized in that, the superframe that described characteristic mark represents described at least one control channel whether with the superframe-synchronized of described control channel of serving.

Images