CN115296781A - Method and apparatus for supporting system messages requested on demand - Google Patents

Method and apparatus for supporting system messages requested on demand Download PDF

Info

Publication number
CN115296781A
CN115296781A CN202211008566.XA CN202211008566A CN115296781A CN 115296781 A CN115296781 A CN 115296781A CN 202211008566 A CN202211008566 A CN 202211008566A CN 115296781 A CN115296781 A CN 115296781A
Authority
CN
China
Prior art keywords
message
information
user
system message
requested
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202211008566.XA
Other languages
Chinese (zh)
Inventor
汪巍崴
柯小婉
王弘
许丽香
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Samsung Electronics Co Ltd
Original Assignee
Samsung Electronics Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Samsung Electronics Co Ltd filed Critical Samsung Electronics Co Ltd
Priority claimed from CN201810437646.4A external-priority patent/CN109152086B/en
Publication of CN115296781A publication Critical patent/CN115296781A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/006—Transmission of channel access control information in the downlink, i.e. towards the terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The application discloses a method for supporting system information requested on demand, which comprises the following steps: a base station distribution unit DU receives configuration information of a physical random access channel PRACH for requesting system information from a base station centralized unit CU; the DU receives a random access preamble for requesting a system message from a user equipment UE; and the DU determines the information of the system message requested by the UE according to the random access preamble and the configuration information of the PRACH for requesting the system message, and sends the system message requested by the UE to the UE. The application also discloses other methods for supporting the system message of the request on demand and corresponding equipment. By applying the technical scheme disclosed by the application, the sending of the system message requested according to the requirement can be supported through the interaction between the CU and the DU.

Description

Method and apparatus for supporting system messages requested on demand
The application is a divisional application of an invention patent application with the application date of 09.05.2018, the application number of 201810437646.4 and the name of 'method and equipment for supporting system messages requested on demand'.
Technical Field
The present application relates to the field of wireless communications technologies, and in particular, to a method and an apparatus for supporting system messages requested on demand.
Background
In a next generation network or a fifth generation (5G) network, in order to support network function virtualization, more efficient resource management and scheduling, a base station (gNB) providing a wireless network interface for a terminal (UE) may be further divided into a base station centralized unit gNB-CU (gNB centralized unit) and a base station distributed unit gNB-DU (gNB distributed unit), (which are referred to as CU and DU, respectively, in the present invention).
The CU has at least Radio Resource Control (RRC) and Packet Data Convergence Protocol (PDCP) Protocol layers, and the like, and also includes a Service Data Adaptation Protocol (SDAP).
The DU has a radio link control protocol (RLC), a Medium Access Control (MAC), a physical layer, and the like.
Between CU and DU is a standardized public interface F1 interface.
The F1 interface is divided into: an F1 interface control plane (F1-C) and an F1 interface user plane (F1-U).
The transport network layer of F1-C is based on IP transport. For more reliable transport signaling, stream Control Transmission Protocol (SCTP) is added on top of IP. The protocol of the application layer is F1AP. SCTP can provide reliable application layer message transport.
The transport layer of the F1-U is UDP/IP, and the GTP-U is used above UDP/IP to carry user plane Protocol Data Units (PDUs).
Fig. 1 shows the structure of CUs and DUs.
In addition, in order to reduce the system overhead caused by the system message, the on-demand system message is defined in the 5G network, and the system message is not always broadcasted in the cell, but is transmitted according to the request of the user. In order to support the system message requested according to the requirement, a user sends a specific random access preamble (PRACH preamble) or sends the preamble on a specific random access resource (PRACH resource), or sends a specific random access preamble on a specific random access resource (rach resource), a base station (gNB) determines which system message or system information messages (system information message) the user requests according to the received random access preamble and/or the resource receiving the random access preamble, the system message may include one or more system information blocks (system information blocks), and then the base station sends the system message requested by the user to the user in a broadcast manner, a multicast manner or a unicast manner.
As mentioned before, in a 5G system, the gNB may be composed of two independent functional entities, namely CU and DU, with the interface between the two being standardized F1. In such a configuration, the CUs are responsible for generating system messages, while the DUs can receive random access preambles sent by users. If there is no support between the CU and DU for the system message requested on demand, the CU cannot know that the user sent the random access preamble associated with the requested system message. Therefore, in order to support the system messages requested on demand, a related mechanism needs to be defined between the CUs and the DUs. There is no relevant discussion so far.
Disclosure of Invention
The application provides a plurality of methods and devices for supporting system messages requested on demand, which can realize the transmission of the system messages requested on demand.
The application discloses a method for supporting system information requested on demand, which comprises the following steps:
A. a base station distribution unit DU receives configuration information of a physical random access channel PRACH for requesting system information from a base station central unit CU;
B. the DU receives a random access preamble for requesting a system message from a user equipment UE;
C. and the DU determines the information of the system message requested by the UE according to the random access preamble and the configuration information of the PRACH for requesting the system message, and sends the system message requested by the UE to the UE.
Preferably, before C, the method further comprises: the DU receives configuration information for on-demand system messages from CUs, the configuration information for on-demand system messages including at least one of:
each system message supporting user on-demand requests comprises at least one system information block SIB or at least one SIB;
scheduling information of each system message supporting a user request on demand;
the corresponding relation between each system message supporting the user request as required and the PRACH configuration information for requesting the system message;
the PRACH configuration information for requesting a system message includes: information of PRACH preamble and/or information of PRACH resource.
Preferably, the information about the system message requested by the UE is: system information requested by the UE;
the C comprises: and the DU determines corresponding PRACH configuration information according to the random access preamble, and determines the system information requested by the UE according to the corresponding relation between each system information supporting the user request as required and the PRACH configuration information for requesting the system information.
Preferably, the information about the system message requested by the UE is: PRACH configuration information corresponding to the random access preamble;
the C comprises the following steps: the DU determines corresponding PRACH configuration information according to the random access preamble and sends the PRACH configuration information to the CU; the DU receives a system message requested by the UE from the CU and transmits the system message requested by the UE to the UE.
Preferably, before C, the method further comprises: the DU receives index information corresponding to PRACH configuration information for each request system message from the CU;
the information about the system message requested by the UE is: index information corresponding to the PRACH configuration information;
the C comprises: the DU determines corresponding PRACH configuration information according to the random access preamble, determines index information corresponding to the PRACH configuration information, and sends the index information to the CU; the DU receives a system message requested by the UE from the CU and transmits the system message requested by the UE to the UE.
Preferably, before C, the method further comprises: the DU receives index information of system messages corresponding to each PRACH configuration information for requesting the system messages from the CU;
the information about the system message requested by the UE is: index information of the system message;
the C comprises: the DU determines corresponding PRACH configuration information according to the random access preamble, determines index information of corresponding system information, and sends the index information to the CU; the DU receives a system message requested by the UE from the CU and transmits the system message requested by the UE to the UE.
Preferably, before the DU sends the system message requested by the UE to the UE, the method further includes:
the DU sends an acknowledgement message to the UE, wherein the acknowledgement message is used for indicating at least one of the following information:
confirming that a network side sends a system message requested by UE;
confirming that the random access preamble transmitted by the UE is received;
confirming that a random access preamble sent by the UE is received and acquiring that the UE requests a system message;
confirming that the random access preamble sent by the UE is received, acquiring that the UE requests a system message, and sending a corresponding request message to the CU;
confirming that the random access preamble sent by the UE has been received and learning that the UE is requesting a system message, and sending a corresponding request message to the CU, and the CU confirming the request of the UE.
The application also discloses a method for supporting the system message requested on demand, which comprises the following steps:
the CU sends configuration information for the physical random access channel PRACH requesting system messages to the DU.
Preferably, the method further comprises: the CU sends the configuration information of the system message requested on demand to the DU.
Preferably, the method further comprises:
a CU receives PRACH configuration information corresponding to a random access preamble sent by UE from a DU;
and the CU determines the system message requested by the UE according to the PRACH configuration information and sends the system message to the DU.
Preferably, the method further comprises:
the CU sends index information corresponding to each PRACH configuration for requesting the system message to the DU;
a CU receives index information corresponding to PRACH configuration information corresponding to a random access preamble sent by UE from a DU;
and the CU determines the system message requested by the UE according to the corresponding index information and sends the system message to the DU.
Preferably, the method further comprises:
the CU sends index information of the system message corresponding to each PRACH configuration information for requesting the system message to the DU;
a CU receives index information of a system message corresponding to PRACH configuration information corresponding to a random access preamble sent by UE from a DU;
and the CU determines the system message requested by the UE according to the corresponding index information and sends the system message to the DU.
The application also discloses a base station distribution unit device, including: CU interactive module, UE interactive module and storage module, wherein:
the CU interaction module is used for receiving the configuration information of the PRACH for requesting the system message from the CU;
the storage module is configured to store the configuration information of the PRACH used for requesting the system message;
and the UE interaction module is used for receiving a random access preamble for requesting the system message from the UE, determining the system message requested by the UE according to the random access preamble and the configuration information of the PRACH for requesting the system message, and sending the system message requested by the UE to the UE.
Preferably, the CU interaction module is further configured to receive at least one of the following information from the CU:
configuration information of system messages requested on demand;
index information corresponding to each PRACH configuration;
index information of the system message corresponding to each PRACH configuration information for requesting the system message.
The application also discloses a base station central unit device, including: DU interaction module and processing module, wherein:
and the DU interactive module is used for sending the configuration information of the PRACH for requesting the system message to the DU.
Preferably, the DU interaction module is further configured to send at least one of the following information to the DU:
configuration information of system messages requested on demand;
index information corresponding to each PRACH configuration;
index information of the system message corresponding to each PRACH configuration information for requesting the system message.
The application also discloses a method for supporting the system message requested on demand, which comprises the following steps:
a base station distribution unit DU receives a system information request message from user equipment UE;
sending a message containing UE information to a base station Central Unit (CU);
receiving a confirmation message which is sent by a CU and correctly receives the system information request message;
and sending the system information requested by the UE to the UE.
Preferably, the confirmation message includes at least one of the following information:
the identification information of the UE, the identification of the cell where the UE is located, and the indication information of the system information sent by the DU to the UE.
The application discloses a method for supporting system information requested on demand, which comprises the following steps:
a base station central unit CU receives a message which is sent by a base station distribution unit DU and contains UE information, wherein the message which contains the UE information is sent by the DU after a system information request message is received from user equipment UE;
an acknowledgement message of correct reception of the system information request message is sent to the DU.
Preferably, the acknowledgement message comprises at least one of the following information:
identification information of the UE, identification of a cell in which the UE is located, and indication information of system information sent by the DU to the UE.
The application discloses a base station distribution unit DU includes:
a first receiving module, configured to receive a system information request message from a user equipment UE;
a first sending module, configured to send a message including UE information to a CU;
the first receiving module is used for receiving a confirmation message which is sent by the CU and correctly receives the system information request message;
the first sending module is used for sending the system information requested by the UE to the UE.
The application discloses base station centralized unit CU includes:
a second receiving module, configured to receive a message containing UE information sent by a base station distribution unit DU, where the message containing UE information is sent by the DU after receiving a system information request message from a user equipment UE;
and a second sending module, configured to send, to the DU, a confirmation message that the system information request message is correctly received.
According to the technical scheme, the method and the device for supporting the system message requested on demand can support the sending of the system message requested on demand through the interaction between the CU and the DU.
Drawings
FIG. 1 is a diagram of a conventional gNB-CU and gNB-DU structure;
FIG. 2 is a diagram illustrating a method for supporting on-demand system messages between CUs and DUs according to the present invention;
FIG. 3 is a diagram illustrating a second method for supporting on-demand system messages between CUs and DUs according to the present invention;
FIG. 4 is a diagram illustrating a third method for supporting on-demand system messages between CUs and DUs according to the present invention;
FIG. 5 is a diagram illustrating a fourth method for supporting on-demand system messages between CUs and DUs according to the present invention;
FIG. 6 is a schematic diagram of a preferred base station distribution unit apparatus according to the present invention;
FIG. 7 is a schematic diagram of a preferred base station central unit apparatus according to the present invention;
FIG. 8 is a diagram illustrating a CU sending an acknowledgment message to a DU when a system information request message is received in accordance with the present invention;
FIG. 9 is a fifth schematic diagram illustrating a method for supporting on-demand system messages between CU and DU in accordance with the present invention;
FIG. 10 is a sixth schematic diagram illustrating a method for supporting on-demand system messages between CU and DU in accordance with the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is further described in detail below by referring to the accompanying drawings and examples.
In a 5G network, the gNB may be composed of CUs and DUs, which are not functionally identical. In addition, a mechanism for requesting system messages on demand may also be supported in a 5G network, and in the mechanism, a user may send a specific random access preamble (PRACH preamble), or send a preamble on a specific random access resource (PRACH resource), or send a specific random access preamble on a specific random access resource, so as to request a network side for a system message required by the user. If the gNB is divided into CU and DU, the DU can receive the random access preamble transmitted by the user, but the system message is generated by the CU, so in order to transmit the system message requested by the user to the user, interaction between the CU and the DU is required. The invention provides a method for supporting system messages requested by a user through interaction between a CU and a DU.
In the present invention, a system message means a message including one or more System Information Blocks (SIBs), or refers to one or more SIBs.
The technical solution of the present application is described in detail by several preferred embodiments.
Example one
In this embodiment, the CU configures all system messages requested as needed in the DU in advance.
This embodiment describes a first method for supporting system messages requested on demand between CUs and DUs according to the present invention. In this method, the CU sends all the system messages requested on demand and the configuration information of the PRACH related to the (on-demand) system messages requested on demand to the DU through the messages of the F1 interface (e.g., the messages of the control plane of the F1 interface, i.e., F1-C messages). When the DU receives a random access preamble (PRACH preamble) associated with the requested system message, the requested system message is sent to the user (the sending may be broadcast or unicast or multicast). The flow chart of the method is shown in fig. 2, and comprises the following steps:
step 201: the CU sends configuration information for supporting on-demand system messages to the DU through messages (e.g., F1-C messages) of the F1 interface, where the configuration information includes one or more of the following information:
1) Each system message supporting user on-demand request may include one SIB (e.g., SIB4 in LTE), may include multiple SIBs (e.g., SIB4, SIB5, SIB6, etc. in LTE), or may be one or more SIBs;
2) Scheduling information of each system message supporting user request on demand, such as time position, and/or frequency position, and/or spatial information, and/or period of sending the system message;
3) The PRACH configuration information includes PRACH preamble information and/or PRACH resource information (for example: time frequency resource for sending PRACH preamble, and space resource for sending PRACH preamble). For example: PRACH configuration 1 is for requesting system messages 1, PRACH configuration 2 is for requesting system messages 2, etc. In addition, one PRACH configuration may also be used to request multiple system messages, such as PRACH configuration 3 is used to request system message 1 and system message 2. Table 1 gives an illustration of the correspondence of PRACH configuration to the system messages requested on demand.
PRACH configuration 1 System message 1
PRACH configuration 2 System message 2
PRACH configuration 3 System message 1 and system message 2
PRACH configuration 4 System message 2 and system message 3
PRACH configuration 5 System messages 4 and 5
TABLE 1
The configuration information in this step may be sent to the DU through the same F1 interface message, or may be sent to the DU through different F1 interface messages. In addition, if the configuration information is updated, the CU also sends an update message to the DU to update the configuration information.
Before or after this step, or in this step, it is assumed that the CU or DU has sent PRACH configuration information for requesting a system message and a correspondence between the PRACH configuration information and each system message supporting a user on-demand request to the user.
Step 202: the user transmits a random access preamble to the DU to request a system message.
In this step, the user sends a corresponding random access preamble according to the received configuration information (PRACH configuration information for requesting a system message, and a corresponding relationship between the PRACH configuration information and each system message supporting the user request as needed) and the system message that the user desires to request.
Step 203: the DU determines one or more system messages requested by the user based on the received random access preamble and then sends an acknowledgement message to the user, the acknowledgement message representing at least one of the following meanings:
1) Confirming that the network side (CU and/or DU and/or base station) will send the system message requested by the user;
2) Confirming that the random access preamble transmitted by the user in step 202 has been received;
3) Confirming that the random access preamble transmitted by the user in step 202 has been received and learning that the user is requesting a system message;
4) It is confirmed that the random access preamble sent by the user in step 202 has been received and it is known which system message or messages the user is requesting (i.e.: learning the system message requested by the user);
5) It is confirmed that the random access preamble sent by the user in step 202 has been received, and it is known which system message or messages the user is requesting, and the DU stores the system messages requested by the user (i.e.: DU stores user requested system messages).
Step 204: the DU sends the user the requested system message.
Before step 204, if the system messages and/or scheduling information stored at the DU has changed, the CU will send updated system messages and/or scheduling information to the DU in step 203 a.
Example two
In this embodiment, the CU notifies the DU of PRACH configuration for requesting a system message.
This embodiment describes a second method for supporting the system message requested on demand between the CU and the DU according to the present invention. In the method, CU sends PRACH configuration for requesting system information to DU, when DU receives a random access preamble requesting system information, the CU is informed of the configuration information corresponding to the received random access preamble, CU acquires the system information requested by user according to the configuration information, and sends the system information to user through DU. The flow chart of the method is shown in fig. 3, and comprises the following steps:
step 301: the CU sends an F1 interface message to the DU, wherein the message comprises PRACH configuration information used for requesting system messages, and the configuration information comprises information of PRACH preamble and/or information of PRACH resource (for example, the time-frequency resource position for sending PRACH preamble, and the space resource for sending PRACH preamble). For example: the message contains PRACH configuration 1 for requesting a system message, PRACH configuration 2 for requesting a system message, and the like. According to these information, the DU cannot know the correspondence between PRACH configuration and system message, but only knows that if a random access preamble matching these configurations is received, it indicates that the user is requesting system message.
Before or after this step, or in this step, it is assumed that the CU or DU has sent PRACH configuration information for requesting a system message and a correspondence between the PRACH configuration information and each system message supporting a user on-demand request to the user.
Step 302: the user transmits a random access preamble to the DU to request a system message.
In this step, the user sends a corresponding random access preamble according to the received configuration information (the PRACH configuration information used for requesting the system message, and the corresponding relationship between the PRACH configuration information and each system message supporting the user request as required) and the system message that the user desires to request.
Step 303: the DU sends an F1AP message (e.g., a system message request) to the CU, where the message includes PRACH configuration information (information of PRACH preamble and/or information of PRACH resource) corresponding to the random access preamble received by the DU. Alternatively, the DU may define the time when the DU receives the response message in one of the following ways:
mode 1: the message sent in step 303 contains clock information (e.g., time length information, time point information) indicating the time point at which the CU sent the response message at the latest;
mode 2: after sending the message of step 303, the DU may start a timer, and expect to receive a response message before the timer expires, and if not, it indicates that the message sent in step 303 was not successfully received by the CU.
Step 304: the CU replies a response message (e.g., a system message request response) to the DU indicating that the CU acknowledges receipt of the message sent by the DU in step 303, which is optional. In addition, optionally, one or more of the following information may also be included in the response message:
1) One or more system messages requested by the user;
2) Scheduling information for one or more system messages requested by the user.
Step 305: the DU sends a confirmation message to the user, the confirmation message representing at least one of the following meanings:
1) Confirming that the network side (CU and/or DU and/or base station) will send the system message requested by the user;
2) Confirming that the random access preamble transmitted by the user in step 302 has been received;
3) Confirming that the random access preamble transmitted by the user in step 302 has been received and learning that the user is requesting a system message;
4) Confirming that the random access preamble sent by the user in step 302 has been received, and knowing that the user is requesting a system message, and sending a corresponding request message to the CU;
5) Confirming that the random access preamble sent by the user in step 302 has been received and that the user is requesting a system message, and sending a corresponding request message to the CU, and that the CU has confirmed the user's request.
Step 306: the DU sends the user requested system messages to the user.
If there is no step 304, or no system message requested by the user is contained in the step 304, or the system message requested by the user and/or the scheduling information stored in the DU is updated, there may be a step 305a before the step 306, in which step 305a, the CU sends the system message requested by the user and/or the scheduling information of the system message to the DU, and then the DU sends the system message requested by the user to the user through the step 306.
If the CU does not send a response message to the DU in step 304, steps 305 and 306 need not be performed.
EXAMPLE III
In this embodiment, the CU notifies the DU of PRACH configuration for requesting a system message and index information of each configuration.
This embodiment describes a third method for supporting the system message requested on demand between the CU and the DU according to the present invention. In the method, a CU sends PRACH configuration for requesting system messages and index information (index) corresponding to each PRACH configuration to a DU, when the DU receives a random access preamble requesting the system messages, the CU is informed of the index information corresponding to the configuration information of the received random access preamble, the CU acquires the system messages requested by users according to the index information, and the system messages are sent to the users through the DU. The flow chart of the method is shown in fig. 4, and comprises the following steps:
step 401: the CU sends an F1 interface message to the DU, where the message includes PRACH configuration information for requesting a system message, and the configuration information includes information of a PRACH preamble and/or information of a PRACH resource (e.g., a time-frequency resource location for sending the PRACH preamble, a space resource for sending the PRACH preamble), and index information corresponding to each PRACH configuration information. For example: the message includes PRACH configuration 1 and index value 1 for requesting a system message, PRACH configuration 2 and index value 2 for requesting a system message, and the like. According to these information, the DU cannot know the correspondence between PRACH configuration and system message, but only knows that if a random access preamble matching these configurations is received, it indicates that the user is requesting system message.
Before or after this step, or in this step, it is assumed that the CU or DU has sent PRACH configuration information for requesting a system message and a correspondence between the PRACH configuration information and each system message supporting a user on-demand request to the user.
Step 402: the user sends a random access preamble to the DU to request a system message.
In this step, the user sends a corresponding random access preamble according to the received configuration information (PRACH configuration information for requesting a system message, and a corresponding relationship between the PRACH configuration information and each system message supporting the user request as needed) and the system message that the user desires to request.
Step 403: the DU sends an F1AP message (such as a system message request) to the CU, where the message includes index information of PRACH configuration information (information of PRACH preamble and/or information of PRACH resource) corresponding to the random access preamble received by the DU. Alternatively, the DU may define the time when the DU receives the response message in one of the following ways:
mode 1: the message sent in step 403 contains clock information (e.g., time length information, time point information) indicating the time point at which the CU sent the response message at the latest;
mode 2: after sending the message of step 403, the DU may start a timer, and expect to receive a response message before the timer expires, and if not, it indicates that the message sent in step 403 was not successfully received by the CU.
Step 404: the CU replies to the DU with a response message (e.g., a system message request response) that indicates that the CU acknowledged receipt of the message sent by the DU in step 403, which is optional. In addition, optionally, one or more of the following information may also be included in the response message:
1) One or more system messages requested by the user;
2) Scheduling information for one or more system messages requested by a user.
Step 405: the DU sends a confirmation message to the user, which at least represents one of the following meanings:
1) Confirming that the network side (CU and/or DU and/or base station) will send the system message requested by the user;
2) Confirming that the random access preamble transmitted by the user in step 402 has been received;
3) Confirming that the random access preamble sent by the user in step 402 has been received and learning that the user is requesting a system message;
4) Confirming that the random access preamble sent by the user in step 402 has been received, and knowing that the user is requesting for a system message, and sending a corresponding request message to the CU;
5) Confirming that the random access preamble transmitted by the user in step 402 has been received and is aware that the user is requesting a system message, and transmitting a corresponding request message to the CU, and the CU has confirmed the user's request.
Step 406: the DU sends the user requested system message to the user.
If there is no step 404, or if there is no system message requested by the user in step 404, or if the system message requested by the user and/or the scheduling information stored in the DU is updated, there may be a step 405a before step 406. In step 405a, the CU sends the system message requested by the user and/or the scheduling information of the system message to the DU, and then the DU sends the system message requested by the user to the user, again in step 406.
If the CU does not send a response message to the DU in time in step 404, steps 405 and 406 need not be performed.
Example four
In this embodiment, the CU notifies the DU of PRACH configuration for requesting a system message and indication information of a corresponding system message.
This embodiment describes a fourth method for supporting the system message requested on demand between the CU and the DU, which is provided by the present invention. In the method, a CU sends PRACH configuration for requesting system messages and indication information of the system messages corresponding to each PRACH configuration to a DU, when the DU receives a random access preamble for requesting the system messages, the DU learns the system messages requested by a user according to the PRACH configuration sent by the CU and the indication information of the system messages corresponding to the PRACH configuration, so that the CU can inform the CU of the indication information of the system messages requested by the user, accordingly, the CU learns the system messages requested by the user, and sends the system messages to the user through the DU. The flow chart of the method is shown in fig. 5, and comprises the following steps:
step 501: the CU sends an F1 interface message to the DU, where the message includes PRACH configuration information for requesting a system message, and the configuration information includes information of a PRACH preamble and/or information of a PRACH resource (for example, a time-frequency resource location for sending the PRACH preamble, and a space resource for sending the PRACH preamble), and indication information of the system message corresponding to each PRACH configuration information (the indication information may be index information of the system message). For example: the message contains PRACH configuration 1 for requesting a system message and indication information that the configuration is for requesting the system message 1, PRACH configuration 2 for requesting the system message and indication information that the configuration is for requesting the system message 2, and so on. From this information, the DU can learn the system messages that the user wants to request.
Before or after this step, or in this step, it is assumed that the CU or DU has sent PRACH configuration information for requesting a system message and a correspondence between the PRACH configuration information and each system message supporting a user on-demand request to the user.
Step 502: the user transmits a random access preamble to the DU to request a system message.
In this step, the user sends a corresponding random access preamble according to the received configuration information (PRACH configuration information for requesting a system message, and a corresponding relationship between the PRACH configuration information and each system message supporting the user request as needed) and the system message that the user desires to request.
Step 503: the DU sends F1AP messages (e.g., system message requests) to CUs that contain information indicative of the system messages requested by the user. Alternatively, the DU may define the time when the DU receives the response message in one of the following ways:
mode 1: the message sent in step 503 contains clock information (e.g., time length information, time point information) indicating the time point at which the CU sent the response message at the latest;
mode 2: after sending the message of step 503, the DU may start a timer, and expect to receive a response message before the timer expires, and if not, it indicates that the message sent in step 503 was not successfully received by the CU.
Step 504: the CU replies a response message (e.g., a system message request response) to the DU indicating that the CU acknowledges receipt of the message sent in step 503, which is optional. In addition, optionally, one or more of the following information may also be included in the response message:
1) One or more system messages requested by the user;
2) Scheduling information for one or more system messages requested by a user.
Step 505: the DU sends a confirmation message to the user, the confirmation message representing at least one of the following meanings:
1) Confirming that the network side (CU and/or DU and/or base station) will send the system message requested by the user;
2) Confirming that the random access preamble transmitted by the user in step 502 has been received;
3) Confirming that the random access preamble sent by the user in step 502 has been received and learning that the user is requesting a system message;
4) Confirming that the random access preamble sent by the user in step 502 has been received and knowing which one or more system messages the user is requesting;
5) Confirming that the random access preamble sent by the user in step 502 has been received and knowing which one or more system messages the user is requesting, and sending the request message to the CU
6) The confirmation has been received that the preamble sent by the user in step 502 and is aware of which system message or messages the user is requesting and the request message is sent to the CU and the CU has confirmed the user's request.
Step 506: the DU sends the user requested system message to the user.
If there is no step 504, or there is no system message requested by the user in step 504, or the stored system message requested by the user and/or the scheduling information in the DU is updated, there may be step 505a before step 506. In step 505a, the CU sends the system message requested by the user and/or the scheduling information of the system message to the DU, and then the DU sends the system message requested by the user to the user, again in step 506.
If the CU does not send a response message to the DU in time in step 504 above, steps 505 and 506 do not need to be performed.
Corresponding to the method, the application also provides corresponding equipment.
Fig. 6 is a schematic diagram of a configuration of a preferred base station distribution unit apparatus of the present invention, the apparatus comprising: CU interactive module, UE interactive module and storage module, wherein:
the CU interaction module is used for receiving the configuration information of the PRACH for requesting the system message from the CU;
the storage module is configured to store the configuration information of the PRACH used for requesting the system message;
and the UE interaction module is used for receiving a random access preamble for requesting the system message from the UE, determining the system message requested by the UE according to the random access preamble and the configuration information of the PRACH for requesting the system message, and sending the system message requested by the UE to the UE.
Preferably, the CU interaction module is further configured to receive at least one of the following information from the CU:
configuration information of system messages requested on demand;
index information corresponding to each PRACH configuration;
index information of the system message corresponding to each PRACH configuration information for requesting the system message.
Fig. 7 is a schematic diagram of a preferred bs hub unit according to the present invention, which includes: a DU interaction module, wherein:
and the DU interactive module is used for sending the configuration information of the PRACH for requesting the system message to the DU.
Preferably, the DU interaction module is further configured to send at least one of the following information to the DU:
configuration information of system messages requested on demand;
index information corresponding to each PRACH configuration;
index information of the system message corresponding to each PRACH configuration information for requesting the system message.
The method and the device for supporting the system message request on demand between the gNB-CU and the gNB-DU can solve the problem of how to support the transmission of the system message request on demand when the gNB is divided into the DU and the CU. The user requests the system message through the random access preamble, but the generation of the system message is completed in the CU, and the invention provides a problem how to complete the transmission of the system message requested on demand through the information interaction of the F1 interface.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.
Example 5
When the user requests the system Message through the RRC Message (that is, requests the system Message through Message 3 in the random access procedure), after receiving the RRC Message, the base station sends a contention resolution Message to the user to notify that the RRC Message sent by the user to request the system Message has been correctly received by the base station, so that the user can prepare to receive the system Message requested by the user. The Contention Resolution message is generated by the MAC layer (e.g., a message containing a Contention Resolution Identity MAC CE (Contention Resolution Identity MAC Control Element)), rather than being an RRC message. Under the structure of CU-DU separation, the DU sends the received RRC message for requesting the system message to the CU. However, in the existing mechanism, the DU cannot know whether the CU correctly receives the RRC message, and therefore, the DU cannot send a contention resolution message to the user to inform the user whether the RRC message for requesting the system message sent by the user is correctly received. To solve this problem, the present embodiment proposes the following mechanism:
the CU sends to the DU an acknowledgement message that correctly received the system information request message sent by the user, as shown in fig. 8, which is used to acknowledge to the DU that the system information request message it sent has been correctly received by the CU. A possible implementation of the confirmation message is a message that contains at least one of the following information (the following information is for one user, and if the confirmation message contains confirmation for multiple users, the message will contain at least one of the following information for each user):
→ user's identification information, such as user's identification information on DU side (gNB-DU UE F1AP ID), user's identification information in cell (C-RNTI)
→ identification of the Cell in which the user is located, such as NR CGI (NR-RAN Cell Global Identifier)
→ indication information of system information transmitted by the DU to the user, the indication information indicating the system information that the DU needs to transmit to the user
According to the above "the CU sends the confirmation message that the system information request message sent by the user is correctly received to the DU", the process that the user requests the system information through the RRC message (i.e. the method five for supporting the system information requested on demand between the CU and the DU) is as follows, as shown in fig. 9:
step 601: the user sends a system information request (systemlnforequest) message, which is an RRC message indicating the system information requested by the user, to the DU.
■ Step 602: the DU sends the system information request Message received in step 601 to the CU through a second Message, where the second Message (which may be an Initial UL RRC Message Transfer Message) may include at least one of the following information: identification information of the user, such as identification information of the user on DU side (gNB-DU UE F1AP ID), identification information of the user in the cell (C-RNTI)
■ Identification of the Cell in which the user is located, e.g. NR CGI (NR-RAN Cell Global Identifier)
■ The RRC message sent by the user is, in this embodiment, the system information request message sent in step 601
Step 603: the CU sends to the DU an acknowledgement message of correct reception of the system information request message sent by the user, which is used to acknowledge to the DU that the system information request message it sent has been correctly received by the CU. A possible implementation of the confirmation message is a message that contains at least one of the following information (the following information is for one user, and if the confirmation message contains confirmation for multiple users, the message will contain at least one of the following information for each user):
→ identification information of the user, such as identification information of the user on the DU side (gNB-DU UE F1AP ID), identification information of the user in the cell (C-RNTI)
→ the identity of the Cell in which the user is located, e.g. NR CGI (NR-RAN Cell Global Identifier)
→ indication information of system information transmitted by DU to user, which indicates the system information that DU needs to transmit to user
Step 604: the DU sends a third message to the user, where the third message is used to inform the user that the system information request sent by the user has been correctly received by the base station, and the third message may be a Contention Resolution message (e.g., a message containing a Contention Resolution Identity MAC CE (Contention Resolution Identity MAC Control Element))
Step 605: the DU may transmit the system message requested by the user to the user in a broadcast manner or in a unicast manner.
In the above steps, the order of step 604 and step 605 may be exchanged or occur simultaneously.
In the above steps, if the "indication information of the system information sent by the DU to the user" is not included in step 603, step 604 may further include the following step 604a, as shown in fig. 10 (i.e. method six for supporting the system message requested on demand between the CU and the DU):
step 604a: the CU sends a system information send command message to the DU indicating the system information that the DU is required to send to the user.
In the above steps, the order of step 604, step 604a and step 605 may be arbitrarily exchanged or may occur simultaneously.
Before step 601, step 600 may also be included, namely, the CU sends a message one to the DU, where the message includes system information and/or information related to scheduling of the system information.

Claims (10)

1. A method performed by a base station distribution unit, DU, in a wireless communication system, comprising:
receiving a second message sent by a CU, for confirming the reception of the system information request from the UE, wherein the second message comprises: identification information of the UE in the distribution unit and indication information of the system information;
and sending the system information according to the indication information of the system information included in the second message.
2. The method of claim 1, wherein the second message for acknowledging receipt of the system information request sent from the UE further comprises at least the following information:
an identity of a cell in which the UE is located.
3. The method of claim 1, wherein the system information request from the UE is included in a Message three Message 3.
4. The method of claim 1, wherein the identification information of the UE in the distribution unit comprises: and the base station distribution unit UE forward interface application protocol identifies gNB-DU UE F1AP ID.
5. The method of claim 1, wherein the third message comprises a contention resolution identity Medium Access Control (MAC) Control Element (CE).
6. A method performed by a base station concentration unit, CU, in a wireless communication system, comprising:
transmitting a second message for confirming the reception of the system information request transmitted from the UE to the base station distribution unit DU, wherein the second message includes: identification information of the UE in the distribution unit and indication information of system information required to be transmitted by the DU, which are included in the first message.
7. The method of claim 6, wherein the second message for acknowledging receipt of the system information request sent from the UE further comprises at least the following information:
an identity of a cell in which the UE is located.
8. The method of claim 6, wherein the identification information of the UE in the distribution unit comprises: and the base station distribution unit UE forward interface application protocol identifies gNB-DU UE F1AP ID.
9. A base station distribution unit, DU, comprising:
a first receiving module, configured to receive a second message sent by a CU, where the second message is used to confirm receipt of a system information request from a UE, and the second message includes: identification information of the UE in the distribution unit and indication information of the system information;
and the first sending module is used for sending the system information according to the indication information of the system information included in the second message.
10. A base station concentration unit, CU, comprising:
a second sending module, configured to send a second message to the base station distribution unit DU, where the second message is used to confirm that the system information request sent by the UE is received, and the second message includes: identification information of the UE in a distribution unit and indication information of system information required to be sent by the DU, which are included in the first message.
CN202211008566.XA 2017-06-16 2018-05-09 Method and apparatus for supporting system messages requested on demand Pending CN115296781A (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
CN201710459634 2017-06-16
CN2017104596347 2017-06-16
CN201810437646.4A CN109152086B (en) 2017-06-16 2018-05-09 Method and apparatus for supporting system messages requested on demand

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
CN201810437646.4A Division CN109152086B (en) 2017-06-16 2018-05-09 Method and apparatus for supporting system messages requested on demand

Publications (1)

Publication Number Publication Date
CN115296781A true CN115296781A (en) 2022-11-04

Family

ID=83829524

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211008566.XA Pending CN115296781A (en) 2017-06-16 2018-05-09 Method and apparatus for supporting system messages requested on demand

Country Status (1)

Country Link
CN (1) CN115296781A (en)

Similar Documents

Publication Publication Date Title
CN109152086B (en) Method and apparatus for supporting system messages requested on demand
US11700552B2 (en) Method and device for switching a serving cell and method and device supporting on-demand system information message
US10736008B2 (en) Method and apparatus for controlling handover in a wireless communication system
CN111491395B (en) Association establishment method and device
CN110213799B (en) Method and device for transmitting downlink small data
CN102342167B (en) Random access scheme for preventing unnecessary retransmission and user equipment for the same
RU2006140091A (en) METHOD AND SYSTEM FOR DISTRIBUTING A MULTIMEDIA CONTENT THROUGH A WIRELESS COMMUNICATION NETWORK, IN PARTICULAR A MOBILE PHONE COMMUNICATION NETWORK
EP3318007B1 (en) Proximity services priority control for multicast traffic in proximity services user equipment network relay scenario
US20230354110A1 (en) Method and device for switching a serving cell and method and device supporting on-demand system information message
CN102204384B (en) Method, device and communication system for requesting resource
CN102598834B (en) For the confirmation of the ul transmissions in the resource based on competition in wireless communication system
CN110061822B (en) Unicast communication channel, communication method and mobile terminal for Internet of vehicles
JP7030698B2 (en) Terminals, wireless base stations and wireless communication methods
EP3637819A1 (en) Information transmission method and apparatus
JP2019537886A (en) Method, user equipment device, processor, and base station
EP4274271A2 (en) Internet of vehicles data transmission method, transmission terminal and network side device
CN117016009A (en) Apparatus and method for providing MBS data to user equipment in cellular communication system
TWI744329B (en) Data transmission method, equipment and system
JPWO2020222283A5 (en) Base station, terminal, communication system, and communication method
CN110291839B (en) Unicast connection establishment method, device and storage medium
CN111147193B (en) Retransmission request method, terminal and network side device for Internet of vehicles
CN109587702B (en) Method and device for transmitting configuration parameters
KR20150015264A (en) Method and apparatus for distributed association of wireless networks
CN115296781A (en) Method and apparatus for supporting system messages requested on demand
US20090170513A1 (en) Mobile station, radio access network apparatus and resource request method

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination