Information transmission method, electronic apparatus, and computer program product

Abstract

Embodiments of the present disclosure provide an information transmission method, an electronic apparatus, and a computer program product. The method comprises: a first device sending first information to a second device, the first information being used for performing configuration indication for an MBS session; and the first device receiving second information from the second device, the second information being used for feeding back that the second device has successfully received or has failed to receive the first information.

Description

Information transmission methods, electronic devices and computer program products

[0001] Cross-reference to related applications

[0002] This disclosure is based on and claims priority to Chinese patent application CN202411000188.X, filed on July 24, 2024, entitled “Information Transmission Method, Electronic Device and Computer Program Product”, and incorporates the entire contents of that patent application by reference. Technical Field

[0003] This disclosure relates to the field of communications, and more specifically, to an information transmission method, electronic device, and computer program product. Background Technology

[0004] The 3GPP Rel-19 version of the Non-Terrestrial Network Work Item Description (NTN WID) discusses two aspects: regenerative payload and how to support multicast and broadcast services in NTN scenarios. However, there is no solution regarding how to support multicast / broadcast services (MBS) in scenarios where base stations or a portion of base stations are deployed on satellites. Summary of the Invention

[0005] This disclosure provides an information transmission method, electronic device, and computer program product to at least solve the problem in related technologies where it is impossible to support multicast or broadcast services in scenarios where base stations or some base stations are deployed on satellites.

[0006] According to one embodiment of this disclosure, an information transmission method is provided, comprising: a first device sending first information to a second device, wherein the first information is used to configure a multicast / broadcast service (MBS) session; the first device receiving second information from the second device, wherein the second information is used to provide feedback on whether the second device successfully received the first information or failed to receive it.

[0007] According to another embodiment of this disclosure, an information transmission method is provided, comprising: a second device receiving first information from a first device, wherein the first information is used to configure a multicast / broadcast service (MBS) session; and the second device sending second information to the first device, wherein the second information is used to provide feedback on whether the second device successfully received the first information or failed to receive it.

[0008] According to yet another embodiment of this disclosure, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0009] According to yet another embodiment of this disclosure, a computer program product is also provided, including a computer program that, when executed by a processor, implements the steps in any of the above method embodiments. Attached Figure Description

[0010] Figure 1 is a diagram of the NTN network architecture in related technologies;

[0011] Figure 2 is a hardware structure block diagram of a computer terminal for an information transmission method according to an embodiment of the present disclosure;

[0012] Figure 3 is a flowchart of an information transmission method according to an embodiment of the present disclosure;

[0013] Figure 4 is another flowchart of the information transmission method according to an embodiment of the present disclosure;

[0014] Figure 5 is a flowchart illustrating the first successful information transmission method according to an embodiment of this disclosure;

[0015] Figure 6 is a flowchart illustrating the information transmission method for the first information transmission failure according to an embodiment of this disclosure;

[0016] Figure 7 is another flowchart illustrating the information transmission method for the first information transmission failure according to an embodiment of this disclosure. Detailed Implementation

[0017] The embodiments of this disclosure will be described in detail below with reference to the accompanying drawings and examples.

[0018] It should be noted that the terms "first," "second," etc., in the specification, claims, and drawings of this disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0019] Figure 1 is a diagram of the NTN network architecture in related technologies. As shown in Figure 1, the Non-Terrestrial Network (NTN) provides New Radio (NR) access to User Equipment (UE) through the NTN payload and the NTN gateway. The figure shows the service link between the NTN payload and the UE, as well as the feed link between the NTN gateway and the NTN payload.

[0020] In related technologies, the NTN payload transparently forwards the radio protocol received from the UE (via the serving link) to the NTN gateway (via the feed link) and vice versa. The NTN payload supports the following connectivity: one NTN gateway can serve multiple NTN payloads; one NTN payload can be served by multiple NTN gateways.

[0021] In related technologies, the NR system supports resource-efficient multicast / broadcast service MBS transmission. For broadcast communication services, the same service and the same specific content data are simultaneously provided to all UEs within a geographical area (i.e., all UEs within the broadcast service area are authorized to receive data). Broadcast communication services are delivered to UEs using broadcast sessions. UEs can receive broadcast communication services in the RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED states. For multicast communication services, the same service and the same specific content data are simultaneously provided to a dedicated group of UEs (i.e., not all UEs within the MBS service area are authorized to receive data). Multicast communication services are delivered to UEs using multicast sessions. UEs can receive multicast communication services in the RRC_CONNECTED state and use mechanisms such as PTP and / or PTM transmission. HARQ feedback / retransmission can be applied to PTP and PTM transmissions.

[0022] The methods and embodiments provided in this disclosure can be executed in a mobile terminal, a computer terminal, or a similar computing device. Taking a computer terminal as an example, FIG2 is a hardware structure block diagram of a computer terminal for the information transmission method of this disclosure. As shown in FIG2, the computer terminal may include one or more (only one is shown in FIG2) processors 202 (processors 202 may include, but are not limited to, processing devices such as microprocessors MCUs or programmable logic devices FPGAs) and a memory 204 for storing data. The computer terminal may also include a transmission device 206 for communication functions and an input / output device 208. It will be understood by those skilled in the art that the structure shown in FIG2 is only illustrative and does not limit the structure of the computer terminal. For example, the computer terminal may also include more or fewer components than shown in FIG2, or have a different configuration than shown in FIG2.

[0023] The memory 204 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the information transmission method in this embodiment. The processor 202 executes various functional applications and data processing by running the computer program stored in the memory 204, thus implementing the above-described method. The memory 204 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 204 may further include memory remotely located relative to the processor 202, and these remote memories can be connected to a computer terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0024] The transmission device 206 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider for the computer terminal. In one example, the transmission device 206 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 206 may be a Radio Frequency (RF) module used for wireless communication with the Internet.

[0025] This disclosure provides an information transmission method. Figure 3 is a flowchart of the information transmission method according to this disclosure. As shown in Figure 3, the process includes the following steps:

[0026] Step S302, the first device sends first information to the second device, wherein the first information is used to provide configuration instructions for the MBS session.

[0027] In this embodiment of the disclosure, when the first device is the core network, the second device is a base station.

[0028] In this embodiment of the disclosure, when the first device is gNB-CU, the second device is gNB-DU.

[0029] In one exemplary embodiment, the first information includes at least one of the following: MBS session start time information; MBS session end time information; MBS session start location information; MBS session end location information; MBS session advanced service area information.

[0030] In this embodiment of the disclosure, the MBS session start time information may include the start time of the relevant MBS session at the receiving end (RAN node or DU). When the receiving end (RAN node or DU) discovers the start time information in the received MBS session configuration information, the receiving end (RAN node or DU) needs to start the playback service of the MBS session at the corresponding time.

[0031] In this embodiment of the disclosure, the MBS session end time information may include the end time of the relevant MBS session at the receiving end (RAN node or DU). When the receiving end (RAN node or DU) discovers the end time information in the configuration information of the received MBS session, the receiving end (RAN node or DU) needs to terminate the playback service of the MBS session at the corresponding time.

[0032] In this embodiment, the MBS session start time and end time information can be configured using at least one of the following time information formats: Timestamp: the duration of time elapsed from a specific point in time. Alternatively, countdown: a time period after which a start or stop operation begins. Or, a pre-configured timetable: both the sender and receiver have a numbered pre-configured countdown table known to each other, with different numbers corresponding to different countdown durations. The sender only sends the relevant countdown number, and the receiver automatically matches the corresponding countdown duration upon receiving the number.

[0033] In this embodiment of the disclosure, the MBS session start location information may include the start service information of the relevant MBS session at the receiver (RAN node or DU). When the receiver (RAN node or DU) moves to a position on a specific track, the receiver needs to activate the playback service of the MBS session.

[0034] In this embodiment of the disclosure, the MBS session end location information may include the end service information of the relevant MBS session at the receiver (RAN node or DU). When the receiver (RAN node or DU) moves to a position on a specific track, the receiver needs to stop the playback service of the ongoing MBS session.

[0035] In this embodiment of the disclosure, the MBS session start location information and MBS session end location information can include at least one of the following information when configured: Specific location information: which can be sent in the form of coordinates or strings. Alternatively, orbit information. The orbit information includes at least one of the following: orbit information of the relevant receiver; angle information or distance information between the receiver and determined relevant ground location information (e.g., the location of the core network, a star observation station, etc.).

[0036] In one exemplary embodiment, the MBS session advanced service area information includes at least one of the following: orbit information of the second device; MBS session start location information and / or MBS session duration; MBS session start location information and / or angle information or distance information between the second device and relevant ground location information; MBS session start location information and / or MBS session end location information.

[0037] In this embodiment of the disclosure, the MBS session advanced service area information may include the service range within which the relevant MBS session provides playback services on the receiving end (RAN node or DU). When the receiving end enters this range, it needs to enable playback services for the relevant MBS session. When the receiving end leaves this range, it needs to disable playback services for the relevant MBS session.

[0038] In one exemplary embodiment, the first information further includes at least one of the following: identification information of the first device; identification information of the MBS session indicated by the first device.

[0039] In step S304, the first device receives second information from the second device, wherein the second information is used to provide feedback on whether the second device successfully received the first information or failed to receive it.

[0040] In one exemplary embodiment, the second information includes at least one of the following: identification information of the second device; identification information of the MBS session corresponding to the second device; status information and reason information of the second device's failure to receive the first information.

[0041] In this embodiment of the disclosure, the identification information of the MBS session corresponding to the second device may include the identification information of the MBS session that was successfully transmitted corresponding to the second device, or the identification information of the MBS session that failed to be transmitted corresponding to the second device.

[0042] In one exemplary embodiment, the method further includes: the first device receiving third information from the second device, wherein the third information is used to provide feedback on the data transmission of the completed MBS session by the second device.

[0043] In this embodiment of the disclosure, after a preset time, the configuration conditions indicated by the first information of the first device are met by the second device (e.g., time, location, region, etc.). The second device needs to operate the data transmission of the corresponding MBS session according to the configuration information indicated by the previously received first information.

[0044] In this embodiment of the disclosure, after the second device completes the operation (starting / stopping the data transmission of the relevant MBS session), the second device sends a third message to the first device to notify that the corresponding operation has been completed.

[0045] In one exemplary embodiment, the third information includes at least one of the following: identification information of the MBS session corresponding to the second device; operation information of the MBS session completed by the second device.

[0046] In this embodiment of the disclosure, the third information includes at least one of the following: Second Device ID: used to identify the second device providing the information; MBS Session ID: used to identify the MBS session corresponding to the information provided to the second device; Processing info: used to notify the first device whether the operation of the relevant MBS session is to start or stop data transmission.

[0047] The above steps provide an information transmission method in which a first device sends first information to a second device, wherein the first information is used to configure an MBS session; the first device receives second information from the second device, wherein the second information is used to provide feedback on whether the second device successfully received the first information or failed to receive it. This solves the problem in related technologies where multicast or broadcast services cannot be supported in scenarios where base stations or some base stations are deployed on satellites, achieving the effect of supporting multicast or broadcast services in scenarios where base stations or some base stations are deployed on satellites.

[0048] This disclosure provides an information transmission method. Figure 4 is another flowchart of the information transmission method according to this disclosure. As shown in Figure 4, the process includes the following steps:

[0049] In step S402, the second device receives first information from the first device, wherein the first information is used to provide configuration instructions for the MBS session.

[0050] In one exemplary embodiment, after the second device receives the first information from the first device, the method further includes: if the second device successfully receives the first information, the second device updates the configuration information of the corresponding MBS session indicated by the first information.

[0051] In one exemplary embodiment, after the second device receives the first information from the first device, the method further includes: if the second device fails to receive the first information, the second device performs data transmission according to the preset configuration information of the MBS session, or the second device terminates the MBS session.

[0052] In this embodiment of the disclosure, if the second device fails to receive all the first information or does not set up completely according to the received first information, it is considered that the second device has failed to receive the first information.

[0053] In this embodiment of the disclosure, for MBS sessions that fail to receive or cannot make relevant settings, the second device will process the relevant MBS session according to the normal MBS session process (i.e., the preset MBS session configuration information) after not receiving more configuration from the first device.

[0054] In this embodiment of the disclosure, the second device may also directly choose to report failure information and cancel the entire configuration process.

[0055] In step S404, the second device sends second information to the first device, wherein the second information is used to provide feedback on whether the second device has successfully received or failed to receive the first information.

[0056] In one exemplary embodiment, after the second device receives the first information from the first device, the method further includes: the second device sending third information to the first device, wherein the third information is used to provide feedback on the second device's completion of data transmission for the MBS session.

[0057] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this disclosure, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this disclosure.

[0058] This embodiment also provides an information transmission device for implementing the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can refer to a combination of software and / or hardware that performs a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0059] The information transmission apparatus provided in this embodiment can be disposed in a first device, including a first sending module and a first receiving module. The first sending module is configured to send first information to a second device, wherein the first information is used to provide configuration instructions for an MBS session. The first receiving module is configured to receive second information from the second device, wherein the second information is used to provide feedback to the second device regarding whether the first information was successfully received or not.

[0060] The information transmission apparatus provided in this embodiment can also be disposed in a second device, including a second receiving module and a second sending module. The second receiving module is configured to receive first information from the first device, wherein the first information is used to configure an MBS session. The second sending module is configured to send second information to the first device, wherein the second information is used to provide feedback to the second device regarding whether the first information was successfully received or not.

[0061] In this embodiment of the disclosure, the information transmission device may further include different modules, and the naming and functional division of the modules may be selected in different ways according to the actual situation, without specific limitations.

[0062] It should be noted that the above modules can be implemented by software or hardware. For the latter, they can be implemented in the following ways, but are not limited to: all the above modules are located in the same processor; or, the above modules are located in different processors in any combination.

[0063] Embodiments of this disclosure also provide a computer-readable storage medium storing a computer program configured to perform the steps in any of the above method embodiments when executed.

[0064] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0065] Embodiments of this disclosure also provide an electronic device including a memory and a processor, the memory storing a computer program and the processor being configured to run the computer program to perform the steps in any of the above method embodiments.

[0066] In one exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0067] This disclosure also provides a computer program product, including a computer program that, when executed by a processor, implements the steps in any of the above method embodiments.

[0068] In one exemplary embodiment, the computer program product described above includes a non-volatile computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the methods described in various embodiments of this disclosure.

[0069] Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.

[0070] It is obvious to those skilled in the art that the modules or steps of this disclosure described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those presented herein, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, this disclosure is not limited to any particular combination of hardware and software.

[0071] To enable those skilled in the art to better understand the technical solutions disclosed herein, the following description is provided in conjunction with different embodiments.

[0072] Example 1

[0073] The embodiments disclosed herein mainly add information about the conditions under which the transmission of user data for an MBS session can be started or terminated in the messages between the core network and the base station or between the Central Unit (CU) and the Distributed Unit (DU), so that the base station (or other equipment) can transmit the user data of the relevant MBS session within a specific time and space.

[0074] In this embodiment of the disclosure, a process is described whereby a first device configures information about starting or ending a specific MBS session playback service to a second device. Specifically, the first message sent by the first device to the second device carries the relevant information about the start or end of the session.

[0075] Figure 5 is a flowchart illustrating the first successful information transmission method according to an embodiment of this disclosure. As shown in Figure 5, it includes the following steps:

[0076] Step S501: The first device sends the first information to the second device.

[0077] In this embodiment of the disclosure, the first information includes at least one of the following:

[0078] The MBS session start time information may include the start time of the relevant MBS session on the receiving end (RAN node or DU). Once the receiving end (RAN node or DU) finds the start time information in the received MBS session configuration information, it needs to start the MBS session playback service at the corresponding time.

[0079] MBS session end time information, which may include the end time of the relevant MBS session at the receiving end (RAN node or DU). When the receiving end (RAN node or DU) finds the end time information in the configuration information of the received MBS session, the receiving end (RAN node or DU) needs to end the playback service of the MBS session at the corresponding time.

[0080] For MBS session start time and end time information, the time information can be configured using at least one of the following formats: Timestamp: the duration of time elapsed from a specific point in time. Alternatively, countdown: a time period after which a start or stop operation will begin. Or, a pre-configured timetable: both the sender and receiver have a numbered set of pre-configured countdown tables, each with a unique number corresponding to a different countdown duration. The sender only sends the countdown number, and the receiver automatically matches the corresponding countdown duration upon receiving the number.

[0081] MBS session start location information, which may include the start service information of the relevant MBS session on the receiver (RAN node or DU). When the receiver (RAN node or DU) moves to a location on a specific track, the receiver needs to start the playback service of the MBS session.

[0082] MBS session end location information, which may include service termination information for the relevant MBS session at the receiver (RAN node or DU). When the receiver (RAN node or DU) moves to a location on a specific track, the receiver needs to stop playing the ongoing MBS session.

[0083] For MBS session start location information and MBS session end location information, the location information can include at least one of the following information during configuration: Specific location information: This can be sent in the form of coordinates or a string. Alternatively, orbit information. The orbit information includes at least one of the following: the orbit information of the relevant receiver; the angle or distance information between the receiver and a determined relevant ground location (e.g., the location of the core network, a star observation station, etc.).

[0084] The MBS session advanced service area information may include the service range within which the relevant MBS session provides playback services on the receiving end (RAN node or DU). When the receiving end enters this range, it needs to enable playback services for the relevant MBS session. When the receiving end leaves this range, it needs to disable playback services for the relevant MBS session.

[0085] The MBS session advanced service area information may include at least one of the following: the orbit information of the relevant receiver (i.e., the second device); the specific location information of the start of the MBS session and / or the duration of the MBS session service; the specific location information of the start of the MBS session and / or the arc information or distance information between the receiver and the relevant ground location information; the specific location information of the start of the MBS session and / or the specific location information of the end of the MBS session.

[0086] In this embodiment of the disclosure, for each involved MBS session, at least one of the following information is also included in the first information: First device identification information ID: used to determine the identifier of the first device providing the information. Alternatively, MBS session ID: used to identify the corresponding MBS session to which the relevant configuration applies.

[0087] In step S502, after receiving the first information, the second device saves the received first information and replies with the second information to inform the first device that the first information has been received normally (e.g., ACK).

[0088] In this embodiment of the disclosure, if the relevant information (i.e., the first information) has been saved before the second device, after receiving the new information, the second device needs to delete the original configuration and save the latest MBS session-related configuration corresponding to the MBS session ID.

[0089] In this embodiment of the disclosure, the second information includes at least one of the following: identification information of the second device, used to determine the identifier of the second device providing the information; or, identification information of the MBS session corresponding to the second device, used to determine the MBS session corresponding to the first information provided to the second device.

[0090] In step S503, the second device performs data transmission for the MBS session.

[0091] In this embodiment of the disclosure, after a preset time, the configuration conditions indicated by the first information of the first device are met by the second device (e.g., time, location, region, etc.). The second device needs to operate the data transmission of the corresponding MBS session according to the configuration information indicated by the previously received first information.

[0092] In step S504, the second device sends third information to the first device. The third information is used to report that the second device has completed the data transmission of the MBS session.

[0093] In this embodiment of the disclosure, after the second device completes the operation (starting / stopping the data transmission of the relevant MBS session), the second device sends a third message to the first device to notify that the corresponding operation has been completed.

[0094] At least one of the following pieces of information will be included in the third information: Second Device ID: an identifier for the second device providing the information. MBS Session ID: an identifier for the MBS session corresponding to the information provided to the second device. Processing info: used to notify the first device whether the operation of the relevant MBS session is to start or stop data transmission.

[0095] In this embodiment of the disclosure, when the first device is the core network and the second device is the base station, the first information, the second information, and the third information in NR are NGAP messages.

[0096] The first message can use predefined NGAP messages, such as: Broadcast Session Setup Request, Broadcast Session Modification Request, Multicast Session Update Request, Distribution Setup Request, Multicast Session Activation Request, and Multicast Session Deactivation Request. Alternatively, the first message can use newly defined NGAP messages, such as: Broadcast Session Suspension Request, Multicast Session Suspension Request, Broadcast Session Resume Request, Multicast Session Resume Request, or other newly defined messages.

[0097] The second message can use predefined NGAP messages, such as: broadcast session setup response, broadcast session modification response, multicast session update response, distribution setup response, multicast session activation response, and multicast session deactivation response. Alternatively, the second message can use newly defined NGAP messages, such as: broadcast session suspension response, multicast session suspension response, broadcast session resumption response, multicast session resumption response, or other newly defined messages.

[0098] In this embodiment of the disclosure, when the first device is gNB-CU and the second device is gNB-DU, the first information, the second information, and the third information in the NR are F1AP messages.

[0099] The first message can use predefined F1AP messages, such as: Broadcast Context Set Request, Broadcast Context Modify Request, Multicast Context Set Request, Multicast Context Modify Request, Multicast Distribution Set Request. Alternatively, the first message can use newly defined F1AP messages, such as: Broadcast Context Suspend Request, Multicast Context Suspend Request, Broadcast Context Resume Request, Multicast Context Resume Request, or other newly defined messages.

[0100] The second message can use predefined F1AP messages, such as: broadcast context setting response, broadcast context modification response, multicast context setting response, multicast context modification response, multicast distribution setting response. Alternatively, the second message can use newly defined F1AP messages, such as: broadcast context suspension response, multicast context suspension response, broadcast context resumption response, multicast context resumption response, or other newly defined messages.

[0101] Example 2

[0102] In Embodiment 2, the following describes how to handle the situation after the second device receives the relevant messages (i.e., the first information) of the MBS session and fails to receive the relevant information (start / stop data transmission time, location, area).

[0103] Figure 6 is a flowchart illustrating the information transmission method for information transmission failure according to an embodiment of this disclosure. As shown in Figure 6, it includes the following steps:

[0104] Step S601: The first device sends the first information to the second device.

[0105] In this embodiment of the disclosure, the first information includes at least one of the following:

[0106] The MBS session start time information may include the start time of the relevant MBS session on the receiving end (RAN node or DU). Once the receiving end (RAN node or DU) finds the start time information in the received MBS session configuration information, it needs to start the MBS session playback service at the corresponding time.

[0107] MBS session end time information, which may include the end time of the relevant MBS session at the receiving end (RAN node or DU). When the receiving end (RAN node or DU) finds the end time information in the configuration information of the received MBS session, the receiving end (RAN node or DU) needs to end the playback service of the MBS session at the corresponding time.

[0108] For MBS session start time and end time information, the time information can be configured using at least one of the following formats: Timestamp: the duration of time elapsed from a specific point in time. Alternatively, countdown: a time period after which a start or stop operation will begin. Or, a pre-configured timetable: both the sender and receiver have a numbered set of pre-configured countdown tables, each with a unique number corresponding to a different countdown duration. The sender only sends the countdown number, and the receiver automatically matches the corresponding countdown duration upon receiving the number.

[0109] MBS session start location information, which may include the start service information of the relevant MBS session on the receiver (RAN node or DU). When the receiver (RAN node or DU) moves to a location on a specific track, the receiver needs to start the playback service of the MBS session.

[0110] MBS session end location information, which may include service termination information for the relevant MBS session at the receiver (RAN node or DU). When the receiver (RAN node or DU) moves to a location on a specific track, the receiver needs to stop playing the ongoing MBS session.

[0111] For MBS session start location information and MBS session end location information, the location information can include at least one of the following information during configuration: Specific location information: This can be sent in the form of coordinates or a string. Alternatively, orbit information. The orbit information includes at least one of the following: the orbit information of the relevant receiver; the angle or distance information between the receiver and a determined relevant ground location (e.g., the location of the core network, a star observation station, etc.).

[0112] The MBS session advanced service area information may include the service range within which the relevant MBS session provides playback services on the receiving end (RAN node or DU). When the receiving end enters this range, it needs to enable playback services for the relevant MBS session. When the receiving end leaves this range, it needs to disable playback services for the relevant MBS session.

[0113] The MBS session advanced service area information may include at least one of the following: the orbit information of the relevant receiver (i.e., the second device); the specific location information of the start of the MBS session and / or the duration of the MBS session service; the specific location information of the start of the MBS session and / or the arc information or distance information between the receiver and the relevant ground location information; the specific location information of the start of the MBS session and / or the specific location information of the end of the MBS session.

[0114] In this embodiment of the disclosure, for each involved MBS session, at least one of the following information is also included in the first information: First device identification information ID: used to determine the identifier of the first device providing the information. Alternatively, MBS session ID: used to identify the corresponding MBS session to which the relevant configuration applies.

[0115] In step S602, the second device sends the second information to the first device.

[0116] In this embodiment of the disclosure, if the second device fails to receive all the first information or does not set up completely according to the received first information, it is considered that the second device has failed to receive the first information.

[0117] In this embodiment of the disclosure, the second information includes at least one of the following: identification information of the second device, used to determine the identifier of the second device providing the information; or identification information of the MBS session corresponding to the second device, used to determine the MBS session corresponding to the first information provided to the second device; or status information and reason information of the second device's failure to receive the first information.

[0118] In step S603, the second device transmits data according to the preset MBS session configuration information.

[0119] In this embodiment of the disclosure, for an MBS session that has successfully received configuration and made relevant settings, after a period of time, the configuration conditions indicated by the first information are met by the second device (e.g., time, location, region, etc.). The second device needs to operate the data transmission of the corresponding MBS session according to the previously received configuration information. For MBS sessions that have not been successfully received or cannot make relevant settings, after the second device does not receive more configuration from the first device, the second device will process the relevant MBS session according to the normal MBS session process (i.e., the preset MBS session configuration information).

[0120] In this embodiment of the disclosure, when the first device is the core network and the second device is the base station, the first information, the second information, and the third information in NR are NGAP messages.

[0121] The first message can use predefined NGAP messages, such as: Broadcast Session Setup Request, Broadcast Session Modification Request, Multicast Session Update Request, Distribution Setup Request, Multicast Session Activation Request, and Multicast Session Deactivation Request. Alternatively, the first message can use newly defined NGAP messages, such as: Broadcast Session Suspension Request, Multicast Session Suspension Request, Broadcast Session Resume Request, Multicast Session Resume Request, or other newly defined messages.

[0122] The second message can use predefined NGAP messages, such as: broadcast session setup response, broadcast session modification response, multicast session update response, distribution setup response, multicast session activation response, and multicast session deactivation response. Alternatively, the second message can use newly defined NGAP messages, such as: broadcast session suspension response, multicast session suspension response, broadcast session resumption response, multicast session resumption response, or other newly defined messages.

[0123] In this embodiment of the disclosure, when the first device is gNB-CU and the second device is gNB-DU, the first information, the second information, and the third information in the NR are F1AP messages.

[0124] The first message can use predefined F1AP messages, such as: Broadcast Context Set Request, Broadcast Context Modify Request, Multicast Context Set Request, Multicast Context Modify Request, Multicast Distribution Set Request. Alternatively, the first message can use newly defined F1AP messages, such as: Broadcast Context Suspend Request, Multicast Context Suspend Request, Broadcast Context Resume Request, Multicast Context Resume Request, or other newly defined messages.

[0125] The second message can use predefined F1AP messages, such as: broadcast context setting response, broadcast context modification response, multicast context setting response, multicast context modification response, multicast distribution setting response. Alternatively, the second message can use newly defined F1AP messages, such as: broadcast context suspension response, multicast context suspension response, broadcast context resumption response, multicast context resumption response, or other newly defined messages.

[0126] Example 3

[0127] In Embodiment 3, after the second device receives the relevant messages of the MBS session (i.e., the first information), the process of handling the failure to receive the relevant information (start / stop data transmission time, location, area) will be further described. Unlike Embodiment 2, in Embodiment 3, the second device can directly choose to report the failure information and cancel the entire configuration process.

[0128] Figure 7 is another flowchart illustrating the information transmission method for information transmission failure according to an embodiment of this disclosure. As shown in Figure 7, it includes the following steps:

[0129] Step S701: The first device sends the first information to the second device.

[0130] In this embodiment of the disclosure, the first information includes at least one of the following:

[0131] The MBS session start time information may include the start time of the relevant MBS session on the receiving end (RAN node or DU). Once the receiving end (RAN node or DU) finds the start time information in the received MBS session configuration information, it needs to start the MBS session playback service at the corresponding time.

[0132] MBS session end time information, which may include the end time of the relevant MBS session at the receiving end (RAN node or DU). When the receiving end (RAN node or DU) finds the end time information in the configuration information of the received MBS session, the receiving end (RAN node or DU) needs to end the playback service of the MBS session at the corresponding time.

[0133] For MBS session start time and end time information, the time information can be configured using at least one of the following formats: Timestamp: the duration of time elapsed from a specific point in time. Alternatively, countdown: a time period after which a start or stop operation will begin. Or, a pre-configured timetable: both the sender and receiver have a numbered set of pre-configured countdown tables, each with a unique number corresponding to a different countdown duration. The sender only sends the countdown number, and the receiver automatically matches the corresponding countdown duration upon receiving the number.

[0134] MBS session start location information, which may include the start service information of the relevant MBS session on the receiver (RAN node or DU). When the receiver (RAN node or DU) moves to a location on a specific track, the receiver needs to start the playback service of the MBS session.

[0135] MBS session end location information, which may include service termination information for the relevant MBS session at the receiver (RAN node or DU). When the receiver (RAN node or DU) moves to a location on a specific track, the receiver needs to stop playing the ongoing MBS session.

[0136] For MBS session start location information and MBS session end location information, the location information can include at least one of the following information during configuration: Specific location information: This can be sent in the form of coordinates or a string. Alternatively, orbit information. The orbit information includes at least one of the following: the orbit information of the relevant receiver; the angle or distance information between the receiver and a determined relevant ground location (e.g., the location of the core network, a star observation station, etc.).

[0137] The MBS session advanced service area information may include the service range within which the relevant MBS session provides playback services on the receiving end (RAN node or DU). When the receiving end enters this range, it needs to enable playback services for the relevant MBS session. When the receiving end leaves this range, it needs to disable playback services for the relevant MBS session.

[0138] The MBS session advanced service area information may include at least one of the following: the orbit information of the relevant receiver (i.e., the second device); the specific location information of the start of the MBS session and / or the duration of the MBS session service; the specific location information of the start of the MBS session and / or the arc information or distance information between the receiver and the relevant ground location information; the specific location information of the start of the MBS session and / or the specific location information of the end of the MBS session.

[0139] In this embodiment of the disclosure, for each involved MBS session, at least one of the following information is also included in the first information: First device identification information ID: used to determine the identifier of the first device providing the information. Alternatively, MBS session ID: used to identify the corresponding MBS session to which the relevant configuration applies.

[0140] In step S702, the second device sends the second information to the first device.

[0141] In this embodiment of the disclosure, if the second device fails to receive all the first information or does not set up completely according to the received first information, it is considered that the second device has failed to receive the first information.

[0142] In this embodiment of the disclosure, the second information includes at least one of the following: identification information of the second device, used to determine the identifier of the second device providing the information. Alternatively, the second device receives status information and reason information indicating a failure to receive the first information, wherein the status information is used to notify the first device that the configuration process cannot be processed by the second device, and the process has failed, and the reason information is used to notify the first device of the specific reason for the failure.

[0143] In this embodiment of the disclosure, when the first device is the core network and the second device is the base station, the first information, the second information, and the third information in NR are NGAP messages.

[0144] The first message can use predefined NGAP messages, such as: Broadcast Session Setup Request, Broadcast Session Modification Request, Multicast Session Update Request, Distribution Setup Request, Multicast Session Activation Request, and Multicast Session Deactivation Request. Alternatively, the first message can use newly defined NGAP messages, such as: Broadcast Session Suspension Request, Multicast Session Suspension Request, Broadcast Session Resume Request, Multicast Session Resume Request, or other newly defined messages.

[0145] The second message can use predefined NGAP messages, such as: broadcast session setup response, broadcast session modification response, multicast session update response, distribution setup response, multicast session activation response, and multicast session deactivation response. Alternatively, the second message can use newly defined NGAP messages, such as: broadcast session suspension response, multicast session suspension response, broadcast session resumption response, multicast session resumption response, or other newly defined messages.

[0146] In this embodiment of the disclosure, when the first device is gNB-CU and the second device is gNB-DU, the first information, the second information, and the third information in the NR are F1AP messages.

[0147] The first message can use predefined F1AP messages, such as: Broadcast Context Set Request, Broadcast Context Modify Request, Multicast Context Set Request, Multicast Context Modify Request, Multicast Distribution Set Request. Alternatively, the first message can use newly defined F1AP messages, such as: Broadcast Context Suspend Request, Multicast Context Suspend Request, Broadcast Context Resume Request, Multicast Context Resume Request, or other newly defined messages.

[0148] The second message can use predefined F1AP messages, such as: broadcast context setting response, broadcast context modification response, multicast context setting response, multicast context modification response, multicast distribution setting response. Alternatively, the second message can use newly defined F1AP messages, such as: broadcast context suspension response, multicast context suspension response, broadcast context resumption response, multicast context resumption response, or other newly defined messages.

[0149] The above description is merely a preferred embodiment of this disclosure and is not intended to limit this disclosure. Various modifications and variations can be made to this disclosure by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the principles of this disclosure should be included within the scope of protection of this disclosure.

Claims

1. A method for information transmission, comprising: sending, by a first device, first information to a second device, wherein the first information is used for configuration indication of a multicast / broadcast service (MBS) session; receiving, by the first device, second information from the second device, wherein the second information is used for feedback of reception success or reception failure of the first information by the second device.

2. The method of claim 1, wherein, The first information comprises at least one of: MBS session start time information; MBS session end time information; MBS session start location information; MBS session end location information; MBS session advanced service area information.

3. The method of claim 2, wherein, The MBS session advanced service area information comprises at least one of: orbit information of the second device; the MBS session start location information and / or the duration of the MBS session; the MBS session start location information and / or angle information or distance information of the second device and the related ground location information; the MBS session start location information and / or the MBS session end location information.

4. The method of claim 2, wherein, The first information further comprises at least one of: identification information of the first device; identification information of the MBS session indicated by the first device.

5. The method of claim 1, wherein, The second information comprises at least one of: identification information of the second device; identification information of the MBS session corresponding to the second device; status information and cause information of reception failure of the first information by the second device. 6.The method of claim 1, further comprising: receiving, by the first device, third information from the second device, wherein the third information is used for feedback of completion of data transmission of the MBS session by the second device.

7. The method of claim 6, wherein, The third information comprises at least one of: identification information of the MBS session corresponding to the second device; operation information of the MBS session completed by the second device. 8.A method for information transmission, comprising: receiving, by a second device, first information from a first device, wherein the first information is used for configuration indication of a multicast / broadcast service (MBS) session; sending, by the second device, second information to the first device, wherein the second information is used for feedback of reception success or reception failure of the first information by the second device.

9. The method of claim 8, wherein, After receiving the first information from the first device by the second device, the method further comprises: in the case of reception success of the first information by the second device, updating, by the second device, configuration information of the MBS session corresponding to the first information indicated by the first device.

10. The method of claim 8, wherein, After receiving the first information from the first device by the second device, the method further comprises: in the case of reception failure of the first information by the second device, performing data transmission according to preset configuration information of the MBS session by the second device, or terminating the MBS session by the second device.

11. The method of claim 8, wherein, After receiving the first information from the first device by the second device, the method further comprises: sending, by the second device, third information to the first device, wherein the third information is used for feedback of completion of data transmission of the MBS session by the second device.

12. An electronic device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the method of any one of claims 1 to 11 when executing the computer program.

13. A computer program product comprising a computer program which, when executed by a processor, implements the method of any one of claims 1 to 11.

Images