WO2004089013A1 - Mechanisms for the addition of new system information block (sib) types in telecommunication message(s) - Google Patents
Mechanisms for the addition of new system information block (sib) types in telecommunication message(s) Download PDFInfo
- Publication number
- WO2004089013A1 WO2004089013A1 PCT/SE2004/000517 SE2004000517W WO2004089013A1 WO 2004089013 A1 WO2004089013 A1 WO 2004089013A1 SE 2004000517 W SE2004000517 W SE 2004000517W WO 2004089013 A1 WO2004089013 A1 WO 2004089013A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- system information
- information block
- block type
- referencing
- type
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
- H04W48/12—Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
- H04W8/183—Processing at user equipment or user record carrier
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/04—Large scale networks; Deep hierarchical networks
Definitions
- the present invention relates to a specific protocol extension scenario for telecommunications, namely the addition of a new system information block (SIB) type to message(s) transmitted in cellular applications such as, for example, a cellular network that uses Wideband Code Division Multiple Access (W-CDJVIA).
- SIB system information block
- W-CDJVIA Wideband Code Division Multiple Access
- wireless user equipment units communicate via a radio access network (RAN) to one or more core networks (CN).
- the user equipment units can be mobile stations such as mobile telephones ("cellular" telephones) and laptops with mobile termination, and thus can be, for example, portable, pocket, hand-held, computer-included, or car-mounted mobile devices which communicate voice and/or data with radio access network.
- the wireless user equipment units can be fixed wireless devices, e.g., fixed cellular devices/terminals which are part of a wireless local loop or the like.
- the radio access network covers a geographical area which is divided into cell areas, with each cell area being served by a base station.
- a cell is a geographical area where radio coverage is provided by the radio base station equipment at a base station site. Each cell is identified by a unique identity, which is broadcast in the cell.
- the base stations communicate over the air interface (e.g., radio frequencies) with the user equipment units (UE) within range of the base stations.
- UE user equipment units
- RNC radio network controller
- the radio network controller also sometimes termed a base station controller (BSC) supervises and coordinates various activities of the plural base stations connected thereto.
- the radio network controllers are typically connected to one or more core networks.
- the core network has various service domains, with an RNC having an interface to these domains.
- Radio access network is the Universal Mobile
- the UMTS is a third generation system which in some respects builds upon the radio access technology known as Global System for Mobile communications (GSM) developed in Europe.
- GSM Global System for Mobile communications
- the UTRAN UMTS Terrestrial Radio Access Network
- WCDMA wideband code division multiple access
- UEs user equipment units
- 3GPP Third Generation Partnership Project
- AMPS Advance Mobile Phone Service
- NAMPS Narrowband AMPS
- TGS Total Access Communications System
- PDS Personal Digital Cellular
- USDC United States Digital Cellular
- CDMA code division multiple access
- a connection involves both a Serving RNC (SRNC) and a drift RNC (DRNC), with the SRNC controlling the connection but with one or more diversity legs of the connection being handling by the DRNC.
- SRNC Serving RNC
- DRNC drift RNC
- An Inter-RNC transport link can be utilized for the transport of control and data signals between Serving RNC and a Drift RNC.
- An interface between radio network controllers e.g., between a Serving RNC [SRNC] and a Drift RNC [DRNC]) is termed the "Iur" interface.
- the RNS Radio Network Subsystem
- the RNS controls a number of Base Stations in the radio access network.
- the radio network controller controls the UTRAN.
- the RNC Radio Network Controller
- Such resources managed by the RNC include (among others) the downlink (DL) power transmitted by the base stations; the uplink (UL) interference perceived by the base stations; and the hardware situated at the base stations.
- the topology of a radio access network can also be conceptualized in areas or units larger than cells.
- a UTRAN Routing Area is a geographical area comprising one or more cells.
- Each URA is identified by a unique identity which is broadcast in all cells belonging to the URA.
- a URA can comprise cells controlled by more than one RNC.
- a URA with more cells in more than one RNC is overlapping between the RNCs, i.e. an overlapping URA.
- a Location Area is a geographical area comprising one or more cells.
- Each LA is identified by a unique identity sent on the broadcast channel, in the same way as the URA.
- a location area is used by the core network to track the location of the UE (in idle mode and in connected mode), while the URA is used by the radio access network to track the location of the UE in connected mode.
- a location area is geographically larger than a URA.
- To each location area there is one of several RNCs having cells in that particular location area. A relationship between location area and RNC is stored in the core network.
- Radio access networks typically have a particular signalling protocol employed between the radio access network and the user equipment unit to support the management of radio resources.
- UTRAN has its Radio Resource Control (RRC) layer 3 signalling protocol.
- RRC Radio Resource Control
- a user equipment unit in the RRC protocol operates in a state model conceptualized as having two modes: an Idle Mode and a Connected Mode.
- the Idle Mode is entered after power on.
- Idle Mode there is no connection between the user equipment unit (UE) and the UTRAN.
- the least active UEs operate in the idle mode, in which UTRAN is unaware of the presence of the UE.
- the core network (CN) is aware of the Location Area (LA)/ Routing Area (RA) in which the UE is located.
- the UE also informs the CN of changes in LA/ RA.
- the CN initiates paging in all cells comprising the LA/ RA in which the UE is registered.
- the user equipment unit When an RRC connection is established, the user equipment unit (UE) is assigned a U-RNTI and the user equipment unit (UE) enters Connected Mode.
- the RNC in charge of the RRC connection for this UE is denoted as the Serving RNC (SRNC).
- SRNC Serving RNC
- the UE In the first two states the UE is inactive, in the URA_PCH state the UTRAN knows the UE position at the UTRAN Routing Area (URA) level while in CELL_DCH UTRAN knows the UE position at the cell level.
- URA_PCH the UTRAN knows the UE position at the UTRAN Routing Area (URA) level
- CELL_DCH UTRAN knows the UE position at the cell level.
- the CELLJFACH state the UE is active but operates on a common channel, which is a channel shared with other UEs.
- the CELL_DCH the UE operates on a dedicated channel which is allocated only for that UE
- the UTRAN controls the mobility of the UE, i.e. it orders the UE to perform measurements and based on , e.g., those measurements performs such activities as, e.g., moving the UE to another cell, adding or removing cells from the active set (i.e., the set of cells actively used in the RRC connection).
- the UE normally decides which cell to move to, although this cell re-selection process is influenced by parameters provided by the network.
- the UTRAN broadcasts or transmits certain "system information" over the air interface which may be relevant for a large number of UEs in a cell.
- the system information includes information and/or parameters which are formatted into information elements (IEs).
- the parameters of the information elements (IEs) are utilized for various purposes such as, e.g., to control the cell re-selection procedure for a UE.
- the broadcast of system information in general is described, e.g., in Technical Specification 3GPP TS 25.331 V3.17.0
- IEs parameters of the system information need to be broadcast more often than other parameters (IEs). For example, some of the parameters (IEs) need to be broadcast more frequently because, e.g., they affect the access delay or because the information changes rapidly. On the other hand, other system information is broadcast less frequently to spare or save the limited radio resources.
- system information e.g., the system information message
- SIBs system information blocks
- This partitioning of the system information into system information blocks (SIBs) permits, among other things, transmission of each type of SIB to be scheduled independently and at different time intervals to accomplish the aforementioned objectives.
- the different types of system information blocks are distinguished by means of a "SIB type" information element.
- system information elements are broadcast in system information blocks.
- a system information block groups together system information elements of the same nature. Different system information blocks may have different characteristics, e.g., regarding their repetition rate and the requirements of the UEs to re-read the system information blocks.
- a "master information block” (MIB) gives references and scheduling information to a number of system information blocks in a cell.
- the system information blocks (SIBs) contain the actual system information.
- the master information block may optionally also contain reference and scheduling information to one or two "scheduling blocks". These scheduling blocks give references and scheduling information for additional system information blocks. Scheduling information for a system information block may only be included in either the master information block or one of the scheduling blocks.
- a channel known as the broadcast channel is used to transfer system information and thus to carry the system information blocks (SIBs).
- the broadcast channel (BCCH) only supports transfer of data units of a fixed size. This can be a problem since many of the system information blocks (SIBs) have a size which exceeds the fixed size of the BCCH. Therefore, in order to support system information blocks with a size exceeding the BCCH limit, a technique known as segmentation is used.
- a concatenation mechanism is provided to use the broadcast channel (BCCH) efficiently. These two mechanisms basically operates as follows: (a) system information blocks may be split into a number of different segments, and (b) a number of segments may be concatenated.
- the concatenation of a number of segments is called a system information message.
- SIBs system information blocks
- the segmentation and concatenation of segments for system information blocks (SIBs) are described, e.g., in Technical Specification 3GPP TS 25.331 V3.17.0 (2003-12), Radio Resource Control (RRC) Protocol Specification (Release 1999), e.g., ⁇ 8.1.1.1.3.
- RRC Radio Resource Control Protocol Specification
- the entire Technical Specification 3GPP TS 25.331 V3.17.0 (2003-12) is incorporated herein by reference.
- SIB system information block
- MIB Master Information Block
- SBs Scheduling Blocks
- the signalling specified in the existing RRC protocol (e.g., Technical Specification 3GPP TS 25.331 V3.17.0 (2003-12), Radio Resource Control (RRC) Protocol Specification (Release 1999)) also provides two specific mechanisms for the possibility of future extensions or modifications to signalling messages. These future extension mechanisms are described, e.g., in RRC protocol (e.g., Technical Specification 3GPP TS 25.331 V3.17.0 (2003-12), Radio Resource Control (RRC) Protocol Specification (Release 1999)) also provides two specific mechanisms for the possibility of future extensions or modifications to signalling messages. These future extension mechanisms are described, e.g., in RRC protocol (e.g., Technical Specification 3GPP TS 25.331 V3.17.0 (2003-12), Radio Resource Control (RRC) Protocol Specification (Release 1999)) also provides two specific mechanisms for the possibility of future extensions or modifications to signalling messages. These future extension mechanisms are described, e.g., in RRC protocol (e.g., Technical Specification 3GPP TS 25.3
- the critical extension mechanism involves the definition of a new version of the message. In the new version of the message the transfer syntax may be completely different from the previous version of the message, except for the initial part that indicates the version.
- the second of the future extension mechanisms is the non-critical message extension. When the non-critical message extension is used, the transfer syntax of the existing message is just extended with new information. In the non-critical message extension case old receivers will still recognize the entire message apart from the newly introduced extensions.
- the non-critical extension message mechanism can be used for system information. Furthermore, for system information the extension mechanism has been defined only at the level of the system information blocks. This means that future extension is neither possible at the level of the segments nor at the level of the system information messages.
- the transfer syntax specifies the range of possible information element values for parameters. In some cases this range includes a number of spare values that are reserved for future extension. This is also the case for the message type information element.
- the RRC protocol (TS 25.331) explicitly specifies that the UE shall ignore broadcast messages (message sent on BCCH) having a type which it does not comprehend. In other words, if the UE receives an RRC message on the BCCH, PCCH, CCCH or SHCCH with a message type not defined for the logical channel type the message was received on, the UE shall ignore the message.
- SIB system information block
- the "SIB type" information element is actually included in a number of hosting information elements, and the number of spare values reserved for future extension is not necessarily uniform among the hosting information elements (note that one information element can be a component or information element of another (host) information element ).
- the information element "SIB type” is used in different segments, such as the information elements "Complete SIB” & “Complete SIB (short)".
- thirty two values have been defined for this "SIB type" when included in these different information element s, of which only two of the values are spare values.
- the information element "SIB and SB Type” is used in IE “References to other system information blocks and scheduling blocks", which is included in the MIB.
- IE "References to other system information blocks and scheduling blocks”
- the information element "SIB type SIBs only” is used in the two information elements known as "SCCPCH Information for FACH” and "References to other system information blocks”.
- SCCPCH Information for FACH and "References to other system information blocks”.
- thirty two values have been defined for this ie , of which five values are spare values. Hence, as seen from the foregoing, the number of spare values is not consistent among the host information elements.
- SIB type One possible way to extend the SIB type is as follows: (1) use the last spare value to indicate that the SIB type is extended; and (2) add a non critical extension to the message in order to support further extensions in future. For example, if it is desired to add support for an additional seven SIB types, one would need to add a three -bit field. In this case the first thirty one SIB types can be signalled by means of the original SIB type, while SIB type 31 up to 37 can be supported by the non-critical extension. Value 7 (' 111 'B) of the non-critical extension would then be reserved for further extensions.
- SIBs system information blocks
- SIBs system information blocks
- nodes of a telecommunications network which prepare network system information for transmission across an air interface to a user equipment unit; methods of operating such node; and, embodiments of user equipment units which receive and process the system information.
- the system information includes a system information block type which is included in protocol blocks.
- the protocol blocks include a system information block and a referencing block (110).
- the referencing block (110) is one or both of a master information block and a scheduling block.
- the protocol blocks in which the system information is included have a system information block type field.
- the information block type field includes a system information block type value which corresponds to the system information block type.
- the system information block can comprise one or more segments.
- the node embodiments include a system information extension utility function which is arranged to facilitate the use of extended system information block types, e.g., the use of system information block type values which are outside a range of nominal system information block type values.
- the system information extension utility function is arranged and functions to accomplish the following: (1) include a first system information block type extension indicator in the system information block type field of the referencing block when the system information block type for a system information block referenced by the referencing block does not have a system information block type value in a nominal range of system information block type values; (2) include a first system information block type extension field in the referencing block; (3) include, in the first system information block type extension field, a system information block type extension value which indicates a system information block type for the system information block referenced by the referencing block; and (4) include a second system information block type extension indicator in the system information block type field of a segment of the system information block referenced by the referencing block.
- the user equipment unit includes a system information processing function which is arranged and functions to accomplish the following: (1) recognize the first system information block type extension indicator in the system information block type field of the referencing block when the system information block type for the system information block referenced by the referencing block does not have a system information block type value in a nominal range of system information block type values; (2) locate the first system information block type extension field in the referencing block; (3) obtain from the first system information block type extension field a system information block type extension value which indicates a system information block type for the system information block referenced by the referencing block; and (4) recognize a second system information block type extension indicator in the system information block type field of a segment of the system information block referenced by the referencing block.
- a system information processing function which is arranged and functions to accomplish the following: (1) recognize the first system information block type extension indicator in the system information block type field of the referencing block when the system information block type for the system information block referenced by the referencing block does not have a system information block type value in a nominal range of system information
- the system information processing function of the user equipment unit could skip processing the referencing block and essentially process only system information blocks, e.g., read the broadcast information continuously. This is feasible because the SIB type extension information is included in the segments of the system information blocks. In such variation, the system information processing function of the user equipment unit performs only the last three of the above enumerated operations.
- the second system information block type extension indicator can have the same value as the first system information block type extension indicator.
- the system information extension utility function is further arranged and further functions to include a second system information block type extension field in the segment of the system information block referenced by the referencing block; and include in the second system information block type extension field the system information block type extension value which indicates the system information block type for the system information block referenced by the referencing block.
- the system information processing function of the user equipment unit for this mode and method locates the second system information block type extension field in the segment of the system information block referenced by the referencing block, and obtains from the second system information block type extension field the system information block type extension value which indicates the system information block type for the system information block referenced by the referencing block.
- the system information extension utility function is arranged and functions to accomplish the following: (1) include, in a system information block type field of a system information block referenced by a referencing block, a system information block type value; and (2) include, in the referencing block, a code set identifier which identifies a selected one of plural code sets for use in interpreting the system information block type value included in the system information block type field of the system information block referenced by the referencing block.
- a first value for the code set identifier can require that the system information block type value be interpreted in accordance with a range of nominal system information block type values for a predetermined protocol, while a second value for the code set identifier can require that the system information block type value be interpreted in accordance with a range of extended system information block type values, the extended system information block type values being outside the range of nominal system information block type values.
- the code set identifier can be included in an extension field of the referencing block.
- the system information processing function of the user equipment unit performs the following basic actions: (1) obtains, from the system information block type field of a system information block referenced by a referencing block, a system information block type value; (2) obtains, from the referencing block, a code set identifier which identifies a selected one of plural code sets; and (3), uses the selected one of the plural code sets for interpreting the system information block type value included in the system information block type field of the system information block referenced by the referencing block, as well as the (preferably same) the system information block type value included in the system information block type field of the referencing block.
- the referencing block can be a master information block.
- the system information block type field is an "SIB and SB type" information element.
- the referencing block can be a scheduling block.
- SIB type SIBS only information element.
- SIB Type information element.
- Fig. 1 is a diagrammatic view of an example mobile communications system.
- FIG. 2 is a simplified function block diagram of a portion of a UMTS
- Terrestrial Radio Access Network including a user equipment unit (UE) station; a radio network controller; and a base station.
- UE user equipment unit
- Fig. 3 is a diagrammatic view of referencing block and a system information block generated according to a first embodiment and a first mode.
- Fig. 3A is a diagrammatic view showing a variation of the referencing block and the system information block of Fig. 3.
- Fig. 4 is a flowchart showing basic example steps performed by a system information extension utility function of a network node for generating the referencing block and the system information block of Fig. 3.
- Fig. 5 is a diagrammatic view of an example format of a system information block such as the system information block of Fig. 3.
- Fig. 6 is a flowchart showing basic example steps performed by a system information processing function of a user equipment unit for processing the referencing block and the system information block of Fig. 3.
- Fig. 6A is a flowchart showing a variation of the processing steps of Fig. 6 performed by a system information processing function of a user equipment unit
- Fig. 7 is a diagrammatic view of referencing block and a system information block generated according to a second embodiment and a second mode.
- Fig. 8 is a flowchart showing basic example steps performed by a system information extension utility function of a network node for generating the referencing block and the system information block of Fig. 7.
- Fig. 9 is a flowchart showing basic example steps performed by a system information processing function of a user equipment unit for processing the referencing block and the system information block of Fig. 7.
- Fig. 10 is a diagrammatic view of referencing block and a system information block generated according to a third embodiment and a third mode.
- Fig. 11 is a flowchart showing basic example steps performed by a system information extension utility function of a network node for generating the referencing block and the system information block of Fig. 10.
- Fig. 12 is a flowchart showing basic example steps performed by a system information processing function of a user equipment unit for processing the referencing block and the system information block of Fig. 10.
- Fig. 13 is a diagrammatic view of an example format of a master information block.
- Fig. 14 is a diagrammatic view of an example format of a scheduling block.
- a representative, connection- oriented, external core network, shown as a cloud 14 may be for example the Public Switched Telephone Network (PSTN) and/or the Integrated Services Digital Network (ISDN).
- PSTN Public Switched Telephone Network
- ISDN Integrated Services Digital Network
- a representative, connectionless-oriented external core network shown as a cloud 16 may be for example the Internet. Both core networks are coupled to their corresponding core network service nodes.
- the PSTN/ISDN connection-oriented network 14 is connected to a connection-oriented service node shown as a Mobile Switching Center (MSC) node 18 that provides circuit-switched services.
- the Internet connectionless-oriented network 16 is connected to a General Packet Radio Service (GPRS) node 20 tailored to provide packet-switched type services which is sometimes referred to as the serving GPRS service node (SGSN).
- GPRS General Packet Radio Service
- Each of the core network service nodes 18 and 20 connects to a UMTS Terrestrial Radio Access Network (UTRAN) 24 over a radio access network (RAN) interface referred to as the lu interface.
- UTRAN 24 includes one or more radio network controllers (RNCs) 26.
- RNCs radio network controllers
- the UTRAN 24 of Fig. 1 is shown with only two RNC nodes, particularly RNC 26. and RNC 26 2 .
- Each RNC 26 is connected to a plurality of base stations (BS) 28.
- BS base stations
- two base station nodes are shown connected to each RNC 26.
- RNC 26 1 serves base station 28 ⁇ . ⁇ and base station 28 1-2
- RNC 26 2 serves base station 28 2-1 and base station 28 2-2 -
- a different number of base stations can be served by each RNC, and that RNCs need not serve the same number of base stations.
- Fig. 1 shows that an RNC can be connected over an Iur interface to one or more other RNCs in the URAN 24.
- base station nodes have, in some contexts, more recently become known as Node B or B -nodes.
- each base station 28 is shown as serving one cell.
- Each cell is represented by a circle which surrounds the respective base station. It will be appreciated by those skilled in the art, however, that a base station may serve for communicating across the air interface for more than one cell. For example, two cells may utilize resources situated at the same base station site.
- a user equipment unit such as user equipment unit (UE) 30 shown in Fig. 1, communicates with one or more cells or one or more base stations (BS) 28 over a radio or air interface 32.
- UE user equipment unit
- BS base stations
- Each of the radio interface 32, the lu interface, the lub interface, and the Iur interface are shown by dash-dotted lines in Fig. 1.
- Fig. 2 shows selected general aspects of user equipment unit (UE) 30 and illustrative nodes such as radio network controller 26 and base station 28.
- the user equipment unit (UE) 30 shown in Fig. 2 includes a data processing and control unit 31 for controlling various operations required by the user equipment unit (UE).
- the UE's data processing and control unit 31 provides control signals as well as data to a radio transceiver 33 connected to an antenna 35.
- the radio transceiver 33 is a function of the physical layer.
- the example radio network controller 26 and base station 28 as shown in Fig. 2 are radio network nodes that each include a corresponding data processing and control unit 36 and 37, respectively, for performing numerous radio and data processing operations required to conduct communications between the RNC 26 and the user equipment units (UEs) 30.
- Part of the equipment controlled by the base station data processing and control unit 37 includes plural radio transceivers 38 connected to one or more antennas 39.
- Fig. 1 shows RNC 26 1 as including an RRC entity 50-RAN while user equipment unit 30 includes a corresponding RRC entity 50-UE.
- Fig. 1 further shows that the RRC entity 50-RAN prepares system information which is transmitted in the manner depicted by arrow 52 to the user equipment unit 30 where it is processed by RRC entity 50-UE.
- the embodiments of the RRC entity 50-UE described herein facilitate the use of extended system information block types, e.g., the use of system information block type values which are outside a range of nominal system information block type values.
- extended system information block types e.g., the use of system information block type values which are outside a range of nominal system information block type values.
- system information extension utility function 100 the particular aspect of the RRC entity 50-RAN which facilitates such use of extended system information block types will be referred to as a system information extension utility function and is illustrated by system information extension utility function 100 in Fig. 2.
- the system information extension utility function 100 is included as part of the data processing and control unit 36 of radio network controller (RNC) node 26. It will be appreciated that this aspect of RRC entity 50-RAN could be denominated by various other names, such as a system information scheduling function or the like.
- system information extension utility function 100 can be realized in other ways than as part of the data processing and control unit 36, and that the data processing and control unit 36 is not limited to one particular processor or circuit.
- the system information extension utility function 100 could be realized by using individual hardware circuits, using software functioning in conjunction with a suitably programmed digital microprocessor or general purpose computer, using an application specific integrated circuit (ASIC), and/or using one or more digital signal processors (DSPs).
- ASIC application specific integrated circuit
- DSPs digital signal processors
- RRC entity 50-UE which detects and processes the extended system information block types is (for simplicity) called a system information processing function and is illustrated as system information processing function 102 in Fig. 2.
- system information processing function 102 is hosted by the data processing and control unit 31 of user equipment unit 30. This particular name is not limiting, and its variety of possible implementations are similar to those above described with reference to the system information extension utility function 100 of RRC entity 50-RAN.
- the system information includes a system information block type which is included in protocol blocks.
- the protocol blocks include a system information block and a referencing block.
- the referencing block is one or both of a master information block and a scheduling block.
- the protocol blocks in which the system information is included have a system information block type field.
- the system information block type field includes a system information block type value which corresponds to the system information block type.
- the system information block can comprise one or more segments.
- FIG. 3 shows both a referencing block 110(3) and a system information block 112(3) generated by the system information extension utility function 100.
- the referencing block 110(3) includes a SIB type field 113(3).
- the system information block 112(3) is shown as having a segment 114(3).
- the segment 114(3) includes both a SIB type field 116(3) and a segment data field 118(3).
- SIB system information block
- SIB system information block
- SIB type field 116(3) is set to a special value, e.g., ' 1111 'B, indicating that it concerns an extended SIB type. This special value ensures that the SIB will be ignored by mobiles (e.g., user equipment units) which do not support this extension.
- a regular extension is added. This extension includes an additional SIB type extension field 120(3) which is used to distinguish a number of additional SIB types.
- SIB type extension field 122(3) is introduced within the segments 114(3). As shown in Fig. 3, the SIB type extension field 122(3) is created within the original SIB data field 118(3).
- FIG. 3 A shows a slight variation of the embodiment of Fig. 3.
- Fig. 3 A shows the SIB type extension field 120(3) as being part of an extension to the referencing block 110(3 A).
- Other embodiments/modes described herein can be comparably varied in the manner depicted in Fig. 3A.
- SIB data field 118 Normally the SIB data field 118 only carries the real payload (part of) a system information block.
- SIB system information block
- FIG. 5 the information element "SIB type” corresponds to the SIB type field 116(3); the information element "SIB data fixed extension” corresponds to the segment data field 118(3); and, the information element "SIB type extension” corresponds to the SIB type extension field 122(3).
- Fig. 4 shows basic, example actions implemented by system information extension utility function 100 in conjunction with the first embodiment/mode.
- Action 4-1 through action 4-3 are actions performed by system information extension utility function 100 with reference to referencing block 110(3); action 4-4 through 4-6 are performed with reference to system information block 112(3).
- the system information extension utility function 100 includes a first system information block type extension indicator (e.g., the value "1111") in the system information block type field 113(3) of the referencing block 110(3) when the system information block type for a system information block referenced by the referencing block does not have a system information block type value in a nominal range of system information block type values. Then, as action 4-2, the system information extension utility function 100 includes the first system information block type extension field 120(3) in the referencing block 110(3).
- a first system information block type extension indicator e.g., the value "1111
- the system information extension utility function 100 includes, in the first system information block type extension field 120(3), a system information block type extension value which indicates a system information block type for the system information block (e.g., system information block 112(3)) referenced by the referencing block.
- a system information block type extension value which indicates a system information block type for the system information block (e.g., system information block 112(3)) referenced by the referencing block.
- the system information extension utility function 100 includes a second system information block type extension indicator in the system information block type field 116(3) of the segment 114 of the system information block referenced by the referencing block, i.e., system information block 112(3).
- the second system information block type extension indicator can have the same value as the first system information block type extension indicator (e.g., "1111").
- the system information extension utility function 100 includes the second system information block type extension field 122(3) in the segment 114 of the system information block referenced by the referencing block, i.e., system information block 112(3). Further, as action 4-6, the system information extension utility function 100 includes in the second system information block type extension field 122(3) the system information block type extension value which indicates the system information block type for the system information block referenced by the referencing block (referencing block 110(3)).
- Fig. 6 shows basic example steps performed by a system information processing function 102 of user equipment unit 30 for processing the referencing block 110(3) and the system information block 112(3) of Fig. 3.
- Action 6-1 through action 6- 3 are performed by system information processing function 102 with reference to referencing block 110(3);
- action 6-4 through 6-6 are performed with reference to system information block 112(3).
- the system information processing function 102 recognizes the first system information block type extension indicator in the system information block type field 113(3) of the referencing block 110(3) when the system information block type for the system information block referenced by the referencing block does not have a system information block type value in a nominal range of system information block type values.
- the system information processing function 102 locates the first system information block type extension field 120(3) in the referencing block 110(3).
- the system information processing function 102 obtains from the first system information block type extension field 120(3) a system information block type extension value which indicates a system information block type for the system information block referenced by the referencing block, i.e., system information block 112(3).
- the system information processing function 102 recognizes a second system information block type extension indicator in the system information block type field 116(3) of the segment 114 of the system information block referenced by the referencing block, i.e., system information block 112(3). Then, as action 6-5, the system information processing function 102 locates the second system information block type extension field 122(3) in the segment of the system information block referenced by the referencing block. As action 6-6 the system information processing function 102 obtains from the second system information block type extension field , 122(3) the system information block type extension value which indicates the system information block type. The system information processing function 102 can then process the system information block 112(3) in accordance with its type.
- the system information processing function of the user equipment unit could skip processing the referencing block and essentially process only system information blocks, e.g., read the broadcast information continuously.
- Such variation is illustrated in Fig. 6A, wherein the system information processing function of the user equipment unit performs only action 6-4, action 6-5, and action 6-6, all as understood with reference to the Fig. 6 description thereof.
- actions 6-1 through 6-3 e.g., the reading/processing of the referencing block
- receivers not supporting the extension will just ignore segments corresponding with extended SIB types (based on the value 'lll l'B within the SIB-type field). This means that the first embodiment/mode is fully backwards compatible.
- Receivers supporting the extensions should be able to decode the SIB data and know that the first bits actually concern the SIB type extension. This can be done by making the IE SIB type extension conditional on the value of SIB type; it is included if SIB type has value "Reserved for extension".
- SIB-TypeAndFirstSegment :: CHOICE ⁇
- FIG. 7 shows both a referencing block 110(4) and a system information block 112(4) generated by the system information extension utility function 100.
- Fields which are common with the embodiment of Fig. 3 are comparably numbered (with the exception of parenthetical suffixes) and comparably understood with reference to the embodiment of Fig. 3.
- both within the referencing block 110(4) and within the segments 114 of the system information block 112(4) the SIB type is set to a special value, e.g., ' 1111 'B, indicating that it concerns an extended SIB type.
- both the SIB type field 113(4) of referencing block 110(4) and the SIB type field 116(4) of the system information block 112(4) are set to the special value. This ensures that the system information block 112(4) will be ignored by mobile stations (e.g., user equipment units (UEs)) which do not support this extension.
- UEs user equipment units
- a regular extension is added including the additional SIB type extension field 120(4), which is used to distinguish a number of additional SIB types. For instance, in case three bits are reserved for the SIB type extension field 120(4), an additional seven SIB types can be supported. In contrast to the first embodiment/mode, no such additional field is introduced with system information block 112(4). In other words, the second embodiment/mode differs from the first in that system information block 112(4) does not have a SIB type extension field 122(4).
- Fig. 8 shows basic, example actions implemented by system information extension utility function 100 in conjunction with the second embodiment/mode.
- Action 8-1 through action 8-4 of Fig. 8 are essentially the same as action 4-1 through action 4-4 of Fig. 4, and accordingly are not discussed herein.
- Fig. 8 omits any actions corresponding to actions 4-5 through 4-6 of Fig. 4.
- Fig. 9 shows basic example steps performed by a system information processing function 102 of user equipment unit 30 for processing the referencing block 110(3) and the system information block 112(3) of Fig. 7.
- Action 9-1 through action 9- 4 of Fig. 9 are essentially the same as action 6-1 through action 6-4 of Fig. 6, and accordingly are not discussed herein.
- Fig. 9 omits any actions corresponding to actions 6-5 through 6-6 of Fig. 6.
- the second embodiment/mode is still fully backwards compatible. Moreover, the second embodiment/mode is more efficient since it involves less overhead in every segment, and also avoids the explosion in ASN.l type definitions, and the existing scheduling algorithms are not affected.
- the second embodiment/mode requires an additional mechanism to allow the scheduling of multiple extended SIB type at the same time and within the same SYSTEM INFORMATION message.
- the details of which extended SIB type is included in a segment is included in the scheduling information.
- the scheduling information should clarify the SIB type for each of those. This can be done by including additional information in the scheduling information or by defining a fixed rale, e.g., that the order used in the SYTEM INFORMATION message is the same as the one used in the scheduling information.
- FIG. 10 An example of the third embodiment/mode is illustrated in Fig. 10, which shows both a referencing block 110(10) and a system information block 112(10) generated by the system information extension utility function 100.
- Fields which are common with the embodiment of Fig. 3 are comparably numbered (with the exception of parenthetical suffixes) and comparably understood with reference to the embodiment of Fig. 3.
- the respective regular SIB type fields 113(10) and 116(10) are used to distinguish the additional SIB types.
- a regular extension is added including an additional code set field 130(10), indicating how the SIB type should be interpreted. For example, a value 0 in the SIB type field would mean SIB type 1 if a first code set is operative (as indicated by the code set identifier in field 130(10)) and would mean SIB type 20 if a second code set is operative.
- no additional fields are introduced or required within the segments of the system information block 112(10) .
- code set field per referencing block or per block that is referenced to be scheduled. This avoids having different code sets being utilized for different system information blocks that are referenced by a referencing block.
- the third embodiment/mode is not backwards compatible since the interpretation of a given SIB type depends on information provided in an extension that earlier mobiles do not support. As a result, these non-supporting mobiles will interpret the information incorrectly.
- the third embodiment/mode does not really require additional mechanisms to support scheduling of multiple extended SIB type at the same time; within the same SYSTEM INFORMATION message.
- the only restriction that applies for the third embodiment/mode is that SIBs with the same value within the SIB type field should not be scheduled together. This is not considered to be an acceptable restriction, that could anyhow be resolved in a manner as described for the second embodiment.
- Fig. 11 shows basic example steps performed by system information extension utility function 100 in conjunction with the third embodiment/mode.
- the system information extension utility function 100 includes, in a system information block type field 116(10) of a system information block 112(10) referenced by a referencing block, a system information block type value.
- the system information extension utility function 100 includes, in the referencing block 110(10), a code set identifier which identifies a selected one of plural code sets for use in interpreting the system information block type value included in the system information block type field 116(10) of the system information block referenced by the referencing block.
- the code set identifier is included in code set identifier field 130(10).
- a first value for the code set identifier can require that the ⁇ system information block type value be interpreted in accordance with a range of nominal system information block type values for a predetermined protocol, while a second value for the code set identifier can require that the system information block type value be interpreted in accordance with a range of extended system information block type values, the extended system information block type values being outside the range of nominal system information block type values.
- the code set identifier field 130(10) can be included in an extension field of the referencing block.
- Fig. 12 shows basic example steps performed by a system information processing function 102 of user equipment unit 30 for processing the referencing block 110(10) and the system information block 112(10) of Fig. 10.
- the system information processing function 102 obtains, from the system information block type field 116(10) of a system information block referenced by a referencing block, a system information block type value.
- the system information processing function 102 obtains, from the referencing block 110(10), a code set identifier (from code set identifier field 130(10)) which identifies a selected one of plural code sets.
- the system information processing function 102 uses the selected one of the plural code sets for interpreting the system information block type value included in the system information block type field 116(10) of the system information block referenced by the referencing block, as well as the (preferably same) the system information block type value included in the system information block type field 113(10) of the referencing block 110(10).
- the referencing block can be a master information block or a scheduling block.
- Fig. 13 depicts certain aspects and information elements of a master information block, and references in parenthesis the pertinent sections of the Technical
- system information block type field is an "SIB and SB type" information element.
- Fig. 14 depicts certain aspects and information elements of a scheduling block, and references in parenthesis the pertinent sections of the Technical
- system information block type field is an "SIB type SIBS only" information element.
- SIB Type field is a "SIB Type" information element.
- system information block type field as utilized herein can correspond in terms of Technical Specification 3GPP TS 25.331 V3.17.0 (2003-12) to any one of the appropriate information elements above mentioned, e.g., the "SIB and SB type” information element; the "SIB type SIBS only” information element; or the "SIB Type” information element.
- the segments can still be decoded and processed without considering the scheduling information.
- the second embodiment tends to be more efficient since it does not involve the additional overhead in every segment, since it avoids the explosion in ASN.l type definitions, and since it does not affect the existing scheduling algorithms. These same considerations applicable to the second embodiment are also valid for the third embodiment. No additional mechanism is required to support scheduling of multiple extended SIB type at the same time/ within the same SYSTEM INFORMATION message.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Stored Programmes (AREA)
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP04725576.5A EP1614306B1 (en) | 2003-04-03 | 2004-04-02 | Mechanisms for the addition of new system information block (sib) types in telecommunication message(s) |
US10/552,295 US10206162B2 (en) | 2003-04-03 | 2004-04-02 | Mechanisms for the addition of new system information block (SIB) types in telecommunication message(s) |
US16/271,961 US10477458B2 (en) | 2003-04-03 | 2019-02-11 | Mechanism for the addition of new system information block (SIB) types in telecommunication message(s) |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
SE0301027-9 | 2003-04-03 | ||
SE0301027A SE0301027D0 (en) | 2003-04-03 | 2003-04-03 | Method and apparatus in a telecommunication system |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/552,295 A-371-Of-International US10206162B2 (en) | 2003-04-03 | 2004-04-02 | Mechanisms for the addition of new system information block (SIB) types in telecommunication message(s) |
US16/271,961 Continuation US10477458B2 (en) | 2003-04-03 | 2019-02-11 | Mechanism for the addition of new system information block (SIB) types in telecommunication message(s) |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2004089013A1 true WO2004089013A1 (en) | 2004-10-14 |
Family
ID=20290963
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/SE2004/000517 WO2004089013A1 (en) | 2003-04-03 | 2004-04-02 | Mechanisms for the addition of new system information block (sib) types in telecommunication message(s) |
Country Status (6)
Country | Link |
---|---|
US (2) | US10206162B2 (en) |
EP (1) | EP1614306B1 (en) |
KR (1) | KR101044836B1 (en) |
CN (1) | CN100384262C (en) |
SE (1) | SE0301027D0 (en) |
WO (1) | WO2004089013A1 (en) |
Cited By (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1705945A1 (en) * | 2005-03-25 | 2006-09-27 | Samsung Electronics Co., Ltd. | Method and apparatus for configuring transport format combination set in a mobile communication system |
WO2007024110A1 (en) * | 2005-08-26 | 2007-03-01 | Electronics And Telecommunications Research Institute | Method and apparatus for providing system information in ofdma cellular system |
GB2429882A (en) * | 2005-08-31 | 2007-03-07 | Infineon Technologies Ag | Formation of system information medium access control protocol messages and ascertainment of system information from system information medium access control |
DE102006037756A1 (en) * | 2006-08-11 | 2008-02-14 | Infineon Technologies Ag | Transmitting data in mobile telephone system involves providing correspondence information at defined position of at least some data blocks, which states whether next bock is associated with subsequent association element in series |
EP1943777A1 (en) * | 2005-10-31 | 2008-07-16 | LG Electronics Inc. | Method for processing control information in a wireless mobile communication system |
EP1946487A1 (en) * | 2005-10-31 | 2008-07-23 | LG Electronics Inc. | Method for processing paging information in a wireless mobile communication system |
CN101297521A (en) * | 2005-10-31 | 2008-10-29 | Lg电子株式会社 | Method for processing control information in a wireless mobile communication system |
EP1997244A1 (en) * | 2006-03-21 | 2008-12-03 | LG Electronics Inc. | Method of transmitting/receiving lte system information in a wireless communication system |
EP2015597A1 (en) * | 2006-05-01 | 2009-01-14 | NTT DoCoMo, Inc. | Base station and communication method |
CN100466849C (en) * | 2006-06-15 | 2009-03-04 | 华为技术有限公司 | Method and system for controlling user terminal to read system message |
EP2037703A1 (en) * | 2007-09-11 | 2009-03-18 | Nokia Siemens Networks Oy | Method and device for providing signalling information and communication system comprising such device |
WO2009112928A2 (en) | 2008-03-10 | 2009-09-17 | Nortel Networks Limited | Methods for control signaling for wireless systems |
US8305970B2 (en) | 2005-10-31 | 2012-11-06 | Lg Electronics Inc. | Method of transmitting a measurement report in a wireless mobile communications system |
RU2470492C2 (en) * | 2008-01-11 | 2012-12-20 | Квэлкомм Инкорпорейтед | Notification and detection of system data modification in wireless communication |
US8559362B2 (en) | 2005-11-04 | 2013-10-15 | Lg Electronics Inc. | Random access channel hopping for frequency division multiplexing access systems |
US8817737B2 (en) | 2005-10-31 | 2014-08-26 | Lg Electronics Inc. | Method of transmitting and receiving data in a mobile communication network |
WO2016121308A1 (en) * | 2015-01-30 | 2016-08-04 | Nec Corporation | Communication system |
Families Citing this family (45)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB0326936D0 (en) * | 2003-11-19 | 2003-12-24 | Samsung Electronics Co Ltd | Mobile communications |
KR100606370B1 (en) * | 2004-11-30 | 2006-07-31 | 엘지노텔 주식회사 | Method for error detection of scheduling information in 3GPP system |
JP4818371B2 (en) * | 2005-10-31 | 2011-11-16 | エルジー エレクトロニクス インコーポレイティド | Method for processing control information in wireless mobile communication system |
US7996010B2 (en) * | 2005-11-02 | 2011-08-09 | Research In Motion Limited | Apparatus and method for querying for RAT handover system information in mobile telecommunications systems |
EP1887822B1 (en) * | 2006-08-09 | 2013-07-24 | Alcatel Lucent | A method for acquiring system information by a mobile station |
US8135405B2 (en) | 2006-08-31 | 2012-03-13 | Qualcomm Incorporated | Efficient search for wireless networks while minimizing page loss |
CA2664000C (en) * | 2006-10-03 | 2014-08-12 | Ntt Docomo, Inc. | Mobile station, radio base station, mobile communication system, and method of transmitting and receiving broadcast information |
US8006190B2 (en) | 2006-10-31 | 2011-08-23 | Yahoo! Inc. | Social namespace addressing for non-unique identifiers |
EP1932760A1 (en) * | 2006-12-13 | 2008-06-18 | Saab Ab | A radio communication system for providing both voice and data communication services over radio communication channels and a method for use in a radio communication system |
US8942695B2 (en) * | 2007-01-31 | 2015-01-27 | Qualcomm Incorporated | Method and apparatus for reducing call setup delay by adjusting SIB7 and SIB14 scheduling frequency |
US8934915B2 (en) * | 2007-01-31 | 2015-01-13 | Qualcomm Incorporated | Method and apparatus for reducing call setup delay by improved SIB7 and SIB14 scheduling |
US8599801B2 (en) * | 2007-02-01 | 2013-12-03 | Yahoo! Inc. | Collecting implicit information for determining context of event actions |
US8370349B2 (en) * | 2007-02-28 | 2013-02-05 | Yahoo! Inc. | Instant contact searching and presentation by category |
US7865206B2 (en) * | 2007-03-20 | 2011-01-04 | Yahoo! Inc. | Employing matching of event characteristics to suggest another characteristic of an event |
KR100914882B1 (en) * | 2007-04-02 | 2009-08-31 | 삼성전자주식회사 | Method for searching of network in wireless communication system |
US8054779B2 (en) * | 2007-05-08 | 2011-11-08 | Microsoft Corporation | Simultaneous wireless support in software defined radio |
KR101137671B1 (en) * | 2007-06-26 | 2012-04-23 | 노키아 코포레이션 | Apparatus, method and computer program product providing distribution of segmented system information |
US8724489B2 (en) * | 2007-10-26 | 2014-05-13 | Nokia Corporation | Method and apparatus for providing detection of a compatible network |
KR100912300B1 (en) | 2007-12-06 | 2009-08-17 | 한국전자통신연구원 | Transmission system and method for system information on a base station |
CN101897218B (en) * | 2007-12-14 | 2013-12-25 | 爱立信电话股份有限公司 | Delivering system information in wireless communications network |
US8599802B2 (en) | 2008-03-14 | 2013-12-03 | Interdigital Patent Holdings, Inc. | Method and apparatus to deliver public warning messages |
US8489084B2 (en) * | 2008-03-31 | 2013-07-16 | At&T Mobility Ii Llc | Over the air programming via cellular broadcast |
EP2283678A2 (en) * | 2008-04-18 | 2011-02-16 | Interdigital Patent Holdings, Inc. | Method and apparatus for broadcast of system information transmission window |
US20100165970A1 (en) * | 2008-12-25 | 2010-07-01 | Via Telecom, Inc. | Apparatus and method for fast synchronization in a dual mode system |
CN101998486B (en) * | 2009-08-11 | 2015-05-20 | 中兴通讯股份有限公司 | Measurement interval configuration method and device |
US8229412B2 (en) * | 2009-10-02 | 2012-07-24 | Sharp Laboratories Of America, Inc. | Determining whether system information can be reused and managing system information in a wireless communication system |
US8503481B2 (en) | 2010-06-29 | 2013-08-06 | Qualcomm Incorporated | Processing extension type system information blocks (SIBs) |
PT2641343T (en) * | 2010-11-15 | 2020-09-21 | Nokia Solutions & Networks Oy | Sub-frame configuration |
US9119167B2 (en) | 2011-08-30 | 2015-08-25 | Qualcomm Incorporated | Generic broadcast of location assistance data |
US9408052B2 (en) * | 2012-12-21 | 2016-08-02 | Qualcomm Incorporated | Techniques for power conservation in emergency broadcast message reception |
CN103124399B (en) * | 2013-01-23 | 2019-01-18 | 中兴通讯股份有限公司 | The intercepting method and device of cluster multi call paging |
JPWO2015020179A1 (en) * | 2013-08-09 | 2017-03-02 | 三菱電機株式会社 | Communications system |
WO2015020583A1 (en) * | 2013-08-09 | 2015-02-12 | Telefonaktiebolaget L M Ericsson (Publ) | System information broadcast for machine-type communication |
WO2015139330A1 (en) * | 2014-03-21 | 2015-09-24 | 华为技术有限公司 | System information transmission method and apparatus |
US10993098B2 (en) * | 2015-03-31 | 2021-04-27 | Sony Corporation | Telecommunications apparatus and methods |
US9736864B2 (en) * | 2015-05-11 | 2017-08-15 | Htc Corporation | Device and method of handling system information |
EP3456099A1 (en) * | 2016-05-13 | 2019-03-20 | Telefonaktiebolaget LM Ericsson (PUBL) | Apparatus and methods for providing and receiving system information in a wireless communications network |
CN107426783B (en) * | 2016-05-23 | 2020-01-14 | 北京佰才邦技术有限公司 | System message transmission method and device, user terminal and network equipment |
CN109756449B (en) * | 2017-11-02 | 2020-10-20 | 维沃移动通信有限公司 | Transmission method of system information block, base station and user terminal |
US11356804B2 (en) | 2018-02-25 | 2022-06-07 | Qualcomm Incorporated | Systems and methods for efficiently supporting broadcast of location assistance data in a wireless network |
US11191056B2 (en) | 2018-08-08 | 2021-11-30 | Qualcomm Incorporated | Systems and methods for validity time and change notification of broadcast location assistance data |
CN110830159B (en) | 2018-08-10 | 2021-07-16 | 华为技术有限公司 | Wireless communication method, device and computer readable storage medium |
US10932302B1 (en) | 2019-11-22 | 2021-02-23 | Sprint Spectrum L.P. | Control of wireless connectivity based on inability to interpret system message data flagged as critical to operation |
US11595962B1 (en) | 2020-09-03 | 2023-02-28 | Sprint Spectrum Llc | Use of network signaling (NS) values to cooperatively control spectral emission and additional functionality such as uplink/downlink subcarrier shifting |
US11659380B1 (en) | 2021-05-05 | 2023-05-23 | T-Mobile Usa, Inc. | UE-capability-based system information block transmission |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1073296A2 (en) * | 1999-07-30 | 2001-01-31 | Hyundai Electronics Industries Co., Ltd. | Method and apparatus for interfacing among mobile terminal, base station and core network in mobile telecommunication system |
US6628946B1 (en) * | 1999-05-20 | 2003-09-30 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for broadcasting system information in a cellular communications network |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5062108A (en) | 1989-09-29 | 1991-10-29 | At&T Bell Laboratories | ISDN codeset conversion |
US5991803A (en) * | 1997-03-28 | 1999-11-23 | Telefonaktiebolaget Lm Ericsson (Publ) | Decoupling service creation environment from service logic execution environment |
CN1132390C (en) * | 2001-03-16 | 2003-12-24 | 北京亿阳巨龙智能网技术有限公司 | Telecom service developing method based on independent service module |
US7346349B2 (en) * | 2002-11-06 | 2008-03-18 | Nokia Corporation | Method for controlling terminal fault corrections in cellular system |
-
2003
- 2003-04-03 SE SE0301027A patent/SE0301027D0/en unknown
-
2004
- 2004-04-02 CN CNB2004800094573A patent/CN100384262C/en not_active Expired - Lifetime
- 2004-04-02 US US10/552,295 patent/US10206162B2/en active Active
- 2004-04-02 WO PCT/SE2004/000517 patent/WO2004089013A1/en active Application Filing
- 2004-04-02 EP EP04725576.5A patent/EP1614306B1/en not_active Expired - Lifetime
- 2004-04-02 KR KR1020057018553A patent/KR101044836B1/en active IP Right Grant
-
2019
- 2019-02-11 US US16/271,961 patent/US10477458B2/en not_active Expired - Lifetime
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6628946B1 (en) * | 1999-05-20 | 2003-09-30 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for broadcasting system information in a cellular communications network |
EP1073296A2 (en) * | 1999-07-30 | 2001-01-31 | Hyundai Electronics Industries Co., Ltd. | Method and apparatus for interfacing among mobile terminal, base station and core network in mobile telecommunication system |
Non-Patent Citations (3)
Title |
---|
RADIO RESOURCE CONTROL (RRC) PROTOCOL SPECIFICATION, 1999 |
RADIO RESOURCE CONTROL, 1999 |
TECHNICAL SPECIFICATION 3GPP TS 25.331 V3.17.0, 2003 |
Cited By (54)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1705945A1 (en) * | 2005-03-25 | 2006-09-27 | Samsung Electronics Co., Ltd. | Method and apparatus for configuring transport format combination set in a mobile communication system |
US7626964B2 (en) | 2005-03-25 | 2009-12-01 | Samsung Electronics Co., Ltd. | Method and apparatus for configuring transport format combination set in a mobile communication system |
WO2007024110A1 (en) * | 2005-08-26 | 2007-03-01 | Electronics And Telecommunications Research Institute | Method and apparatus for providing system information in ofdma cellular system |
US9730032B2 (en) | 2005-08-31 | 2017-08-08 | Intel Deutschland Gmbh | Computer-aided mapping of system information medium access control protocol messages |
GB2429882B (en) * | 2005-08-31 | 2008-04-30 | Infineon Technologies Ag | Method and medium access control unit generating system information medium access control protocol messages |
US8380204B2 (en) | 2005-08-31 | 2013-02-19 | Intel Mobile Communications GmbH | Computed-aided mapping of system information medium access control protocol messages |
US10321277B2 (en) | 2005-08-31 | 2019-06-11 | Intel Deutschland Gmbh | Computer-aided mapping of system information medium access control protocol messages |
GB2429882A (en) * | 2005-08-31 | 2007-03-07 | Infineon Technologies Ag | Formation of system information medium access control protocol messages and ascertainment of system information from system information medium access control |
US8977271B2 (en) | 2005-08-31 | 2015-03-10 | Intel Mobile Communications GmbH | Computer-aided mapping of system information medium access control protocol messages |
US9088932B2 (en) | 2005-10-31 | 2015-07-21 | Lg Electronics Inc. | Method for processing paging information in a wireless mobile communication system |
US8305970B2 (en) | 2005-10-31 | 2012-11-06 | Lg Electronics Inc. | Method of transmitting a measurement report in a wireless mobile communications system |
CN101297521B (en) * | 2005-10-31 | 2014-11-12 | Lg电子株式会社 | Method for processing control information in a wireless mobile communication system |
US9516573B2 (en) | 2005-10-31 | 2016-12-06 | Lg Electronics Inc. | Data transfer management in a radio communications network |
CN101297521A (en) * | 2005-10-31 | 2008-10-29 | Lg电子株式会社 | Method for processing control information in a wireless mobile communication system |
EP1946487A1 (en) * | 2005-10-31 | 2008-07-23 | LG Electronics Inc. | Method for processing paging information in a wireless mobile communication system |
EP1943777A4 (en) * | 2005-10-31 | 2012-09-05 | Lg Electronics Inc | Method for processing control information in a wireless mobile communication system |
US9930580B2 (en) | 2005-10-31 | 2018-03-27 | Lg Electronics Inc. | Data transfer management in a radio communications network |
EP1946487A4 (en) * | 2005-10-31 | 2012-11-21 | Lg Electronics Inc | Method for processing paging information in a wireless mobile communication system |
US8817737B2 (en) | 2005-10-31 | 2014-08-26 | Lg Electronics Inc. | Method of transmitting and receiving data in a mobile communication network |
US10129795B2 (en) | 2005-10-31 | 2018-11-13 | Lg Electronics Inc. | Data transfer management in a radio communications network |
US8831616B2 (en) | 2005-10-31 | 2014-09-09 | Lg Electronics Inc. | Data transfer management in a radio communications network |
EP1943777A1 (en) * | 2005-10-31 | 2008-07-16 | LG Electronics Inc. | Method for processing control information in a wireless mobile communication system |
US8406767B2 (en) | 2005-10-31 | 2013-03-26 | Lg Electronics Inc. | Data transfer management in a radio communications network |
US8559362B2 (en) | 2005-11-04 | 2013-10-15 | Lg Electronics Inc. | Random access channel hopping for frequency division multiplexing access systems |
EP1997244A4 (en) * | 2006-03-21 | 2012-12-05 | Lg Electronics Inc | Method of transmitting/receiving lte system information in a wireless communication system |
US8538444B2 (en) | 2006-03-21 | 2013-09-17 | Lg Electronics Inc. | Method of transmitting/receiving LTE system information in a wireless communication system |
EP1997244A1 (en) * | 2006-03-21 | 2008-12-03 | LG Electronics Inc. | Method of transmitting/receiving lte system information in a wireless communication system |
USRE46756E1 (en) | 2006-03-21 | 2018-03-13 | Lg Electronics Inc. | Method of transmitting/receiving LTE system information in a wireless communication system |
EP2629569A3 (en) * | 2006-05-01 | 2013-11-06 | NTT DoCoMo, Inc. | Base station and communication method |
EP2015597A4 (en) * | 2006-05-01 | 2013-01-02 | Ntt Docomo Inc | Base station and communication method |
EP2015597A1 (en) * | 2006-05-01 | 2009-01-14 | NTT DoCoMo, Inc. | Base station and communication method |
CN100466849C (en) * | 2006-06-15 | 2009-03-04 | 华为技术有限公司 | Method and system for controlling user terminal to read system message |
DE102006037756A1 (en) * | 2006-08-11 | 2008-02-14 | Infineon Technologies Ag | Transmitting data in mobile telephone system involves providing correspondence information at defined position of at least some data blocks, which states whether next bock is associated with subsequent association element in series |
EP2037703A1 (en) * | 2007-09-11 | 2009-03-18 | Nokia Siemens Networks Oy | Method and device for providing signalling information and communication system comprising such device |
RU2470492C2 (en) * | 2008-01-11 | 2012-12-20 | Квэлкомм Инкорпорейтед | Notification and detection of system data modification in wireless communication |
US9008655B2 (en) | 2008-01-11 | 2015-04-14 | Qualcomm Incorporated | Notification of modification of system information in a wireless communication system |
US10091762B2 (en) | 2008-01-11 | 2018-10-02 | Qualcomm Incorporated | System information modification notification and detection in wireless communications |
WO2009112928A2 (en) | 2008-03-10 | 2009-09-17 | Nortel Networks Limited | Methods for control signaling for wireless systems |
US11317384B2 (en) | 2008-03-10 | 2022-04-26 | Apple Inc. | Communication of control information using alert flag and version number |
US9655082B2 (en) | 2008-03-10 | 2017-05-16 | Apple Inc. | Communication of control information using alert flag and version number |
US9749994B2 (en) | 2008-03-10 | 2017-08-29 | Apple Inc. | Feedback of channel quality information in a multi-carrier environment |
US11595950B2 (en) | 2008-03-10 | 2023-02-28 | Apple Inc. | Communication of control information using alert flag and version number |
US9686773B2 (en) | 2008-03-10 | 2017-06-20 | Apple Inc. | Cross-carrier scheduling |
US9247531B2 (en) | 2008-03-10 | 2016-01-26 | Apple Inc. | Methods for control signaling for wireless systems |
EP2258123A4 (en) * | 2008-03-10 | 2014-10-22 | Apple Inc | Methods for control signaling for wireless systems |
US10321440B2 (en) | 2008-03-10 | 2019-06-11 | Apple Inc. | Communication of control information using alert flag and version number |
EP2258123A2 (en) * | 2008-03-10 | 2010-12-08 | Nortel Networks Limited | Methods for control signaling for wireless systems |
EP3557912A1 (en) * | 2008-03-10 | 2019-10-23 | Apple Inc. | Methods for control signaling for wireless systems |
US10862619B2 (en) | 2015-01-30 | 2020-12-08 | Nec Corporation | Method and apparatus for machine type communication of system information |
EP3893555A1 (en) * | 2015-01-30 | 2021-10-13 | NEC Corporation | Configuration of coverage enhancement schemes in volving transport block sizes and number of repetitions of sib |
WO2016121308A1 (en) * | 2015-01-30 | 2016-08-04 | Nec Corporation | Communication system |
US11539459B2 (en) | 2015-01-30 | 2022-12-27 | Nec Corporation | Method and apparatus for machine type communication of system information |
GB2534866A (en) * | 2015-01-30 | 2016-08-10 | Nec Corp | Communication system |
US11736228B2 (en) | 2015-01-30 | 2023-08-22 | Nec Corporation | Method and apparatus for machine type communication of system information |
Also Published As
Publication number | Publication date |
---|---|
KR101044836B1 (en) | 2011-06-28 |
CN1771745A (en) | 2006-05-10 |
US20070049344A1 (en) | 2007-03-01 |
US10206162B2 (en) | 2019-02-12 |
US20190191361A1 (en) | 2019-06-20 |
EP1614306B1 (en) | 2013-06-12 |
EP1614306A1 (en) | 2006-01-11 |
US10477458B2 (en) | 2019-11-12 |
CN100384262C (en) | 2008-04-23 |
KR20060007010A (en) | 2006-01-23 |
SE0301027D0 (en) | 2003-04-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10477458B2 (en) | Mechanism for the addition of new system information block (SIB) types in telecommunication message(s) | |
EP1561355B1 (en) | Collective notification of node reset to subset of connections in radio access network | |
EP1428397B1 (en) | Recovery of mobile station(s) in connected mode upon rnc failure | |
JP4354704B2 (en) | Release multiple wireless connections using a global release message | |
CN101278592B (en) | Paging for a radio access network having pico base stations | |
RU2388184C2 (en) | Method of use in communication system | |
CN1739267B (en) | Hybrid protocol to support communications with multiple networks | |
EP1360860B1 (en) | Partial support of mobility between radio access networks | |
RU2378763C2 (en) | Common channel reconfiguration method and device | |
US7003297B2 (en) | Partial support of mobility between radio access networks | |
CN110999440B (en) | Radio base station and radio communication method | |
WO2006062338A1 (en) | Method and system for relocating serving radio network controller in a network sharing system | |
CN101911777A (en) | High-speed serving cell change | |
EP2286607B1 (en) | Method for clearing invalid user equipment information in home node b-gateway | |
CN102448043A (en) | Circuit switching domain rollback method and device | |
CN104380798A (en) | Method, device and system for network handover | |
KR100971592B1 (en) | Method and System for Controlling Update of Routing Area and Location Area | |
CN106304309B (en) | Multi-carrier power adjustment method and system | |
CN115399003A (en) | Multi-subscriber identity module techniques for wireless systems | |
KR101777860B1 (en) | Apparatus and Method for Stand-by Loading, Network Apparatus and Driving Method Thereof |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): BW GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2004725576 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1020057018553 Country of ref document: KR |
|
WWE | Wipo information: entry into national phase |
Ref document number: 20048094573 Country of ref document: CN |
|
WWP | Wipo information: published in national office |
Ref document number: 2004725576 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 1020057018553 Country of ref document: KR |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2007049344 Country of ref document: US Ref document number: 10552295 Country of ref document: US |
|
WWP | Wipo information: published in national office |
Ref document number: 10552295 Country of ref document: US |