Communication method and communication apparatus

Abstract

Embodiments of the present application relate to the technical field of communications, and provide a communication method and a communication apparatus, capable of increasing the probability that a WAB-MT is authorized and providing wireless backhaul for a WAB-gNB in a timely manner. In the method, when registration is rejected, a third message may be sent again to a core network to request registration, or the core network indicates to the WAB-MT that a slice associated with a WAB node is allowed, partially allowed or partially rejected, or indicates to the WAB-MT that the slice associated with the WAB node is partially allowed; or, the core network indicates to the WAB-MT that a first slice of the WAB node is accepted for registration, wherein the first slice is used for a mobile terminal module to be in a connected state, the first slice is different from a second slice, and the second slice is used for indicating the type of the WAB node. The embodiments of the present application are used for a registration process of the WAB-MT.

Description

A communication method and a communication apparatus

[0001] The present application claims priority from the Chinese patent application No. 202411073864.6 filed on August 6, 2024, and entitled "A communication method and a communication apparatus", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The present application relates to the field of communication technology, and in particular to a communication method and a communication apparatus. BACKGROUND

[0003] A wireless access and backhaul (WAB) node includes a module of base station (gNodeB, gNB) function and a module of mobile terminal (MT) function, which can be denoted as WAB-gNB and WAB-MT. A terminal device can access the WAB-gNB through a Uu port, and data of the terminal device is routed to a core network by the WAB-MT. As a special terminal device, the WAB-MT needs to provide the WAB-gNB with the right of wireless backhaul under authorization.

[0004] The authorization of the WAB-MT can be determined by the core network based on subscription information. Specifically, in the case of determining the WAB-MT authorization based on the subscription information, the WAB-MT can be indicated as authorized by allowed network slice selection assistance information (allowed NSSAI) indicating the slice associated with the WAB-MT. In the case of determining that the WAB-MT is unauthorized based on the subscription information, the WAB-MT can be indicated as unauthorized by rejected NSSAI indicating the slice associated with the WAB-MT. If the slice applied for registration by the terminal device when initially accessing the network is indicated as rejected NSSAI, it will result in that the wireless backhaul for the WAB-gNB cannot be provided in time, and the user experience of the terminal device is affected. SUMMARY

[0005] Embodiments of the present application provide a communication method and a communication apparatus, which can improve the probability of the WAB-MT being authorized and provide the WAB-gNB with wireless backhaul in time.

[0006] In a first aspect, a communication method is provided. Optionally, an execution subject of the method can be a WAB node, or a component or device (e.g., a processor, a chip, or a chip system, etc.) applied to the WAB node, or a logical module or software capable of realizing all or part of the function of the terminal device. In this application, the execution subject of the first aspect can be a WAB-MT in the WAB node. The method comprises: sending a first message, the first message being used for a mobile terminal module (WAB-MT) of the WAB node to request registration to a core network in a registration area (RA); receiving a second message, the second message indicating that a slice associated with the WAB node is rejected for registration; and sending a third message, the third message being used for the mobile terminal module to request registration to the core network again in the registration area, the third message comprising indication information of the slice associated with the WAB node.

[0007] Thus, in the present application, if the slice associated with the WAB is initially rejected for registration, the WAB-MT will not initiate a registration request in the RA, which is different from the prior art. In the present application, the WAB-MT can attempt to register again in the RA after being rejected for registration. Once the WAB-MT sends a registration request again in a time and location where the slice associated with the WAB node is allowed to work, the WAB-MT can be accepted for registration in time, or in other words, from unlicensed to licensed, so that the WAB-MT can be connected to the network in time to provide wireless backhaul for the WAB-gNB.

[0008] In a second aspect, a communication method is provided. Optionally, an execution subject of the method can be a core network device supporting backhaul (BH), or a component or device (e.g., a processor, a chip, or a chip system, etc.) applied to the core network device, or a logical module or software capable of realizing all or part of the function of the core network device. For example, the core network device can be an access and mobility management function (AMF) network element. The method comprises: receiving a first message, the first message being used for a mobile terminal module of a wireless access backhaul (WAB) node to request registration to a core network in a registration area (RA); sending a second message, the second message indicating that a slice associated with the WAB node is rejected for registration; and receiving a third message, the third message being used for the mobile terminal module to request registration to the core network again in the registration area, the third message comprising indication information of the slice associated with the WAB node.

[0009] The beneficial effects of the second aspect can be seen from the description of the first aspect.

[0010] In the first aspect and / or the second aspect,

[0011] In a possible design, the second message includes first indication information, and the first indication information indicates that the mobile terminal module is required to carry indication information of the WAB node and / or identification information of the core network device in access layer information when next establishing a connection with the network. In this way, the BH gNB can select an AMF supporting the WAB function to perform authorization judgment for the WAB-MT at the next time when the WAB-MT accesses the network, thereby reducing the overhead caused by AMF redirection.

[0012] In a possible design, the indication information of the WAB node includes a slice identifier associated with the WAB node, and the identification information of the core network device includes a globally unique access and mobility management function identifier (GUAMI). The slice identifier associated with the WAB node can be a WAB-specific slice identifier.

[0013] In a possible design, the second message includes second indication information, and the second indication information indicates time information and / or location information in which a slice associated with the WAB node is allowed to work. In this way, the WAB-MT can attempt to register again at the allowed time and location according to the time information and the location information in which the slice associated with the WAB node is allowed to work.

[0014] In a possible design, the third message is sent at the time and / or the location in which the slice associated with the WAB node is allowed to work. In this way, in the case that the WAB-MT is rejected when initially requesting registration, the WAB-MT can change from being rejected to being accepted for registration in time and be connected to the network in time when attempting to register again according to the time information and the location information in which the slice associated with the WAB node is allowed to work.

[0015] In a third aspect, a communication method is provided. Optionally, an execution subject of the method can be a WAB node, a component or apparatus (for example, a processor, a chip, or a chip system) applied to the WAB node, or a logic module or software capable of realizing all or part of terminal device functions. In this application, the execution subject of the first aspect can be a WAB-MT or a BH-gNB in the WAB node. The method includes: sending a first message, the first message being used for a mobile terminal module of a wireless access backhaul (WAB) node to request registration with a core network; and receiving a second message, the second message being used for indicating, to the mobile terminal module, that a slice associated with the WAB node is allowed, or is partially allowed, or is partially rejected, and the second message including time information in which the slice associated with the WAB node is allowed to work; or the second message being used for indicating, to a network device accessed by the mobile terminal module, that the slice associated with the WAB node is partially allowed, and the second message including the time information and / or location information in which the slice associated with the WAB node is allowed to work.

[0016] Thus, in the present application, in one way, even if the core network determines that the WAB-MT is in a time or location that is not allowed, but the second message fed back by the core network element is equivalent to a registration acceptance message, and indicates to the WAB-MT the indication information of the slice part associated with the WAB node being allowed or partially prohibited, so that the WAB-MT can judge by itself when the time and location allowed to work, and then initiate a registration again. Or initiate a PDU establishment request to access the network. In another way, the WAB-MT does not perceive whether it is allowed to work, that is, whether the registration request initiated in the allowed time and location, but the second message received from the core network element is equivalent to a registration acceptance message, and whether the WAB-MT is allowed to work is controlled by the BH gNB according to the time information and / or location information of the slice associated with the WAB node allowed to work. In this way, both ways can flexibly control the authorization state of the WAB-MT, so that the WAB-MT can enter the network in time, and provide wireless backhaul for the WAB-gNB.

[0017] In a fourth aspect, a communication method is provided. The execution subject of the method can be a core network device supporting backhaul, a component or apparatus (such as a processor, a chip, or a chip system) applied to the core network device, or a logic module or software capable of realizing all or part of the functions of the core network device. For example, the core network device can be a BH AMF network element. The method comprises: receiving a first message, the first message being used for a mobile terminal module of a wireless access backhaul WAB node to request registration to a core network; and sending a second message, the second message being used for indicating to the mobile terminal module that a slice associated with the WAB node is allowed, or is partially allowed, or is partially refused, the second message comprising time information of the slice associated with the WAB node allowed to work; or the second message being used for indicating to a network device accessed by the mobile terminal module that the slice associated with the WAB node is partially allowed, the second message comprising time information and / or location information of the slice associated with the WAB node allowed to work.

[0018] The beneficial effects of the fourth aspect can be referred to the description of the third aspect.

[0019] In the third aspect and / or the fourth aspect:

[0020] In one possible design, the second message comprises first indication information, the first indication information indicating that the slice associated with the WAB node is partially allowed. This design is equivalent to that even if the core network determines that the WAB-MT is in a time or location that is not allowed, but the second message fed back by the core network element is equivalent to a registration acceptance message, or the WAB-MT does not perceive whether it is allowed to work, that is, whether the registration request initiated in the allowed time and location, but the second message received from the core network element is equivalent to a registration acceptance message.

[0021] In a possible design, the second message includes second indication information, and the second indication information indicates that the slice associated with the WAB node is partially rejected. Although the slice associated with the WAB node is indicated to be partially rejected, the second message is similar to the above design, and is also a registration accept message, avoiding the case that the WAB-MT cannot access the network.

[0022] In a possible design, the second message further includes third indication information and / or fourth indication information; the third indication information indicates time information during which the slice associated with the WAB node is allowed to work; and the fourth indication information indicates time information during which the slice associated with the WAB node is prohibited to work. In this way, the WAB-MT can determine the time during which the WAB-MT is allowed to initiate the registration request according to the time information during which the slice is allowed to work and / or the time information during which the slice is prohibited to work, so that the WAB-MT can be accepted for registration in time.

[0023] In a third aspect, a method for a WAB node is provided, including:

[0024] In a possible design, the method further includes: sending a third message, the third message being used for the mobile terminal module to request the core network to establish a protocol data unit (PDU) session, or the third message being used for the mobile terminal module to request registration; and the third message being sent at the time during which the slice associated with the WAB node is allowed to work. That is, the WAB-MT can initiate the PDU session or request registration at the time during which the slice is allowed to work, so that the WAB-MT can establish the PDU session in time or access the network in time, and wireless backhaul is provided for the WAB-gNB.

[0025] In a possible design, the method further includes: receiving a fifth message, the fifth message including fifth indication information and / or sixth indication information; the fifth indication information indicating that the slice associated with the WAB node is accepted for registration; and the sixth indication information indicating that the mobile terminal module carries indication information of the WAB node or identification information of the core network device in access layer information when the mobile terminal module next establishes a connection with the network. In this way, the WAB-MT can initiate the registration request again at the time and location during which the slice is allowed to work, in the case that the WAB-MT is initially not allowed to work. Alternatively, when the WAB-MT requests registration again, the BH gNB can select the core network device supporting the WAB function to authorize the WAB-MT according to the registration request message sent by the WAB-MT, reducing the overhead caused by redirection of the core network device.

[0026] In a possible design, the method further includes: sending a sixth message, where the sixth message includes data bearer resources allocated for the WAB node; and the sixth message is sent at a time and / or a location where the slice associated with the WAB node is allowed to work. In this way, when the WAB-MT receives the data bearer resources allocated by the BH gNB, the WAB-MT can establish a data bearer with the BH gNB according to the data bearer resources, to provide wireless backhaul for the WAB-gNB, i.e., backhaul traffic of the WAB-gNB, on the data bearer.

[0027] In a possible design, the method further includes: sending a seventh message, where the seventh message is used to request, from a target network device, switching of the mobile terminal module, and the seventh message includes time information and / or location information of a slice associated with the WAB node that is allowed to work. In this way, the target network device does not need to perform a procedure of establishing a context of the WAB-MT with the core network, and signaling overhead can be saved.

[0028] In a fourth aspect, a method is provided.

[0029] In a possible design, the method further includes: receiving a third message, where the third message is used by the mobile terminal module to request, from the core network, establishment of a PDU session, or the third message is used by the mobile terminal module to request, from the core network, registration; and the third message is sent at a time and / or a location where a slice associated with the WAB node is allowed to work. In this way, the WAB-MT can initiate the PDU session or request registration at the time when the slice is allowed to work, so that the WAB-MT can establish the PDU session in time or access the network in time, to provide wireless backhaul for the WAB-gNB.

[0030] In a fifth aspect, a communication method is provided. The execution subject of the method can be a WAB node, a component or apparatus (for example, a processor, a chip, or a chip system) applied to the WAB node, a logic module or software capable of implementing all or part of functions of a terminal device, or the like. In this application, the execution subject of the first aspect can be a WAB-MT in a WAB node. The method includes: sending a first message, where the first message is used by a mobile terminal module of a wireless access backhaul WAB node to request registration with a core network; and receiving a second message, where the second message indicates that a first slice of the WAB node is accepted for registration, the first slice is used for the mobile terminal module to be in a connected state, and the first slice is different from a second slice, and the second slice is used to indicate a type of the WAB node.

[0031] The second slice is equivalent to a slice associated with the WAB node in this application.

[0032] Thus, the application can make the WAB-MT pass the authorization by using the first slice in the case that the second slice authorization of the WAB-MT fails, and still enable the WAB-MT to remain in the registered state in the network, so that the WAB-MT can provide wireless backhaul for the WAB-gNB in time.

[0033] In a sixth aspect, a communication method is provided, comprising: receiving a first message, the first message being used for a mobile terminal module of a wireless access backhaul (WAB) node to request registration to a core network; and sending a second message, the second message indicating that a first slice of the WAB node is accepted for registration, the first slice being used for the mobile terminal module to be in a connected state, and the first slice being different from a second slice, the second slice being used to indicate a type of the WAB node.

[0034] The beneficial effects of the sixth aspect can be referred to the description of the fifth aspect.

[0035] In the fifth aspect and / or the sixth aspect,

[0036] In a possible design, the second message includes first indication information, the first indication information indicating that the first slice is accepted for registration. In this way, in the case that the second slice is rejected for registration, the WAB-MT can still maintain the connection with the network through the first slice.

[0037] In a possible design, the first message includes an identity of the second slice, and / or an identity of the first slice. That is, the WAB-MT can request the first slice and / or the second slice to be accepted for registration when requesting registration.

[0038] In a possible design, the second message includes second indication information, the second indication information indicating that the second slice is rejected, or is partially allowed, or is partially rejected. For example, the second indication information indicates that the second slice is a rejected NSSAI or a partially rejected NSSAI or a partially allowed NSSAI. In this way, the WAB-MT can use the second slice to request registration when requesting to enter the network next time.

[0039] In the fifth aspect,

[0040] In a possible design, in the case that the second indication information indicates that the second slice is rejected, the method further includes: receiving a third message, the third message indicating that the second slice is allowed; and the third message being received at a time and / or a location at which the second slice is allowed to work. The third message is equivalent to a configuration update command, which updates the state of the second slice to an authorized state, so that the WAB-MT can enter the network in time.

[0041] In the sixth aspect,

[0042] In a possible design, in the case where the second indication information indicates that the second slice is rejected for registration, the method further includes: sending a third message, the third message indicating that the second slice is allowed; and the third message is sent at a time and / or a location at which the second slice is allowed to work.

[0043] In a possible design, the first slice is not used for the mobile terminal module to transmit service data of the base station module of the WAB node. In this way, the network side needs to ensure that the WAB-MT does not use a PDU session established by using an identifier of the first slice to backhaul service data of the WAB-gNB. That is, only a PDU session established by using an identifier of the second slice can backhaul service data of the WAB-gNB, so as to ensure the exclusivity of the second slice for the WAB-MT.

[0044] In a seventh aspect, a communication method is provided. An execution subject of the method can be an access network device that supports or does not support serving a WAB-MT, can be a component or apparatus (for example, a processor, a chip, or a chip system) applied to the access network device, can also be a logic module or software that can realize all or part of functions of the access network device. For example, the access network device is a gNB or a BH gNB. The method includes: receiving, by the gNB, a first message, the first message indicating that RRC connection establishment of the WAB-MT is completed, and the first message including an identifier of a slice associated with the WAB node; and in the case where the gNB does not support the slice associated with the WAB node, releasing, by the gNB, the RRC connection with the WAB-MT. The gNB receiving the first message can be understood as the gNB receiving the first message sent by the WAB-MT.

[0045] In this way, when the gNB establishes the RRC connection with the WAB-MT, the gNB can determine that the RRC connection is established with one WAB-MT based on the identifier of the slice associated with the WAB node, but in the case where the gNB does not support the slice associated with the WAB node, the gNB can release the RRC connection with the WAB-MT. This is equivalent to the gNB directly rejecting the WAB-MT to access the network at the RRC connection establishment stage of the WAB-MT, so that the WAB-MT avoids accessing the BH gNB that does not support serving the WAB, and this is beneficial to guaranteeing the performance of the WAB.

[0046] In some embodiments, the first message is an RRC setup complete message, which can be understood as Msg5 in a random access procedure. The first message can also be understood as a registration request message in this application. That is, whether to support serving the WAB node can be determined when the WAB-MT establishes the connection with the gNB.

[0047] In some embodiments, the method further includes that the gNB sends a second message, and the second message indicates redirection information of the WAB node. For example, the second message is an RRC release message. In this way, in the case that the gNB does not support serving the WAB node, the WAB-MT can find a serving network device as early as possible through the redirection information, so as to facilitate the guarantee of WAB performance.

[0048] In some embodiments, the gNB does not support serving the WAB can mean that the gNB does not support configuring resource isolation between the WAB-MT and the WAB-gNB, or does not support configuring special resources for the WAB-MT as a special UE, or does not support serving the WAB node in which the WAB-MT and the WAB-gNB work in the same frequency (i.e., the backhaul link and the access link work in the same frequency).

[0049] In the eighth aspect, a communication method is provided. The execution subject of the method can be an access network device that supports or does not support serving a WAB-MT, can be a component or apparatus (such as a processor, a chip, or a chip system) applied to the access network device, can also be a logic module or software that can realize all or part of the functions of the access network device. For example, the access network device is a gNB or a BH gNB. The method includes that the gNB receives a first message, the first message requests random access, and the first message is sent on a random access channel resource configured by a slice associated with a WAB node; and in the case that the gNB does not support a slice associated with a first WAB node, the gNB determines to reject access of the WAB-MT. Wherein, the gNB receiving the first message can include that the gNB receives the first message sent by the WAB-MT.

[0050] In this way, the present application can make the WAB-MT access only a BH gNB that supports serving the WAB, so as to facilitate the guarantee of WAB performance.

[0051] In some embodiments, the first message is Msg1 in a random access procedure. That is, when initiating random access, the WAB-MT can send Msg1 on PRACH resources configured by a slice associated with a WAB node.

[0052] In some embodiments, the method further includes that the gNB does not send Msg2 to the WAB-MT, that is, does not send a random access response. Alternatively, the gNB sends a second message, and the second message indicates rejection of access of the WAB-MT. Correspondingly, the WAB-MT receives the second message.

[0053] In a ninth aspect, a communication apparatus, which can be a WAB-MT in a WAB node, is provided. The communication apparatus includes a sending unit configured to send a first message, the first message being used for a mobile terminal module of a wireless access backhaul (WAB) node to request registration to a core network within a registration area; and a receiving unit configured to receive a second message, the second message indicating that a slice associated with the WAB node is rejected for registration. The sending unit is further configured to send a third message, the third message being used for the mobile terminal module to request registration to the core network within the registration area again, the third message including indication information of the slice associated with the WAB node.

[0054] In a tenth aspect, a communication apparatus, which can be a core network device adapted to provide backhaul by a WAB network, for example, a BH AMF, is provided. The communication apparatus includes a receiving unit configured to receive a first message, the first message being used for a mobile terminal module of a wireless access backhaul (WAB) node to request registration to a core network within a registration area; and a sending unit configured to send a second message, the second message indicating that a slice associated with the WAB node is rejected for registration. The receiving unit is further configured to receive a third message, the third message being used for the mobile terminal module to request registration to the core network within the registration area again, the third message including indication information of the slice associated with the WAB node.

[0055] In the ninth aspect and / or the tenth aspect,

[0056] In a possible design, the second message includes first indication information, the first indication information indicating that, when the mobile terminal module establishes connection with the network next time, the indication information of the WAB node and / or identification information of the core network device is carried in access stratum information.

[0057] In a possible design, the indication information of the WAB node includes a slice identifier associated with the WAB node; and the identification information of the core network device includes a globally unique access and mobility management function identifier (GUAMI).

[0058] In a possible design, the second message includes second indication information, the second indication information indicating time information and / or location information in which the slice associated with the WAB node is allowed to work.

[0059] In a possible design, the third message is sent in the time and / or the location in which the slice associated with the WAB node is allowed to work.

[0060] In an eleventh aspect, a communication apparatus, which can be a WAB-MT in a WAB node or a BH-gNB, is provided. The communication apparatus includes: a sending unit configured to send a first message, the first message being used for a mobile terminal module of a wireless access backhaul (WAB) node to request registration with a core network; and a receiving unit configured to receive a second message, the second message being used for indicating to the mobile terminal module that a slice associated with the WAB node is allowed, or is partially allowed, or is partially rejected, the second message including time information of a time period during which the slice associated with the WAB node is allowed to work, or the second message being used for indicating to a network device accessed by the mobile terminal module that the slice associated with the WAB node is partially allowed, the second message including the time information of the time period during which the slice associated with the WAB node is allowed to work and / or location information.

[0061] In a twelfth aspect, a communication apparatus, which can be a core network device in a WAB network, for example, a BH AMF, is provided. The communication apparatus includes: a receiving unit configured to receive a first message, the first message being used for a mobile terminal module of a wireless access backhaul (WAB) node to request registration with a core network; and a sending unit configured to send a second message, the second message being used for indicating to the mobile terminal module that a slice associated with the WAB node is allowed, or is partially allowed, or is partially rejected, the second message including time information of a time period during which the slice associated with the WAB node is allowed to work, or the second message being used for indicating to a network device accessed by the mobile terminal module that the slice associated with the WAB node is partially allowed, the second message including the time information of the time period during which the slice associated with the WAB node is allowed to work and / or location information.

[0062] In the eleventh aspect and / or the twelfth aspect,

[0063] In a possible design of the eleventh aspect and / or the twelfth aspect, the second message includes first indication information, the first indication information indicating that the slice associated with the WAB node is partially allowed.

[0064] In a possible design of the eleventh aspect and / or the twelfth aspect, the second message includes second indication information, the second indication information indicating that the slice associated with the WAB node is partially rejected.

[0065] In a possible design of the eleventh aspect and / or the twelfth aspect, the second message further includes third indication information and / or fourth indication information, the third indication information indicating the time information of the time period during which the slice associated with the WAB node is allowed to work, and the fourth indication information indicating time information of a time period during which the slice associated with the WAB node is prohibited to work.

[0066] In the eleventh aspect,

[0067] In one possible design, the sending unit is also used to send a third message, which is used by the mobile terminal module to request the core network to establish a Protocol Data Unit (PDU) session, or by the mobile terminal module to request registration with the core network; the third message is sent during the time when the slice associated with the WAB node is allowed to operate.

[0068] In one possible design, the receiving unit is also configured to receive a fifth message, which includes a fifth indication information and / or a sixth indication information; the fifth indication information indicates that the slice associated with the WAB node has been accepted for registration; the sixth indication information indicates that the mobile terminal module will carry the WAB node's indication information or the core network device's identification information in the access layer information when it establishes a connection with the network again.

[0069] In one possible design, the sending unit is also used to send a sixth message, which includes data bearer resources allocated to the WAB node; the sixth message is sent at the time and / or location where the slice associated with the WAB node is allowed to work.

[0070] In one possible design, the sending unit is also used to send a seventh message, which is used to request the target network device to switch the mobile terminal module. The seventh message includes time information and / or location information of the slice associated with the WAB node that is allowed to work.

[0071] In the twelfth aspect:

[0072] The receiving unit is also used to receive a third message, which is used by the mobile terminal module to request the core network to establish a PDU session, or by the mobile terminal module to request registration with the core network; the third message is sent at the time and / or location when the slice associated with the WAB node is allowed to work.

[0073] In a thirteenth aspect, a communication device is provided, which can be a WAB-MT in a WAB node. The communication device includes: a transmitting unit for transmitting a first message, the first message being used for a mobile terminal module of the wireless access backhaul WAB node to request registration from the core network; and a receiving unit for receiving a second message, the second message indicating that a first slice of the WAB node has been accepted for registration, the first slice being used for the mobile terminal module to be in a connected state, and the first slice being different from the second slice, the second slice being used to indicate the type of the WAB node.

[0074] In a fourteenth aspect, a communication apparatus is provided, which can be a core network device in a WAB network, for example, a BH AMF. The communication apparatus includes: a receiving unit, configured to receive a first message, the first message being used for a mobile terminal module of a wireless access backhaul (WAB) node to request registration to a core network; and a sending unit, configured to send a second message, the second message indicating that a first slice of the WAB node is accepted for registration, the first slice being used for the mobile terminal module in a connected state, and the first slice being different from a second slice, the second slice being used to indicate a type of the WAB node.

[0075] In the thirteenth aspect and / or the fourteenth aspect,

[0076] In a possible design, the second message includes first indication information, the first indication information indicating that the first slice is accepted for registration.

[0077] In a possible design, the first message includes an identity of the second slice, and / or an identity of the first slice.

[0078] In a possible design, the second message includes second indication information, the second indication information indicating that the second slice is rejected, or is partially allowed, or is partially rejected.

[0079] In the thirteenth aspect,

[0080] In a possible design, in a case where the second indication information indicates that the second slice is rejected, the receiving unit is further configured to receive a third message, the third message indicating that the second slice is allowed; and the third message is received at a time and / or a location at which the second slice is allowed to work.

[0081] In the fourteenth aspect,

[0082] In a possible design, in a case where the second indication information indicates that the second slice is rejected for registration, the sending unit is further configured to send a third message, the third message indicating that the second slice is allowed; and the third message is sent at a time and / or a location at which the second slice is allowed to work.

[0083] In a fifteenth aspect, a communication apparatus is provided, which can be an access network device. The communication apparatus includes: a receiving unit, configured to receive a first message, the first message indicating that a radio resource control (RRC) connection establishment of a WAB-MT is completed, and the first message including an identity of a slice associated with a WAB node; and a processing unit, configured to release the RRC connection with the WAB-MT in a case where the slice associated with the WAB node is not supported.

[0084] In some embodiments, the communication apparatus further includes a sending unit, configured to send a second message, the second message indicating redirection information of the WAB node.

[0085] In a sixteenth aspect, a communication apparatus is provided, which can be an access network device. The communication apparatus includes: a receiving unit, configured to receive a first message, the first message requesting random access, the first message being sent on a random access channel resource configured by a slice associated with a WAB node; and a processing unit, configured to determine to reject WAB-MT access in a case that the gNB does not support the slice associated with the first WAB node.

[0086] In some embodiments, the communication apparatus further includes a sending unit, configured to not send a Msg2, i.e., a random access response, to the WAB-MT. Alternatively, the sending unit is configured to send a second message, the second message indicating rejection of the WAB-MT access.

[0087] In a seventeenth aspect, a communication apparatus is provided, including at least one processor and a memory connected to the at least one processor, the at least one processor being configured to read and execute a program stored in the memory, so that the apparatus performs the method of any one of the first aspect to the eighth aspect, or the method of any possible design of the first aspect to the eighth aspect.

[0088] In an eighteenth aspect, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions, when the computer instructions are executed on a communication apparatus, causing the communication apparatus to perform the method of any one of the first aspect to the eighth aspect, or the method of any possible design of the first aspect to the eighth aspect.

[0089] In a nineteenth aspect, a computer program product is provided, including computer instructions, when the computer instructions are executed on a communication apparatus, causing the communication apparatus to perform the method of any one of the first aspect to the eighth aspect, or the method of any possible design of the first aspect to the eighth aspect. BRIEF DESCRIPTION OF DRAWINGS

[0090] FIG. 1 is a schematic diagram of a VMR scenario in a network architecture of a WAB according to an embodiment of the present application;

[0091] FIG. 2 is a schematic diagram of a network architecture of a WAB node according to an embodiment of the present application;

[0092] FIG. 3 is a schematic diagram of a partially allowed slice according to an embodiment of the present application;

[0093] FIG. 4 is a flowchart of a communication method according to an embodiment of the present application;

[0094] FIG. 5 is a flowchart of a communication method according to an embodiment of the present application;

[0095] FIG. 6 is a flowchart of a communication method according to an embodiment of the present application;

[0096] FIG. 7 is a flow diagram of a communication method according to an embodiment of the present application;

[0097] FIG. 8 is a schematic diagram of an O-RAN architecture according to an embodiment of the present application;

[0098] FIG. 9 is a schematic diagram of an interaction process between BH gNBs in an O-RAN architecture according to an embodiment of the present application;

[0099] FIG. 10 is a schematic diagram of a communication apparatus according to an embodiment of the present application;

[0100] FIG. 11 is a schematic diagram of a communication apparatus according to an embodiment of the present application. DETAILED DESCRIPTION

[0101] Embodiments of the present application can be applied to a network architecture of wireless access and backhaul (WAB). The network architecture of WAB is being studied in a topology enhancement scheme, and the main scenario is a vehicle mounted relay (VMR) scenario, i.e., a relay node is deployed on a vehicle, such as a car or even an airplane, to provide wireless coverage for terminals within the vehicle to overcome the problem of poor wireless signals within the vehicle. The relay node can access a macro station through wireless backhaul, and the macro station is a backhaul base station (gNodeB, gNB) for example. As shown in FIG. 1, which is a schematic diagram of a VMR scenario in a network architecture of WAB, the medical vehicle 101, the bus 102, and the engineering vehicle 103 shown in FIG. 1 can all be arranged with relay nodes (e.g., 110-112), which can access a radio access network (RAN) including BH gNBs 104, 105, and 106, respectively, to provide wireless coverage for terminals 107-109 within the vehicles.

[0102] The relay node can be referred to as a WAB node, and as shown in FIG. 2, which is a schematic diagram of a network architecture 200 of a WAB node. The network architecture 200 includes a terminal, a WAB node, a BH gNB, a BH access and mobility management function (AMF) network element, a BH user plane function (UPF) network element, an AMF network element of a terminal or gNB, and a UPF network element of a terminal.

[0103] The terminal is a device with wireless transceiver function, which can send signals to the base station or receive signals from the base station. The terminal can also be referred to as a terminal device, user equipment (UE), mobile station, mobile terminal, etc. The terminal can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), internet of things (IOT), virtual reality, augmented reality, industrial control, automatic driving, remote medical treatment, smart grid, smart furniture, smart office, smart wear, smart transportation, smart city, etc. The terminal can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a wearable device, a vehicle, an airplane, a ship, a robot, a mechanical arm, a smart home device, etc. The embodiments of the present application do not limit the specific technology and specific device form of the terminal.

[0104] As shown in FIG. 2, the WAB node includes a module of gNB function and a module of mobile terminal (MT) function, which can be denoted as WAB-gNB and WAB-MT. The WAB-gNB can provide access services for the terminal, and the WAB-MT can provide wireless backhaul for the WAB-gNB.

[0105] The BH gNB can be used as a host gNB to support WAB access and transmit service data of the WAB-MT.

[0106] The BH-AMF network element can be understood as a service AMF network element of the WAB-MT, which is responsible for the authorization of the WAB-MT.

[0107] The data backhaul process of the UE data in the network architecture 200 is exemplarily described below taking the terminal as an example.

[0108] The UE can access the WAB-gNB through the Uu interface, the data of the UE is wrapped in the packet data unit (PDU) session message of the WAB-MT by the WAB-MT, the PDU session message is sent to the BH UPF network element through the Uu interface between the WAB-MT and the BH gNB and the N3 interface between the BH-gNB and the BH UPF network element. The BH UPF network element can parse the WAB-MT related data packet header information to obtain the UE related data packet header information, and the BH UPF network element sends the UE related data to the UPF network element of the UE through the N6 interface according to the IP routing information. The UPF network element of the UE sends the UE related data to the UE. From the logic shown in FIG. 2, the terminal and the UPF network element of the terminal can also establish a terminal PDU session, but it should be understood that the UE related data sent by the UPF network element of the UE is transmitted in the MT PDU session established by the WAB-MT.

[0109] In the WAB, in the case where the data of the UE is directly wrapped in the PDU session of the WAB-MT for transmission, the data of the UE is regarded as the user plane data of the WAB-MT itself in the WAB-MT backhaul process, and after the data of the WAB-MT reaches the BH gNB through the data radio bearer (DRB) of the WAB-MT, the BH gNB can only parse the data of the WAB-MT and cannot obtain the data of the UE. After the BH gNB sends the data received from the WAB-MT to the BH UPF network element, the BH UPF network element can parse the WAB-MT related packet header and obtain the UE related packet header information. The BH UPF network element forwards the UE related packet header information to the UPF network element of the UE.

[0110] The above only illustrates how the UE transmits user plane data to the UPF network element of the UE, and the control plane data transmission between the WAB-gNB and the AMF network element of the WAB-gNB is similar. The control plane data is also wrapped in the PDU session of the WAB-MT and forwarded to the AMF network element of the WAB-gNB by the UPF network element of the WAB-MT through IP routing.

[0111] In order to facilitate understanding of the embodiments of the present application, the concept of network slicing is introduced first. The network slicing can also be applied to the scenario shown in FIG. 1 and the network architecture 200 shown in FIG. 2.

[0112] Network slice is an end-to-end concept introduced in the 5th-generation mobile communication technology (5G) and can provide end-to-end resource isolation for the services of a UE. When registering in the network, the UE can carry at least one slice identity, i.e., single network slice selection assistance information (S-NSSAI), in the non-access stratum (NAS) message of the registration request. The AMF network element can determine whether these slices are allowed to be used by the UE in the registration area (RA) based on the subscription information. If the AMF network element determines that there are slices allowed to be used by the UE in the RA, a registration accept message is returned to the UE, the registration of the UE is accepted, and it is indicated in the registration accept message whether each slice requested by the UE is allowed to be used. For the slices allowed to be used by the UE, the allowed NSSAI is indicated, and for the slices not allowed to be used, the rejected NSSAI is indicated. After the UE is accepted to register, the registration state (RM-REGISTERED) is maintained between the UE and the core network. If the AMF network element determines that none of the slices requested by the UE is allowed to be used, a registration reject message is returned to the UE, all slice identities are indicated as the rejected NSSAI, the UE is in the deregistered state (RM-DEREGISTERED), and there is no connection between the UE and the network.

[0113] The UE can also not carry any slice identity in the registration request when registering in the network, in which case the AMF can directly allocate a default slice identity for the UE based on the subscription information of the UE and carry it in the registration accept message as the allowed NSSAI. Of course, in the case where the UE does not carry any slice identity in the registration request, if the AMF finds that the UE has no available slice based on the subscription information of the UE, a registration reject message is returned to the UE, and the UE is deregistered.

[0114] In the case that the core network divides the geographical area into different tracking areas (TA), the slices are deployed homogeneously within a TA. The meaning of homogeneously deployed is that all base stations within the range of a TA support the same slices. The RA of a UE is represented by a list of TAs, and the slices supported within one TA are the same. But within the RA of a certain UE (containing multiple TAs), not all base stations in the TAs necessarily support the same slices. Considering that the AMF needs to "determine whether these slices are allowed to be used by the UE within the RA of the UE", before Rel-18, specifically, the AMF network element needs to query whether all TAs within the RA support the slice, and only in the case that all TAs support the slice, it is considered to be an allowed NSSAI, and a registration accept is replied. For a rejected NSSAI, the UE will not initiate a registration request again within the RA, and only when the UE moves out of the RA (i.e., the UE moves to a cell whose broadcasted TAC (tracking area code) does not belong to the TA List configured for the UE), the UE will perform a TAU (tracking area update, also known as registration update) to re-request the registration of each slice.

[0115] In Rel-18, in order to improve the flexibility of slices, the concept of partially allowed NSSAI (partially allowed network slice selection support information / partially allowed slice) is introduced. As shown in FIG. 3 is a schematic diagram of a partially allowed slice, wherein range 301 represents the RA of the UE, and each area 302 represents a TA. For example, for a partially allowed slice requested by the UE: slice#2 (including the case that the UE is located in the allowed range of slice#2 when initiating registration and is not located in the allowed range of slice#2), if some TAs in the RA of the UE support slice 2 and some TAs do not support slice 2, the AMF network element can still reply to the UE with a registration accept and indicate that this slice#2 is partially allowed NSSAI, and indicate the TA List in which slice#2 is allowed to work. If the UE is located in the TA List in which slice#2 is allowed to work, the UE can initiate a PDU session establishment request with slice#2, and if the UE is not located in the TA List in which slice#2 is allowed to work, the UE can directly initiate a PDU session establishment request with slice#2 when the UE moves to the TA List in which slice#2 is allowed to work, and in this case, there is no need to re-initiate a registration update with slice#2, the registration of slice#2 has been passed, and the UE can directly initiate a PDU session establishment request with slice#2. Alternatively, if the UE is not located in the TA List in which slice#2 is allowed to work when initiating registration, the network can also not use the above partially allowed scheme (determined by the network implementation), but reply to the UE with a registration reject message and indicate that slice#2 is partially rejected NSSAI, and indicate the TA List in which slice#2 is prohibited to work. When the UE moves out of the TA List in which slice#2 is prohibited to work, the UE re-initiates a registration update with slice#2.

[0116] It should be understood that the main difference between partially allowed and partially rejected is that partially allowed is carried in the registration accept message, and the UE directly initiates a PDU session establishment with this slice afterwards, while partially rejected is carried in the registration reject message, and the UE needs to re-register this slice through registration update afterwards.

[0117] In the network architecture of WAB, the WAB-MT in WAB node also needs to be "authorized" as a special UE, which can be understood as granting the WAB-MT the right to provide wireless backhaul for the WAB-gNB. In some scenarios, the authorization of the WAB-MT is carried out by the core network of the WAB-MT. The SA2 working group has agreed that the authorization of the WAB-MT is based on network slicing. That is, an associated slice needs to be introduced for the WAB-MT, and the identity of the associated slice can be understood as a WAB dedicated S-NSSAI, which is used to indicate the type of WAB node. The AMF network element of the WAB-MT can determine whether the WAB-MT is authorized based on subscription information. Among them, whether the WAB-MT is authorized can be related to time and / or space. That is, the WAB-MT can be allowed to provide wireless backhaul as a WAB-MT in some areas or at some times, and not allowed to provide wireless backhaul as a WAB-MT in other areas or at other times. For example, the WAB-MT deployed on the bus stop is only allowed to be operational on the bus line and during the operating time.

[0118] If the WAB-MT is authorized, the AMF network element of the WAB-MT can feed back a registration accept message to the WAB-MT through the BH gNB, indicating that the WAB-MT is allowed to register, and indicating that the WAB associated slice is allowed NSSAI; if the WAB-MT is unauthorized, the AMF network element of the WAB-MT can feed back a registration reject message to the WAB-MT through the BH gNB, and indicate that the WAB associated slice is rejected NSSAI.

[0119] However, if the WAB associated slice is allowed NSSAI indicates that the WAB-MT is authorized, and the WAB associated slice is rejected NSSAI indicates that the WAB-MT is unauthorized, the following problem of not being able to enter the network will exist. This is because, according to the protocol, if the slice applied for registration by the UE when initially entering the network is indicated as rejected NSSAI, the UE will not attempt to initiate registration using this slice again within the RA. In this way, in the network architecture of WAB, the unauthorized WAB-MT will actually move to a time or space where authorization is allowed, but since it does not move out of the RA, the WAB-MT still cannot re-initiate registration, resulting in the WAB-MT being unable to be authorized, that is, the WAB-MT cannot enter the network to provide wireless backhaul for the WAB-gNB.

[0120] Therefore, in the present application, for the problem that the WAB-MT cannot access the network at an unlicensed time, a communication method and a communication device are provided, in which a plurality of possible registration methods of the WAB-MT are provided for the WAB-MT in the WAB node, the probability of authorization of the WAB-MT is improved, and the WAB-MT can be connected to the network in time to provide wireless backhaul for the WAB-gNB.

[0121] In the present application, the WAB-MT registration request can be understood as a WAB-MT authorization request, the WAB-MT registration acceptance has a similar meaning to the WAB-MT authorization, and the WAB-MT registration rejection has a similar meaning to the WAB-MT non-authorization.

[0122] As shown in FIG. 4, a flowchart of a communication method provided by an embodiment of the present application is shown, which is used to change the unlicensed state to the authorized state in time for the WAB-associated slice, the present application allows the registration to be tried again in the RA when the WAB-associated slice is rejected. In this way, the WAB-MT can be connected to the network in time when changing from unlicensed to authorized. The method includes the following processes.

[0123] 401. The mobile terminal module (WAB-MT) of the WAB node sends a first message, and the first message is used for the WAB-MT to request registration to the core network in the RA.

[0124] Correspondingly, the core network device receives the first message. For example, the core network device is a BH AMF.

[0125] In some embodiments, the first message is a registration request message. The WAB-MT sending the first message includes that the WAB-MT sends the registration request message to the BH AMF network element through the BH gNB. The registration request message is used for the WAB-MT to request registration to the core network in the RA.

[0126] Optionally, the registration request message carries a slice identifier associated with the WAB node. The slice associated with the WAB node is used to indicate that the registration request is a WAB-MT type of UE.

[0127] Alternatively, the registration request message does not carry the slice identity associated with the WAB node, the BH AMF can determine whether the UE requesting registration is a WAB-MT type of UE by querying the subscription information of the WAB node from a unified data management (UDM) network element. For example, the BH AMF can query whether the UE requesting registration is a WAB-MT type of UE through other identifiers of the WAB-MT carried in the registration request message, such as the card number of the WAB-MT.

[0128] 402、The core network device sends a second message, and the second message indicates that the slice associated with the WAB node is rejected for registration.

[0129] Correspondingly, the WAB-MT receives the second message.

[0130] In some embodiments, the second message is a registration reject message.

[0131] For example, when it is determined that the WAB-MT is rejected for registration, the BH AMF network element can send a registration reject message to the WAB-MT through the BH gNB, the registration reject message includes the slice identity associated with the WAB node, and indicates that the slice associated with the WAB node is rejected for registration, that is, the slice associated with the WAB node is a rejected NSSAI.

[0132] For example, the BH AMF network element can send a registration reject message to the WAB-MT, if it is determined according to the subscription information of the WAB node that the UE requesting registration is not a WAB-MT type. Alternatively, the BH AMF network element determines that the WAB-MT is legal if it is determined according to the subscription information of the WAB node that the UE requesting registration is a WAB-MT type. However, at the same time, if the BH AMF network element determines that the WAB-MT sends the registration request message at an unallowed time or in an unallowed space, the BH AMF network element determines that the WAB-MT is unauthorized or rejected for registration, and the BH-AMF network element sends a registration reject message to the WAB-MT through the BH gNB. Similarly, if the BH AMF network element determines according to the subscription information of the WAB node that the UE requesting registration is a WAB-MT type, and the WAB-MT sends the registration request message at an allowed time and space, the BH AMF network element can directly send a registration accept message to the WAB-MT through the BH gNB, so that the WAB-MT initiates a PDU session establishment request.

[0133] In some embodiments, in the case where the BH AMF network element determines that the WAB-MT is unauthorized, the second message includes first indication information, and the first indication information indicates that the WAB-MT carries indication information of the WAB node and / or identification information of the core network device in access stratum (AS) information when the WAB-MT establishes a connection with the network next time.

[0134] In some embodiments, the indication information of the WAB node includes a slice identifier associated with the WAB node; and the identification information of the core network device includes a globally unique AMF identifier (GUAMI). The core network device is the BH AMF network element.

[0135] This is considering that if step 401 is WAB-MT initial registration, the indication information of the WAB node may not be carried in the first message, indicating that a WAB-MT type UE is requested to register. At this time, the BH gNB will randomly select a BH AMF network element for the WAB-MT. If the randomly selected BH AMF network element does not support WAB function, the BH gNB needs to perform AMF redirection and reselect a BH AMF, which will increase the delay and signaling overhead. At this time, the BH AMF network element has determined according to the subscription information that the request for registration is a WAB-MT, therefore, the BH AMF network element can indicate the WAB-MT in step 402 through the registration reject message, and the next time the WAB-MT establishes a connection with the network, the indication information that it is a WAB node needs to be carried in the access layer information, or the GUAMI of the BH AMF can be carried in the registration reject message, which can be used for the BH gNB to select an AMF supporting WAB function at one time when the WAB-MT requests registration next time, or when the BH gNB already knows that the last randomly selected BH AMF network element is a network element supporting WAB function, the last randomly selected BH AMF GUAMI can be directly carried in the registration reject message for WAB MT registration.

[0136] In this way, the BH gNB can select an AMF supporting WAB function at one time for the WAB-MT to perform authorization judgment when the WAB-MT enters the network next time, reducing the overhead caused by AMF redirection.

[0137] In some embodiments, the second message includes second indication information, and the second indication information indicates time information and / or location information in which a slice associated with the WAB node is allowed to work.

[0138] For example, the registration reject message sent by the BH-AMF network element to the WAB-MT through the BH gNB can also include second indication information indicating time information and / or location information in which the WAB-MT is allowed to work. For example, the registration reject message includes a slice identifier associated with the WAB node and time information and location information in which the slice identifier associated with the WAB node is allowed to work, so that the WAB-MT can attempt to register again at the allowed time and location according to the time information and location information in which the slice identifier associated with the WAB node is allowed to work. In this way, the WAB-MT can be registered in time according to the time information and location information in which the slice identifier associated with the WAB node is allowed to work from being rejected to being accepted for registration in the case of initial registration being rejected, and timely connect with the network.

[0139] For example, the BH-AMF network element can be preconfigured with time information and location information in which the WAB-MT is allowed to work, and the BH-AMF network element also supports a function of determining the location of the WAB-MT.

[0140] The location information may, for example, be indicated by a TA.

[0141] 403. The WAB-MT sends a third message, the third message being used by the WAB-MT to request registration again from the core network within the RA, and the third message including indication information of a slice associated with the WAB node.

[0142] Correspondingly, the core network device receives the third message. The third message may, for example, be a registration request message.

[0143] In some embodiments, the WAB-MT can periodically send a registration request message to the BH AMF within the RA, and the BH AMF network element is indicated by the BH gNB in the registration reject message.

[0144] Alternatively, in some embodiments, the third message is sent at a time and / or location in which the slice associated with the WAB node is allowed to work. That is, the WAB-MT can send a registration request message to the BH AMF network element at a time and location in which the slice associated with the WAB node is allowed to work, based on the second message.

[0145] Optionally, the third message carries indication information of the slice associated with the WAB node. If the indication information of the WAB node carried by the WAB-MT when establishing a connection with the network next time is carried in the second message, the third message carries indication information of the slice associated with the WAB node.

[0146] The indication information of the slice associated with the WAB node is the indication information of the WAB node, and both may, for example, be an identifier of the slice associated with the WAB node.

[0147] Thus, in the present application, unlike in the prior art, if the slice associated with the WAB is initially in an unauthorized state, the present application can attempt to register again within the RA after the WAB-MT is rejected for registration, and once the WAB-MT sends a registration request when attempting to register again at a time and location in which the slice associated with the WAB node is allowed to work, the WAB-MT can be changed from being rejected for registration to being accepted for registration in a timely manner, or from being unauthorized to being authorized, so that the WAB-MT can be connected to the network in a timely manner, and wireless backhaul is provided for the WAB-gNB.

[0148] As shown in FIG. 5, a flowchart of a communication method provided by an embodiment of the present application is shown. The method can enable the WAB-MT to initiate registration again, initiate a PDU establishment request, or be allocated resources by the BH gNB in a time and location where work is allowed, when the WAB-MT initiates the initial request for registration in a time and location where work is not allowed.

[0149] In the method, the BH AMF network element can indicate the time and / or spatial range of the WAB-MT authorization to the WAB-MT through the partially allowed or partially rejected slice, so as to enable the WAB-MT to determine whether to initiate a PDU session establishment request or a registration request based on the information of the two dimensions of time and space.

[0150] Alternatively, the BH AMF network element can indicate the time and / or spatial range of the WAB-MT authorization to the BH gNB through the partially allowed slice, so as to enable the BH gNB to determine whether to allocate resources to the WAB-MT based on the time and / or spatial range of the WAB-MT authorization.

[0151] As shown in FIG. 5, the method includes the following processes.

[0152] 501. The WAB-MT sends a first message, and the first message is used for the WAB-MT to request registration from the core network. Then, step 502 or step 504 is performed.

[0153] The implementation of step 501 can refer to the description in step 401.

[0154] 502. The core network device sends a second message, and the second message is used for the WAB-MT to indicate that the slice associated with the WAB node is allowed, or partially allowed, or partially rejected, and the second message includes time information of the slice associated with the WAB node allowed to work.

[0155] In some embodiments, in the case of the core network device being a BH AMF network element, the core network device sending the second message includes: the BH AMF network element sending the second message to the WAB-MT through the BH gNB.

[0156] In some embodiments, the second message includes first indication information, and the first indication information indicates that the slice associated with the WAB node is partially allowed.

[0157] Alternatively, the second message includes second indication information, and the second indication information indicates that the slice associated with the WAB node is partially rejected.

[0158] Exemplarily, the second message is a registration accept message or a registration reject message. The registration accept message or the registration reject message can carry the indication information that the slice associated with the WAB node is partially allowed or the indication information that the slice associated with the WAB node is partially rejected as the first indication information or the second indication information, to indicate that the slice associated with the WAB node is partially allowed or partially rejected.

[0159] In some embodiments, the second message further comprises third indication information and / or fourth indication information.

[0160] The third indication information indicates time information during which the slice associated with the WAB node is allowed to work.

[0161] The fourth indication information indicates time information during which the slice associated with the WAB node is prohibited to work.

[0162] Exemplarily, the BH AMF network element sends a registration accept message to the WAB-MT through the BH gNB, and the registration accept message comprises the indication information of the WAB node, for example, the indication information of the WAB node is the indication information that the slice associated with the WAB node is partially allowed, for example, the indication information that the slice associated with the WAB node is partially allowed NSSAI. The registration accept message further comprises time information during which the slice associated with the WAB node is allowed, or the allowed time information and location information.

[0163] Alternatively, the BH AMF network element sends a registration reject message to the WAB-MT through the BH gNB, and the registration reject message comprises the indication information of the WAB node, for example, the indication information of the WAB node is the indication information that the slice associated with the WAB node is partially rejected, for example, the indication information that the slice associated with the WAB node is partially rejected NSSAI. The registration reject message further comprises time information during which the slice associated with the WAB node is rejected, or the rejected time information and location information.

[0164] Exemplarily, if the BH AMF network element determines that the WAB-MT is sent at a time when the slice associated with the WAB is not allowed to work when receiving the first message, the BH AMF network element can reply to the WAB-MT with a registration accept message and indicate that the slice associated with the WAB is partially allowed NSSAI, and indicate the time information when the slice associated with the WAB is allowed to work.

[0165] Alternatively, if the BH AMF determines that the WAB-MT is sent at a time or location when the slice associated with the WAB is not allowed to work when receiving the first message, the BH AMF network element can reply to the WAB-MT with a registration reject message and indicate that the slice associated with the WAB is partially rejected NSSAI, and indicate the time information when the slice associated with the WAB is not allowed to work.

[0166] 503、The WAB-MT sends a third message, and the third message is used for the WAB-MT to request the core network to establish a PDU session, or the third message is used for the WAB-MT to request the core network to register.

[0167] The third message is sent at a time when the slice associated with the WAB node is allowed to work, and the third message is a registration request message.

[0168] Exemplarily, if the second message received by the WAB-MT is a registration reject message, the WAB-MT can determine the time when the slice associated with the WAB is allowed to work according to the time information when the slice associated with the WAB is allowed to work carried in the registration reject message, or determine the time when the slice associated with the WAB is allowed to work according to the time information when the slice associated with the WAB is not allowed to work carried in the registration reject message, and when the WAB-MT is located at the time when the slice associated with the WAB is allowed to work and the location where the slice associated with the WAB is allowed to work has been determined, the WAB-MT sends a registration request message to the BH AMF network element through the BH gNB. In this way, the WAB-MT can re-initiate a registration request within the allowed time and location, so that the WAB-MT can be accepted for registration in time, and wireless backhaul is provided for the WAB-gNB.

[0169] If the second message received by the WAB-MT is a registration accept message, the WAB-MT can determine the WAB-associated slice allowed working time according to the WAB-associated slice allowed working time information carried in the registration accept message, or determine the WAB-associated slice allowed working time according to the WAB-associated slice prohibited working time information carried in the registration accept message, and when the WAB-MT is located in the WAB-associated slice allowed working time and the WAB-associated slice allowed working location has been determined, the WAB-MT sends a PDU session establishment request to the BH AMF network element through the BH gNB. In this way, the WAB-MT can initiate a PDU session establishment request within the allowed working time and location, so that the WAB-MT can establish a PDU session in time, and provide wireless backhaul for the WAB-gNB.

[0170] 504、The core network device sends a fifth message, the fifth message comprising fifth indication information and / or sixth indication information, the fifth indication information indicating that the WAB node-associated slice is accepted for registration; and the sixth indication information indicating that the WAB-MT carries the indication information of the WAB node or the identification information of the core network device in access layer information when establishing connection with the network next time.

[0171] Correspondingly, the WAB-MT receives the fifth message. The core network device is a BH AMF network element, and the fifth message is a registration accept message.

[0172] In some embodiments, the core network device sending the fifth message comprises: the BH AMF network element sending a registration accept message through the BH gNB.

[0173] In some embodiments, the fifth indication information indicating that the WAB node-associated slice is accepted for registration comprises: the fifth indication information indicating that the WAB node-associated slice is an allowed NSSAI. In this way, it is equivalent to that the WAB-MT is accepted for registration.

[0174] Exemplarily, the BH AMF network element sends an initial connection establishment request (initial context setup request) message to the BH gNB, and the initial context setup request message includes indication information indicating that the slice associated with the WAB node is partially allowed. When the BH gNB receives the initial context setup request message, the BH gNB sends a registration acceptance (registration accept) message to the WAB-MT, and the registration accept message includes fifth indication information.

[0175] Exemplarily, the initial context setup request message sent by the BH AMF network element to the BH gNB can further include time information and / or location information in which the slice associated with the WAB node is allowed to work. For the BH gNB, it can be understood that the WAB-MT is accepted for registration. In this way, the WAB-MT can also initiate a registration request again at a time and location in which the WAB node is allowed to work under the condition that the WAB-MT is not allowed to work initially.

[0176] The registration accept message sent by the BH gNB to the WAB-MT can further include sixth indication information indicating that the WAB-MT carries indication information of the WAB node or identification information of the core network device in access layer information when establishing a connection with the network next time. The indication information of the WAB node can be a slice identifier associated with the WAB node. The identification information of the core network device can be a GUAMI. In this way, when the WAB-MT requests registration again, the BH gNB can select an AMF supporting the WAB function according to the registration request message sent by the WAB-MT to authorize the WAB-MT at one time, reducing the overhead caused by AMF redirection.

[0177] 505、The BH gNB sends a sixth message, and the sixth message includes data bearer resources allocated for the WAB node. The sixth message is sent at a time and / or location in which the slice associated with the WAB node is allowed to work.

[0178] Correspondingly, the WAB-MT receives the sixth message.

[0179] It should be understood that if the BH gNB determines that the WAB-MT does not meet the time and / or location requirements in which the WAB node is allowed to work based on the time information and / or location information in which the slice associated with the WAB node is allowed to work carried by the initial context setup request message sent by the BH AMF network element, the BH gNB does not allocate data bearer resources for the slice associated with the WAB.

[0180] When the WAB-MT receives the data bearer resource allocated by the BH gNB, the WAB-MT can establish a data bearer with the BH gNB according to the data bearer resource, so as to provide wireless backhaul for the WAB-gNB on the data bearer, i.e. backhaul the service of the WAB-gNB.

[0181] Optionally, the next steps 506-508 can also be included.

[0182] 506. The BH gNB sends a seventh message, the seventh message being used to request the handover of the WAB-MT from the target network device, the seventh message including time information and / or location information in which the slice associated with the WAB node is allowed to work.

[0183] For example, when the WAB-MT is connected to the BH gNB, the WAB-MT can periodically send a measurement report to the BH gNB, the measurement report indicating the signal quality of the WAB-MT. If the BH gNB determines that the signal quality of the WAB-MT is poor according to the measurement report and needs to perform cell handover, the BH gNB can select a target BH gNB for the WAB-MT, denoted as BH gNB'. The BH gNB corresponds to the source base station, and the BH gNB' corresponds to the target base station. Then, the BH gNB sends a seventh message to the BH gNB'. The seventh message can be understood as a handover request message. The seventh message includes the slice identifier associated with the WAB node and the time information and / or location information in which the slice associated with the WAB node is allowed to work.

[0184] It should be understood that the time information and / or location information in which the slice associated with the WAB node is allowed to work carried in the seventh message can be transmitted from the source base station to the target base station every time the WAB-MT needs to perform cell handover. In this way, the target base station does not need to perform the process of establishing the context of the WAB-MT with the core network, and the signaling overhead can be saved.

[0185] 507. The BH gNB' determines to allocate data bearer resources for the slice associated with the WAB-MT if the WAB-MT is located in the time and location in which the slice associated with the WAB node is allowed to work.

[0186] The implementation of step 507 can refer to the description in step 505.

[0187] 508. The BH gNB' sends indication information to the BH AMF network element that the resources have been allocated for the slice associated with the WAB node.

[0188] In this way, the BH AMF network element can establish a tunnel between the BH AMF network element and the BH gNB', that is, establish a channel for transmitting data between the BH gNB' and the BH AMF network element. The BH gNB' and the BH AMF network element can perform service data transmission of the WAB-gNB.

[0189] For example, the indication information of the slice associated with the WAB node and allocated with resources can be carried in a PDU session resource notification (session resource notify).

[0190] It should be understood that the essential difference between the execution processes of steps 502-503 and steps 504-508 is that, in the execution process of steps 502-503, the WAB-MT determines when it can work by being indicated by the WAB node of the partially allowed time range or the partially rejected time range. In the execution process of steps 504-508, the BH AMF network element directly indicates that the WAB-MT is registered, and indicates the time and / or space range in which the WAB-MT is actually allowed to work to the BH gNB, and whether the WAB-MT is allowed to work is controlled by whether the BH gNB allocates resources to the WAB-MT.

[0191] In addition, in the prior art, when the AMF network element indicates that the UE is partially allowed or partially rejected, the AMF network element does not indicate the working time and space range of the UE partially allowed / rejected to the serving gNB of the UE, because in the prior art, the serving gNB knows whether it supports a certain slice, and as long as the serving gNB supports the slice, the UE is allowed to work, without considering whether other base stations support the slice. In the WAB scenario of the present application, whether the BH gNB supports the slice associated with the WAB node is a different concept from whether the WAB-MT is authorized or accepted to register, and in the case where the BH gNB supports the slice associated with the WAB node, it is further necessary to determine whether the WAB-MT is allowed to work at the current location. Therefore, the present application is different from the prior art, and in the execution process of steps 502-503, the BH AMF network element needs to indicate the partially allowed time range of the slice associated with the WAB node to the BH gNB, and in the execution process of steps 504-508, the BH AMF network element needs to indicate the partially allowed time range and the location range of the slice associated with the WAB node to the BH gNB.

[0192] Thus, in the present application, during the execution of steps 502-503, even if the BH AMF network element determines that the WAB-MT is at a time or location that is not allowed, the BH AMF network element still feeds back a registration acceptance message and indicates to the WAB-MT the indication information of the WAB node associated slice part allowing or part prohibiting, and the WAB-MT itself judges at the allowed time and location, and then initiates registration again. Or initiate a PDU establishment request to access the network. During the execution of steps 504-508, the WAB-MT does not perceive whether it is allowed to work, that is, whether the registration request initiated in the allowed time and location, but receives a registration acceptance message from the BH AMF network element, and whether to allocate resources is determined by the BH gNB whether the WAB-MT is allowed to work. In this way, both of the above-mentioned two ways can flexibly control the authorization state of the WAB-MT, so that the WAB-MT can be authorized in time, and the WAB-gNB provides wireless backhaul.

[0193] As shown in FIG. 6, a flowchart of a communication method provided by an embodiment of the present application is shown. The method is for the case that when the WAB-MT only requests a WAB node associated slice to register, if the WAB node associated slice is refused to register, the WAB-MT is in a deregistered state (rm-deregistered), and there is no connection with the network. The present application proposes that when the WAB node associated slice is refused to register, the WAB-MT can use another non-associated slice to maintain the backhaul link connectivity, so that the WAB-MT can be authorized. The method includes the following processes.

[0194] 601, the WAB-MT sends a first message, and the first message is used for the WAB-MT to request registration to the core network.

[0195] The implementation of step 601 can refer to the description in step 401.

[0196] The difference is that the first message can also carry a first slice. The first slice is used for the WAB-MT to be in a connected state.

[0197] Therefore, in some embodiments, the first message includes an identification of the second slice, and / or an identification of the first slice. Alternatively, the first message can not carry the identification of the first slice, nor the identification of the second slice, which is directly specified by the core network side. The second slice is used to indicate the type of the WAB node. In the present application, the second slice can be understood as the WAB node associated slice in the present application.

[0198] The first slice can be a legal slice pre-configured for the WAB-MT.

[0199] The first slice can also be understood as being able to use the first slice to maintain the backhaul link connectivity when the second slice authorization does not pass.

[0200] In some embodiments, the WAB-MT sending the first message comprises the WAB-MT sending, to a BH AMF network element via a BH gNB, a registration request message.

[0201] 602、The core network device determines that the WAB-MT is rejected for authorization, the second slice authorization is not passed, but the first slice authorization allocated for the WAB-MT is passed.

[0202] For example, the BH AMF network element determines that the second slice of the WAB-MT cannot be authorized or is rejected for registration based on subscription information, or the BH AMF network element determines that the WAB-MT sends the first message in a prohibited time range and / or a prohibited spatial range, and the BH AMF network element determines that the WAB-MT is rejected for authorization.

[0203] In this case, if the first message carries an identifier of the first slice, the BH AMF network element can pass or accept the registration of the first slice. Alternatively, if the first message does not carry the identifier of the first slice, the BH AMF network element can allocate the first slice for the WAB-MT and determine that the first slice is passed for authorization.

[0204] 603、The core network device sends a second message, the second message indicating that the first slice of the WAB node is accepted for registration, the first slice being used for the WAB-MT in a connected state, and the first slice being different from a second slice, the second slice being used for indicating a type of the WAB node.

[0205] Correspondingly, the WAB-MT receives the second message.

[0206] In some embodiments, the second message comprises first indication information, the first indication information indicating that the first slice is accepted for registration.

[0207] In some embodiments, the core network device sending the second message comprises the BH AMF network element sending, to the WAB-MT via the BH gNB, a registration accept message, the registration accept message indicating that the first slice of the WAB node is accepted for registration.

[0208] For example, the first indication information indicating that the first slice is accepted for registration comprises the first indication information indicating that the first slice is an allowed NSSAI.

[0209] In some embodiments, the second message comprises second indication information, the second indication information indicating that the second slice is rejected, or is partially allowed, or is partially rejected.

[0210] Exemplarily, the second indication information indicates that the second slice is a rejected NSSAI or a partially rejected NSSAI or a partially allowed NSSAI.

[0211] Exemplarily, if the first message includes the identity of the second slice, the second message includes the second indication information, and the second indication information indicates that the second slice is a rejected NSSAI or a partially rejected NSSAI or a partially allowed NSSAI.

[0212] If the first message does not include the identity of the second slice, the second message can not include the second indication information, that is, does not indicate whether the second slice is authorized, and the WAB-MT can default that the second slice is rejected for registration. However, the second message includes the first indication information, indicating that the first slice is an allowed NSSAI.

[0213] In this way, it is equivalent that even if the authorization of the second slice fails, the application can still use the first slice for network registration to keep the WAB-MT in the registered state in the network.

[0214] In addition, since the WAB-MT keeps the registered state in the network through the first slice, the network side needs to ensure that the WAB-MT does not use the PDU session established by the identity of the first slice to backhaul the service data of the WAB-gNB. That is, only the PDU session established by the identity of the second slice can backhaul the service data of the WAB-gNB to ensure the exclusivity of the second slice for the WAB-MT.

[0215] Therefore, in the present application, the first slice is not used for the WAB-MT to transmit the service data of the WAB-gNB. In this way, it can be limited that the data packet using the identity of the first slice is transmitted to the core network of the WAB-gNB, that is, when the core network of the WAB-MT receives the data packet including the identity of the first slice, the core network of the WAB-MT will directly discard the data packet.

[0216] Exemplarily, the identity of the first slice can be used for operations and management maintenance (OAM) services other than transmitting the service data of the WAB-gNB. When the BH user plane function (UPF) network element on the core network side receives the data packet carrying the identity of the first slice sent by the WAB-MT, if the BH UPF network element determines that the destination IP address of the data packet is the core network device of the WAB-gNB, the BH UPF determines that the data packet is an illegal data packet, and the BU UPF does not forward the data packet.

[0217] 604、In a case where the second indication information indicates that the second slice is rejected, the core network device sends a third message, the third message indicating that the second slice is allowed; the third message is sent in a time and / or a location in which the second slice is allowed to work.

[0218] Correspondingly, the WAB-MT receives the third message.

[0219] For example, when the second indication information indicates that the second slice is a rejected NSSAI, if the WAB-MT moves to a time range and a location range in which the second slice is allowed to work, the BH AMF network element or the OAM network element can send a third message to the WAB-MT, the third message indicating that the second slice is an allowed NSSAI. The third message is equivalent to a configuration update command, which updates the state of the second slice to an authorized state. Of course, the third message is also sent in a time and a location in which the second slice is allowed to work.

[0220] When the second indication information indicates that the second slice is a partially rejected NSSAI or a partially allowed NSSAI, if the BH AMF network element or the OAM network element determines that the time and / or the location information in which the second slice of the WAB-MT is allowed to work needs to be changed, the BH AMF network element or the OAM network element can send a configuration update command to the WAB-MT, the configuration update command including indication information of updated time and / or location information in which the second slice is allowed to work, i.e., a time range and / or a space range in which the second slice is allowed to work when the second slice is a partially rejected NSSAI or a partially allowed NSSAI.

[0221] Therefore, in a case where the second slice authorization of the WAB-MT fails and the WAB-MT cannot access the network, the first slice can be used to make the WAB-MT authorized to pass, so that the WAB-MT can still remain in a registered state in the network, and the WAB-MT can provide wireless backhaul for the WAB-gNB in time.

[0222] In addition, in the prior art, when a serving gNB of a UE does not allow the UE to access the network at a stage of establishing an RRC connection of the UE, the serving gNB directly rejects the UE to access the network based on a slice identifier requested by the UE. If the serving gNB does not support the slice requested by the UE, the serving gNB can not allocate resources for a PDU session of the slice requested by the UE. That is, the serving gNB only does not activate the PDU session of the slice requested by the UE, but the serving gNB cannot reject the UE to access the network.

[0223] However, in the scenario of the WAB of the present application, the slice associated with the WAB node is not only an identifier of the service for the WAB-gNB, but can also be understood as an identifier of the identity of the WAB node. If the gNB accessed by the WAB-MT does not support WAB-related functions, for example, does not support configuring resource isolation between the WAB-MT and the WAB-gNB (which can also be expressed as not supporting the WAB node serving the MT module and the gNB module working with the same frequency) to reduce interference, or does not support configuring special resources for the WAB-MT (for example, allocating resources to the WAB-MT), it is feasible for the gNB to directly reject the WAB-MT from accessing the network in the RRC connection establishment stage of the WAB-MT. If the WAB-MT is rejected from accessing the network in the RRC connection establishment stage of the WAB-MT, the WAB-MT can only access the BH gNB supporting the WAB function, which is beneficial to the guarantee of the WAB performance.

[0224] Therefore, in the present application, for the slice associated with the WAB node, the gNB not supporting the slice associated with the WAB node can directly reject the WAB-MT from accessing the network. As shown in FIG. 7, a flowchart of a communication method provided by an embodiment of the present application is shown, and the method includes the following flows.

[0225] 701. The WAB-MT sends a first message, the first message indicating that the RRC connection establishment of the WAB-MT is completed, and the first message including an identifier of the slice associated with the WAB node.

[0226] Correspondingly, the gNB receives the first message.

[0227] In some embodiments, when the WAB-MT establishes an RRC connection with the gNB, the WAB-MT sends a first message, the first message being an RRC setup complete message (RRC setup complete message), that is, Msg5 in the random access process, and carrying the identifier of the slice associated with the WAB node.

[0228] The registration request message in the embodiment of the present application can be understood as Msg5 herein.

[0229] 702. The gNB releases the RRC connection with the WAB-MT in the case that the slice associated with the WAB node is not supported.

[0230] For example, when the gNB serves the WAB node as a BH gNB, the gNB can determine that the RRC connection is established for a WAB-MT based on the identity of the slice associated with the WAB node, but in the case where the gNB does not support the slice associated with the WAB node, for example, the gNB does not support configuring resource isolation between the WAB-MT and the WAB-gNB, or does not support configuring special resources for the WAB-MT as a special UE, or does not support serving the WAB node in which the WAB-MT and the WAB-gNB work on the same frequency (i.e., the backhaul link and the access link work on the same frequency), the gNB can send an RRC release message to the WAB-MT. This is equivalent to the gNB directly rejecting the WAB-MT to access the network in the RRC connection establishment stage of the WAB-MT, so that the WAB-MT avoids accessing the BH gNB that does not support the WAB function, which is beneficial to the guarantee of the WAB performance.

[0231] Optionally, the method further includes: the gNB sending a second message, the second message indicating redirection information of the WAB node.

[0232] For example, the second message is an RRC release message, and the RRC release message can further include indication information indicating re-direction, for example, the indication information indicating a beam index for re-direction, so that the WAB-MT performs a cell reselection process after measuring the indicated beam.

[0233] In this way, the present application can make the WAB-MT only access the BH gNB that supports the WAB function, which is beneficial to the guarantee of the WAB performance.

[0234] In some embodiments, as shown in FIG. 7, the process in which the gNB that does not support the slice associated with the WAB node directly rejects the WAB-MT to access the network can also be the process as illustrated in steps 703-704.

[0235] 703. The WAB-MT sends a first message, the first message requesting random access, and the first message is sent on the random access channel resource configured by the slice associated with the WAB node.

[0236] Correspondingly, the gNB receives the first message.

[0237] Exemplarily, the random access channel (RACH) resource configured for the slice associated with the WAB node on the gNB can be configured in a pre-defined or protocol-defined manner, for example, a dedicated RO or a dedicated preamble. The RO can be a physical random access channel (PRACH) occasion or a PRACH transmission occasion.

[0238] The gNB can send the RACH resource configured for the slice associated with the WAB node through a broadcast message.

[0239] The first message is Msg1 in the random access procedure, that is, a random access preamble. In this way, when the WAB-MT initiates random access, the WAB-MT can send Msg1 on the PRACH resource configured for the slice associated with the WAB node.

[0240] 704、The gNB determines to reject the WAB-MT access in the case that the first WAB node associated slice is not supported.

[0241] The gNB can determine that the WAB-MT initiates random access based on the random access channel resource on which the first message is received. If the gNB does not support the first WAB node associated slice, for example, does not support configuring resource isolation between the WAB-MT and the WAB-gNB, or does not support configuring special resources for the WAB-MT as a special UE, or does not support serving the WAB node that the WAB-MT and the WAB-gNB work on the same frequency (that is, the backhaul link and the access link work on the same frequency), the gNB determines to reject the WAB-MT access.

[0242] In some embodiments, the gNB does not send Msg2 to the WAB-MT, that is, does not send a random access response (RAR).

[0243] Alternatively, in some embodiments, the gNB sends a second message, and the second message indicates to reject the WAB-MT access. Accordingly, the WAB-MT receives the second message.

[0244] In this way, the present application can make the WAB-MT access only the BH gNB supporting the WAB function, which is beneficial to the guarantee of WAB performance.

[0245] The embodiments of the present application can also be applied to an open radio access network (open RAN, O-RAN or ORAN). As shown in FIG. 8, it is a schematic diagram of an O-RAN architecture. The O-RAN architecture includes a RIC (RAN intelligent controller), a BH gNB-CU (central unit) and a BH gNB-DU (distributed unit).

[0246] The RIC is used to collect network information and perform necessary optimization tasks, and communicates with the BH gNB-CU and the BH gNB-DU through an E2 interface, that is, the RIC can control both the BH gNB-CU and the BH gNB-DU.

[0247] The BH gNB-CU supports a gNB-CU with O-RAN functions, and communicates with the BH gNB-DU through an F1 interface.

[0248] The BH gNB-DU supports a gNB-DU with O-RAN functions.

[0249] The BH gNB in the embodiments of the present application includes the BH gNB-CU and the BH gNB-DU herein.

[0250] The embodiments of the present application involve a process of interaction between two BH gNBs, which can be the interaction between the BH gNB-CU in the two BH gNBs in the O-RAN architecture and through the RIC.

[0251] For example, if the interaction between the BH gNB and the BH gNB' in the embodiment shown in FIG. 5 is applied to the O-RAN architecture, it can be the interaction between the BH gNB' in the BH gNB-CU through the RIC. As shown in FIG. 9, it is a schematic diagram of an interaction process between BH gNBs in an O-RAN architecture, which includes the following processes.

[0252] 901. The BH gNB-CU sends an E2 message to the RIC, and the E2 message includes the slice identification associated with the WAB node and the time information and / or location information in which the slice associated with the WAB node is allowed to work.

[0253] The E2 message herein is equivalent to the seventh message in step 506.

[0254] 902. The RIC sends an E2 message to the BH gNB'-CU.

[0255] In this way, through the indication on the E2 interface, the RIC can maintain the information of the WAB-MT and forward it between the CUs of the BH gNB.

[0256] It can be understood that, in order to implement the functions in the above embodiments, the WAB node, the base station and the core network device include hardware structures and / or software modules corresponding to the functions. Those skilled in the art should easily understand that, in combination with the units and method steps of the examples described in the embodiments disclosed in the present application, the present application can be realized in the form of hardware or a combination of hardware and computer software. Whether a certain function is implemented in hardware or computer software driven hardware depends on the specific application scenarios and design constraints of the technical solutions.

[0257] FIGS. 10 and 11 are structural schematic diagrams of possible communication apparatuses provided by the embodiments of the present application. The communication apparatuses can be used to implement the functions of the WAB node, the base station or the core network device in the above method embodiments, and thus can also achieve the beneficial effects possessed by the above method embodiments. In the embodiments of the present application, the communication apparatus can be the relay device as shown in FIG. 1, i.e., the WAB node 110-112, or the base station 104-106 as shown in FIG. 1, or the BH AMF as shown in FIG. 2, or a module (such as a chip) applied to the WAB node, the base station or the BH AMF. Among them, the base station 104-106 can be the BH gNB in FIG. 2. The execution process of the WAB node 110-112 can be performed by the WAB-MT.

[0258] As shown in FIG. 10, the communication apparatus 1000 includes a processing unit 1010 and a transceiver unit 1020. The communication apparatus 1000 is used to implement the functions of the WAB-MT, the gNB or the BH AMF in the above method embodiments shown in FIGS. 4-7.

[0259] When the communication apparatus 1000 is used to implement the functions of the WAB-MT in the method embodiment shown in FIG. 4, the transceiver unit 1020 is configured to send a first message to request registration to the core network within the RA, receive a second message indicating that the slice associated with the WAB node is rejected to register, and send a third message to request registration to the core network again within the RA by the WAB-MT. The processing unit 1010 is configured to determine the time and the location at which the third message can be sent when the second message carries the time information and / or the location information in which the slice associated with the WAB node is allowed to work.

[0260] When the communication apparatus 1000 is configured to implement the function of the WAB-MT in the method embodiment shown in FIG. 5, the transceiver 1020 is configured to: send the first message, for the WAB-MT to request registration to the core network; receive the second message, the second message indicating that the slice associated with the WAB node is allowed, or is partially allowed or is partially rejected; send the third message, for the WAB-MT to request the establishment of a PDU session to the core network or for the WAB-MT to request registration to the core network; or, send the fifth message, including the fifth indication information and / or the sixth indication information, the fifth indication information indicating that the slice associated with the WAB node is accepted for registration; the sixth indication information indicating that the WAB-MT carries the indication information of the WAB node or the identification information of the core network device next time when establishing a connection; and receive the sixth message, including the data bearer resource allocated by the WAB node. The processing unit 1010 is configured to determine the time information or the location information in which the slice associated with the WAB node is allowed to work.

[0261] When the communication apparatus 1000 is configured to implement the function of the WAB-MT in the method embodiment shown in FIG. 6, the transceiver 1020 is configured to: send the first message, for the WAB-MT to request registration to the core network; receive the second message, indicating that the first slice is accepted for registration; and in the case that the second slice is rejected according to the second indication information, send the third message, the third message indicating that the second slice is allowed; and the processing unit 1010 is configured to determine the time and / or location in which the second slice is allowed to work.

[0262] When the communication apparatus 1000 is configured to implement the function of the WAB-MT in the method embodiment shown in FIG. 7, the transceiver 1020 is configured to: send the first message, indicating that the RRC connection establishment of the WAB-MT is completed, the first message including the identification of the slice associated with the WAB node; or, send the first message, requesting random access, the first message being sent on the random access channel resource configured by the slice associated with the WAB node.

[0263] When the communication apparatus 1000 is configured to implement the function of the gNB in the method embodiment shown in FIG. 4, the transceiver 1020 is configured to: send the second message sent by the BH AMF to the WAB-MT; and send the third message sent by the WAB-MT to the BH-AMF.

[0264] When the communication apparatus 1000 is configured to implement the function of the gNB in the method embodiment shown in FIG. 5, the transceiver 1020 is configured to: send the first message sent by the WAB-MT to the BH AMF; send the second message sent by the BH AMF to the WAB-MT; send the third message sent by the WAB-MT to the BH AMF; send the fifth message sent by the BH AMF to the WAB-MT; send the sixth message to the WAB-MT; and send the seventh message to the BH gNB’.

[0265] When the communication apparatus 1000 is configured to implement the function of the gNB in the method embodiment shown in FIG. 6, the transceiver unit 1020 is configured to send the first message sent by the WAB-MT to the BH AMF; send the second message sent by the BH AMF to the WAB-MT; send the third message sent by the BH AMF to the WAB-MT.

[0266] When the communication apparatus 1000 is configured to implement the function of the gNB in the method embodiment shown in FIG. 7, the transceiver unit 1020 is configured to receive the first message sent by the WAB-MT; the processing unit 1010 is configured to release the RRC connection with the WAB-MT in the case that the slice associated with the WAB node is not supported. Alternatively, the processing unit 1010 is configured to determine to reject the access of the WAB-MT in the case that the slice associated with the WAB node is not supported.

[0267] When the communication apparatus 1000 is configured to implement the function of the BH AMF in the method embodiment shown in FIG. 4, the transceiver unit 1020 is configured to receive the first message sent by the WAB-MT; send the second message to the WAB-MT; receive the third message sent by the WAB-MT; the processing unit 1010 is configured to determine whether to accept the registration of the WAB-MT according to the third message.

[0268] When the communication apparatus 1000 is configured to implement the function of the BH AMF in the method embodiment shown in FIG. 5, the transceiver unit 1020 is configured to receive the first message sent by the WAB-MT; send the second message to the WAB-MT; receive the third message sent by the WAB-MT; the processing unit 1010 is configured to determine whether to accept the registration of the WAB-MT or establish the PDU session according to the third message. Alternatively, the transceiver unit 1020 is configured to send the fifth message to the WAB-MT; receive the seventh message sent by the BH gNB; receive the indication information that the BH gNB' has allocated resources for the slice associated with the WAB node.

[0269] When the communication apparatus 1000 is configured to implement the function of the BH AMF in the method embodiment shown in FIG. 6, the transceiver unit 1020 is configured to receive the first message sent by the WAB-MT; send the second message to the WAB-MT, indicating that the first slice of the WAB node is accepted for registration; send the third message in the case that the second slice is rejected, indicating that the second slice is allowed; the processing unit 1010 is configured to determine that the registration of the WAB-MT is rejected, but the authorization of the first slice allocated for the WAB-MT is passed.

[0270] For more detailed description of the processing unit 1010 and the transceiver unit 1020, please refer to the relevant description in the method embodiments shown in FIG. 4-7.

[0271] As shown in FIG. 11, the communication apparatus 1100 includes a processor 1110 and an interface circuit 1120. The processor 1110 and the interface circuit 1120 are coupled to each other. It can be understood that the interface circuit 1120 can be a transceiver or an input / output interface. Optionally, the communication apparatus 1100 can further include a memory 1130 for storing instructions executed by the processor 1110 or storing input data required by the processor 1110 to execute instructions or storing data generated after the processor 1110 executes instructions.

[0272] When the communication apparatus 1100 is used to implement the methods shown in FIGs. 4-6, the processor 1110 is configured to implement the functions of the processing unit 1010, and the interface circuit 1120 is configured to implement the functions of the transceiver unit 1020.

[0273] In the present application, when entity A sends information to entity B, it can be that A directly sends to B, or A indirectly sends to B through other entities. Similarly, when entity B receives information from entity A, it can be that entity B directly receives the information sent by entity A, or entity B indirectly receives the information sent by entity A through other entities. Here, entity A and B can be RAN nodes or terminals, or modules inside RAN nodes or terminals. The sending and receiving of information can be the information interaction between RAN nodes and terminals, for example, the information interaction between base stations and terminals; the sending and receiving of information can also be the information interaction between two RAN nodes, for example, the information interaction between CUs and DUs; the sending and receiving of information can also be the information interaction between different modules inside one apparatus, for example, the information interaction between a terminal chip and other modules of the terminal, or the information interaction between a base station chip and other modules of the base station.

[0274] It can be understood that the processor in the embodiments of the present application can be a central processing unit (CPU), and can also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. The general-purpose processor can be a microprocessor or any conventional processor.

[0275] The method steps in the embodiments of the present application can be implemented in hardware or in software instructions executable by a processor. The software instructions can be composed of corresponding software modules, which can be stored in a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an erasable programmable read-only memory, an electrically erasable programmable read-only memory, a register, a hard disk, a mobile hard disk, a CD-ROM, or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor, so that the processor can read information from the storage medium and write information to the storage medium. The storage medium can also be an integral part of the processor. The processor and the storage medium can be located in an ASIC. In addition, the ASIC can be located in a base station or a terminal. The processor and the storage medium can also exist as discrete components in the base station or the terminal.

[0276] In the above embodiments, the implementation can be entirely or partially achieved by software, hardware, firmware, or any combination thereof. When implemented by software, the implementation can be entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer programs or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are entirely or partially performed. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable devices. The computer programs or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another, for example, the computer programs or instructions can be transferred from one website, computer, server, or data center to another by wired or wireless means. The computer-readable storage medium can be any available medium accessible by a computer or a data storage device such as a server, data center, etc. integrated with one or more available media. The available media can be a magnetic medium, such as a floppy disk, a hard disk, a magnetic tape; an optical medium, such as a digital video disc; and a semiconductor medium, such as a solid-state disk. The computer-readable storage medium can be a volatile or non-volatile storage medium, or can include both volatile and non-volatile storage media.

[0277] In various embodiments of the present application, the terms and / or descriptions of different embodiments are consistent and can be mutually referred to if there is no special description and no logical conflict. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0278] In the present application, "at least one" means one or more, "multiple" means two or more. The "and / or" describes the association relationship of the associated objects, which means that there can be three kinds of relationships, for example, A and / or B can represent: A exists alone, A and B exist together, B exists alone, where A, B can be singular or plural. In the text description of the present application, the character " / ", generally indicates that the front and rear associated objects are in an "or" relationship. "Including at least one of A, B and C" can mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B and C.

[0279] It can be understood that various numerical numbers involved in the embodiments of the present application are only distinguished for the convenience of description, and are not used to limit the scope of the embodiments of the present application. The size of the serial number of the above processes does not mean the order of execution, and the execution order of the processes should be determined according to its function and inherent logic.

Claims

1. A communication method characterized by comprising: Comprising: sending a first message for a mobile terminal module of a wireless access backhaul (WAB) node to request registration to a core network in a registration area; receiving a second message indicating that a slice associated with the WAB node is rejected for registration; sending a third message for the mobile terminal module to request registration to the core network again in the registration area, the third message including indication information of the slice associated with the WAB node.

2. A communication method characterized by comprising: Comprising: receiving a first message for a mobile terminal module of a wireless access backhaul (WAB) node to request registration to a core network in a registration area; sending a second message indicating that a slice associated with the WAB node is rejected for registration; receiving a third message for the mobile terminal module to request registration to the core network again in the registration area, the third message including indication information of the slice associated with the WAB node.

3. The method of claim 1 or 2, wherein the second message includes first indication information indicating that, when the mobile terminal module next establishes a connection with a network, indication information of a WAB node and / or identification information of a core network device is carried in access layer information.

4. The method of claim 3, wherein the indication information of the WAB node includes a slice identifier associated with the WAB node; and the identification information of the core network device includes a globally unique access and mobility management function identifier (GUAMI).

5. The method of any one of claims 1-4, wherein the second message includes second indication information indicating time information and / or location information in which the slice associated with the WAB node is allowed to work.

6. The method of claim 5, wherein the third message is sent at the time and / or location in which the slice associated with the WAB node is allowed to work. Comprising: sending a first message for a mobile terminal module of a wireless access backhaul (WAB) node to request registration to a core network; receiving a second message for indicating to the mobile terminal module that a slice associated with the WAB node is allowed, or is partially allowed, or is partially rejected, the second message including time information in which the slice associated with the WAB node is allowed to work; alternatively, the second message is for indicating to a network device accessed by the mobile terminal module that the slice associated with the WAB node is partially allowed, the second message including time information and / or location information in which the slice associated with the WAB node is allowed to work. Comprising:

7. A communication method characterized by comprising: receiving a first message for a mobile terminal module of a wireless access backhaul (WAB) node to request registration to a core network; sending a second message for indicating to the mobile terminal module that a slice associated with the WAB node is allowed, or is partially allowed, or is partially rejected, the second message including time information in which the slice associated with the WAB node is allowed to work. ​ ​ 8. A communication method characterized by comprising: ​ ​ ​ Alternatively, the second message is used to indicate that the slice associated with the WAB node is partially allowed to the network device accessed by the mobile terminal module, and the second message comprises time information and / or location information in which the slice associated with the WAB node is allowed to work.

9. The method of claim 7 or 8, wherein the second message comprises first indication information indicating that the slice associated with the WAB node is partially allowed. The second message comprises second indication information indicating that the slice associated with the WAB node is partially rejected.

10. The method according to claim 7 or 8, characterized in that, 11. The method of claim 9 or 10, wherein the second message further comprises third indication information and / or fourth indication information; The third indication information indicates time information in which the slice associated with the WAB node is allowed to work. The fourth indication information indicates time information in which the slice associated with the WAB node is prohibited to work. The method further comprises: sending a third message, the third message being used for the mobile terminal module to request the core network to establish a protocol data unit (PDU) session, or the third message being used for the mobile terminal module to request the core network to register; 12. The method of claim 7, wherein, The third message is sent at a time in which the slice associated with the WAB node is allowed to work. The method further comprises: receiving a fifth message, the fifth message comprising fifth indication information and / or sixth indication information; 13. The method of claim 7, wherein, The fifth indication information indicates that the slice associated with the WAB node is accepted to register. The sixth indication information indicates that the mobile terminal module carries indication information of the WAB node or identification information of the core network device in access layer information when establishing connection with the network next time. The method further comprises: sending a sixth message, the sixth message comprising data bearer resources allocated for the WAB node; 14. The method of claim 7, wherein, The sixth message is sent at a time and / or a location in which the slice associated with the WAB node is allowed to work. The method further comprises: sending a seventh message, the seventh message being used for requesting handover of the mobile terminal module to a target network device, the seventh message comprising time information and / or location information in which the slice associated with the WAB node is allowed to work.

15. The method of claim 7, wherein, The method further comprises: receiving a third message, the third message being used for the mobile terminal module to request the core network to establish a PDU session, or the third message being used for the mobile terminal module to request the core network to register; 16. The method of claim 8, wherein, The third message is sent at a time and / or a location in which the slice associated with the WAB node is allowed to work. comprising: sending a first message, the first message being used for a mobile terminal module of a wireless access backhaul (WAB) node to request registration with a core network; 17. A method of communication, comprising: receiving a second message, the second message indicating that a first slice of the WAB node is accepted to register, the first slice being used for the mobile terminal module in a connected state, and the first slice being different from a second slice, the second slice being used to indicate a type of the WAB node. comprising: ​ 18. A method of communication, comprising: ​ receiving a first message, the first message being used for a mobile terminal module of a wireless access backhaul (WAB) node to request registration to a core network; sending a second message, the second message indicating that a first slice of the WAB node is accepted for registration, the first slice being used for the mobile terminal module in a connected state, and the first slice being different from a second slice, the second slice being used to indicate a type of the WAB node.

19. The method of claim 17 or 18, wherein the second message comprises first indication information, the first indication information indicating that the first slice is accepted for registration.

20. The method of any of claims 17-19, wherein the first message comprises an identity of the second slice, and / or an identity of the first slice.

21. The method of any of claims 17-20, wherein the second message comprises second indication information, the second indication information indicating that the second slice is rejected, or is partially allowed, or is partially rejected.

22. The method of claim 21, wherein, in a case where the second indication information indicates that the second slice is rejected, the method further comprises: receiving a third message, the third message indicating that the second slice is allowed; the third message is received at a time and / or a location where the second slice is allowed to work.

23. The method of claim 21, wherein, in a case where the second indication information indicates that the second slice is rejected for registration, the method further comprises: sending a third message, the third message indicating that the second slice is allowed; the third message is sent at a time and / or a location where the second slice is allowed to work.

24. A communications device, characterized by comprising: a receiving unit configured to perform the receiving operations in the method of any of claims 1, 3-6, 7, 9-15, 17, or 19-22; a sending unit configured to perform the sending operations in the method of any of claims 1, 3-6, 7, 9-15, 17, 19-22.

25. A communications device, characterized by comprising: a receiving unit configured to perform the receiving operations in the method of any of claims 1, 3-6, 7, 9-15, 17, or 19-22; a sending unit configured to perform the sending operations in the method of any of claims 2-6, 8-11, 16, 18-21, and 23.

26. A computer-readable storage medium, characterized in that, The computer readable storage medium has stored therein computer instructions, which when executed on a communication device, cause the communication device to perform the method of any of claims 1, 3-6, 7, 9-15, 17, or 19-22.

27. A computer-readable storage medium, characterized in that, The computer readable storage medium has stored therein computer instructions, which when executed on a communication device, cause the communication device to perform the method of any of claims 2-6, 8-11, 16, 18-21, or 23.

Images