WO2022006828A1

WO2022006828A1 - Wireless communication method and device

Info

Publication number: WO2022006828A1
Application number: PCT/CN2020/101166
Authority: WO
Inventors: 付喆; 卢前溪
Original assignee: Oppo广东移动通信有限公司
Priority date: 2020-07-09
Filing date: 2020-07-09
Publication date: 2022-01-13
Also published as: CN115486130A

Abstract

Provided are a wireless communication method and device. The method comprises: a terminal device acquiring target unified access control (UAC) information corresponding to a target network slice; and on the basis of the target UAC information, the terminal device determining UAC information for the terminal device and/or determining whether to access a network. On the basis of the technical solution, different UAC information can be used for access control requirements of different network slices, thereby avoiding the problem that UAC information determined on the basis of an access identifier cannot meet an access control requirement of a network slice. Accordingly, the accuracy of access control for the network slice can be improved.

Description

Wireless communication method and device

technical field

The embodiments of the present application relate to the field of communication, and more particularly, to wireless communication methods and devices.

Background technique

Currently, network slicing technology only involves core network nodes. Specifically, when the terminal device reports the required network slice, the network side will select an appropriate access management function (Access Management Function, AMF) according to the network slice reported by the terminal device to establish a service session between the terminal device and the network side. .

The main purpose of unified access control (UAC) is to control network overload or make special restrictions on network applications. Access control is divided into cell-level access control and UE-level access control. Specifically, the access stratum (Access Stratrum, AS) of the terminal device obtains UAC information according to the access identifier and the access category provided by the non-access stratum (Non-Access Stratrum, NAS) or AS, and then executes the execution based on the UAC information. The access control process of the access network slice. The access identifier is used to define different services on each access category or a network slice selection policy (Network Slice Selection Policy, NSSP) adopted by the user.

However, different network slices may correspond to one NSSP, and the access control requirements of different network slices may also be different. Therefore, the UAC information determined based on the access identifier cannot meet the access control requirements of the network slice, and accordingly, the accuracy of the access control of the network slice is too low.

Therefore, there is an urgent need in the art for a method capable of improving the accuracy of access control of network slices.

SUMMARY OF THE INVENTION

Provided are a wireless communication method and device, which can improve the accuracy of access control of network slices.

In a first aspect, a wireless communication method is provided, including:

The terminal device obtains the target unified access control UAC information corresponding to the target network slice;

The terminal device determines UAC information for the terminal device and/or determines whether to access the network based on the target UAC information.

In a second aspect, a wireless communication method is provided, including:

The network device sends target unified access control UAC information corresponding to the target network slice to the terminal device, where the target UAC information is used by the terminal device to determine UAC information for the terminal device and/or determine whether to access the network.

In a third aspect, a terminal device is provided for executing the method in the above-mentioned first aspect or each implementation manner thereof. Specifically, the terminal device includes a functional module for executing the method in the first aspect or each implementation manner thereof.

In a fourth aspect, a network device is provided for executing the method in the second aspect or each of its implementations. Specifically, the network device includes a functional module for executing the method in the second aspect or each implementation manner thereof.

In a fifth aspect, a terminal device is provided, including a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory, so as to execute the method in the above-mentioned first aspect or each implementation manner thereof.

In a sixth aspect, a network device is provided, including a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory, so as to execute the method in the above-mentioned second aspect or each implementation manner thereof.

In a seventh aspect, a chip is provided for implementing any one of the above-mentioned first aspect to the second aspect or the method in each implementation manner thereof. Specifically, the chip includes: a processor for calling and running a computer program from a memory, so that a device installed with the chip executes any one of the above-mentioned first to second aspects or each of its implementations method in .

In an eighth aspect, a computer-readable storage medium is provided for storing a computer program, and the computer program causes a computer to execute the method in any one of the above-mentioned first aspect to the second aspect or each implementation manner thereof.

In a ninth aspect, a computer program product is provided, comprising computer program instructions, the computer program instructions causing a computer to execute the method in any one of the above-mentioned first to second aspects or the implementations thereof.

In a tenth aspect, there is provided a computer program which, when run on a computer, causes the computer to perform the method in any one of the above-mentioned first to second aspects or the respective implementations thereof.

Based on the above technical solutions, according to the access control requirements of different network slices, different UAC information can be used, which avoids the problem that the UAC information determined based on the access identifier cannot meet the access control requirements of the network slices. Correspondingly, it is possible to Improve the accuracy of access control for network slices.

Description of drawings

FIG. 1 and FIG. 2 are examples of the system framework provided by the embodiments of the present application.

FIG. 3 is a schematic flowchart of a wireless communication method provided by an embodiment of the present application.

FIG. 4 is another schematic flowchart of a wireless communication method provided by an embodiment of the present application.

FIG. 5 is a schematic block diagram of a terminal device provided by an embodiment of the present application.

FIG. 6 is a schematic block diagram of a network device provided by an embodiment of the present application.

FIG. 7 is a schematic block diagram of a communication device provided by an embodiment of the present application.

FIG. 8 is a schematic block diagram of a chip provided by an embodiment of the present application.

detailed description

The technical solutions in the present application will be described below with reference to the accompanying drawings.

FIG. 1 is a schematic block diagram of a wireless communication system architecture 100 provided in accordance with the present application.

As shown in FIG. 1 , the system architecture 100 includes a terminal device 110 , an access network device 120 , a core network device 130 and a data network (DN) 160 . The core network device 130 includes a management device 140 and a gateway device 150 .

In some embodiments of the present application, optionally, the terminal device 110 may be configured to connect to the access network device 120 deployed by the operator through a wireless air interface, and then connect to the data network 160 through the core network device 130 . The terminal device 110 may also be referred to as user equipment (user equipment, UE).

For example, the terminal device 110 includes, but is not limited to, a mobile phone, a computer, and can also be a cellular phone, a cordless phone, a session initiation protocol (session initiation protocol, SIP) phone, a smart phone, a wireless local loop (WLL) ) station, personal digital assistant (PDA), computer, laptop computer, handheld communication device, handheld computing device, satellite wireless device, wireless modem card, television set top box (STB), user Premises equipment (customer premise equipment, CPE) and/or other equipment used to communicate over the wireless system.

In some embodiments of the present application, optionally, the access network device 120 may also be referred to as an access network (access network, AN)/radio access network (radio access network, RAN) device. The access network device 120 is mainly used to implement functions such as wireless physical layer functions, resource scheduling and wireless resource management, wireless access control, and mobility management. The access network device 120 may also be referred to as a 5G-AN/5G-RAN node.

For example, the access network device 120 includes but is not limited to: an access point (access point, AP), a next-generation base station (NR NodeB, gNB), a central unit (central unit, CU) and Distributed unit (DU) separate form gNB, transmission receive point (TRP), transmission point (TP) or some other access node.

In some embodiments of the present application, optionally, the core network device 130 is mainly used to implement functions such as call connection, charging, mobility management, and implementation of supplementary services.

For example, the core network device 130 may include a management device 140 and a gateway device 150 . The access network device 120 can communicate with the management device 140 and the gateway device 150 respectively, and the gateway device 150 can communicate with the data network 160 . The management device 140 is mainly used for device registration, security authentication, mobility management and location management of the terminal device, and the gateway device 150 is mainly used to establish a channel with the terminal device, and forward the communication between the terminal device and the external data network on the channel. data pack.

In some embodiments of the present application, optionally, the data network 160 may correspond to a variety of different service domains, such as IP multimedia subsystem (IMS), Internet, Internet protocol television (internet protocol). television, IPTV), other operator business domains, etc., are mainly used to provide a variety of data business services for terminal equipment.

For example, the data network 160 may include network devices such as servers (including servers providing multicast services), routers, and gateways.

It should be noted that FIG. 1 is only an exemplary architecture diagram, and should not be construed as a limitation on itself.

For example, in addition to the functional units shown in FIG. 1 , the network architecture 100 may further include other functional units or functional entities.

FIG. 2 is an example of the system architecture shown in FIG. 1 .

As shown in FIG. 2 , the management device 140 may include a management device access & mobility function (AMF), a session management function (SMF), and a policy control function (PCF) ) and other functional units. The gateway device 150 may include functional units such as a user plane function (UPF), and these functional units may work independently, or may be combined together to implement certain control functions.

In other words, AMF, SMF and PCF can be combined as a management device to complete access control and mobility management functions such as access authentication, security encryption, and location registration of terminal devices, as well as the establishment and release of user plane transmission paths. Session management functions such as changes and changes, as well as the function of analyzing some slice-related data (such as congestion) and terminal device-related data. As a gateway device, UPF mainly performs functions such as routing and forwarding of user plane data. For example, it is responsible for data packet filtering, data transmission/forwarding, rate control, and generation of billing information for terminal devices.

As shown in FIG. 2 , the terminal device 110 can establish a control plane signaling connection with the AMF through the NG interface 1 (NG1, N1); the access network device 120 can establish a control plane signaling connection with the AMF through the NG interface 2 (NG2, N2) connection; the access network device 120 can establish a user plane data connection with the UPF through the NG interface 3 (NG3, N3); the UPF can establish a control plane signaling connection with the SMF through the NG interface 4 (NG4, N4); the UPF can pass the NG interface 6 (NG6, N6) Exchange user plane data with the data network.

Of course, FIG. 2 is only an example of the present application, and should not be construed as a limitation on the present application.

For example, the terminal device 110 can establish an air interface connection with the access network device 120 through the NR interface for transmitting user plane data and control plane signaling; the AMF can establish control plane signaling with the SMF through the NG interface 11 (NG11, N11). The SMF can establish a control plane signaling connection with the PCF through the NG interface 7 (NG7, N7).

It should be noted that the network architecture 100 in the embodiment of the present application may support a PDU connection service, and the PDU connection service refers to a service of exchanging PDU data packets between the UE and the DN.

For example, a service of exchanging PDU data packets between the terminal device 110 and the data network 160. The terminal device realizes the PDU session connection by initiating the establishment of the PDU session. After a single PDU session is established, a data transmission channel between the terminal device 110 and the data network 160 is established. In other words, the PDU session refers to the process of communication between the terminal device 110 and the data network 160 .

In addition, the terminal device 110 may establish multiple PDU session connections, and the SMF corresponding to each PDU session may be different or the same. For example, terminal devices 110 may be connected to the same data network through different UPFs. In other words, a PDU session can have multiple N6 interfaces at the same time. The UPF connecting each N6 interface is called a PDU Session Anchor, and each PDU Session Anchor provides a different path to the same data network. The terminal device 110 may establish multiple PDU sessions, each of which may include multiple data radio bearers (DRBs) on the RAN side.

In some embodiments of the present application, optionally, the PDU data packet may include at least one of the following information: a number, an International Mobile Subscriber Identity (IMSI), an International Mobile Equipment Identity (International Mobile Equipment) Identity, MEI), PDU session identifier (ID), session type (IPv4, IPv6, IPv4v6 and Ethernet frame), uplink and downlink rate, charging ID, roaming status information, IP information of terminal equipment, policy control function equipment (Policy Control function, PCF) information, quality of service (Quality of service, QoS) information, tunnel information, destination address, session management function (Session Management Function, SMF) identification, slice information (if supported), default data radio bearer (Data Radio) Bearer, DRB) information, data network name, access management function (Access Management Function, AMF) information, user location information, session management information, UPF ID, online charging identification, offline charging identification and other related information.

It should be noted that, before the terminal device 110 transmits data, it needs to access the network slice. In other words, a user plane connection between the terminal device 110 and the data network 160 may be established through network slicing. For example, after the access network device 120 selects an AMF capable of supporting the required network slice, one or more PDU sessions connected to the data network 160 may be established through the network slice. Optionally, different network slices have different single network slice selection assistance information (Single Network Slice Selection Assistance Information, S-NSSAI). In other words, S-NSSAI can be used to identify network slices.

Each PDU session can have multiple quality of service flows (Quality of Service flow, QoS Flow), thus, it can be subordinate to different network slices and different transmission performance requirements (such as reliability, transmission delay, transmission rate, etc. ) data communication is carried by different protocol data unit (Protocol Data Unit, PDU) sessions (sessions). For example, the network can carry Enhanced Mobile Broadband (eMBB) and Ultra-Reliable and Low Latency Communication (URLLC) services on different PDU sessions respectively.

Taking the downlink direction as an example, the Non-Access Stratum (NAS) service data flow (SDF) template (template) of the core network device 130 classifies and maps different data packets from the application layer to different Different QoS Flows in the PDU session, and make it sent to the access network device 120 in different PDU sessions. The access network device 120 maps the QoS Flow to different data radio bearers (Data Radio Bearer, DRB) according to the identification (ID) information of the QoS Flow and sends it to the UE through the air interface. Similarly, for uplink data, a similar operation can also be used.

FIG. 3 shows a schematic flowchart of a wireless communication method 200 according to an embodiment of the present application, and the method 200 may be executed by a terminal device. The terminal device shown in FIG. 3 may be the terminal device shown in FIG. 1 .

As shown in FIG. 3, the method 200 includes some or all of the following contents:

S210, the terminal device acquires target unified access control (Unified Access Control, UAC) information corresponding to the target network slice.

S220, the terminal device determines UAC information for the terminal device and/or determines whether to access the network based on the target UAC information.

For example, when the terminal device determines that it needs to access the network, it first obtains the target UAC information corresponding to the target slice, then determines the UAC information of the terminal device based on the target UAC information, and finally determines the UAC information of the terminal device based on the UAC information of the terminal device. Access the network. For example, the terminal device may access the target network slice based on the target UAC information. For another example, when the terminal device determines that it needs to access the network, it first obtains target UAC information corresponding to the target slice, and then determines whether the terminal device can access the network based on the target UAC information. For example, the terminal device may determine whether to access the target network slice based on the target UAC information.

In short, the UAC information for the terminal device can be determined based on the UAC information corresponding to the network slice, and/or whether the terminal device accesses the network or the target network slice can be controlled.

In other words, according to the access control requirements of different network slices, different UAC information can be used, avoiding the problem that the UAC information determined based on the access identifier cannot meet the access control requirements of network slices, and correspondingly, it can improve network slices. accuracy of access control.

It should be noted that, the UAC information may also be corresponding to the granularity of the network slice group. For example, after acquiring the target UAC information corresponding to the target network slice group, the terminal device may determine the UAC information of the terminal device and/or whether to access the network based on the target UAC information.

In some embodiments of the present application, the S210 may include:

The terminal device acquires at least one UAC information corresponding to at least one network slice, where the at least one network slice corresponds to at least one of the same access category, the same access identifier, and the same access level, and the at least one network slice corresponds to at least one of the same access class, the same access identifier, and the same access class A network slice includes the target network slice.

In other words, the at least one network slice is associated with the at least one UAC information, so that after the terminal device determines the network slice that needs to be registered (that is, the target network slice), it can be based on the at least one network slice The correspondence between the slice and the at least one UAC information, and the target UAC information corresponding to the target network slice is determined in the at least one UAC information.

Furthermore, by structuring the at least one network slice to correspond to at least one of the same access class, the same access identity, and the same access class, the access class, the access identity, or the access class can be The corresponding UAC information is converted into the UAC information corresponding to the network slice, which is equivalent to refining the granularity of the UAC information. Accordingly, the accuracy of the access control of the network slice can be improved.

It should be noted that, if the target UAC information acquired by the terminal device is the UAC information corresponding to the target network slice group, the terminal device may also acquire at least one UAC information corresponding to at least one network slice group, the at least one network slice group. The slice group corresponds to at least one of the same access category, the same access identifier, and the same access level, and the at least one network slice includes the target network slice group.

Certainly, the target UAC information may also include UAC information of the target network slice and/or an absolute value used for determining whether to access the target network. In other words, the UAC information of the target network slice and/or whether to access the target network may be determined only by the target UAC information corresponding to the target network slice in the at least one network slice.

Taking an example as an example to facilitate understanding of the present application, the following describes the access category, the access identifier, and the access level.

Illustratively, the access category may be determined based on a triggering event of an access attempt. For example, the following describes the correspondence between the access attempt and the access category with reference to Table 1.

Table 1

As shown in Table 1, the access category can be determined by the triggering event of the access attempt and the conditions related to the terminal device. For example, if the triggering event of the access attempt is a Mobile Originate (MO) signal generated by paging, it may be determined that the access class of the terminal device is access class 0.

Exemplarily, the access class (Access Class, AC) may be used to associate with an access class or an access identity. Optionally, each user may be randomly assigned an AC within (0..9), and the one AC within (0..9) may be stored in the SIM card. Optionally, some special users may have one or more ACs located in (11..15), and the one or more ACs located in (11..15) may be stored in the SIM card. Optionally, the one or more ACs located in (11..15) may have a higher priority. It should be understood that the specific value of the AC may be different from the priority of the AC. For example, the AC numerical order may not be used to represent the priority order of the ACs.

For example, the numerical value of AC can be assigned as follows:

Access levels 0 to 9 can be assigned to ordinary users; access level 11 can be assigned to PLMN management, etc.; access level 12 can be assigned to security sector applications; access level 13 can be assigned to public utilities; 14 may be assigned to emergency services; access class 15 may be assigned to PLMN staff.

Exemplarily, the access identifier may be used to define different services on each access category or a network slice selection policy (Network Slice Selection Policy, NSSP) adopted by the user. Optionally, the access identifier may be determined based on the access level or service type configured for the UE. For example, the relationship between the access identifier and the access UE configuration is described below with reference to Table 2.

Table 2

As shown in Table 2, different UE configurations may have different access identities. For example, if the UE is not configured with any parameters in Table 2, the access identifier of the terminal device may be access identifier 0. For another example, if the UE is configured for MPS, the access identifier of the terminal device may be access identifier 1. For another example, if an access class 11 is configured in the UE, the access identifier of the terminal device may be the access identifier 11 .

In some embodiments of the present application, the S220 may include:

The terminal device determines UAC information for the terminal device and/or determines whether to access the network based on the target UAC information and the first UAC information, where the first UAC information is the same access type, all The UAC information corresponding to the same access identifier or the same access class.

For example, after acquiring the target UAC information and the first UAC information, the terminal device may adjust the first UAC information based on the target UAC information to acquire UAC information for the terminal device.

It should be understood that the function of the first UAC information in this embodiment of the present application is to control network overload or to impose special restrictions on network applications, and the target UAC information is used to adjust the first UAC information. This application does not limit the specific content of the first UAC information. For example, the first UAC information may be used for access control, and optionally, the access control may include cell-level access control and user equipment (User Equipment, UE)-level access control. In other words, the first UAC information may be cell-level access control information or UE-level control information.

For example, the first UAC information may be used for cell-level access control.

Exemplarily, the first UAC information may include at least one of the following information:

Information indicating whether the cell is barred (Cellbarred), information indicating whether the cell is reserved for operational use (cellReservedForOperatorUse), information indicating whether the cell is reserved for other purposes (cellReservedForOtherUse), and information indicating whether Information to allow intraFreqRese.

The information used to indicate whether the cell is barred may indicate that the cell is barred (barred), or may indicate that the cell is not barred (not barred); optionally, the information may be carried in the master-information block (Master-information block). Information Block, MIB); optionally, the information may be for all PLMNs, that is, valid or valid for all PLMNs; for example, if the information indicates that the cell is prohibited, then for all terminal equipment, access is prohibited Network Slicing.

The information used to indicate whether the cell is reserved for operational purposes may be indicated as reserved (Reserved), or may be indicated as not reserved (not Reserved); optionally, the information may be carried in the system information block 1 ( System Information Block 1, SIB1); Optionally, if the information is indicated as reserved, it will have the effect of prohibiting access to some terminal equipment; Interrupting the device has the effect of prohibiting access.

The information used to indicate whether the cell is reserved for other purposes may be indicated as true (True); optionally, the information may be carried in a system information block 1 (System Information Block 1, SIB1).

The information used to indicate whether intraFreqRese is allowed, the information can be indicated as allowed (allowed) or indicated as not allowed (not allowed); optionally, the information can be carried in the main-information block (Master Information Block, MIB); optional, if the current cell is a barred cell, it is allowed to reselect to the same-frequency neighbor cell; The restriction is canceled later; optionally, the certain period of time may be 300s.

For another example, the first UAC information may be used for UE-level access control.

The access control at the UE level may be based on trigger factors, that is, each access attempt is classified into a specified access class, and then the access control is performed based on the access class. Equivalently, probabilistic access can be performed according to trigger factors, which can not only solve all use cases and scenarios, but also reduce the complexity of protocol writing. The UE-level access control can be used for terminal devices in any state. In other words, the methods in the embodiments of the present application can be applied to terminal devices in any state. For example, it can be applied to a terminal device in an idle state (RRC_IDLE state), an inactive state (RRC_INACTIVE state), or a connected state (RRC_CONNECTED state).

The idle state, the inactive state, and the connected state will be described below.

Idle state: mobility is based on UE-based cell selection and reselection, paging is initiated by CN, and paging area is configured by CN; in addition, there is no UE AS context on the access network device side, that is, there is no RRC connection.

Connected state: There is an RRC connection, that is, the UE AS context exists between the access network device side and the UE. The access network device knows the location of the UE at a specific cell level. Mobility is the mobility controlled by the access network equipment. Unicast data can be transmitted between the UE and the access network equipment.

Deactivated state: mobility is UE-based cell selection and reselection, there is a connection between CN-NR, UE AS context exists on an access network device, paging is triggered by RAN, and RAN-based paging area is set by RAN Management, the access network device side knows the location of the UE is based on the paging area level of the RAN.

In some embodiments of the present application, the target UAC information includes adjustment values and/or adjustment factors for at least some parameters in the first UAC information.

Taking an example as an example to facilitate understanding of this solution, the parameters of the first UAC information type are described below. Optionally, the first UAC information may also be referred to as barring information setting (UAC-BarringInfoSet).

Exemplarily, 8 UAC barring information settings (UAC-BarringInfoSet) may be configured, and each access category may be associated with one UAC barring information setting (ie, the first UAC information). For example, access classes may include 64. Optionally, access category 0 may not be configured or associated with UAC barring information settings. It is also possible to configure or associate a UAC barring information setting per PLMN. If the UAC barring information setting is not associated with each PLMN information, the same UAC barring information setting may be used for all PLMNs.

Exemplarily, the terminal device may be triggered to execute the UAC process through the NAS layer, or the terminal device may be triggered to execute the UAC process through the AS. For example, AS-triggered access may include paging-triggered access and RAN-based Notification Area update (RAN-based Notification Area update, RNAU)-triggered access. For example, for the access in response to paging, its access class is 0, that is, the terminal device may not perform access control, in other words, the terminal device may directly initiate the process of accessing the network. For another example, for the access triggered by the RNAU, the access type is 8, that is, the terminal device needs to perform access control.

Specifically, the AS layer obtains the prohibition information setting (ie, the first UAC information) according to the access identifier and the access class provided by the NAS layer or the access class generated by the AS, and then executes the access control process. Optionally, when the NAS trigger event and the AS trigger event trigger the UE to perform the UAC procedure at the same time, the priority of setting the cause value and the access type may be sorted in the following order: paging-triggered access, NAS-triggered event, and RNAU-triggered access.

Exemplarily, the barring information setting may include a UAC barring threshold (uac-BarringFactor), a UAC barring timing (uac-BarringTime), and a UAC barring access identifier (uac-BarringForAccessIdentities).

Based on this, if the corresponding bit of the access identifier in the UAC prohibition information setting is set to 0, it indicates that the access is allowed; if the corresponding bit is set to 1, further judgment is required. For example, a random number A is generated first, and 0≤A<1; if the random number A is lower than uac-BarringFactor, it means that access is allowed, otherwise, it means that access is forbidden. If access is forbidden, a random number B is generated, and 0≤B<1, then T390 is started and T390=(0.7+0.6*B)*uac-BarringTime.

Wherein, T390 may be a timer for access control, or may be a timer started for each access type. Optionally, the access control timer may be specified and maintained at the AS layer. When T390 stops or times out and the access prohibition is released, the AS notifies the NAS layer, which is also based on the access type to notify the access prohibition release. For the handover scenario, the UE may start the UAC procedure after obtaining the valid configuration UAC configuration parameter (SIB1) from the target cell.

It can be seen that after acquiring the first UAC information, the terminal device can convert the UAC information corresponding to the access category to the UAC information corresponding to the network slice based on the target UAC information corresponding to the target network slice, so as to improve the access control of the network slice accuracy.

In some embodiments of the present application, the target UAC information includes the same adjustment value and/or adjustment factor corresponding to all parameters in the first UAC information, and/or the target UAC information includes the first UAC Adjustment value and/or adjustment factor corresponding to at least one parameter in the information.

For example, the target UAC information may include an adjustment value and/or an adjustment factor corresponding to each parameter in the first UAC information.

In some embodiments of the present application, the first UAC information includes a barring factor and/or an access control timing. Optionally, the barring threshold may be the aforementioned uac-BarringFactor. Optionally, the access control timing may be the aforementioned uac-BarringTime or the access control time. Based on this, the target UAC information may include an adjustment value and/or an adjustment factor for the barring threshold, and/or an adjustment value and/or an adjustment factor for the access control timing.

Exemplarily, access category K corresponds to network slice 1 and network slice 2. The UAC information corresponding to the access category K includes the prohibition threshold value of A and the access control timing of B.

For example, for network slice 1, the adjustment factor of A in the UAC information of the access category K is 0.5, and the adjustment factor of B in the UAC information of the access category K is 0.3. If the target network slice is network slice 1, that is, the terminal device selects network slice 1, the UAC information corresponding to the target network slice (ie, network slice 1) is 0.5 and 0.3. Based on this, the UAC information for the terminal device is A*0.5 and B*0.3. In other words, the terminal device can determine whether it can access the network based on A*0.5 and B*0.3.

For another example, for network slice 1, the adjustment value of A in the UAC information of the access type K is C, and the adjustment value of B in the UAC information of the access type K is D. If the target network slice is network slice 1, that is, the terminal device selects network slice 1, the UAC information corresponding to the target network slice (ie, network slice 1) is C and D. Based on this, the UAC information for the terminal device is A+C and B+C. In other words, the terminal device can determine whether it can access the network based on A+C and B+C.

For another example, for network slice 1, the adjustment factor of all parameters in the UAC information of access category K is 0.5. For network slice 2, the adjustment factor of all the information in the UAC information of access category K is 0.3. If the target network slice is network slice 1, that is, the terminal device selects network slice 1, the UAC information corresponding to the target network slice (ie, network slice 1) is 0.5. Based on this, the UAC information for the terminal device is A*0.5 and B*0.5. In other words, the terminal device can determine whether it can access the network based on A*0.5 and B*0.5. If the target network slice is network slice 2, that is, the terminal device selects network slice 2, the UAC information corresponding to the target network slice (ie, network slice 2) is 0.3. Based on this, the UAC information for the terminal device is A*0.3 and B*0.3. In other words, the terminal device can determine whether it can access the network based on A*0.3 and B*0.3.

Certainly, the target UAC information may also include all parameters in the first UAC information or other adjustment amounts of at least one parameter. This application does not specifically limit this.

In some embodiments of the present application, the at least one UAC information is multiple UAC information, and different UAC information in the multiple UAC information includes partially the same information, and/or different UAC information among the multiple UAC information UAC information is completely different.

For example, different UAC information in the plurality of UAC information includes the same barring factor (Barringfactor) and/or access control timing. For another example, different UAC information among the plurality of UAC information includes different barring thresholds (Barringfactors) and/or access control timings.

In some embodiments of the present application, one UAC information of the at least one UAC information corresponds to one or more network slices of the at least one network slice.

In other words, the same access category, the same access identity or the same access class may correspond to one or more UAC information.

Certainly, one UAC information in the at least one UAC information may also correspond to one or more network slice groups in the at least one network slice.

In some embodiments of the present application, the method 200 may further include:

The terminal device sends a mapping relationship to the access network device and/or the core network device, where the mapping relationship includes a corresponding relationship between the at least one network slice and at least one of the following:

the same access class, the same access identity, and the same access class; or

The terminal device receives the mapping relationship sent by the core network device.

For example, after generating the mapping relationship, the terminal device sends the mapping relationship to the access network device and/or the core network device. For another example, after the core network device generates the mapping relationship, the terminal device receives the mapping relationship sent by the core network device.

Certainly, the embodiment of the present application does not specifically limit the sending time or timing of the mapping relationship. For example, the terminal device may directly send the mapping relationship, or the network may trigger the terminal device to send the mapping relationship.

The terminal device determines the target network slice.

Exemplarily, the target network slice is at least one of a network slice selected by the terminal device, expected, interested, preconfigured, allowed, and a network slice with a priority greater than or equal to a certain threshold. Optionally, the target network slice is the union or intersection of network slices selected, expected, interested, preconfigured, allowed, and the priority of which is greater than or equal to a certain threshold by the terminal device. Optionally, the certain threshold may be a statically configured threshold, a dynamically configured threshold, a threshold negotiated between the terminal device and other devices, or a threshold predefined by a protocol.

In some embodiments of the present application, the S210 may include at least one of the following:

The terminal device receives broadcast information sent by an access network device, where the broadcast information includes the target UAC information; or

The terminal device receives dedicated signaling sent by the access network device, where the dedicated signaling includes the target UAC information; or

The terminal device receives pre-configuration information sent by the access network device and/or the core network device, where the pre-configuration information includes the target UAC information; or

The terminal device receives a non-access stratum NAS message sent by a core network device, where the NAS message includes the target UAC information.

For example, the target UAC information may be information generated by a core network device or an access network device and sent to the terminal device.

In some embodiments of the present application, the target UAC information is information determined by the terminal device.

For example, the target UAC information may be information generated by the terminal device.

Exemplarily, the target UAC information is information determined by the terminal device according to at least one of service characteristics, service requirements and network status.

Based on this, the terminal device determines the target UAC information or the core network device determines the target UAC information, which avoids the access network device from broadcasting the target UAC information, which can not only improve the accuracy of access control, but also avoid the need for SIB signaling/base station Impact.

The terminal device receives indication information sent by the access network device, where the indication information is used to indicate whether to use the UAC information corresponding to the network slice; or, the indication information is used to indicate whether to determine whether to use the UAC information corresponding to the network slice The UAC information of the terminal device; or, the indication information is used to indicate whether to access the network based on the UAC information corresponding to the network slice; or the indication information is used to indicate whether to use the access category, access identifier or access level Corresponding UAC information; or, the indication information is used to indicate whether the UAC information for the terminal device is determined based on the UAC information corresponding to the access type, access identifier or access level; or, the indication information is used to indicate Whether to access the network based on the UAC information corresponding to the access type, access identifier or access level.

For example, before acquiring the target unified access control UAC information corresponding to the target network slice, the terminal device may first acquire the indication information, and if the indication information belongs to at least one of the following, acquire the target UAC information :

The indication information is used to indicate that the UAC information corresponding to the network slice is used; or the indication information is used to indicate that the UAC information for the terminal device is determined based on the UAC information corresponding to the network slice; or the indication information is used to indicate Access the network based on the UAC information corresponding to the network slice; or, the indication information is used to indicate that the UAC information corresponding to the access type, access identifier or access level is not used; or, the indication information is used to indicate that the access The UAC information corresponding to the access category, access identifier or access level determines the UAC information for the terminal device; or, the indication information is used to indicate that the UAC information not based on the access category, access identifier or access level corresponds to Access the network.

FIG. 4 is a schematic flowchart of a wireless communication method 300 provided by an embodiment of the present application. The method 300 may be executed interactively by a terminal device and a network device. The terminal equipment shown in FIG. 4 may be the terminal equipment shown in FIG. 1 , the network equipment shown in FIG. 4 may be the core network equipment shown in FIG. 1 , or the access equipment shown in FIG. 1 . network equipment. Optionally, the core network device may be a device with AMF. It should be understood that the method 200 shown in FIG. 3 describes the wireless communication method according to the embodiment of the present application from the perspective of a terminal device. The method 300 shown in FIG. 4 describes the wireless communication method according to the embodiment of the present application in detail from the perspective of the interaction between the terminal device and the network device. For the steps in the method 300, reference may be made to the corresponding steps in the method 200. For brevity, here Repeated content in the method 200 will not be repeated.

As shown in FIG. 4, the method 300 may include:

S310, target UAC information corresponding to the target network slice.

S320, based on the target UAC information, determine UAC information for the terminal device and/or determine whether to access the network.

It should be understood that S320 in the method 300 may refer to S220 in the method 200, and S310 in the method 300 is an implementation manner of S210 in the method 200. In order to avoid repetition, the following describes the implementation manner of the S320 No further description will be given, and only the S310 will be described.

In some embodiments of the present application, the network device sends target unified access control UAC information corresponding to the target network slice to the terminal device, where the target UAC information is used by the terminal device to determine UAC information for the terminal device and/or determine whether to access the network.

For example, the network device sends at least one UAC information corresponding to at least one network slice to the terminal device, where the at least one network slice corresponds to the same access category, the same access In at least one item, the at least one network slice includes the target network slice. Of course, the network device may also send at least one UAC information corresponding to at least one network slice group to the terminal device, where the at least one network slice group corresponds to the same access category, the same access identifier, and the same access at least one of the entry levels, the at least one network slice group includes the target network slice group.

In some embodiments of the present application, the method 300 may further include:

The network device sends first UAC information to the terminal device, where the first UAC information is UAC information corresponding to the same access category, the same access identifier, or the same access level.

For example, the network device is an access network device, and the access network device may send the first UAC information to the terminal device through a broadcast message.

In some embodiments of the present application, the network device is an access network device; the method 300 may further include:

The access network device receives the mapping relationship sent by the terminal device and/or the core network device, where the mapping relationship includes a corresponding relationship between the at least one network slice and at least one of the following:

The same access category, the same access identifier, and the same access class.

In some embodiments of the present application, the network device is a core network device; the method 300 may further include:

The core network device sends a mapping relationship to the access network device and/or the terminal device, where the mapping relationship includes a corresponding relationship between the at least one network slice and at least one of the following:

the same access class, the same access identity, and the same access class; or

The core network device receives the mapping relationship sent by the terminal device.

In some embodiments of the present application, the network device is an access network device, and the S310 may include at least one of the following:

The access network device sends broadcast information to the terminal device, where the broadcast information includes the target UAC information; or the access network device sends dedicated signaling to the terminal device, where the dedicated signaling includes all the target UAC information; or the access network device sends pre-configuration information to the terminal device, where the pre-configuration information includes the target UAC information.

In some embodiments of the present application, the network device is a core network device, and the S310 may include at least one of the following:

The core network device sends pre-configuration information to the terminal device, where the pre-configuration information includes the target UAC information; or the core network device sends a non-access stratum NAS message to the terminal device, the NAS message Include the target UAC information.

In some embodiments of the present application, the network device is an access network device, and the method 300 may further include:

The access network device sends indication information to the terminal device, where the indication information is used to indicate whether to use the UAC information corresponding to the network slice; or, the indication information is used to indicate whether to determine whether to use the UAC information corresponding to the network slice UAC information of the terminal device; or, the indication information is used to indicate whether to access the network based on the UAC information corresponding to the network slice; or, the indication information is used to indicate whether to use the access type, access identifier or access UAC information corresponding to the level; or, the indication information is used to indicate whether the UAC information for the terminal device is determined based on the UAC information corresponding to the access class, the access identifier or the access level; or, the indication information is used for Indicates whether to access the network based on the UAC information corresponding to the access class, access identifier or access class.

The preferred embodiments of the present application have been described in detail above with reference to the accompanying drawings. However, the present application is not limited to the specific details of the above-mentioned embodiments. Within the scope of the technical concept of the present application, various simple modifications can be made to the technical solutions of the present application. These simple modifications all belong to the protection scope of the present application.

For example, the specific technical features described in the above-mentioned specific embodiments can be combined in any suitable manner unless they are inconsistent. In order to avoid unnecessary repetition, this application does not describe any possible combination. State otherwise.

For another example, the various embodiments of the present application can also be combined arbitrarily, as long as they do not violate the idea of the present application, they should also be regarded as the content disclosed in the present application.

It should be understood that in the various method embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not be implemented in the present application. The implementation of the examples constitutes no limitation.

The method embodiments of the present application are described in detail above with reference to FIGS. 1 to 4 , and the apparatus embodiments of the present application are described in detail below with reference to FIGS. 5 to 8 .

FIG. 5 is a schematic block diagram of a terminal device 400 according to an embodiment of the present application.

Referring to FIG. 5, the terminal device 400 may include:

A communication unit 410, configured to acquire target unified access control UAC information corresponding to the target network slice;

The processing unit 420 is configured to determine UAC information for the terminal device and/or determine whether to access the network based on the target UAC information.

In some embodiments of the present application, the communication unit 410 is specifically configured to:

Acquire at least one UAC information corresponding to at least one network slice, where the at least one network slice corresponds to at least one of the same access category, the same access identifier, and the same access level, and the at least one network slice includes the target network slice.

In some embodiments of the present application, the processing unit 420 is specifically configured to:

Determine the UAC information for the terminal device and/or determine whether to access the network based on the target UAC information and the first UAC information, where the first UAC information is the same access type, the same access type Access ID or UAC information corresponding to the same access level.

In some embodiments of the present application, the first UAC information includes a barring threshold and/or an access control timing.

In some embodiments of the present application, the target UAC information includes an adjustment value and/or an adjustment factor for the barring threshold, and/or an adjustment value and/or an adjustment factor for the access control timing.

In some embodiments of the present application, the communication unit 410 is further configured to:

Send a mapping relationship to the access network device and/or the core network device, where the mapping relationship includes a corresponding relationship between the at least one network slice and at least one of the following:

the same access class, the same access identity, and the same access class; or

The mapping relationship sent by the core network device is received.

In some embodiments of the present application, the processing unit 420 is further configured to:

The target network slice is determined.

In some embodiments of the present application, the target network slice is at least one of a network slice selected by the terminal device, expected, interested, preconfigured, allowed, and a network slice with a priority greater than or equal to a certain threshold.

In some embodiments of the present application, the communication unit 410 is specifically configured to perform at least one of the following:

receiving broadcast information sent by an access network device, where the broadcast information includes the target UAC information; or

Receive dedicated signaling sent by an access network device, where the dedicated signaling includes the target UAC information; or

receiving pre-configuration information sent by an access network device and/or a core network device, where the pre-configuration information includes the target UAC information; or

A non-access stratum NAS message sent by a core network device is received, where the NAS message includes the target UAC information.

In some embodiments of the present application, the target UAC information is information determined by the terminal device according to at least one of service characteristics, service requirements, and network status.

Receive indication information sent by the access network device, where the indication information is used to indicate whether to use the UAC information corresponding to the network slice; UAC information; or, the indication information is used to indicate whether to access the network based on the UAC information corresponding to the network slice; or the indication information is used to indicate whether to use the UAC information corresponding to the access type, access identifier or access level ; Or, the indication information is used to indicate whether the UAC information for the terminal device is determined based on the UAC information corresponding to the access category, the access identifier or the access level; or, the indication information is used to indicate whether the UAC information is based on the access The UAC information corresponding to the category, access identifier or access level accesses the network.

It should be understood that the apparatus embodiments and the method embodiments may correspond to each other, and similar descriptions may refer to the method embodiments. Specifically, the terminal device 400 shown in FIG. 5 may correspond to executing the method 200 or the corresponding subject in the method 300 of the embodiments of the present application, and the aforementioned and other operations and/or functions of each unit in the terminal device 400 are for the purpose of realizing For the sake of brevity, the corresponding processes in each method in FIG. 3 or FIG. 4 will not be repeated here.

FIG. 6 is a schematic block diagram of a network device 500 provided by an embodiment of the present application. Optionally, the network device 500 may be a core network device or an access network device.

As shown in FIG. 6, the network device 500 may include:

A communication unit 510, configured to send the target unified access control UAC information corresponding to the target network slice to the terminal device, where the target UAC information is used by the terminal device to determine the UAC information for the terminal device and/or determine whether to access The internet.

In some embodiments of the present application, the communication unit 510 is specifically used for:

sending at least one UAC information corresponding to at least one network slice to the terminal device, the at least one network slice corresponding to at least one of the same access category, the same access identifier, and the same access level, the At least one network slice includes the target network slice.

In some embodiments of the present application, the communication unit 510 is further configured to:

Send first UAC information to the terminal device, where the first UAC information is UAC information corresponding to the same access category, the same access identifier, or the same access level.

In some embodiments of the present application, the network device is an access network device; the communication unit 510 is further configured to:

Receive a mapping relationship sent by the terminal device and/or the core network device, where the mapping relationship includes a corresponding relationship between the at least one network slice and at least one of the following:

In some embodiments of the present application, the network device is a core network device; the communication unit 510 is further configured to:

Send a mapping relationship to the access network device and/or the terminal device, where the mapping relationship includes a corresponding relationship between the at least one network slice and at least one of the following:

the same access class, the same access identity, and the same access class; or

The mapping relationship sent by the terminal device is received.

In some embodiments of the present application, the network device is an access network device, and the communication unit 510 is configured to perform at least one of the following:

sending broadcast information to the terminal device, the broadcast information including the target UAC information; or

sending dedicated signaling to the terminal device, the dedicated signaling including the target UAC information; or

Sending pre-configuration information to the terminal device, where the pre-configuration information includes the target UAC information.

In some embodiments of the present application, the network device is a core network device, and the communication unit 510 is configured to perform at least one of the following:

sending pre-configuration information to the terminal device, where the pre-configuration information includes the target UAC information; or

Send a non-access stratum NAS message to the terminal device, where the NAS message includes the target UAC information.

In some embodiments of the present application, the network device is an access network device, and the communication unit 510 is further configured to:

Sending indication information to the terminal device, where the indication information is used to indicate whether to use the UAC information corresponding to the network slice; or, the indication information is used to indicate whether to determine the UAC for the terminal device based on the UAC information corresponding to the network slice information; or, the indication information is used to indicate whether to access the network based on the UAC information corresponding to the network slice; or, the indication information is used to indicate whether to use the UAC information corresponding to the access type, access identifier or access level; Or, the indication information is used to indicate whether the UAC information for the terminal device is determined based on the UAC information corresponding to the access class, the access identifier or the access class; or the indication information is used to indicate whether the UAC information is based on the access class , UAC information corresponding to the access identifier or the access level to access the network.

It should be understood that the apparatus embodiments and the method embodiments may correspond to each other, and similar descriptions may refer to the method embodiments. Specifically, the network device 500 shown in FIG. 6 may correspond to the corresponding subject in executing the method 300 of the embodiment of the present application, and the aforementioned and other operations and/or functions of the various units in the network device 500 are respectively for the purpose of realizing the method shown in FIG. 4 . For the sake of brevity, the corresponding processes in each of the methods are not repeated here.

The communication device of the embodiments of the present application is described above from the perspective of functional modules with reference to the accompanying drawings. It should be understood that the functional modules can be implemented in the form of hardware, can also be implemented by instructions in the form of software, and can also be implemented by a combination of hardware and software modules.

Specifically, the steps of the method embodiments in the embodiments of the present application may be completed by hardware integrated logic circuits in the processor and/or instructions in the form of software, and the steps of the methods disclosed in conjunction with the embodiments of the present application may be directly embodied as hardware The execution of the decoding processor is completed, or the execution is completed by a combination of hardware and software modules in the decoding processor.

Optionally, the software module may be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers and other storage media mature in the art. The storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps in the above method embodiments in combination with its hardware.

For example, the processing unit and the communication unit referred to above may be implemented by a processor and a transceiver, respectively.

Fig. 7 is a schematic structural diagram of a communication device 600 according to an embodiment of the present application.

Referring to FIG. 7 , the communication device 600 may include a processor 610 .

The processor 610 may call and run a computer program from the memory to implement the methods in the embodiments of the present application.

Please continue to refer to FIG. 7 , the communication device 600 may further include a memory 620 .

The memory 620 may be used to store indication information, and may also be used to store codes, instructions, etc. executed by the processor 610 . The processor 610 may call and run a computer program from the memory 620 to implement the methods in the embodiments of the present application. The memory 620 may be a separate device independent of the processor 610 , or may be integrated in the processor 610 .

Please continue to refer to FIG. 7 , the communication device 600 may further include a transceiver 630 .

The processor 610 can control the transceiver 630 to communicate with other devices, and specifically, can send information or data to other devices, or receive information or data sent by other devices. Transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include antennas, and the number of the antennas may be one or more.

It should be understood that each component in the communication device 600 is connected through a bus system, wherein the bus system includes a power bus, a control bus and a status signal bus in addition to a data bus.

It should also be understood that the communication device 600 may be a terminal device of an embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application. The communication device 600 may correspond to the terminal device 400 in the embodiment of the present application, and may correspond to the corresponding subject in executing the method 200 or the method 300 according to the embodiment of the present application, which is not repeated here for brevity. Similarly, the communication device 600 may be the network device of the embodiments of the present application, and the communication device 600 may implement the corresponding processes implemented by the network device in each method of the embodiments of the present application. That is to say, the communication device 600 in the embodiment of the present application may correspond to the network device 500 in the embodiment of the present application, and may correspond to the corresponding subject in executing the method 300 according to the embodiment of the present application, which is not omitted here for brevity. Repeat.

In addition, the embodiment of the present application also provides a chip.

For example, the chip may be an integrated circuit chip, which has a signal processing capability, and can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The chip may also be referred to as a system-on-chip, a system-on-chip, a system-on-a-chip, or a system-on-a-chip, or the like. Optionally, the chip can be applied to various communication devices, so that the communication device installed with the chip can execute the methods, steps and logic block diagrams disclosed in the embodiments of the present application.

8 is a schematic structural diagram of a chip 700 according to an embodiment of the present application.

Please refer to FIG. 8 , the chip 700 includes the processor 710 .

The processor 710 may call and run a computer program from the memory to implement the methods in the embodiments of the present application.

Please continue to refer to FIG. 8 , the chip 700 may further include a memory 720 .

The processor 710 may call and run a computer program from the memory 720 to implement the methods in the embodiments of the present application. The memory 720 may be used to store instruction information, and may also be used to store codes, instructions and the like executed by the processor 710 . The memory 720 may be a separate device independent of the processor 710 , or may be integrated in the processor 710 .

Please continue to refer to FIG. 8 , the chip 700 may further include an input interface 730 .

The processor 710 may control the input interface 730 to communicate with other devices or chips, and specifically, may acquire information or data sent by other devices or chips.

Please continue to refer to FIG. 8 , the chip 700 may further include an output interface 740 .

The processor 710 can control the output interface 740 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.

It should be understood that the chip 700 can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in the various methods of the embodiments of the present application, and can also implement the various methods of the embodiments of the present application. For the sake of brevity, the corresponding process implemented by the terminal device in FIG. 1 is not repeated here.

It should also be understood that various components in the chip 700 are connected through a bus system, wherein the bus system includes a power bus, a control bus and a status signal bus in addition to a data bus.

The processors referred to above may include, but are not limited to:

General-purpose processor, Digital Signal Processor (DSP), Application Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic devices, discrete gates Or transistor logic devices, discrete hardware components, and so on.

The processor may be used to implement or execute the methods, steps, and logical block diagrams disclosed in the embodiments of this application. The steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module may be located in random access memory, flash memory, read-only memory, programmable read-only memory or erasable programmable memory, registers and other storage media mature in the art. The storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.

The memory mentioned above includes but is not limited to:

Volatile memory and/or non-volatile memory. Wherein, the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically programmable read-only memory (Erasable PROM, EPROM). Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. Volatile memory may be Random Access Memory (RAM), which acts as an external cache. By way of illustration and not limitation, many forms of RAM are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM).

It should be noted that the memory described herein is intended to include these and any other suitable types of memory.

Embodiments of the present application also provide a computer-readable storage medium for storing a computer program. The computer-readable storage medium stores one or more programs including instructions that, when executed by a portable electronic device including a plurality of application programs, enable the portable electronic device to perform method 200 or method 300 The method of the illustrated embodiment.

Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For brevity, here No longer.

Optionally, the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application. , and are not repeated here for brevity.

The embodiments of the present application also provide a computer program product, including a computer program.

Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in each method of the embodiments of the present application. Repeat.

Optionally, the computer program product can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application, in order to It is concise and will not be repeated here.

A computer program is also provided in the embodiments of the present application. When the computer program is executed by the computer, the computer can execute the method of the embodiment shown in the method 200 or the method 300 .

Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program is run on the computer, it causes the computer to execute the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity. , and will not be repeated here.

In addition, an embodiment of the present application further provides a communication system, which may include the above-mentioned terminal equipment and network equipment to form a communication system 100 as shown in FIG. 1 , which is not repeated here for brevity. It should be noted that the terms "system" and the like in this document may also be referred to as "network management architecture" or "network system" and the like.

It should also be understood that the terms used in the embodiments of the present application and the appended claims are only for the purpose of describing specific embodiments, and are not intended to limit the embodiments of the present application.

For example, as used in the embodiments of this application and the appended claims, the singular forms "a," "the," "above," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. meaning.

Those skilled in the art can realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Experts may use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of the embodiments of the present application.

If implemented in the form of a software functional unit and sold or used as a stand-alone product, it may be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of the present application can be embodied in the form of software products in essence, or the parts that make contributions to the prior art or the parts of the technical solutions, and the computer software products are stored in a storage medium , including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the embodiments of the present application. The aforementioned storage medium includes: a U disk, a removable hard disk, a read-only memory, a random access memory, a magnetic disk or an optical disk and other media that can store program codes.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods may be implemented in other manners.

For example, the division of units, modules or components in the apparatus embodiments described above is only a logical function division, and other division methods may be used in actual implementation. For example, multiple units, modules or components may be combined or integrated. To another system, or some units or modules or components can be ignored, or not implemented.

For another example, the above-mentioned units/modules/components described as separate/display components may or may not be physically separated, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units/modules/components may be selected according to actual needs to achieve the purpose of the embodiments of the present application.

Finally, it should be noted that the mutual coupling or direct coupling or communication connection shown or discussed above may be through some interfaces, indirect coupling or communication connection of devices or units, which may be electrical, mechanical or other forms .

The above contents are only specific implementations of the embodiments of the present application, but the protection scope of the embodiments of the present application is not limited thereto. Changes or substitutions should all be covered within the protection scope of the embodiments of the present application. Therefore, the protection scope of the embodiments of the present application should be subject to the protection scope of the claims.

Claims

A wireless communication method, comprising:

The terminal device obtains the target unified access control UAC information corresponding to the target network slice;

The terminal device determines UAC information for the terminal device and/or determines whether to access the network based on the target UAC information.
The method according to claim 1, wherein the terminal device obtains the target unified access control UAC information corresponding to the target network slice, comprising:

The terminal device acquires at least one UAC information corresponding to at least one network slice, where the at least one network slice corresponds to at least one of the same access category, the same access identifier, and the same access level, and the at least one network slice corresponds to at least one of the same access class, the same access identifier, and the same access class A network slice includes the target network slice.
The method according to claim 2, wherein, based on the target UAC information, the terminal device determines the UAC information for the terminal device and/or determines whether to access the network, comprising:

The terminal device determines UAC information for the terminal device and/or determines whether to access the network based on the target UAC information and the first UAC information, where the first UAC information is the same access type, all The UAC information corresponding to the same access identifier or the same access class.
The method according to claim 3, wherein the target UAC information includes adjustment values and/or adjustment factors for at least some parameters in the first UAC information.
The method according to claim 3, wherein the target UAC information includes the same adjustment value and/or adjustment factor corresponding to all parameters in the first UAC information, and/or the target UAC information includes all parameters in the first UAC information. adjustment value and/or adjustment factor corresponding to at least one parameter in the first UAC information.
The method according to claim 3, wherein the first UAC information includes a barring threshold and/or an access control timing.
The method according to claim 6, wherein the target UAC information comprises an adjustment value and/or adjustment factor for the barring threshold, and/or an adjustment value and/or adjustment for the access control timing factor.
The method according to any one of claims 2 to 7, wherein the at least one UAC information is multiple UAC information, and different UAC information in the multiple UAC information includes partially identical information, and/or , different UAC information in the multiple UAC information is completely different.
The method according to any one of claims 2 to 8, wherein one UAC information in the at least one UAC information corresponds to one or more network slices in the at least one network slice.
The method according to any one of claims 2 to 9, wherein the method further comprises:

The terminal device sends a mapping relationship to the access network device and/or the core network device, where the mapping relationship includes a corresponding relationship between the at least one network slice and at least one of the following:

the same access class, the same access identity, and the same access class; or

The terminal device receives the mapping relationship sent by the core network device.
The method according to any one of claims 1 to 10, wherein the method further comprises:

The terminal device determines the target network slice.
The method according to any one of claims 1 to 11, wherein the target network slice is selected, expected, interested, preconfigured, allowed, and the priority of the terminal device is greater than or equal to a certain Threshold at least one of the network slices.
The method according to any one of claims 1 to 12, wherein the terminal device obtains the target unified access control UAC information corresponding to the target network slice, including at least one of the following:

The terminal device receives broadcast information sent by an access network device, where the broadcast information includes the target UAC information; or

The terminal device receives dedicated signaling sent by the access network device, where the dedicated signaling includes the target UAC information; or

The terminal device receives pre-configuration information sent by the access network device and/or the core network device, where the pre-configuration information includes the target UAC information; or

The terminal device receives a non-access stratum NAS message sent by a core network device, where the NAS message includes the target UAC information.
The method according to any one of claims 1 to 12, wherein the target UAC information is information determined by the terminal device.
The method according to claim 14, wherein the target UAC information is information determined by the terminal device according to at least one of service characteristics, service requirements and network status.
The method according to any one of claims 1 to 15, wherein the method further comprises:

The terminal device receives indication information sent by the access network device, where the indication information is used to indicate whether to use the UAC information corresponding to the network slice; or, the indication information is used to indicate whether to determine whether to use the UAC information corresponding to the network slice The UAC information of the terminal device; or, the indication information is used to indicate whether to access the network based on the UAC information corresponding to the network slice; or the indication information is used to indicate whether to use the access category, access identifier or access level Corresponding UAC information; or, the indication information is used to indicate whether the UAC information for the terminal device is determined based on the UAC information corresponding to the access type, access identifier or access level; or, the indication information is used to indicate Whether to access the network based on the UAC information corresponding to the access type, access identifier or access level.
A wireless communication method, comprising:

The network device sends target unified access control UAC information corresponding to the target network slice to the terminal device, where the target UAC information is used by the terminal device to determine UAC information for the terminal device and/or determine whether to access the network.
The method according to claim 17, wherein the network device sends the target unified access control UAC information corresponding to the target network slice to the terminal device, comprising:

The network device sends at least one UAC information corresponding to at least one network slice to the terminal device, where the at least one network slice corresponds to at least one of the same access class, the same access identifier, and the same access class. item, the at least one network slice includes the target network slice.
The method of claim 18, wherein the method further comprises:

The network device sends first UAC information to the terminal device, where the first UAC information is UAC information corresponding to the same access category, the same access identifier, or the same access level.
The method according to claim 19, wherein the target UAC information includes adjustment values and/or adjustment factors for at least some parameters in the first UAC information.
The method according to claim 19, wherein the target UAC information includes the same adjustment value and/or adjustment factor corresponding to all parameters in the first UAC information, and/or the target UAC information includes all parameters in the first UAC information. adjustment value and/or adjustment factor corresponding to at least one parameter in the first UAC information.
The method of claim 19, wherein the first UAC information includes a barring threshold and/or an access control timing.
The method according to claim 22, wherein the target UAC information comprises an adjustment value and/or adjustment factor for the barring threshold, and/or an adjustment value and/or adjustment for the access control timing factor.
The method according to any one of claims 18 to 23, wherein the at least one UAC information is multiple UAC information, and different UAC information in the multiple UAC information includes partially identical information, and/or , different UAC information in the multiple UAC information is completely different.
The method according to any one of claims 18 to 24, wherein one UAC information in the at least one UAC information corresponds to one or more network slices in the at least one network slice.
The method according to any one of claims 18 to 25, wherein the network device is an access network device; the method further comprises:

The access network device receives the mapping relationship sent by the terminal device and/or the core network device, where the mapping relationship includes a corresponding relationship between the at least one network slice and at least one of the following:

The same access category, the same access identifier, and the same access class.
The method according to any one of claims 18 to 25, wherein the network device is a core network device; the method further comprises:

The core network device sends a mapping relationship to the access network device and/or the terminal device, where the mapping relationship includes a corresponding relationship between the at least one network slice and at least one of the following:

the same access class, the same access identity, and the same access class; or

The core network device receives the mapping relationship sent by the terminal device.
The method according to any one of claims 17 to 27, wherein the network device is an access network device, and the network device sends the target unified access control UAC information corresponding to the target network slice to the terminal device, Include at least one of the following:

The access network device sends broadcast information to the terminal device, where the broadcast information includes the target UAC information; or

The access network device sends dedicated signaling to the terminal device, where the dedicated signaling includes the target UAC information; or

The access network device sends pre-configuration information to the terminal device, where the pre-configuration information includes the target UAC information.
The method according to any one of claims 17 to 27, wherein the network device is a core network device, and the network device sends the target unified access control UAC information corresponding to the target network slice to the terminal device, including At least one of the following:

The core network device sends pre-configuration information to the terminal device, where the pre-configuration information includes the target UAC information; or

The core network device sends a non-access stratum NAS message to the terminal device, where the NAS message includes the target UAC information.
The method according to any one of claims 17 to 27, wherein the network device is an access network device, and the method further comprises:

The access network device sends indication information to the terminal device, where the indication information is used to indicate whether to use the UAC information corresponding to the network slice; or, the indication information is used to indicate whether to determine whether to use the UAC information corresponding to the network slice UAC information of the terminal device; or, the indication information is used to indicate whether to access the network based on the UAC information corresponding to the network slice; or, the indication information is used to indicate whether to use the access type, access identifier or access UAC information corresponding to the level; or, the indication information is used to indicate whether the UAC information for the terminal device is determined based on the UAC information corresponding to the access class, the access identifier or the access level; or, the indication information is used for Indicates whether to access the network based on the UAC information corresponding to the access class, access identifier or access class.
A terminal device, characterized in that it includes:

a communication unit, configured to obtain the target unified access control UAC information corresponding to the target network slice;

A processing unit, configured to determine UAC information for the terminal device and/or determine whether to access the network based on the target UAC information.
The terminal device according to claim 31, wherein the communication unit is specifically used for:

Acquire at least one UAC information corresponding to at least one network slice, where the at least one network slice corresponds to at least one of the same access category, the same access identifier, and the same access level, and the at least one network slice includes the target network slice.
The terminal device according to claim 32, wherein the processing unit is specifically configured to:

Determine the UAC information for the terminal device and/or determine whether to access the network based on the target UAC information and the first UAC information, where the first UAC information is the same access type, the same access type Access ID or UAC information corresponding to the same access level.
The terminal device according to claim 33, wherein the target UAC information includes adjustment values and/or adjustment factors for at least some parameters in the first UAC information.
The terminal device according to claim 33, wherein the target UAC information includes the same adjustment value and/or adjustment factor corresponding to all parameters in the first UAC information, and/or the target UAC information includes Adjustment value and/or adjustment factor corresponding to at least one parameter in the first UAC information.
The terminal device according to claim 33, wherein the first UAC information includes a barring threshold and/or an access control timing.
The terminal device according to claim 36, wherein the target UAC information comprises an adjustment value and/or an adjustment factor for the barring threshold, and/or an adjustment value and/or an adjustment value for the access control timing adjustment factor.
The terminal device according to any one of claims 32 to 37, wherein the at least one UAC information is multiple UAC information, and different UAC information in the multiple UAC information includes partially identical information, and/ Or, different UAC information among the plurality of UAC information is completely different.
The terminal device according to any one of claims 32 to 38, wherein one UAC information in the at least one UAC information corresponds to one or more network slices in the at least one network slice.
The terminal device according to any one of claims 32 to 39, wherein the communication unit is further configured to:

Send a mapping relationship to the access network device and/or the core network device, where the mapping relationship includes a corresponding relationship between the at least one network slice and at least one of the following:

the same access class, the same access identity, and the same access class; or

The mapping relationship sent by the core network device is received.
The terminal device according to any one of claims 31 to 40, wherein the processing unit is further configured to:

The target network slice is determined.
The terminal device according to any one of claims 31 to 41, wherein the target network slice is selected, expected, interested, preconfigured, allowed, and the priority of the terminal device is greater than or equal to a certain A threshold of at least one of the network slices.
The terminal device according to any one of claims 31 to 42, wherein the communication unit is specifically configured to perform at least one of the following:

receiving broadcast information sent by an access network device, where the broadcast information includes the target UAC information; or

Receive dedicated signaling sent by an access network device, where the dedicated signaling includes the target UAC information; or

receiving pre-configuration information sent by an access network device and/or a core network device, where the pre-configuration information includes the target UAC information; or

A non-access stratum NAS message sent by a core network device is received, where the NAS message includes the target UAC information.
The terminal device according to any one of claims 31 to 42, wherein the target UAC information is information determined by the terminal device.
The terminal device according to claim 44, wherein the target UAC information is information determined by the terminal device according to at least one of service characteristics, service requirements and network status.
The terminal device according to any one of claims 31 to 45, wherein the communication unit is further configured to:

Receive indication information sent by the access network device, where the indication information is used to indicate whether to use the UAC information corresponding to the network slice; UAC information; or, the indication information is used to indicate whether to access the network based on the UAC information corresponding to the network slice; or the indication information is used to indicate whether to use the UAC information corresponding to the access type, access identifier or access level ; Or, the indication information is used to indicate whether the UAC information for the terminal device is determined based on the UAC information corresponding to the access category, the access identifier or the access level; or, the indication information is used to indicate whether the UAC information is based on the access The UAC information corresponding to the category, access identifier or access level accesses the network.
A network device, characterized in that it includes:

A communication unit, configured to send the target unified access control UAC information corresponding to the target network slice to the terminal device, where the target UAC information is used by the terminal device to determine the UAC information for the terminal device and/or determine whether to access the network .
The network device according to claim 47, wherein the communication unit is specifically configured to:

sending at least one UAC information corresponding to at least one network slice to the terminal device, the at least one network slice corresponding to at least one of the same access category, the same access identifier, and the same access level, the At least one network slice includes the target network slice.
The network device according to claim 48, wherein the communication unit is further configured to:

Send first UAC information to the terminal device, where the first UAC information is UAC information corresponding to the same access category, the same access identifier, or the same access level.
The network device according to claim 49, wherein the target UAC information includes adjustment values and/or adjustment factors for at least some parameters in the first UAC information.
The network device according to claim 49, wherein the target UAC information includes the same adjustment value and/or adjustment factor corresponding to all parameters in the first UAC information, and/or the target UAC information includes Adjustment value and/or adjustment factor corresponding to at least one parameter in the first UAC information.
The network device according to claim 49, wherein the first UAC information includes a barring threshold and/or an access control timing.
The network device according to claim 52, wherein the target UAC information comprises an adjustment value and/or adjustment factor for the barring threshold, and/or an adjustment value and/or an adjustment value for the access control timing adjustment factor.
The network device according to any one of claims 48 to 53, wherein the at least one UAC information is multiple UAC information, and different UAC information in the multiple UAC information includes partially identical information, and/ Or, different UAC information among the plurality of UAC information is completely different.
The network device according to any one of claims 48 to 54, wherein one UAC information in the at least one UAC information corresponds to one or more network slices in the at least one network slice.
The network device according to any one of claims 48 to 55, wherein the network device is an access network device; the communication unit is further configured to:

Receive a mapping relationship sent by the terminal device and/or the core network device, where the mapping relationship includes a corresponding relationship between the at least one network slice and at least one of the following:

The same access category, the same access identifier, and the same access class.
The network device according to any one of claims 48 to 55, wherein the network device is a core network device; the communication unit is further configured to:

Send a mapping relationship to the access network device and/or the terminal device, where the mapping relationship includes a corresponding relationship between the at least one network slice and at least one of the following:

the same access class, the same access identity, and the same access class; or

The mapping relationship sent by the terminal device is received.
The network device according to any one of claims 47 to 57, wherein the network device is an access network device, and the communication unit is configured to perform at least one of the following:

sending broadcast information to the terminal device, the broadcast information including the target UAC information; or

sending dedicated signaling to the terminal device, the dedicated signaling including the target UAC information; or

Sending pre-configuration information to the terminal device, where the pre-configuration information includes the target UAC information.
The network device according to any one of claims 47 to 57, wherein the network device is a core network device, and the communication unit is configured to perform at least one of the following:

sending pre-configuration information to the terminal device, where the pre-configuration information includes the target UAC information; or

Send a non-access stratum NAS message to the terminal device, where the NAS message includes the target UAC information.
The network device according to any one of claims 47 to 57, wherein the network device is an access network device, and the communication unit is further configured to:

Sending indication information to the terminal device, where the indication information is used to indicate whether to use the UAC information corresponding to the network slice; or, the indication information is used to indicate whether to determine the UAC for the terminal device based on the UAC information corresponding to the network slice information; or, the indication information is used to indicate whether to access the network based on the UAC information corresponding to the network slice; or, the indication information is used to indicate whether to use the UAC information corresponding to the access type, access identifier or access level; Alternatively, the indication information is used to indicate whether the UAC information for the terminal device is determined based on the UAC information corresponding to the access class, the access identifier or the access class; or the indication information is used to indicate whether the UAC information is based on the access class , UAC information corresponding to the access identifier or the access level to access the network.
A terminal device, characterized in that it includes:

A processor, a memory and a transceiver, the memory for storing a computer program, the processor for invoking and running the computer program stored in the memory to perform the method of any one of claims 1 to 16.
A network device, characterized in that it includes:

A processor, a memory and a transceiver, the memory for storing a computer program, the processor for invoking and running the computer program stored in the memory to perform the method of any one of claims 17 to 30.
A chip, characterized in that it includes:

A processor for invoking and running a computer program from a memory, so that a device on which the chip is installed performs the method as claimed in any one of claims 1 to 16.
A chip, characterized in that it includes:

A processor for invoking and running a computer program from the memory, so that the device on which the chip is installed performs the method as claimed in any one of claims 17 to 30.
A computer-readable storage medium, characterized by being used for storing a computer program, the computer program causing a computer to execute the method according to any one of claims 1 to 16.
A computer-readable storage medium, characterized by being used for storing a computer program, the computer program causing a computer to execute the method according to any one of claims 17 to 30.
A computer program product comprising computer program instructions that cause a computer to perform the method of any one of claims 1 to 16.
A computer program product comprising computer program instructions, the computer program instructions causing a computer to perform the method of any one of claims 17 to 30.
A computer program, characterized in that the computer program causes a computer to perform the method according to any one of claims 1 to 16.
A computer program, characterized in that the computer program causes a computer to perform the method according to any one of claims 17 to 30.